IXXAT Emtas CANopen Manager Stack

IXXAT Emtas CANopen Manager Stack
The CANopen Manager Stack by emtas extends the well-proven CANopen Master Stack by additional manager functions according to the CiA specification 302 “Additional Application Layer Functions”.
Additional functions :
BootUp Manager (CiA 302-2)

The bootup manager implements the boot up behavior of a CANopen network as defined in CiA 302. The manager can be configured to check for mandatory and optional devices according there device types (0x1000) and identity data (0x1018) and inform the application about all devices. Configuration Manager (CiA 302-3)

The configuration manager is able to check if the devices are configures as expected and if not, it can start a configuration process automatically. Configurations may be read from DCF files or Concise-DCF files. Of course all CANopen master services as defined in CiA 301 are included. Generally, the CANopen manager stack should be used if the CANopen network is very dynamic with a varying number and types of CANopen slaves. There are optional extension modules for Flying Master, SDO Requesting Device (CiA 302-5), Redundant Networks (CiA 302-6) and Multi-Level-Networking (302-7) available.

System requirements

ANSI-C compiler

Scope of delivery/licensing

• CANopen protocol source code (ANSI-C compatible)
• Ready to run example applications
• User manual and reference manual in electronic format available
• Site license
• 6 months free-of-charge support and updates
• Optional maintenance agreement
• 1 named user license of CANopen DeviceDesigner include



• ANSI-C CANopen source code stack
• MISRA-C conform
• Supports CANopen services of CiA 301 and CiA 302-2
• Extension modules for further standards available
• Available for many CAN-controller and CPU types
• Comfortable user interface
• Widely scalable and configurable

CANopen Features

ServicesBasic SlaveMaster/SlaveManager
SDO Server 2 128 128
SDO Client 128 128
SDO expedited/ segmented/block ●/●/- ●/●/○ ●/●/○
PDO Producer 32 512 512
PDO Consumer 32 512 512
PDO Mapping static static/dynamic static/dynamic
MPDO Dest Mode
MPDO Src. Mode
SYNC Producer
SYNC Consumer
Time Producer
Time Consumer
Emergency Producer
Emergency Consumer 127 127
Guarding Master
Guarding Slave
Bootup Handling
Heartbeat Producer
Heartbeat Consumer 127 127
NMT Master function
NMT Slave
LED CiA-303
LSS CiA-305
SDO Requester (SRD) CiA-302-5
CANopen Router CiA-302-7
Master Bootup CiA 302
Configuration Manager
Flying Master
C#-API-Wrapper for Windows
Delphi-API-Wrapper for Windows
CANopen Profiles
CiA 401 (U8/INT16)
CiA 402
CiA 404
CiA 406
CiA 413
CiA 418
CiA 419
CiA 437
CiA 443
CiA 447
CiA 454

● – included
○ – optionally available

Caratteristiche e Benefici

Supported Controllers

The following chip manufacturers and their families are supported at the moment by the emtas CANopen and J1939 stacks:

AMD x86 Architecture
ATMEL ATmega64C, AT90CAN64, AT90CAN128, SAM C21
Freescale (NXP) Kinetis, msCAN12 (e.g. HCS08, HCS12), i.MX, MPC560x
Cypress (Spansion/Fujitsu) FM3 (ARM Cortex-M3)
Infineon XMC4000 (ARM Cortex-M4, MultiCAN), XMC1400 (Cortex-M0), XE166
Intel x86 Architecture
Microchip dsPIC33, PIC24H, PIC32
NXP LPC17xx, LPC40xx, LPC546xx
NuvoTon NUC130, NUC140
Renesas R-IN32M3, RX62, V850E2, RH850/F1L, Synergy S1,S3,S5,S7
ST Microelectronics STM32 (ARM Cortex-M0, Cortex-M3, Cortex-M4, Cortex-M7, bxCAN, M_CAN)
Texas Instruments TMS320, C2000 (DSP), ARM, Stellaris LM4F, TMS570 (Hercules), Tiva TM4C129
LINUX systems can4linux, SocketCAN, ECI


The table only lists the families. All providers offer within each family a large number of “family members”
that differ in periphery, maximum clock rate or size of housing. In consequence the number of pins and pin
assignment also differ.


The CANopen stack can be used with the following compilers or IDEs:

• gcc
• Keil
• Crossworks
• Atmel Studio
• Atollic True Studio
• Tasking
• Mikro C

and more.