Skip to Content
Last modified by Mengting Qiu on 2023/12/14 11:15
From version 109.4
edited by Xiaoling
on 2023/08/07 09:26
Change comment: There is no comment for this version
To version 90.17
edited by Xiaoling
on 2023/07/15 15:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -155,8 +155,8 @@
155 155  
156 156  == 1.8 Pin Definitions ==
157 157  
158 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/WL03A-LB_LoRaWAN_None-Position_Rope_Type_Water_Leak_Controller_User_Manual/WebHome/image-20230613144156-1.png?rev=1.1||alt="image-20230613144156-1.png"]]
158 158  
159 -[[image:image-20230805144259-1.png||height="413" width="741"]]
160 160  
161 161  == 1.9 Mechanical ==
162 162  
... ... @@ -253,8 +253,6 @@
253 253  
254 254  Example parse in TTNv3
255 255  
256 -[[image:image-20230805103904-1.png||height="131" width="711"]]
257 -
258 258  (% style="color:blue" %)**Sensor Model**(%%): For LDS12-LB, this value is 0x24
259 259  
260 260  (% style="color:blue" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
... ... @@ -310,11 +310,11 @@
310 310  
311 311  
312 312  (((
313 -LDS12-LB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LDS12-LB will:
311 +LDS12-LB will uplink payload via LoRaWAN with below payload format: 
312 +)))
314 314  
315 -periodically send this uplink every 20 minutes, this interval [[can be changed>>||anchor="H3.3.1SetTransmitIntervalTime"]].
316 -
317 -Uplink Payload totals 11 bytes.
314 +(((
315 +Uplink payload includes in total 11 bytes.
318 318  )))
319 319  
320 320  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -329,7 +329,7 @@
329 329  [[Message Type>>||anchor="HMessageType"]]
330 330  )))
331 331  
332 -[[image:image-20230805104104-2.png||height="136" width="754"]]
330 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654833689380-972.png?rev=1.1||alt="1654833689380-972.png"]]
333 333  
334 334  
335 335  ==== (% style="color:blue" %)**Battery Info**(%%) ====
... ... @@ -379,33 +379,18 @@
379 379  Customers can judge whether they need to adjust the environment based on the signal strength.
380 380  
381 381  
382 -**1) When the sensor detects valid data:**
383 -
384 -[[image:image-20230805155335-1.png||height="145" width="724"]]
385 -
386 -
387 -**2) When the sensor detects invalid data:**
388 -
389 -[[image:image-20230805155428-2.png||height="139" width="726"]]
390 -
391 -
392 -**3) When the sensor is not connected:**
393 -
394 -[[image:image-20230805155515-3.png||height="143" width="725"]]
395 -
396 -
397 397  ==== (% style="color:blue" %)**Interrupt Pin & Interrupt Level**(%%) ====
398 398  
399 399  
400 400  This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.3.2SetInterruptMode"]] for the hardware and software set up.
401 401  
402 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.8PinDefinitions"]] of GPIO_EXTI .
385 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.8PinDefinitions"]].
403 403  
404 404  **Example:**
405 405  
406 -If byte[0]&0x01=0x00 : Normal uplink packet.
389 +0x00: Normal uplink packet.
407 407  
408 -If byte[0]&0x01=0x01 : Interrupt Uplink Packet.
391 +0x01: Interrupt Uplink Packet.
409 409  
410 410  
411 411  ==== (% style="color:blue" %)**LiDAR temp**(%%) ====
... ... @@ -431,97 +431,13 @@
431 431  
432 432  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:499px" %)
433 433  |=(% style="width: 161px;background-color:#4F81BD;color:white" %)**Message Type Code**|=(% style="width: 164px;background-color:#4F81BD;color:white" %)**Description**|=(% style="width: 174px;background-color:#4F81BD;color:white" %)**Payload**
434 -|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)Normal Uplink Payload
435 -|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)Configure Info Payload
417 +|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]
418 +|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.ConfigureLDS12-LB"]]
436 436  
437 -[[image:image-20230805150315-4.png||height="233" width="723"]]
438 438  
421 +=== 2.3.3 Decode payload in The Things Network ===
439 439  
440 -=== 2.3.3 Historical measuring distance, FPORT~=3 ===
441 441  
442 -
443 -LDS12-LB stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.5.4Pollsensorvalue"]].
444 -
445 -The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time measuring distance.
446 -
447 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
448 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
449 -**Size(bytes)**
450 -)))|=(% style="width: 80px;background-color:#4F81BD;color:white" %)1|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 50px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 70px;background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD; color: white; width: 88px;" %)**1**|=(% style="background-color: #4F81BD; color: white; width: 85px;" %)4
451 -|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)Interrupt flag & Interrupt_level|(% style="width:62.5px" %)(((
452 -Reserve(0xFF)
453 -)))|Distance|Distance signal strength|(% style="width:88px" %)(((
454 -LiDAR temp
455 -)))|(% style="width:85px" %)Unix TimeStamp
456 -
457 -**Interrupt flag & Interrupt level:**
458 -
459 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:501px" %)
460 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
461 -**Size(bit)**
462 -)))|=(% style="width: 30px;background-color:#4F81BD;color:white" %)**bit7**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**bit6**|=(% style="width: 50px;background-color:#4F81BD;color:white" %)**[bit5:bit2]**|=(% style="width: 91px; background-color: rgb(79, 129, 189); color: white;" %)**bit1**|=(% style="background-color: rgb(79, 129, 189); color: white; width: 88px;" %)**bit0**
463 -|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)No ACK message|(% style="width:62.5px" %)Poll Message Flag|Reserve|(% style="width:91px" %)Interrupt level|(% style="width:88px" %)(((
464 -Interrupt flag
465 -)))
466 -
467 -* (((
468 -Each data entry is 11 bytes and has the same structure as [[Uplink Payload>>http://8.211.40.43/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS12-LB_LoRaWAN_LiDAR_ToF_Distance_Sensor_User_Manual/#H2.3.2UplinkPayload2CFPORT3D2]], to save airtime and battery, LDS12-LB will send max bytes according to the current DR and Frequency bands.
469 -)))
470 -
471 -For example, in the US915 band, the max payload for different DR is:
472 -
473 -**a) DR0:** max is 11 bytes so one entry of data
474 -
475 -**b) DR1:** max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
476 -
477 -**c) DR2:** total payload includes 11 entries of data
478 -
479 -**d) DR3:** total payload includes 22 entries of data.
480 -
481 -If LDS12-LB doesn't have any data in the polling time. It will uplink 11 bytes of 0
482 -
483 -
484 -**Downlink:**
485 -
486 -0x31 64 CC 68 0C 64 CC 69 74 05
487 -
488 -[[image:image-20230805144936-2.png||height="113" width="746"]]
489 -
490 -**Uplink:**
491 -
492 -43 FF 0E 10 00 B0 1E 64 CC 68 0C 40 FF 0D DE 00 A8 1E 64 CC 68 29 40 FF 09 92 00 D3 1E 64 CC 68 65 40 FF 02 3A 02 BC 1E 64 CC 68 A1 41 FF 0E 1A 00 A4 1E 64 CC 68 C0 40 FF 0D 2A 00 B8 1E 64 CC 68 E8 40 FF 00 C8 11 6A 1E 64 CC 69 24 40 FF 0E 24 00 AD 1E 64 CC 69 6D
493 -
494 -
495 -**Parsed Value:**
496 -
497 -[DISTANCE , DISTANCE_SIGNAL_STRENGTH，LIDAR_TEMP，EXTI_STATUS , EXTI_FLAG , TIME]
498 -
499 -
500 -[360,176,30,High,True,2023-08-04 02:53:00],
501 -
502 -[355,168,30,Low,False,2023-08-04 02:53:29],
503 -
504 -[245,211,30,Low,False,2023-08-04 02:54:29],
505 -
506 -[57,700,30,Low,False,2023-08-04 02:55:29],
507 -
508 -[361,164,30,Low,True,2023-08-04 02:56:00],
509 -
510 -[337,184,30,Low,False,2023-08-04 02:56:40],
511 -
512 -[20,4458,30,Low,False,2023-08-04 02:57:40],
513 -
514 -[362,173,30,Low,False,2023-08-04 02:58:53],
515 -
516 -
517 -**History read from serial port：**
518 -
519 -[[image:image-20230805145056-3.png]]
520 -
521 -
522 -=== 2.3.4 Decode payload in The Things Network ===
523 -
524 -
525 525  While using TTN network, you can add the payload format to decode the payload.
526 526  
527 527  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654592762713-715.png?rev=1.1||alt="1654592762713-715.png"]]
... ... @@ -536,9 +536,15 @@
536 536  )))
537 537  
538 538  
539 -== 2.4 ​Show Data in DataCake IoT Server ==
438 +== 2.4 Uplink Interval ==
540 540  
541 541  
441 +The LDS12-LB 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>>||anchor="H3.3.1SetTransmitIntervalTime"]]
442 +
443 +
444 +== 2.5 ​Show Data in DataCake IoT Server ==
445 +
446 +
542 542  (((
543 543  [[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps:
544 544  )))
... ... @@ -571,13 +571,13 @@
571 571  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDDS75%20-%20LoRaWAN%20Distance%20Detection%20Sensor%20User%20Manual/WebHome/image-20220610165129-11.png?width=1088&height=595&rev=1.1||alt="image-20220610165129-11.png"]]
572 572  
573 573  
574 -== 2.5 Datalog Feature ==
479 +== 2.6 Datalog Feature ==
575 575  
576 576  
577 577  Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, LDS12-LB will store the reading for future retrieving purposes.
578 578  
579 579  
580 -=== 2.5.1 Ways to get datalog via LoRaWAN ===
485 +=== 2.6.1 Ways to get datalog via LoRaWAN ===
581 581  
582 582  
583 583  Set PNACKMD=1, LDS12-LB will wait for ACK for every uplink, when there is no LoRaWAN network,LDS12-LB will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
... ... @@ -594,7 +594,7 @@
594 594  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/WebHome/image-20220703111700-2.png?width=1119&height=381&rev=1.1||alt="图片-20220703111700-2.png" height="381" width="1119"]]
595 595  
596 596  
597 -=== 2.5.2 Unix TimeStamp ===
502 +=== 2.6.2 Unix TimeStamp ===
598 598  
599 599  
600 600  LDS12-LB uses Unix TimeStamp format based on
... ... @@ -611,7 +611,7 @@
611 611  So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
612 612  
613 613  
614 -=== 2.5.3 Set Device Time ===
519 +=== 2.6.3 Set Device Time ===
615 615  
616 616  
617 617  User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
... ... @@ -621,7 +621,7 @@
621 621  (% style="color:red" %)**Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.**
622 622  
623 623  
624 -=== 2.5.4 Poll sensor value ===
529 +=== 2.6.4 Poll sensor value ===
625 625  
626 626  
627 627  Users can poll sensor values based on timestamps. Below is the downlink command.
... ... @@ -648,7 +648,7 @@
648 648  )))
649 649  
650 650  
651 -== 2.6 Frequency Plans ==
556 +== 2.7 Frequency Plans ==
652 652  
653 653  
654 654  The LDS12-LB 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.
... ... @@ -656,9 +656,9 @@
656 656  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]]
657 657  
658 658  
659 -== 2.7 LiDAR ToF Measurement ==
564 +== 2.8 LiDAR ToF Measurement ==
660 660  
661 -=== 2.7.1 Principle of Distance Measurement ===
566 +=== 2.8.1 Principle of Distance Measurement ===
662 662  
663 663  
664 664  The LiDAR probe is based on TOF, namely, Time of Flight principle. To be specific, the product emits modulation wave of near infrared ray on a periodic basis, which will be reflected after contacting object. The product obtains the time of flight by measuring round-trip phase difference and then calculates relative range between the product and the detection object, as shown below.
... ... @@ -666,7 +666,7 @@
666 666  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654831757579-263.png?rev=1.1||alt="1654831757579-263.png"]]
667 667  
668 668  
669 -=== 2.7.2 Distance Measurement Characteristics ===
574 +=== 2.8.2 Distance Measurement Characteristics ===
670 670  
671 671  
672 672  With optimization of light path and algorithm, The LiDAR probe has minimized influence from external environment on distance measurement performance. Despite that, the range of distance measurement may still be affected by the environment illumination intensity and the reflectivity of detection object. As shown in below:
... ... @@ -704,7 +704,7 @@
704 704  )))
705 705  
706 706  
707 -=== 2.7.3 Notice of usage ===
612 +=== 2.8.3 Notice of usage ===
708 708  
709 709  
710 710  Possible invalid /wrong reading for LiDAR ToF tech:
... ... @@ -714,7 +714,7 @@
714 714  * The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
715 715  * The sensor window is made by Acrylic. Don't touch it with alcohol material. This will destroy the sensor window.
716 716  
717 -=== 2.7.4  Reflectivity of different objects ===
622 +=== 2.8.4  Reflectivity of different objects ===
718 718  
719 719  
720 720  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:379px" %)
... ... @@ -821,9 +821,9 @@
821 821  === 3.3.2 Set Interrupt Mode ===
822 822  
823 823  
824 -Feature, Set Interrupt mode for pin of GPIO_EXTI.
729 +Feature, Set Interrupt mode for PA8 of pin.
825 825  
826 -When AT+INTMOD=0 is set, GPIO_EXTI is used as a digital input port.
731 +When AT+INTMOD=0 is set, PA8 is used as a digital input port.
827 827  
828 828  (% style="color:blue" %)**AT Command: AT+INTMOD**
829 829  
... ... @@ -834,11 +834,7 @@
834 834  OK
835 835  the mode is 0 =Disable Interrupt
836 836  )))
837 -|(% style="width:154px" %)(((
838 -AT+INTMOD=2
839 -
840 -(default)
841 -)))|(% style="width:196px" %)(((
742 +|(% style="width:154px" %)AT+INTMOD=2|(% style="width:196px" %)(((
842 842  Set Transmit Interval
843 843  0. (Disable Interrupt),
844 844  ~1. (Trigger by rising and falling edge)
... ... @@ -858,7 +858,7 @@
858 858  
859 859  === 3.3.3  Set Power Output Duration ===
860 860  
861 -Control the output duration 3V3(pin of VBAT_OUT) . Before each sampling, device will
762 +Control the output duration 3V3 . Before each sampling, device will
862 862  
863 863  ~1. first enable the power output to external sensor,
864 864  
... ... @@ -874,7 +874,6 @@
874 874  OK
875 875  |(% style="width:154px" %)AT+3V3T=1000|(% style="width:196px" %)Close after a delay of 1000 milliseconds.|(% style="width:157px" %)OK
876 876  |(% style="width:154px" %)AT+3V3T=0|(% style="width:196px" %)Always turn on the power supply of 3V3 pin.|(% style="width:157px" %)OK
877 -|(% style="width:154px" %)AT+3V3T=65535|(% style="width:196px" %)Always turn off the power supply of 3V3 pin.|(% style="width:157px" %)OK
878 878  
879 879  (% style="color:blue" %)**Downlink Command: 0x07**(%%)
880 880  Format: Command Code (0x07) followed by 3 bytes.
... ... @@ -883,7 +883,6 @@
883 883  
884 884  * Example 1: Downlink Payload: 07 01 00 00  **~-~-->**  AT+3V3T=0
885 885  * Example 2: Downlink Payload: 07 01 01 F4  **~-~-->**  AT+3V3T=500
886 -* Example 3: Downlink Payload: 07 01 FF FF  **~-~-->**  AT+3V3T=65535
887 887  
888 888  = 4. Battery & Power Consumption =
889 889  
image-20230805103904-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Saxer
Size
... ... @@ -1,1 +1,0 @@
1 -46.9 KB
Content
image-20230805104104-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Saxer
Size
... ... @@ -1,1 +1,0 @@
1 -46.3 KB
Content
image-20230805144259-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Saxer
Size
... ... @@ -1,1 +1,0 @@
1 -872.7 KB
Content
image-20230805144936-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Saxer
Size
... ... @@ -1,1 +1,0 @@
1 -37.5 KB
Content
image-20230805145056-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Saxer
Size
... ... @@ -1,1 +1,0 @@
1 -30.7 KB
Content
image-20230805150315-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Saxer
Size
... ... @@ -1,1 +1,0 @@
1 -90.6 KB
Content
image-20230805155335-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Saxer
Size
... ... @@ -1,1 +1,0 @@
1 -45.4 KB
Content
image-20230805155428-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Saxer
Size
... ... @@ -1,1 +1,0 @@
1 -45.5 KB
Content
image-20230805155515-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Saxer
Size
... ... @@ -1,1 +1,0 @@
1 -45.7 KB
Content