CANopen Firmware
11. CANopen Firmware
Apart from basic descriptions of CANopen, this chapter contains the most significant information
about the implemented functions.
A complete CANopen description is too extensive for the purpose of this manual. Further
information can therefore be taken from the CANopen specification CiA 301 [2].
11.1 Definition of Terms
COB ...
Communication Object
Emergency-Id... Emergency Data Object
n.a.
not applicable
NMT...
Network Management (Master)
Rx...
receive
SDO...
Service Data Object
SYNC...
SYNC (frame) Telegram
tbd.
to be defined
Tx...
transmit
PDOs
(Process Data Objects)
PDOs are used to transmit up to 8 bytes process data.
In the ‘Receive’-PDO (RPDO) the process data are received.
In the ‘Transmit’-PDO (TPDO) the process data are transmitted.
SDOs
(Service Data Objects)
SDOs are used to transmit module internal configuration- and parameter data. The object directory
is accessed via SDOs.
In opposition to the PDOs SDO-messages are confirmed. A write or read request on a data object
is always answered by a response telegram with an error index.
NMT State Machine
For the control of the device functionality all CANopen devices come with an internal state
machine. In the individual states only defined operations are allowed. The state transitions can be
triggered by internal events (e.g. boot-up, error, reset) or by the NMT master.
Page 88 of 105
Manual • Doc. No.: C.2921.21 / Rev. 1.6
CANopen-PN