
Communication via CAN bus (CANopen and CANopen Safety)
IKM360M
Date: 21.01.2021
Art. No. 90444
Mod. status 222/20
Page 13 of 58
5.3.1.1
Transmit-PDO (from the IKM360R to the master)
PDO transfer from the IKM360R to the bus master can be initiated as a result of various
events:
asynchronous, controlled by an internal device timer
synchronous as a response to a SYNC telegram
as a response to an RTR message
The TPDO1 contains the slope long16. The transfer behavior of TPDO1 is determined via the
objects 1800h and 1A00h and is assigned to asynchronous transmission. Synchronous data
transmission is set at delivery. Other TPDOs are not supported.
COB ID
Process data in binary code
Byte 0 (LSB)
Byte 1 (MSB)
TPDO1
180h + Node ID
Slope long16
Table 9: TPDO message
Asynchronous data transmission
If a TPDO1 is to be sent cyclically, 254 (FEh) or 255 (FFh) must be entered in object 1800h,
sub-index 02h. The cycle time can be entered in milliseconds in object 1800h, sub-index 05h.
The TPDO1 will not be sent if the value 0 ms is written. The function is disabled. The minimum
value to be set is 1h (= 1 ms).
Synchronous data transfer
As delivered, the device responds to every SYNC Message received with the output of the
TPDO1 message. 1h is entered for synchronous transmission in object 1800h, sub-index 02h.
If a value n is entered between 1d and 240d (= F0h), the device will respond to every nth
SYNC message.
RTR
Queries can be sent via RTR (see chapter
) toTPDO1.
5.4
Parameter data exchange
5.4.1
Transmission of Service Data Objects (SDO)
Service data objects serve mainly device configuration via the directory of objects. SDOs in
the expedited Request/Response and in the normal Request/Response are supported.
The identifier is set to 11 bits and cannot be changed.
Two SDO services are available:
SDO (rx) (Master
Slave): 600h + Node ID
SDO (tx) (Slave
Master): 580h + Node ID
Two SDO services are available!