Skip to Content
Last modified by Mengting Qiu on 2023/12/14 11:15
From version 84.2
edited by Xiaoling
on 2023/06/15 15:30
Change comment: There is no comment for this version
To version 94.1
edited by Saxer Lin
on 2023/08/05 14:43
Change comment: Uploaded new attachment "image-20230805144259-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Saxer
Content
... ... @@ -130,7 +130,7 @@
130 130  
131 131  
132 132  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
133 -|=(% style="width: 167px;background-color:#D9E2F3;color:#0070C0" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 225px;background-color:#D9E2F3;color:#0070C0" %)**Action**
133 +|=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 225px;background-color:#4F81BD;color:white" %)**Action**
134 134  |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((
135 135  If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once.
136 136  Meanwhile, BLE module will be active and user can connect via BLE to configure device.
... ... @@ -242,31 +242,101 @@
242 242  
243 243  == 2.3 ​Uplink Payload ==
244 244  
245 +=== 2.3.1 Device Status, FPORT~=5 ===
245 245  
246 -(((
247 -LDS12-LB will uplink payload via LoRaWAN with below payload format: 
248 -)))
249 249  
248 +Users can use the downlink command(**0x26 01**) to ask LDS12-LB to send device configure detail, include device configure status. LDS12-LB will uplink a payload via FPort=5 to server.
249 +
250 +The Payload format is as below.
251 +
252 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
253 +|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
254 +**Size(bytes)**
255 +)))|=(% style="width: 100px; background-color: #4F81BD;color:white;" %)**1**|=(% style="width: 100px; background-color: #4F81BD;color:white;" %)**2**|=(% style="background-color: #4F81BD;color:white; width: 100px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 100px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 50px;" %)**2**
256 +|(% style="width:62.5px" %)Value|(% style="width:110px" %)Sensor Model|(% style="width:48px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:91px" %)Sub-band|(% style="width:60px" %)BAT
257 +
258 +Example parse in TTNv3
259 +
260 +[[image:image-20230805103904-1.png||height="131" width="711"]]
261 +
262 +(% style="color:blue" %)**Sensor Model**(%%): For LDS12-LB, this value is 0x24
263 +
264 +(% style="color:blue" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
265 +
266 +(% style="color:blue" %)**Frequency Band**:
267 +
268 +0x01: EU868
269 +
270 +0x02: US915
271 +
272 +0x03: IN865
273 +
274 +0x04: AU915
275 +
276 +0x05: KZ865
277 +
278 +0x06: RU864
279 +
280 +0x07: AS923
281 +
282 +0x08: AS923-1
283 +
284 +0x09: AS923-2
285 +
286 +0x0a: AS923-3
287 +
288 +0x0b: CN470
289 +
290 +0x0c: EU433
291 +
292 +0x0d: KR920
293 +
294 +0x0e: MA869
295 +
296 +(% style="color:blue" %)**Sub-Band**:
297 +
298 +AU915 and US915:value 0x00 ~~ 0x08
299 +
300 +CN470: value 0x0B ~~ 0x0C
301 +
302 +Other Bands: Always 0x00
303 +
304 +(% style="color:blue" %)**Battery Info**:
305 +
306 +Check the battery voltage.
307 +
308 +Ex1: 0x0B45 = 2885mV
309 +
310 +Ex2: 0x0B49 = 2889mV
311 +
312 +
313 +=== 2.3.2 Uplink Payload, FPORT~=2 ===
314 +
315 +
250 250  (((
251 -Uplink payload includes in total 11 bytes.
317 +LDS12-LB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LDS12-LB will:
318 +
319 +periodically send this uplink every 20 minutes, this interval [[can be changed>>https://111]].
320 +
321 +Uplink Payload totals 11 bytes.
252 252  )))
253 253  
254 254  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
255 -|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)(((
325 +|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
256 256  **Size(bytes)**
257 -)))|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**
258 -|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1BatteryInfo"]]|(% style="width:62.5px" %)(((
259 -[[Temperature DS18B20>>||anchor="H2.3.2DS18B20Temperaturesensor"]]
260 -)))|[[Distance>>||anchor="H2.3.3Distance"]]|[[Distance signal strength>>||anchor="H2.3.4Distancesignalstrength"]]|(((
261 -[[Interrupt flag>>||anchor="H2.3.5InterruptPin"]]
262 -)))|[[LiDAR temp>>||anchor="H2.3.6LiDARtemp"]]|(((
263 -[[Message Type>>||anchor="H2.3.7MessageType"]]
327 +)))|=(% style="width: 30px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**2**|=(% 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: 80px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 70px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 70px;" %)**1**
328 +|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)[[BAT>>||anchor="HBatteryInfo"]]|(% style="width:62.5px" %)(((
329 +[[Temperature DS18B20>>||anchor="HDS18B20Temperaturesensor"]]
330 +)))|[[Distance>>||anchor="HDistance"]]|[[Distance signal strength>>||anchor="HDistancesignalstrength"]]|(% style="width:122px" %)(((
331 +[[Interrupt flag & Interrupt_level>>||anchor="HInterruptPin26A0InterruptLevel"]]
332 +)))|(% style="width:54px" %)[[LiDAR temp>>||anchor="HLiDARtemp"]]|(% style="width:96px" %)(((
333 +[[Message Type>>||anchor="HMessageType"]]
264 264  )))
265 265  
266 -[[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"]]
336 +[[image:image-20230805104104-2.png||height="136" width="754"]]
267 267  
268 268  
269 -=== 2.3.1 Battery Info ===
339 +==== (% style="color:blue" %)**Battery Info**(%%) ====
270 270  
271 271  
272 272  Check the battery voltage for LDS12-LB.
... ... @@ -276,7 +276,7 @@
276 276  Ex2: 0x0B49 = 2889mV
277 277  
278 278  
279 -=== 2.3.2 DS18B20 Temperature sensor ===
349 +==== (% style="color:blue" %)**DS18B20 Temperature sensor**(%%) ====
280 280  
281 281  
282 282  This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
... ... @@ -289,7 +289,7 @@
289 289  If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
290 290  
291 291  
292 -=== 2.3.3 Distance ===
362 +==== (% style="color:blue" %)**Distance**(%%) ====
293 293  
294 294  
295 295  Represents the distance value of the measurement output, the default unit is cm, and the value range parsed as a decimal number is 0-1200. In actual use, when the signal strength value Strength.
... ... @@ -300,7 +300,7 @@
300 300  If the data you get from the register is 0x0B 0xEA, the distance between the sensor and the measured object is 0BEA(H) = 3050 (D)/10 = 305cm.
301 301  
302 302  
303 -=== 2.3.4 Distance signal strength ===
373 +==== (% style="color:blue" %)**Distance signal strength**(%%) ====
304 304  
305 305  
306 306  Refers to the signal strength, the default output value will be between 0-65535. When the distance measurement gear is fixed, the farther the distance measurement is, the lower the signal strength; the lower the target reflectivity, the lower the signal strength. When Strength is greater than 100 and not equal to 65535, the measured value of Dist is considered credible.
... ... @@ -313,7 +313,7 @@
313 313  Customers can judge whether they need to adjust the environment based on the signal strength.
314 314  
315 315  
316 -=== 2.3.5 Interrupt Pin ===
386 +==== (% style="color:blue" %)**Interrupt Pin & Interrupt Level**(%%) ====
317 317  
318 318  
319 319  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.
... ... @@ -327,7 +327,7 @@
327 327  0x01: Interrupt Uplink Packet.
328 328  
329 329  
330 -=== 2.3.6 LiDAR temp ===
400 +==== (% style="color:blue" %)**LiDAR temp**(%%) ====
331 331  
332 332  
333 333  Characterize the internal temperature value of the sensor.
... ... @@ -337,7 +337,7 @@
337 337  If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
338 338  
339 339  
340 -=== 2.3.7 Message Type ===
410 +==== (% style="color:blue" %)**Message Type**(%%) ====
341 341  
342 342  
343 343  (((
... ... @@ -354,7 +354,7 @@
354 354  |(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.ConfigureLDS12-LB"]]
355 355  
356 356  
357 -=== 2.3.8 Decode payload in The Things Network ===
427 +=== 2.3.3 Decode payload in The Things Network ===
358 358  
359 359  
360 360  While using TTN network, you can add the payload format to decode the payload.
... ... @@ -371,15 +371,9 @@
371 371  )))
372 372  
373 373  
374 -== 2.4 Uplink Interval ==
444 +== 2.4 ​Show Data in DataCake IoT Server ==
375 375  
376 376  
377 -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"]]
378 -
379 -
380 -== 2.5 ​Show Data in DataCake IoT Server ==
381 -
382 -
383 383  (((
384 384  [[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:
385 385  )))
... ... @@ -412,13 +412,13 @@
412 412  [[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"]]
413 413  
414 414  
415 -== 2.6 Datalog Feature ==
479 +== 2.5 Datalog Feature ==
416 416  
417 417  
418 418  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.
419 419  
420 420  
421 -=== 2.6.1 Ways to get datalog via LoRaWAN ===
485 +=== 2.5.1 Ways to get datalog via LoRaWAN ===
422 422  
423 423  
424 424  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.
... ... @@ -435,7 +435,7 @@
435 435  [[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"]]
436 436  
437 437  
438 -=== 2.6.2 Unix TimeStamp ===
502 +=== 2.5.2 Unix TimeStamp ===
439 439  
440 440  
441 441  LDS12-LB uses Unix TimeStamp format based on
... ... @@ -452,7 +452,7 @@
452 452  So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
453 453  
454 454  
455 -=== 2.6.3 Set Device Time ===
519 +=== 2.5.3 Set Device Time ===
456 456  
457 457  
458 458  User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
... ... @@ -462,13 +462,13 @@
462 462  (% 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.**
463 463  
464 464  
465 -=== 2.6.4 Poll sensor value ===
529 +=== 2.5.4 Poll sensor value ===
466 466  
467 467  
468 468  Users can poll sensor values based on timestamps. Below is the downlink command.
469 469  
470 470  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:425.818px" %)
471 -|(% colspan="4" style="background-color:#d9e2f3; color:#0070c0; width:423px" %)**Downlink Command to poll Open/Close status (0x31)**
535 +|(% colspan="4" style="background-color:#4f81bd; color:white; width:423px" %)**Downlink Command to poll Open/Close status (0x31)**
472 472  |(% style="width:58px" %)**1byte**|(% style="width:127px" %)**4bytes**|(% style="width:124px" %)**4bytes**|(% style="width:114px" %)**1byte**
473 473  |(% style="width:58px" %)31|(% style="width:127px" %)Timestamp start|(% style="width:124px" %)Timestamp end|(% style="width:114px" %)Uplink Interval
474 474  
... ... @@ -489,7 +489,7 @@
489 489  )))
490 490  
491 491  
492 -== 2.7 Frequency Plans ==
556 +== 2.6 Frequency Plans ==
493 493  
494 494  
495 495  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.
... ... @@ -497,9 +497,9 @@
497 497  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]]
498 498  
499 499  
500 -== 2.8 LiDAR ToF Measurement ==
564 +== 2.7 LiDAR ToF Measurement ==
501 501  
502 -=== 2.8.1 Principle of Distance Measurement ===
566 +=== 2.7.1 Principle of Distance Measurement ===
503 503  
504 504  
505 505  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.
... ... @@ -507,7 +507,7 @@
507 507  [[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"]]
508 508  
509 509  
510 -=== 2.8.2 Distance Measurement Characteristics ===
574 +=== 2.7.2 Distance Measurement Characteristics ===
511 511  
512 512  
513 513  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:
... ... @@ -545,7 +545,7 @@
545 545  )))
546 546  
547 547  
548 -=== 2.8.3 Notice of usage ===
612 +=== 2.7.3 Notice of usage ===
549 549  
550 550  
551 551  Possible invalid /wrong reading for LiDAR ToF tech:
... ... @@ -556,7 +556,7 @@
556 556  * The sensor window is made by Acrylic. Don't touch it with alcohol material. This will destroy the sensor window.
557 557  
558 558  
559 -=== 2.8.4  Reflectivity of different objects ===
623 +=== 2.7.4  Reflectivity of different objects ===
560 560  
561 561  
562 562  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:379px" %)
... ... @@ -697,83 +697,34 @@
697 697  * Example 2: Downlink Payload: 06000003  ~/~/  Set the interrupt mode to rising edge trigger
698 698  
699 699  
700 -=== 3.3.3 Get Firmware Version Info ===
764 +=== 3.3.3  Set Power Output Duration ===
701 701  
766 +Control the output duration 3V3 . Before each sampling, device will
702 702  
703 -Feature: use downlink to get firmware version.
768 +~1. first enable the power output to external sensor,
704 704  
705 -(% style="color:blue" %)**Downlink Command: 0x26**
770 +2. keep it on as per duration, read sensor value and construct uplink payload
706 706  
707 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:492px" %)
708 -|(% style="background-color:#4f81bd; color:white; width:191px" %)**Downlink Control Type**|(% style="background-color:#4f81bd; color:white; width:57px" %)**FPort**|(% style="background-color:#4f81bd; color:white; width:91px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:153px" %)**Downlink payload size(bytes)**
709 -|(% style="width:191px" %)Get Firmware Version Info|(% style="width:57px" %)Any|(% style="width:91px" %)26|(% style="width:151px" %)2
772 +3. final, close the power output.
710 710  
711 -* Reply to the confirmation package: 26 01
712 -* Reply to non-confirmed packet: 26 00
774 +(% style="color:blue" %)**AT Command: AT+3V3T**
713 713  
714 -Device will send an uplink after got this downlink command. With below payload:
776 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
777 +|=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 197px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Response**
778 +|(% style="width:154px" %)AT+3V3T=?|(% style="width:196px" %)Show 3V3 open time.|(% style="width:157px" %)0 (default)
779 +OK
780 +|(% style="width:154px" %)AT+3V3T=1000|(% style="width:196px" %)Close after a delay of 1000 milliseconds.|(% style="width:157px" %)OK
781 +|(% style="width:154px" %)AT+3V3T=0|(% style="width:196px" %)Always turn on the power supply of 3V3 pin.|(% style="width:157px" %)OK
715 715  
716 -Configures info payload:
783 +(% style="color:blue" %)**Downlink Command: 0x07**(%%)
784 +Format: Command Code (0x07) followed by 3 bytes.
717 717  
718 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
719 -|=(% style="background-color:#4F81BD;color:white" %)(((
720 -**Size(bytes)**
721 -)))|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**5**|=(% style="background-color:#4F81BD;color:white" %)**1**
722 -|**Value**|Software Type|(((
723 -Frequency Band
724 -)))|Sub-band|(((
725 -Firmware Version
726 -)))|Sensor Type|Reserve|(((
727 -[[Message Type>>||anchor="H2.3.7MessageType"]]
728 -Always 0x02
729 -)))
786 +The first byte is 01,the second and third bytes are the time to turn on.
730 730  
731 -(% style="color:#037691" %)**Software Type**(%%): Always 0x03 for LLDS12
788 +* Example 1: Downlink Payload: 07 01 00 00  **~-~-->**  AT+3V3T=0
789 +* Example 2: Downlink Payload: 07 01 01 F4  **~-~-->**  AT+3V3T=500
732 732  
733 -(% style="color:#037691" %)**Frequency Band**:
734 734  
735 -*0x01: EU868
736 -
737 -*0x02: US915
738 -
739 -*0x03: IN865
740 -
741 -*0x04: AU915
742 -
743 -*0x05: KZ865
744 -
745 -*0x06: RU864
746 -
747 -*0x07: AS923
748 -
749 -*0x08: AS923-1
750 -
751 -*0x09: AS923-2
752 -
753 -*0xa0: AS923-3
754 -
755 -
756 -(% style="color:#037691" %)**Sub-Band**(%%): value 0x00 ~~ 0x08
757 -
758 -(% style="color:#037691" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
759 -
760 -(% style="color:#037691" %)**Sensor Type**:
761 -
762 -0x01: LSE01
763 -
764 -0x02: LDDS75
765 -
766 -0x03: LDDS20
767 -
768 -0x04: LLMS01
769 -
770 -0x05: LSPH01
771 -
772 -0x06: LSNPK01
773 -
774 -0x07: LLDS12
775 -
776 -
777 777  = 4. Battery & Power Consumption =
778 778  
779 779  
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