Wireless · LoRa · BLE · Matter/Thread

Wireless IoT where the radio is engineered, not dropped in from a module

LoRaWAN, BLE 5, Matter and Thread on Nordic nRF52 and nRF53 — with the antenna, link budget and range designed and measured here, not inherited from a module datasheet. Range is an RF problem, and RF is solved in-house. One lead engineer owns the result. 20+ years.

What this service covers

Wireless IoT development is the full radio side of a connected device — protocol stack, firmware, antenna, and the RF path that decides whether the link holds at range. Most shops write firmware on top of a pre-certified module and stop. Here the antenna and RF front end are designed to the product, because that is what actually sets range and battery life.

A wireless product that works on the bench and fails across the building almost always fails in RF, not in code — a poorly matched antenna, a bad ground plane, an unrealistic link budget. Designing the radio in-house is what closes that gap.

Who needs it

Products needing long range on a battery — LoRaWAN or Sub-GHz sensors that must reach a gateway across a site or a field.
Smart-home and building devices targeting Matter and Thread interoperability on Nordic silicon.
BLE 5 devices — wearables, tags, sensors — that need reliable connection and a real power budget.
Teams whose wireless product passes on the bench but drops out at range, where the fix is antenna and RF, not firmware.
Devices needing a custom antenna on the PCB because a chip antenna or module will not meet the size, cost, or range target.

How the work runs

Protocol and link budget

The right protocol (LoRaWAN, BLE, Matter/Thread, Sub-GHz) chosen against range, power, and topology — with a link budget calculated up front so range is a number, not a hope.

Antenna and RF path

Antenna designed on FR-4 — patch, trace, or array — with matching network and ground plane laid out for the frequency, then measured on real hardware.

Stack and firmware

Protocol stack and application firmware on nRF Connect SDK / Zephyr, with OTA updates and a power budget engineered for battery life.

Certification path

Design toward FCC and CE pre-compliance so the device is ready for the test lab, not surprised by it.

Range validation

Range, throughput, and power measured on real hardware in a real environment — the numbers that decide whether the product works in the field.

Why MPV-LAB for this

The radio is designed, not inherited. Antenna, matching, and RF path built to the product — the piece that sets range and battery life, and the piece most shops skip.
Antennas on FR-4. Patch and trace antennas designed and measured in-house — the same RF practice behind the radar work.
Certification designed in. FCC and CE pre-compliance considered from the layout, not discovered at the test lab.
One hand from antenna to app. RF, firmware, and power come from one accountable engineer, so range and battery targets are engineered together.
You keep everything. Antenna design, firmware source, and RF measurements are handed over — no lock-in.

Common questions

Do you design the antenna or use a module?

Either, driven by the product. A pre-certified module is fastest when size and range allow; a custom antenna on FR-4 wins when a module will not meet the size, cost, or range target. The rare capability here is that the antenna can be designed and measured in-house rather than accepted from a datasheet.

Which protocol is right for my product?

It follows range, power, and topology: LoRaWAN or Sub-GHz for long range on a battery, BLE for phones and wearables, Matter/Thread for interoperable smart-home mesh. The choice is made against your requirements with a link budget, not by default.

Can you get my device through FCC or CE?

The design targets FCC and CE pre-compliance from the layout — antenna, emissions, and power — so the device arrives at the test lab ready rather than needing a re-spin after it fails.

My wireless product works close up but drops at range. Can you fix it?

Usually yes, and usually it is RF, not firmware — antenna matching, ground plane, or an optimistic link budget. It starts with measurement on real hardware, then a targeted fix to the RF path.

Who owns the design?

You do, once the milestone is paid. Antenna design, firmware source, and RF measurement data are handed over in full — any other engineer can continue from there.