Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Mengting Qiu on 2025/06/04 18:42
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -241,7 +241,6 @@ 241 241 * Go to your application's page and click on the **End devices** in the left menu. 242 242 * On the End devices page, click on **+ Register end device**. Two registration options are available: 243 243 244 - 245 245 ==== 3.2.1.1 Using the LoRaWAN Device Repository ==== 246 246 247 247 ... ... @@ -303,7 +303,7 @@ 303 303 === 3.2.2 Joining === 304 304 305 305 306 -On the Device's page, click on **Live data** tab. The Live data panel for your device will display.305 +On the end device's page (in this case, lt-22222-l), click on **Live data** tab. The Live data panel for your device will display. Initially, it is blank. 307 307 308 308 Now power on your LT-22222-L. The **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack network server. The **TX LED** will be on for **5 seconds** after joining the network. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. 309 309 ... ... @@ -314,14 +314,14 @@ 314 314 === 3.2.3 Uplinks === 315 315 316 316 317 -After successfully joining, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes.316 +After successfully joining, the device will send its first **uplink data message** to The Things Stack application it belongs to (in this example, it is **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes. 318 318 319 -Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object. 318 +Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the **decode_payload {}** JSON object. 320 320 321 321 [[image:lt-22222-ul-payload-decoded.png]] 322 322 323 323 324 -If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > your application > End devices** > **your end device** > **Payload formatters** > **Uplink**. Then select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes. 323 +If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > [your application] > End devices** > [**your end device]** > **Payload formatters** > **Uplink**. Then select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes. 325 325 326 326 {{info}} 327 327 The Things Stack provides two levels of payload formatters: application level and device level. The device-level payload formatters **override **the application-level payload formatters. ... ... @@ -330,7 +330,7 @@ 330 330 [[image:lt-22222-ul-payload-fmt.png]] 331 331 332 332 333 -We alsohave a payload formatter that resolves some decoding issues present inthe Device Repository formatter. You can add it under the Custom JavaScript formatter. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]:332 +We have written a payload formatter that resolves some decoding issues present in The Things Stack Device Repository payload formatter. You can add it under the **Custom JavaScript formatter**. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]: 334 334 335 335 (% class="wikigeneratedid" %) 336 336 [[image:lt-22222-l-js-custom-payload-formatter.png]] ... ... @@ -339,7 +339,7 @@ 339 339 === 3.2.4 Downlinks === 340 340 341 341 342 -When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.341 +When the LT-22222-L receives a downlink message from the LoRaWAN Network Server, the **RX LED** turns on for **1 second**. 343 343 344 344 345 345 == 3.3 Working Modes and Uplink Payload formats == ... ... @@ -1495,53 +1495,64 @@ 1495 1495 DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which DO1 pin takes no action, DO2 pin is set to high, and DO3 pin is set to low. 1496 1496 ))) 1497 1497 1498 - 1499 1499 ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ==== 1500 1500 1501 1501 1502 - *(% style="color:#037691" %)**AT Command:**1500 +(% style="color:#037691" %)**AT Command:** 1503 1503 1504 -There is no AT Command to control the Relay Output 1502 +There is no AT Command to control the Relay Output. 1505 1505 1506 1506 1507 - *(% style="color:#037691" %)**Downlink Payload(prefix 0x03):**1505 +(% style="color:#037691" %)**Downlink Payload** 1508 1508 1509 -(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Sets RO1/RO2 output 1507 +(% border="2" style="width:500px" %) 1508 +|(% style="width:113px" %)**Prefix**|(% style="width:384px" %)0x03 1509 +|(% style="width:113px" %)**Parameters**|(% style="width:384px" %)((( 1510 +**RO1_status** : 1 byte in hex 1510 1510 1512 +00: Close 1511 1511 1512 -((( 1513 -If the payload is 0x030100, it means setting RO1 to close and RO2 to open. 1514 -))) 1514 +01: Open 1515 1515 1516 -((( 1517 -00: Close , 01: Open , 11: No action 1516 +11: No action 1518 1518 1519 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %) 1520 -|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2** 1521 -|03 00 11|Open|No Action 1522 -|03 01 11|Close|No Action 1523 -|03 11 00|No Action|Open 1524 -|03 11 01|No Action|Close 1525 -|03 00 00|Open|Open 1526 -|03 01 01|Close|Close 1527 -|03 01 00|Close|Open 1528 -|03 00 01|Open|Close 1529 -))) 1530 1530 1531 - (%style="color:red" %)**Thedevicewilluplink a packetif thedownlinkcodeexecutes successfully.**1519 +**RO2_status** : 1 byte in hex 1532 1532 1521 +00: Close 1533 1533 1523 +01: Open 1524 + 1525 +11: No action 1526 +))) 1527 +|(% style="width:113px" %)**Payload format**|(% style="width:384px" %)<prefix><RO1_status><RO2_status> 1528 +|(% style="width:113px" %)**Example**|(% style="width:384px" %)((( 1529 +(% border="2" %) 1530 +|=Payload|=RO1|=RO2 1531 +|03 00 11|Open|No action 1532 +|03 01 11|Close|No action 1533 +|03 11 00|No action|Open 1534 +|03 11 10|No action|Close 1535 +|03 00 00|Open|Open 1536 +|03 01 01|Close|Close 1537 +|03 01 00|Close|Open 1538 +|03 00 01|Open|Close 1539 + 1540 +(% style="color:red" %)**The device will transmit an uplink packet if the downlink payload is executed successfully.** 1541 +))) 1542 + 1534 1534 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1535 1535 1536 1536 1537 1537 Controls the relay output time. 1538 1538 1539 -* (% style="color:#037691" %)**AT Command:** 1540 1540 1549 +(% style="color:#037691" %)**AT Command:** 1550 + 1541 1541 There is no AT Command to control the Relay Output 1542 1542 1543 1543 1544 - *(% style="color:#037691" %)**Downlink Payload (prefix 0x05):**1554 +(% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1545 1545 1546 1546 (% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Sets RO1/RO2 relays with time control 1547 1547 ... ... @@ -2116,7 +2116,7 @@ 2116 2116 [[image:thingseye-events.png]] 2117 2117 2118 2118 2119 -* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 2129 +* To view the **JSON payload** of a message, click on the **three dots (...)** in the **Message** column of the desired message. 2120 2120 2121 2121 [[image:thingseye-json.png]] 2122 2122 ... ... @@ -2127,12 +2127,16 @@ 2127 2127 If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 2128 2128 2129 2129 2130 -==== 3.5.2.4 Creatinga Dashboardto DisplayandAnalyzeLT-22222-L Data ====2140 +==== 3.5.2.4 Viewing sensor data on a dashboard ==== 2131 2131 2132 2132 2133 -This willbe added soon.2143 +You can create a dashboard with ThingsEye to visualize the sensor data coming from the LHT65N-VIB. The following image shows a dashboard created for the LT-22222-L. See **Creating a dashboard** in ThingsEye documentation for more information. 2134 2134 2135 2135 2146 + 2147 +[[image:lt-22222-l-dashboard.png]] 2148 + 2149 + 2136 2136 == 3.6 Interface Details == 2137 2137 2138 2138 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===