BUDE_Manual-CANopen_EN.doc
8/55
Baumer Hübner GmbH
23.10.2012/bja
Berlin, Germany
3.2
CANopen
Under the technical management of the Steinbeis Transfer Centre for Automation, the CANopen profile was
developed on the basis of the Layer 7 specification CAL (CAN Application Layer). In comparison with CAL,
CANopen only contains the functions suitable for this application. CANopen thus represents only a partial
function of CAL optimized for the application in hand, so permitting a simplified system structure and the use
of simplified devices. CANopen is optimized for fast data exchange in real time systems.
The organization CAN in Automation (CiA) is responsible for the applicable standards of the relevant profiles.
CANopen permits:
• Simplified access to all device and communication parameters
• Synchronization of several devices
• Automatic configuration of the network
• Cyclical and event-controlled process data communication
CANopen comprises four communication objects (COB) with different characteristics:
• Process data objects for real time data (PDO)
• Service data objects for parameter and program transmission (SDO)
• Network management (NMT, Heartbeat)
• Pre-defined objects (for synchronization, emergency message)
All device and communication parameters are subdivided into an object directory. An object directory
encompasses the name of the object, data type, number of subindexes, structure of the parameters and the
address. According to CiA, this object directory is subdivided into three different parts. Communication
profile, device profile and a manufacturer-specific profile (see object directory).
