Build standards-compliant CANopen devices faster.
Production-ready CANopen and CANopen FD protocol stacks in ANSI-C, supported by graphical configuration, code generation, diagnostics and engineering expertise.
From object dictionary to a working CANopen device
The emotas environment brings the protocol stack, configuration tools and diagnostic utilities together. Teams can create CANopen-compliant devices, generate consistent EDS/XDD files, integrate with their target platform and validate behavior on the network.
CANopen protocol stacks for every device role
A common, scalable code base lets you begin with the device role you need and extend functionality as the product evolves.
CANopen Slave Stack
For embedded devices that participate as CANopen nodes and expose application data through a standards-based object dictionary.
- CiA 301 communication services
- PDO, SDO, NMT, heartbeat and EMCY
- Compact and configurable footprint
Master / Slave Stack
Add master functionality while retaining full device capability—ideal for controllers coordinating multiple CANopen nodes.
- Master and slave services
- Network start-up and supervision
- CiA 302-2 master properties
CANopen Manager Stack
An extension for applications that need centralized boot-up and configuration management across the complete network.
- Boot-Up Manager
- Configuration Manager
- Advanced network coordination
CANopen FD Stack
For applications using the higher payload and bandwidth potential of CAN FD while preserving the CANopen engineering model.
- CiA 1301 communication profile
- CANopen FD services and tools
- Modern high-performance networks
A clean boundary between hardware, stack and application
The defined driver interface helps teams adapt the stack to existing or new CAN controllers and CPUs. Hardware platforms can be changed with limited impact on the application.
Proven across leading semiconductor platforms
A clearly defined driver interface helps engineering teams integrate CANopen with established and next-generation controller platforms.
The supported hardware ecosystem also includes Bosch, Intel and legacy Atmel platforms. Additional CAN-controller and CPU driver packages can be provided for project-specific targets.
CANopen Tool Chain and Stack
Design the device and network, generate source artifacts, integrate the stack, then inspect and validate real CANopen traffic using one connected toolchain.
CANopen DeviceDesigner
Build an object dictionary from predefined profiles, configure the stack and CAN driver, and generate object dictionary source, initialization functions, EDS/XDD files and device documentation.
Technical details at emotas ↗CANopen DeviceExplorer
Use CANopen master functions for development, test, diagnosis and service. Read or write object entries, work with EDS files, save DCF configurations and manage network projects.
Technical details at emotas ↗NetworkDesigner and services
Model complete networks and communication relationships, generate component source code, and engage emotas engineering for integration, commissioning, consulting and training.
Technical details at emotas ↗Support for established CANopen device profiles
Across mobile machines, devices and infrastructure
CANopen is used wherever dependable, interoperable embedded communication matters.
Protocol expertise translated into practical development tools
Let’s map the right CANopen stack to your device.
Share your target hardware, operating environment and device role. Lexington Soft can arrange a technical discussion, demonstration, evaluation or commercial proposal.