Skip to content

Pre-flight

Use this page as the final AstroNav Nano readiness check. It does not replace the rocket, recovery-system, range, or local safety procedures.

Before opening Settings.ini:

  1. Disconnect the battery, E-match, pyro charge, and other hazardous hardware.
  2. Connect AstroNav Nano to the programming board with the flat cable.
  3. Connect the programming board to your computer with a USB-C data cable.
  4. Wait for startup checks to finish.
  5. Open the AstroNav Nano drive in Windows File Explorer.
  6. Open Settings.ini from the root of the drive.

The drive should also contain Howto.txt. Read it before changing settings.

Before installing or connecting live pyro hardware:

  • Open the intended Settings.ini or review the settings in AstroNav MC.
  • Confirm the expected flight values:
    • ESTIMATED_HEIGHT_M
    • HEIGHT_MARGIN_M
    • ESTIMATED_SPEED_MPS
    • SPEED_MARGIN_MPS
  • Set LAUNCH_THRESHOLD_G safely above expected handling and vibration noise. Do not set it close to 1 g. A value around 2 g or higher may be appropriate for some vehicles, but it is not universal; validate it for the specific flight.
  • Confirm FIRE_PYRO_APOGEE has the intended value.
  • Save the configuration, safely eject the device, reconnect it, and verify that the values persisted.
  • Test configuration and detection with hazardous outputs physically disconnected.

AstroNav Nano recognizes these intended power ranges:

Source Voltage
USB 4.5 - 5.5 V
1S LiPo 3.0 - 4.35 V
2S LiPo 6.0 - 8.4 V

Check:

  • Battery condition, voltage, polarity, connector, and insulation.
  • Flat-cable orientation and condition.
  • Programming-board and Nano connectors.
  • Pyro wiring for damage, exposed conductors, pinching, and strain.
  • That the selected battery is appropriate for the vehicle and intended pyro use.

Confirm that:

  • AstroNav Nano is firmly secured in its case or fixture.
  • The orientation matches the configured and calibrated flight orientation.
  • The sensor area is unobstructed.
  • The board cannot shift, rotate, or vibrate during flight.
  • Cables are protected from abrasion, heat, recovery-system movement, and sharp edges.
  • The USB connection, status LED, and access needed for post-flight data retrieval remain available as designed.

Power the vehicle only when it is in a safe location and can remain still.

  1. Place the vehicle in its intended flight orientation.
  2. Keep it stationary during startup and calibration.
  3. Wait for calibration to complete.
  4. Confirm that the board reaches Idle.
  5. Confirm that no critical fault is present.

Only complete this section after the configuration and board checks pass.

  • Use only approved low-voltage, low-power pyro hardware.
  • Follow the vehicle-specific recovery and charge procedure; this page does not approve a charge amount or live-charge assembly method.
  • Confirm that the deployment charge is positioned according to the recovery-system design, normally under the parachute where that design requires it.
  • Use the approved fireproof cotton, paper, or blanket to protect the parachute.
  • Confirm that the parachute, recovery lines, and deployment path are free to move.
  • Keep live pyro hardware disconnected until the vehicle is otherwise ready and the launch-area procedure permits connection.
  • Never use PYROTEST with a live pyro circuit.

See Using the pyro function for the complete safety workflow.

Before launch, confirm:

  • The nose cone, case, fasteners, and access panels are secure.
  • The board, battery, and wiring cannot move inside the vehicle.
  • The recovery system is installed in the correct order.
  • The motor, launch hardware, and recovery hardware follow their own instructions.
  • The vehicle is stable and suitable for the planned flight.
  • The launch area and range procedure permit the planned operation.
  • A second person has independently reviewed the vehicle when possible.

Board readiness is only one part of launch readiness. Do not launch with an unresolved warning, fault, damaged component, uncertain setting, or improvised recovery arrangement.

If troubleshooting is required, inspect these fields:

FAULT_REASON
POWER_MODE
STATE
VIN_VOLTAGE
HEALTHY
IMU_STREAM_OK
BARO_OK
FLASH_FS_OK
CRITICAL

Serial monitoring uses 115200 baud:

Terminal window
pio device monitor

After the vehicle has landed:

  • Confirm the vehicle is safe before approaching it.
  • Wait for the landing indication and saved flight data.
  • Disconnect power and hazardous hardware according to the recovery procedure.
  • Copy and preserve the CSV flight log.
  • Review warnings, faults, and pyro status in Flight logs.