Last modified by Mengting Qiu on 2024/03/07 08:41
<
From version < 138.4 >
edited by Xiaoling
on 2022/06/10 17:04
To version < 136.1 >
edited by Xiaoling
on 2022/06/10 16:50
>
Change comment: Uploaded new attachment "1654851029373-510.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -57,9 +57,6 @@
57 57  * IP66 Waterproof Enclosure
58 58  * 4000mAh or 8500mAh Battery for long term use
59 59  
60 -
61 -
62 -
63 63  == 1.3  Specification ==
64 64  
65 65  === 1.3.1  Rated environmental conditions ===
... ... @@ -83,7 +83,6 @@
83 83  (% style="display:none" %) (%%)
84 84  
85 85  
86 -
87 87  == 1.5 ​ Applications ==
88 88  
89 89  * Horizontal distance measurement
... ... @@ -96,9 +96,6 @@
96 96  * Sewer
97 97  * Bottom water level monitoring
98 98  
99 -
100 -
101 -
102 102  == 1.6  Pin mapping and power on ==
103 103  
104 104  
... ... @@ -105,7 +105,6 @@
105 105  [[image:1654847583902-256.png]]
106 106  
107 107  
108 -
109 109  = 2.  Configure LDDS75 to connect to LoRaWAN network =
110 110  
111 111  == 2.1  How it works ==
... ... @@ -119,7 +119,6 @@
119 119  )))
120 120  
121 121  
122 -
123 123  == 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
124 124  
125 125  (((
... ... @@ -240,6 +240,7 @@
240 240  * 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.
241 241  
242 242  
234 +
243 243  === 2.3.3  Interrupt Pin ===
244 244  
245 245  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.
... ... @@ -288,7 +288,7 @@
288 288  
289 289  == 2.4  Uplink Interval ==
290 290  
291 -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"]]
283 +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"]]
292 292  
293 293  
294 294  
... ... @@ -319,25 +319,47 @@
319 319  
320 320  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
321 321  
322 -(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
314 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
323 323  
324 -[[image:1654851029373-510.png]]
316 +[[image:1654832691989-514.png]]
325 325  
326 326  
327 -After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
319 +[[image:1654592833877-762.png]]
328 328  
329 -[[image:image-20220610165129-11.png||height="595" width="1088"]]
330 330  
322 +[[image:1654832740634-933.png]]
331 331  
332 332  
333 -== 2.6  Frequency Plans ==
334 334  
335 335  (((
336 -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.
327 +(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
337 337  )))
338 338  
330 +(((
331 +
332 +)))
339 339  
334 +[[image:1654833065139-942.png]]
340 340  
336 +
337 +
338 +[[image:1654833092678-390.png]]
339 +
340 +
341 +
342 +After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
343 +
344 +[[image:1654833163048-332.png]]
345 +
346 +
347 +
348 +== 2.6  Frequency Plans ==
349 +
350 +(((
351 +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.
352 +)))
353 +
354 +
341 341  === 2.6.1  EU863-870 (EU868) ===
342 342  
343 343  (((
... ... @@ -401,51 +401,20 @@
401 401  === 2.6.2  US902-928(US915) ===
402 402  
403 403  (((
404 -Used in USA, Canada and South America. Default use CHE=2
418 +Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
419 +)))
405 405  
406 -(% style="color:blue" %)**Uplink:**
421 +(((
422 +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.
423 +)))
407 407  
408 -903.9 - SF7BW125 to SF10BW125
409 -
410 -904.1 - SF7BW125 to SF10BW125
411 -
412 -904.3 - SF7BW125 to SF10BW125
413 -
414 -904.5 - SF7BW125 to SF10BW125
415 -
416 -904.7 - SF7BW125 to SF10BW125
417 -
418 -904.9 - SF7BW125 to SF10BW125
419 -
420 -905.1 - SF7BW125 to SF10BW125
421 -
422 -905.3 - SF7BW125 to SF10BW125
423 -
424 -
425 -(% style="color:blue" %)**Downlink:**
426 -
427 -923.3 - SF7BW500 to SF12BW500
428 -
429 -923.9 - SF7BW500 to SF12BW500
430 -
431 -924.5 - SF7BW500 to SF12BW500
432 -
433 -925.1 - SF7BW500 to SF12BW500
434 -
435 -925.7 - SF7BW500 to SF12BW500
436 -
437 -926.3 - SF7BW500 to SF12BW500
438 -
439 -926.9 - SF7BW500 to SF12BW500
440 -
441 -927.5 - SF7BW500 to SF12BW500
442 -
443 -923.3 - SF12BW500(RX2 downlink only)
444 -
445 -
446 -
425 +(((
426 +After Join success, the end node will switch to the correct sub band by:
447 447  )))
448 448  
429 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
430 +* 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)
431 +
449 449  === 2.6.3  CN470-510 (CN470) ===
450 450  
451 451  (((
... ... @@ -538,51 +538,24 @@
538 538  === 2.6.4  AU915-928(AU915) ===
539 539  
540 540  (((
541 -Default use CHE=2
524 +Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
525 +)))
542 542  
543 -(% style="color:blue" %)**Uplink:**
527 +(((
528 +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.
529 +)))
544 544  
545 -916.8 - SF7BW125 to SF12BW125
546 -
547 -917.0 - SF7BW125 to SF12BW125
548 -
549 -917.2 - SF7BW125 to SF12BW125
550 -
551 -917.4 - SF7BW125 to SF12BW125
552 -
553 -917.6 - SF7BW125 to SF12BW125
554 -
555 -917.8 - SF7BW125 to SF12BW125
556 -
557 -918.0 - SF7BW125 to SF12BW125
558 -
559 -918.2 - SF7BW125 to SF12BW125
560 -
561 -
562 -(% style="color:blue" %)**Downlink:**
563 -
564 -923.3 - SF7BW500 to SF12BW500
565 -
566 -923.9 - SF7BW500 to SF12BW500
567 -
568 -924.5 - SF7BW500 to SF12BW500
569 -
570 -925.1 - SF7BW500 to SF12BW500
571 -
572 -925.7 - SF7BW500 to SF12BW500
573 -
574 -926.3 - SF7BW500 to SF12BW500
575 -
576 -926.9 - SF7BW500 to SF12BW500
577 -
578 -927.5 - SF7BW500 to SF12BW500
579 -
580 -923.3 - SF12BW500(RX2 downlink only)
581 -
582 -
531 +(((
583 583  
584 584  )))
585 585  
535 +(((
536 +After Join success, the end node will switch to the correct sub band by:
537 +)))
538 +
539 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
540 +* 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)
541 +
586 586  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
587 587  
588 588  (((
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