Glossary · Industrial communication
CANopen
Also known as: CiA 301
German: CANopen
In industrial communication, CANopen is a higher-layer protocol and device profile family for the CAN bus, maintained by CAN in Automation (CiA). Each device has an object dictionary; process data are exchanged in PDOs and configuration data in SDOs.
- Industrial communication
- Standards
In one sentence
CANopen is a CAN-based higher-layer protocol with object dictionary, PDOs and SDOs and standardized device profiles (CiA 301, EN 50325-4).
Example
A servo drive with a CANopen interface follows the CiA 402 drive profile, so the controller can command position mode with standard objects.
How it applies
- Engineering: The object dictionary describes all parameters and data of a device; an electronic data sheet (EDS file) makes it available to configuration tools. Device profiles such as CiA 402 for drives let devices from different manufacturers behave alike.
- Commissioning: Node IDs and bit rates are set on each device. The network management (NMT) master switches the nodes to the operational state, and PDO mapping defines which objects are sent cyclically.
- Operation: Heartbeat or node guarding detects failed nodes; emergency messages (EMCY) report device errors.
- Documentation: The documentation team publishes the object dictionary with index, subindex, data type, access rights and units, and states which profile the device implements. This is the reference integrators actually need.
CANopen vs. EtherCAT
EtherCAT can carry the CANopen application layer (CoE, CANopen over EtherCAT), so object dictionaries and drive profiles are reused on Ethernet hardware. The transport and the timing behavior are different, though.
The Information model idea is similar: CANopen's object dictionary is a structured description of what a device offers, which makes it a useful source for semantic documentation.