Skip to Content
Last modified by Mengting Qiu on 2025/07/08 11:11
From version 191.1
edited by Mengting Qiu
on 2025/04/23 10:08
Change comment: There is no comment for this version
To version 192.1
edited by Dilisi S
on 2025/05/12 16:31
Change comment: May 12 edits

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.pradeeka
Content
... ... @@ -183,7 +183,8 @@
183 183  == 2.1 How it works ==
184 184  
185 185  
186 -The LDS25-LB/LS is configured as (% style="color:#037691" %)**LoRaWAN OTAA Class A**(%%) mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and press the button to activate the LDS25-LB/LS. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.
186 +The LDS25-LB/LS is configured in LoRaWAN **Class A** mode by default. The device ships with unique registration information that can be used to configure it for OTAA (Over-The-Air Activation).
187 +To connect to a local LoRaWAN network, you must first register the device with the respective LoRaWAN network server using the registration information. We recommend using the **OTAA **activation method because it is more secure than the ABP method. After adding the registration information, press the **ACT **button to activate the LDS25-LB/LS. It will automatically join the network using OTAA and start sending sensor values. The default uplink interval is **20 **minutes.
187 187  
188 188  (% style="display:none" %) (%%)
189 189  
... ... @@ -256,10 +256,10 @@
256 256  
257 257  == 2.3 ​Uplink Payload ==
258 258  
259 -=== 2.3.1 Device Status, FPORT~=5 ===
260 +=== 2.3.1 Device Status, FPort~=5 ===
260 260  
261 261  
262 -Users can use the downlink command(**0x26 01**) to ask LDS25-LB/LS to send device configure detail, include device configure status. LDS25-LB/LS will uplink a payload via FPort=5 to server.
263 +You can use the downlink command (**0x26 01**) to ask LDS25-LB/LS to send device configuration details, including device configuration status. LDS25-LB/LS will uplink a payload via FPort=5 to the network server.
263 263  
264 264  The Payload format is as below.
265 265  
... ... @@ -269,13 +269,13 @@
269 269  )))|=(% style="width: 100px; background-color: #4F81BD;color:white;" %)**1**|=(% style="width: 100px; background-color: #4F81BD;color:white;" %)**2**|=(% style="background-color: #4F81BD;color:white; width: 100px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 100px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 50px;" %)**2**
270 270  |(% style="width:62.5px" %)Value|(% style="width:110px" %)Sensor Model|(% style="width:48px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:91px" %)Sub-band|(% style="width:60px" %)BAT
271 271  
272 -Example parse in TTNv3:
273 +Example payload in The Things Stack v3:
273 273  
274 274  [[image:image-20241007153616-2.png||height="277" width="1283"]]
275 275  
276 276  (% style="color:blue" %)**Sensor Model**(%%): For LDS25-LB/LS, this value is 0x3E
277 277  
278 -(% style="color:blue" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
279 +(% style="color:blue" %)**Firmware Version**(%%): 0x0100, which means v1.0.0
279 279  
280 280  (% style="color:blue" %)**Frequency Band**:
281 281  
... ... @@ -313,17 +313,23 @@
313 313  
314 314  CN470: value 0x0B ~~ 0x0C
315 315  
316 -Other Bands: Always 0x00
317 +Other Bands: always 0x00
317 317  
318 318  (% style="color:blue" %)**Battery Info**:
319 319  
320 -Check the battery voltage.
321 +Calculate the battery voltage as follows:
321 321  
322 -Ex1: 0x0B45 = 2885mV
323 +Battery Voltage (mV) = (High Byte × 256) + Low Byte
323 323  
324 -Ex2: 0x0B49 = 2889mV
325 +0x0C96 = 3222mV
325 325  
327 +More examples:
326 326  
329 +Example 1: 0x0B45 = 2885mV
330 +
331 +Example 2: 0x0B49 = 2889mV
332 +
333 +
327 327  === 2.3.2 Uplink Payload, FPORT~=2 ===
328 328  
329 329