CANopen is a higher layer protocol operating on a CAN Bus network. The CAN Bus specification defines solely the physical and data link layers in the ISO/OSI 7-layer Reference Model. Consequently, only the physical bus and the CAN Bus message format is defined, but not how the CAN Bus message applies. CANopen provides an open and standardized but customizable description of how to transfer data of various types between different CAN Bus nodes. The end user can purchase off-the-shelf CANopen compliant nodes and plug them into a network with minimum effort. It also can be used in place of an in-house proprietary higher layer protocol development.

The CAN in Automation (CiA) User's Group supervises the CANopen protocol, and it is an international standard. Use of CANopen does not require any royalties, and the specification expands or changes to suit closed networks when necessary.

Typical applications for CANopen include:

• Commercial Vehicles
• Medical Equipment
• Maritime Electronics 
• Building Automation 
• Light Rail Systems 

CANopen Architect

Electronic Datasheets (EDS) are files which define the abilities of CANopen nodes and are consequently central to CANopen. EDS files are commonly used when CANopen modules are sold or made available to third parties. They provide a standardized and easy-to-use format for describing how CANopen nodes are integrated into networks. They can also serve as in-house documentation of the node.

The CANopen Architect software by the Embedded Systems Academy provides quick and easy generation and editing of EDS files. Files can be built from scratch or based on one of the versions in the included library. The user interface displays the contents of the EDS file in a tree view, allowing swift and straightforward editing of any aspect.

CANopen Architect also supports the creation and editing of Device Configuration Files (DCF). DCFs are the same as EDS files but include authentic settings of a specific node. Unlike many other EDS editors, CANopen Architect supports the editing of data specific to DCFs.

CANopen Architect implements an integrated EDS checker and supports the use of third-party EDS checkers. EDS checkers verify the EDS files and produce error and warning information.

More Information...

CANgineBerry - CANopen Module for Raspberry Pi

The CANgineBerry for CANopen is an active CAN Bus co-processor module that uses a regular UART communication channel towards the host system. With its independent 32-bit microcontroller, the CANgineBerry can easily execute CAN Bus protocols with tough timing demands such as CANcrypt or CANopen with response times of under 10 ms.

Depending on the configuration, the CAN Bus communication can be up and running within 50 ms after power-on, even if the host system takes significantly longer to boot.

Available firmware options at launch include a generic minimal CANopen Manager/Controller and a CANopenIA Device both based on the CANopenIA implementation.

More Information...