emtas CANopen Master/Slave stack
Software package for the development of CiA301 & CiA302-2 CANopen master or slave devices
The CANopen Master Stack is written in ANSI-C and it is MISRA conform. Using the CANopen Master/Slave Stack by emtas leads to fast and easy development or extension of CANopen conform master applications
- ANSI-C compatible CANopen Master/Slave source code stack
- Supports all CANopen services of CiA301 V4.2 & CiA302-2
- Layer Setting Service (LSS) included
- Extensions for further standards available
- Available for many CAN-controllers and CPU types
- Comfortable user interface
- Widely configurable and scalable
The stack includes all features and services of the emtas CANopen Slave Stack. In addition it is featured with NMT Master functionalities and network management. Several master examples are available to make the first steps in using the complex master functionalities as easy as possible.
A flexible user interface provides functions to evaluate the received data and to use the CANopen Master/Slave services in the network.
A flexible user interface provides functions to evaluate the received data and to use the CANopen FD services in the network. To connect the CANopen Master/Slave Stack to multiple CAN controllers and CPU types, a well-defined driver interface is used. Using this driver interface the CANopen FD stack can also easily be adapted to new CAN controllers or CPU types. Also it is possible to substitute hardware platforms with only little effort.
The CANopen Slave Stack can be used with various Realtime Operating Systems such as ThreadX, FreeRTOS, Keil RTX oder TI-RTOS ,and as well with Linux (SocketCAN, can4linux) or QNX and also with Real time extensions for Windows.
Besides the function API there is also an Mailbox API available for an easy use with multiple tasks resp. threads. Messages between application modules and CANopen Master/Slave stack are send via mailboxes instead of function calls. This secures a non-blocking communication. An application may consist of several tasks that use the CANopen Stack in parallel.
Overview of the CANopen functions of the Master/Slave stack in comparison with the other emas stacks
|SDO expedited/ segmented/block||●/●/-||●/●/○||●/●/○|
|MPDO Dest Mode||○||○|
|MPDO Src. Mode||○||○|
|NMT Master function||●||●|
|SDO Requester (SRD) CiA-302-5||○||○|
|CANopen Router CiA-302-7||○||○|
|Master Bootup CiA 302||●|
|C#-API-Wrapper for Windows||○||○||○|
|Delphi-API-Wrapper for Windows||○||○||○|
|● - Inclusief
○ - Optioneel
To save resources the CANopen Master/Slave Stack is widely configurable and scalable. The settings for these features are supported by the graphical configuration tool, CANopen DeviceDesigner, which also allows the creation of the object directory and EDS file using a built-in database. As a consequence, changes can be realized fast and easy.
Using the unique CANopen DeviceDesigner valuable development time is saved.
Easy start up
Many ready-to-run examples are provided to make the start with the CANopen Master/Slave stack as easy as possible. Additionally a user manual, which describes principles and use cases and a reference manual, which describes each API function in detail belongs to the scope of delivery. The stack is constantly tested with the CANopen Conformance Test for compliance with the specification.
Supported processors and IDEs
The following chip manufacturers and their families are supported by the emtas CANopen Master/Slave Stack: ATMEL, BOSCH, Freescale (NXP), Cypress (Spansion/Fujitsu), Infineon, Microchip, NXP, NuvoTon, Renesas, ST Microelectronics, Texas Instruments. Furthermore, the x86- and LINUX-architecture are generically supported.
CANopen Master/Slave Stack code can be generated by compilers or IDE’s by GCC / GNU, Keil, IAR, Crossworks, Atollic True Studio, Tasking and the specific development environments of the various chip manufacturers.
Ask for the specific possibilities of a specific controller / IDE combination.
The CANopen Master/Slave Stack is delivered as source code in the form of a one-time Project or Site License. The distinction between them is as follows:
- Project license
The software (source code) may be used at one defined development location for one defined project. The default support period is 6 months.
- Site license
The software (source code) may be used on one development site / location, by various developers at this location, for an unlimited number of products. The standard support period is 24 months.
There are no run-time fees or royalties on the generated object code.
|Contents of delivery|
|- Source code in C|
|- Example code in C|
|- Software user license|
|- Programming manual|
|- CANopen DeviceDesigner (named-user license)|
|- Technical support (time limited)|