CANopen
• 83
Network Communication
WAGO-I/O-SYSTEM 750
CANopen
Function
code
Resulting COB-ID
Object directory
index
Communication objects
dec
bin
dec
bin
hex
Broadcast
messages
NMT Command
Sync message
System time
Alarm objects
0
1
2
1
0000
0001
0010
0001
0
128
256
129-255
80
100
81-FF
1005, 1006, 1007
1012, 1013
1014, 1015
Tx-PDO1
Rx-PDO1
Tx-PDO2
Rx-PDO2
Tx-PDO3
Rx-PDO3
Tx-PDO4
Rx-PDO4
3
4
5
6
7
8
9
10
0011
0100
0101
0110
0111
1000
1001
1010
385-511
513-639
641-767
769-895
897-1023
1025-1151
1153-1279
1281-1407
181-1FF
201-27F
281-2FF
301-37F
381-3FF
401-47F
481-4FF
501-57F
1800
1400
1801
1401
1802
1402
1803
1403
Tx-SDO
Rx-SDO
11
12
1011
1100
1409-1535
1537-1663
581-5FF
601-67F
1200
1200
Peer-to-
Peer
messages
node monitoring
14
1110
1793-1919 701-77F
100C, 100D
1016, 1017
The parameters required for the communication objects as well as the parame-
ters and data of the CANopen subscribers are filled in the object directory.
Type and number of objects supported by the node depend on the individual
fieldbus coupler.
In addition to several special objects, i.e. for the network management (NMT),
for synchronization (SYNC) or for error messages (EMCY), the communica-
tion profile contains the two object types PDO and SDO.
The PDOs (process data objects) are used for the transmission of real time
data, and the SDOs (service data objects) permit access to the object directory
both for reading and writing.
4.3.1 Communication Objects
4.3.1.1 Process Data Object - PDO
PDOs contain real time data with high priority identifiers. The data telegrams
consist of a maximum of 8 bytes and can be interchanged among the individ-
ual sub-assemblies, as required. This data exchange can be optionally event
controlled or performed in a synchronized manner. The event controlled mode
allows the bus load to be drastically reduced permitting a high communication
capacity at a low Baud rate. However, the various modes can also be proc-
essed as a mix (see chapter 4.3.4.2.19 "Object 0x1400– 0x141F, Receive PDO
Communication Parameter")