The famous Wireless M-Bus protocol stack by STACKFORCE leads to competitive products that are easy to install and maintain. The stack implements all protocol elements that are required for Wireless M-Bus compliance and provides additional tool support. It is optimized towards a compromise of small footprint, excellent modularity and scalability, but though being feature-rich.
STACKFORCE has partnered with multiple industry leading silicon vendors, thus the stack has already been ported to various platforms.
Compliant according EN 13757-4 "Wireless M-Bus Communication"
- All layers supported:
- Physical Layer
- Data Link Layer
- Extended Data Link Layer
- All modes supported:
- Mode S, including long preamble for synchronous data
- Mode T, permitting short Rx windows for meters (2..3ms)
- Mode C, including support for combined T and C mode as collector
- Mode N
- Both frame formats A and B supported
Compliant according EN 13757-3 "Application protocols"
- All layers supported:
- Application Layer
- Transport Layer
Compliant to other Wireless M-Bus based Standards
- Version 3
- Version 4.0.2, prepared for encryption mode 13 (TLS)
- Version 4.1.2 (under development), prepare for encryption mode 13 (TLS)
- Version 2.2
- Version 4.0.5
- ESMR Version 5
- CIG UNI/TS 11291-11
A few feature highlights
- API for Application Layer
- API for other layers (like e.g. DLL) possible
- API for externalization of security functions
- Well formed hardware abstraction layer (HAL)
- Available as source code for certification purpose
- Well proven serial interface with minimal
- All API functions available via serial interface
- Serial interface supports UART, SPI, I²C, …
Support of hardware acceleration
If provided by the platform, the stack supports use of hardware acceleration, like
- AES de-/encryption
- De-/Encoding of Manchester, 3-of-6, ...
Wireless M-bus mode and device type selection
Selection of mode (S, T, C, N), direction (unidirectional/bidirectional) and device type (meter/collector) is possible ...
- during compile time to shrink the memory footprint.
- during runtime to permit flexible role change at anytime in the field.
Flexible Software Timer
Dynamic hardware timer adaptation including compensation in order to occupy only one hardware timer (and an RTC if applicable) for all Wireless M-Bus related timings.
Support of any type of non-volatile memory
- EEPROM, Flash, MRAM, …
- internal/external (e.g. connected via SPI)
- One-off license for single-stop shopping
- Royalty based to have spending spread
- Totally individual
- As source code, e.g. for certification purpose
- As object code, no (accidental) breaking of the stack and much cheaper
Extensive support for R&D, training and customization can be obtained in any case.