Release Notes

New features

• Uplink frame buffer (only for devices equipped with the optional external flash) Uplinks are buffered in flash memory. In case of packet loss, this lets the back-end request the missing frames through the new get buffered uplinks command.

• Reset by magnet action. A RESET command has been added to the actions that can be assigned to the button events in core_buttonX_map paramters in the system group.

• DevNonce cycling
  As a protection against replay attacks, LoRaWAN requires each JOIN request to use a new DevNonce. For LoRaWAN-only devices, the maximum number of DevNonce values (65,535 in LoRaWAN 1.0.x) is usually sufficient for the lifetime of the device. By default, the LoRa Basics Modem stack stops at the maximum DevNonce value.

  However, for dual-network devices such as the Combo tracker, more frequent rejoin attempts may be required. Starting with AT3 1.3, the device will cycle the DevNonce back to 0 instead of remaining stuck at 65,535.

  These frames are still blocked by the LoRaWAN Network Server (LNS) replay protection, but they can easily be unblocked through the LNS API. Since the application can detect in advance when a device is approaching DevNonce exhaustion, the authorization for cycling can be proactively provided to the LNS.

• File authentication (signed firmware) for remote upgrades
  To comply with the new EU security standard EN 18031, which requires file authentication, all remote firmware upgrade methods now require signed firmware. Local firmware update via USB still supports unsigned images.

  Signed firmware files are identified by the .bin.sign extension added to the firmware filename.

• Firmware update over BLE. In addition to the existing firmware update via USB, it is now possible to upgrade both the application and the BLE firmware through BLE. This is supported by the browser based tool Beehive. This will only work with signed firmware, check that you have the .bin.sign extension.

• Firmware update via LTE. (Experimental only). In this release only CLI trigerred updates are supported.

• Network parameter differentiation according to motion status
  The parameters related to network probing (net_reconnection_spacing, net_main_probe_timeout, lorawan_probe_max_attempts, lorawan_probe_period, cell_cnx_timeout) are now separately tunable for static conditions (_static suffix) or while in motion (_motion suffix). When upgrading the existing parameters get mapped to the _static parameters.

  This improvement reduces network flapping when the device is static in areas without coverage (e.g., underground parking), while making the switch to a backup network more responsive when the device is in motion.

• Parameter lorawan_dl_trigger_period renamed to lorawan_heartbeat_period
  The parameter ID remains unchanged. This renaming improves consistency with the notification flags of parameter 0x0102 core_notif_enable, which includes a heartbeat flag to enable heartbeat messages. The periodicity of these messages is controlled by lorawan_heartbeat_period.

• Shutdown uplink. In case the device shuts down through user action or in a critical low battery condition, the power manager will keep the network up long enough to send a shutdown notification.

Known-issues

AT3 v1.3.0

No known issue yet