<
From version < 107.1 >
edited by Xiaoling
on 2022/06/10 11:52
To version < 109.10 >
edited by Xiaoling
on 2022/06/10 13:57
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,6 +4,7 @@
4 4  
5 5  **Contents:**
6 6  
7 +{{toc/}}
7 7  
8 8  
9 9  
... ... @@ -10,6 +10,7 @@
10 10  
11 11  
12 12  
14 +
13 13  = 1.  Introduction =
14 14  
15 15  == 1.1 ​ What is LoRaWAN LiDAR ToF Distance Sensor ==
... ... @@ -17,18 +17,30 @@
17 17  (((
18 18  
19 19  
22 +(((
20 20  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 +)))
21 21  
26 +(((
22 22  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 +)))
23 23  
30 +(((
24 24  It detects the distance between the measured object and the sensor, and uploads the value via wireless to LoRaWAN IoT Server.
32 +)))
25 25  
34 +(((
26 26  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 +)))
27 27  
38 +(((
28 28  LLDS12 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years.
40 +)))
29 29  
42 +(((
30 30  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.
31 31  )))
45 +)))
32 32  
33 33  
34 34  [[image:1654826306458-414.png]]
... ... @@ -81,7 +81,7 @@
81 81  * Automatic control
82 82  * Sewer
83 83  
84 -== 1.6 Pin mapping and power on ==
98 +== 1.6  Pin mapping and power on ==
85 85  
86 86  
87 87  [[image:1654827332142-133.png]]
... ... @@ -88,10 +88,11 @@
88 88  
89 89  
90 90  
91 -= 2. Configure LLDS12 to connect to LoRaWAN network =
92 92  
93 -== 2.1 How it works ==
106 += 2.  Configure LLDS12 to connect to LoRaWAN network =
94 94  
108 +== 2.1  How it works ==
109 +
95 95  (((
96 96  The LLDS12 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LLDS12. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.
97 97  )))
... ... @@ -101,7 +101,7 @@
101 101  )))
102 102  
103 103  
104 -== 2.2 ​Quick guide to connect to LoRaWAN server (OTAA) ==
119 +== 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
105 105  
106 106  (((
107 107  Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example.
... ... @@ -136,11 +136,13 @@
136 136  [[image:1654592600093-601.png]]
137 137  
138 138  
154 +
139 139  **Add APP EUI and DEV EUI**
140 140  
141 141  [[image:1654592619856-881.png]]
142 142  
143 143  
160 +
144 144  **Add APP EUI in the application**
145 145  
146 146  [[image:1654592632656-512.png]]
... ... @@ -152,7 +152,7 @@
152 152  [[image:1654592653453-934.png]]
153 153  
154 154  
155 -(% style="color:blue" %)**Step 2**(%%): Power on LSPH01
172 +(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
156 156  
157 157  
158 158  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
... ... @@ -161,17 +161,17 @@
161 161  
162 162  
163 163  (((
164 -(% style="color:blue" %)**Step 3**(%%)**:** The LSPH01 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel.
181 +(% style="color:blue" %)**Step 3**(%%)**:** The LLDS12 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel.
165 165  )))
166 166  
167 -[[image:1654592697690-910.png]]
184 +[[image:1654833501679-968.png]]
168 168  
169 169  
170 170  
171 -== 2.3 ​Uplink Payload ==
188 +== 2.3  ​Uplink Payload ==
172 172  
173 173  (((
174 -LSPH01 will uplink payload via LoRaWAN with below payload format: 
191 +LLDS12 will uplink payload via LoRaWAN with below payload format: 
175 175  )))
176 176  
177 177  (((
... ... @@ -179,7 +179,7 @@
179 179  )))
180 180  
181 181  (((
182 -Normal uplink payload:
199 +
183 183  )))
184 184  
185 185  (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
... ... @@ -189,21 +189,21 @@
189 189  |(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1BatteryInfo"]]|(% style="width:62.5px" %)(((
190 190  [[Temperature>>||anchor="H2.3.2DS18B20Temperaturesensor"]]
191 191  
192 -[[(Optional)>>||anchor="H2.3.2DS18B20Temperaturesensor"]]
193 -)))|[[Soil pH>>||anchor="H2.3.3SoilpH"]]|[[Soil Temperature>>||anchor="H2.3.4SoilTemperature"]]|(((
194 -[[Digital Interrupt (Optional)>>||anchor="H2.3.5InterruptPin"]]
195 -)))|Reserve|(((
209 +[[DS18B20>>||anchor="H2.3.2DS18B20Temperaturesensor"]]
210 +)))|[[Distance>>||anchor="H"]]|[[Distance signal strength>>||anchor="H2.3.4SoilTemperature"]]|(((
211 +[[Interrupt flag>>||anchor="H2.3.5InterruptPin"]]
212 +)))|[[LiDAR temp>>||anchor="H"]]|(((
196 196  [[Message Type>>||anchor="H2.3.6MessageType"]]
197 197  )))
198 198  
199 -[[image:1654592721645-318.png]]
216 +[[image:1654833689380-972.png]]
200 200  
201 201  
202 202  
203 -=== 2.3.1 Battery Info ===
220 +=== 2.3.1  Battery Info ===
204 204  
205 205  
206 -Check the battery voltage for LSPH01.
223 +Check the battery voltage for LLDS12.
207 207  
208 208  Ex1: 0x0B45 = 2885mV
209 209  
... ... @@ -211,7 +211,7 @@
211 211  
212 212  
213 213  
214 -=== 2.3.2 DS18B20 Temperature sensor ===
231 +=== 2.3.2  DS18B20 Temperature sensor ===
215 215  
216 216  This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
217 217  
... ... @@ -224,33 +224,35 @@
224 224  
225 225  
226 226  
227 -=== 2.3.3 Soil pH ===
244 +=== 2.3.3  Distance ===
228 228  
229 -Range: 0 ~~ 14 pH
246 +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.
230 230  
231 -**Example:**
232 232  
233 -(% style="color:#037691" %)** 0x02B7(H) = 695(D) = 6.95pH**
249 +**Example**:
234 234  
251 +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.
235 235  
236 236  
237 -=== 2.3.4 Soil Temperature ===
238 238  
239 -Get Soil Temperature 
255 +=== 2.3.4  Distance signal strength ===
240 240  
257 +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.
241 241  
259 +
242 242  **Example**:
243 243  
244 -If payload is: **0105H**:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
262 +If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
245 245  
246 -If payload is: **FF3FH** (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
264 +Customers can judge whether they need to adjust the environment based on the signal strength.
247 247  
248 248  
249 249  
250 -=== 2.3.5 Interrupt Pin ===
268 +=== 2.3.5  Interrupt Pin ===
251 251  
252 252  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.
253 253  
272 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>path:#pins]].
254 254  
255 255  **Example:**
256 256  
... ... @@ -260,8 +260,18 @@
260 260  
261 261  
262 262  
263 -=== 2.3.6 Message Type ===
282 +=== 2.3.6  LiDAR temp ===
264 264  
284 +Characterize the internal temperature value of the sensor.
285 +
286 +**Example: **
287 +If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
288 +If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
289 +
290 +
291 +
292 +=== 2.3.7  Message Type ===
293 +
265 265  (((
266 266  For a normal uplink payload, the message type is always 0x01.
267 267  )))
... ... @@ -275,10 +275,11 @@
275 275  |=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
276 276  |(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]
277 277  |(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.4GetFirmwareVersionInfo"]]
278 -|(% style="width:160px" %)0x03|(% style="width:163px" %)Reply Calibration Info|(% style="width:173px" %)[[Calibration Payload>>||anchor="H2.7Calibration"]]
279 279  
280 -=== 2.3.7 Decode payload in The Things Network ===
281 281  
309 +
310 +=== 2.3.8  Decode payload in The Things Network ===
311 +
282 282  While using TTN network, you can add the payload format to decode the payload.
283 283  
284 284  
... ... @@ -294,13 +294,13 @@
294 294  
295 295  
296 296  
297 -== 2.4 Uplink Interval ==
327 +== 2.4  Uplink Interval ==
298 298  
299 -The LSPH01 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>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]
329 +The LLDS12 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>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]
300 300  
301 301  
302 302  
303 -== 2.5 ​Show Data in DataCake IoT Server ==
333 +== 2.5  ​Show Data in DataCake IoT Server ==
304 304  
305 305  (((
306 306  [[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:
... ... @@ -327,42 +327,40 @@
327 327  
328 328  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
329 329  
330 -(% style="color:blue" %)**Step 4**(%%)**: Create LSPH01 product.**
360 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
331 331  
332 -[[image:1654592819047-535.png]]
362 +[[image:1654832691989-514.png]]
333 333  
334 334  
335 -
336 336  [[image:1654592833877-762.png]]
337 337  
338 338  
339 -[[image:1654592856403-259.png]]
368 +[[image:1654832740634-933.png]]
340 340  
341 341  
371 +
342 342  (((
343 343  (% style="color:blue" %)**Step 5**(%%)**: add payload decode**
344 344  )))
345 345  
346 346  (((
347 -Download Datacake decoder from: [[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/LSPH01/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSNPK01/Decoder/]]
377 +
348 348  )))
349 349  
380 +[[image:1654833065139-942.png]]
350 350  
351 -[[image:1654592878525-845.png]]
352 352  
353 -[[image:1654592892967-474.png]]
354 354  
384 +[[image:1654833092678-390.png]]
355 355  
356 -[[image:1654592905354-123.png]]
357 357  
358 358  
359 -After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
388 +After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
360 360  
390 +[[image:1654833163048-332.png]]
361 361  
362 -[[image:1654592917530-261.png]]
363 363  
364 364  
365 -
366 366  == 2.6  Frequency Plans ==
367 367  
368 368  (((
... ... @@ -447,9 +447,8 @@
447 447  * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
448 448  * 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)
449 449  
478 +=== 2.6.3  CN470-510 (CN470) ===
450 450  
451 -=== 2.6.3 CN470-510 (CN470) ===
452 -
453 453  (((
454 454  Used in China, Default use CHE=1
455 455  )))
... ... @@ -537,7 +537,7 @@
537 537  
538 538  
539 539  
540 -=== 2.6.4 AU915-928(AU915) ===
567 +=== 2.6.4  AU915-928(AU915) ===
541 541  
542 542  (((
543 543  Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
... ... @@ -558,7 +558,7 @@
558 558  * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
559 559  * 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)
560 560  
561 -=== 2.6.5 AS920-923 & AS923-925 (AS923) ===
588 +=== 2.6.5  AS920-923 & AS923-925 (AS923) ===
562 562  
563 563  (((
564 564  (% style="color:blue" %)**Default Uplink channel:**
... ... @@ -667,7 +667,7 @@
667 667  
668 668  
669 669  
670 -=== 2.6.6 KR920-923 (KR920) ===
697 +=== 2.6.6  KR920-923 (KR920) ===
671 671  
672 672  (((
673 673  (% style="color:blue" %)**Default channel:**
... ... @@ -740,7 +740,7 @@
740 740  
741 741  
742 742  
743 -=== 2.6.7 IN865-867 (IN865) ===
770 +=== 2.6.7  IN865-867 (IN865) ===
744 744  
745 745  (((
746 746  (% style="color:blue" %)**Uplink:**
... ... @@ -784,8 +784,6 @@
784 784  * The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
785 785  * Blink once when device transmit a packet.
786 786  
787 -
788 -
789 789  == 2.8  ​Firmware Change Log ==
790 790  
791 791  
... ... @@ -1239,5 +1239,3 @@
1239 1239  
1240 1240  * 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.
1241 1241  * 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]].
1242 -
1243 -
1654833501679-968.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +58.3 KB
Content
1654833689380-972.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +60.5 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0