Skip to Content
Last modified by Mengting Qiu on 2025/06/04 18:42
From version 236.1
edited by Dilisi S
on 2024/12/18 06:03
Change comment: Dec 17 - some minor edits
To version 235.1
edited by Dilisi S
on 2024/12/17 06:12
Change comment: Dec 16 edits

Summary

Details

Page properties
Content
... ... @@ -302,7 +302,7 @@
302 302  === 3.2.2 Joining ===
303 303  
304 304  
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.
305 +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 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.
316 +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.
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 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.
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 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 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]]:
332 +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**.
341 +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 ==
... ... @@ -1540,6 +1540,7 @@
1540 1540  (% style="color:red" %)**The device will transmit an uplink packet if the downlink payload is executed successfully.**
1541 1541  )))
1542 1542  
1543 +
1543 1543  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
1544 1544  
1545 1545