Changes for page LMDS200 -- LoRaWAN Microwave Radar Distance Sensor User Manual
Last modified by Mengting Qiu on 2024/03/07 08:41
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -4,7 +4,6 @@ 4 4 5 5 **Contents:** 6 6 7 -{{toc/}} 8 8 9 9 10 10 ... ... @@ -11,7 +11,6 @@ 11 11 12 12 13 13 14 - 15 15 = 1. Introduction = 16 16 17 17 == 1.1 What is LoRaWAN LiDAR ToF Distance Sensor == ... ... @@ -19,30 +19,18 @@ 19 19 ((( 20 20 21 21 22 -((( 23 23 The Dragino LLDS12 is a (% style="color:blue" %)**LoRaWAN LiDAR ToF (Time of Flight) Distance Sensor**(%%) for Internet of Things solution. It is capable to measure the distance to an object as close as 10 centimeters (+/- 5cm up to 6m) and as far as 12 meters (+/-1% starting at 6m)!. The LiDAR probe uses laser induction technology for distance measurement. 24 -))) 25 25 26 -((( 27 27 The LLDS12 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc. 28 -))) 29 29 30 -((( 31 31 It detects the distance between the measured object and the sensor, and uploads the value via wireless to LoRaWAN IoT Server. 32 -))) 33 33 34 -((( 35 35 The LoRa wireless technology used in LLDS12 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. 36 -))) 37 37 38 -((( 39 39 LLDS12 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years. 40 -))) 41 41 42 -((( 43 43 Each LLDS12 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. 44 44 ))) 45 -))) 46 46 47 47 48 48 [[image:1654826306458-414.png]] ... ... @@ -64,6 +64,7 @@ 64 64 * 8500mAh Battery for long term use 65 65 66 66 53 + 67 67 == 1.3 Probe Specification == 68 68 69 69 * Storage temperature :-20℃~~75℃ ... ... @@ -80,6 +80,7 @@ 80 80 * Wire length - 25cm 81 81 82 82 70 + 83 83 == 1.4 Probe Dimension == 84 84 85 85 ... ... @@ -86,6 +86,7 @@ 86 86 [[image:1654827224480-952.png]] 87 87 88 88 77 + 89 89 == 1.5 Applications == 90 90 91 91 * Horizontal distance measurement ... ... @@ -97,6 +97,7 @@ 97 97 * Sewer 98 98 99 99 89 + 100 100 == 1.6 Pin mapping and power on == 101 101 102 102 ... ... @@ -103,6 +103,8 @@ 103 103 [[image:1654827332142-133.png]] 104 104 105 105 96 + 97 + 106 106 = 2. Configure LLDS12 to connect to LoRaWAN network = 107 107 108 108 == 2.1 How it works == ... ... @@ -112,7 +112,7 @@ 112 112 ))) 113 113 114 114 ((( 115 -In case you can’t set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H6. A0UseATCommand"]]to set the keys in the LLDS12.107 +In case you can’t set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H6.UseATCommand"]]to set the keys in the LLDS12. 116 116 ))) 117 117 118 118 ... ... @@ -203,12 +203,14 @@ 203 203 |=(% style="width: 62.5px;" %)((( 204 204 **Size (bytes)** 205 205 )))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1** 206 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)((( 207 -[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]] 208 -)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|((( 209 -[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]] 210 -)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|((( 211 -[[Message Type>>||anchor="H2.3.7A0MessageType"]] 198 +|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1BatteryInfo"]]|(% style="width:62.5px" %)((( 199 +[[Temperature>>||anchor="H2.3.2DS18B20Temperaturesensor"]] 200 + 201 +[[(Optional)>>||anchor="H2.3.2DS18B20Temperaturesensor"]] 202 +)))|[[Soil pH>>||anchor="H2.3.3SoilpH"]]|[[Soil Temperature>>||anchor="H2.3.4SoilTemperature"]]|((( 203 +[[Digital Interrupt (Optional)>>||anchor="H2.3.5InterruptPin"]] 204 +)))|Reserve|((( 205 +[[Message Type>>||anchor="H2.3.6MessageType"]] 212 212 ))) 213 213 214 214 [[image:1654833689380-972.png]] ... ... @@ -215,10 +215,10 @@ 215 215 216 216 217 217 218 -=== 2.3.1 212 +=== 2.3.1 Battery Info === 219 219 220 220 221 -Check the battery voltage for L LDS12.215 +Check the battery voltage for LSPH01. 222 222 223 223 Ex1: 0x0B45 = 2885mV 224 224 ... ... @@ -226,7 +226,7 @@ 226 226 227 227 228 228 229 -=== 2.3.2 223 +=== 2.3.2 DS18B20 Temperature sensor === 230 230 231 231 This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature. 232 232 ... ... @@ -239,35 +239,33 @@ 239 239 240 240 241 241 242 -=== 2.3.3 Distance===236 +=== 2.3.3 Soil pH === 243 243 244 -R epresents the distance value of the measurement output, the default unit is cm, and the value rangeparsedasa decimal number is 0-1200.In actual use, when the signal strength value Strength.238 +Range: 0 ~~ 14 pH 245 245 240 +**Example:** 246 246 247 -** Example**:242 +(% style="color:#037691" %)** 0x02B7(H) = 695(D) = 6.95pH** 248 248 249 -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. 250 250 251 251 246 +=== 2.3.4 Soil Temperature === 252 252 253 - === 2.3.4 Distancesignalstrength===248 +Get Soil Temperature 254 254 255 -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. 256 256 257 - 258 258 **Example**: 259 259 260 -If payload is: 01 D7(H)=471(D),distancesignalstrength=471,471>100,471≠65535,theeasuredvalueofDistisconsidered credible.253 +If payload is: **0105H**: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree 261 261 262 - Customerscanjudgewhethertheyneedtoadjusttheenvironmentbasedonthesignalstrength.255 +If payload is: **FF3FH** : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. 263 263 264 264 265 265 266 -=== 2.3.5 259 +=== 2.3.5 Interrupt Pin === 267 267 268 -This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H 4.2A0SetInterruptMode"]] for the hardware and software set up.261 +This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.2SetInterruptMode"]] for the hardware and software set up. 269 269 270 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]]. 271 271 272 272 **Example:** 273 273 ... ... @@ -277,18 +277,8 @@ 277 277 278 278 279 279 280 -=== 2.3.6 LiDAR temp ===272 +=== 2.3.6 Message Type === 281 281 282 -Characterize the internal temperature value of the sensor. 283 - 284 -**Example: ** 285 -If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃. 286 -If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃. 287 - 288 - 289 - 290 -=== 2.3.7 Message Type === 291 - 292 292 ((( 293 293 For a normal uplink payload, the message type is always 0x01. 294 294 ))) ... ... @@ -302,8 +302,9 @@ 302 302 |=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload** 303 303 |(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]] 304 304 |(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.4GetFirmwareVersionInfo"]] 287 +|(% style="width:160px" %)0x03|(% style="width:163px" %)Reply Calibration Info|(% style="width:173px" %)[[Calibration Payload>>||anchor="H2.7Calibration"]] 305 305 306 -=== 2.3. 8Decode payload in The Things Network ===289 +=== 2.3.7 Decode payload in The Things Network === 307 307 308 308 While using TTN network, you can add the payload format to decode the payload. 309 309 ... ... @@ -471,7 +471,7 @@ 471 471 * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 472 472 * Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include) 473 473 474 -=== 2.6.3 457 +=== 2.6.3 CN470-510 (CN470) === 475 475 476 476 ((( 477 477 Used in China, Default use CHE=1 ... ... @@ -560,7 +560,7 @@ 560 560 561 561 562 562 563 -=== 2.6.4 546 +=== 2.6.4 AU915-928(AU915) === 564 564 565 565 ((( 566 566 Frequency band as per definition in LoRaWAN 1.0.3 Regional document. ... ... @@ -581,7 +581,7 @@ 581 581 * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 582 582 * Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include) 583 583 584 -=== 2.6.5 567 +=== 2.6.5 AS920-923 & AS923-925 (AS923) === 585 585 586 586 ((( 587 587 (% style="color:blue" %)**Default Uplink channel:** ... ... @@ -690,7 +690,7 @@ 690 690 691 691 692 692 693 -=== 2.6.6 676 +=== 2.6.6 KR920-923 (KR920) === 694 694 695 695 ((( 696 696 (% style="color:blue" %)**Default channel:** ... ... @@ -763,7 +763,7 @@ 763 763 764 764 765 765 766 -=== 2.6.7 749 +=== 2.6.7 IN865-867 (IN865) === 767 767 768 768 ((( 769 769 (% style="color:blue" %)**Uplink:** ... ... @@ -807,6 +807,7 @@ 807 807 * The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected. 808 808 * Blink once when device transmit a packet. 809 809 793 + 810 810 == 2.8 Firmware Change Log == 811 811 812 812 ... ... @@ -1260,3 +1260,4 @@ 1260 1260 1261 1261 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 1262 1262 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]. 1247 +