CANopen gateway
Wieland Electric GmbH | BA000970 | 07/2019 [9855]
142
NOTICE
This also applies to the SDO index in data bytes 2 and 3, which is of the data type UINT. This means
that the low byte is transmitted in data byte 2 and the high byte in data type 3.
Example:
The following messages are required to read SDO 1003,1 of the CANopen device with de-
vice address 2. The data type of the data to be read is UDINT.
The client sends:
CAN ID
DLC
Data
602h
8
40h
03h
10h
01h
00h
00h
00h
00h
The server responds:
CAN ID
DLC
Data
582h
8
42h
03h
10h
01h
08h
00h
50h
02h
The combined response data result in the 32-bit word 02500008h.
SDO object directory
78681739
Each CANopen device manages its SDOs in an object directory. The complete
object directory is formally described in an EDS file. Many CANopen tools can ready this EDS file and
therefore know the object characteristics of the CANopen device.
The following table shows all SDOs for the SP-CANopen gateway.
Table 105: Supported SDOs
SDO #
Type
1000
Device type
1001
Error register
1003
Error list (error history)
1005
COB ID SYNC
1008
Device name
1009
Hardware version
100A
Software version
100C
Guard Time
100D
Life Time Factor
1016
Consumer Heartbeat Time
1017
Producer Heartbeat Time
1018
Identification
1027
Module list
1400…1403
Communication parameter for RxPDO 1 … 4
1600…1603
Mapping parameter for RxPDO 1 … 4
1800…1803
Communication parameter for TxPDO 1 … 4
1A00…1A03
Mapping parameter for TxPDO 1 … 4
3100
Module status bits
3200
Config-CRC
3300
Module type code
6000
Process data input objects
6200
Process data output objects
You will find more detailed information about these SDOs in the CANopen standard draft DS 301
V4.02 (DSP 301 V4.1).
10.10