Effectiv configuration, operation and controlling of the most complex CAN networks.
The CANopen Manager allows configuration, control and regulation of a complex CANopen network. Prepared and standardised solutions help to safe useful time and to use it efficiently during the project planning and realisation.
A maximum of usability is guaranteed due to the implementation for CiA draft standard 301 for communication with OSI layer 7. This CANopen communication profile is being complemented by CiA DSP 4.05 for IEC1131-3 programmable devices.
The CANopen Communication Profile provides an open standard for industrial applications and defines the configuration phase, the transmission of process data in real-time and the synchronous data exchange between net members. As the CANopen Manager is used for initialisation, observance, controlling and synchronisation of CAN networks, it concludes all necessary functions for the communication with OSI layer 7 after the CiA DS 301 (CANopen Communication Profile) standard. It is completed by CiA DSP 405 (Device Profile for IEC 11313 programmable Devices) for a dynamic allocation of application variables.
The data of bus members are deposited in defined application objects. That information can be required selectively by other net nodes and also provided to other CAN devices. Needed application objects, PDOs and SDOs are completed with the CANopen configuration program. Different values of the parameters are adjusted for the configuration und more net nodes can be processed simultaneously.
The object index operates similar to a mail box. The data of bus members are deposited in defined application objects (variables) for the application. That information can also be required from other net nodes. The other way round, application objects of the object index can be provided to other CAN devises automatically (i. e. cyclic in certain time intervals) and also on request.
An „Electronic Data Sheet“ (EDS) serves as initial point for further processing to the CANopen Configuration Program. For every special configuration the general properties of the CANopen nodes are arranged like on a framework.
Needed application objects, PDOs and SDOs can be completed with the CANopen Configuration Program in the object index. The different parameter values are adjusted for the configuration. More net nodes can be processed simultaneously, so that the identifiers of the PDOs or SDOs can simply be adapted to each other. When all adjustments are done, the CANopen Configuration Program creates a device configuration file (DCF) out of it.
A homonymous binary and header file can be created by calling the additional tool DCF-comp, which is included in delivery. The header file can be integrated into the system application. So the access to entries in the object index happens via their names. The binary file with the configuration data is read by the CANopen driver and replaces the standard configuration. Initialising the CANopen driver, the new configuration is taken as basic for dynamic creation of objects and lists.
The CANopen Manager adopts the initialisation of the CANopen network and the CANopen nodes (engine and temperature regulation, IO modules, etc.) in the starting phase. During the operation the CANopen Manager is responsible for node observance (guarding), synchronisation of CANopen nodes and error handling.
The exchange of process data (Is-value of temperature regulator, conditions of light barrier, position and speed data of the motor regulator, setting of outputs) happens also via a comfortable interface between CANopen Manager and application.