Versions Compared

Old Version 48

changes.mady.by.user Theodor Rohde

Saved on

compared with

New Version Current

changes.mady.by.user Theodor Rohde

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TypeData (example)Data
config


Code Block
{
  "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


Code Block
{
	"d": { 
		"app": "app-firmware-1.x.x-mcuboot-slot1.hex",
	 	"boot": "app-boot-nrf9160-sec-TZ2-1.8.2-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.

  • app: Application firmware file ("device.app")
  • boot: Associated matching secure boot firmware file ("device.boot")

(info) 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!

fw


Code Block
{
	"d": { 
		"app": "app-firmware-1.x.x-mcuboot-slot1.hex" 
	}, 
	"q": "fw"
}

The JSON Format might be subject to change in future releases.

Only the application firmware file to be downloaded by the device.

  • app: Application firmware file ("device.app")

(warning) This is the faster (since less data has to be downloaded by the device) 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.

If in doubt use the command above that updates both firmware images.



fw


Code Block
{
	"d": { 
		"boot": "app-boot-nrf9160-sec-TZ2-1.8.2-mcuboot-slot1.hex" 
	}, 
	"q": "fw"
}

The JSON Format might be subject to change in future releases.

Only secure boot firmware to be downloaded by the device.

  • boot: Associated matching secure boot firmware file ("device.boot")


If in doubt use the command above that updates both application + secure boot firmware images.

fw
Code Block
{
	"d": { 
		"mfw": "mfw_nrf9160_update_from_1.3.2_to_1.3.4.bin" 
	}, 
	"q": "fw"
}

The JSON Format might be subject to change in future releases.

Delta modem firmware update to be downloaded by the device.

  • mfw: Associated matching delta modem firmware file provided by Nordic Semiconductor ("device.modem")

Delta modem firmware updates can only be performed in small version steps. Please consult Lobaro for available options.

Only newer Lobaro firmware support this type of update, e.g. for wmbus GW V3 from v0app-nrf9160-wmbus+0.24.0 + onwards.

lorawan


Code Block
{
  "data": "scmodeDurSec=15",
  "type": "ascii",
  "fPort": 128
}


to insert a lorawan downlink over the platform a json object with the fiels type, data and fPort needs to be added.

TYPE: choose "base64", "hex" or "ascii" depending on the data content.

data needs to contain the contet that is send to the device over the network server.

Details about data and the right fPort for Lobaro Devices can be found under: LoRaWAN Downlink Config

ATTENTION: the downlinks will only be send if you have a default LoraWan Server defined under Integrations or the device is assigned to a loranwan server integration!

fw


Code Block
{
  "q": "reboot"
}

The JSON Format might be subject to change in future releases.


fw


Code Block
{
  "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


Code Block
{
	format: "ASCII",
	data: "ascii-downlink-payload"
}

Lobaro NB-IoT Devices:

Config change:

Code Block
{
  "format": "cbor"
  "data": {
    "d": {
      "cmodeDurSec": 123
    },
    "q": "config"
  }
}

reboot:

Code Block
{
  "format": "cbor"
  "data": {
       "q": "reboot" 
  }
}


Raw downlink data, with tyoe ASCII currently only supported for Tektelek devices.


Format: "cbor": meant for Lobaro Devices. The content JSON Object of "data" is marshaled to cbor and send to the device.


...