Release Notes
AT3 v1.4.1
New features
-
Power update event. A new event
type_power_update(class 4, type 4) is raised when the remaining battery capacity is calculated and/or the USB state is updated. See Event manager. -
Data buffering timeout event. A new event
type_core_db_timeout(class 9, type 23) is raised on a data buffering transmission timeout. See Event manager. -
PSM information in the network notification. The network notification now reports the
PSM active timeandPSM TAUwhen the cellular network is active and configured for low power mode. See Notification class 4: network. -
BLE battery and temperature characteristics. The values of the BLE battery and temperature characteristics are now updated.
Bug fixes
-
Cellular connectivity stuck after airplane mode. When attempting to put the modem in airplane mode to release the antenna to probe the LoRaWAN network, if the modem did not confirm the airplane mode as expected, the cellular connectivity could remain stuck.
-
Network stuck in backup connecting state. The
net_reconnection_spacing_xxparameters did not recover the network from this state. -
BLE access race condition. When using a short duration for the BLE scan parameters and writing the configuration in the flash, the device got stuck and the watchdog reset it.
-
Buffered messages lost after a LoRa settings change. Changing a parameter of the LoRaWAN group caused the loss of the buffered messages.
-
LoRa network not resuming. The LoRaWAN network failed to resume when the maximum number of probing attempts was set to 0.
-
Weekly system time update. The weekly system time update did not work.
-
Wrong UTC time from the cellular modem. The GM02S cellular modem could provide a wrong UTC time.
-
Rolling crash with two bonded devices. Bonding two devices could cause a rolling crash.
-
Cellular aggregation timer after shutdown notification. The cellular aggregation timer was not correctly restored after sending the shutdown notification.
AT3 v1.4.0
New features
-
Improved FUOTA network interactions. Network management has been enhanced to support cellular FUOTA in different network configurations. Please refer to the Binary file download section.
-
Remote command for triggering FUOTA. A new downlink command
FUOTA requesthas been added to remotely trigger a FUOTA and corresponding responsesFUOTA response, and notifications have been added. -
Battery management. Power management has been enhanced to handle battery charging and replacement more efficiently: Power management.
-
Firmware update over the CLI. The device firmware update (DFU) can now be performed through the CLI.
Bug fixes
-
Device reset when erasing parameters over BLE. Erasing the configuration while connected over BLE with very fast connection parameters reset the device without erasing the configuration.
-
NULL character in BLE string parameters. A NULL character was returned when reading a string parameter through the BLE characteristic.
-
Rolling reset with a heartbeat period of 0. When the heartbeat period was set to 0 and the heartbeat notification was enabled, the device entered a rolling reset loop.
-
Configuration CRC error. Under certain conditions, the device reported a wrong CRC after a configuration update.
-
Empty string parameters over BLE. Reading an empty string parameter or writing an empty string over BLE returned an error.
Known issues
-
Cellular stop working. When attempting to put the modem in airplane mode to release the antenna to probe the LoRaWAN network, if the modem does not confirm the airplane mode as expected, the cellular connectivity may remain stuck. Fixed in v1.4.1.
-
Network stuck in backup connecting state. The net_reconnection_spacing_xx does not seem to recover from this state. Fixed in v1.4.1.
-
BLE access race condition. When using short duration for BLE scan parameters and writing config in the flash the device stucks and the watchdog resets it. Fixed in v1.4.1.