CANopen Manager Stack

Generally, the CANopen manager stack should be used if the CANopen network is very dynamic with a varying number and types of CANopen slaves.

The CANopen (FD) Manager Stack extends CANopen (FD) Master capabilities with additional manager functions according to the CiA specification 302 “Additional Application Layer Functions”. All CANopen master services as defined in CiA 301 are included.

The additional functions to handle dynamic CANopen (FD) networks are:

BootUp Manager (CiA 302-2)

The bootup manager implements the boot up behavior of a CANopen (FD) network as defined in CiA 302. The manager can be configured to check for mandatory and optional devices according there device types (0x1000) and identity data (0x1018) and inform the application about all devices.

Configuration Manager (CiA 302-3)

The configuration manager is able to check if the devices are configured as expected and if not, it is able to start a configuration process automatically. Configurations may be read from DCF files or Concise-DCF files.

In summary, the CANopen Manager Stack is preferable to the CANopen Master Stack if the CANopen network is dynamic in terms of the number and type of slave devices and the master/manager is required to reflect this flexibility.

Additionally, there are optional extension modules for Redundant Networks (CiA 302-6) and Multi-Level-Networking (302-7) available.