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, 5 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Saxer - 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"]] 159 159 159 +[[image:image-20230805144259-1.png||height="413" width="741"]] 160 160 161 161 == 1.9 Mechanical == 162 162 ... ... @@ -253,6 +253,8 @@ 253 253 254 254 Example parse in TTNv3 255 255 256 +[[image:image-20230805103904-1.png||height="131" width="711"]] 257 + 256 256 (% style="color:blue" %)**Sensor Model**(%%): For LDS12-LB, this value is 0x24 257 257 258 258 (% style="color:blue" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version ... ... @@ -308,11 +308,11 @@ 308 308 309 309 310 310 ((( 311 -LDS12-LB will uplink payload via LoRaWAN with below payload format: 312 -))) 313 +LDS12-LB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LDS12-LB will: 313 313 314 -((( 315 -Uplink payload includes in total 11 bytes. 315 +periodically send this uplink every 20 minutes, this interval [[can be changed>>http://8.211.40.43/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS12-LB_LoRaWAN_LiDAR_ToF_Distance_Sensor_User_Manual/#H3.3.1SetTransmitIntervalTime]]. 316 + 317 +Uplink Payload totals 11 bytes. 316 316 ))) 317 317 318 318 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -327,7 +327,7 @@ 327 327 [[Message Type>>||anchor="HMessageType"]] 328 328 ))) 329 329 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"]]332 +[[image:image-20230805104104-2.png||height="136" width="754"]] 331 331 332 332 333 333 ==== (% style="color:blue" %)**Battery Info**(%%) ==== ... ... @@ -382,7 +382,7 @@ 382 382 383 383 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. 384 384 385 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.8PinDefinitions"]]. 387 +Note: The Internet Pin is a separate pin in the screw terminal. See GPIO_EXTI of [[pin mapping>>||anchor="H1.8PinDefinitions"]]. 386 386 387 387 **Example:** 388 388 ... ... @@ -418,6 +418,68 @@ 418 418 |(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.ConfigureLDS12-LB"]] 419 419 420 420 423 +=== 2.3.3 Historical Water Flow Status, FPORT~=3 === 424 + 425 +LDS12-LB stores sensor values and users can retrieve these history values via the [[downlink command>>url:http://8.211.40.43/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SW3L-LB_LoRaWAN_Flow_Sensor_User_Manual/#H2.5DatalogFeature]]. 426 + 427 +The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time water flow status. 428 + 429 + 430 +* ((( 431 +Each data entry is 11 bytes and has the same structure as [[real time water flow status>>url:http://8.211.40.43/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SW3L-LB_LoRaWAN_Flow_Sensor_User_Manual/#H2.3.3A0WaterFlowValue2CUplinkFPORT3D2]], to save airtime and battery, LDS12-LB will send max bytes according to the current DR and Frequency bands. 432 +))) 433 + 434 +For example, in the US915 band, the max payload for different DR is: 435 + 436 +**a) DR0:** max is 11 bytes so one entry of data 437 + 438 +**b) DR1:** max is 53 bytes so devices will upload 4 entries of data (total 44 bytes) 439 + 440 +**c) DR2:** total payload includes 11 entries of data 441 + 442 +**d) DR3:** total payload includes 22 entries of data. 443 + 444 +If LDS12-LB doesn't have any data in the polling time. It will uplink 11 bytes of 0 445 + 446 + 447 +**Downlink:** 448 + 449 +0x31 64 CC 68 0C 64 CC 69 74 05 450 + 451 +[[image:image-20230805144936-2.png||height="113" width="746"]] 452 + 453 +**Uplink:** 454 + 455 +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 456 + 457 + 458 +**Parsed Value:** 459 + 460 +[DISTANCE , DISTANCE_SIGNAL_STRENGTH,LIDAR_TEMP,EXTI_STATUS , EXTI_FLAG , TIME] 461 + 462 + 463 +[360,176,30,High,True,2023-08-04 02:53:00], 464 + 465 +[355,168,30,Low,False,2023-08-04 02:53:29], 466 + 467 +[245,211,30,Low,False,2023-08-04 02:54:29], 468 + 469 +[57,700,30,Low,False,2023-08-04 02:55:29], 470 + 471 +[361,164,30,Low,True,2023-08-04 02:56:00], 472 + 473 +[337,184,30,Low,False,2023-08-04 02:56:40], 474 + 475 +[20,4458,30,Low,False,2023-08-04 02:57:40], 476 + 477 +[362,173,30,Low,False,2023-08-04 02:58:53], 478 + 479 + 480 +History read from serial port: 481 + 482 +[[image:image-20230805145056-3.png]] 483 + 484 + 421 421 === 2.3.3 Decode payload in The Things Network === 422 422 423 423 ... ... @@ -435,15 +435,9 @@ 435 435 ))) 436 436 437 437 438 -== 2.4 Uplink Interval==502 +== 2.4 Show Data in DataCake IoT Server == 439 439 440 440 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 - 447 447 ((( 448 448 [[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: 449 449 ))) ... ... @@ -476,13 +476,13 @@ 476 476 [[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"]] 477 477 478 478 479 -== 2. 6Datalog Feature ==537 +== 2.5 Datalog Feature == 480 480 481 481 482 482 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. 483 483 484 484 485 -=== 2. 6.1 Ways to get datalog via LoRaWAN ===543 +=== 2.5.1 Ways to get datalog via LoRaWAN === 486 486 487 487 488 488 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. ... ... @@ -499,7 +499,7 @@ 499 499 [[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"]] 500 500 501 501 502 -=== 2. 6.2 Unix TimeStamp ===560 +=== 2.5.2 Unix TimeStamp === 503 503 504 504 505 505 LDS12-LB uses Unix TimeStamp format based on ... ... @@ -516,7 +516,7 @@ 516 516 So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25 517 517 518 518 519 -=== 2. 6.3 Set Device Time ===577 +=== 2.5.3 Set Device Time === 520 520 521 521 522 522 User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command. ... ... @@ -526,7 +526,7 @@ 526 526 (% 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.** 527 527 528 528 529 -=== 2. 6.4 Poll sensor value ===587 +=== 2.5.4 Poll sensor value === 530 530 531 531 532 532 Users can poll sensor values based on timestamps. Below is the downlink command. ... ... @@ -553,7 +553,7 @@ 553 553 ))) 554 554 555 555 556 -== 2. 7Frequency Plans ==614 +== 2.6 Frequency Plans == 557 557 558 558 559 559 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. ... ... @@ -561,9 +561,9 @@ 561 561 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]] 562 562 563 563 564 -== 2. 8LiDAR ToF Measurement ==622 +== 2.7 LiDAR ToF Measurement == 565 565 566 -=== 2. 8.1 Principle of Distance Measurement ===624 +=== 2.7.1 Principle of Distance Measurement === 567 567 568 568 569 569 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. ... ... @@ -571,7 +571,7 @@ 571 571 [[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"]] 572 572 573 573 574 -=== 2. 8.2 Distance Measurement Characteristics ===632 +=== 2.7.2 Distance Measurement Characteristics === 575 575 576 576 577 577 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: ... ... @@ -609,7 +609,7 @@ 609 609 ))) 610 610 611 611 612 -=== 2. 8.3 Notice of usage ===670 +=== 2.7.3 Notice of usage === 613 613 614 614 615 615 Possible invalid /wrong reading for LiDAR ToF tech: ... ... @@ -619,7 +619,7 @@ 619 619 * The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe. 620 620 * The sensor window is made by Acrylic. Don't touch it with alcohol material. This will destroy the sensor window. 621 621 622 -=== 2. 8.4 Reflectivity of different objects ===680 +=== 2.7.4 Reflectivity of different objects === 623 623 624 624 625 625 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:379px" %) ... ... @@ -759,7 +759,7 @@ 759 759 760 760 === 3.3.3 Set Power Output Duration === 761 761 762 -Control the output duration 3V3 . Before each sampling, device will 820 +Control the output duration 3V3(pin of VBAT_OUT) . Before each sampling, device will 763 763 764 764 ~1. first enable the power output to external sensor, 765 765 ... ... @@ -775,6 +775,7 @@ 775 775 OK 776 776 |(% style="width:154px" %)AT+3V3T=1000|(% style="width:196px" %)Close after a delay of 1000 milliseconds.|(% style="width:157px" %)OK 777 777 |(% style="width:154px" %)AT+3V3T=0|(% style="width:196px" %)Always turn on the power supply of 3V3 pin.|(% style="width:157px" %)OK 836 +|(% style="width:154px" %)AT+3V3T=65535|(% style="width:196px" %)Always turn off the power supply of 3V3 pin.|(% style="width:157px" %)OK 778 778 779 779 (% style="color:blue" %)**Downlink Command: 0x07**(%%) 780 780 Format: Command Code (0x07) followed by 3 bytes. ... ... @@ -783,6 +783,7 @@ 783 783 784 784 * Example 1: Downlink Payload: 07 01 00 00 **~-~-->** AT+3V3T=0 785 785 * Example 2: Downlink Payload: 07 01 01 F4 **~-~-->** AT+3V3T=500 845 +* Example 3: Downlink Payload: 07 01 FF FF **~-~-->** AT+3V3T=65535 786 786 787 787 = 4. Battery & Power Consumption = 788 788
- image-20230805103904-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Saxer - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.9 KB - Content
- image-20230805104104-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Saxer - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.3 KB - Content
- image-20230805144259-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Saxer - Size
-
... ... @@ -1,0 +1,1 @@ 1 +872.7 KB - Content
- image-20230805144936-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Saxer - Size
-
... ... @@ -1,0 +1,1 @@ 1 +37.5 KB - Content
- image-20230805145056-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Saxer - Size
-
... ... @@ -1,0 +1,1 @@ 1 +30.7 KB - Content