Technical Summary



Message IDs
Layer-2 Driver
Layer-7 API


MicroMessaging Specification

Layer 2:
Driver Interface

What is special about the MicroMessaging layer 2 driver interface is that all functions and their parameters are carefully selected to be efficiently usable AND interchangeable with most serial busses, especially with UARTs/RS-232/RS-485, I2C, SPI, LIN and CAN.

Both polling and interrupt driven communication modes are supported.

Layer 7:
API - Application Interface

 Some networking standards, including CANopen do not provide an API hindering portability between different implementations. This also results in additional software overhead if different implementations are merged into or exchanged with other network systems.

 The MicroMessaging layer 7 API provides a simple standardized interface focusing on the process data exchanged.

The MicroMessaging Protocol

 The MicroMessaging protocol stack is based on a minimal CANopen implementation optimized for the usage in embedded systems, making the protocol stack usable on the smallest 8-bit microcontrollers. MicroMessaging devices are intentionally not CANopen compliant, however all major CANopen development tools such as monitors, analyzers, masters, managers and configuration tools are usable if CAN is used as the layer-2 transport media.

If the physical implementation is not CAN based, simple gateways (for example based on existing microcontroller evaluation/starter kits) can provide a CAN interface to the network which is usable by all CANopen development tools.

Embedded Internetworking

Although not part of the MicroMessaging specification and implementation, remote access to a MicroMessaging network via the Internet is easily possible. In its layout, MicroMessaging already supports the Internet Draft "Remote Access to Embedded Devices" published with the RFC-Editor and on