miro
Cargo
Configuration
1. Overview
miro Cargo is configured with LoRaWAN® downlinks which are transmitted to port 220. The payload of a configuration downlink corresponds to a so-called AT command. After one or more configuration downlinks are received, a reset command needs to be transmitted to the miro Cargo such that the configuration is stored in non-volatile memory and an a reset is triggered. After this reset, the miro Cargo uses the new configuration.
2. Downlink commands
2.1. Overview
The following configuration downlinks are available:
| Command | Description | Default value | Min value | Max value | Unit |
|---|---|---|---|---|---|
|
Reset the MCU |
- |
- |
- |
- |
|
Moving interval |
120'000 |
60'000 |
4'294'967'295 |
ms |
|
Steady interval |
21'600'000 |
60'000 |
4'294'967'295 |
ms |
|
Status message interval |
21'600'000 |
600'000 |
4'294'967'295 |
ms |
2.2. ATZ
Resets the MCU. If the configuration has been changed, the new configuration is stored in non-volatile memory and applied after the reset.
2.3. AT+GPSHOLD
Sets the GPS hold time, also known as moving interval. The GPS hold time inhibits further GPS fix acquisition for a certain time period. This setting is used when GPS fixes are triggered by the accelerometer. A first accelerometer event will trigger GPS fix acquisition immediately. Further accelerometer events will be ignored until after the hold time interval. However, a flag will be set in this case, so that the next GPS fix acquisition will immediately start right after the hold time interval.
AT+GPSHOLD=300000
2.4. AT+GPSCYC
Sets the regular GPS fix cycle time, also known as steady interval. The GPS cycle time is used when GPS fixes are triggered by the timer. The GPS cycle time is the time between two consecutive GPS fix acquisitions. The GPS cycle time is running independently from accelerometer events.
AT+GPSCYC=3600000
2.5. AT+STACYC
Sets the regular status interval. Status messages are enabled by default, all sensors are read out when the regular status interval expires. Please refer to the payload documentation for more information about the generated status message. To save battery life, keep it at a large value.
AT+STACYC=43200000
3. Downlink responses
For every downlink packet, an uplink packet is scheduled containing the corresponding AT response code. The following response codes are available:
| Response code | Hexadecimal | Description |
|---|---|---|
|
|
Command executed successfully |
|
|
Command was outside of the valid range |
|
|
Command execution failed |
4. Downlink command format
The payload of an AT command downlink corresponds to an ASCII encoded AT command with zero-termination. Zero-termination means that 00 needs to be added at the very end of the hexadecimal representation of the AT command. The last line of the following examples corresponds to the payload of the respective downlink.
Example - Changing the moving interval to 3 minutes (180 seconds):
AT command as ASCII string: AT+GPSHOLD=180000
AT command as hex: 41542B475053484F4C443D313830303030
AT command as hex with zero termination: 41542B475053484F4C443D31383030303000
Example - Resetting the device:
AT command as ASCII string: ATZ
AT command as hex: 41545A
AT command as hex with zero termination: 41545A00
After changing a configuration parameter via downlink, the miro Cargo needs to be reset such that the configuration is loaded. This is done by sending the downlink command ATZ on port 220.
|
For every downlink packet, an uplink packet is scheduled containing the corresponding AT response code (usually AT_OK or 41545F4F4B in hexadecimal representation). If both the configuration change and the reset are queued simultaneously on the LoRaWAN® network server, the configuration is applied the fastest way possible. The reason for this being that the configuration change triggers an uplink message (usually AT_OK) which opens another downlink slot for the reset command to be received immediately.