Modernizing a High-Precision RF Generator Platform
Modernization of device software, service access and communication architecture for a high-precision RF generator platform in small-series industrial production.
This case study describes a practical modernization project for an existing technical device platform. The focus was not a full rewrite, but a controlled restructuring of the software architecture, communication paths and service access around an existing embedded device.
Context
Time Base GmbH develops high-precision RF generator platforms for technical and industrial applications. The project focused on improving the structure, maintainability and connectivity of an existing device software platform.
Initial challenge
Grown software structure
The existing device software had grown over time and required clearer separation between hardware communication, service logic and user interface components.
Need for modern device access
The platform needed structured interfaces for service, automation and browser-based access to device status and functions.
Diagnostics and integration
Hardware/software integration, troubleshooting and diagnostic workflows needed to be supported more systematically.
Release and update structure
Versioning, update mechanisms and technical documentation had to support long-term maintainability of the device platform.
Solution
Architecture reconstruction:
the existing software architecture was analysed and restructured to make responsibilities and dependencies visible.
Dedicated service and communication layer:
communication logic was separated into a dedicated service layer connecting hardware interfaces, device services and UI components.
REST and MQTT interfaces:
REST API and MQTT-based communication were introduced for structured device access, automation and event-driven communication.
Embedded runtime and browser UI:
a Node.js-based runtime and Vue.js-based browser interface were used for device access, status display and service functions.
Component-based secure OTA:
a secure update mechanism was implemented for different device software components, including microcontroller firmware, hardware service, Node.js runtime files and Vue.js frontend files. Updates could be applied in any required combination, with backup, digital signature verification and rollback support.
Implementation areas
Hardware communication
Integration with device interfaces such as UART, USB, CAN and Ethernet as part of the device communication path.
Service functions
Structured access to status, configuration, diagnostic and maintenance-relevant information.
The modernization followed a layered approach. Hardware-near communication was separated from service logic. The service layer then provided structured access to device functions through documented APIs and event-driven communication. The browser-based interface used these service interfaces instead of directly depending on hardware-level implementation details.
Layer
Purpose
Device and hardware interfaces
Communication with RF generator hardware, controller modules and device-specific interfaces.
Service and communication layer
Protocol adaptation, device state handling, diagnostics, API access and MQTT messaging.
Browser-based user interface
Device status, service functions, configuration access and structured interaction with the device.
Documentation and release structure
Interface documentation, versioning, update concepts and maintainability support.
Outcome
Clearer separation between hardware communication, service layer and user interface
Improved maintainability of the device software platform
Structured basis for external device integration through REST and MQTT
Improved diagnostic and service access for hardware/software integration
Better foundation for versioning, updates and technical documentation
Reduced coupling between device internals and user-facing software components
Component-based OTA update workflow for MCU firmware, hardware service, Node.js runtime files and Vue.js frontend files
Flexible update package structure allowing selected device components to be updated in any required combination
Backup, digital signature verification and rollback support for safer field updates
This case study is based on project work for Time Base GmbH.
A shorter portfolio-style project reference is available here:
Time Base RF Generator Project.
Why this approach works for existing devices
Many technical devices do not need a complete software rewrite to become easier to maintain and integrate. A practical modernization can start by introducing clear boundaries, a service layer, documented APIs and a browser-based service interface around the existing platform.
This allows the device manufacturer to keep proven hardware-near functionality while improving service access, diagnostics, integration capabilities and future maintainability.
Need a similar modernization for an existing device?
I support device manufacturers with architecture assessment, service layer design, web-based UI, REST/MQTT interfaces, diagnostics, documentation and update concepts.
