Last modified by Mengting Qiu on 2024/03/07 08:41
<
From version < 138.5 >
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,8 +57,6 @@
57 57  * IP66 Waterproof Enclosure
58 58  * 4000mAh or 8500mAh Battery for long term use
59 59  
60 -
61 -
62 62  == 1.3  Specification ==
63 63  
64 64  === 1.3.1  Rated environmental conditions ===
... ... @@ -82,7 +82,6 @@
82 82  (% style="display:none" %) (%%)
83 83  
84 84  
85 -
86 86  == 1.5 ​ Applications ==
87 87  
88 88  * Horizontal distance measurement
... ... @@ -95,8 +95,6 @@
95 95  * Sewer
96 96  * Bottom water level monitoring
97 97  
98 -
99 -
100 100  == 1.6  Pin mapping and power on ==
101 101  
102 102  
... ... @@ -103,7 +103,6 @@
103 103  [[image:1654847583902-256.png]]
104 104  
105 105  
106 -
107 107  = 2.  Configure LDDS75 to connect to LoRaWAN network =
108 108  
109 109  == 2.1  How it works ==
... ... @@ -117,7 +117,6 @@
117 117  )))
118 118  
119 119  
120 -
121 121  == 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
122 122  
123 123  (((
... ... @@ -237,6 +237,8 @@
237 237  * If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
238 238  * 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.
239 239  
233 +
234 +
240 240  === 2.3.3  Interrupt Pin ===
241 241  
242 242  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.
... ... @@ -285,7 +285,7 @@
285 285  
286 286  == 2.4  Uplink Interval ==
287 287  
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"]]
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"]]
289 289  
290 290  
291 291  
... ... @@ -316,25 +316,47 @@
316 316  
317 317  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
318 318  
319 -(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
314 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
320 320  
321 -[[image:1654851029373-510.png]]
316 +[[image:1654832691989-514.png]]
322 322  
323 323  
324 -After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
319 +[[image:1654592833877-762.png]]
325 325  
326 -[[image:image-20220610165129-11.png||height="595" width="1088"]]
327 327  
322 +[[image:1654832740634-933.png]]
328 328  
329 329  
330 -== 2.6  Frequency Plans ==
331 331  
332 332  (((
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.
327 +(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
334 334  )))
335 335  
330 +(((
331 +
332 +)))
336 336  
334 +[[image:1654833065139-942.png]]
337 337  
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 +
338 338  === 2.6.1  EU863-870 (EU868) ===
339 339  
340 340  (((
... ... @@ -398,51 +398,20 @@
398 398  === 2.6.2  US902-928(US915) ===
399 399  
400 400  (((
401 -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 +)))
402 402  
403 -(% 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 +)))
404 404  
405 -903.9 - SF7BW125 to SF10BW125
406 -
407 -904.1 - SF7BW125 to SF10BW125
408 -
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 -
425 +(((
426 +After Join success, the end node will switch to the correct sub band by:
444 444  )))
445 445  
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 +
446 446  === 2.6.3  CN470-510 (CN470) ===
447 447  
448 448  (((
... ... @@ -535,51 +535,24 @@
535 535  === 2.6.4  AU915-928(AU915) ===
536 536  
537 537  (((
538 -Default use CHE=2
524 +Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
525 +)))
539 539  
540 -(% 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 +)))
541 541  
542 -916.8 - SF7BW125 to SF12BW125
543 -
544 -917.0 - SF7BW125 to SF12BW125
545 -
546 -917.2 - SF7BW125 to SF12BW125
547 -
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 -
531 +(((
580 580  
581 581  )))
582 582  
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 +
583 583  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
584 584  
585 585  (((
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