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,6 +241,7 @@ 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 + 244 244 ==== 3.2.1.1 Using the LoRaWAN Device Repository ==== 245 245 246 246 ... ... @@ -302,7 +302,7 @@ 302 302 === 3.2.2 Joining === 303 303 304 304 305 -On the e nd 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.306 +On the Device's page, click on **Live data** tab. The Live data panel for your device will display. 306 306 307 307 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. 308 308 ... ... @@ -313,14 +313,14 @@ 313 313 === 3.2.3 Uplinks === 314 314 315 315 316 -After successfully joining, the device will send its first **uplink data message** to TheThings 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.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. 317 317 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.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. 319 319 320 320 [[image:lt-22222-ul-payload-decoded.png]] 321 321 322 322 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.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. 324 324 325 325 {{info}} 326 326 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. ... ... @@ -329,7 +329,7 @@ 329 329 [[image:lt-22222-ul-payload-fmt.png]] 330 330 331 331 332 -We have writtena payload formatter that resolves some decoding issues present inTheThings StackDevice Repositorypayloadformatter. 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]]:333 +We also have a payload formatter that resolves some decoding issues present in the 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]]: 333 333 334 334 (% class="wikigeneratedid" %) 335 335 [[image:lt-22222-l-js-custom-payload-formatter.png]] ... ... @@ -338,7 +338,7 @@ 338 338 === 3.2.4 Downlinks === 339 339 340 340 341 -When the LT-22222-L receives a downlink message from the LoRaWAN Network Server, the **RX LED** turns on for **1 second**.342 +When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. 342 342 343 343 344 344 == 3.3 Working Modes and Uplink Payload formats == ... ... @@ -1494,64 +1494,53 @@ 1494 1494 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. 1495 1495 ))) 1496 1496 1498 + 1497 1497 ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ==== 1498 1498 1499 1499 1500 -(% style="color:#037691" %)**AT Command:** 1502 +* (% style="color:#037691" %)**AT Command:** 1501 1501 1502 -There is no AT Command to control the Relay Output .1504 +There is no AT Command to control the Relay Output 1503 1503 1504 1504 1505 -(% style="color:#037691" %)**Downlink Payload** 1507 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1506 1506 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 1509 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Sets RO1/RO2 output 1511 1511 1512 -00: Close 1513 1513 1514 -01: Open 1512 +((( 1513 +If the payload is 0x030100, it means setting RO1 to close and RO2 to open. 1514 +))) 1515 1515 1516 -11: No action 1516 +((( 1517 +00: Close , 01: Open , 11: No action 1517 1517 1518 - 1519 -**RO2_status** : 1 byte in hex 1520 - 1521 -00: Close 1522 - 1523 -01: Open 1524 - 1525 -11: No action 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 1526 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 1539 1540 -(% style="color:red" %)**The device will transmit an uplink packet if the downlink payload is executed successfully.** 1541 -))) 1531 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.** 1542 1542 1533 + 1543 1543 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1544 1544 1545 1545 1546 1546 Controls the relay output time. 1547 1547 1539 +* (% style="color:#037691" %)**AT Command:** 1548 1548 1549 -(% style="color:#037691" %)**AT Command:** 1550 - 1551 1551 There is no AT Command to control the Relay Output 1552 1552 1553 1553 1554 -(% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1544 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1555 1555 1556 1556 (% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Sets RO1/RO2 relays with time control 1557 1557 ... ... @@ -2126,7 +2126,7 @@ 2126 2126 [[image:thingseye-events.png]] 2127 2127 2128 2128 2129 -* To view the **JSON payload** of a message, click on the **three dots (...)** in the **Message**column of the desired message.2119 +* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 2130 2130 2131 2131 [[image:thingseye-json.png]] 2132 2132 ... ... @@ -2137,16 +2137,12 @@ 2137 2137 If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 2138 2138 2139 2139 2140 -==== 3.5.2.4 Viewing sensorataon adashboard====2130 +==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ==== 2141 2141 2142 2142 2143 - You can create a dashboard withThingsEyeto visualize the sensor data coming from the LHT65N-VIB. The followingimageshowsaashboardcreatedfor the LT-22222-L. See **Creating a dashboard** in ThingsEye documentation for more information.2133 +This will be added soon. 2144 2144 2145 2145 2146 - 2147 -[[image:lt-22222-l-dashboard.png]] 2148 - 2149 - 2150 2150 == 3.6 Interface Details == 2151 2151 2152 2152 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===