A pilot on your own data
Bring your hardest incident.
Send one failure you have already investigated. We rebuild it on your data, beside your current tools, and show where the evidence agrees with your conclusion and where it doesn’t.
- Your logs can stay in your network
- Runs beside your current tools
- A reply from an engineer
What to send
- PX4 flight logRequired.ulgThe completed ULog from the flight controller’s SD card.
- Companion journalRecommendedjournalctl -o json --since … --until …The systemd journal export covering the flight, with its boot ID.
- Ground receive logRecommended.jsonlWhat range control heard from the vehicle, and when.
- Collector samplesOptional.jsonlProcess memory, CPU and restarts, if the collector was installed.
What happens next
- 1Send one incidentA failure you have already investigated, with the flight log and whatever companion or ground evidence you kept.
- 2We reconstruct itBeside your current tools, on your data, with every claim traced to its source.
- 3Compare the answersWhere the evidence agrees with your conclusion, where it does not, and what it cannot decide.
Do the logs have to leave our network?
No. A pilot can run on a Foxborne install inside your network, and you decide what anyone else sees.
Which vehicles and autopilots do you read?
PX4 flight logs, systemd journal exports from Linux companion computers, MAVLink receive records and IRIG 106 Chapter 10 flight test recordings. Tell us what else you record and we will say plainly whether Foxborne reads it today.
Who answers?
An engineer who builds Foxborne. There is no sales queue between your message and the people who can reconstruct your incident.