Skip to main content
Version: Firmware AT3 v1.6

Release Notes

AT3 v1.6.1​

Bug fixes​

  • Geolocation on shock or temperature event. Geolocation was not triggered by a shock or by a low/high temperature event.

  • Cellular modem suspend. Suspending the cellular modem could fail due to a race condition during the system time refresh.

  • GNSS chip stuck in power-on state. The MT3333 GNSS chip could remain stuck in the power-on state.


AT3 v1.6.0​

  • BLE presence detection. A new BLE presence detection feature is available. Two new parameters ble_scan_presence_period and ble_scan_presence_max_time control the detection window. See Configuration.

  • Shock notification GADD index. The GADD index in the shock notification payload has been extended from 1 byte to 4 bytes, allowing a wider range of index values.

  • BLE scan — 100 beacons support. The ble_scan_nb_beacons parameter maximum has been increased from 20 to 100 beacons.

  • BLE beacon advertising intervals. The minimum value for ble_beacon_fast_adv_interval and ble_beacon_slow_adv_interval has been raised from 20 ms to 40 ms.

  • Cellular LPM recovery timeout. A new cell_lpm_recovery_timeout parameter allows configuring an automatic recovery timeout from low-power mode. See Configuration.

Bug fixes​

  • SOS mode instability. When a second geolocation trigger was received during an ongoing SOS geolocation acquisition, the triggers were merged and the SOS trigger was incorrectly dropped, preventing the device from entering SOS mode.

  • BLE beacon not restarting after bond removal. After a BLE connection ended and the bond was cleared, the device continued advertising but did not resume QUUPPA beacon mode. A magnet trigger was required to relaunch advertisement for the le_cnx_adv_duration period and return to QUUPPA mode.

  • Cellular sockets FSM stuck in starting state. When the modem failed (driver busy or not responding) during socket initialisation, the failure event was not handled in the starting state, leaving the sockets FSM permanently stuck and preventing any further cellular communication.

Known issues​

  • Geolocation on shock or temperature event. Geolocation is not triggered by a shock or by a low/high temperature event. Fixed in v1.6.1.

  • Cellular modem suspend. Suspending the cellular modem may fail due to a race condition during the system time refresh. Fixed in v1.6.1.

  • GNSS chip stuck in power-on state. The MT3333 GNSS chip may remain stuck in the power-on state. Fixed in v1.6.1.