← All case studies Case studyInvestigate
Industrial & Consumer IoT · Embedded System Investigation · Device Development · 4-month alpha

50 undocumented RF protocols, decoded and shipped in one platform

A global leader in automation needed its next-generation product to interoperate with decades of legacy field equipment none of it documented, none of it supported. Better Devices reverse engineered the signals and delivered a working embedded platform in four months.

Scroll
An engineer probing a board while decoding its protocol on a logic analyser
Exhibit Industrial & Consumer IoT
Results 04
50+ proprietary analog RF protocols decoded with no surviving documentation
4 months from kickoff to functional alpha hardware + firmware
Days, not weeks, to adapt when new protocols surfaced late in development
First decoded message in days once the reference implementation was running
01

The challenge

The client's product portfolio had to speak to a diverse installed base of legacy analog communication systems proprietary, high-bandwidth signaling schemes designed decades ago, with no specifications, no reference hardware, and no vendors left to ask. Interoperability with this equipment was not optional; it was the feature.

Sophisticated integrations like this carry a specific risk profile: every unknown signal is a potential late-stage redesign, and the final set of protocols was still moving while development had to begin. The program needed the unknowns resolved early, without stalling hardware, firmware, and software teams while research ran.

02

The approach

01

A focused research phase firstFour weeks of broadband signal capture and analysis high-bandwidth oscilloscopes, Python and MATLAB signal processing identified the modulation schemes, framing, and timing hidden in each analog signal.

02

An executable spec instead of a written oneBetter Devices built a software-defined-radio reference implementation that ingested real signal captures and output decoded, structured messages a single runnable source of truth every team could test against.

03

Three tracks in parallelWith the spec as the shared reference, hardware, firmware, and software development ran concurrently instead of in sequence software integrated against replayed captures before boards existed.

04

Integration as confirmationBecause every discipline built against the same decoded reality, system integration verified known behavior rather than discovering new problems.

03

The outcome

The client received a fully functional alpha embedded hardware and software four months after kickoff, compatible with more than fifty undocumented signaling schemes. When additional protocols appeared late in the program, the executable spec absorbed them in hours rather than triggering hardware revisions. The reference implementation remains in the client's toolchain as a regression suite for future product variants: the knowledge lives in code and captures, not in slides.

Services used

Facing an undocumented system of your own?