LoRa Downlink Commands
- Matthieu Behroozi
LoRa Downlink commands can be sent to a device to change configuration, request position update or activate alert service.
For list of downlink commands please refer to the product Guide.
Note when using Senet LNS:
If the Device is is in Class A, maximum of 3 downlinks can be queued for any one device at a time on Senet, if the device is in Class B only 1 can be scheduled per device.
Time out should be minimum 2x heart beat rate, this is because of the following reasons:
if the Asset + device is operating in Class A, it will open a RX window where the LNS will be able to send the downlink command to the device. On the following uplink from the device, the device will confirm receipt of the downlink which will allow Bluzone to mark the job as complet, if the device is stationary this will be at the next heart beat period. If the time out is set to less then 2x of the heartbeat rate then the command may be correctly received by the device however the downlink job may be marked as timed out if Bluzone did not receive the confirmation within the time out duration.
there is no Senet API to inform Bluzone of downlink failure, Bluzone is monitoring confirmation of receipt of downlink from the Asset+, the Asset+ will sent the confirmation in the next uplink which worst case will be the next scheduled heartbeat.
There are two methods to sending downlink commands to asset+ using Bluzone
Using Device Job Tab to send the command to a single device
using the actions Drop down under beacons tab allows a user to send a downlink to multiple Asset+ devices, this then creates multiple device jobs which can be reviewed under device jobs for a specific beacon.
Device Job:
within Bluzone, follow these steps
select “Beacon” from the Menu bar on the left,
select a Asset+ device that you which to send a downlink command to,
Navigate to “Job” tab along the top menu bar,
Press the “Actions” drop down and select “Downlink command”
Enter the correct PDU, and a timeout in Minutes that equates to a minimum of 2x of the Heart Beat rate
NOTE: Pressing on a Row in the table will provide detailed information for the specific job, such as when the job was schedule and at what time Bluzone received confirmation of the job being complet along with any error message that may be received from the LNS. NOTE that the completion of the job requires the Asset+ device to send a confirmation flag within the next uplink from the device, if the device is not moving it will occurs at the next heart beat period.
Scheduling a downlink to be sent to multiple devices
To mass update a specific setting to multiple devices, select multiple devices you wish to send the command two in the beacons table by ticking the selection box, under the actions drop down select “downlink command.” this will schedule a device job for each selected device to send a downlink to update the configuration of the selected devices. The progress of the job can be reviewed under the “job” tab for each device.
List of Downlink Commands
| Data | Command ID (Unsigned 8 Bits) | Configuration Data | Units | Sample Commands (Default Values) | Config Decimal / ASCII Value | Range | Remarks | |
Type | Length (Bits) | ||||||||
Alert Service | Debug Tones Activation/Deactivation | 0x00 | Unsigned | 4 |
| 0010 | 1 | 00:Deactivate |
|
Alert Start/Stop | 0x01 | Unsigned | 4 |
| 0110 | 1 | 00:Deactivate | Starting the Alert service triggers a switch in LoRaWAN to class B and which will revert back when the button on the board is pressed. Else it will remain in the same Class | |
Buzzer Duty Cycle | 0x02 | Unsigned | 16 | mS | 0200FA | 250 | 0~65535 |
| |
Buzzer On Frequency | 0x03 | Unsigned | 16 | Hz | 030EA6 | 3750 | 0~65535 |
| |
Buzzer Off Frequency | 0x04 | Unsigned | 16 | Hz | 04128E | 4750 | 0~65535 |
| |
Alert Duration | 0x05 | Unsigned | 16 | S | 05012C | 300 | 0~65535 |
| |
Motion Engine | Config DBR period | 0x10 | Unsigned | 8 | Hours | 1018 | 24 | 1~255 |
|
Accelerometer Threshold | 0x11 | Unsigned | 8 |
| 1109 | 9 | 0~10 |
| |
Accelerometer Activity Window | 0x12 | Unsigned | 8 |
| 1214 | 20 | 1~255 |
| |
Accelerometer Activity Threshold | 0x13 | Unsigned | 8 |
| 130F | 15 | 0~255 |
| |
GNSS Max Lock Timeout | 0x14 | Unsigned | 8 | Minutes | 140F | 15 | 1~25 |
| |
DOP Threshold | 0x15 | Unsigned | 8 |
| 150A | 10 | 1.0~10.0 | 150A= DOP 1 | |
GNSS Forced Uplink | 0x16 | Unsigned | 4 |
| 1610 | 1 | 00:Deactivate |
| |
BLE Scan Forced Start and Send Uplink | 0x17 | Unsigned | 4 |
| 1710 | 1 | 00:Deactivate | When triggered, the device will search for any reference tags in range and if found, there will be Tag data uplinks and if not it will switch to GNSS location retrival | |
Motion Stationary to Moved | 0x18 | Unsigned | 16 |
| 180001 | 1 | 0~65535 |
| |
Motion Moved to Stationary | 0x19 | Unsigned | 16 |
| 190384 | 900 | 0~15240 |
| |
BLE | BLE Advertising Name | 0x20 | String | 64 |
| 2053656E7365412B00 | SenseA+ |
| Make sure to append '00' at the end |
BLE Set Gain | 0x21 | Signed | 8 | dBm | 21F4 | -12 | -40dBm |
| |
BLE Beacon Rate | 0x22 | Unsigned | 16 | mS | 222710 | 10000 | Off: 0 | 222710=10sec (2710 is hex for 10,000) | |
BLE Enable Reference Tag Scan | 0x23 | Unsigned | 4 |
| 2310 | 1 | 00:Deactivate |
| |
BLE Scan Window Length | 0x24 | Unsigned | 16 | mS | 242710 | 10000 | 1000~65535 |
| |
BLE RSSI threshold | 0x25 | Signed | 8 | dBm | 25B5 | -75 | -128~127 |
| |
BLE Set Reference Tag Filter Name or UUID | 0x26 | Unsigned | 128 |
| 264F6D6E692D494400 | Omni-ID |
| Make sure to append '00' at the end | |
| BLE Advertising Type | 0x27 | Unsigned | 1 |
| 2700 | 0 | 0:Default advertising |
|
LoRaWAN | LoRaWAN Enable/Disable | 0x30 | Unsigned | 4 |
| 3010 | 1 | 00:Deactivate |
|
LoRaWAN Maximum Datarate Set | 0x31 | Unsigned | 8 |
| 31FF | 5~255:ADR | 0:DR0 |
| |
LoRaWAN Class | 0x32 | Unsigned | 4 |
| 3200 | Class A | 00: Class A |
| |
LoRaWAN Ping Slot period | 0x33 | Unsigned | 8 |
| 3307 | 7 | 0:SMTC_MODEM_CLASS_B_PINGSLOT_1_S |
| |
LoRaWAN Class B timeout & switch to Class A | 0x34 | Unsigned | 8 | Minutes | 3408 | 8 | 3 - 255 |
| |
LoRaWAN Confirmed Uplinks Enable/Disable | 0x35 | Unsigned | 4 |
| 3510 | 1 | 00:Deactivate |
| |
LoRaWAN Sub-band Hopping Enable/Disable | 0x36 | Unsigned | 4 |
| 3610 | 1 | 00:Deactivate | Enabling this allows the uplinks to communicate in unique and random channels where the sub-bands are hopping sequencially | |
Device | Tag Status: Awake / Sleep mode | 0x40 | Unsigned | 4 |
| 4010 | 1 | 00:Sleep |
|
|
|
|
|
|
|
|
|
| |
Hardware | Button press behavior | 0x50 | Unsigned | 4 |
| 5000 | 1 | 00: Standard btn press |
|
|
|
|
|
|
|
|
| ||