Major release Software Version V3.171

This software brings several bug fixes, management improvements, faster cloud access and uses the new DZ database for the logbook entry.

change list

V3.15

Firebase library migration — Firebase V7.x / new JSON API The Firebase client library has been updated to the new V7.x-compatible version with updated JSON handling throughout the codebase.

CSV array size changes Internal CSV data arrays were resized to match updated logging requirements.

Sleep timer extended to 2 hours (motion-detection inactive) The auto-sleep timeout has been increased from the previous value to 2 hours when no action is detected.

Firebase stability fixes Several Firebase connectivity and write issues were resolved.

Device path corrected (fix from 23FEB26) Device name now correctly at runtime and used in Firebase RTDB paths.

GPS fix status display: “FIX” indicator now shows inverse when FIXOK GPS flag is set.

V3.151

Wi-Fi credentials can be pre-loaded from SD card on startup, Wi-Fi SSID and password are read from the SD card (readWifiFromSD()), allowing deployment without interactive Wi-Fi setup.

GPS parser timeout added A watchdog timeout has been added to the GPS UART parser to prevent hangs if the GPS receiver stops sending data.

Fixed: crash in book2RTDB when logbook entry has empty location Uploading a logbook entry with an empty/missing GPS location no longer causes a crash.

Fixed: shutdown sequence — all EPD lines now properly released All EPD SPI/control lines are set to floating/input after the display hibernates, preventing leakage current during deep sleep.

V3.16

Shutdown screen with full white refresh (ByeScreen) The shutdown screen now performs a full all-white EPD panel clear before drawing the goodbye screen, reducing possible ghost images.

Altitude rounding at Set0 fixed The rounding behaviour for the altitude display at the Set0 calibration baseline has been corrected.

Wi-Fi stop button A button shortcut (SET0 held during Wi-Fi init) allows the user to skip/abort Wi-Fi connection and continue offline.

V3.162

Crash diagnostics breadcrumbs A crash_stage counter is now incremented at key milestones throughout startup and runtime. This value is stored in RTC RAM (survives deep sleep) and mirrored to NVS Preferences and Firebase RTDB under devices//diag. Previous boot’s crash record is archived so it survives subsequent boots. The ESP reset reason (esp_reset_reason()) is also captured and stored. This enables remote field diagnostics without physical access to the device.

V3.17

LIS3DH accelerometer support added (Mini V36B / V38 / airlogOne38) The STMicroelectronics LIS3DH 3-axis accelerometer is now supported on compatible hardware variants. It is initialised at startup (±2g, high-resolution, 50 Hz), and its X/Y/Z acceleration data is logged into the CSV track file on each 200 ms sample tick (on Mini variants without the truemove AHRS).

Ground calibration pressure: stored with timestamp, restored on reboot The ground-level reference pressure (Zpressure) and its timestamp are saved to NVS Preferences at calibration time. On reboot, if the stored value is valid and ≤ 3 hours old (compared to the RTC clock), it is automatically restored — avoiding an incorrect altitude baseline after a brief restart at the DZ.

Wind vector calculation added (interpolatewind) Raw winds-aloft data (direction + speed at 16 altitudes in 300 m steps) is now interpolated to 100 m steps using vector (U/V component) interpolation.

Wind forecast appended to CSV track (windwrite) At the end of each jump, if wind data is loaded and current, the interpolated winds-aloft profile (altitude, direction, speed, temperature at 100 m steps up to 4800 m) is appended to the jump’s CSV track file.

Firebase timeout checks added Timeout guards have been added around Firebase RTDB write operations to prevent the device from hanging indefinitely on a slow or failed connection.

BlenderM font used on AltiScreen The altimeter display screen now uses the monospaced BlenderM font for improved readability of the altitude value.

V3.171

GPS dynamic model fixed to Airborne <1G . This optimises the receiver’s navigation engine for aerial dynamics, improving fix stability and velocity accuracy from exit through canopy.

Removed GeoAPIfy reverse-geocode call for logPlace The on-device API call to resolve a jump’s GPS coordinates to a city/DZ name has been removed. The Drop Zone name is now populated by the companion app directly from the central DZ database. This eliminates the Geoapify external dependency during logbook sync and reduces upload time. The logPlace field remains in the RTDB schema (written as empty string) for compatibility.

Applies to all hardware variants: airlogOne32, airlogOne35, airlogOne36, airlogOne38, airlogOne-Mini V31 – V38.