Changes for page DS20L -- LoRaWAN Smart Distance Detector User Manual 01
Last modified by Mengting Qiu on 2023/12/14 11:15
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 11 added, 0 removed)
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-2023061 4162334-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 == ... ... @@ -127,7 +127,7 @@ 127 127 128 128 129 129 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 130 -|=(% 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** 131 131 |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( 132 132 If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. 133 133 Meanwhile, BLE module will be active and user can connect via BLE to configure device. ... ... @@ -155,10 +155,9 @@ 155 155 156 156 == 1.8 Pin Definitions == 157 157 158 -[[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"]] 159 159 159 +[[image:image-20230805144259-1.png||height="413" width="741"]] 160 160 161 - 162 162 == 1.9 Mechanical == 163 163 164 164 ... ... @@ -174,7 +174,6 @@ 174 174 (% style="color:blue" %)**Probe Mechanical:** 175 175 176 176 177 - 178 178 [[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"]] 179 179 180 180 ... ... @@ -194,7 +194,7 @@ 194 194 195 195 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. 196 196 197 -[[image:image-2023061 4162359-3.png||height="468" width="800"]](% style="display:none" %)195 +[[image:image-20230615153004-2.png||height="459" width="800"]](% style="display:none" %) 198 198 199 199 200 200 (% style="color:blue" %)**Step 1:**(%%) Create a device in TTN with the OTAA keys from LDS12-LB. ... ... @@ -240,32 +240,101 @@ 240 240 241 241 == 2.3 Uplink Payload == 242 242 241 +=== 2.3.1 Device Status, FPORT~=5 === 243 243 244 -((( 245 -LDS12-LB will uplink payload via LoRaWAN with below payload format: 246 -))) 247 247 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 + 248 248 ((( 249 -Uplink payload includes in total 11 bytes. 250 -))) 313 +LDS12-LB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LDS12-LB will: 251 251 315 +periodically send this uplink every 20 minutes, this interval [[can be changed>>||anchor="H3.3.1SetTransmitIntervalTime"]]. 252 252 317 +Uplink Payload totals 11 bytes. 318 +))) 319 + 253 253 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 254 -|=(% style="width: 6 2.5px;background-color:#4F81BD;color:white" %)(((321 +|=(% style="width: 60px;background-color:#4F81BD;color:white" %)((( 255 255 **Size(bytes)** 256 -)))|=(% 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**257 -|(% style="width:62.5px" %) **Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1BatteryInfo"]]|(% style="width:62.5px" %)(((258 -[[Temperature DS18B20>>||anchor="H 2.3.2DS18B20Temperaturesensor"]]259 -)))|[[Distance>>||anchor="H 2.3.3Distance"]]|[[Distance signal strength>>||anchor="H2.3.4Distancesignalstrength"]]|(((260 -[[Interrupt 2.3.5InterruptPin"]]261 -)))|[[LiDAR temp>>||anchor="H 2.3.6LiDARtemp"]]|(((262 -[[Message Type>>||anchor="H 2.3.7MessageType"]]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"]] 263 263 ))) 264 264 265 -[[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"]] 266 266 267 267 268 -=== 2.3.1Battery Info ===335 +==== (% style="color:blue" %)**Battery Info**(%%) ==== 269 269 270 270 271 271 Check the battery voltage for LDS12-LB. ... ... @@ -275,7 +275,7 @@ 275 275 Ex2: 0x0B49 = 2889mV 276 276 277 277 278 -=== 2.3.2DS18B20 Temperature sensor ===345 +==== (% style="color:blue" %)**DS18B20 Temperature sensor**(%%) ==== 279 279 280 280 281 281 This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature. ... ... @@ -288,7 +288,7 @@ 288 288 If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. 289 289 290 290 291 -=== 2.3.3Distance ===358 +==== (% style="color:blue" %)**Distance**(%%) ==== 292 292 293 293 294 294 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. ... ... @@ -299,7 +299,7 @@ 299 299 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. 300 300 301 301 302 -=== 2.3.4Distance signal strength ===369 +==== (% style="color:blue" %)**Distance signal strength**(%%) ==== 303 303 304 304 305 305 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. ... ... @@ -312,21 +312,36 @@ 312 312 Customers can judge whether they need to adjust the environment based on the signal strength. 313 313 314 314 315 - ===2.3.5 InterruptPin===382 +**1) When the sensor detects valid data:** 316 316 384 +[[image:image-20230805155335-1.png||height="145" width="724"]] 317 317 386 + 387 +**2) When the sensor detects invalid data:** 388 + 389 +[[image:image-20230805155428-2.png||height="139" width="726"]] 390 + 391 + 392 +**3) When the sensor is not connected:** 393 + 394 +[[image:image-20230805155515-3.png||height="143" width="725"]] 395 + 396 + 397 +==== (% style="color:blue" %)**Interrupt Pin & Interrupt Level**(%%) ==== 398 + 399 + 318 318 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. 319 319 320 -Note: The Internet Pin is a separate pin in the screw terminal. See 402 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.8PinDefinitions"]] of GPIO_EXTI . 321 321 322 322 **Example:** 323 323 324 -0x00: Normal uplink packet. 406 +If byte[0]&0x01=0x00 : Normal uplink packet. 325 325 326 -0x01: Interrupt Uplink Packet. 408 +If byte[0]&0x01=0x01 : Interrupt Uplink Packet. 327 327 328 328 329 -=== 2.3.6LiDAR temp ===411 +==== (% style="color:blue" %)**LiDAR temp**(%%) ==== 330 330 331 331 332 332 Characterize the internal temperature value of the sensor. ... ... @@ -336,7 +336,7 @@ 336 336 If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃. 337 337 338 338 339 -=== 2.3.7Message Type ===421 +==== (% style="color:blue" %)**Message Type**(%%) ==== 340 340 341 341 342 342 ((( ... ... @@ -349,14 +349,96 @@ 349 349 350 350 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:499px" %) 351 351 |=(% 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** 352 -|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %) [[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]353 -|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %) [[Configure Info Payload>>||anchor="H3.ConfigureLDS12-LB"]]434 +|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)Normal Uplink Payload 435 +|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)Configure Info Payload 354 354 437 +[[image:image-20230805150315-4.png||height="233" width="723"]] 355 355 356 356 357 -=== 2.3. 8 Decodepayloadin TheThingsNetwork===440 +=== 2.3.3 Historical measuring distance, FPORT~=3 === 358 358 442 +LDS12-LB stores sensor values and users can retrieve these history values via the [[downlink command>>http://8.211.40.43/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS12-LB_LoRaWAN_LiDAR_ToF_Distance_Sensor_User_Manual/#H2.5.4Pollsensorvalue]]. 359 359 444 +The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time measuring distance. 445 + 446 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 447 +|=(% style="width: 60px;background-color:#4F81BD;color:white" %)((( 448 +**Size(bytes)** 449 +)))|=(% style="width: 30px;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: rgb(79, 129, 189); color: white; width: 88px;" %)**1**|=(% style="background-color: rgb(79, 129, 189); color: white; width: 85px;" %)4 450 +|(% style="width:62.5px" %)Value|(% style="width:62.5px" %)Interrupt flag & Interrupt_level|(% style="width:62.5px" %)((( 451 +Reserve(0xFF) 452 +)))|Distance|Distance signal strength|(% style="width:88px" %)((( 453 +LiDAR temp 454 +)))|(% style="width:85px" %)Unix TimeStamp 455 + 456 +**Interrupt flag & Interrupt level:** 457 + 458 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:501px" %) 459 +|=(% style="width: 60px;background-color:#4F81BD;color:white" %)((( 460 +**Size(bit)** 461 +)))|=(% style="width: 30px;background-color:#4F81BD;color:white" %)**bit7**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**bit6**|=(% style="width: 50px;background-color:#4F81BD;color:white" %)**[bit5:bit2]**|=(% style="width: 91px; background-color: rgb(79, 129, 189); color: white;" %)**bit1**|=(% style="background-color: rgb(79, 129, 189); color: white; width: 88px;" %)**bit0** 462 +|(% 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" %)((( 463 +Interrupt flag 464 +))) 465 + 466 +* ((( 467 +Each data entry is 11 bytes and has the same structure as [[Uplink Payload>>http://8.211.40.43/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS12-LB_LoRaWAN_LiDAR_ToF_Distance_Sensor_User_Manual/#H2.3.2UplinkPayload2CFPORT3D2]], to save airtime and battery, LDS12-LB will send max bytes according to the current DR and Frequency bands. 468 +))) 469 + 470 +For example, in the US915 band, the max payload for different DR is: 471 + 472 +**a) DR0:** max is 11 bytes so one entry of data 473 + 474 +**b) DR1:** max is 53 bytes so devices will upload 4 entries of data (total 44 bytes) 475 + 476 +**c) DR2:** total payload includes 11 entries of data 477 + 478 +**d) DR3:** total payload includes 22 entries of data. 479 + 480 +If LDS12-LB doesn't have any data in the polling time. It will uplink 11 bytes of 0 481 + 482 + 483 +**Downlink:** 484 + 485 +0x31 64 CC 68 0C 64 CC 69 74 05 486 + 487 +[[image:image-20230805144936-2.png||height="113" width="746"]] 488 + 489 +**Uplink:** 490 + 491 +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 492 + 493 + 494 +**Parsed Value:** 495 + 496 +[DISTANCE , DISTANCE_SIGNAL_STRENGTH,LIDAR_TEMP,EXTI_STATUS , EXTI_FLAG , TIME] 497 + 498 + 499 +[360,176,30,High,True,2023-08-04 02:53:00], 500 + 501 +[355,168,30,Low,False,2023-08-04 02:53:29], 502 + 503 +[245,211,30,Low,False,2023-08-04 02:54:29], 504 + 505 +[57,700,30,Low,False,2023-08-04 02:55:29], 506 + 507 +[361,164,30,Low,True,2023-08-04 02:56:00], 508 + 509 +[337,184,30,Low,False,2023-08-04 02:56:40], 510 + 511 +[20,4458,30,Low,False,2023-08-04 02:57:40], 512 + 513 +[362,173,30,Low,False,2023-08-04 02:58:53], 514 + 515 + 516 +**History read from serial port:** 517 + 518 +[[image:image-20230805145056-3.png]] 519 + 520 + 521 +=== 2.3.4 Decode payload in The Things Network === 522 + 523 + 360 360 While using TTN network, you can add the payload format to decode the payload. 361 361 362 362 [[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"]] ... ... @@ -371,15 +371,9 @@ 371 371 ))) 372 372 373 373 374 -== 2.4 Uplink Interval==538 +== 2.4 Show Data in DataCake IoT Server == 375 375 376 376 377 -The LDS12-LB by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>||anchor="H3.3.1SetTransmitIntervalTime"]] 378 - 379 - 380 -== 2.5 Show Data in DataCake IoT Server == 381 - 382 - 383 383 ((( 384 384 [[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps: 385 385 ))) ... ... @@ -412,13 +412,13 @@ 412 412 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDDS75%20-%20LoRaWAN%20Distance%20Detection%20Sensor%20User%20Manual/WebHome/image-20220610165129-11.png?width=1088&height=595&rev=1.1||alt="image-20220610165129-11.png"]] 413 413 414 414 415 -== 2. 6Datalog Feature ==573 +== 2.5 Datalog Feature == 416 416 417 417 418 418 Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, LDS12-LB will store the reading for future retrieving purposes. 419 419 420 420 421 -=== 2. 6.1 Ways to get datalog via LoRaWAN ===579 +=== 2.5.1 Ways to get datalog via LoRaWAN === 422 422 423 423 424 424 Set PNACKMD=1, LDS12-LB will wait for ACK for every uplink, when there is no LoRaWAN network,LDS12-LB will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery. ... ... @@ -435,7 +435,7 @@ 435 435 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/WebHome/image-20220703111700-2.png?width=1119&height=381&rev=1.1||alt="图片-20220703111700-2.png" height="381" width="1119"]] 436 436 437 437 438 -=== 2. 6.2 Unix TimeStamp ===596 +=== 2.5.2 Unix TimeStamp === 439 439 440 440 441 441 LDS12-LB uses Unix TimeStamp format based on ... ... @@ -452,7 +452,7 @@ 452 452 So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25 453 453 454 454 455 -=== 2. 6.3 Set Device Time ===613 +=== 2.5.3 Set Device Time === 456 456 457 457 458 458 User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command. ... ... @@ -462,13 +462,13 @@ 462 462 (% style="color:red" %)**Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.** 463 463 464 464 465 -=== 2. 6.4 Poll sensor value ===623 +=== 2.5.4 Poll sensor value === 466 466 467 467 468 468 Users can poll sensor values based on timestamps. Below is the downlink command. 469 469 470 470 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:425.818px" %) 471 -|(% colspan="4" style="background-color:# d9e2f3; color:#0070c0; width:423px" %)**Downlink Command to poll Open/Close status (0x31)**629 +|(% colspan="4" style="background-color:#4f81bd; color:white; width:423px" %)**Downlink Command to poll Open/Close status (0x31)** 472 472 |(% style="width:58px" %)**1byte**|(% style="width:127px" %)**4bytes**|(% style="width:124px" %)**4bytes**|(% style="width:114px" %)**1byte** 473 473 |(% style="width:58px" %)31|(% style="width:127px" %)Timestamp start|(% style="width:124px" %)Timestamp end|(% style="width:114px" %)Uplink Interval 474 474 ... ... @@ -489,7 +489,7 @@ 489 489 ))) 490 490 491 491 492 -== 2. 7Frequency Plans ==650 +== 2.6 Frequency Plans == 493 493 494 494 495 495 The LDS12-LB uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets. ... ... @@ -497,23 +497,22 @@ 497 497 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]] 498 498 499 499 500 -== 2. 8LiDAR ToF Measurement ==658 +== 2.7 LiDAR ToF Measurement == 501 501 502 -=== 2. 8.1 Principle of Distance Measurement ===660 +=== 2.7.1 Principle of Distance Measurement === 503 503 504 504 505 505 The LiDAR probe is based on TOF, namely, Time of Flight principle. To be specific, the product emits modulation wave of near infrared ray on a periodic basis, which will be reflected after contacting object. The product obtains the time of flight by measuring round-trip phase difference and then calculates relative range between the product and the detection object, as shown below. 506 506 665 +[[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"]] 507 507 508 -[[image:1654831757579-263.png]] 509 509 668 +=== 2.7.2 Distance Measurement Characteristics === 510 510 511 -=== 2.8.2 Distance Measurement Characteristics === 512 512 513 - 514 514 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: 515 515 516 -[[image:1654831774373-275.png]] 673 +[[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"]] 517 517 518 518 519 519 ((( ... ... @@ -533,23 +533,20 @@ 533 533 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: 534 534 ))) 535 535 693 +[[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"]] 536 536 537 -[[image:1654831797521-720.png]] 538 - 539 - 540 540 ((( 541 541 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. 542 542 ))) 543 543 544 -[[image:1654831810009-716.png]] 699 +[[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"]] 545 545 546 - 547 547 ((( 548 548 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. 549 549 ))) 550 550 551 551 552 -=== 2. 8.3 Notice of usage:===706 +=== 2.7.3 Notice of usage === 553 553 554 554 555 555 Possible invalid /wrong reading for LiDAR ToF tech: ... ... @@ -559,11 +559,11 @@ 559 559 * The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe. 560 560 * The sensor window is made by Acrylic. Don't touch it with alcohol material. This will destroy the sensor window. 561 561 562 -=== 2. 8.4 Reflectivity of different objects ===716 +=== 2.7.4 Reflectivity of different objects === 563 563 564 564 565 565 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:379px" %) 566 -|=(% 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" %)Relectivity720 +|=(% 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 567 567 |(% style="width:53px" %)1|(% style="width:229px" %)Black foam rubber|(% style="width:93px" %)2.4% 568 568 |(% style="width:53px" %)2|(% style="width:229px" %)Black fabric|(% style="width:93px" %)3% 569 569 |(% style="width:53px" %)3|(% style="width:229px" %)Black rubber|(% style="width:93px" %)4% ... ... @@ -630,7 +630,7 @@ 630 630 ))) 631 631 632 632 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 633 -|=(% style="width: 156px;background-color:# D9E2F3;#0070c0" %)**Command Example**|=(% style="width: 137px;background-color:#D9E2F3;#0070c0" %)**Function**|=(% style="background-color:#D9E2F3;#0070c0" %)**Response**787 +|=(% 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** 634 634 |(% style="width:156px" %)AT+TDC=?|(% style="width:137px" %)Show current transmit Interval|((( 635 635 30000 636 636 OK ... ... @@ -658,25 +658,32 @@ 658 658 ))) 659 659 * ((( 660 660 Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds 815 + 816 + 817 + 661 661 ))) 662 662 663 663 === 3.3.2 Set Interrupt Mode === 664 664 665 665 666 -Feature, Set Interrupt mode for PA8ofpin.823 +Feature, Set Interrupt mode for pin of GPIO_EXTI. 667 667 668 -When AT+INTMOD=0 is set, P A8is used as a digital input port.825 +When AT+INTMOD=0 is set, GPIO_EXTI is used as a digital input port. 669 669 670 670 (% style="color:blue" %)**AT Command: AT+INTMOD** 671 671 672 672 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 673 -|=(% 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**830 +|=(% 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** 674 674 |(% style="width:154px" %)AT+INTMOD=?|(% style="width:196px" %)Show current interrupt mode|(% style="width:157px" %)((( 675 675 0 676 676 OK 677 677 the mode is 0 =Disable Interrupt 678 678 ))) 679 -|(% style="width:154px" %)AT+INTMOD=2|(% style="width:196px" %)((( 836 +|(% style="width:154px" %)((( 837 +AT+INTMOD=2 838 + 839 +(default) 840 +)))|(% style="width:196px" %)((( 680 680 Set Transmit Interval 681 681 0. (Disable Interrupt), 682 682 ~1. (Trigger by rising and falling edge) ... ... @@ -694,86 +694,35 @@ 694 694 695 695 * Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger 696 696 858 +=== 3.3.3 Set Power Output Duration === 697 697 698 - ===3.3.3 GetFirmwareVersionInfo===860 +Control the output duration 3V3(pin of VBAT_OUT) . Before each sampling, device will 699 699 862 +~1. first enable the power output to external sensor, 700 700 701 - Feature:usedownlinktogetfirmwareversion.864 +2. keep it on as per duration, read sensor value and construct uplink payload 702 702 703 - (%style="color:#037691"%)**DownlinkCommand: 0x26**866 +3. final, close the power output. 704 704 705 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:492px" %) 706 -|(% 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)** 707 -|(% style="width:191px" %)Get Firmware Version Info|(% style="width:57px" %)Any|(% style="width:91px" %)26|(% style="width:151px" %)2 868 +(% style="color:blue" %)**AT Command: AT+3V3T** 708 708 709 -* Reply to the confirmation package: 26 01 710 -* Reply to non-confirmed packet: 26 00 870 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 871 +|=(% 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** 872 +|(% style="width:154px" %)AT+3V3T=?|(% style="width:196px" %)Show 3V3 open time.|(% style="width:157px" %)0 (default) 873 +OK 874 +|(% style="width:154px" %)AT+3V3T=1000|(% style="width:196px" %)Close after a delay of 1000 milliseconds.|(% style="width:157px" %)OK 875 +|(% style="width:154px" %)AT+3V3T=0|(% style="width:196px" %)Always turn on the power supply of 3V3 pin.|(% style="width:157px" %)OK 876 +|(% style="width:154px" %)AT+3V3T=65535|(% style="width:196px" %)Always turn off the power supply of 3V3 pin.|(% style="width:157px" %)OK 711 711 712 -Device will send an uplink after got this downlink command. With below payload: 878 +(% style="color:blue" %)**Downlink Command: 0x07**(%%) 879 +Format: Command Code (0x07) followed by 3 bytes. 713 713 714 - Configures infopayload:881 +The first byte is 01,the second and third bytes are the time to turn on. 715 715 716 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %) 717 -|=(% style="background-color:#D9E2F3;color:#0070C0" %)((( 718 -**Size(bytes)** 719 -)))|=(% 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** 720 -|**Value**|Software Type|((( 721 -Frequency 722 -Band 723 -)))|Sub-band|((( 724 -Firmware 725 -Version 726 -)))|Sensor Type|Reserve|((( 727 -[[Message Type>>||anchor="H2.3.7A0MessageType"]] 728 -Always 0x02 729 -))) 883 +* Example 1: Downlink Payload: 07 01 00 00 **~-~-->** AT+3V3T=0 884 +* Example 2: Downlink Payload: 07 01 01 F4 **~-~-->** AT+3V3T=500 885 +* Example 3: Downlink Payload: 07 01 FF FF **~-~-->** AT+3V3T=65535 730 730 731 -(% style="color:#037691" %)**Software Type**(%%): Always 0x03 for LLDS12 732 - 733 -(% style="color:#037691" %)**Frequency Band**: 734 - 735 -*0x01: EU868 736 - 737 -*0x02: US915 738 - 739 -*0x03: IN865 740 - 741 -*0x04: AU915 742 - 743 -*0x05: KZ865 744 - 745 -*0x06: RU864 746 - 747 -*0x07: AS923 748 - 749 -*0x08: AS923-1 750 - 751 -*0x09: AS923-2 752 - 753 -*0xa0: AS923-3 754 - 755 - 756 -(% style="color:#037691" %)**Sub-Band**(%%): value 0x00 ~~ 0x08 757 - 758 -(% style="color:#037691" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version 759 - 760 -(% style="color:#037691" %)**Sensor Type**: 761 - 762 -0x01: LSE01 763 - 764 -0x02: LDDS75 765 - 766 -0x03: LDDS20 767 - 768 -0x04: LLMS01 769 - 770 -0x05: LSPH01 771 - 772 -0x06: LSNPK01 773 - 774 -0x07: LLDS12 775 - 776 - 777 777 = 4. Battery & Power Consumption = 778 778 779 779 ... ... @@ -794,7 +794,7 @@ 794 794 795 795 * Fix bugs. 796 796 797 -Firmware and changelog can be downloaded from : **[[Firmware download link>>url:https://www.dropbox.com/sh/p h4uyz0rchflrnw/AADr1f_5Sg30804NItpfOQbla?dl=0]]**907 +Firmware and changelog can be downloaded from : **[[Firmware download link>>url:https://www.dropbox.com/sh/w1p7ukjrx49e62r/AAB3uCNCt-koYUvMkZUPBRSca?dl=0]]** 798 798 799 799 Methods to Update Firmware: 800 800 ... ... @@ -822,11 +822,11 @@ 822 822 823 823 824 824 ((( 825 -(% 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.) 935 +(% 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.) 826 826 ))) 827 827 828 828 ((( 829 -Troubleshooting: Please avoid use of this product under such circumstance in practice. 939 +(% style="color:red" %)**Troubleshooting**(%%): Please avoid use of this product under such circumstance in practice. 830 830 ))) 831 831 832 832 ... ... @@ -835,7 +835,7 @@ 835 835 ))) 836 836 837 837 ((( 838 -Troubleshooting: please use dry dust-free cloth to gently remove the foreign matter. 948 +(% style="color:red" %)**Troubleshooting**(%%): please use dry dust-free cloth to gently remove the foreign matter. 839 839 ))) 840 840 841 841
- 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
- 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