Changes for page DS20L -- LoRaWAN Smart Distance Detector User Manual 01
Last modified by Mengting Qiu on 2023/12/14 11:15
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 7 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Saxer - Content
-
... ... @@ -163,8 +163,8 @@ 163 163 164 164 == 1.8 Pin Definitions == 165 165 166 +[[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"]] 166 166 167 -[[image:image-20230805144259-1.png||height="413" width="741"]] 168 168 169 169 == 1.9 Mechanical == 170 170 ... ... @@ -261,8 +261,6 @@ 261 261 262 262 Example parse in TTNv3 263 263 264 -[[image:image-20230805103904-1.png||height="131" width="711"]] 265 - 266 266 (% style="color:blue" %)**Sensor Model**(%%): For LDS12-LB, this value is 0x24 267 267 268 268 (% style="color:blue" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version ... ... @@ -318,11 +318,11 @@ 318 318 319 319 320 320 ((( 321 -LDS12-LB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LDS12-LB will: 319 +LDS12-LB will uplink payload via LoRaWAN with below payload format: 320 +))) 322 322 323 -periodically send this uplink every 20 minutes, this interval [[can be changed>>||anchor="H3.3.1SetTransmitIntervalTime"]]. 324 - 325 -Uplink Payload totals 11 bytes. 322 +((( 323 +Uplink payload includes in total 11 bytes. 326 326 ))) 327 327 328 328 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -337,7 +337,7 @@ 337 337 [[Message Type>>||anchor="HMessageType"]] 338 338 ))) 339 339 340 -[[image:i mage-20230805104104-2.png||height="136" width="754"]]338 +[[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"]] 341 341 342 342 343 343 ==== (% style="color:blue" %)**Battery Info**(%%) ==== ... ... @@ -387,33 +387,18 @@ 387 387 Customers can judge whether they need to adjust the environment based on the signal strength. 388 388 389 389 390 -**1) When the sensor detects valid data:** 391 - 392 -[[image:image-20230805155335-1.png||height="145" width="724"]] 393 - 394 - 395 -**2) When the sensor detects invalid data:** 396 - 397 -[[image:image-20230805155428-2.png||height="139" width="726"]] 398 - 399 - 400 -**3) When the sensor is not connected:** 401 - 402 -[[image:image-20230805155515-3.png||height="143" width="725"]] 403 - 404 - 405 405 ==== (% style="color:blue" %)**Interrupt Pin & Interrupt Level**(%%) ==== 406 406 407 407 408 408 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. 409 409 410 -Note: The Internet Pin is a separate pin in the screw terminal. See of GPIO_EXTI.393 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.8PinDefinitions"]]. 411 411 412 412 **Example:** 413 413 414 - If byte[0]&0x01=0x00: Normal uplink packet.397 +0x00: Normal uplink packet. 415 415 416 - If byte[0]&0x01=0x01: Interrupt Uplink Packet.399 +0x01: Interrupt Uplink Packet. 417 417 418 418 419 419 ==== (% style="color:blue" %)**LiDAR temp**(%%) ==== ... ... @@ -439,97 +439,14 @@ 439 439 440 440 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:499px" %) 441 441 |=(% 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** 442 -|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)Normal Uplink Payload 443 -|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)Configure Info Payload 425 +|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]] 426 +|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.ConfigureLDS12-LB"]] 444 444 445 -[[image:image-20230805150315-4.png||height="233" width="723"]] 446 446 447 447 448 -=== 2.3.3 Historicalmeasuringdistance,FPORT~=3===430 +=== 2.3.3 Decode payload in The Things Network === 449 449 450 450 451 -LDS12-LB stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.5.4Pollsensorvalue"]]. 452 - 453 -The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time measuring distance. 454 - 455 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 456 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)((( 457 -**Size(bytes)** 458 -)))|=(% 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: 85px;" %)**1**|=(% style="background-color: #4F81BD; color: white; width: 85px;" %)4 459 -|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)Interrupt flag & Interrupt_level|(% style="width:62.5px" %)((( 460 -Reserve(0xFF) 461 -)))|Distance|Distance signal strength|(% style="width:88px" %)((( 462 -LiDAR temp 463 -)))|(% style="width:85px" %)Unix TimeStamp 464 - 465 -**Interrupt flag & Interrupt level:** 466 - 467 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:480px" %) 468 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)((( 469 -**Size(bit)** 470 -)))|=(% style="width: 90px;background-color:#4F81BD;color:white" %)**bit7**|=(% style="width: 90px;background-color:#4F81BD;color:white" %)**bit6**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**[bit5:bit2]**|=(% style="width: 90px; background-color: #4F81BD; color: white;" %)**bit1**|=(% style="background-color: #4F81BD; color: white; width: 90px;" %)**bit0** 471 -|(% 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" %)((( 472 -Interrupt flag 473 -))) 474 - 475 -* ((( 476 -Each data entry is 11 bytes and has the same structure as [[Uplink Payload>>||anchor="H2.3.2UplinkPayload2CFPORT3D2"]], to save airtime and battery, LDS12-LB will send max bytes according to the current DR and Frequency bands. 477 -))) 478 - 479 -For example, in the US915 band, the max payload for different DR is: 480 - 481 -**a) DR0:** max is 11 bytes so one entry of data 482 - 483 -**b) DR1:** max is 53 bytes so devices will upload 4 entries of data (total 44 bytes) 484 - 485 -**c) DR2:** total payload includes 11 entries of data 486 - 487 -**d) DR3:** total payload includes 22 entries of data. 488 - 489 -If LDS12-LB doesn't have any data in the polling time. It will uplink 11 bytes of 0 490 - 491 - 492 -**Downlink:** 493 - 494 -0x31 64 CC 68 0C 64 CC 69 74 05 495 - 496 -[[image:image-20230805144936-2.png||height="113" width="746"]] 497 - 498 -**Uplink:** 499 - 500 -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 501 - 502 - 503 -**Parsed Value:** 504 - 505 -[DISTANCE , DISTANCE_SIGNAL_STRENGTH,LIDAR_TEMP,EXTI_STATUS , EXTI_FLAG , TIME] 506 - 507 - 508 -[360,176,30,High,True,2023-08-04 02:53:00], 509 - 510 -[355,168,30,Low,False,2023-08-04 02:53:29], 511 - 512 -[245,211,30,Low,False,2023-08-04 02:54:29], 513 - 514 -[57,700,30,Low,False,2023-08-04 02:55:29], 515 - 516 -[361,164,30,Low,True,2023-08-04 02:56:00], 517 - 518 -[337,184,30,Low,False,2023-08-04 02:56:40], 519 - 520 -[20,4458,30,Low,False,2023-08-04 02:57:40], 521 - 522 -[362,173,30,Low,False,2023-08-04 02:58:53], 523 - 524 - 525 -**History read from serial port:** 526 - 527 -[[image:image-20230805145056-3.png]] 528 - 529 - 530 -=== 2.3.4 Decode payload in The Things Network === 531 - 532 - 533 533 While using TTN network, you can add the payload format to decode the payload. 534 534 535 535 [[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"]] ... ... @@ -544,9 +544,15 @@ 544 544 ))) 545 545 546 546 547 -== 2.4 Show DatainDataCakeIoT Server==447 +== 2.4 Uplink Interval == 548 548 549 549 450 +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"]] 451 + 452 + 453 +== 2.5 Show Data in DataCake IoT Server == 454 + 455 + 550 550 ((( 551 551 [[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: 552 552 ))) ... ... @@ -579,13 +579,13 @@ 579 579 [[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"]] 580 580 581 581 582 -== 2. 5Datalog Feature ==488 +== 2.6 Datalog Feature == 583 583 584 584 585 585 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. 586 586 587 587 588 -=== 2. 5.1 Ways to get datalog via LoRaWAN ===494 +=== 2.6.1 Ways to get datalog via LoRaWAN === 589 589 590 590 591 591 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. ... ... @@ -602,7 +602,7 @@ 602 602 [[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"]] 603 603 604 604 605 -=== 2. 5.2 Unix TimeStamp ===511 +=== 2.6.2 Unix TimeStamp === 606 606 607 607 608 608 LDS12-LB uses Unix TimeStamp format based on ... ... @@ -619,7 +619,7 @@ 619 619 So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25 620 620 621 621 622 -=== 2. 5.3 Set Device Time ===528 +=== 2.6.3 Set Device Time === 623 623 624 624 625 625 User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command. ... ... @@ -629,7 +629,7 @@ 629 629 (% 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.** 630 630 631 631 632 -=== 2. 5.4 Poll sensor value ===538 +=== 2.6.4 Poll sensor value === 633 633 634 634 635 635 Users can poll sensor values based on timestamps. Below is the downlink command. ... ... @@ -656,7 +656,7 @@ 656 656 ))) 657 657 658 658 659 -== 2. 6Frequency Plans ==565 +== 2.7 Frequency Plans == 660 660 661 661 662 662 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. ... ... @@ -664,9 +664,9 @@ 664 664 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]] 665 665 666 666 667 -== 2. 7LiDAR ToF Measurement ==573 +== 2.8 LiDAR ToF Measurement == 668 668 669 -=== 2. 7.1 Principle of Distance Measurement ===575 +=== 2.8.1 Principle of Distance Measurement === 670 670 671 671 672 672 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. ... ... @@ -674,7 +674,7 @@ 674 674 [[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"]] 675 675 676 676 677 -=== 2. 7.2 Distance Measurement Characteristics ===583 +=== 2.8.2 Distance Measurement Characteristics === 678 678 679 679 680 680 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: ... ... @@ -712,7 +712,7 @@ 712 712 ))) 713 713 714 714 715 -=== 2. 7.3 Notice of usage ===621 +=== 2.8.3 Notice of usage === 716 716 717 717 718 718 Possible invalid /wrong reading for LiDAR ToF tech: ... ... @@ -724,7 +724,7 @@ 724 724 725 725 726 726 727 -=== 2. 7.4 Reflectivity of different objects ===633 +=== 2.8.4 Reflectivity of different objects === 728 728 729 729 730 730 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:379px" %) ... ... @@ -835,9 +835,9 @@ 835 835 === 3.3.2 Set Interrupt Mode === 836 836 837 837 838 -Feature, Set Interrupt mode for pinofGPIO_EXTI.744 +Feature, Set Interrupt mode for PA8 of pin. 839 839 840 -When AT+INTMOD=0 is set, GPIO_EXTIis used as a digital input port.746 +When AT+INTMOD=0 is set, PA8 is used as a digital input port. 841 841 842 842 (% style="color:blue" %)**AT Command: AT+INTMOD** 843 843 ... ... @@ -848,11 +848,7 @@ 848 848 OK 849 849 the mode is 0 =Disable Interrupt 850 850 ))) 851 -|(% style="width:154px" %)((( 852 -AT+INTMOD=2 853 - 854 -(default) 855 -)))|(% style="width:196px" %)((( 757 +|(% style="width:154px" %)AT+INTMOD=2|(% style="width:196px" %)((( 856 856 Set Transmit Interval 857 857 0. (Disable Interrupt), 858 858 ~1. (Trigger by rising and falling edge) ... ... @@ -874,7 +874,7 @@ 874 874 875 875 === 3.3.3 Set Power Output Duration === 876 876 877 -Control the output duration 3V3 (pinof VBAT_OUT). Before each sampling, device will779 +Control the output duration 3V3 . Before each sampling, device will 878 878 879 879 ~1. first enable the power output to external sensor, 880 880 ... ... @@ -890,7 +890,6 @@ 890 890 OK 891 891 |(% style="width:154px" %)AT+3V3T=1000|(% style="width:196px" %)Close after a delay of 1000 milliseconds.|(% style="width:157px" %)OK 892 892 |(% style="width:154px" %)AT+3V3T=0|(% style="width:196px" %)Always turn on the power supply of 3V3 pin.|(% style="width:157px" %)OK 893 -|(% style="width:154px" %)AT+3V3T=65535|(% style="width:196px" %)Always turn off the power supply of 3V3 pin.|(% style="width:157px" %)OK 894 894 895 895 (% style="color:blue" %)**Downlink Command: 0x07**(%%) 896 896 Format: Command Code (0x07) followed by 3 bytes. ... ... @@ -899,7 +899,6 @@ 899 899 900 900 * Example 1: Downlink Payload: 07 01 00 00 **~-~-->** AT+3V3T=0 901 901 * Example 2: Downlink Payload: 07 01 01 F4 **~-~-->** AT+3V3T=500 902 -* Example 3: Downlink Payload: 07 01 FF FF **~-~-->** AT+3V3T=65535 903 903 904 904 905 905
- 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