By adding “CM598-CN ”to configuration, “CANopen Manager” is added automatically.
Double click at “CANopen Manager” to show related parameters/information in a new window.
The tab “General” contains the following parameters:
|
Parameter |
Default value |
Value |
Description |
|
|---|---|---|---|---|
|
General |
||||
|
Node-ID |
1 |
1-127 |
Unique node id for “CANopen Manager”. |
|
|
Check and fix configuration |
This button opens the dialog that allows checking and fixing the current configuration.
|
|||
|
Autostart “CANopen Manager” |
Not supported (“CANopen Manager” always starts automatically). |
|||
|
Polling of optional slaves |
Not supported |
|||
|
Start slaves |
Not supported |
|||
|
NMT start all (if possible) |
Not supported |
|||
|
NMT error behavior |
Not supported |
|||
|
Guarding |
||||
|
Enable heartbeat producing |
Disabled |
Disabled |
The heartbeat generation is disabled. Nodeguarding is enabled instead. Note that CANopen remote devices can also be configured as heartbeat producers. |
|
|
Enabled |
The “CANopen Manager” sends heartbeats according to the interval defined in parameter “Heartbeat time”. If new remote devices with heartbeat functionality are added their behavior will automatically be enabled and configured appropriately. |
|||
|
Node-ID |
1 |
0 -127 |
Unique node id for “CANopen Manager”. |
|
|
Producer time (ms) (only if heartbeat producing is active) |
200 |
1..65535 |
Interval length between successive heartbeats (in milliseconds). |
|
|
SYNC |
||||
|
Enable SYNC producing |
Disabled |
Disabled |
No SYNC telegrams are sent. |
|
|
Enabled |
The “CANopen Manager” sends SYNC telegrams. The synchrounus PDOs are sent directly after the SYNC telegram. |
|||
|
COB-ID (Hex) |
80 |
1-2047 |
COB-ID of the SYNC telegram. |
|
|
Cycle period (µs) |
1000 |
1000-65535000 |
Interval length (in microseconds) after which the SYNC telegram is sent. |
|
|
Window length (µs) |
1200 |
|
Not supported |
|
|
Enable SYNC consuming |
|
|
Not supported |
|
|
TIME |
||||
|
Enable TIME producing |
|
|
Not supported |
|
|
COB-ID (Hex) |
|
|
Not supported |
|
|
Producer time (ms) |
|
|
Not supported |
|
Dialog “Check and fix Configuration”
If you insert several devices below the “CANopen Manager”, then error messages may report multiple assigned Node-IDs or invalid COB-IDs. The “Check and Fix Configuration” button opens a dialog for solving these conflicts.
For conflicts with Node-IDs or PDO COB-IDs, you can click “Edit Conflicts” to open a dialog with detailed information.
|
“Doubled node number ” |
List of all devices with identical IDs. In the field of the “Node-ID” column, you can enter new node numbers for the affected devices. |
|
“ Incorrect and double assignment of PDO COB-IDs ” |
The COB-IDs that are generated automatically from the device description files may not be permitted. All incorrect entries are listed with the respective device names, Node-IDs, and indexes. There are three options for correcting invalid COB-IDs:
|
Corrected entries are removed from the displayed list automatically.
Solve timing problems automatically by using the “Automatic Repair”. The command modifies all timing values to compatible values. (The time should be a multiple of the task time.)
The tab “Live list” can be used to check CANopen network for devices. The tab is only shown in online mode. If communication module is up and running after clicking button “Scan” all remote devices are listed showing their node-Ids and types.