Telemetry and ground link
Most telemetry hands you a filtered summary of a vehicle you cannot reach. We build links that hand you the vehicle — every subsystem addressable from the ground as though the bus ran across your desk.
The register you need is the one nobody published
Conventional telemetry publishes a chosen set of fields at a fixed rate. It tells you that something happened, and rarely what. The moment you need a register nobody thought to publish before take-off, the flight is already over.
We build transport that extends the vehicle's internal buses to the ground station over the radio link, so a subsystem is addressable in flight exactly as it is on the bench. Not a stream describing the vehicle — the vehicle's own interfaces, live.
Engineers use the tools they already have, against the real hardware, while it is flying. One workflow instead of two, and no test campaign that can only reproduce the fault on the ground.
What that changes on a test campaign
- Diagnosis during the event. Interrogate a misbehaving subsystem while it is misbehaving, rather than inferring the cause from a log after recovery.
- One set of tools. The same scripts and parameter sets on the bench and in the air.
- Shorter campaigns. Faults that take several flights to characterise through conventional telemetry are often closed inside one.
- Full-rate capture where it matters, with bandwidth allocated deliberately instead of by whatever the autopilot chose to publish.
A link is only as good as its worst minute
Live access is worth nothing without the link under it, so we design that too — and build it from commercial radios, RFDesign and Taisync class, rather than pretending the physics is proprietary.
Link budgets against the real terrain and range. Antenna placement and pattern on the actual airframe. Contention and interference behaviour measured rather than assumed. And a defined degradation: what is still guaranteed to arrive when the channel is poor. Command integrity and authentication are part of that design, not an afterthought.
What you get
- Bench-grade access to every subsystem while the vehicle is flying
- Diagnosis during the fault rather than reconstruction after it
- A link with defined behaviour at the edge of its range
Related work
Tell us the constraint you cannot get past
The mass budget, the latency, the environment, the certification route. We will tell you honestly whether it is something we should be working on — and if it is not, who should.