There are different downlink Types to be queued:
Downlink Types
| Type | Data (example) | Data |
|---|---|---|
| config | {
"d": {
"mFilter": "LOB",
"listenCron": "0 0/20 * * * *",
"cmodeDurSec": "600"
},
"q": "config"
}
The JSON Format might be subject to change in future releases. | The config values to be updated. |
| fw | {
"d": {
"app": "app-firmware-1.x.x-slot1.hex",
"boot": "app-boot-nrf9160-sec-TZ2-1.8.0-mcuboot-slot1.hex"
},
"q": "fw"
}
The JSON Format might be subject to change in future releases. | The application + secure boot firmware files to be downloaded by the device.
|
| fw | {
"d": {
"app": "app-firmware-1.x.x-slot1.hex"
},
"q": "fw"
}
The JSON Format might be subject to change in future releases. | The application firmware file to be downloaded by the device.
If in doubt use the command above that updates both firmware images. |
| reboot | {
"q": "reboot"
}
The JSON Format might be subject to change in future releases. | |
| comment | {
"d": "ASCII string to print to log",
"q": "comment"
}
The JSON Format might be subject to change in future releases. | ASCII String that will be printed to device's Log. |
| raw | {
format: "ASCII",
data: "ascii-downlink-payload"
}
| Raw downlink data, currently only supported for Tektelek devices. |
The firmware that works for remote firmware updates is uploaded to the platform by Lobaro. This is a different version than the one used via the USB adapter!
This is the faster alternative of the firmware update command above and can be used if the needed "device.boot" firmware is already present in the device. The appropriate boot firmware version for a particular application firmware can be obtained from Lobaro. The currently installed boot firmware can be read from the device properties in the Lobaro platform.Raw Downlinks
Tekelek
Scheduling TCP/IP downlinks for Tekelek devices.
You can schedule a downlink with the following content:
Type: raw
Data:
{
format: "ASCII",
data: "ascii-downlink-payload"
}
Currently only the format "ASCII" is supported.