This is the release page for the Ezurio RS26x product family Codec for TTI.
This repository includes the following files.
| File Name | Description |
|---|---|
| Downlink_TTI.js | Downlink Encoder with commented JavaScript code. |
| Downlink_TTI_Uncommented.js | Downlink Encoder with comments removed. |
| Uplink_TTI.js | Uplink Decoder with commented JavaScript code. |
| Uplink_TTI_Uncommented.js | Uplink Decoder with comments removed. |
Uncommented files are intended for integration within TTI. Commented versions are provided for developer reference. A character count limitation enforced by TTI results in file size needing to be minimized, with comments being included in the character count.
Codec integration is performed on a per device basis. From within the TTI instance user interface, the Application where the device to add codec support for resides should be navigated to. The device should then be selected from the 'End devices' option and then the 'Payload formatters' tab selected.
Within the 'Payload formatters' tab, 'Uplink' and 'Downlink' tabs are available for selection. The 'Uplink' tab is selected for determining the 'Payload formatter' of uplink messages and the 'Downlink' tab selected for downlink messages.
The sequence of steps to arrive at the 'Uplink' 'Payload formatters' tab is shown below.
The 'Formatter type' dropdown should be set to 'Custom Javascript formatter', then the code from the appropriate Uncommented codec file pasted into the 'Formatter code' pane as shown below.
Once the code has been pasted into the 'Formatter code' pane, towards the foot of the page, 'Save changes' must be clicked before navigating away from the page as shown below.
The steps described above must be repeated for each codec type being installed.
Following integration of the Uplink decoder, messages received from the device are decoded automatically, with the results visible in the 'Live data' tab associated with the device as shown below.
From the 'Messaging' tab associated with the device, 'Schedule downlink' should be selected, then the 'Payload type' set to JSON, as shown below. This allows messages to be described in JSON format. The RS26x LoRa Protocol specification should be referred to for details of the expected JSON format.
The message to be sent to the device should be entered in JSON format in the 'Payload' pane as shown below.
Once entered, the 'Schedule downlink' button at the foot of the page should be clicked as shown below.
The queued downlink is sent to the device on the next available receive window following an uplink from the device. Decoded downlink data and the decoded response appears as shown below in the 'Messaging' tab associated with the device.
