Proof of Know-How
Selected technical proof points from embedded-systems development, communication protocols, and testing methodology. The anonymized examples cover safety-relevant communication, industrial system integration, and the technical evaluation of OCPP 2.1 for charging hardware. Customer names are not published.
Technical depth, not marketing claims
Customer names are not published. Each project below is presented as an anonymized case study. What matters is not who it was built for, but what was built and how.
The case studies document concrete technical work in firmware, protocol integration, and test frameworks. Each case study describes a real technical challenge from embedded development.
The same embedded discipline also applies to charging infrastructure: safety-relevant communication, protocol integration, and structured testing procedures. The following technical evaluation of OCPP 2.1 for charging hardware shows this connection.
Selected technical proof points
Protocol, communication, and system integration
Technical evaluation of OCPP 2.1 for charging hardware
C · OCPP 2.1 · MQTT · WebSocket
Technical evaluation of OCPP 2.1 message handling in collaboration with partners and their existing CSMS environments. OCTT conformity preparation and formal OCPP certification are not part of this proof point.
Embedded system with safety and communication
C · CAN Bus · RTOS
Clemios transferred a safety-relevant embedded system with validated real-time CAN communication into industrial production.
System integration and error handling
Modbus TCP/RTU
Clemios secured multi-device operation with structured error recovery for industrial communication systems.
Modbus RTU communication and timing synchronization fix
Modbus RTU · C
Clemios fixed a field-critical timing error without downtime and rolled out the fix for Modbus RTU devices.
Embedded systems and testing methodology
Training and workshop for MCU integration
Ethernet/IP · MCU
Clemios enabled a customer engineering team to perform MCU-to-Ethernet integration independently.
Custom PCB design and firmware
Altium Designer · C · Ceedling
Clemios delivered production-ready PCB firmware validated with Ceedling unit tests.
Programming tool for STM32 MCU
C · STM32 · Hex File Flashing
Clemios optimized STM32 firmware flashing for the production line.
Hysteresis control for positioning
C · CAN Bus
Clemios achieved precision positioning with hysteresis compensation in CAN-based industrial machines.
Automated unit tests for MCU verification
Python · pytest
Clemios automated MCU tests and expanded regression coverage.
Comparison of unit-testing frameworks
Ceedling · GoogleTest · C
Clemios substantiated the framework selection and introduced Ceedling for embedded C unit tests.
Enhanced data integrity with CRC checking
C · EEPROM · CRC Algorithms
Clemios protected non-volatile memory against data corruption with CRC-based verification.
Technologies and tools
| Category | Technologies and tools |
|---|---|
| Collaboration & documentation | |
| Team meetings, communication, and documentation | Word, Excel, Outlook, Teams, Slack, Meet, Calendly, Discord |
| Development tools | |
| Development environment |
|
| AI-assisted development | Cursor, Claude, GPT |
| Modeling | Enterprise Architect, PlantUML, StarUML |
| Debugging tools | Segger, Saleae, ST-LINK V2, PCAN-USB, AZ-Delivery Logic Analyzer |
| Hardware & communication | |
| Microcontrollers and platforms |
|
| Microcontroller interfaces | Ethernet, WLAN, Bluetooth Low Energy, USB |
| Communication protocols |
|
| Microcontroller operating systems | Linux, Embedded Linux (Yocto), RTOS (FreeRTOS, Zephyr), Bare-Metal |
| Code quality & programming | |
| Programming languages | C/C++, Python (unit testing with Ceedling, GoogleTest, or pytest) |
| Code documentation | Doxygen |
| Coding guidelines | MISRA-C |
| Static code analysis | SonarQube, Pylint |
| Version control | GitHub, GitLab, Azure DevOps, Subversion (SVN), TortoiseSVN |
| Manufacturing & prototyping | |
| PCB-Design | Altium, Fusion 360° |
| 3D printer, PCB microscope | Creality Ender 5, KERN Optic |
| Project & requirements management | |
| Requirement Engineering | Confluence, Requirement Yogi, Polarion |
| Test Engineering | Polarion, Xray |
| Project management | Jira, Azure DevOps, Projektron BCS, GitLab |
Frequently asked questions
Why are all projects anonymized?
The projects are anonymized. Clemios presents the engineering work, not the customer name.
Does Clemios have eMobility-specific projects?
Yes. This page shows the technical evaluation of OCPP 2.1 for charging hardware in collaboration with partners and their existing CSMS environments.
For the current product context, see ChargeSphere.OCPP and the Integration and Validation page.
Are further details about a specific project available?
Yes. Clemios can discuss technical details under NDA in a project-specific conversation. Get in touch through the contact page.
Which industries has Clemios worked in?
The case studies shown on this page cover safety-relevant embedded communication and industrial system integration.
Further areas include testing tools and the technical evaluation of OCPP 2.1 for charging infrastructure.
Which test frameworks does Clemios use?
Ceedling for embedded C unit tests. GoogleTest for C++. pytest for Python-based test automation.
Technical conversation
Selected technical proof points from embedded-systems development, communication protocols, and testing methodology. Talk to the team about your project.