CANopenNode
CANopen protocol stack
|
Stack configuration and enabling macros. More...
Topics | |
Common definitions | |
Constants for common definitions. | |
NMT master/slave and HB producer/consumer | |
Specified in standard CiA 301 | |
CANopen Node Guarding slave and master objects. | |
Specified in standard CiA 301 | |
Emergency producer/consumer | |
Specified in standard CiA 301 | |
SDO server/client | |
Specified in standard CiA 301 | |
Time producer/consumer | |
Specified in standard CiA 301 | |
SYNC and PDO producer/consumer | |
Specified in standard CiA 301 | |
Data storage | |
Data storage with CANopen OD objects 1010 and 1011, CiA 301 | |
CANopen LED diodes | |
Specified in standard CiA 303-3 | |
Safety Related Data Objects (SRDO) | |
Specified in standard EN 50325-5 (CiA 304) | |
LSS master/slave | |
Specified in standard CiA 305 | |
CANopen gateway | |
Specified in standard CiA 309 | |
CRC 16 calculation | |
Helper object for CRC-16 checksum | |
FIFO buffer | |
Helper object for FIFO buffer | |
Trace recorder | |
Non standard object | |
Debug messages | |
Messages from different parts of the stack. | |
Files | |
file | CO_config.h |
Configuration macros for CANopenNode. | |
Stack configuration and enabling macros.
Default values for stack configuration macros are set in corresponding header files. The same default values are also provided in this file, but only for documentation generator. Default values can be overridden by CO_driver_target.h file. If specified so, they can further be overridden by CO_driver_custom.h file.
Stack configuration macro is specified as bits, where each bit enables/disables some part of the configurable CANopenNode object. Flags are used for enabling or checking specific bit. Multiple flags can be ORed together.
Some functionalities of CANopenNode objects, enabled by configuration macros, requires some objects from Object Dictionary to exist. Object Dictionary configuration must match Stack configuration.