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.
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:
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.
All CANopen profile extension modules include:
Depending on the complexity of the profile and on the implemented functionality of the extension it may include:
Die Cookie-Einstellungen auf dieser Website sind auf "Cookies zulassen" eingestellt, um das beste Surferlebnis zu ermöglichen. Wenn du diese Website ohne Änderung der Cookie-Einstellungen verwendest oder auf "Akzeptieren" klickst, erklärst du sich damit einverstanden.