Feature: Medical IoT
measurement data aggregation. Te resulting data packets are then sent over a UART to the Proteus-IV module, which forwards it via its SPP-like BLE profile to an app residing on a smartphone or tablet. Te app may also visualise the data, upload it to the cloud or connect it to a clinical server. Te communication can bi-directional: i.e., the app can send
configuration commands such as sampling rate, measurement mode or thresholds back through Proteus-IV to the host MCU. Tis architecture cleanly separates sensor and application logic from the wireless stack. To simplify integration on the host MCU, Würth Elektronik provides
the open-source Wireless Connectivity SDK with drivers, and examples in C. Te SDK abstracts the UART protocol and module control into high-level functions. It also provides the features of the radio modules as functions, so that its integration is done in a few steps:
1. First, the GPIOs and UART of the host MCU must be defined. Here, the available pins of the host MCU are chosen to be used for GPIO and UART purposes:
With this module, the actual firmware work on the MCU side
remains focused on sensor handling and data formatting, not on implementing a Bluetooth LE stack.
Its faster with pre-certified modules Using a pre-certified module with SPP-like BLE firmware has a measurable impact on both engineering and business metrics. Typical values for a wearable device project include integration time of 1-2 weeks at application level, compared with 6-8 weeks for a custom GATT-based solution. The code size of the application firmware stays below a
few tens of kilobytes when the BLE stack is offloaded to the module, which simplifies maintenance. In addition, RF-related effort, certification time and costs
are significantly reduced by leveraging module certifications (Figure 3) – this is particularly valuable to companies that are entering new medical segments or expanding existing product lines.
2. Next, the callback functions must be defined, to inform the application about events sent from the module to the host. Tis includes events for connection and security setup, as well as data reception:
Future trends Wearable health monitoring combines strict medical expectations with consumer demands. Teams that try to reinvent BLE connectivity and RF design from scratch often lose precious months and undertake risks that could be considered unnecessary. Pre-certified radio modules with proven SPP-like BLE
firmware decouple sensor and algorithm innovation from wireless complexity. Modules like Proteus-IV and Ophelia- IV form a scaleable platform for developing robust, safe and secure medical and health wearables. And as regulatory and cybersecurity requirements continue to tighten, modular standards-based connectivity will become an even more important foundation for safe, efficient and innovative applications with wireless connectivity like healthcare products.
26 April 2026
www.electronicsworld.co.uk
3. To start the Proteus-IV radio module in the chosen operation mode, the ProteusIV_Init function must be called:
4. Data is then fetched from the sensors and sent via the Proteus- IV to the mobile phone app, once the radio link is open:
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48
