Skip to main content
Version: Firmware AT3 v1.6

Functioning

High level features​

This section describes the high-level features of AT3 V1.6 release.

  • Main LoRaWAN features

    • Class A
    • Support for all main regional parameters (EU, AS, IN, AU, US)
    • Network access: OTAA
    • Network monitoring (Link check, Reset on prolonged network loss)
    • Multiple transmissions strategies (configurable ADR, Dual transmissions)
    • Configurable confirmed uplinks
    • Uplink queue (Up to 40 messages)
    • Downlink messages processing
    • Configurable heartbeat
    • Synchronization to network time
  • Main Cellular LPWAN features

    • Support for NB-IoT and LTE-M
    • Support for physical SIM and eSIM
    • Support for PSM and eDRX modes
    • Uplink queue (Up to 40 messages)
    • End to end encryption and authentication
    • Configurable heartbeat
    • Network time synchronization
    • Uplink message agregation for power consumption optimization
  • Geolocation

    • Configurable multi-technology (GNSS, A-GNSS, LP-GNSS, BLE, WiFi) geolocation profiles based on triggers (button press, motion and so on)
    • Flexible technologies scheduling
    • BLE scan using beacon type (Eddystone, Altbeacon, iBeacon) & beacon identifier filtering
    • Configurable timing for geolocation
  • SOS support

    • Configurable user interface for SoS
    • Configurable geolocation
  • BLE connectivity

    • Single bonding support
    • Passkey authentication support
    • Export standard characteristics (temperature, battery and so on)
    • Export vendor specific characteristics (parameters, mode change and so on)
    • Notification support (send notifications to mobile phone)
    • BLE firmware update over the air
    • MCU firmware update over the air
    • CLI over BLE
    • Find me support
    • BLE presence detection
  • BLE beaconing

    • Configurable beacon transmission (Eddystone, Altbeacon, iBeacon & Quuppa)
    • Configurable TPX power
  • Recovery beacon (EU868 and US915 regions only)

    • Device localization using a dedicated finder device or a network of proximate devices, see Recovery beacon
  • Device management

    • Command Line Interface (CLI) (support multiple commands, two access levels)
    • Log facility (per module log)
    • Accelerometer management (motion and shock detection)
    • Temperature management (permanent storage of the min/max values, specific actions taken when thresholds reached)
    • Battery management (primary vs rechargeable batteries, remaining capacity measurement and estimated consumption)
    • Dynamic configuration parameters management (permanent storage, configuration files and accesible from CLI and network)
    • Dedicated startup modes
    • Firmware update over USB, BLE, and cellular network (FUOTA)

Startup and Shutdown​

Startup​

Depending on the ordering option (done by the factory), the device can be:

  • Shipping Mode: low-power state designed to preserve the batteries. LPWAN networking is disabled. To live this mode a manual action is required (button press, or a magnet presence).
  • Network activation Mode: the device is waiting for a network activation (LoRa joined) before actually starting (geolocation disabled).
  • Automatic start Mode: the device starts as soon as it is powered (geolocation enabled)
tip

The Network activation Mode works as follow:

  • The device sends periodic LoRaWAN join uplinks (with exponential back-off retries, so energy usage remains low)
  • BLE connectivity is activated (so a user may use the BLE command line interface for configuration). After the device has successfully joined a network, the application starts automatically. This mode is useful for consumer products that does not expect a humain action to activate the device. Once the device has been activated a first time, it remains active forever (will not stop even if LoRaWAN connectivity is lost and the device goes to joining mode again). This mode can only be used with LoRaWAN as primary network.

Shutdown​

Usuelly, devices equipped with primary batteries can be shutdown only via network commands. However, it is possible to stop the device by configuring a button or magnet. Similarly, devices using rechargeable batteries can be stopped using a dedicated button configuration. Such devices are automatically shutdown in case of critical low battery.

In the off state, the following features are disabled:

  • BLE beaconing
  • BLE connectivity
  • Recovery beacon
  • Accelerometer
  • Geolocation (ongoing acquisitions are cancelled)
  • Network (LoRaWAN and cellular)

Geolocation​

This section describes the high level geolocation features of the device. For more details, please refer to Geolocation manager.

GNSS​

The device features a multi-constellation GNSS chip compatible with GPS, GLONASS, Galileo, and BeiDou systems. When utilizing GNSS for geolocation, the device's uplink payload includes its GPS coordinates, along to the estimated location accuracy, heading, and speed. It's important to note that GNSS position acquisition and tracking are energy-intensive processes. To manage this, the AT3 multi-technology geolocation engine offers various configuration parameters. These settings allow for fine-tuning and balance the trade-offs between energy consumption, fix latency and accuracy. For more information, please refer to GNSS manager.

Low-Power GNSS​

The device supports Abeeway proprietary Low-Power GNSS (LP-GNSS). With LP-GNSS, the onboard GNSS processing is limited to the acquisition of GNSS pseudoranges. A patented technology combines pseudoranges, network time and cloud based processing to obtain a fix. LP-GNSS has an extremely low power consumption compared to full GNSS and provides faster time-to-first fix (TTFF) in case of bad wheather conditions or during indoor-outdoor transitions. Note that LP-GNSS has lower accuracy than on-board made GNSS fix. LP-GNSS is optimal for use with a vehicle in motion (high accuracy not needed), while on-board made GNSS fix may be preferred for on-demand fixes. For more information, please refer to GNSS manager.

tip

This feature requires a subscription to ThingPark X Location Engine (TPX-LE).

WiFi indoor/outdoor geolocation​

The device supports scanning of WiFi MAC addresses which are reported to the customer's business application or ThingPark location. The WiFi MAC addresses can be used for indoor positioning using a network-based geolocation service.

tip

This feature requires a subscription to ThingPark X Location Engine (TPX-LE), or a 3rd party WiFi location solver. For more information, please refer to Geolocation Manager.

BLE indoor geolocation​

The device supports scanning of BLE MAC addresses or a part of the advertisement which are reported to the customer's business application or ThingPark location. This information can be used for indoor positioning using ThingPark location.

tip

This feature requires a subscription to ThingPark X Location Engine (TPX-LE), or a 3rd party WiFi location solver. For more information, please refer to BLE scan.

BLE beaconing​

The device supports BLE advertising of standard beacon types (Eddystone, iBeacon, Altbeacon & Quuppa). Support for Quuppa beaconing enables precise location of Abeeway trackers through Quuppa angle-of-arrival location infrastructure. The beacon identifier can be configured using the firmware parameters. For more details on BLE beaconing, please refer to BLE group.

User interfaces​

Depending on the device model, the application firmware user interface controls a buzzer/speaker, LEDs, and buttons. Please refer to section user interface for more details.

SOS​

SOS mode may switch the device to a specific geolocation. Once this mode is activated, the behavior is the following:

  • The device may send (if configured for) a SOS-on notification payload.
  • The device may start a specific geolocation (based on the configuration).
  • The device's user interface can be configured.
  • The device may send (if configured for) a SOS-off notification payload.
  • This mode can be enter from a downlink command.

Motion detection​

The device embeds a three axes accelerometer, which detects accelerations. It generates motion events (if configured for). It is fully configurable. The generated event can be sent along to notifications via the network.

For more information, please refer to Accelerometer.

Shock detection​

This feature enables the reporting of the shocks detected by the device. The shock detection threshold is configurable.

For more information, please refer to Accelerometer.

Notification Messages​

These uplink messages are sent by the device informing the application server about specific events. These events can be system related (low battery, temperature, ...) or application specific (SOS, motion, network, ...).

Refer to the section Notifications for the format of the notification uplinks.

Temperature monitoring​

The device monitors periodically the temperature. The period is configurable as well as the high and the low thresholds. Once these thresholds reached, notifications may be sent if configured for. The min and max temperatures are stored in a non volatile memory.

Power management​

The device periodically reports its battery level and sends a system notification when detecting low battery level if configured for.

LoRaWAN and Cellular network management​

The device firmware supports the LoRaWAN network and on some devices the cellular network (Combo cellular-LPWAN compact).

The device embedds a network manager which performs:

  • The network connectivity state management.
  • Switching between networks in case of failure.
  • Probing the primary network for recovery purpose.
  • Routing the application messages over the active network.

For more information on network management, please refer to Network manager.