Last modified by Mengting Qiu on 2025/07/08 11:11
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -375,7 +375,6 @@ 375 375 376 376 * Example 2: 0x0B49 = 2889mV 377 377 378 - 379 379 (% class="wikigeneratedid" id="HDS18B20Temperaturesensor" %) 380 380 (% style="color:blue" %)**DS18B20 Temperature sensor:** 381 381 ... ... @@ -447,7 +447,6 @@ 447 447 * If byte[0] & 0x01 = 0x00: Normal uplink packet 448 448 * If byte[0] & 0x01 = 0x01: Interrupt-generated uplink packet 449 449 450 - 451 451 (% class="wikigeneratedid" id="HLiDARtemp" %) 452 452 (% style="color:blue" %)**LiDAR temp:** 453 453 ... ... @@ -458,7 +458,6 @@ 458 458 * If the payload is 1C(H), then ((1C << 24) >> 24) = 26 (decimal), so **LiDAR temp = 26 °C** 459 459 * If the payload is F2(H), then ((F2 << 24) >> 24) = -14 (decimal), so **LiDAR temp = -14 °C** 460 460 461 - 462 462 (% class="wikigeneratedid" id="HMessageType" %) 463 463 (% style="color:blue" %)**Message Type:** 464 464 ... ... @@ -557,16 +557,16 @@ 557 557 [[image:image-20241009105513-2.png]] 558 558 559 559 560 -=== 2.3.4 Uplink after automatic cleaning, FP ORT~=6 (Since firmware v1.2) ===557 +=== 2.3.4 Uplink after automatic cleaning, FPort~=6 (Since firmware v1.2) === 561 561 562 562 563 -The LDS25-LB/LS sends this uplink after the clean uplinkfunction is enabled.560 +The LDS25-LB/LS sends this uplink after the automatic cleaning function is enabled. 564 564 565 -(% style="color:red" %)**Note: Effective only if the d parameter is set to 1, [[AT+REMODUST=a,b,c,1>>]]**562 +(% style="color:red" %)**Note: This is effective only if the d parameter is set to 1 in the command, [[AT+REMODUST=a,b,c,1>>]]** 566 566 567 - Intheexample ofAT+REMODUST=1,1,5,**1**, LDS25-LB/LS willbe cleaned once every 5 minutes and **send an uplink** afterthe cleaning is complete.564 +For example, with the command AT+REMODUST=1,1,5,**1**, the LDS25-LB/LS will perform a cleaning cycle every 5 minutes and **send an uplink** after each cleaning is complete. 568 568 569 - UplinkPayloadtotals 8 bytes.566 +The uplink payload is 8 bytes in total. 570 570 571 571 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 572 572 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)((( ... ... @@ -583,50 +583,52 @@ 583 583 584 584 This field displays the current cleaning mode. 585 585 586 -0x01: "1" ,Wiper cleaning isstarted at regular intervals583 +0x01: "1" - Wiper cleaning is activated at regular intervals 587 587 588 588 589 589 (% style="color:blue" %)**Wiper_clean_times** 590 590 591 -This field shows the number of Wiper cleanings, with each round trip count ing1.588 +This field shows the number of Wiper cleanings, with each round trip counted as 1. 592 592 593 -Ex1: 0x01(H) = once590 +**Example 1**: 0x01(H) = 1 time 594 594 595 -Ex2: 0x03(H) = 3 times 592 +**Example 2**: 0x03(H) = 3 times 596 596 597 597 598 598 (% style="color:blue" %)**Wiper_clean_interval** 599 599 600 -This field shows the automatic cleaning interval. (Unit: minute) 597 +This field shows the automatic cleaning interval. (Unit: minutes) 601 601 602 -Ex1: 0x00 05(H) =5 minutes 599 +Example 1: 0x00 05(H) = 5 minutes 603 603 604 -Ex2: 0x03 84(H) = 900 minutes = 15hours 601 +Example 2: 0x03 84(H) = 900 minutes = 15hours 605 605 606 606 607 607 (% style="color:blue" %)**Wiper_last_clean_time** 608 608 609 -This field shows the last automatic cleaning start time.606 +This field shows the start time of the last automatic cleaning. 610 610 611 -Unit Time StampExample: 67B45050(H) = 1739870288(D)608 +**Unit**: Timestamp 612 612 613 - Put the decimalvalueinto this link(https://www.epochconverter.com/[[https://www.epochconverter.com/]])toget the time.610 +**Example**: 67B45050(H) = 1739870288(D) 614 614 612 +Paste the decimal value into this converter (https://www.epochconverter.com/[[https://www.epochconverter.com/]]) to get the human-readable time. 615 615 616 -=== 2.3.5 Decode payload in The Things Network === 617 617 615 +=== 2.3.5 Decode payload in The Things Stack === 618 618 619 -While using TTN network, you can add the payload format to decode the payload. 620 620 618 +When using The Things Stack (TTS), you can add a payload formatter to decode the payload. 619 + 621 621 [[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"]] 622 622 623 623 624 624 ((( 625 -The payload decoder function for TT Nis here:624 +The payload decoder function for The Things Stack is available here: 626 626 ))) 627 627 628 628 ((( 629 -LDS25-LB/LS TT NPayload Decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]628 +LDS25-LB/LS TTS Payload Decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]] 630 630 ))) 631 631 632 632 ... ... @@ -683,16 +683,16 @@ 683 683 b) LDS25-LB/LS will send data in **CONFIRMED Mode** when PNACKMD=1, but LDS25-LB/LS won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink if LDS25-LB/LS gets a ACK, LDS25-LB/LS will consider there is a network connection and resend all NONE-ACK messages. 684 684 ))) 685 685 686 -=== 2.5.2 Unix Time Stamp ===685 +=== 2.5.2 Unix Timestamp === 687 687 688 688 689 -LDS25-LB/LS uses Unix Time Stamp format based on688 +LDS25-LB/LS uses Unix Timestamp format based on the following: 690 690 691 691 [[image:image-20250403170642-8.jpeg]] 692 692 693 - Usercan get thistime from link: [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :692 +You can get the Unix timestamp from the following link: [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] : 694 694 695 -Below is the converter example694 +Below is an example using the Code Beauty - Decimal to Hex converter. 696 696 697 697 [[image:image-20250403170700-9.jpeg]] 698 698 ... ... @@ -703,13 +703,18 @@ 703 703 === 2.5.3 Set Device Time === 704 704 705 705 706 - Userneed to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable syncmevia MAC command.705 +You need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable time synchronization via MAC command. 707 707 708 -Once LDS25-LB/LS JoinedLoRaWAN network, it will sendtheMAC command (DeviceTimeReq)and the server will replywith(DeviceTimeAns)tosend the current time to LDS25-LB/LS. IfLDS25-LB/LSfails togetthe time from the server,LDS25-LB/LSwill use theinternal time and wait for next time request(AT+SYNCTDC to set thetimerequestperiod,defaultis10 days).707 +Once the **LDS25-LB/LS** joins a LoRaWAN network, it will send a MAC command (DeviceTimeReq). The server will respond with a DeviceTimeAns command to provide the current time to the LDS25-LB/LS. If the device fails to receive the time from the server, it will use its internal time and wait for the next time request. The request interval can be set using the AT+SYNCTDC command (default: 10 days). 709 709 710 -(% style="color:red" %)**Note: LoRaWAN Server needtosupport 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.**709 +(% style="color:red" %)**Note: LoRaWAN Network Server must support LoRaWAN v1.0.3 (MAC v1.0.3) or higher to support this MAC command feature.** 711 711 711 +* (% style="color:red" %)**Supported: ChirpStack, TTN v3, Loriot** 712 +* (% style="color:red" %)**Not supported: TTN v2 .** 712 712 714 +(% style="color:red" %)**If the server does not support this command, it will discard uplink packets containing the time request. As a result, the user will lose that packet when using TTN v2 with SYNCMOD=1.** 715 + 716 + 713 713 === 2.5.4 Poll sensor value === 714 714 715 715