Eight INAV debug values

INAV keeps eight debug slots. The debug mode decides what the firmware writes into them, and the same choice feeds the debug fields of a blackbox log. The footer on the tab says that in one sentence: the mode picks what the flight controller writes into the eight debug values and the blackbox debug fields.

This tab reads all eight as signed 32-bit numbers. The sensors tab is a different graph. On INAV that graph asks for the older debug message, which carries only the first four values and cuts each one to 16 bits. If a number looks clipped on Sensors and whole on Debug, that is the difference between the two messages, not two modes.

The sample rate here is fixed at 10 Hz, and only while the tab is open. It is not the 10, 20 or 50 Hz choice on the sensors tab. Pause holds the last samples. Resume starts the 10 Hz updates again. The traces keep about the last 150 samples, and a quiet line sits near zero when the mode is writing nothing.

NONE is the first name on the INAV 8 list. Other names on that list include GPS, LANDING, ALTITUDE and DYN_GYRO_LPF. The tab does not hard-code them. It shows the lookup that came from the board. If the saved index is outside that lookup, the label is Mode and the number, not a guessed name.

The mode shown as in use is the value read from the board, not the row you just highlighted. Change the choice, and the eight traces keep drawing the old mode. Save, let the flight controller reboot, and come back. The new mode is then the one in use, and the numbers follow it.

That reboot is the save for this tab. The board drops off and comes back, the same way other INAV settings that need a restart do. Reading the tab during the reboot just waits. When the board is up, Mode in use should be the name you saved.

A build that has no debug_mode setting cannot offer the list. The tab says this firmware has no debug_mode setting. The eight values can still be drawn, but there is no mode name to change.

Blackbox is where those same debug fields are stored for a flight, on the craft. This tab is the live look while you are connected. The log viewer opens the file afterwards. Use a mode only when you mean to read those fields. Leave it on NONE when you are done, then save and reboot, so later logs are not full of a test you have finished.

Betaflight has no Debug tab in FlySpark. Its debug mode is on the configuration tab, the same names as set debug_mode in the CLI, and the sensors graph draws up to eight channels from the older debug message. Do not look for this INAV list on a Betaflight board.

Chrome or Edge connects over USB or Bluetooth. Android adds Wi-Fi. iPhone uses Bluetooth or Wi-Fi and has no USB host. The debug tab needs an INAV board on that link. The 10 Hz updates are light, so Bluetooth can carry them, but a noisy link will skip samples the same way any other live graph does.