OMS® v4.5.1 / wM-Bus for Gateways

Single Stack

Gateway

Compliant to EN 13757-3/-4/-7 (Wireless) M-Bus and OMS® Specification

Twenty end devices can be connected to one gateway device.

Bidirectional as well as unidirectional communication possible.

Pre-certification on reference hardware platform.

Test your preferred protocol stack for free with an evaluation license

  • Register a business account
    Click “Sign in” in the license selection to start the registration process.

  • Select product
    Once your account is approved, choose your desired product and click “Start your free trial”.

  • Sign the agreement
    Digitally sign the evaluation agreement for your selected product.

  • Download & start testing
    After signing, you can download the software package and start your evaluation.

Product description

Benefits

Features

Hardware

Technical Information

FAQ

Commercial Features

  • First Level Support
    Professional first‑level support from experts in embedded connectivity – quick, efficient, and ready to help.

  • Quality Product
    Our protocol stacks undergo extensive testing, ensuring proven reliability across various IoT applications worldwide.

  • Easy commissioning
    Thanks to our modular, standardized software solutions, configuring embedded systems is simple and hassle‑free.

  • Warranty & Maintenance
    We deliver all our products with clear manufacturer warranties and comprehensive guarantees for maximum reliability.

OMS® v4.5.1 / wM-Bus for Gateways

The OMS® Stack for Gateway Devices plays a central role within a smart metering network. It enables data transmission from numerous meters and sensors and allows the device to manage a large number of connections simultaneously.

The OMS® v4.5.1 stack implements all the protocol elements required for Wireless M-Bus compliance. It also covers a large part of the options and features specified in EN 13757 and its sub-standards, with a focus on the most commonly used options and features.

Version 4.5.1 of the OMS® Stack offers several new features and you can be sure that you are equipping your products with a proven and constantly evolving software solution.

Your benefits with our Protocol Stack Package

Platform Interface available as source code

Customization and fine-tuning of platform driver

Customization of radio settings (e.g., frequency)

Example application available

Example application allowing an easy start-up of the stack

Customization possibilities

Customization of this OMS® v4.5.1 stack to your requirements is possible.

Protocol Stack Features

OMS® v4.5.1

EN 13757-3/-4/-7 (Wireless M-Bus) compliant protocol stack for gateway devices

  • Operation modes S, T or C
  • Encryption modes 5 and 7

Compliant to specification OMS® v4.5.1 by OMS® group, referring to EN 13757

  • Security profiles A or B
  • Security profile D (encryption mode 10)1
  • Enables application to support all use cases specified by Annex M “Requirements for OMS® use case support”
  • Enables optimization of TRX timing1

1Features will be implemented in a later product version.

Available for the following hardware platforms

Silicon Labs

  • EFR32FG23
  • EFR32FG28

STMicroelectronics

  • STM32WL3

Technical Information

Supported Specifications

OMS® v.4.5.1 Protocol Stack compliant according

  • EN 13757-3/-4/-7
  • OMS®​​​​​​ Specification

Reference Hardware

  • Silicon Labs EFR32FG23: EFR32FG23 BRD2600A REV 01
  • Silicon Labs EFR32FG28: EFR32xG28 BRD4001A Rev A01
  • STMicroelectronics STM32WL3: Nucleo-WL33CC1

Memory Requirements

The code sizes described above indicate the typical memory requirements for operating the fully equipped protocol stack as a library, including associated drivers. The values are based on the specified reference hardware: STMicroelectronics STM32WL3: Nucleo-WL33CC1.

Frequently asked Questions

What is included in the STACKFORCE software package?
Our Protocol Stack package includes everything you need for integration:

  • Precompiled stack library
  • Hardware-specific drivers
  • Serial interface (UART, SPI, etc.)
  • Power management
  • Example applications for quick integration
  • Documentation

Is the source code open or encrypted? Can we make adjustments ourselves?
The Protocol Stack itself is delivered as object code and cannot be directly modified. The platform interface (including HAL and RF driver integration) is provided as source code. This allows you to:

  • Adapt the platform driver to your target hardware
  • Configure specific radio settings such as frequencies
  • Optimize driver behavior
  • Add your own components such as security and timers

For further adjustments to the stack itself, we are happy to support you with specific development services.

Our requirements are not fully covered by this stack. Can STACKFORCE make custom modifications?
Yes, that’s possible. In addition to our standard solutions, we offer customer-specific extensions of our Protocol Stacks. This enables us to implement your specific requirements so that the stack integrates seamlessly into your system environment.

My preferred hardware is not supported. What can I do?
We are happy to check compatibility with your specific hardware. If your hardware meets the minimum requirements for running a Protocol Stack, porting is generally possible. We can discuss the porting effort with you or provide our Platform Porting Guide so you can perform the porting yourself.

Can we test our preferred stack before making a decision?
Yes. You can request a free evaluation license and test the software in your target environment – without obligation and risk-free. More information about the evaluation offer can be found on our website under: Evaluation License.

Does STACKFORCE provide support for product certification? If so, how?
STACKFORCE uses a multi-stage testing process to ensure high software quality. This includes:

  • Unit, module, and firmware tests to check the functionality and stability of individual components
  • Static code analysis to detect errors and vulnerabilities at an early stage
  • Automated system tests on simulated and real hardware
  • Regression tests to ensure that existing functions continue to work reliably and that no new errors are introduced.