“Node-ID”

The node number identifies the CANopen Remote Device uniquely. It corresponds to the number (value between 1 and 127) set on the device (hardware). You have to provide the Node-ID as a decimal.

“Expert settings”

: All settings are displayed that are predefined by the device description (EDS file) for the device.

“SDO channels (...)”

Click this button to open a dialog for activating the SDO channels that are predefined in the EDS file. Service data objects (SDOs) allow access to all entries in the CANopen object directory. An SDO creates a peer-to-peer communication channel between two devices (SDO server and client channel).

“Optional device”

: The slave is optional and not required for starting the CAN network.

“Sync producing”

Available only when the “Enable sync producing” option is cleared in the CANopen Manager.

: The I/O transmission is synchronized on the bus. The slave works as a sync producer. The parameters of the sync interval are defined in the settings of the CANopen Manager.

“No initialization”

This option is for non-configurable slave that already start with a valid configuration.

: The master does not send configuration SDOs or NMT start commands to the slave. PDO communication and monitoring (heartbeat, node guarding) are performed when this has been configured in the configurator.

If the slave does not start automatically, then the user can use the CiA405 NMT function block to send an NMT start command to the slave.

“Default settings”

The availability of this option depends on the contents of the device description file.

: Activated by default. The slave nodes are reset to the default parameters before the configuration is loaded to the device or always when the slave is configured. Which parameters can be set is device-specific. The concrete task is performed from the subindex of the list box.

“Autoconfig PDO mapping”.

This option is available for modular devices only.

PDO mapping is generated automatically from the definitions in the device description and then cannot be changed in the two mapping dialogs. If the automatically generated mapping does not match your application, then you can deactivate the option and configure the mapping manually. We recommend that this option is activated for standard applications.

Node guarding is an outdated monitoring method and should not be used anymore because is uses RTR frames. You should always use heartbeats whenever possible. In some exceptions, such as for older slaves, you can use only node guarding.

“Enable node guarding”

: The CANopen Manager sends a message to the slave in the “Guard time (ms)” interval. If the slave does not respond with the given “Guard COB-ID” (Communication Object Identifier), then the CANopen Manager resends this message as many times as defined in “Lifetime factor” or until the slave responds.

If the slave does not respond, then it is marked as "unavailable".

“Guard time (ms)”

Interval for sending messages (default: 200 ms)

“Lifetime factor”

When the slave does not respond, a node-guarding error is established according to the “Lifetime factor” time multiplied by the “Guard time”.

“Enable heartbeat producing”

: The module sends heartbeats in the time intervals as given in “Producer time (ms)”.

“Producer time (ms)”:

The default setting is 200 as long as there is no special entry or the entry in the device description file is 0.

“Heartbeat consuming (...)”

Opens a “Heartbeat Consuming Properties” dialog. There you activate the slaves that you want to watch.

The number of possible slaves to be monitored is defined in the EDS file. To do this, you must select the "Enable" check box and enter the Node-ID of the slave and the required values in the “Heartbeat time” field (in milliseconds). Then the slave monitors the heartbeats that are sent from the affected slaves (defined by the Node-ID). When no more heartbeats are received, the slave switches off the I/Os.

When a slave is monitoring, a green check mark is displayed on the “Heartbeat Consuming” button.

Note: When you insert a device with the heartbeat function, its heartbeat settings are harmonized automatically with the master (CANopen Manager).

“Activate Emergency”

: When internal errors occur, the slave sends emergency messages with a unique COB-ID. You can read these messages by using the function blocks from the library ‎CAA Can Low Level Extern‎ (‎RECV_EMCY_DEF‎, ‎RECV_EMCY‎).

“COB-ID”

CAN ID of the EMCY message. Range of possible values: [1...2047].

The availability of this function depends on the device description.

“Enable TIME producing”

: The device sends TIME messages.

“COB-ID (Hex)”

(Communication Object Identifier): identifies the time stamp of the message.

“Enable TIME consuming”

: The device processes TIME messages.

The respective information is read from the firmware of the CANopen Slave (0x1018 identity object) and compared to the information from the EDS file. In case of disparities, the configuration is stopped and the slaves are not started.

“Vendor ID”

: Check of the vendor ID at startup

“Product number”

: Check of the product number at startup

“Revision number”

: Check of the revision number at startup