Skip to content

How every board is tested

A flight computer you can’t trust is worse than none. Every AstroNav Nano goes through the same steps before it flies. Steps 4 and 5 you can repeat yourself at any time.

Before the flight firmware goes on, a separate self-test firmware (TestTools) checks the board:

  • the IMU and the barometer respond
  • the input voltage is measured correctly, and the power source (USB, 1S or 2S) is recognised
  • the pyro output and GPIO 2 and 3 stay low the whole time

The status LED shows the result at a glance.

When the flight firmware is installed, each board gets its own serial number in the RP2350’s one-time-programmable (OTP) memory. It can never be changed or lost, so every board, flight log and support question can be traced back to one specific unit. See Production identity.

Right after flashing, the upload tool asks the board for its health report (sensors, power, storage and battery) and shows a clear pass or fail.

Run GYROTEST: turn the board 90° flat on the table, and it prints the total angle per axis. It should read about 90°, not 45° or 180°.

Run PYROTEST with an LED or a resistor on the pyro output, never a real charge. The board asks for confirmation first. It records how far the battery voltage dipped during the pulse (PYRO_MIN_BATTERY_V), so you know whether your battery can deliver the firing current.

Each flight log records what the board decided and why: the apogee trigger, whether the pyro fired or why it was blocked, and how landing was detected. See Flight logs. Open the flight in Mission replay to check that every phase was detected at the right moment.