µC/CAN Overview: Introduction
Architecture
The µC/CAN goal is to reduce the developer's development effort wanting to embed CAN. The developer just needs to understand signals, messages and bus configurations.
The different abstraction layers can be used independently.
µC/ CAN can be used with or without RTOS.
Application Signal
This layer gives access to logical signals, which are located in one or more CAN messages. Changes of signals can be checked and predefined actions can be executed.
Message
The message layer organizes all information necessary for sending and receiving CAN messages. Identifier, data length code (DLC) and data (and the linked signals) are bundled and dedicated to one or more buses.
Bus Management
µC/ CAN can communicate via one ore more CAN buses at the same time. The bus management layer organizes the CAN buses and distributes the messages to the different device drivers.
Device Driver Layer
The device driver layer buffers CAN messages to be sent and received. All hardware dependencies are capsulated in this layer. Your embedded target can also have multiple, different CAN controllers.
Protocols
µC/CAN enables the easy and quick implementation of custom CAN protocols such as CANopen.
This module enables the easy and quick implementation of custom CAN protocols. The following standard protocols Add-Ons are available:
- µC/ CANopen (Small Sensor Slave)
We planed three different CANopen implementations in the next 2 years:
- (1) the sensor slave stack for small sensor devices : µC/CANopen Sensor
- (2) the full slave stack for bigger input/output devices like DS401 devices : µC/CANopen Slave
- (3) a master stack for the CANopen network master : µC/CANopen Master
Driver
Four (4) different CAN controllers Device Drivers are currently available. Please contact us for more details.
» further information on german