Skip to content

ground-v1.5.5

Pre-release
Pre-release

Choose a tag to compare

@ThePrivatePanda ThePrivatePanda released this 08 Nov 14:57
· 72 commits to 3b20485ea8ad2812f895888466b11c265310d1d0 since this release

Test build with new flight software. Boot-air ending and the IMU stepping up on the ground have been seen on a real board; take-off, landing, the landed sleep, Stop2 and the IMU pin reset have only been tested on a computer, so try it on a spare board first. It is marked as a pre-release, so the app won't offer it as an update.

New in 1.5.5

  • Analysis tab: pick a pull and it lays out what the board logged, boot by boot. Reset causes and how each boot ended, phase changes with the firmware's own reason, sensor and bus events, the sensors' valid flags, lowest and highest readings, gaps, and what the log can't show. Open in Replay charts the values.
  • Pulls: choose the baud rate, see valid and invalid records as they come in, and a chip with 0 records or only boot events is a finished pull, not a failure.
  • Clear erases with no checks first.
  • T-Beam firmware 1.2.2: the receiver reports the spreading factor its radio chip is actually on and whether it is listening, and the app confirms a factor only from that.

Flight software in this build

  • Ground and air: the IMU decides and a live barometer or GPS has to agree, a climb to go up and flat to come down. The barometer alone never puts a board in the air. The rules are in fsw/V2_6_X_Code/docs/phases.md.
  • On the ground the IMU runs at 1 Hz and steps up to 20 Hz when moved.
  • After a flight the board looks for a GPS fix, then puts the GPS in standby and sleeps between packets (Stop2), transmitting and logging at the ground gaps. Movement wakes everything again.
  • The radio sleeps between packets in every phase.
  • The IMU is reset through its reset pin at every boot and when it stops answering or holds the I2C bus.
  • Sensor, bus, phase, radio and flash events are logged on the chip and show in pulls and the Analysis tab.
  • A ground log gap of 0 keeps every IMU reading and writes it at once.

Everything else is in the 1.5.0 to 1.5.4 notes.