Health data from inside the flight controller.
An SDK manufacturers build into their firmware. It records the signals INSICK needs at the right rate, computes basic health flags on board, and writes them in one standard format.
Flight logs were made for debugging, not for health.
Default logs miss signals that matter for wear or record them too coarsely, and every custom flight controller logs in its own format. Probe fixes the input instead of guessing from it.
- Firmware teamsAt manufacturers with their own flight controllers.
- ArduPilot and PX4 integratorsWho want richer health logging without writing it themselves.
- OperatorsBenefit indirectly: better data, earlier warnings, the same tools.
Health data from inside the flight controller.
- 1
Integrate
A C library, or a module for ArduPilot and PX4, connected through a few hooks in the firmware.
- 2
Record
Per-motor current and RPM, vibration spectrum, cell voltages and temperatures at fixed rates, in a compact health log.
- 3
Flag on board
Simple checks run on the controller and appear on the OSD or ground station — for example, a motor drawing far more than its neighbours.
- 4
Analyse
The health log goes into Hangar, Preflight or Bench like any other source.
- Per-motor current and RPM
- Vibration spectrum, not just RMS
- Per-cell voltage and pack temperature
- ESC temperature
- Hard-landing and impact events
- Configuration and firmware fingerprint
- Form
- C library; ArduPilot and PX4 modules
- Overhead target
- Under 2% CPU and 64 KB of flash
- Licence
- Free for manufacturers
- Output
- An open, documented health-log format
- Probe only observes. It never changes flight behaviour, control loops or failsafes.
- On-board flags are advisory and shown to the pilot; nothing acts on them automatically.
- Supported controllers and hardware requirements will be published with the SDK.