Skip to Content
Last modified by Mengting Qiu on 2023/12/14 11:15
From version 82.6
edited by Xiaoling
on 2023/06/14 16:55
Change comment: There is no comment for this version
To version 97.1
edited by Saxer Lin
on 2023/08/05 14:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Saxer
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 ==
... ... @@ -99,7 +99,6 @@
99 99  * Sleep Mode: 5uA @ 3.3v
100 100  * LoRa Transmit Mode: 125mA @ 20dBm, 82mA @ 14dBm
101 101  
102 -
103 103  == 1.4 Applications ==
104 104  
105 105  
... ... @@ -111,7 +111,6 @@
111 111  * Automatic control
112 112  * Sewer
113 113  
114 -
115 115  (% style="display:none" %)
116 116  
117 117  == 1.5 Sleep mode and working mode ==
... ... @@ -129,7 +129,7 @@
129 129  
130 130  
131 131  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
132 -|=(% 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**
130 +|=(% 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 133  |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((
134 134  If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once.
135 135  Meanwhile, BLE module will be active and user can connect via BLE to configure device.
... ... @@ -157,10 +157,9 @@
157 157  
158 158  == 1.8 Pin Definitions ==
159 159  
160 -[[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"]]
161 161  
159 +[[image:image-20230805144259-1.png||height="413" width="741"]]
162 162  
163 -
164 164  == 1.9 Mechanical ==
165 165  
166 166  
... ... @@ -176,7 +176,6 @@
176 176  (% style="color:blue" %)**Probe Mechanical:**
177 177  
178 178  
179 -
180 180  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654827224480-952.png?rev=1.1||alt="1654827224480-952.png"]]
181 181  
182 182  
... ... @@ -196,7 +196,7 @@
196 196  
197 197  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.
198 198  
199 -[[image:image-20230614162359-3.png||height="468" width="800"]](% style="display:none" %)
195 +[[image:image-20230615153004-2.png||height="459" width="800"]](% style="display:none" %)
200 200  
201 201  
202 202  (% style="color:blue" %)**Step 1:**(%%) Create a device in TTN with the OTAA keys from LDS12-LB.
... ... @@ -240,34 +240,103 @@
240 240  After join success, it will start to upload messages to TTN and you can see the messages in the panel.
241 241  
242 242  
243 -== 2.3  ​Uplink Payload ==
239 +== 2.3 ​Uplink Payload ==
244 244  
241 +=== 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  
244 +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.
245 +
246 +The Payload format is as below.
247 +
248 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
249 +|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
250 +**Size(bytes)**
251 +)))|=(% 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**
252 +|(% 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
253 +
254 +Example parse in TTNv3
255 +
256 +[[image:image-20230805103904-1.png||height="131" width="711"]]
257 +
258 +(% style="color:blue" %)**Sensor Model**(%%): For LDS12-LB, this value is 0x24
259 +
260 +(% style="color:blue" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
261 +
262 +(% style="color:blue" %)**Frequency Band**:
263 +
264 +0x01: EU868
265 +
266 +0x02: US915
267 +
268 +0x03: IN865
269 +
270 +0x04: AU915
271 +
272 +0x05: KZ865
273 +
274 +0x06: RU864
275 +
276 +0x07: AS923
277 +
278 +0x08: AS923-1
279 +
280 +0x09: AS923-2
281 +
282 +0x0a: AS923-3
283 +
284 +0x0b: CN470
285 +
286 +0x0c: EU433
287 +
288 +0x0d: KR920
289 +
290 +0x0e: MA869
291 +
292 +(% style="color:blue" %)**Sub-Band**:
293 +
294 +AU915 and US915:value 0x00 ~~ 0x08
295 +
296 +CN470: value 0x0B ~~ 0x0C
297 +
298 +Other Bands: Always 0x00
299 +
300 +(% style="color:blue" %)**Battery Info**:
301 +
302 +Check the battery voltage.
303 +
304 +Ex1: 0x0B45 = 2885mV
305 +
306 +Ex2: 0x0B49 = 2889mV
307 +
308 +
309 +=== 2.3.2 Uplink Payload, FPORT~=2 ===
310 +
311 +
250 250  (((
251 -Uplink payload includes in total 11 bytes.
252 -)))
313 +LDS12-LB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LDS12-LB will:
253 253  
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]].
254 254  
317 +Uplink Payload totals 11 bytes.
318 +)))
319 +
255 255  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
256 -|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)(((
321 +|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
257 257  **Size(bytes)**
258 -)))|=(% 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**
259 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
260 -[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
261 -)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
262 -[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
263 -)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
264 -[[Message Type>>||anchor="H2.3.7A0MessageType"]]
323 +)))|=(% 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**
324 +|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)[[BAT>>||anchor="HBatteryInfo"]]|(% style="width:62.5px" %)(((
325 +[[Temperature DS18B20>>||anchor="HDS18B20Temperaturesensor"]]
326 +)))|[[Distance>>||anchor="HDistance"]]|[[Distance signal strength>>||anchor="HDistancesignalstrength"]]|(% style="width:122px" %)(((
327 +[[Interrupt flag & Interrupt_level>>||anchor="HInterruptPin26A0InterruptLevel"]]
328 +)))|(% style="width:54px" %)[[LiDAR temp>>||anchor="HLiDARtemp"]]|(% style="width:96px" %)(((
329 +[[Message Type>>||anchor="HMessageType"]]
265 265  )))
266 266  
267 -[[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"]]
268 268  
269 269  
270 -=== 2.3.1  Battery Info ===
335 +==== (% style="color:blue" %)**Battery Info**(%%) ====
271 271  
272 272  
273 273  Check the battery voltage for LDS12-LB.
... ... @@ -277,7 +277,7 @@
277 277  Ex2: 0x0B49 = 2889mV
278 278  
279 279  
280 -=== 2.3.2  DS18B20 Temperature sensor ===
345 +==== (% style="color:blue" %)**DS18B20 Temperature sensor**(%%) ====
281 281  
282 282  
283 283  This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
... ... @@ -290,7 +290,7 @@
290 290  If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
291 291  
292 292  
293 -=== 2.3.3  Distance ===
358 +==== (% style="color:blue" %)**Distance**(%%) ====
294 294  
295 295  
296 296  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.
... ... @@ -301,7 +301,7 @@
301 301  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.
302 302  
303 303  
304 -=== 2.3.4  Distance signal strength ===
369 +==== (% style="color:blue" %)**Distance signal strength**(%%) ====
305 305  
306 306  
307 307  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.
... ... @@ -314,12 +314,12 @@
314 314  Customers can judge whether they need to adjust the environment based on the signal strength.
315 315  
316 316  
317 -=== 2.3.5  Interrupt Pin ===
382 +==== (% style="color:blue" %)**Interrupt Pin & Interrupt Level**(%%) ====
318 318  
319 319  
320 -This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H4.2A0SetInterruptMode"]] for the hardware and software set up.
385 +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.
321 321  
322 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
387 +Note: The Internet Pin is a separate pin in the screw terminal. See GPIO_EXTI of [[pin mapping>>||anchor="H1.8PinDefinitions"]].
323 323  
324 324  **Example:**
325 325  
... ... @@ -328,7 +328,7 @@
328 328  0x01: Interrupt Uplink Packet.
329 329  
330 330  
331 -=== 2.3.6  LiDAR temp ===
396 +==== (% style="color:blue" %)**LiDAR temp**(%%) ====
332 332  
333 333  
334 334  Characterize the internal temperature value of the sensor.
... ... @@ -338,7 +338,7 @@
338 338  If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
339 339  
340 340  
341 -=== 2.3.7  Message Type ===
406 +==== (% style="color:blue" %)**Message Type**(%%) ====
342 342  
343 343  
344 344  (((
... ... @@ -350,19 +350,81 @@
350 350  )))
351 351  
352 352  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:499px" %)
353 -|=(% style="width: 161px;background-color:#D9E2F3;color:#0070C0" %)**Message Type Code**|=(% style="width: 164px;background-color:#D9E2F3;color:#0070C0" %)**Description**|=(% style="width: 174px;background-color:#D9E2F3;color:#0070C0" %)**Payload**
354 -|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
355 -|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
418 +|=(% 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**
419 +|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]
420 +|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.ConfigureLDS12-LB"]]
356 356  
357 -=== 2.3.8  Decode payload in The Things Network ===
358 358  
423 +=== 2.3.3 Historical Water Flow Status, FPORT~=3 ===
359 359  
360 -While using TTN network, you can add the payload format to decode the payload.
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]].
361 361  
427 +The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time water flow status.
362 362  
363 -[[image:1654592762713-715.png]]
364 364  
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 +)))
365 365  
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 +
485 +=== 2.3.3 Decode payload in The Things Network ===
486 +
487 +
488 +While using TTN network, you can add the payload format to decode the payload.
489 +
490 +[[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"]]
491 +
492 +
366 366  (((
367 367  The payload decoder function for TTN is here:
368 368  )))
... ... @@ -372,15 +372,9 @@
372 372  )))
373 373  
374 374  
375 -== 2.4  Uplink Interval ==
502 +== 2.4 ​Show Data in DataCake IoT Server ==
376 376  
377 377  
378 -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"]]
379 -
380 -
381 -== 2.5  ​Show Data in DataCake IoT Server ==
382 -
383 -
384 384  (((
385 385  [[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:
386 386  )))
... ... @@ -413,13 +413,13 @@
413 413  [[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"]]
414 414  
415 415  
416 -== 2.6 Datalog Feature ==
537 +== 2.5 Datalog Feature ==
417 417  
418 418  
419 419  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.
420 420  
421 421  
422 -=== 2.6.1 Ways to get datalog via LoRaWAN ===
543 +=== 2.5.1 Ways to get datalog via LoRaWAN ===
423 423  
424 424  
425 425  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.
... ... @@ -436,7 +436,7 @@
436 436  [[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"]]
437 437  
438 438  
439 -=== 2.6.2 Unix TimeStamp ===
560 +=== 2.5.2 Unix TimeStamp ===
440 440  
441 441  
442 442  LDS12-LB uses Unix TimeStamp format based on
... ... @@ -453,7 +453,7 @@
453 453  So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
454 454  
455 455  
456 -=== 2.6.3 Set Device Time ===
577 +=== 2.5.3 Set Device Time ===
457 457  
458 458  
459 459  User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
... ... @@ -463,13 +463,13 @@
463 463  (% 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.**
464 464  
465 465  
466 -=== 2.6.4 Poll sensor value ===
587 +=== 2.5.4 Poll sensor value ===
467 467  
468 468  
469 469  Users can poll sensor values based on timestamps. Below is the downlink command.
470 470  
471 471  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:425.818px" %)
472 -|(% colspan="4" style="background-color:#d9e2f3; color:#0070c0; width:423px" %)**Downlink Command to poll Open/Close status (0x31)**
593 +|(% colspan="4" style="background-color:#4f81bd; color:white; width:423px" %)**Downlink Command to poll Open/Close status (0x31)**
473 473  |(% style="width:58px" %)**1byte**|(% style="width:127px" %)**4bytes**|(% style="width:124px" %)**4bytes**|(% style="width:114px" %)**1byte**
474 474  |(% style="width:58px" %)31|(% style="width:127px" %)Timestamp start|(% style="width:124px" %)Timestamp end|(% style="width:114px" %)Uplink Interval
475 475  
... ... @@ -490,7 +490,7 @@
490 490  )))
491 491  
492 492  
493 -== 2.7 Frequency Plans ==
614 +== 2.6 Frequency Plans ==
494 494  
495 495  
496 496  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.
... ... @@ -498,23 +498,22 @@
498 498  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]]
499 499  
500 500  
501 -== 2.8 LiDAR ToF Measurement ==
622 +== 2.7 LiDAR ToF Measurement ==
502 502  
503 -=== 2.8.1 Principle of Distance Measurement ===
624 +=== 2.7.1 Principle of Distance Measurement ===
504 504  
505 505  
506 506  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 507  
629 +[[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 -[[image:1654831757579-263.png]]
510 510  
632 +=== 2.7.2 Distance Measurement Characteristics ===
511 511  
512 -=== 2.8.2 Distance Measurement Characteristics ===
513 513  
514 -
515 515  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:
516 516  
517 -[[image:1654831774373-275.png]]
637 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654831774373-275.png?rev=1.1||alt="1654831774373-275.png"]]
518 518  
519 519  
520 520  (((
... ... @@ -534,23 +534,20 @@
534 534  Vertical Coordinates: Represents the radius of light spot for The LiDAR probe at different distances. The diameter of light spot depends on the FOV of The LiDAR probe (the term of FOV generally refers to the smaller value between the receiving angle and the transmitting angle), which is calculated as follows:
535 535  )))
536 536  
657 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654831797521-720.png?rev=1.1||alt="1654831797521-720.png"]]
537 537  
538 -[[image:1654831797521-720.png]]
539 -
540 -
541 541  (((
542 542  In the formula above, d is the diameter of light spot; D is detecting range; β is the value of the receiving angle of The LiDAR probe, 3.6°. Correspondence between the diameter of light spot and detecting range is given in Table below.
543 543  )))
544 544  
545 -[[image:1654831810009-716.png]]
663 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654831810009-716.png?rev=1.1||alt="1654831810009-716.png"]]
546 546  
547 -
548 548  (((
549 549  If the light spot reaches two objects with different distances, as shown in Figure 3, the output distance value will be a value between the actual distance values of the two objects. For a high accuracy requirement in practice, the above situation should be noticed to avoid the measurement error.
550 550  )))
551 551  
552 552  
553 -=== 2.8.3 Notice of usage: ===
670 +=== 2.7.3 Notice of usage ===
554 554  
555 555  
556 556  Possible invalid /wrong reading for LiDAR ToF tech:
... ... @@ -560,11 +560,11 @@
560 560  * The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
561 561  * The sensor window is made by Acrylic. Don't touch it with alcohol material. This will destroy the sensor window.
562 562  
563 -=== 2.8.4  Reflectivity of different objects ===
680 +=== 2.7.4  Reflectivity of different objects ===
564 564  
565 565  
566 566  (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:379px" %)
567 -|=(% style="width: 54px;background-color:#D9E2F3;color:#0070C0" %)Item|=(% style="width: 231px;background-color:#D9E2F3;color:#0070C0" %)Material|=(% style="width: 94px;background-color:#D9E2F3;color:#0070C0" %)Relectivity
684 +|=(% style="width: 54px;background-color:#4F81BD;color:white" %)Item|=(% style="width: 231px;background-color:#4F81BD;color:white" %)Material|=(% style="width: 94px;background-color:#4F81BD;color:white" %)Relectivity
568 568  |(% style="width:53px" %)1|(% style="width:229px" %)Black foam rubber|(% style="width:93px" %)2.4%
569 569  |(% style="width:53px" %)2|(% style="width:229px" %)Black fabric|(% style="width:93px" %)3%
570 570  |(% style="width:53px" %)3|(% style="width:229px" %)Black rubber|(% style="width:93px" %)4%
... ... @@ -631,7 +631,7 @@
631 631  )))
632 632  
633 633  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
634 -|=(% style="width: 156px;background-color:#D9E2F3; color:#0070c0" %)**Command Example**|=(% style="width: 137px;background-color:#D9E2F3; color:#0070c0" %)**Function**|=(% style="background-color:#D9E2F3; color:#0070c0" %)**Response**
751 +|=(% style="width: 156px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 137px;background-color:#4F81BD;color:white" %)**Function**|=(% style="background-color:#4F81BD;color:white" %)**Response**
635 635  |(% style="width:156px" %)AT+TDC=?|(% style="width:137px" %)Show current transmit Interval|(((
636 636  30000
637 637  OK
... ... @@ -659,6 +659,9 @@
659 659  )))
660 660  * (((
661 661  Example 2: Downlink Payload: 0100003C  ~/~/ Set Transmit Interval (TDC) = 60 seconds 
779 +
780 +
781 +
662 662  )))
663 663  
664 664  === 3.3.2 Set Interrupt Mode ===
... ... @@ -671,7 +671,7 @@
671 671  (% style="color:blue" %)**AT Command: AT+INTMOD**
672 672  
673 673  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
674 -|=(% style="width: 155px;background-color:#D9E2F3;color:#0070C0" %)**Command Example**|=(% style="width: 197px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 158px;background-color:#D9E2F3;color:#0070C0" %)**Response**
794 +|=(% 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**
675 675  |(% style="width:154px" %)AT+INTMOD=?|(% style="width:196px" %)Show current interrupt mode|(% style="width:157px" %)(((
676 676  0
677 677  OK
... ... @@ -695,87 +695,35 @@
695 695  
696 696  * Example 2: Downlink Payload: 06000003  ~/~/  Set the interrupt mode to rising edge trigger
697 697  
818 +=== 3.3.3  Set Power Output Duration ===
698 698  
820 +Control the output duration 3V3(pin of VBAT_OUT) . Before each sampling, device will
699 699  
700 -=== 3.3.3 Get Firmware Version Info ===
822 +~1. first enable the power output to external sensor,
701 701  
824 +2. keep it on as per duration, read sensor value and construct uplink payload
702 702  
703 -Feature: use downlink to get firmware version.
826 +3. final, close the power output.
704 704  
705 -(% style="color:#037691" %)**Downlink Command: 0x26**
828 +(% style="color:blue" %)**AT Command: AT+3V3T**
706 706  
707 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:492px" %)
708 -|(% style="background-color:#d9e2f3; color:#0070c0; width:191px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:57px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:91px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; 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
830 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
831 +|=(% 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**
832 +|(% style="width:154px" %)AT+3V3T=?|(% style="width:196px" %)Show 3V3 open time.|(% style="width:157px" %)0 (default)
833 +OK
834 +|(% style="width:154px" %)AT+3V3T=1000|(% style="width:196px" %)Close after a delay of 1000 milliseconds.|(% style="width:157px" %)OK
835 +|(% 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
710 710  
711 -* Reply to the confirmation package: 26 01
712 -* Reply to non-confirmed packet: 26 00
838 +(% style="color:blue" %)**Downlink Command: 0x07**(%%)
839 +Format: Command Code (0x07) followed by 3 bytes.
713 713  
714 -Device will send an uplink after got this downlink command. With below payload:
841 +The first byte is 01,the second and third bytes are the time to turn on.
715 715  
716 -Configures info payload:
843 +* Example 1: Downlink Payload: 07 01 00 00  **~-~-->**  AT+3V3T=0
844 +* Example 2: Downlink Payload: 07 01 01 F4  **~-~-->**  AT+3V3T=500
845 +* Example 3: Downlink Payload: 07 01 FF FF  **~-~-->**  AT+3V3T=65535
717 717  
718 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
719 -|=(% style="background-color:#D9E2F3;color:#0070C0" %)(((
720 -**Size(bytes)**
721 -)))|=(% style="background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="background-color:#D9E2F3;color:#0070C0" %)**5**|=(% style="background-color:#D9E2F3;color:#0070C0" %)**1**
722 -|**Value**|Software Type|(((
723 -Frequency
724 -Band
725 -)))|Sub-band|(((
726 -Firmware
727 -Version
728 -)))|Sensor Type|Reserve|(((
729 -[[Message Type>>||anchor="H2.3.7A0MessageType"]]
730 -Always 0x02
731 -)))
732 -
733 -(% style="color:#037691" %)**Software Type**(%%): Always 0x03 for LLDS12
734 -
735 -(% style="color:#037691" %)**Frequency Band**:
736 -
737 -*0x01: EU868
738 -
739 -*0x02: US915
740 -
741 -*0x03: IN865
742 -
743 -*0x04: AU915
744 -
745 -*0x05: KZ865
746 -
747 -*0x06: RU864
748 -
749 -*0x07: AS923
750 -
751 -*0x08: AS923-1
752 -
753 -*0x09: AS923-2
754 -
755 -*0xa0: AS923-3
756 -
757 -
758 -(% style="color:#037691" %)**Sub-Band**(%%): value 0x00 ~~ 0x08
759 -
760 -(% style="color:#037691" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
761 -
762 -(% style="color:#037691" %)**Sensor Type**:
763 -
764 -0x01: LSE01
765 -
766 -0x02: LDDS75
767 -
768 -0x03: LDDS20
769 -
770 -0x04: LLMS01
771 -
772 -0x05: LSPH01
773 -
774 -0x06: LSNPK01
775 -
776 -0x07: LLDS12
777 -
778 -
779 779  = 4. Battery & Power Consumption =
780 780  
781 781  
... ... @@ -796,7 +796,7 @@
796 796  
797 797  * Fix bugs.
798 798  
799 -Firmware and changelog can be downloaded from : **[[Firmware download link>>url:https://www.dropbox.com/sh/ph4uyz0rchflrnw/AADr1f_5Sg30804NItpfOQbla?dl=0]]**
867 +Firmware and changelog can be downloaded from : **[[Firmware download link>>url:https://www.dropbox.com/sh/w1p7ukjrx49e62r/AAB3uCNCt-koYUvMkZUPBRSca?dl=0]]**
800 800  
801 801  Methods to Update Firmware:
802 802  
... ... @@ -824,11 +824,11 @@
824 824  
825 825  
826 826  (((
827 -(% style="color:blue" %)**Cause ①**(%%)**：**Due to the physical principles of The LiDAR probe, the above phenomenon is likely to occur if the detection object is the material with high reflectivity (such as mirror, smooth floor tile, etc.) or transparent substance (such as glass and water, etc.)
895 +(% style="color:blue" %)**Cause ①**(%%)**：**Due to the physical principles of The LiDAR probe, the above phenomenon is likely to occur if the detection object is the material with high reflectivity (such as mirror, smooth floor tile, etc.) or transparent substance. (such as glass and water, etc.)
828 828  )))
829 829  
830 830  (((
831 -Troubleshooting: Please avoid use of this product under such circumstance in practice.
899 +(% style="color:red" %)**Troubleshooting**(%%): Please avoid use of this product under such circumstance in practice.
832 832  )))
833 833  
834 834  
... ... @@ -837,7 +837,7 @@
837 837  )))
838 838  
839 839  (((
840 -Troubleshooting: please use dry dust-free cloth to gently remove the foreign matter.
908 +(% style="color:red" %)**Troubleshooting**(%%): please use dry dust-free cloth to gently remove the foreign matter.
841 841  )))
842 842  
843 843  
image-20230615152941-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +87.9 KB
Content
image-20230615153004-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +87.9 KB
Content
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