Each power-on writes a console log to the device. Older ones are rotated out as new ones arrive.

Flight logs are compressed on the board before they upload. Harder compression makes the file smaller, so it uploads faster and uses less of your data, but the board is busy compressing and cannot send its position for that time. The log itself is identical either way, so this only trades post-landing delay against file size.

The gap the board leaves between each piece of a flight log as it uploads over the mobile network. A longer gap gives the modem time to send each piece before the next, which is more reliable on a weak or congested signal; a shorter gap uploads faster where reception is strong. If uploads on a poor signal need a lot of retries, increase this. Default is 250 ms.

How long we keep this device's position history for the tracking page. This is our database, not the device: the flight log itself is unaffected.