EC2036 - Measurement IFM - Free user manual and instructions
Find the device manual for free EC2036 IFM in PDF.
| Product Type | Measurement Sensor |
| Model | EC2036 |
| Brand | IFM |
| Category | Measurement |
| Dimensions (H x W x D) | 80 mm x 40 mm x 30 mm |
| Weight | 100 g |
| Power Supply | 24 V DC |
| Operating Temperature | -25°C to +70°C |
| Protection Rating | IP67 |
| Main Functions | Voltage/Current measurement, signal output 4-20 mA |
| Display | LED status indicator |
| Output | Analog (4-20 mA) and switching output |
| Settings | DIP switch configuration |
| Housing Material | Stainless steel / Plastic |
| Electrical Connection | M12 connector |
| Maintenance | Clean with dry cloth; no lubrication required |
| Safety | Comply with EMC directives; correct polarity required |
| Certifications | CE, RoHS |
| Spare Parts | M12 cable, mounting bracket |
| Repairability | Not user-serviceable; contact manufacturer |
| Manual Pages | 59 |
Frequently Asked Questions - EC2036 IFM
User questions about EC2036 IFM
0 question about this device. Answer the ones you know or ask your own.
Ask a new question about this device
Download the instructions for your Measurement in PDF format for free! Find your manual EC2036 - IFM and take your electronic device back in hand. On this page are published all the documents necessary for the use of your device. EC2036 by IFM.
USER MANUAL EC2036 IFM
Hand-held operating terminal for CANopen and layer 2 protocol
Manual CAN Analyser in August 1999
Guarantee
This manual was written with the utmost care. However, we cannot assume any guarantee for the contents.
Since errors cannot be avoided despite all efforts we appreciate any comment.
We reserve the right to make technical alterations to the product which might result in a change of contents of the manual.
- Allgemeines 5
Menu User Defined 37
Menu SDO1 Upload 37
Menu SDO1 Download 38
2.1.2. Menu Input, Output 38
Menu PDO1 Outputs 39
Menu PDO1 Inputs 39
Menu PDOx Outputs 40
Menu PDOx Inputs 40
2.1.3. Menu Trace
Menu Trigger 41
Menu Trigger Type 42
Menu Trigger Message 42
Menu RecTele: 0000 43
2.1.4. Menu Bus-Statistics
Menu Selective 46
Menu All Frames 47
Menu Module List 47
2.2. Menu Node Config.
Menu Set Node ID 48
Menu Set Baudrate 49
Menu I/O Config. 50
Menu Com. Parameter 51
2.3. Menu Layer-2 Main 52
2.3.1. Menu Send Telegram 52
2.3.2. Menu Show Data 53
2.3.3. Menu Trace 53
Menu Trigger 54
Menu Trigger Type 54
Menu RecTele: 0000 55
Menu Selective Read 55
Display of messages 55
2.3.4 Menu Bus-Statistics 56
Menu Selective 56
Menu All Frames 57
2.4. Menu Baudrate 58
F8 Sel. "Select Node by ID"-Telegramm (0x04)
| F1 Auto |
| F2 Pre-trigger |
| F3 Mid-trigger |
| F4 Post-trigger |
| F1 NMT, GUAR, EMCY |
| F2 SDO-Mess. |
| F3 PDO-Mess. |
| F4 All Types |
| F1 NMT-Mess. |
| F2 GUARD-Mess. |
| F3 EMERGCY-Mess. |
| F1 NMT, GUAR, EMGY |
| F2 SDO-Mess. |
| F3 PDO-Mess. |
| F4 All Types |
| F1 Auto |
| F2 Pre-trigger |
| F3 Mid-trigger |
| F4 Post-trigger |
1.1. Safety instructions
Observe the information of the description. Non-observance of the notes, operation which is not in accordance with use as prescribed below, wrong installation or handling can result in serious harm concerning the safety of persons and plants.
The instructions are for authorised persons according to the EMC and low voltage guidelines. The devices must be installed and commissioned by a skilled electrician (programmer or service technician).
This description is part of the device. It contains texts and drawings concerning the correct handling and must be read before installation or use.
If the device is not supplied by the internal voltage source (4 x 1,5 V battery) or the mobile on-board system (24V battery operation), it must be ensured that the external voltage is generated and supplied according to the criteria for safety extra-low voltage (SELV) as this is supplied without further measures to the connected controller, the sensors, and the actuators.
The wiring of all signals in connection with the SELV circuit of the device must also comply with the SELV criteria (safe extra-low voltage, safe electrical separation from other electric circuits).
If the supplied SELV voltage has an external connection to ground (SELV becomes PELV), the responsibility lies with the user and the respective national regulations for installation must be complied with. All statements in these operation instructions refer to the device the SELV voltage of which is not grounded.
The terminals may only be supplied with the signals indicated in the technical data or on the device label and only the approved accessories of ifm electronic gmbh may be connected.
In the case of malfunctions or uncertainties please contact the manufacturer. Tampering with the device can lead to considerable risks for the safety of persons and plant. It is not permitted and leads to the exclusion of any liability and warranty claims.
1.2. Functions
- Ergonomic, easy-to-use user interface with a display of 4 x 16 characters and a pad of 45 membrane keys according to the protection rating IP 65.
- Simple handling by menu-controlled user guidance.
- The baud rate of a module or CAN network can be automatically detected.
- At the CAN layer 2 level the number of the data frames, error frames, overload frames as well as the bus load can be displayed globally or selectively for individual nodes and message types in a cumulative and differential way (in frames per second).
- The list of all connected modules as well as their type can be displayed easily.
- At the user level (CAN layer 7) all types of service and data message can be sent to any CAN nodes and received messages can be indicated in plain language.
- Any user-defined messages can be sent to the CAN bus.
- Digital and analog outputs and inputs can be set and displayed (even without master in the network).
- Writing received messages into the message buffer can be triggered by certain node addresses and message types via four different trigger modes.
- When reading from the message buffer all messages and special message types can be indicated at special node addresses.
- When reading from the message buffer the time stamp can be indicated in steps of 1 ms for each received message.
- The contents of the message buffer can be sent again to the CAN bus. This is done to transfer and further process the traced messages.
1.3. Menu structure
General notes on handling
- The sub-menu is selected with the function keys F1 to F4 (without Shift key).
- With the ESC key the user returns to the higher-level menu. This key is also used to abort all input fields.
- The decimal format is used for the input and output of all node IDs. For the input and output of all other data the hexadecimal format is used.
- The DEL key deletes the last entered character in input fields for numerical values.
- All input fields are confirmed by pressing ENTER.
- The display illumination can be activated or deactivated by pressing the START button. This function is only available when voltage is supplied via the CAN connection (D-SUB socket, pin no. 9).
- The contrast of the display can be set by pressing the + and * buttons.
2. Main menu
| F1 CANopen Main |
| F2 Node Config. |
| F3 Layer-2 Main |
| F4 Baud: 125 kBps |
F1 CANopen Main Opens the CANopen main menu (section 2.1.).
F2 Node Config. Opens the node configuration main menu (section 2.2.).
F3 Layer-2 Main Opens the Layer 2 main menu (section 2.3.).
F4 Baud: 125 kBps Changes the baud rate (section 2.4.).
2.1. Menu CANopen Main
| F1 Service Mess. |
| F2 Input, Output |
| F3 Trace |
| F4 Bus-Statistic |
F1 Service Mess. Enables the sending of service messages (NMT, SDO and user-defined) to any slave nodes.
F2 Input, Output Setting outputs and monitoring inputs via PDO messages.
F3 Trace Tracing and display of messages transferred via the bus at the layer 7 level.
F4 Bus-Statistic Monitoring the bus at the layer 2 level, display of the number of data and error frames as well as the bus load.
2.1.1. Menu Service Mess.
| F1 NMT-Services |
| F2 User Defined |
| F3 SDO1 Upload |
| F4 SDO1 Download |
F1 NMT-Services Sending NMT messages to any slave nodes.
F2 User Defined Sending a user-defined message.
F3 SDO1 Upload Reading a variable of the object directory via a SDO1 message.
F4 SDO1 Download Writing a variable of the object directory via a SDO1 message.
Menu NMT-Services
| Node-ID: ddd |
Node-ID: ddd Input of the slave node address (3 digits, decimal) or "0" for a "broadcast" message (all slave nodes are accessed).
After the slave node address has been entered the menu for the selection of the NMT message type is shown:
| F1 R_Nod | F5 Star |
| F2 R_Com | F6 Disc |
| F3 Preop | F7 Prep |
| F4 ---- | F8 Sel. |
F1 R_Nod "Reset Node" message (0x81)
F2 R_Com "Reset Communication" message (0x82)
F3 Preop "Go Preoperational" message (0x80)
F4 ---- reserved
F5 Star "Start Node" message (Go Operational) (0x01)
F6 Disc "Disconnect" message (0x03)
F7 Prep "Prepare Node" message (0x02)
F8 Sel. "Select Node by ID" message (0x04)
After selection of the NMT message type the message is sent.
Menu User Defined
Length: d Input of the data length of the message (DLC).
Dat. Input of the data of the message (with RTR = 1 messages no data are entered).
After the last data byte has been entered the message is sent. With the ENTER key the message can now be sent repeatedly. By pressing the ESC key you return to the menu "Service-Mess.". With the Z key the message can be sent cyclically and automatically every 100 ms.
Menu SDO1 Upload
| Node-ID: ddd |
| Index: xxxx |
| Subindex: xx |
Node-ID: ddd Input of the slave node address (3 digits, decimal) or "0" for a "broadcast" message (all slave nodes are accessed).
Index: xxxx Input of the variable index of the object directory (4 digits, hexadecimal).
Subindex: xx
Input of the variable subindex of the object directory (2 digits, hexadecimal).
After the subindex has been entered the SDO message is sent and the terminal awaits the response from the module. If the variable has been read successfully, the node ID is followed by (+), if not by (-). The contents of the variable (or an error code) are now indicated in line 4 of the display (e.g. Rsp: 1234 56 78).
With the keys and the variable with the next higher or lower index can be read. With the and keys the subindex can be increased or decreased. The PgUp or PgDn keys search for the next valid variable.
Only SDOs with a length of max. 4 bytes are supported.
Menu SDO1 Download
| Node-ID: ddd |
| Index: xxxx |
| Subindex: xx |
| Length: d or Dat: |
Node-ID: ddd Input of the slave node address (3 digits, decimal) or "0" for a "broadcast" message (all slave nodes are accessed).
Index: xxxx Input of the variable index of the object directory (4 digits, hexadecimal).
Subindex: xx Input of the variable subindex of the object directory (2 digits, hexadecimal).
Length: d: Input of the data length (1 to 4, 1 digit, decimal).
Dat: 00 ... 00 After the input of the data length the data are entered.
After the last data byte has been entered the SDO message is sent and the terminal awaits a response from the module. If writing to the variable has been successful, the node ID is followed by (+), if not by (-). If the response is negative, the error codes are indicated in line 4 of the display (e.g. Rsp: 12 34 56 78).
Only SDOs with a length of max. 4 bytes are supported. The input is hexadecimal with the most significant byte being entered first and the least significant byte last.
2.1.2. Menu Input, Output
| F1 PDO1 Outputs |
| F2 PDO1 Inputs |
| F3 PDOx Outputs |
| F4 PDOx Inputs |
F1 PDO1 Outputs Enables the setting of digital outputs.
F2 PDO1 Inputs Monitors digital inputs.
F3 PDOx Outputs Enables the setting of analog or digital outputs (PDO1 to PDO9).
F4 PDOx Inputs Monitors analog or digital inputs (PDO1 to PDO9).
Menu PDO1 Outputs
After the last data byte has been entered (depending on "Length") it is checked whether the module is already in the "OPERATIONAL" state and controlled by a bus master. Otherwise, the module is set to the "Operational" state by means of a "NMT-START-NODE" message and cyclically monitored with Guarding RTR messages every 100 ms.
With an SDO upload the COB identifier of the PDO1 is requested from the module and the data are cyclically sent via a "PDO1 message" every 100 ms until the key "ESC" is pressed. If no master was active, the node is then reset to "Pre-Operational".
Menu PDO1 Inputs
After the node ID has been entered it is checked whether the module is already in the "OPERATIONAL" state and controlled by a bus master. If not, the module is set to the "Operational state" by means of a "NMT-START-NODE" message.
With a SDO upload the COB identifier of the PDO1 is requested from the module and the data are cyclically requested from the module via a "RTR PDO1 message" every 100 ms. During the display the PDO no. can be changed with the numerical keys "1" to "9". By pressing the key "ESC" the display of data is finished and if no master was active the node is reset to "Pre-Operational".
Menu PDOx Outputs
After the last data byte has been entered (depending on "Length") it is checked whether the module is already in the "OPERATIONAL" state and controlled by a bus master. Otherwise the module is set to the "Operational" state with a "NMT-START-NODE" message and cyclically monitored with Guarding RTR messages every 100 ms.
With a SDO upload the COB identifier of the desired PDO is requested from the module and the data are cyclically sent via a "PDOx message" every 100 ms until the key "ESC" is pressed. If no master was active, the node is then reset again to "Pre-Operational".
Menu PDOx Inputs
After the node ID has been entered it is checked whether the module is already in the "OPERATIONAL" state and controlled by a bus master. Otherwise the module is set to the "Operational" state by means of a "NMT-START-NODE" message.
With a SDO upload the COB identifier of the desired PDO is requested from the module and the data are cyclically requested from the module via a "RTR-PDOx message" every 100 ms. During the display the PDO no. can be changed with the numerical keys "1" to "9".
By pressing "ESC" the data display is finished and if no master was active, the node is reset again to "Pre-Operational".
2.1.3. Menu Trace
| F1 Trigger: AUTO |
| F2 RecTele: 0000 |
| F3 Start, *Stop |
| F4 Send Buffer |
| F1 Trigger: AUTO | Displays the current trigger mode. With the F1 key the trigger mode and the trigger conditions can be changed (=> menu "Trigger"). |
| F2 RecTele: 0000 | Enables to look at the messages transferred via the bus with the key F2. The number of the received messages is indicated right-aligned.Since the buffer can only contain 1024 messages the first messages are overwritten by current messages if this number is exceeded. |
| F3 _Start, *Stop | Starts or stops the writing of the current messages transferred via the bus into the buffer. If the trigger type is not set to "AUTO", starting or stopping the writing into the buffer depends on the occurrence of the trigger condition according to the selected trigger type. "*" before "_Start" or "_Stop" indicates the current state "Reception" or "Reception stopped".!" at the end of the 4th display line (after "F4 Send Buffer") indicates that the bus transmission is disturbed (error frames were received). |
| F4 Send Buffer | Sends the buffer contents to the CAN bus. This is done to transfer and further process the traced messages, e.g. to an external PC. |
Menu Trigger
| F1 Trigger: AUTO |
| F2 Node-IDs: |
| 3,4,12,103 |
| F3 Msg: NMT |
F1 Trigger: AUTO Selection of the trigger type (=> menu "Trigger type").
F2 Node-IDs Input of max. four node addresses whose messages release triggering or "0" for all node addresses.
F3 Msg: NMT Selection of the message type which releases triggering (=> menu "trigger message").
Menu Trigger Type
| F1 Auto |
| F2 Pre-trigger |
| F3 Mid-trigger |
| F4 Post-trigger |
F1 Auto Triggering is released by no message. The cyclical writing of current messages into the buffer starts by pressing "*Start" in the menu "Trace" and stops by pressing "*Stop" in the menu "Trace".
F2 Pre-Trigger Current messages are continuously and cyclically written into the buffer by pressing "*Start" in the menu "Trace". When the trigger condition is met or by pressing "*Stop" in the menu "Trace", the reception stops.
F3 Mid-Trigger Current messages are continuously and cyclically written into the buffer by pressing "*Start" in the menu "Trace". When the trigger condition is met, writing new messages into the buffer continues until half the buffer is overwritten or by pressing "*Stop" in the menu "Trace".
F4 Post-Trigger Writing current messages into the buffer only starts when the trigger condition is met and "*Start" in the menu "Trace" has been pressed. Writing into the buffer continues until the whole buffer is full or by pressing "*Stop" in the menu "Trace".
Menu Trigger Message
| F1 NMT, GUAR, EMCY |
| F2 SDO-Mess. |
| F3 PDO-Mess. |
| F4 All Types |
F1 NMT, GUAR, EMCY Selection of the type of service message which releases triggering
| F1 NMT-Mess. |
| F2 GUARD-Mess. |
| F3 EMERGCY-Mess. |
F1 NMT-Mess.: All NMT messages release triggering.
F2 GUARD-Mess.: All Guard messages release triggering.
F3 EMERGCY-Mess.: All Emergency messages release triggering.
F2 SDO-Mess. All SDO messages release triggering.
F3 PDO-Mess. All PDO messages release triggering.
F4 All Types All message types release triggering.
Menu RecTele: 0000
| Read Buffer: |
| F1 Selective |
| F2 All Telegrams |
F1 Selective
Only certain message types with certain node IDs are displayed.
F2 All Telegrams All messages are displayed.
The following sub-menu is shown by selecting "Selective Read".
| Filt. Node-IDs: |
| 003 004 012 103 |
Node IDs Input of maximum four node addresses whose messages are to be displayed or "0" for messages of all node addresses.
Then the message type is selected:
| F1 NMT, GUAR, EMGY |
| F2 SDO-Mess. |
| F3 PDO-Mess. |
| F4 All Types |
F1 NMT, GUAR, EMGY Selection of which type of service message is to be displayed.
F1 NMT-Mess.
F2 GUARD-Mess.
F3 EMERGCY-Mess.
F1 NMT-Mess.: All NMT messages release triggering.
F2 GUARD-Mess.: All Guard messages release triggering.
F3 EMERGCY-Mess.: All Emergency messages release triggering.
F2 SDO-Mess. Only all SDO messages are displayed.
F3 PDO-Mess. Only all PDO messages are displayed.
F4 All Types All message types are displayed.
The selected messages from the buffer are then displayed.
All messages in the buffer or the messages in the buffer selected in the menu "Selective Read" are displayed in plain language. With the selected trigger type "Auto" the first message in the buffer is indicated. With all other trigger types the first message displayed is the one in the buffer which released triggering.
The keys ↑ and ↓ enable scrolling through the buffer contents. With the keys Home and End you jump to the beginning or end of the buffer contents.
The first three characters of the message display show the node address (3 digits, decimal) of the message. Then comes the message type in plain language consisting of 12 characters. For messages which contain additional data these data are indicated right-aligned in hexadecimal format in the following line.
With the T key the time stamp for the messages can be indicated (toggle). The display is in 4 digits in decimal format in steps of 1 ms starting when "F3 *Start* has been pressed (e.g. 012 SDO1 ST:0732). With the key "0" the time stamp for the message in the first display line can be set to "0000" as a reference time stamp.
List of the abbreviations of all message types and examples of representation on the display
| CANopen Func. Code | Message Abbreviation | Additional data | |
| 0x0 NMT NMT State | |||
| 0x1 Synchronisation | (Node ID 0) | SYNC - | |
| 0x1 Emergency | (Node ID 1...127) | PDOEMGY Data | |
| 0x2 Time stamp TIMESTAMP Data | |||
| 0x3 PDO1 (tx) PDO1S2M Data | |||
| 0x4 PDO1 (rx) PDO1M2S Data | |||
| 0x5 PDO2 (tx) PDO2S2M Data | |||
| 0x6 PDO2 (rx) PDO2M2S Data | |||
| 0xB SDO (tx) | SDO1S2M Data | ||
| 0xC | SDO (rx) | SDO1M2S Data | |
| 0xE Nodeguard | GUARD Data | ||
| RTR messages | RTR | - | |
Examples
| 011 SDO1M2S-UPLD |
| 1401 01:No Data |
| 011 SDO1S2M-UPLD |
| 1401 01:0B0300C0 |
First message: SDO1 Upload from the master to the slave with the ID 11 and the index 0x1401, subindex 0x01.
Second message: SDO1 Upload response from the slave with the ID 11 to the master and the index 0x1401, subindex 0x01 and the data 0x0B, 0x03, 0x00, 0xC0.
| 011 NMT START_NO |
| 011 PDOEMCY: |
| 0010812001000000 |
| --- RTR-Telegram |
First message: NMT Start Node to the module with the ID 11 (decimal).
Second message: PDO Emergency with the data 0x00, 0x10, 0x81, 0x20, x01, x00, x00, x00.
Third message: RTR message.
With RTR messages neither the message type nor the node ID can be indicated. Owing to the characteristics of the Intel 82C527 „--- RTR-Telegram“ is always indicated.
2.1.4. Menu Bus-Statistics
| Bus-Statistics: |
| F1 Selective |
| F2 All Frames |
| F3 Module List |
F1 Selective Selection of certain message frames via "Acceptance Mask" and "Acceptance Code" (=>menu "Selective").
F2 All Frames Display of the bus statistics for all message frame types (=> menu "All Frames").
F3 Module List Display of the modules which are active on the bus.
Menu Selective
| EnterFrameFilter |
| --Use Keys 0-F-- |
| FEDCBA9876543210 |
| X10XX01X1100XXXX |
This allows to define a filter for the bus statistics of the data frames and the bus load at the layer 2 level. It has an effect on the 1st and 2nd bytes of the CAN message (COB ID). In the CANopen protocol the CAN identifier is set up as follows:
1st byte:
| bit ‘F’ | bit ‘E’ | bit ‘D’ | bit ‘C’ | bit ‘B’ | bit ‘A’ | bit ‘9’ | bit ‘8’ |
| CANopen Function Code most significant 4 bits of the node ID | |||||||
2nd byte:
| bit '7' | bit '6' | bit '5' | bit '4' | bit '3' | bit '2' | bit '1' | bit '0' |
| least significant 3 bits of the node ID RTR bit data length (DLC) | |||||||
The "Frame Filter" indicates which bits of the 1st and 2nd bytes of the CAN identifier are to be set (bit = 1), to be reset (bit = 0) or are not to be considered (bit = X) so that the message can pass the filter thus being considered for the bus statistics. With the keys 0 - 9 or A - F the individual bits of the 16-bit mask can be changed. With the key "ENTER" the bus statistics are indicated by using the entered filter.
Menu All Frames
| Fr/s Tot. |
| Data: 215 5310 |
| Error: 10 34 |
| Busld: 30% 45% |
Data Display of the number of the data frames per s and their total number.
Error Display of the number of the error frames per s and their total number.
Overl Display of the number of the overload frames per s and their total number.
Busld Display of the bus load in % per s and the total bus load in %.
With the key "0" all values can be reset to zero. If a value becomes greater than "9999", "OvFI" (overflow) is indicated.
Menu Module List
| 003 6DI 2DO |
| 004 8DO |
| 008 4AI-16 |
| 101 4AO-16 |
Indicates all modules which are active on the bus. The keys and are used to scroll through the list. The keys Home and End are used to jump to the beginning and end of the module list.
The first three characters of the message display indicate the node address (3 digits, decimal) of the active module. Then comes the module type with the number of the input bytes or channels:
Example 6DI 2DO: 6 digital inputs (8 bits each) and 2 digital outputs
8DO: 8 digital outputs (8 bits each)
4AI-16: 4 analog input channels (16 bits each)
4AO-16: 4 analog output channels (16 bits each)
2.2. Menu Node Config.
Specially for the non programmable bus modules with CANopen capabilities from ifm electronic some device parameters must be set before using the modules. The parameters are the node number (node ID) and the baud rate. The valid default setting is specified in the data sheets of the devices.
Also, the module configuration can be changed. A module connection can for example be configured as a digital output or an analog input. The possible settings are stated in the data sheets of the devices.
To avoid conflicts with the node configuration only one module should be connected to the CAN analyser. Since with some settings the CAN analyser performs master services no other network master (e.g. ecomat R 360) must be active.
| F1 Set Node ID |
| F2 Set Baudrate |
| F3 I/O Config. |
| F4 Com. Parameter |
F1 Set Node ID Setting of the module number (node number).
F2 Set Baudrate Setting of the module baud rate.
F3 I/O Config. Setting of the requested input/output configuration.
F4 Com. Parameter Setting of the module communication parameters Guard time and Life time.
Menu Set Node ID
After selection of the menu point first enter the number of the node (3 digits, decimal) for which the new setting is to be valid.
| Node-ID: ddd |
After pressing ENTER the new node number (3 digits, decimal) can be entered in the next line.
After pressing ENTER again the new node number is entered. If the configuration is successful, (+) is indicated in the first line and the CAN analyser immediately performs a node reset. Thus the new number becomes valid immediately.
If the configuration is not successful, (-) is shown in the first line.
Menu Set Baudrate
After selection of the menu point first enter the number of the node (3 digits, decimal) for which the new setting is to be valid.
| Node-ID: ddd |
After pressing ENTER the new baud rate can be directly entered as a decimal numerical value (4 digits, decimal, e.g. 50, 250, 1000) in the next line. The default value is 125 (125 Kbits/s).
| Node-ID: ddd |
| Baudrate: dddd |
After pressing ENTER again the new baud rate is entered. If the configuration is successful, (+) is indicated in the first line. The baud rate does not become valid until the user has performed a node reset (via software or by turning power on and off).
If the configuration is not successful, (-) is shown in the first line.
Menu I/O Config.
After selection of the menu point first enter the number of the node (3 digits, decimal) for which the new setting is to be valid.
| Node-ID: ddd |
After pressing ENTER the PWM frequency can be entered if the module allows this setting. The default value is 100 (100 Hz). The setting is valid for the whole module.
In the next line the wire break and short circuit diagnosis for modules with diagnostic capabilities can be activated and deactivated. The default setting is 0 (off). The setting is valid for the whole module.
In the lines 3 and 4 the configuration of the input/output channel can be changed. To do so, the channel number and then the type are entered.
| PWM-Frq: ddd |
| Diag. 0/1: d |
| Channel: dd |
| Type: dd |
With pressing ENTER the new PWM frequency, the diagnostic state and the configuration of the selected channel are transferred. If the configuration is successful, (+) is indicated in the corresponding line.
If the configuration is not successful or the function is not valid for the connected module, (-) is indicated.
After input of the values in line 4 and pressing ENTER the channel number is increased by 1 in the third line. This enables a channel configuration in rising order. Only the channel type must be entered.
Pressing ESC terminates the configuration.
Menu Com. Parameter
After selection of the menu point first enter the number of the node (3 digits, decimal) for which the new setting is to be valid.
| Node-ID: ddd |
After pressing ENTER the guard time can be entered. The default value is 500 (500 ms).
In the next line the life time can be set. The default value is 3.
| Node-ID: ddd |
| GuardTime: ddddd |
| Life-Time: ddd |
The settings are valid for the whole module.
2.3. Menu Layer-2 Main
| F1 Send Telegram |
| F2 Show Data |
| F3 Trace |
| F4 Bus-Statistic |
F1 Send Telegram Enables to send any message.
F2 Show Data Monitoring of data of a module via RTR messages.
F3 Trace Tracing and display of the messages transferred via the bus at the layer 2 level.
F4 Bus-Statistic Bus monitoring at the layer 2 level, display of the number of data and error frames as well as the bus load.
2.3.1. Menu Send Telegram
Length: d Input of the data length of the message (DLC).
Dat: Input of the data of the message (with RTR = 1 messages no data are entered).
After the last data byte has been entered the message is sent. With the Enter key the message can now be sent repeatedly. You return to the main menu by pressing ESC. With the Z key the message can be sent automatically and cyclically every 100 ms.
2.3.2. Menu Show Data
| COB-ID: xxx |
| Length: d |
| D.:xx xx xx xx |
| xx xx xx xx |
COB-ID: xxx Input of the complete CAN-ID (3 digits, hexadecimal, 11 bits)
Length: d Display of the number of the data bytes
D.: xx xx xx xx Display of data
The indicated data are updated every 200 ms via RTR message requests.
2.3.3. Menu Trace
| F1 Trigger: AUTO |
| F2 RecTele: 0000 |
| F3 _Start, *Stop |
| F4 Send Buffer |
F1 Trigger: AUTO Display of the current trigger mode. By pressing F1 the trigger mode and the trigger conditions can be changed (=> menu "Trigger").
F2 RecTele: 0000 By pressing F2 it is possible to look at the messages transferred via the bus. The number of the received messages is shown right-aligned.
Since the buffer can only contain 1024 messages the first messages are overwritten by current messages if this number is exceeded.
F3 _Start, *Stop Starts or stops writing current messages transferred via the bus into the buffer. If the trigger type is not set to "AUTO", starting or stopping the writing into the buffer depends on the occurrence of the trigger condition according to the selected trigger type. "*" before "_Start" or "_Stop" indicates the current state "Reception" or "Reception stopped". "!" at the end of the 4th display line (after "F4 Send Buffer") indicates that the bus transmission is disturbed (error frames received).
F4 Send Buffer Sends the contents of the buffer to the CAN bus. This is done to transfer and further process the traced messages, e.g. to an external PC.
Menu Trigger
| F1 Trigger: AUTO |
| F2 COBI-IDs: |
| 181,194,201,701 |
F1 Trigger: AUTO Selection of the trigger type (=> menu "Trigger type").
F2 COB-IDs Input of maximum four CAN COB IDs whose messages release triggering or "FFF" for all IDs (3 digits, hexadecimal, 11 bits).
Menu Trigger Type
| F1 Auto |
| F2 Pre-trigger |
| F3 Mid-trigger |
| F4 Post-trigger |
F1 Auto Triggering is released by no message. The cyclical writing of current messages into the buffer starts by pressing "*Start" in the menu "Trace" and stops by pressing "*Stop" in the menu "Trace".
F2 Pre-Trigger Current messages are continuously and cyclically written into the buffer by pressing "*Start" in the menu "Trace". When the trigger condition is met or by pressing "*Stop" in the menu "Trace" the reception stops.
F3 Mid-Trigger Current messages are continuously and cyclically written into the buffer by pressing "*Start" in the menu "Trace". When the trigger condition is met writing new messages into the buffer continues until half the buffer is overwritten or by pressing "*Stop" in the menu "Trace".
F4 Post-Trigger Writing current messages into the buffer only starts when the trigger condition is met and "*Start" in the menu "Trace" has been pressed. Writing into the buffer continues until the whole buffer is full or by pressing "*Stop" in the menu "Trace".
Menu RecTele: 0000
| Read Buffer: |
| F1 Selective |
| F2 All Telegrams |
F1 Selective Only certain message types with certain COB IDs are displayed (=> menu "Selective Read").
F2 All Telegrams All messages are displayed (=> display "Messages").
Menu Selective Read
| Filt. COB-IDs: |
| 181 194 201 701 |
COB-IDs: Input of max. four CAN COB IDs whose messages are to be displayed or "FFF" for messages of all IDs (3 digits, hexadecimal, 11 bits)
Display of messages
All messages in the buffer or the messages in the buffer selected in the menu "Selective Read" are displayed in plain language. With the selected trigger type "Auto" the first message in the buffer is indicated. With all other trigger types the first message displayed is the one in the buffer which released triggering.
The keys ↑ and ↓ enable scrolling through the buffer contents. With Home and End you can jump to the beginning and the end of the buffer contents.
The first three characters of the message display are the CAN COB ID (3 digits, hexadecimal, 11 bits) of the message. Then come the data of the message in hexadecimal format.
With the T key the time stamp for the messages can be indicated (toggle). The display is in 4 digits in decimal format in steps of 1 ms starting after "F3 *Start" has been pressed (e.g.: 012 90 FF T:0732).
Examples of how the messages are represented on the display:
| 181 AB CD EF |
| 194 FF DD CC BB |
| 77 88 99 12 |
| --- RTR-Telegram |
With RTR messages the COB ID cannot be indicated. Owing to the characteristics of the Intel 82C527 "--- RTR-Telegram" is always displayed.
2.3.4 Menu Bus-Statistics
| Bus-Statistics: |
| F1 Selective |
| F2 All Frames |
F1 Selective Selection of certain message frames via "Acceptance Mask" and "Acceptance Code" (=> menu "Selective").
F2 All Frames Display of the bus statistics for all message frame types (=> menu "All Frames").
Menu Selective
| EnterFrameFilter |
| --Use Keys 0-F-- |
| FEDCBA9876543210 |
| X10XX01X1100XXXX |
This allows to define a filter for the bus statistics of the data frames and the bus load at the layer 2 level. It has an effect on the 1st and 2nd bytes of the CAN message (COB ID). In the CANopen protocol the CAN identifier is set up as follows:
1st byte:
| bit ‘F’ | bit ‘E’ | bit ‘D’ | bit ‘C’ | bit ‘B’ | bit ‘A’ | bit ‘9’ | bit ‘8’ |
| most significant 8 bits of the COB ID | |||||||
2nd byte:
| bit '7' | bit '6' | bit '5' | bit '4' | bit '3' | bit '2' | bit '1' | bit '0' |
| least significant 3 bits of the COB ID RTR bit data length (DLC) | |||||||
The "Frame Filter" indicates which bits of the 1st and 2nd bytes of the CAN identifier are to be set (bit = 1), to be reset (bit = 0) or are not to be considered (bit = X) so that the message can pass the filter thus being considered for the bus statistics.
With the keys 0-9 or A-F the individual bits of the 16-bit mask can be changed.
With the key "ENTER" the bus statistics are indicated by using the entered filter.
Menu All Frames
| Fr/s Tot. |
| Data: 215 5310 |
| Error: 10 34 |
| BusId: 30% 45% |
Data Display of the data frames per s and their total number
Error Display of the number of the error frames per s and their total number.
Overl Display of the number of the overload frames per s and their total number.
Busld Display of the bus load in % per s and the total bus load in %.
With the key "0" all values can be reset to zero. If a value becomes greater than "9999", "OvFl" (overflow) is indicated.
2.4. Menu Baudrate
| F1 1M F5 100k |
| F2 500k F6 50k |
| F3 250k F7 20k |
| F4 125k F8 AUTO |
After power on the default baud rate is 125 Kbits/s.
With the keys F1 to F7 the requested baud rate can be selected.
F8 AUTO automatically determines the baud rate of the connected modules or of the CAN network in the range of 1 Mbits/s to 10Kbits/s. The "Scan" operation does not stop before the baud rate is clearly detected.