CANopen Profile
CAN in Automation e.V. defines a large number of CANopen device or application profiles that specify the interface and behavior of certain devices.
Device profiles define all communication properties and the behavior of a certain device class (e.g. IO devices or batteries). This includes a number of mandatory or optional parameters with their data types, access rights and values ranges as well the default PDO mapping.
The application profile defines a complete application that consists of multiple CANopen devices. An example is an electric bicycle that contains of a drive controller, a main controller, a battery, a display or a temporary charger. Another application profile covers a complete lift system. Besides the devices also the communication connections (PDO Linking, PDO COB Assignment) between the devices are defined by these CANopen application profiles.
CANopen Profile Support
We offer extensions to support the functionalities of these profiles and to provide the data and events to the application in a preprocessed way. Currently extensions for the following profiles are available:
- CiA 401 – device profile for IO modules
- CiA 402 – device profile for drives
- CiA 404 – device profile for measurement devices and closed-loop controllers
- CiA 406 – device profile for encoder
- CiA 413 – interface profile for truck gateways
- CiA 418 – device profile for batteries
- CiA 419 – device profile for chargers
- CiA 437 – application profile for grid-based photo-voltaic components
- CiA 443 – Device profile for sub sea instruments (SIIS Level-2)
- CiA 447 – application profile for add-on devices for passenger cars (taxi, police, …)
- CiA 454 – application profile for Energy Management Systems e.g. in LEVs(EnergyBus)
Some of the mentioned profile require additional CANopen features such as MPDO or “SDO Requesting Device”, which are available as well.
Additionally, our CANopen Stacks can be used to develop any CANopen application even for other profiles as mentioned before.
Functionality
All CANopen profile extension modules include:
- CANopen DeviceDesigner object database for all objects defined in the profile
- generic (Linux) example application(s) for one or more devices that cover the communication of the devices
Depending on the complexity of the profile and on the implemented functionality of the extension it may include:
- source code for profile specific state machines
- source code to handle profile specific scaling of measured values
- source code to handle profile specific PDO transmission triggers
- source code to configure application profile specific PDO and SDO configurations
- a CANopen bootloader implementation (CiA 443 only)
