Firmware · embedded · software
A catalogue drone flies a catalogue mission. The work that makes it yours happens in the flight stack, the payload bus and the software your operators sit in front of.
Three layers
Netopia Autonomous
Flight parameters, failsafe logic, geofences, return-to-home behaviour and mission modes rewritten against your operating procedures. We work at the source level on the stacks we support, and validate every build on the bench before it reaches an airframe.
Harmony
Sensors, radios and payload controllers integrated at board level by Harmony, the group’s IoT and embedded practice. Where a payload has no driver for your airframe, they write one.
Netopia
The console, the mission archive and the integrations into what you already run — built by Netopia, the group’s software house, on the same infrastructure that holds your data.
Scope
A typical engagement touches these areas. Anything outside them we say so up front rather than discover in flight test.
| Area | What changes | Owner |
|---|---|---|
| Flight control | Parameter set, tuning, custom modes | Autonomous |
| Failsafe | Link loss, low battery, geofence breach | Autonomous |
| Payload | Driver, mount, power and data bus | Harmony |
| Link | Radio, LTE fallback, mesh relay | Harmony |
| Console | Live telemetry, planning, replay | Netopia |
| Records | Signed logs, export, retention policy | Netopia |
| Hosting | Moroccan datacentre, backup and keys | Netopia |
Flight control
Parameter set, tuning, custom modes
Autonomous
Failsafe
Link loss, low battery, geofence breach
Autonomous
Payload
Driver, mount, power and data bus
Harmony
Link
Radio, LTE fallback, mesh relay
Harmony
Console
Live telemetry, planning, replay
Netopia
Records
Signed logs, export, retention policy
Netopia
Hosting
Moroccan datacentre, backup and keys
Netopia
How it runs
We sit with your operations team and write the mission profile down — airspace, payload, endurance, weather envelope, who signs the flight off.
Two or three airframes from our referenced manufacturers, with the adaptation cost and lead time attached to each. You choose against real numbers.
Firmware, payload and console work run in parallel across the three entities, against one backlog and one delivery date.
Bench validation, flight test and an acceptance flight with your operators. You receive the test report, the firmware hashes and the training record.
Two weeks from the first meeting we can usually tell you the airframe, the adaptation scope and the cost.