Tailored. Flexible. Future-proof.
You’re planning an innovative wireless product based on a specific or proprietary communication technology – but lack a suitable protocol stack?
That’s exactly where we come in: STACKFORCE is your development partner for customized protocol stacks based on modern communication technologies such as Wired and Wireless M-Bus/OMS®, LoRaWAN®, and mioty®, for which we already offer standard solutions – as well as other technologies like 6LoWPAN/TSCH, IEEE 802.15.4, LoRa®, Sigfox, Wi-SUN®, and more.
We develop tailored communication solutions based on standard technologies, modified standard protocols, or entirely proprietary systems – always aligned with your use case, tar-get platform, and technical requirements. Thanks to hardware-agnostic design, our protocol stacks can be ported to any hardware platform with minimal effort.
Who are our typical customers?
Evaluation and selection of appropriate wireless technologies or the design of proprietary protocols
Development of modular stack architectures
Implementation of efficient firmware
Support for product certification
Adapting firmware to the target hardware
Extensive testing at module and system level, including pre-certification
Delivery of detailed documentation and test reports
Reusability & Modular Architecture
Project & Source Code Management
Portability & Hardware Abstraction
Testing & Verification at All Levels
Questions? Get the answers here!
We start with a consultation to analyze your requirements and use case. Based on this, we recommend the most suitable wireless technology that supports your goals and ensures long-term viability.
Modified standards are based on well-known technologies adapted to meet your spe-cific needs. A proprietary protocol is developed entirely from scratch for your use case – ideal when existing standards are insufficient.
We leverage modular stack architectures, collaborate with major technology provid-ers, and have deep experience with a wide range of microcontrollers and RF chips – significantly reducing development time and accelerating time-to-market.
Yes. Our protocol stacks are pre-tested using official certification tools from organizations like the LoRa® Alliance or OMS® Group. We support you throughout the certification process, offering guidance, technical documentation, and direct assistance.
We work closely and transparently with you throughout the entire project. Regular milestones and progress reports ensure timely delivery. Agile methods allow us to adapt flexibly to changes or new requirements.
We collaborate closely with leading manufacturers like NXP, Semtech, Silicon Labs, STMicroelectronics, and Texas Instruments. We continuously monitor the market to identify additional partners relevant to our focus areas.
STACKFORCE relies on a comprehensive, multi-stage testing and verification process to ensure the highest software quality. Various test methods and tools are used to cover different levels of software development:
Our software development is primarily done in C, with code structured for seamless integration into C++-based software. For system tests and automation, we additionally use Python.
Our standard development environment is Visual Studio Code combined with CMake and the GCC compiler. At our customers’ request, we also work with alternative IDEs, including commercial environments such as IAR or Keil, as well as chip-specific IDEs like:
This flexibility ensures seamless integration into customer-specific development processes.
By default, we use the GCC toolchain for ARM, known for its wide adoption and reliability. Depending on the hardware platform, we also use specialized compilers provided by chip manufacturers, such as the compiler integrated in CCS by Texas Instruments. Additionally, the IAR compiler is frequently supported alongside GCC.
We primarily use CMake for creating and managing build configurations—a flexible, cross-platform build system that integrates perfectly into our automated development and testing processes. In exceptional cases, we use other build systems, for example, when they are directly integrated into the IDE specified by the customer.
Software versioning is managed with Git, and version numbers follow the established SemVer approach (Semantic Versioning). Our central platform for version control is GitLab. Additionally, CI jobs include automated tests such as static code analysis and unit tests to detect potential regression errors early.
