Last modified by Mengting Qiu on 2025/02/26 15:04
<
From version < 137.3 >
edited by Xiaoling
on 2022/06/10 16:55
To version < 134.1 >
edited by Xiaoling
on 2022/06/10 16:41
>
Change comment: Uploaded new attachment "1654850511545-399.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -92,6 +92,7 @@
92 92  * Sewer
93 93  * Bottom water level monitoring
94 94  
95 +
95 95  == 1.6  Pin mapping and power on ==
96 96  
97 97  
... ... @@ -183,7 +183,7 @@
183 183  == 2.3  ​Uplink Payload ==
184 184  
185 185  (((
186 -LDDS75 will uplink payload via LoRaWAN with below payload format: 
187 +LDDS75 will uplink payload via LoRaWAN with below payload format:
187 187  
188 188  Uplink payload includes in total 4 bytes.
189 189  Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
... ... @@ -205,7 +205,7 @@
205 205  [[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
206 206  )))|[[Sensor Flag>>path:#Sensor_Flag]]
207 207  
208 -[[image:1654850511545-399.png]]
209 +[[image:1654833689380-972.png]]
209 209  
210 210  
211 211  
... ... @@ -224,14 +224,15 @@
224 224  
225 225  Get the distance. Flat object range 280mm - 7500mm.
226 226  
227 -For example, if the data you get from the register is 0x0B 0x05, the distance between the sensor and the measured object is(% style="color:#4472c4" %)** 0B05(H) = 2821 (D) = 2821 mm.**
228 +For example, if the data you get from the register is 0x0B 0x05, the distance between the sensor and the measured object is
228 228  
230 +**0B05(H) = 2821 (D) = 2821 mm.**
229 229  
232 +
230 230  * If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
231 231  * If the sensor value lower than 0x0118 (280mm), the sensor value will be invalid. Since v1.1.4, all value lower than 280mm will be set to 0x0014(20mm) which means the value is invalid.
232 232  
233 233  
234 -
235 235  === 2.3.3  Interrupt Pin ===
236 236  
237 237  This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H4.2A0SetInterruptMode"]] for the hardware and software set up.
... ... @@ -270,17 +270,21 @@
270 270  While using TTN network, you can add the payload format to decode the payload.
271 271  
272 272  
273 -[[image:1654850829385-439.png]]
275 +[[image:1654592762713-715.png]]
274 274  
275 -The payload decoder function for TTN V3 is here:
277 +(((
278 +The payload decoder function for TTN is here:
279 +)))
276 276  
277 -LDDS75 TTN V3 Payload Decoder: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LDDS75/Payload_Decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Payload_Decoder/]]
281 +(((
282 +LLDS12 TTN Payload Decoder: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Decoder/]]
283 +)))
278 278  
279 279  
280 280  
281 281  == 2.4  Uplink Interval ==
282 282  
283 -The LDDS75 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]
289 +The LLDS12 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]
284 284  
285 285  
286 286  
... ... @@ -311,21 +311,44 @@
311 311  
312 312  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
313 313  
314 -(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
320 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
315 315  
316 -[[image:1654851029373-510.png]]
322 +[[image:1654832691989-514.png]]
317 317  
318 318  
319 -After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
325 +[[image:1654592833877-762.png]]
320 320  
321 -[[image:image-20220610165129-11.png||height="595" width="1088"]]
322 322  
328 +[[image:1654832740634-933.png]]
323 323  
324 324  
331 +
332 +(((
333 +(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
334 +)))
335 +
336 +(((
337 +
338 +)))
339 +
340 +[[image:1654833065139-942.png]]
341 +
342 +
343 +
344 +[[image:1654833092678-390.png]]
345 +
346 +
347 +
348 +After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
349 +
350 +[[image:1654833163048-332.png]]
351 +
352 +
353 +
325 325  == 2.6  Frequency Plans ==
326 326  
327 327  (((
328 -The LDDS75 uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
357 +The LLDS12 uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
329 329  )))
330 330  
331 331  
... ... @@ -392,51 +392,20 @@
392 392  === 2.6.2  US902-928(US915) ===
393 393  
394 394  (((
395 -Used in USA, Canada and South America. Default use CHE=2
424 +Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
425 +)))
396 396  
397 -(% style="color:blue" %)**Uplink:**
427 +(((
428 +To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
429 +)))
398 398  
399 -903.9 - SF7BW125 to SF10BW125
400 -
401 -904.1 - SF7BW125 to SF10BW125
402 -
403 -904.3 - SF7BW125 to SF10BW125
404 -
405 -904.5 - SF7BW125 to SF10BW125
406 -
407 -904.7 - SF7BW125 to SF10BW125
408 -
409 -904.9 - SF7BW125 to SF10BW125
410 -
411 -905.1 - SF7BW125 to SF10BW125
412 -
413 -905.3 - SF7BW125 to SF10BW125
414 -
415 -
416 -(% style="color:blue" %)**Downlink:**
417 -
418 -923.3 - SF7BW500 to SF12BW500
419 -
420 -923.9 - SF7BW500 to SF12BW500
421 -
422 -924.5 - SF7BW500 to SF12BW500
423 -
424 -925.1 - SF7BW500 to SF12BW500
425 -
426 -925.7 - SF7BW500 to SF12BW500
427 -
428 -926.3 - SF7BW500 to SF12BW500
429 -
430 -926.9 - SF7BW500 to SF12BW500
431 -
432 -927.5 - SF7BW500 to SF12BW500
433 -
434 -923.3 - SF12BW500(RX2 downlink only)
435 -
436 -
437 -
431 +(((
432 +After Join success, the end node will switch to the correct sub band by:
438 438  )))
439 439  
435 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
436 +* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
437 +
440 440  === 2.6.3  CN470-510 (CN470) ===
441 441  
442 442  (((
1654850829385-439.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -59.2 KB
Content
1654851029373-510.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -92.0 KB
Content
image-20220610165129-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -50.5 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0