Skip to Content
Last modified by Mengting Qiu on 2023/12/14 11:15
From version 109.12
edited by Xiaoling
on 2023/10/28 16:57
Change comment: There is no comment for this version
To version 84.2
edited by Xiaoling
on 2023/06/15 15:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -45,8 +45,8 @@
45 45  * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
46 46  * Ultra-low power consumption
47 47  * Laser technology for distance detection
48 -* Measure Distance: 0.1m~~12m
49 -* Accuracy :  ±5cm@(0.1-5m), ±1%@(5m-12m)
48 +* Measure Distance: 0.1m~~12m @ 90% Reflectivity
49 +* Accuracy :  ±5cm@(0.1-6m), ±1%@(6m-12m)
50 50  * Monitor Battery Level
51 51  * Support Bluetooth v5.1 and LoRaWAN remote configure
52 52  * Support wireless OTA update firmware
... ... @@ -70,8 +70,8 @@
70 70  * Measure Distance:
71 71  ** 0.1m ~~ 12m @ 90% Reflectivity
72 72  ** 0.1m ~~ 4m @ 10% Reflectivity
73 -* Accuracy : ±5cm@(0.1-5m), ±1%@(5m-12m)
74 -* Distance resolution : 1cm
73 +* Accuracy : ±5cm@(0.1-6m), ±1%@(6m-12m)
74 +* Distance resolution : 5mm
75 75  * Ambient light immunity : 70klux
76 76  * Enclosure rating : IP65
77 77  * Light source : LED
... ... @@ -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:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 225px;background-color:#4F81BD;color:white" %)**Action**
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**
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.
... ... @@ -159,8 +159,8 @@
159 159  
160 160  == 1.8 Pin Definitions ==
161 161  
162 +[[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"]]
162 162  
163 -[[image:image-20230805144259-1.png||height="413" width="741"]]
164 164  
165 165  == 1.9 Mechanical ==
166 166  
... ... @@ -242,101 +242,31 @@
242 242  
243 243  == 2.3 ​Uplink Payload ==
244 244  
245 -=== 2.3.1 Device Status, FPORT~=5 ===
246 246  
247 -
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 -
316 316  (((
317 -LDS12-LB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LDS12-LB will:
247 +LDS12-LB will uplink payload via LoRaWAN with below payload format: 
248 +)))
318 318  
319 -periodically send this uplink every 20 minutes, this interval [[can be changed>>||anchor="H3.3.1SetTransmitIntervalTime"]].
320 -
321 -Uplink Payload totals 11 bytes.
250 +(((
251 +Uplink payload includes in total 11 bytes.
322 322  )))
323 323  
324 324  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
325 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
255 +|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)(((
326 326  **Size(bytes)**
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"]]
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"]]
334 334  )))
335 335  
336 -[[image:image-20230805104104-2.png||height="136" width="754"]]
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"]]
337 337  
338 338  
339 -==== (% style="color:blue" %)**Battery Info**(%%) ====
269 +=== 2.3.1 Battery Info ===
340 340  
341 341  
342 342  Check the battery voltage for LDS12-LB.
... ... @@ -346,7 +346,7 @@
346 346  Ex2: 0x0B49 = 2889mV
347 347  
348 348  
349 -==== (% style="color:blue" %)**DS18B20 Temperature sensor**(%%) ====
279 +=== 2.3.2 DS18B20 Temperature sensor ===
350 350  
351 351  
352 352  This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
... ... @@ -359,7 +359,7 @@
359 359  If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
360 360  
361 361  
362 -==== (% style="color:blue" %)**Distance**(%%) ====
292 +=== 2.3.3 Distance ===
363 363  
364 364  
365 365  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.
... ... @@ -370,7 +370,7 @@
370 370  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.
371 371  
372 372  
373 -==== (% style="color:blue" %)**Distance signal strength**(%%) ====
303 +=== 2.3.4 Distance signal strength ===
374 374  
375 375  
376 376  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.
... ... @@ -383,36 +383,21 @@
383 383  Customers can judge whether they need to adjust the environment based on the signal strength.
384 384  
385 385  
386 -**1) When the sensor detects valid data:**
316 +=== 2.3.5 Interrupt Pin ===
387 387  
388 -[[image:image-20230805155335-1.png||height="145" width="724"]]
389 389  
390 -
391 -**2) When the sensor detects invalid data:**
392 -
393 -[[image:image-20230805155428-2.png||height="139" width="726"]]
394 -
395 -
396 -**3) When the sensor is not connected:**
397 -
398 -[[image:image-20230805155515-3.png||height="143" width="725"]]
399 -
400 -
401 -==== (% style="color:blue" %)**Interrupt Pin & Interrupt Level**(%%) ====
402 -
403 -
404 404  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.
405 405  
406 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.8PinDefinitions"]] of GPIO_EXTI .
321 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.8PinDefinitions"]].
407 407  
408 408  **Example:**
409 409  
410 -If byte[0]&0x01=0x00 : Normal uplink packet.
325 +0x00: Normal uplink packet.
411 411  
412 -If byte[0]&0x01=0x01 : Interrupt Uplink Packet.
327 +0x01: Interrupt Uplink Packet.
413 413  
414 414  
415 -==== (% style="color:blue" %)**LiDAR temp**(%%) ====
330 +=== 2.3.6 LiDAR temp ===
416 416  
417 417  
418 418  Characterize the internal temperature value of the sensor.
... ... @@ -422,7 +422,7 @@
422 422  If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
423 423  
424 424  
425 -==== (% style="color:blue" %)**Message Type**(%%) ====
340 +=== 2.3.7 Message Type ===
426 426  
427 427  
428 428  (((
... ... @@ -435,97 +435,13 @@
435 435  
436 436  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:499px" %)
437 437  |=(% 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**
438 -|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)Normal Uplink Payload
439 -|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)Configure Info Payload
353 +|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]
354 +|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.ConfigureLDS12-LB"]]
440 440  
441 -[[image:image-20230805150315-4.png||height="233" width="723"]]
442 442  
357 +=== 2.3.8 Decode payload in The Things Network ===
443 443  
444 -=== 2.3.3 Historical measuring distance, FPORT~=3 ===
445 445  
446 -
447 -LDS12-LB stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.5.4Pollsensorvalue"]].
448 -
449 -The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time measuring distance.
450 -
451 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
452 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
453 -**Size(bytes)**
454 -)))|=(% 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
455 -|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)Interrupt flag & Interrupt_level|(% style="width:62.5px" %)(((
456 -Reserve(0xFF)
457 -)))|Distance|Distance signal strength|(% style="width:88px" %)(((
458 -LiDAR temp
459 -)))|(% style="width:85px" %)Unix TimeStamp
460 -
461 -**Interrupt flag & Interrupt level:**
462 -
463 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:480px" %)
464 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
465 -**Size(bit)**
466 -)))|=(% 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**
467 -|(% 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" %)(((
468 -Interrupt flag
469 -)))
470 -
471 -* (((
472 -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.
473 -)))
474 -
475 -For example, in the US915 band, the max payload for different DR is:
476 -
477 -**a) DR0:** max is 11 bytes so one entry of data
478 -
479 -**b) DR1:** max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
480 -
481 -**c) DR2:** total payload includes 11 entries of data
482 -
483 -**d) DR3:** total payload includes 22 entries of data.
484 -
485 -If LDS12-LB doesn't have any data in the polling time. It will uplink 11 bytes of 0
486 -
487 -
488 -**Downlink:**
489 -
490 -0x31 64 CC 68 0C 64 CC 69 74 05
491 -
492 -[[image:image-20230805144936-2.png||height="113" width="746"]]
493 -
494 -**Uplink:**
495 -
496 -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
497 -
498 -
499 -**Parsed Value:**
500 -
501 -[DISTANCE , DISTANCE_SIGNAL_STRENGTH，LIDAR_TEMP，EXTI_STATUS , EXTI_FLAG , TIME]
502 -
503 -
504 -[360,176,30,High,True,2023-08-04 02:53:00],
505 -
506 -[355,168,30,Low,False,2023-08-04 02:53:29],
507 -
508 -[245,211,30,Low,False,2023-08-04 02:54:29],
509 -
510 -[57,700,30,Low,False,2023-08-04 02:55:29],
511 -
512 -[361,164,30,Low,True,2023-08-04 02:56:00],
513 -
514 -[337,184,30,Low,False,2023-08-04 02:56:40],
515 -
516 -[20,4458,30,Low,False,2023-08-04 02:57:40],
517 -
518 -[362,173,30,Low,False,2023-08-04 02:58:53],
519 -
520 -
521 -**History read from serial port：**
522 -
523 -[[image:image-20230805145056-3.png]]
524 -
525 -
526 -=== 2.3.4 Decode payload in The Things Network ===
527 -
528 -
529 529  While using TTN network, you can add the payload format to decode the payload.
530 530  
531 531  [[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"]]
... ... @@ -540,9 +540,15 @@
540 540  )))
541 541  
542 542  
543 -== 2.4 ​Show Data in DataCake IoT Server ==
374 +== 2.4 Uplink Interval ==
544 544  
545 545  
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 +
546 546  (((
547 547  [[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:
548 548  )))
... ... @@ -575,13 +575,13 @@
575 575  [[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"]]
576 576  
577 577  
578 -== 2.5 Datalog Feature ==
415 +== 2.6 Datalog Feature ==
579 579  
580 580  
581 581  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.
582 582  
583 583  
584 -=== 2.5.1 Ways to get datalog via LoRaWAN ===
421 +=== 2.6.1 Ways to get datalog via LoRaWAN ===
585 585  
586 586  
587 587  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.
... ... @@ -598,7 +598,7 @@
598 598  [[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"]]
599 599  
600 600  
601 -=== 2.5.2 Unix TimeStamp ===
438 +=== 2.6.2 Unix TimeStamp ===
602 602  
603 603  
604 604  LDS12-LB uses Unix TimeStamp format based on
... ... @@ -615,7 +615,7 @@
615 615  So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
616 616  
617 617  
618 -=== 2.5.3 Set Device Time ===
455 +=== 2.6.3 Set Device Time ===
619 619  
620 620  
621 621  User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
... ... @@ -625,13 +625,13 @@
625 625  (% 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.**
626 626  
627 627  
628 -=== 2.5.4 Poll sensor value ===
465 +=== 2.6.4 Poll sensor value ===
629 629  
630 630  
631 631  Users can poll sensor values based on timestamps. Below is the downlink command.
632 632  
633 633  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:425.818px" %)
634 -|(% colspan="4" style="background-color:#4f81bd; color:white; width:423px" %)**Downlink Command to poll Open/Close status (0x31)**
471 +|(% colspan="4" style="background-color:#d9e2f3; color:#0070c0; width:423px" %)**Downlink Command to poll Open/Close status (0x31)**
635 635  |(% style="width:58px" %)**1byte**|(% style="width:127px" %)**4bytes**|(% style="width:124px" %)**4bytes**|(% style="width:114px" %)**1byte**
636 636  |(% style="width:58px" %)31|(% style="width:127px" %)Timestamp start|(% style="width:124px" %)Timestamp end|(% style="width:114px" %)Uplink Interval
637 637  
... ... @@ -652,7 +652,7 @@
652 652  )))
653 653  
654 654  
655 -== 2.6 Frequency Plans ==
492 +== 2.7 Frequency Plans ==
656 656  
657 657  
658 658  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.
... ... @@ -660,9 +660,9 @@
660 660  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]]
661 661  
662 662  
663 -== 2.7 LiDAR ToF Measurement ==
500 +== 2.8 LiDAR ToF Measurement ==
664 664  
665 -=== 2.7.1 Principle of Distance Measurement ===
502 +=== 2.8.1 Principle of Distance Measurement ===
666 666  
667 667  
668 668  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.
... ... @@ -670,7 +670,7 @@
670 670  [[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"]]
671 671  
672 672  
673 -=== 2.7.2 Distance Measurement Characteristics ===
510 +=== 2.8.2 Distance Measurement Characteristics ===
674 674  
675 675  
676 676  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:
... ... @@ -708,7 +708,7 @@
708 708  )))
709 709  
710 710  
711 -=== 2.7.3 Notice of usage ===
548 +=== 2.8.3 Notice of usage ===
712 712  
713 713  
714 714  Possible invalid /wrong reading for LiDAR ToF tech:
... ... @@ -719,7 +719,7 @@
719 719  * The sensor window is made by Acrylic. Don't touch it with alcohol material. This will destroy the sensor window.
720 720  
721 721  
722 -=== 2.7.4  Reflectivity of different objects ===
559 +=== 2.8.4  Reflectivity of different objects ===
723 723  
724 724  
725 725  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:379px" %)
... ... @@ -828,9 +828,9 @@
828 828  === 3.3.2 Set Interrupt Mode ===
829 829  
830 830  
831 -Feature, Set Interrupt mode for pin of GPIO_EXTI.
668 +Feature, Set Interrupt mode for PA8 of pin.
832 832  
833 -When AT+INTMOD=0 is set, GPIO_EXTI is used as a digital input port.
670 +When AT+INTMOD=0 is set, PA8 is used as a digital input port.
834 834  
835 835  (% style="color:blue" %)**AT Command: AT+INTMOD**
836 836  
... ... @@ -841,11 +841,7 @@
841 841  OK
842 842  the mode is 0 =Disable Interrupt
843 843  )))
844 -|(% style="width:154px" %)(((
845 -AT+INTMOD=2
846 -
847 -(default)
848 -)))|(% style="width:196px" %)(((
681 +|(% style="width:154px" %)AT+INTMOD=2|(% style="width:196px" %)(((
849 849  Set Transmit Interval
850 850  0. (Disable Interrupt),
851 851  ~1. (Trigger by rising and falling edge)
... ... @@ -864,36 +864,83 @@
864 864  * Example 2: Downlink Payload: 06000003  ~/~/  Set the interrupt mode to rising edge trigger
865 865  
866 866  
867 -=== 3.3.3  Set Power Output Duration ===
700 +=== 3.3.3 Get Firmware Version Info ===
868 868  
869 -Control the output duration 3V3(pin of VBAT_OUT) . Before each sampling, device will
870 870  
871 -~1. first enable the power output to external sensor,
703 +Feature: use downlink to get firmware version.
872 872  
873 -2. keep it on as per duration, read sensor value and construct uplink payload
705 +(% style="color:blue" %)**Downlink Command: 0x26**
874 874  
875 -3. final, close the power output.
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
876 876  
877 -(% style="color:blue" %)**AT Command: AT+3V3T**
711 +* Reply to the confirmation package: 26 01
712 +* Reply to non-confirmed packet: 26 00
878 878  
879 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
880 -|=(% 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**
881 -|(% style="width:154px" %)AT+3V3T=?|(% style="width:196px" %)Show 3V3 open time.|(% style="width:157px" %)0 (default)
882 -OK
883 -|(% style="width:154px" %)AT+3V3T=1000|(% style="width:196px" %)Close after a delay of 1000 milliseconds.|(% style="width:157px" %)OK
884 -|(% style="width:154px" %)AT+3V3T=0|(% style="width:196px" %)Always turn on the power supply of 3V3 pin.|(% style="width:157px" %)OK
885 -|(% style="width:154px" %)AT+3V3T=65535|(% style="width:196px" %)Always turn off the power supply of 3V3 pin.|(% style="width:157px" %)OK
714 +Device will send an uplink after got this downlink command. With below payload:
886 886  
887 -(% style="color:blue" %)**Downlink Command: 0x07**(%%)
888 -Format: Command Code (0x07) followed by 3 bytes.
716 +Configures info payload:
889 889  
890 -The first byte is 01,the second and third bytes are the time to turn on.
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 +)))
891 891  
892 -* Example 1: Downlink Payload: 07 01 00 00  **~-~-->**  AT+3V3T=0
893 -* Example 2: Downlink Payload: 07 01 01 F4  **~-~-->**  AT+3V3T=500
894 -* Example 3: Downlink Payload: 07 01 FF FF  **~-~-->**  AT+3V3T=65535
731 +(% style="color:#037691" %)**Software Type**(%%): Always 0x03 for LLDS12
895 895  
733 +(% style="color:#037691" %)**Frequency Band**:
896 896  
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 +
897 897  = 4. Battery & Power Consumption =
898 898  
899 899  
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