Data Interface CANopen®
English, Revision 06, Date: 12.07.2011
39
5.1.2
RxPDO
The RxPDO contains the system configuration in two bytes. A dynamic mapping is not
designed. The RxPDO operation mode is asynchronous.
The RxPDO can be momentarily activated/deactivated due to setting/deleting the
most significant bits in the COB-identifier [1600,01].
RxPDO will be received with the Identifier 0x200 + Node-ID.
5.2
Heartbeat
The Optical Line Tracker supports the Heartbeat mode. Whenever a Heartbeat time >
0 is set in the CAN menu, the device status is transmitted under identifier (0x700 +
Node address) once the heartbeat timer has expired. The guard time is then set to 0.
5.3
Node Guarding
Whenever the Heartbeat time is set to 0, the device replies to a Remote Transmission
Request of the Identifier (0x700 + Node address) with the device status (refer to Table
10 above), while the highest bit changes. The device does not monitor the timely re-
ception of RTR Frames.
5.4
Description of the Service Data Objects (SDOs)
The service data object is used to access to the object index. An SDO is always trans-
mitted with a confirmation, i. e. each reception of the message is acknowledged. The
identifiers for read and write access are:
Read access:
0x600 + Node address,
Write access:
0x580 + Node address.
The SDO telegrams are described in the CiA standard DS-301. The error codes in
case of faulty communication are listed in the following table:
Value
Character
Range
Remark
Config
unsigned 16
0..0xffff
configuration bits according Table 31 on page 48
Table 9
Character description of the RxPDO_1
Node status
Code
stopped
0x04
preoperational
0x7f
operational
0x05
Table 10
Coding of the Node status