Systec CANopen Master & Slave Source Code CiA 301

The CANopen source code implements the complete functionality pursuant to the CiA 301 draft standard. The CANopen source code supports the fast and standard compliant design of own fully-featured CANopen master or slave devices, including NMT master (Network Management), LSS master (Layer Setting Services) or SDO client.

The straightforward, event-oriented signaling up to Application Level attains a high degree of performance. The CANopen source code is prepared for easy integration to operating systems. The well-defined and thoroughly thought-out API allows for an easy use of the CANopen services without diving into details of the implementation. Many example programs, target specific demo projects and the comprehensive documentation assist you step-by-step.

A CAN driver porting, implementing of specific demo projects or adaptation of the CANopen software to processors that are not directly supported can be carried out in a few days. Please contact SYS TEC for further information on the available adaptation services.

Modular, Scalable and Portable

The continuous modularization of the functionalities and implementation in ANSI-C make possible simple porting to different target systems. Great importance was set on scalability and performance. Highly optimized memory management and zero-copy implementation prevent unnecessary copying of data. With our CANopen Source you can just as cost-effectively create single-chip solutions and complex, multi-channel master applications. Our CANopen protocol stack was successfully ported, along with a number of microcontrollers, to a DSP.

The CANopen software is organized into individual modules. Some modules can be incorporated into or removed from the project, depending on the required functionality. The modules do not cross-call functions to another module but only functions from subordinate or superordinate modules (as Callback function). There are no cross-references of global variables between the modules. A central software layer, called "CANopen Controlling Module" (CCM), provides a simplified API of the CANopen functions to the application layer and controls the interaction of the individual modules. Furthermore, the hardware specific implementation is clearly decoupled from the CANopen protocol stack, resulting in a minimum effort required for porting to a new target platform.

No Royalties on Deployed Products

We offer an attractive pricing structure. You get the complete source with project examples on every purchase as Buy-Out license for an economic one-time fee. There are no royalties on your deployed products.
The license is location-bound and can be used for various targets, projects and products by your engineers without further license fees.
Through a license extension, development partners and other sites of their company can use the source code.
Our update and support services can be renewed annually - so your stack is always up to date.