The CAN driver forms the basis for higher layer protocols (CANopen / J1939) and may be used for manufacturer-specific CAN communication between embedded systems. CANpie FD is available for a wide range of microcontrollers (more than 160 at the moment). A variety of configuration options facilitates adjustment to individual target systems.

The CAN physical layer (data link layer) comprises two protocols: the classical CAN standard and CAN FD. The protocols are described in the ISO 11898-1:2015 specification. The CANpie FD API defines 19 functions to allow manufacturer independent access to the CAN controller to entirely support ISO specifications. The API is based on the concept of dedicated message buffers (mailboxes) in combination with acceptance masks to minimize the application software’s overhead for filtering and managing messages. Each message buffer can be expanded by FIFO function.

Product Features

• supports (virtual) mailboxes
• supports acceptance masks
• optional FIFO for each mailbox
• supports time-stamps
• consistent structure of CAN messages
• optional user-fields may be included in the CAN structure
• supports all CAN FD formats (CBFF / CEFF / FBFF / FEFF)

The CANopen Slave protocol stack will come as C99 source together with a manual in English (electronic and print version). The scope of delivery also includes:

• a site-related company license without additional runtime costs
• 12 months technical support by email or phone

Manufacturer / Controller Options

The post CANpie FD Protocol Stack appeared first on DAQLOG Systems Ltd.

The CANopen bootloader protocol stack provides the complete functionality for integration of a bootloader according to the CANopen standard in your existing devices. Versatile configuration options facilitate individual customization to a target product. The Bootloader was implemented to meet low storage requirements.

The CANopen bootloader stack comprises a reduced object dictionary and supports NMT, SDO (Expedited / Segmented / Block), Emergency, Heartbeat as well as LSS services. Up to four separate sections for storage of programmes and data may be defined. The CANopen Download Tool is used to update programmes and data of the target hardware.

A defined API facilitates adjustment to a flash memory of the target hardware. Flash drivers for various controllers (e.g. STM32 series) are part of the CANpie driver.

Product Features

• Complete functionality according to CANopen specification CiA 301 and CiA 302
• Modular software structure with versatile configuration options
• Optimized to low resource requirements (Flash / RAM)
• Broad range of supported CAN controllers (CANpie)
• Defined API for access to flash memory

The CANopen bootloader protocol stack will come as ANSI-C source code with a user manual in English (electronic and printed version). The scope of delivery also includes:

• Ready-to-run examples for various demo boards
• Site-related company licence without any additional runtime costs
• 12 months technical support by email or telephone

The post CANopen – CANopen FD Bootloader Protocol Stack appeared first on DAQLOG Systems Ltd.

Versatile configuration options allow individual customization to the target system. Example codes facilitate the start-up phase, enabling the user to focus on the implementation of their own application. The open CAN driver (CANpie) provides the flexibility to use any CAN controller available on the market. 

The bridge function for the CANopen Slave protocol stack facilitates realization of devices with multi protocol capability. In addition, less development time is needed for the implementation of parameters as these are addressed by all protocols in the same way.

Product Features

• Functionality according to SAE specification J1939
• Modular software structure with versatile adjustment options
• Adaption to the target product without changing the code structure
• Optimized to low resource consumption (ROM / RAM)
• Wide range of supported CAN controllers
• Standardized interface for the CAN driver (CANpie FD)
• Cyclic transmission and reception of J1939 messages
• Transport protocols (TP.DT and TP.BAM) for transmission of large data volumes
• Setting of node address via address claiming
• Supervision of timeouts for J1939 messages
• Bridge function for the CANopen Slave protocol stack

The J1939 protocol stack will comes as ANSI-C source code with a user manual in English (electronic and printed version). The scope of delivery also contains:

• Ready-to-run examples for various demo boards
• Site-related company licence without royalty fees
• 12 months technical support by email or telephone

The post J1939 – J1939 FD Protocol Stack appeared first on DAQLOG Systems Ltd.

Implementation supports the following CANopen services:

• Service Data Objects (SDOs), Client and Server
• Process Data Objects (PDOs)
• Network Management (NMT)
• Emergency Messages (EMCY)
• Synchronisation Messages (SYNC)
• Layer Setting Services (LSS)

All services can be parameterized during runtime via the application or via the local object dictionary. You may extend the local object dictionary according to your specific purposes.

Versatile configuration options allow individual customization to the target system. In addition to the maximum number of supported PDOs, you may also adjust the number of SDO–client connections as well as multichannel support, thus adapting the use of resources (RAM/ROM) in an optimum way to the target application prerequisites.

Example codes facilitate the start-up phase, enabling the user to focus on the implementation of their own application. A consistent driver interface provides the flexibility to use any CAN controller available on the market.

The optional Safety added-on (SKU: 50.02.031) provides an implementation of the European standard EN 50325-5 featuring the following functions:

• max. 64 SRDOs (SR Data Object)
• global fail-safe command
• Expansion of the CANopen Master APIs

Product Features

• CANopen services according to CiA 301
• network management in compliance with CiA 302
• layer setting services according to CiA 305
• multichannel support (1 to 250 CAN channels)
• number of client SDOs individually adjustable (1 to 127)
• number of PDOs individually adjustable (0 to 512 RPDO / TPDO)
• local object dictionary (expandable)
• optional CANopen Safety Add-on available
• broad range of supported CAN controllers (CANpie)

The CANopen Master protocol stack will come as ANSI-C source code with a user manual in English (provided by download link). The scope of delivery also contains:

• site-related company licence, no additional runtime costs
• 12 months technical support by email or telephone
• ready-to-run examples for various demo boards

The post CANopen Master Protocol Stack appeared first on DAQLOG Systems Ltd.

The CANopen / CANopen FD Slave Protocol Stack is a professional embedded software solution for developers building CANopen-enabled devices. Delivered as portable C99 source code, the stack enables rapid integration of CANopen and CAN FD communication into industrial electronics, automation controllers, sensors, actuators and distributed I/O modules.

Supporting both CiA 301 and CiA 1301 standards, the protocol stack provides a scalable architecture with configurable PDOs, flexible object dictionary management and support for multiple CAN controllers through the CANpie FD interface.

CANopen / CANopen FD Slave Protocol Stack Key Features

• CANopen and CANopen FD support according to CiA 301 and CiA 1301
• Delivered as portable C99 source code
• Optimised for low RAM and ROM usage
• Modular architecture with flexible configuration
• Support for standard and extended CAN frames
• Runtime parameterisation via object dictionary
• Easy integration with embedded applications
• Broad CAN controller compatibility via CANpie FD
• Vendor-specific object dictionary extensions supported
• Optional CANopen Safety and Mini-Master add-ons available

Supported CANopen Services

The CANopen slave stack includes comprehensive protocol functionality for embedded CAN networks, including:

• Service Data Objects (SDO / USDO Server)
• Process Data Objects (PDO Consumer / Producer)
• Network Management (NMT Slave)
• Emergency Messages (EMCY)
• Synchronisation Messages (SYNC)
• Layer Setting Services (LSS)
• TIME Producer and Consumer support

Flexible PDO and Object Dictionary Configuration

The protocol stack allows developers to configure up to 32 transmit PDOs and 32 receive PDOs while maintaining compliance with predefined connection sets defined in CiA standards. The local object dictionary can also be extended with custom vendor-specific parameters for application-specific communication requirements.

CANopen FD Stack Applications

Typical applications include:

• Industrial automation systems
• Embedded control devices
• CAN FD data acquisition systems
• Sensors and actuators
• Motion control and drives
• Distributed I/O systems
• Automotive and off-highway electronics
• Energy management and battery systems

The stack is suitable for both new product development and upgrading existing CANopen devices to CAN FD capability.

Optional Add-Ons and Device Profiles

Additional options are available to expand functionality, including:

• CANopen Mini-Master functions
• CANopen Safety (EN 50325-5)
• CiA 401 I/O profile
• CiA 402 drives profile
• CiA 406 encoder profile
• CiA 418 battery profile
• CiA 419 charging device profile

Development Support and Licensing

The CANopen / CANopen FD Slave Protocol Stack includes:

• Site-related company licence
• No runtime royalties
• Technical support for 12 months
• Example applications for demo boards
• English documentation and user manual

Stack / Profile / Driver Options

The post CANopen – CANopen FD Slave Protocol Stack appeared first on DAQLOG Systems Ltd.