Skip to Content
Last modified by Mengting Qiu on 2023/12/14 11:15
From version 84.1
edited by Xiaoling
on 2023/06/15 15:30
Change comment: Uploaded new attachment "image-20230615153004-2.png", version {1}
To version 109.11
edited by Xiaoling
on 2023/08/07 09:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -35,7 +35,7 @@
35 35  
36 36  Each LDS12-LB is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on.
37 37  
38 -[[image:image-20230614162334-2.png||height="468" width="800"]]
38 +[[image:image-20230615152941-1.png||height="459" width="800"]]
39 39  
40 40  
41 41  == 1.2 ​Features ==
... ... @@ -133,7 +133,7 @@
133 133  
134 134  
135 135  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
136 -|=(% 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**
136 +|=(% 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**
137 137  |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((
138 138  If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once.
139 139  Meanwhile, BLE module will be active and user can connect via BLE to configure device.
... ... @@ -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"]]
167 167  
167 +[[image:image-20230805144259-1.png||height="413" width="741"]]
168 168  
169 169  == 1.9 Mechanical ==
170 170  
... ... @@ -200,7 +200,7 @@
200 200  
201 201  The LPS8v2 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.
202 202  
203 -[[image:image-20230614162359-3.png||height="468" width="800"]](% style="display:none" %)
203 +[[image:image-20230615153004-2.png||height="459" width="800"]](% style="display:none" %)
204 204  
205 205  
206 206  (% style="color:blue" %)**Step 1:**(%%) Create a device in TTN with the OTAA keys from LDS12-LB.
... ... @@ -246,31 +246,101 @@
246 246  
247 247  == 2.3 ​Uplink Payload ==
248 248  
249 +=== 2.3.1 Device Status, FPORT~=5 ===
249 249  
250 -(((
251 -LDS12-LB will uplink payload via LoRaWAN with below payload format: 
252 -)))
253 253  
252 +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.
253 +
254 +The Payload format is as below.
255 +
256 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
257 +|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
258 +**Size(bytes)**
259 +)))|=(% 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**
260 +|(% 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
261 +
262 +Example parse in TTNv3
263 +
264 +[[image:image-20230805103904-1.png||height="131" width="711"]]
265 +
266 +(% style="color:blue" %)**Sensor Model**(%%): For LDS12-LB, this value is 0x24
267 +
268 +(% style="color:blue" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
269 +
270 +(% style="color:blue" %)**Frequency Band**:
271 +
272 +0x01: EU868
273 +
274 +0x02: US915
275 +
276 +0x03: IN865
277 +
278 +0x04: AU915
279 +
280 +0x05: KZ865
281 +
282 +0x06: RU864
283 +
284 +0x07: AS923
285 +
286 +0x08: AS923-1
287 +
288 +0x09: AS923-2
289 +
290 +0x0a: AS923-3
291 +
292 +0x0b: CN470
293 +
294 +0x0c: EU433
295 +
296 +0x0d: KR920
297 +
298 +0x0e: MA869
299 +
300 +(% style="color:blue" %)**Sub-Band**:
301 +
302 +AU915 and US915:value 0x00 ~~ 0x08
303 +
304 +CN470: value 0x0B ~~ 0x0C
305 +
306 +Other Bands: Always 0x00
307 +
308 +(% style="color:blue" %)**Battery Info**:
309 +
310 +Check the battery voltage.
311 +
312 +Ex1: 0x0B45 = 2885mV
313 +
314 +Ex2: 0x0B49 = 2889mV
315 +
316 +
317 +=== 2.3.2 Uplink Payload, FPORT~=2 ===
318 +
319 +
254 254  (((
255 -Uplink payload includes in total 11 bytes.
321 +LDS12-LB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LDS12-LB will:
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.
256 256  )))
257 257  
258 258  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
259 -|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)(((
329 +|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
260 260  **Size(bytes)**
261 -)))|=(% 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**
262 -|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1BatteryInfo"]]|(% style="width:62.5px" %)(((
263 -[[Temperature DS18B20>>||anchor="H2.3.2DS18B20Temperaturesensor"]]
264 -)))|[[Distance>>||anchor="H2.3.3Distance"]]|[[Distance signal strength>>||anchor="H2.3.4Distancesignalstrength"]]|(((
265 -[[Interrupt flag>>||anchor="H2.3.5InterruptPin"]]
266 -)))|[[LiDAR temp>>||anchor="H2.3.6LiDARtemp"]]|(((
267 -[[Message Type>>||anchor="H2.3.7MessageType"]]
331 +)))|=(% 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**
332 +|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)[[BAT>>||anchor="HBatteryInfo"]]|(% style="width:62.5px" %)(((
333 +[[Temperature DS18B20>>||anchor="HDS18B20Temperaturesensor"]]
334 +)))|[[Distance>>||anchor="HDistance"]]|[[Distance signal strength>>||anchor="HDistancesignalstrength"]]|(% style="width:122px" %)(((
335 +[[Interrupt flag & Interrupt_level>>||anchor="HInterruptPin26A0InterruptLevel"]]
336 +)))|(% style="width:54px" %)[[LiDAR temp>>||anchor="HLiDARtemp"]]|(% style="width:96px" %)(((
337 +[[Message Type>>||anchor="HMessageType"]]
268 268  )))
269 269  
270 -[[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"]]
340 +[[image:image-20230805104104-2.png||height="136" width="754"]]
271 271  
272 272  
273 -=== 2.3.1 Battery Info ===
343 +==== (% style="color:blue" %)**Battery Info**(%%) ====
274 274  
275 275  
276 276  Check the battery voltage for LDS12-LB.
... ... @@ -280,7 +280,7 @@
280 280  Ex2: 0x0B49 = 2889mV
281 281  
282 282  
283 -=== 2.3.2 DS18B20 Temperature sensor ===
353 +==== (% style="color:blue" %)**DS18B20 Temperature sensor**(%%) ====
284 284  
285 285  
286 286  This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
... ... @@ -293,7 +293,7 @@
293 293  If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
294 294  
295 295  
296 -=== 2.3.3 Distance ===
366 +==== (% style="color:blue" %)**Distance**(%%) ====
297 297  
298 298  
299 299  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.
... ... @@ -304,7 +304,7 @@
304 304  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.
305 305  
306 306  
307 -=== 2.3.4 Distance signal strength ===
377 +==== (% style="color:blue" %)**Distance signal strength**(%%) ====
308 308  
309 309  
310 310  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.
... ... @@ -317,21 +317,36 @@
317 317  Customers can judge whether they need to adjust the environment based on the signal strength.
318 318  
319 319  
320 -=== 2.3.5 Interrupt Pin ===
390 +**1) When the sensor detects valid data:**
321 321  
392 +[[image:image-20230805155335-1.png||height="145" width="724"]]
322 322  
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 +==== (% style="color:blue" %)**Interrupt Pin & Interrupt Level**(%%) ====
406 +
407 +
323 323  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.
324 324  
325 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.8PinDefinitions"]].
410 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.8PinDefinitions"]] of GPIO_EXTI .
326 326  
327 327  **Example:**
328 328  
329 -0x00: Normal uplink packet.
414 +If byte[0]&0x01=0x00 : Normal uplink packet.
330 330  
331 -0x01: Interrupt Uplink Packet.
416 +If byte[0]&0x01=0x01 : Interrupt Uplink Packet.
332 332  
333 333  
334 -=== 2.3.6 LiDAR temp ===
419 +==== (% style="color:blue" %)**LiDAR temp**(%%) ====
335 335  
336 336  
337 337  Characterize the internal temperature value of the sensor.
... ... @@ -341,7 +341,7 @@
341 341  If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
342 342  
343 343  
344 -=== 2.3.7 Message Type ===
429 +==== (% style="color:blue" %)**Message Type**(%%) ====
345 345  
346 346  
347 347  (((
... ... @@ -354,14 +354,97 @@
354 354  
355 355  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:499px" %)
356 356  |=(% 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**
357 -|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]
358 -|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.ConfigureLDS12-LB"]]
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
359 359  
445 +[[image:image-20230805150315-4.png||height="233" width="723"]]
360 360  
361 361  
362 -=== 2.3.8 Decode payload in The Things Network ===
448 +=== 2.3.3 Historical measuring distance, FPORT~=3 ===
363 363  
364 364  
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 +
365 365  While using TTN network, you can add the payload format to decode the payload.
366 366  
367 367  [[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"]]
... ... @@ -376,15 +376,9 @@
376 376  )))
377 377  
378 378  
379 -== 2.4 Uplink Interval ==
547 +== 2.4 ​Show Data in DataCake IoT Server ==
380 380  
381 381  
382 -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"]]
383 -
384 -
385 -== 2.5 ​Show Data in DataCake IoT Server ==
386 -
387 -
388 388  (((
389 389  [[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:
390 390  )))
... ... @@ -417,13 +417,13 @@
417 417  [[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"]]
418 418  
419 419  
420 -== 2.6 Datalog Feature ==
582 +== 2.5 Datalog Feature ==
421 421  
422 422  
423 423  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.
424 424  
425 425  
426 -=== 2.6.1 Ways to get datalog via LoRaWAN ===
588 +=== 2.5.1 Ways to get datalog via LoRaWAN ===
427 427  
428 428  
429 429  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.
... ... @@ -440,7 +440,7 @@
440 440  [[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"]]
441 441  
442 442  
443 -=== 2.6.2 Unix TimeStamp ===
605 +=== 2.5.2 Unix TimeStamp ===
444 444  
445 445  
446 446  LDS12-LB uses Unix TimeStamp format based on
... ... @@ -457,7 +457,7 @@
457 457  So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
458 458  
459 459  
460 -=== 2.6.3 Set Device Time ===
622 +=== 2.5.3 Set Device Time ===
461 461  
462 462  
463 463  User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
... ... @@ -467,13 +467,13 @@
467 467  (% 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.**
468 468  
469 469  
470 -=== 2.6.4 Poll sensor value ===
632 +=== 2.5.4 Poll sensor value ===
471 471  
472 472  
473 473  Users can poll sensor values based on timestamps. Below is the downlink command.
474 474  
475 475  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:425.818px" %)
476 -|(% colspan="4" style="background-color:#d9e2f3; color:#0070c0; width:423px" %)**Downlink Command to poll Open/Close status (0x31)**
638 +|(% colspan="4" style="background-color:#4f81bd; color:white; width:423px" %)**Downlink Command to poll Open/Close status (0x31)**
477 477  |(% style="width:58px" %)**1byte**|(% style="width:127px" %)**4bytes**|(% style="width:124px" %)**4bytes**|(% style="width:114px" %)**1byte**
478 478  |(% style="width:58px" %)31|(% style="width:127px" %)Timestamp start|(% style="width:124px" %)Timestamp end|(% style="width:114px" %)Uplink Interval
479 479  
... ... @@ -494,7 +494,7 @@
494 494  )))
495 495  
496 496  
497 -== 2.7 Frequency Plans ==
659 +== 2.6 Frequency Plans ==
498 498  
499 499  
500 500  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.
... ... @@ -502,9 +502,9 @@
502 502  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]]
503 503  
504 504  
505 -== 2.8 LiDAR ToF Measurement ==
667 +== 2.7 LiDAR ToF Measurement ==
506 506  
507 -=== 2.8.1 Principle of Distance Measurement ===
669 +=== 2.7.1 Principle of Distance Measurement ===
508 508  
509 509  
510 510  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.
... ... @@ -512,7 +512,7 @@
512 512  [[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"]]
513 513  
514 514  
515 -=== 2.8.2 Distance Measurement Characteristics ===
677 +=== 2.7.2 Distance Measurement Characteristics ===
516 516  
517 517  
518 518  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:
... ... @@ -550,7 +550,7 @@
550 550  )))
551 551  
552 552  
553 -=== 2.8.3 Notice of usage ===
715 +=== 2.7.3 Notice of usage ===
554 554  
555 555  
556 556  Possible invalid /wrong reading for LiDAR ToF tech:
... ... @@ -562,7 +562,7 @@
562 562  
563 563  
564 564  
565 -=== 2.8.4  Reflectivity of different objects ===
727 +=== 2.7.4  Reflectivity of different objects ===
566 566  
567 567  
568 568  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:379px" %)
... ... @@ -673,9 +673,9 @@
673 673  === 3.3.2 Set Interrupt Mode ===
674 674  
675 675  
676 -Feature, Set Interrupt mode for PA8 of pin.
838 +Feature, Set Interrupt mode for pin of GPIO_EXTI.
677 677  
678 -When AT+INTMOD=0 is set, PA8 is used as a digital input port.
840 +When AT+INTMOD=0 is set, GPIO_EXTI is used as a digital input port.
679 679  
680 680  (% style="color:blue" %)**AT Command: AT+INTMOD**
681 681  
... ... @@ -686,7 +686,11 @@
686 686  OK
687 687  the mode is 0 =Disable Interrupt
688 688  )))
689 -|(% style="width:154px" %)AT+INTMOD=2|(% style="width:196px" %)(((
851 +|(% style="width:154px" %)(((
852 +AT+INTMOD=2
853 +
854 +(default)
855 +)))|(% style="width:196px" %)(((
690 690  Set Transmit Interval
691 691  0. (Disable Interrupt),
692 692  ~1. (Trigger by rising and falling edge)
... ... @@ -706,83 +706,37 @@
706 706  
707 707  
708 708  
709 -=== 3.3.3 Get Firmware Version Info ===
875 +=== 3.3.3  Set Power Output Duration ===
710 710  
877 +Control the output duration 3V3(pin of VBAT_OUT) . Before each sampling, device will
711 711  
712 -Feature: use downlink to get firmware version.
879 +~1. first enable the power output to external sensor,
713 713  
714 -(% style="color:blue" %)**Downlink Command: 0x26**
881 +2. keep it on as per duration, read sensor value and construct uplink payload
715 715  
716 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:492px" %)
717 -|(% 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)**
718 -|(% style="width:191px" %)Get Firmware Version Info|(% style="width:57px" %)Any|(% style="width:91px" %)26|(% style="width:151px" %)2
883 +3. final, close the power output.
719 719  
720 -* Reply to the confirmation package: 26 01
721 -* Reply to non-confirmed packet: 26 00
885 +(% style="color:blue" %)**AT Command: AT+3V3T**
722 722  
723 -Device will send an uplink after got this downlink command. With below payload:
887 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
888 +|=(% 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**
889 +|(% style="width:154px" %)AT+3V3T=?|(% style="width:196px" %)Show 3V3 open time.|(% style="width:157px" %)0 (default)
890 +OK
891 +|(% style="width:154px" %)AT+3V3T=1000|(% style="width:196px" %)Close after a delay of 1000 milliseconds.|(% style="width:157px" %)OK
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
724 724  
725 -Configures info payload:
895 +(% style="color:blue" %)**Downlink Command: 0x07**(%%)
896 +Format: Command Code (0x07) followed by 3 bytes.
726 726  
727 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
728 -|=(% style="background-color:#4F81BD;color:white" %)(((
729 -**Size(bytes)**
730 -)))|=(% 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**
731 -|**Value**|Software Type|(((
732 -Frequency Band
733 -)))|Sub-band|(((
734 -Firmware Version
735 -)))|Sensor Type|Reserve|(((
736 -[[Message Type>>||anchor="H2.3.7MessageType"]]
737 -Always 0x02
738 -)))
898 +The first byte is 01,the second and third bytes are the time to turn on.
739 739  
740 -(% style="color:#037691" %)**Software Type**(%%): Always 0x03 for LLDS12
900 +* Example 1: Downlink Payload: 07 01 00 00  **~-~-->**  AT+3V3T=0
901 +* Example 2: Downlink Payload: 07 01 01 F4  **~-~-->**  AT+3V3T=500
902 +* Example 3: Downlink Payload: 07 01 FF FF  **~-~-->**  AT+3V3T=65535
741 741  
742 -(% style="color:#037691" %)**Frequency Band**:
743 743  
744 -*0x01: EU868
745 745  
746 -*0x02: US915
747 -
748 -*0x03: IN865
749 -
750 -*0x04: AU915
751 -
752 -*0x05: KZ865
753 -
754 -*0x06: RU864
755 -
756 -*0x07: AS923
757 -
758 -*0x08: AS923-1
759 -
760 -*0x09: AS923-2
761 -
762 -*0xa0: AS923-3
763 -
764 -
765 -(% style="color:#037691" %)**Sub-Band**(%%): value 0x00 ~~ 0x08
766 -
767 -(% style="color:#037691" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
768 -
769 -(% style="color:#037691" %)**Sensor Type**:
770 -
771 -0x01: LSE01
772 -
773 -0x02: LDDS75
774 -
775 -0x03: LDDS20
776 -
777 -0x04: LLMS01
778 -
779 -0x05: LSPH01
780 -
781 -0x06: LSNPK01
782 -
783 -0x07: LLDS12
784 -
785 -
786 786  = 4. Battery & Power Consumption =
787 787  
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
image-20230805150315-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Saxer
Size
... ... @@ -1,0 +1,1 @@
1 +90.6 KB
Content
image-20230805155335-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Saxer
Size
... ... @@ -1,0 +1,1 @@
1 +45.4 KB
Content
image-20230805155428-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Saxer
Size
... ... @@ -1,0 +1,1 @@
1 +45.5 KB
Content
image-20230805155515-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Saxer
Size
... ... @@ -1,0 +1,1 @@
1 +45.7 KB
Content