
4th edition, 9-11-2018
7000.05050, 4th edition, 9-11-2018
7000.05050
CANopen protocol description
15
3.2
Communication services
Fig. 4:
Communication services of the Motion Controller
The communication part contains communication services as specified in CiA 301.
Tab. 2:
Communication services to CiA 301
Communications profile
FAULHABER Motion Controllers support the CANopen communications profile to
CiA 301 V4:
4 transmission PDOs
4 receipt PDOs
1 server SDO
Emergency object
NMT with node guarding and heartbeat
SYNC object
Communication services
Description
NMT (Network Management)
Activates nodes and monitors the current status of a node (see chap. 3.8, p. 27).
SDO (Service Data Object)
The CANopen master uses the SDO to access parameters within a node. Each
SDO access reads or writes exactly one parameter. An SDO can only address one
node in a network (see chap. 3.5, p. 21).
PDO (Process Data Object)
The PDO is used to access real-time data. A PDO can use a CAN message to
access multiple drive parameters concurrently. The parameters sent or received
in a PDO can be freely configured (see chap. 3.4, p. 17).
SYNC object
SYNC objects are used to synchronise different applications on the CAN-BUS
(see chap. 3.7, p. 26).
EMCY (Emergency Object)
An emergency message is used to inform the CANopen master about errors. A
CAN message conveys the error code asynchronously so that the status of the
CANopen slave need not be interrogated after an error (see chap. 3.6, p. 24).
Communication
Application
Motor
CAN
n , Pos
∗
∗
Motor Control
Control Word
Status Word
n, Pos
EMCY
PDO1 … PDO4
SDO
CiA 301 CANopen
Statemachine
NMT
Guarding
CAN Bus
Error Handling
Object Dictionary
CiA 402 Drive
Statemachine