CANopen SIG programmable devices


Enhancement and maintenance of CANopen profiles as well as additional application layer functions, relevant for programmable devices such as e.g. host controllers.



Group meetings

No events found.


Title Date Status Size Published Action
SIG programmable devices2014-12-08Minutes1.3 MiB2017-07-18Login
SIG programmable devices2017-10-24Minutes124 KiB2017-10-30Login
SIG programmable devices2017-11-10Minutes14.5 MiB2017-11-28Login
SIG programmable devices2017-12-07Minutes181 KiB2017-12-11Login
SIG programmable devices2018-02-16Minutes468 KiB2018-02-20Login
SIG programmable devices2018-03-09Minutes334 KiB2018-03-09Login
SIG programmable devices2018-03-28Minutes731 KiB2018-03-29Login
SIG programmable devices2018-07-03Minutes129 KiB2018-07-04Login


Title Details
CiA 302-1 version 4.1.0CANopen additional application layer functions - Part 1: General definitions
DescriptionThis document defines additional services and functionalities that extend the services and functionalities of the CiA 301: CANopen — application layer and communication profile. These additional services and functionalities are not required for CANopen devices, but may be useful for certain types of networks. This includes network management, configuration and program download, network variables and process image, dynamic SDO management, network redundancy, and multi-level networking.
DSP85 KiB2009-02-02Login
CiA 302-2 version 4.1.0CANopen additional application layer functions – Part 2: Network management
DescriptionThe definition of the network management includes the definition of the network startup behavior as well as definitions that are related to networks that operate without NMT master, networks with one CANopen device capable of the NMT master mode, and networks with more than one CANopen device capable of the NMT master mode (NMT flying master for higher availability). These definitions are intended to be an add-on to the CANopen application layer and communication profile (see /CiA301/).
DSP1.5 MiB2009-02-02Login
CiA 302-3 version 4.1.0CANopen additional application layer functions – Part 3: Configuration and program download
DescriptionThis document defines objects and file formats for the configuration manager and for program download and control.
DSP331 KiB2010-04-08Login
CiA 302-4 version 4.1.0CANopen additional application layer functions – Part 4: Network variables and process image
DescriptionIn a network programmable CANopen devices can be characterized as a process having input variables and output variables. The set of variables will be arguments of the program and hence will be only known in a final state when the program is written. The arguments are handled as variables located in the object dictionary. The marking of such parameters depends on the programming system (e.g. /IEC61131–3/) and does not fall into the scope of this document. But it can be assumed that there is a set of network variables with the logic attribute EXTERN. Compiling/Linking (or interpreting) a program including EXTERN variables requires relocation information. Within CANopen devices this information is the index (and sub-index) of the variable. Most of the programming systems know the mechanism of a resource definition. This can be used to assign the CANopen attributes (index, sub-index, R/W, assignment of CANopen data type to local data type etc.) to the corresponding symbolic names (variable name in the program). The resource definition may be created with a simple editor by the user or with much more comfort by a configuration tool. Systems with a disk-based file system may exchange the information directly, e.g. via a device configuration file. The names of variables may meet the rules of the underlying programming system. The definition does not fall into the scope of this document. This is the responsibility of the programmer/manufacturer. Defining EXTERN variables requires a rule for distributing the indices. It is called "dynamic index assignment".
DSP162 KiB2009-02-02Login
CiA 302-5 version 4.1.0CANopen additional application layer functions – Part 5: SDO manager
DescriptionCANopen offers a communication mechanism between CANopen devices via SDO. These communication channels are always established between two CANopen devices. For accessing a CANopen device the first time at least one SDO channel per CANopen device is required. This is called the default SDO channel. Only the SDO manager is allowed to use that SDO channel. Simple networks may use SDO channels that are pre-configured between a pair of CANopen devices. This allows direct communication between CANopen devices without the need of a SDO manager. This document defines mechanisms that may be used for plug-n-play networks, without the requirement of a pre-configuration of the network. These mechanisms may be used to establish dynamic SDO connections between CANopen devices. These mechanisms require a specific CANopen device in the network that is able to handle the dynamic request; this CANopen device is called SDO manager. These mechanisms require CANopen devices that are able to perform a dynamic request; these CANopen devices are called SDO Requesting Device (SRD).
DSP397 KiB2009-02-02Login
CiA 314 version 1.0.0Accessing CANopen services in devices programmable in IEC 61131-3 languages
DescriptionThis document specifies function blocks to produce or consume CANopen communication services for devices programmable in IEC 61131-3 languages and to provide local CANopen functions. This specification is suitable for programmable logic controllers (PLCs), PC-based controllers running a PLC-software, and other programmable devices compliant to IEC 61131. NOTE: This specification substitutes the CiA 405 document those content has been moved to different documents (CiA 302-4 and CiA 306-3).
DSP363 KiB2015-10-09Login
CiA 302-8 version 0.0.4CANopen additional application layer functions – Part 8: Project management parameters
WD371 KiB2016-08-11Login