
Communication via CAN bus (CANopen and CANopen Safety)
IKM360M
Date: 21.01.2021
Art. No. 90444
Mod. status 222/20
Page 9 of 58
5
Communication via CAN bus (CANopen and CANopen Safety)
The basis for the inclinometer IKM360R is the CANopen communication profile CiA 301 V4.2,
the device profile for inclinometer CiA 410 V2.0.0. The CANopen Safety protocol EN50325-5 is
additionally implemented for safety-relevant applications. Safety-relevant applications as well
as safety-non-relevant applications can be operated on a CAN bus. The IKM360R supports
device class C1. The details required for a better understanding of the operation are included
in this documentation. If more in-depth information is required, we recommend the
applicable technical literature on CAN, CANopen and CANopen Safety.
5.1
Telegram structure
The data telegram of a CAN message consists of the following fields:
SOF Identifier (COB ID) Control field Data field (max. 8 Byte)
CRC
ACK / EOF
SOF:
(Start of Frame) start bit of the telegram.
Identifier (COB ID):
By means of the identifier, all bus subscribers check whether the message is relevant for
each of them.
The identifier determines the priority of the message. The lower the value of the identifier,
the higher is the priority of the message. This enables preferential transmission of
important messages via the bus.
The Identifier field contains the identifier as well as bits for the recognition of the length of
the identifiers (11 or 29 bits). The device address, channel selection as well as data direction
are determined via the identifier as well.
Thus, the 11bits identifier (COB identifier) consists of a 4bit function code and a 7bit node
number:
Bit no.
10
9
8
7
6
5
4
3
2
1
0
Type
Functional code
Node number (Node ID)
Assignment x
x
x
x
0
0
x
x
x
x
x
The following functional codes have been defined in the "Pre-defined Connection Set" (only
the functional codes used in the present device are shown):
Object
Functional code Resulting COB ID
Object
Page
Network management
(NMT)
0000b
0
-
SYNC message
0001b
128d (80h)
1005h
Emergency message
0001b
128d (80h) + Node ID
1014h
TPD01
0011b
384d (180h) + Node ID
1800h
SDO (tx)
1011b
1408d (580h) + Node ID
1200h
SDO (rx)
1100b
1536d (600h) + Node ID
1200h
Heartbeat message
1110b
1792d (700h) + Node ID
-
Node Guard message
1110b
1792d (700h) + Node ID
-