Reference
Look up a record field, a PX4 parameter, a console status, a limit, a shortcut or a term, stated exactly as Foxborne uses it, so you can check it against your own console.
On this page2
These pages hold facts, not procedures. Each one is a set of tables under stable headings, so you can link to a section and cite it in a review.
Rule pages#
Each detection rule has its own page: what it reads, when it fires, its exact wording and what a finding does not mean. Start with How rules work, then Thresholds, scopes and overrides.
| Reads | Rules |
|---|---|
| Companion journal | process_exit, service_restart, device_disconnect |
| Process samples | memory_pressure |
| Ground receive log | telemetry_gap |
| Flight log | vibration_high, failsafe_entered, topic_stall, gnss_jamming, gps_quality_drop, log_dropout, battery_sag |
| Every source | clock_uncertain |
Rule versions explains how a rule's version changes and how to trace those changes in your audit log.
File formats and platforms#
The format pages in the Documentation tab describe the files Foxborne imports and the fields it reads from them.
- Supported file formats: every format Foxborne reads, and how it recognizes each one.
- PX4 ULog: the flight log from the flight controller's SD card.
- journalctl JSON exports: the systemd journal from the companion computer.
- MAVLink telemetry logs and receive records: ground station
.tlogfiles and the Foxborne receiver's records. - IRIG 106 Chapter 10 recordings: flight test recordings, packet by packet.
- Range records: radar TSPI, telemetry receiver and flight termination console logs.
The two JSONL formats are documented here, field by field: Collector JSONL records and Receiver JSONL records. For what changed in each version of Foxborne, see Release notes.
Platforms and Vehicle parts and their logs show which part of each machine records which of these files.