Last modified by Mengting Qiu on 2024/03/07 08:41
<
From version < 134.2 >
edited by Xiaoling
on 2022/06/10 16:43
To version < 138.5 >
edited by Xiaoling
on 2022/06/10 17:04
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -57,6 +57,8 @@
57 57  * IP66 Waterproof Enclosure
58 58  * 4000mAh or 8500mAh Battery for long term use
59 59  
60 +
61 +
60 60  == 1.3  Specification ==
61 61  
62 62  === 1.3.1  Rated environmental conditions ===
... ... @@ -80,6 +80,7 @@
80 80  (% style="display:none" %) (%%)
81 81  
82 82  
85 +
83 83  == 1.5 ​ Applications ==
84 84  
85 85  * Horizontal distance measurement
... ... @@ -92,6 +92,8 @@
92 92  * Sewer
93 93  * Bottom water level monitoring
94 94  
98 +
99 +
95 95  == 1.6  Pin mapping and power on ==
96 96  
97 97  
... ... @@ -98,6 +98,7 @@
98 98  [[image:1654847583902-256.png]]
99 99  
100 100  
106 +
101 101  = 2.  Configure LDDS75 to connect to LoRaWAN network =
102 102  
103 103  == 2.1  How it works ==
... ... @@ -111,6 +111,7 @@
111 111  )))
112 112  
113 113  
120 +
114 114  == 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
115 115  
116 116  (((
... ... @@ -224,11 +224,9 @@
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
234 +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 228  
229 -**(% style="color:#4472C4" %) 0B05(H) = 2821 (D) = 2821 mm.**
230 230  
231 -
232 232  * If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
233 233  * 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.
234 234  
... ... @@ -270,21 +270,17 @@
270 270  While using TTN network, you can add the payload format to decode the payload.
271 271  
272 272  
273 -[[image:1654592762713-715.png]]
278 +[[image:1654850829385-439.png]]
274 274  
275 -(((
276 -The payload decoder function for TTN is here:
277 -)))
280 +The payload decoder function for TTN V3 is here:
278 278  
279 -(((
280 -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/]]
281 -)))
282 +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/]]
282 282  
283 283  
284 284  
285 285  == 2.4  Uplink Interval ==
286 286  
287 -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"]]
288 +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"]]
288 288  
289 289  
290 290  
... ... @@ -315,47 +315,25 @@
315 315  
316 316  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
317 317  
318 -(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
319 +(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
319 319  
320 -[[image:1654832691989-514.png]]
321 +[[image:1654851029373-510.png]]
321 321  
322 322  
323 -[[image:1654592833877-762.png]]
324 +After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
324 324  
326 +[[image:image-20220610165129-11.png||height="595" width="1088"]]
325 325  
326 -[[image:1654832740634-933.png]]
327 327  
328 328  
329 -
330 -(((
331 -(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
332 -)))
333 -
334 -(((
335 -
336 -)))
337 -
338 -[[image:1654833065139-942.png]]
339 -
340 -
341 -
342 -[[image:1654833092678-390.png]]
343 -
344 -
345 -
346 -After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
347 -
348 -[[image:1654833163048-332.png]]
349 -
350 -
351 -
352 352  == 2.6  Frequency Plans ==
353 353  
354 354  (((
355 -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.
333 +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.
356 356  )))
357 357  
358 358  
337 +
359 359  === 2.6.1  EU863-870 (EU868) ===
360 360  
361 361  (((
... ... @@ -419,20 +419,51 @@
419 419  === 2.6.2  US902-928(US915) ===
420 420  
421 421  (((
422 -Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
423 -)))
401 +Used in USA, Canada and South America. Default use CHE=2
424 424  
425 -(((
426 -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.
427 -)))
403 +(% style="color:blue" %)**Uplink:**
428 428  
429 -(((
430 -After Join success, the end node will switch to the correct sub band by:
431 -)))
405 +903.9 - SF7BW125 to SF10BW125
432 432  
433 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
434 -* 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)
407 +904.1 - SF7BW125 to SF10BW125
435 435  
409 +904.3 - SF7BW125 to SF10BW125
410 +
411 +904.5 - SF7BW125 to SF10BW125
412 +
413 +904.7 - SF7BW125 to SF10BW125
414 +
415 +904.9 - SF7BW125 to SF10BW125
416 +
417 +905.1 - SF7BW125 to SF10BW125
418 +
419 +905.3 - SF7BW125 to SF10BW125
420 +
421 +
422 +(% style="color:blue" %)**Downlink:**
423 +
424 +923.3 - SF7BW500 to SF12BW500
425 +
426 +923.9 - SF7BW500 to SF12BW500
427 +
428 +924.5 - SF7BW500 to SF12BW500
429 +
430 +925.1 - SF7BW500 to SF12BW500
431 +
432 +925.7 - SF7BW500 to SF12BW500
433 +
434 +926.3 - SF7BW500 to SF12BW500
435 +
436 +926.9 - SF7BW500 to SF12BW500
437 +
438 +927.5 - SF7BW500 to SF12BW500
439 +
440 +923.3 - SF12BW500(RX2 downlink only)
441 +
442 +
443 +
444 +)))
445 +
436 436  === 2.6.3  CN470-510 (CN470) ===
437 437  
438 438  (((
... ... @@ -525,24 +525,51 @@
525 525  === 2.6.4  AU915-928(AU915) ===
526 526  
527 527  (((
528 -Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
529 -)))
538 +Default use CHE=2
530 530  
531 -(((
532 -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.
533 -)))
540 +(% style="color:blue" %)**Uplink:**
534 534  
535 -(((
536 -
537 -)))
542 +916.8 - SF7BW125 to SF12BW125
538 538  
539 -(((
540 -After Join success, the end node will switch to the correct sub band by:
541 -)))
544 +917.0 - SF7BW125 to SF12BW125
542 542  
543 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
544 -* 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)
546 +917.2 - SF7BW125 to SF12BW125
545 545  
548 +917.4 - SF7BW125 to SF12BW125
549 +
550 +917.6 - SF7BW125 to SF12BW125
551 +
552 +917.8 - SF7BW125 to SF12BW125
553 +
554 +918.0 - SF7BW125 to SF12BW125
555 +
556 +918.2 - SF7BW125 to SF12BW125
557 +
558 +
559 +(% style="color:blue" %)**Downlink:**
560 +
561 +923.3 - SF7BW500 to SF12BW500
562 +
563 +923.9 - SF7BW500 to SF12BW500
564 +
565 +924.5 - SF7BW500 to SF12BW500
566 +
567 +925.1 - SF7BW500 to SF12BW500
568 +
569 +925.7 - SF7BW500 to SF12BW500
570 +
571 +926.3 - SF7BW500 to SF12BW500
572 +
573 +926.9 - SF7BW500 to SF12BW500
574 +
575 +927.5 - SF7BW500 to SF12BW500
576 +
577 +923.3 - SF12BW500(RX2 downlink only)
578 +
579 +
580 +
581 +)))
582 +
546 546  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
547 547  
548 548  (((
1654850829385-439.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +59.2 KB
Content
1654851029373-510.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +92.0 KB
Content
image-20220610165129-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +50.5 KB
Content

Applications

Navigation

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