Independent Engineering Review · Open-Hardware IoT Sensor

RINAsense —
RINA IoT Sensor Node

An independent engineering review of an open-hardware RINA research node — proven as research, scoped for production.

Credible research platform · production is a separate engineering program
RINAsense IoT sensor node

Meet the RINAsense node

The RINAsense node is a low-cost (~€35), low-power environmental sensor built around an Espressif ESP32 microcontroller and a DHT22 temperature/humidity sensor. What sets it apart is its firmware — a purpose-built implementation of the RINA networking architecture — so the device joins and communicates over a RINA network natively, rather than over the usual TCP/IP. It was created and published as open hardware by the IoT Research Group at Fundació i2CAT (Barcelona) as a reproducible instrument for RINA research, and validated in a real smart-building testbed.

Design & files © Fundació i2CAT, published open-hardware. Reviewed here independently.

Our goal

Answer one question for an open-hardware IoT sensor node: how sound is the engineering, and what would it take to move from a research instrument toward a product? Rather than judge the paper at face value, Product Engineer LLC worked up from the design's own evidence — the peer-reviewed paper, component datasheets, cited standards, and the project's actual published source code — and produced electrical, mechanical and software reviews culminating in a severity-first FMEA. Every finding is traceable; nothing is asserted.

This is an independent, constructive review of a credible, peer-reviewed open-hardware design. The device is a strong research artifact for RINA experimentation; taking it to a fielded product would be a separate, well-defined engineering effort, which this review maps out.
ESP32 + DHT22Wi-Fi node · native RINA stack
2 variantsUSB & battery, assessed separately
26Evidence-backed FMEA findings
Source-verifiedSecurity findings from the project's own config

What is RINA — and why it's different

Most connected devices talk over TCP/IP, the protocols that run the internet. To send a reading, the software connects to a numeric address and port (for example 192.168.1.100:1883) and then bolts a separate security layer (TLS) on top. If the address or network changes, the app breaks, and security is always an add-on.

RINA — the Recursive InterNetwork Architecture — takes a cleaner approach: it treats all networking as one simple, repeating idea. A device joins a named network (called a "DIF" — think of it as a members-only club you join by name) and then reaches other applications by name, not by address. And security and quality-of-service are built into the club's rules: a device that is admitted automatically inherits them, instead of each app adding its own.

RINAsense device Named network (a "DIF") e.g. "building-sensors.DIF" security + quality built in (unauthorised devices refused at the door) Another app "data-collector.APP" enrol (authenticated) reach by name You join a named network and reach apps by name — security comes with membership. TCP/IP instead uses numeric addresses + ports, with security bolted on.

Why it matters for IoT: simpler device code (no hard-coded addresses), built-in authentication (an unauthorised device is refused at enrolment — which the authors demonstrated), and a design that scales from one sensor to a whole network by stacking these named layers. RINAsense is a working proof that this can run on a tiny, low-power chip.

The review process

Each step feeds the next — from reading the paper to a two-variant system FMEA.

1
Read the paperUnderstand the peer-reviewed HardwareX paper and the open-access technical text — architecture, BOM, schematic, firmware modules, energy method, and validation.
2
Systems understanding + block diagramMap the whole system — ESP32, DHT22 sensor, power, and the layered RINA firmware stack — and explain how the device satisfies the conditions of RINA.
3
Product specificationReconstruct a detailed, tagged requirement set (electrical, sensor, power/battery, wireless, firmware, security, mechanical, environmental).
4
Discipline reviewsElectrical, mechanical/enclosure and software/firmware reviews against component datasheets and the IPC/IEC/ETSI standards.
5
System FMEA (two variants)Culminate in a severity-first FMEA for the USB and battery variants — every finding backed by the paper, the project's own source code, a datasheet or a standard.

System block diagram

The node's hardware, its layered RINA firmware stack, and the external RINA testbed it joins.

RINAsense system block diagram

What we concluded

As a RINA / networking research platform the design is genuinely credible — working, reproducible, open, and peer-reviewed. Two honest caveats sit under the "scientific instrument" label: a sealed, unvented enclosure can bias the temperature/humidity readings well beyond the sensor's own accuracy, and the headline battery life is optimistic because it was measured bypassing the development board's own power draw. It is not a product and was never presented as one — a production version would need a real PCB, a protected battery front-end, a rated/vented enclosure, a proper device-security stack (secure boot, encrypted per-device credentials, secure updates), and EMC/safety qualification.

The deliverables

Evidence & sources

Every figure comes directly from the design's own evidence and checked against the relevant standards. Notably, the security findings are read directly from the project's published configuration file, not inferred.

Standards applied (all held in the review knowledge base): IEC 62133-2 & UN 38.3 (battery), IEC 61000-4-2 & ANSI/ESD S20.20 (ESD), IEC 62368-1 (product safety), UL 94 (flammability), IEC 60529 (ingress), IEC 60068-2 (mechanical), J-STD-001 & IPC-A-610 (solder), MISRA C:2012 (firmware), ETSI EN 303 645 · OWASP IoT · NIST SP 800-213 · EU Cyber Resilience Act (IoT security), EN 300 328 / EN 301 489 / CISPR 32/35 / FCC Part 15 (EMC/radio), AIAG-VDA / SAE J1739 / MIL-STD-1629A (FMEA method).

Design evidence: the RINAsense HardwareX paper (2025), the open-access technical text and design files, the ESP32-WROOM-32 & DHT22 datasheets, and the project's published source configuration.

Acknowledgements & sources

This is an independent engineering review of an openly published, peer-reviewed design; it exists only because the original authors shared their work as open hardware and open access. Full credit to David Sarabia-Jácome, Eduard Grasa and Marisa Catalán of Fundació i2CAT (Internet of Things Research Group, Barcelona), whose RINAsense node and firmware — released under Apache-2.0 (firmware) and CERN-OHL-S v2 (hardware) — made this analysis possible. The work was funded by the European Union Horizon 2020 programme (TERMINET project).

Project & paper: RINAsense in HardwareX (2025). Technical details & design-file downloads: open-access full text (PMC).

Product Engineer LLC is not affiliated with Fundació i2CAT. This review is offered constructively to support an open-source project.