Skip to Content
Last modified by Mengting Qiu on 2025/08/06 17:02
From version 169.6
edited by Xiaoling
on 2022/06/15 09:34
Change comment: There is no comment for this version
To version 125.1
edited by Xiaoling
on 2022/06/10 16:10
Change comment: Uploaded new attachment "1654848616367-242.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -LDDS20 - LoRaWAN Ultrasonic Liquid Level Sensor User Manual
1 +LDDS75 - LoRaWAN Distance Detection Sensor User Manual
Content
... ... @@ -1,97 +1,54 @@
1 1  (% style="text-align:center" %)
2 -[[image:1655254599445-662.png]]
2 +[[image:1654846127817-788.png]]
3 3  
4 +**Contents:**
4 4  
5 5  
6 6  
7 -**Table of Contents:**
8 8  
9 9  
10 10  
11 11  
12 12  
13 -
14 -
15 -
16 16  = 1.  Introduction =
17 17  
18 -== 1.1 ​ What is LoRaWAN Ultrasonic liquid level Sensor ==
15 +== 1.1 ​ What is LoRaWAN Distance Detection Sensor ==
19 19  
20 20  (((
21 21  
22 22  
23 23  (((
24 -(((
25 -(((
26 -The Dragino LDDS20 is a (% style="color:#4472c4" %)**LoRaWAN Ultrasonic liquid level sensor**(%%) for Internet of Things solution. It uses (% style="color:#4472c4" %)**none-contact method **(%%)to measure the height of liquid in a container without opening the container, and send the value via LoRaWAN network to IoT Server
27 -)))
21 +The Dragino LDDS75 is a (% style="color:#4472c4" %)** LoRaWAN Distance Detection Sensor**(%%) for Internet of Things solution. It is used to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses (% style="color:#4472c4" %)** ultrasonic sensing** (%%)technology for distance measurement, and (% style="color:#4472c4" %)** temperature compensation**(%%) is performed internally to improve the reliability of data. The LDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc.
28 28  
29 -(((
30 -
31 -)))
32 32  
33 -(((
34 -The LDDS20 sensor is installed directly below the container to detect the height of the liquid level. User doesn’t need to open a hole on the container to be tested. The (% style="color:#4472c4" %)**none-contact measurement makes the measurement safety, easier and possible for some strict situation**. 
35 -)))
24 +It detects the distance** (% style="color:#4472c4" %) between the measured object and the sensor(%%)**, and uploads the value via wireless to LoRaWAN IoT Server.
36 36  
37 -(((
38 -
39 -)))
40 40  
41 -(((
42 -LDDS20 uses ultrasonic sensing technology for distance measurement. LDDS20 is of high accuracy to measure various liquid such as: (% style="color:#4472c4" %)**toxic substances**(%%), (% style="color:#4472c4" %)**strong acids**(%%), (% style="color:#4472c4" %)**strong alkalis**(%%) and (% style="color:#4472c4" %)**various pure liquids**(%%) in high-temperature and high-pressure airtight containers.
43 -)))
27 +The LoRa wireless technology used in LDDS75 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.
44 44  
45 -(((
46 -
47 -)))
48 48  
49 -(((
50 -The LoRa wireless technology used in LDDS20 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.
51 -)))
30 +LDDS75 is powered by (% style="color:#4472c4" %)** 4000mA or 8500mAh Li-SOCI2 battery**(%%); It is designed for long term use up to 10 years*.
52 52  
53 -(((
54 -
55 -)))
56 56  
57 -(((
58 -LDDS20 is powered by (% style="color:#4472c4" %)**8500mA Li-SOCI2 battery**(%%); It is designed for long term use up to 10 years*.
59 -)))
33 +Each LDDS75 pre-loads with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect if there is network coverage, after power on.
60 60  
61 -(((
62 -
63 -)))
64 64  
65 -(((
66 -Each LDDS20 pre-loads with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect if there is network coverage, after power on.
36 +(% style="color:#4472c4" %) ***** (%%)Actually lifetime depends on network coverage and uplink interval and other factors
67 67  )))
68 -
69 -(((
70 -
71 71  )))
72 -)))
73 73  
74 -(((
75 -(((
76 -(% style="color:#4472c4" %) * (%%)Actually lifetime depends on network coverage and uplink interval and other factors.
77 -)))
78 -)))
79 -)))
80 -)))
81 81  
41 +[[image:1654847051249-359.png]]
82 82  
83 -[[image:1655255122126-327.png]]
84 84  
85 85  
86 -
87 87  == ​1.2  Features ==
88 88  
89 89  * LoRaWAN 1.0.3 Class A
90 90  * Ultra low power consumption
91 -* Liquid Level Measurement by Ultrasonic technology
92 -* Measure through container, No need to contact Liquid.
93 -* Valid level range 20mm - 2000mm
94 -* Accuracy: ±(5mm+S*0.5%) (S: Measure Value)
49 +* Distance Detection by Ultrasonic technology
50 +* Flat object range 280mm - 7500mm
51 +* Accuracy: ±(1cm+S*0.3%) (S: Distance)
95 95  * Cable Length : 25cm
96 96  * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
97 97  * AT Commands to change parameters
... ... @@ -98,102 +98,32 @@
98 98  * Uplink on periodically
99 99  * Downlink to change configure
100 100  * IP66 Waterproof Enclosure
101 -* 8500mAh Battery for long term use
58 +* 4000mAh or 8500mAh Battery for long term use
102 102  
103 103  
104 -== 1.3  Suitable Container & Liquid ==
61 +== 1.3  Specification ==
105 105  
106 -* Solid Wall container such as: steel, iron, glass, ceramics, non-foaming plastics etc.
107 -* Container shape is regular, and surface is smooth.
108 -* Container Thickness:
109 -** Pure metal material.  2~~8mm, best is 3~~5mm
110 -** Pure non metal material: <10 mm
111 -* Pure liquid without irregular deposition.
63 +=== 1.3.1  Rated environmental conditions ===
112 112  
65 +[[image:image-20220610154839-1.png]]
113 113  
114 -== 1.4  Mechanical ==
67 +**Remarks: (1) a. When the ambient temperature is 0-39 ℃, the maximum humidity is 90% (non-condensing);**
115 115  
116 -[[image:image-20220615090910-1.png]]
69 +**b. When the ambient temperature is 40-50 ℃, the highest humidity is the highest humidity in the natural world at the current temperature (no condensation)**
117 117  
118 118  
119 -[[image:image-20220615090910-2.png]]
120 120  
73 +=== 1.3.2  Effective measurement range Reference beam pattern ===
121 121  
75 +**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**[[image:image-20220610155021-2.png||height="440" width="1189"]]
122 122  
123 -== 1.5  Install LDDS20 ==
124 124  
125 125  
126 -(% style="color:blue" %)**Step 1**(%%):  Choose the installation point.
79 +**(2)** The object to be tested is a "corrugated cardboard box" perpendicular to the central axis of 0 °, and the length * width is 60cm * 50cm.[[image:image-20220610155021-3.png||height="437" width="1192"]]
127 127  
128 -LDDS20 (% style="color:red" %)**MUST**(%%) be installed on the container bottom middle position.
81 +(% style="display:none" %) (%%)
129 129  
130 -[[image:image-20220615091045-3.png]]
131 131  
132 -
133 -
134 -(% style="color:blue" %)**Step 2**(%%):  Polish the installation point.
135 -
136 -For Metal Surface with paint, it is important to polish the surface, first use crude sand paper to polish the paint level , then use exquisite sand paper to polish the metal level to make it shine & smooth.
137 -
138 -[[image:image-20220615092010-11.png]]
139 -
140 -
141 -No polish needed if the container is shine metal surface without paint or non-metal container.
142 -
143 -[[image:image-20220615092044-12.png]]
144 -
145 -
146 -(% style="color:blue" %)**Step3:   **(%%)Test the installation point.
147 -
148 -Power on LDDS75, check if the blue LED is on, If the blue LED is on, means the sensor works. Then put ultrasonic coupling paste on the sensor and put it tightly on the installation point.
149 -
150 -
151 -It is necessary to put the coupling paste between the sensor and the container, otherwise LDDS20 won’t detect the liquid level.
152 -
153 -[[image:1655256160324-178.png]][[image:image-20220615092327-13.png]]
154 -
155 -
156 -After paste the LDDS20 well, power on LDDS20. In the first 30 seconds of booting, device will check the sensors status and BLUE LED will show the status as below. After 30 seconds, BLUE LED will be off to save battery life.
157 -
158 -
159 -(% style="color:red" %)**LED Status:**
160 -
161 -* Onboard LED: When power on device, the onboard LED will fast blink 4 times which means detect the sensor well.
162 -
163 -* (% style="color:blue" %)BLUE LED(% style="color:red" %) always ON(%%): Sensor is power on but doesn’t detect liquid. There is problem in installation point.
164 -* (% style="color:blue" %)BLUE LED(% style="color:red" %) slowly blinking(%%): Sensor detects Liquid Level, The installation point is good.
165 -
166 -LDDS20 will enter into low power mode at 30 seconds after system reset or power on, Blue LED will be off after that.
167 -
168 -
169 -(% style="color:red" %)**Note 2:**
170 -
171 -(% style="color:red" %)Ultrasonic coupling paste (%%) is subjected in most shipping way. So the default package doesn’t include it and user needs to purchase locally.
172 -
173 -
174 -(% style="color:blue" %)**Step4:   **(%%)Install use Epoxy ab glue.
175 -
176 -
177 -Prepare Eproxy AB glue.
178 -
179 -Put Eproxy AB glue in the sensor and press it hard on the container installation point.
180 -
181 -Reset LDDS20 and see if the BLUE LED is slowly blinking.
182 -
183 -[[image:image-20220615091045-8.png||height="226" width="380"]] [[image:image-20220615091045-9.png||height="239" width="339"]]
184 -
185 -
186 -(% style="color:red" %)**Note 1:**
187 -
188 -Eproxy AB glue needs 3~~ 5 minutes to stable attached. we can use other glue material to keep it in the position.
189 -
190 -
191 -(% style="color:red" %)**Note 2:**
192 -
193 -(% style="color:red" %)Eproxy AB glue(%%) is subjected in most shipping way. So the default package doesn’t include it and user needs to purchase locally.
194 -
195 -
196 -
197 197  == 1.5 ​ Applications ==
198 198  
199 199  * Horizontal distance measurement
... ... @@ -206,6 +206,8 @@
206 206  * Sewer
207 207  * Bottom water level monitoring
208 208  
96 +
97 +
209 209  == 1.6  Pin mapping and power on ==
210 210  
211 211  
... ... @@ -212,7 +212,6 @@
212 212  [[image:1654847583902-256.png]]
213 213  
214 214  
215 -
216 216  = 2.  Configure LDDS75 to connect to LoRaWAN network =
217 217  
218 218  == 2.1  How it works ==
... ... @@ -226,7 +226,6 @@
226 226  )))
227 227  
228 228  
229 -
230 230  == 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
231 231  
232 232  (((
... ... @@ -234,7 +234,7 @@
234 234  )))
235 235  
236 236  (((
237 -[[image:1654848616367-242.png]]
124 +[[image:1654827857527-556.png]]
238 238  )))
239 239  
240 240  (((
... ... @@ -242,67 +242,57 @@
242 242  )))
243 243  
244 244  (((
245 -
246 -
247 -(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS75.
132 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSPH01.
248 248  )))
249 249  
250 250  (((
251 -Each LDDS75 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
136 +Each LSPH01 is shipped with a sticker with the default device EUI as below:
252 252  )))
253 253  
254 254  [[image:image-20220607170145-1.jpeg]]
255 255  
256 256  
257 -(((
258 -For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
259 -)))
260 260  
261 -(((
262 -Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
263 -)))
143 +You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
264 264  
265 -(((
266 -
267 267  
268 -**Add APP EUI in the application**
269 -)))
146 +**Register the device**
270 270  
271 -[[image:image-20220610161353-4.png]]
272 272  
273 -[[image:image-20220610161353-5.png]]
149 +[[image:1654592600093-601.png]]
274 274  
275 -[[image:image-20220610161353-6.png]]
276 276  
277 277  
278 -[[image:image-20220610161353-7.png]]
153 +**Add APP EUI and DEV EUI**
279 279  
155 +[[image:1654592619856-881.png]]
280 280  
281 -You can also choose to create the device manually.
282 282  
283 - [[image:image-20220610161538-8.png]]
284 284  
159 +**Add APP EUI in the application**
285 285  
161 +[[image:1654592632656-512.png]]
286 286  
287 -**Add APP KEY and DEV EUI**
288 288  
289 -[[image:image-20220610161538-9.png]]
290 290  
165 +**Add APP KEY**
291 291  
167 +[[image:1654592653453-934.png]]
292 292  
293 -(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
294 294  
170 +(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
295 295  
172 +
296 296  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
297 297  
298 -[[image:image-20220610161724-10.png]]
175 +[[image:image-20220607170442-2.png]]
299 299  
300 300  
301 301  (((
302 -(% style="color:blue" %)**Step 3**(%%)**:** The LDDS75 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.
179 +(% 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.
303 303  )))
304 304  
305 -[[image:1654849068701-275.png]]
182 +[[image:1654833501679-968.png]]
306 306  
307 307  
308 308  
... ... @@ -309,15 +309,12 @@
309 309  == 2.3  ​Uplink Payload ==
310 310  
311 311  (((
312 -(((
313 -LDDS75 will uplink payload via LoRaWAN with below payload format: 
189 +LLDS12 will uplink payload via LoRaWAN with below payload format: 
314 314  )))
315 315  
316 316  (((
317 -Uplink payload includes in total 4 bytes.
318 -Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
193 +Uplink payload includes in total 11 bytes.
319 319  )))
320 -)))
321 321  
322 322  (((
323 323  
... ... @@ -326,23 +326,23 @@
326 326  (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
327 327  |=(% style="width: 62.5px;" %)(((
328 328  **Size (bytes)**
329 -)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
330 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
331 -[[Distance>>||anchor="H2.3.2A0Distance"]]
203 +)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
204 +|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
205 +[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
206 +)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
207 +[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
208 +)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
209 +[[Message Type>>||anchor="H2.3.7A0MessageType"]]
210 +)))
332 332  
333 -(unit: mm)
334 -)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.3A0InterruptPin"]]|(((
335 -[[Temperature (Optional )>>||anchor="H2.3.4A0DS18B20Temperaturesensor"]]
336 -)))|[[Sensor Flag>>||anchor="H2.3.5A0SensorFlag"]]
212 +[[image:1654833689380-972.png]]
337 337  
338 -[[image:1654850511545-399.png]]
339 339  
340 340  
341 -
342 342  === 2.3.1  Battery Info ===
343 343  
344 344  
345 -Check the battery voltage for LDDS75.
219 +Check the battery voltage for LLDS12.
346 346  
347 347  Ex1: 0x0B45 = 2885mV
348 348  
... ... @@ -350,69 +350,96 @@
350 350  
351 351  
352 352  
353 -=== 2.3.2  Distance ===
227 +=== 2.3.2  DS18B20 Temperature sensor ===
354 354  
355 -(((
356 -Get the distance. Flat object range 280mm - 7500mm.
357 -)))
229 +This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
358 358  
359 -(((
360 -For example, if the data you get from the register is 0x0B 0x05, the distance between the sensor and the measured object is(% style="color:#4472c4" %)** 0B05(H) = 2821 (D) = 2821 mm.**
361 -)))
362 362  
232 +**Example**:
363 363  
364 -* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
365 -* If the sensor value lower than 0x0118 (280mm), the sensor value will be invalid. Since v1.1.4, all value lower than 280mm will be set to 0x0014(20mm) which means the value is invalid.
234 +If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
366 366  
367 -=== 2.3.3  Interrupt Pin ===
236 +If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
368 368  
369 -This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.3A0SetInterruptMode"]] for the hardware and software set up.
370 370  
371 -**Example:**
372 372  
373 -0x00: Normal uplink packet.
240 +=== 2.3.3  Distance ===
374 374  
375 -0x01: Interrupt Uplink Packet.
242 +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.
376 376  
377 377  
245 +**Example**:
378 378  
379 -=== 2.3.4  DS18B20 Temperature sensor ===
247 +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.
380 380  
381 -This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
382 382  
250 +
251 +=== 2.3.4  Distance signal strength ===
252 +
253 +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.
254 +
255 +
383 383  **Example**:
384 384  
385 -If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
258 +If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
386 386  
387 -If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
260 +Customers can judge whether they need to adjust the environment based on the signal strength.
388 388  
389 -(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
390 390  
391 391  
264 +=== 2.3.5  Interrupt Pin ===
392 392  
393 -=== 2.3.5  Sensor Flag ===
266 +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.
394 394  
268 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
269 +
270 +**Example:**
271 +
272 +0x00: Normal uplink packet.
273 +
274 +0x01: Interrupt Uplink Packet.
275 +
276 +
277 +
278 +=== 2.3.6  LiDAR temp ===
279 +
280 +Characterize the internal temperature value of the sensor.
281 +
282 +**Example: **
283 +If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
284 +If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
285 +
286 +
287 +
288 +=== 2.3.7  Message Type ===
289 +
395 395  (((
396 -0x01: Detect Ultrasonic Sensor
291 +For a normal uplink payload, the message type is always 0x01.
397 397  )))
398 398  
399 399  (((
400 -0x00: No Ultrasonic Sensor
295 +Valid Message Type:
401 401  )))
402 402  
403 403  
299 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
300 +|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
301 +|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
302 +|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
404 404  
405 -=== 2.3.6  Decode payload in The Things Network ===
304 +=== 2.3.8  Decode payload in The Things Network ===
406 406  
407 407  While using TTN network, you can add the payload format to decode the payload.
408 408  
409 409  
410 -[[image:1654850829385-439.png]]
309 +[[image:1654592762713-715.png]]
411 411  
412 -The payload decoder function for TTN V3 is here:
311 +(((
312 +The payload decoder function for TTN is here:
313 +)))
413 413  
414 414  (((
415 -LDDS75 TTN V3 Payload Decoder: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LDDS75/Payload_Decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Payload_Decoder/]]
316 +LLDS12 TTN Payload Decoder: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Decoder/]]
416 416  )))
417 417  
418 418  
... ... @@ -419,7 +419,7 @@
419 419  
420 420  == 2.4  Uplink Interval ==
421 421  
422 -The LDDS75 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"]]
323 +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"]]
423 423  
424 424  
425 425  
... ... @@ -450,25 +450,47 @@
450 450  
451 451  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
452 452  
453 -(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
354 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
454 454  
455 -[[image:1654851029373-510.png]]
356 +[[image:1654832691989-514.png]]
456 456  
457 457  
458 -After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
359 +[[image:1654592833877-762.png]]
459 459  
460 -[[image:image-20220610165129-11.png||height="595" width="1088"]]
461 461  
362 +[[image:1654832740634-933.png]]
462 462  
463 463  
464 -== 2.6  Frequency Plans ==
465 465  
466 466  (((
467 -The LDDS75 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.
367 +(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
468 468  )))
469 469  
370 +(((
371 +
372 +)))
470 470  
374 +[[image:1654833065139-942.png]]
471 471  
376 +
377 +
378 +[[image:1654833092678-390.png]]
379 +
380 +
381 +
382 +After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
383 +
384 +[[image:1654833163048-332.png]]
385 +
386 +
387 +
388 +== 2.6  Frequency Plans ==
389 +
390 +(((
391 +The LLDS12 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.
392 +)))
393 +
394 +
472 472  === 2.6.1  EU863-870 (EU868) ===
473 473  
474 474  (((
... ... @@ -532,51 +532,20 @@
532 532  === 2.6.2  US902-928(US915) ===
533 533  
534 534  (((
535 -Used in USA, Canada and South America. Default use CHE=2
458 +Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
459 +)))
536 536  
537 -(% style="color:blue" %)**Uplink:**
461 +(((
462 +To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
463 +)))
538 538  
539 -903.9 - SF7BW125 to SF10BW125
540 -
541 -904.1 - SF7BW125 to SF10BW125
542 -
543 -904.3 - SF7BW125 to SF10BW125
544 -
545 -904.5 - SF7BW125 to SF10BW125
546 -
547 -904.7 - SF7BW125 to SF10BW125
548 -
549 -904.9 - SF7BW125 to SF10BW125
550 -
551 -905.1 - SF7BW125 to SF10BW125
552 -
553 -905.3 - SF7BW125 to SF10BW125
554 -
555 -
556 -(% style="color:blue" %)**Downlink:**
557 -
558 -923.3 - SF7BW500 to SF12BW500
559 -
560 -923.9 - SF7BW500 to SF12BW500
561 -
562 -924.5 - SF7BW500 to SF12BW500
563 -
564 -925.1 - SF7BW500 to SF12BW500
565 -
566 -925.7 - SF7BW500 to SF12BW500
567 -
568 -926.3 - SF7BW500 to SF12BW500
569 -
570 -926.9 - SF7BW500 to SF12BW500
571 -
572 -927.5 - SF7BW500 to SF12BW500
573 -
574 -923.3 - SF12BW500(RX2 downlink only)
575 -
576 -
577 -
465 +(((
466 +After Join success, the end node will switch to the correct sub band by:
578 578  )))
579 579  
469 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
470 +* 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)
471 +
580 580  === 2.6.3  CN470-510 (CN470) ===
581 581  
582 582  (((
... ... @@ -665,54 +665,28 @@
665 665  
666 666  
667 667  
560 +
668 668  === 2.6.4  AU915-928(AU915) ===
669 669  
670 670  (((
671 -Default use CHE=2
564 +Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
565 +)))
672 672  
673 -(% style="color:blue" %)**Uplink:**
567 +(((
568 +To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
569 +)))
674 674  
675 -916.8 - SF7BW125 to SF12BW125
676 -
677 -917.0 - SF7BW125 to SF12BW125
678 -
679 -917.2 - SF7BW125 to SF12BW125
680 -
681 -917.4 - SF7BW125 to SF12BW125
682 -
683 -917.6 - SF7BW125 to SF12BW125
684 -
685 -917.8 - SF7BW125 to SF12BW125
686 -
687 -918.0 - SF7BW125 to SF12BW125
688 -
689 -918.2 - SF7BW125 to SF12BW125
690 -
691 -
692 -(% style="color:blue" %)**Downlink:**
693 -
694 -923.3 - SF7BW500 to SF12BW500
695 -
696 -923.9 - SF7BW500 to SF12BW500
697 -
698 -924.5 - SF7BW500 to SF12BW500
699 -
700 -925.1 - SF7BW500 to SF12BW500
701 -
702 -925.7 - SF7BW500 to SF12BW500
703 -
704 -926.3 - SF7BW500 to SF12BW500
705 -
706 -926.9 - SF7BW500 to SF12BW500
707 -
708 -927.5 - SF7BW500 to SF12BW500
709 -
710 -923.3 - SF12BW500(RX2 downlink only)
711 -
712 -
571 +(((
713 713  
714 714  )))
715 715  
575 +(((
576 +After Join success, the end node will switch to the correct sub band by:
577 +)))
578 +
579 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
580 +* 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)
581 +
716 716  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
717 717  
718 718  (((
... ... @@ -821,6 +821,7 @@
821 821  
822 822  
823 823  
690 +
824 824  === 2.6.6  KR920-923 (KR920) ===
825 825  
826 826  (((
... ... @@ -893,6 +893,7 @@
893 893  
894 894  
895 895  
763 +
896 896  === 2.6.7  IN865-867 (IN865) ===
897 897  
898 898  (((
... ... @@ -929,93 +929,95 @@
929 929  
930 930  
931 931  
800 +
932 932  == 2.7  LED Indicator ==
933 933  
934 -The LDDS75 has an internal LED which is to show the status of different state.
803 +The LLDS12 has an internal LED which is to show the status of different state.
935 935  
936 -
937 -* Blink once when device power on.
938 -* The device detects the sensor and flashes 5 times.
939 -* Solid ON for 5 seconds once device successful Join the network.
805 +* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
940 940  * Blink once when device transmit a packet.
941 941  
942 942  == 2.8  ​Firmware Change Log ==
943 943  
944 944  
945 -(((
946 -**Firmware download link: **[[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/]]
947 -)))
811 +**Firmware download link: **[[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Firmware/]]
948 948  
949 -(((
950 -
951 -)))
952 952  
953 -(((
954 954  **Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
955 -)))
956 956  
957 957  
958 958  
959 -== 2.9  Mechanical ==
818 += 3.  LiDAR ToF Measurement =
960 960  
820 +== 3.1 Principle of Distance Measurement ==
961 961  
962 -[[image:image-20220610172003-1.png]]
822 +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.
963 963  
824 +[[image:1654831757579-263.png]]
964 964  
965 -[[image:image-20220610172003-2.png]]
966 966  
967 967  
828 +== 3.2 Distance Measurement Characteristics ==
968 968  
969 -== 2.10  Battery Analysis ==
830 +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:
970 970  
971 -=== 2.10.1  Battery Type ===
832 +[[image:1654831774373-275.png]]
972 972  
973 -The LDDS75 battery is a combination of a 4000mAh or 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
974 974  
835 +(((
836 +(% style="color:blue" %)**① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
837 +)))
975 975  
976 -The battery related documents as below:
839 +(((
840 +(% style="color:blue" %)**② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
841 +)))
977 977  
978 -* (((
979 -[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
843 +(((
844 +(% style="color:blue" %)**③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
980 980  )))
981 -* (((
982 -[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
983 -)))
984 -* (((
985 -[[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC_1520_datasheet.jpg]], [[Tech Spec>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC1520%20Technical%20Specification20171123.pdf]]
986 -)))
987 987  
988 - [[image:image-20220610172400-3.png]]
989 989  
848 +(((
849 +Vertical Coordinates: Represents the radius of light spot for The LiDAR probe at the 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:
850 +)))
990 990  
991 991  
992 -=== 2.10.2  Replace the battery ===
853 +[[image:1654831797521-720.png]]
993 993  
994 -(((
995 -You can change the battery in the LDDS75.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
996 -)))
997 997  
998 998  (((
999 -
857 +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.
1000 1000  )))
1001 1001  
860 +[[image:1654831810009-716.png]]
861 +
862 +
1002 1002  (((
1003 -The default battery pack of LDDS75 includes a ER18505 plus super capacitor. If user can't find this pack locally, they can find ER18505 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)
864 +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.
1004 1004  )))
1005 1005  
1006 1006  
1007 1007  
1008 -= 3.  Configure LDDS75 via AT Command or LoRaWAN Downlink =
869 +== 3.3 Notice of usage: ==
1009 1009  
871 +Possible invalid /wrong reading for LiDAR ToF tech:
872 +
873 +* Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
874 +* While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might wrong.
875 +* The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
876 +* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
877 +
878 += 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
879 +
1010 1010  (((
1011 1011  (((
1012 -Use can configure LDDS75 via AT Command or LoRaWAN Downlink.
882 +Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
1013 1013  )))
1014 1014  )))
1015 1015  
1016 1016  * (((
1017 1017  (((
1018 -AT Command Connection: See [[FAQ>>||anchor="H4.A0FAQ"]].
888 +AT Command Connection: See [[FAQ>>||anchor="H7.A0FAQ"]].
1019 1019  )))
1020 1020  )))
1021 1021  * (((
... ... @@ -1030,7 +1030,7 @@
1030 1030  )))
1031 1031  
1032 1032  (((
1033 -There are two kinds of commands to configure LDDS75, they are:
903 +There are two kinds of commands to configure LLDS12, they are:
1034 1034  )))
1035 1035  )))
1036 1036  
... ... @@ -1071,155 +1071,352 @@
1071 1071  
1072 1072  * (((
1073 1073  (((
1074 -(% style="color:#4f81bd" %)** Commands special design for LDDS75**
944 +(% style="color:#4f81bd" %)** Commands special design for LLDS12**
1075 1075  )))
1076 1076  )))
1077 1077  
1078 1078  (((
1079 1079  (((
1080 -These commands only valid for LDDS75, as below:
950 +These commands only valid for LLDS12, as below:
1081 1081  )))
1082 1082  )))
1083 1083  
1084 1084  
1085 1085  
1086 -== 3.1  Access AT Commands ==
956 +== 4.1  Set Transmit Interval Time ==
1087 1087  
1088 -LDDS75 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LDDS75 for using AT command, as below.
958 +Feature: Change LoRaWAN End Node Transmit Interval.
1089 1089  
1090 -[[image:image-20220610172924-4.png||height="483" width="988"]]
960 +(% style="color:#037691" %)**AT Command: AT+TDC**
1091 1091  
962 +[[image:image-20220607171554-8.png]]
1092 1092  
1093 -Or if you have below board, use below connection:
1094 1094  
965 +(((
966 +(% style="color:#037691" %)**Downlink Command: 0x01**
967 +)))
1095 1095  
1096 -[[image:image-20220610172924-5.png]]
969 +(((
970 +Format: Command Code (0x01) followed by 3 bytes time value.
971 +)))
1097 1097  
973 +(((
974 +If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
975 +)))
1098 1098  
977 +* (((
978 +Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
979 +)))
980 +* (((
981 +Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
982 +)))
983 +
984 +== 4.2  Set Interrupt Mode ==
985 +
986 +Feature, Set Interrupt mode for GPIO_EXIT.
987 +
988 +(% style="color:#037691" %)**AT Command: AT+INTMOD**
989 +
990 +[[image:image-20220610105806-2.png]]
991 +
992 +
1099 1099  (((
1100 -In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LDDS75. LDDS75 will output system info once power on as below:
994 +(% style="color:#037691" %)**Downlink Command: 0x06**
1101 1101  )))
1102 1102  
997 +(((
998 +Format: Command Code (0x06) followed by 3 bytes.
999 +)))
1103 1103  
1104 - [[image:image-20220610172924-6.png||height="601" width="860"]]
1001 +(((
1002 +This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
1003 +)))
1105 1105  
1005 +* (((
1006 +Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
1007 +)))
1008 +* (((
1009 +Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
1010 +)))
1106 1106  
1012 +== 4.3  Get Firmware Version Info ==
1107 1107  
1108 -== 3.2  Set Transmit Interval Time ==
1014 +Feature: use downlink to get firmware version.
1109 1109  
1110 -Feature: Change LoRaWAN End Node Transmit Interval.
1016 +(% style="color:#037691" %)**Downlink Command: 0x26**
1111 1111  
1112 -(% style="color:#037691" %)**AT Command: AT+TDC**
1018 +[[image:image-20220607171917-10.png]]
1113 1113  
1114 -[[image:image-20220610173409-7.png]]
1020 +* Reply to the confirmation package: 26 01
1021 +* Reply to non-confirmed packet: 26 00
1115 1115  
1023 +Device will send an uplink after got this downlink command. With below payload:
1116 1116  
1025 +Configures info payload:
1026 +
1027 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
1028 +|=(((
1029 +**Size(bytes)**
1030 +)))|=**1**|=**1**|=**1**|=**1**|=**1**|=**5**|=**1**
1031 +|**Value**|Software Type|(((
1032 +Frequency
1033 +
1034 +Band
1035 +)))|Sub-band|(((
1036 +Firmware
1037 +
1038 +Version
1039 +)))|Sensor Type|Reserve|(((
1040 +[[Message Type>>||anchor="H2.3.7A0MessageType"]]
1041 +Always 0x02
1042 +)))
1043 +
1044 +**Software Type**: Always 0x03 for LLDS12
1045 +
1046 +
1047 +**Frequency Band**:
1048 +
1049 +*0x01: EU868
1050 +
1051 +*0x02: US915
1052 +
1053 +*0x03: IN865
1054 +
1055 +*0x04: AU915
1056 +
1057 +*0x05: KZ865
1058 +
1059 +*0x06: RU864
1060 +
1061 +*0x07: AS923
1062 +
1063 +*0x08: AS923-1
1064 +
1065 +*0x09: AS923-2
1066 +
1067 +*0xa0: AS923-3
1068 +
1069 +
1070 +**Sub-Band**: value 0x00 ~~ 0x08
1071 +
1072 +
1073 +**Firmware Version**: 0x0100, Means: v1.0.0 version
1074 +
1075 +
1076 +**Sensor Type**:
1077 +
1078 +0x01: LSE01
1079 +
1080 +0x02: LDDS75
1081 +
1082 +0x03: LDDS20
1083 +
1084 +0x04: LLMS01
1085 +
1086 +0x05: LSPH01
1087 +
1088 +0x06: LSNPK01
1089 +
1090 +0x07: LLDS12
1091 +
1092 +
1093 +
1094 += 5.  Battery & How to replace =
1095 +
1096 +== 5.1  Battery Type ==
1097 +
1117 1117  (((
1118 -(% style="color:#037691" %)**Downlink Command: 0x01**
1099 +LLDS12 is equipped with a [[8500mAH ER26500 Li-SOCI2 battery>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]. The battery is un-rechargeable battery with low discharge rate targeting for 8~~10 years use. This type of battery is commonly used in IoT target for long-term running, such as water meter.
1119 1119  )))
1120 1120  
1121 1121  (((
1103 +The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
1104 +)))
1105 +
1106 +[[image:1654593587246-335.png]]
1107 +
1108 +
1109 +Minimum Working Voltage for the LLDS12:
1110 +
1111 +LLDS12:  2.45v ~~ 3.6v
1112 +
1113 +
1114 +
1115 +== 5.2  Replace Battery ==
1116 +
1122 1122  (((
1123 -Format: Command Code (0x01) followed by 3 bytes time value.
1118 +Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
1119 +)))
1124 1124  
1125 1125  (((
1126 -If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
1122 +And make sure the positive and negative pins match.
1127 1127  )))
1128 1128  
1129 -* Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
1130 -* Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
1125 +
1126 +
1127 +== 5.3  Power Consumption Analyze ==
1128 +
1129 +(((
1130 +Dragino Battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
1131 1131  )))
1132 +
1133 +(((
1134 +Instruction to use as below:
1132 1132  )))
1133 1133  
1134 1134  
1138 +**Step 1**: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
1135 1135  
1140 +[[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
1136 1136  
1137 1137  
1138 -== 3.3  Set Interrupt Mode ==
1143 +**Step 2**: Open it and choose
1139 1139  
1140 -Feature, Set Interrupt mode for GPIO_EXIT.
1145 +* Product Model
1146 +* Uplink Interval
1147 +* Working Mode
1141 1141  
1142 -(% style="color:#037691" %)**Downlink Command: AT+INTMOD**
1149 +And the Life expectation in difference case will be shown on the right.
1143 1143  
1144 -[[image:image-20220610174917-9.png]]
1151 +[[image:1654593605679-189.png]]
1145 1145  
1146 1146  
1147 -(% style="color:#037691" %)**Downlink Command: 0x06**
1154 +The battery related documents as below:
1148 1148  
1149 -Format: Command Code (0x06) followed by 3 bytes.
1156 +* (((
1157 +[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
1158 +)))
1159 +* (((
1160 +[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
1161 +)))
1162 +* (((
1163 +[[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC_1520_datasheet.jpg]], [[Tech Spec>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC1520%20Technical%20Specification20171123.pdf]]
1164 +)))
1150 1150  
1166 +[[image:image-20220607172042-11.png]]
1167 +
1168 +
1169 +
1170 +=== 5.3.1  ​Battery Note ===
1171 +
1151 1151  (((
1152 -This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
1173 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
1153 1153  )))
1154 1154  
1155 -* Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
1156 -* Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
1157 1157  
1158 -= 4.  FAQ =
1159 1159  
1160 -== 4.1  What is the frequency plan for LDDS75? ==
1178 +=== ​5.3.2  Replace the battery ===
1161 1161  
1162 -LDDS75 use the same frequency as other Dragino products. User can see the detail from this link:  [[Introduction>>doc:Main.End Device Frequency Band.WebHome||anchor="H1.Introduction"]]
1180 +(((
1181 +You can change the battery in the LLDS12.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won’t be voltage drop between battery and main board.
1182 +)))
1163 1163  
1184 +(((
1185 +The default battery pack of LLDS12 includes a ER26500 plus super capacitor. If user can’t find this pack locally, they can find ER26500 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)
1186 +)))
1164 1164  
1165 1165  
1166 -== 4.2  How to change the LoRa Frequency Bands/Region ==
1167 1167  
1168 -You can follow the instructions for [[how to upgrade image>>||anchor="H2.8A0200BFirmwareChangeLog"]].
1169 -When downloading the images, choose the required image file for download. ​
1190 += 6.  Use AT Command =
1170 1170  
1192 +== 6.1  Access AT Commands ==
1171 1171  
1194 +LLDS12 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LLDS12 for using AT command, as below.
1172 1172  
1173 -== 4.3  Can I use LDDS75 in condensation environment? ==
1196 +[[image:1654593668970-604.png]]
1174 1174  
1175 -LDDS75 is not suitable to be used in condensation environment. Condensation on the LDDS75 probe will affect the reading and always got 0.
1198 +**Connection:**
1176 1176  
1200 +(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
1177 1177  
1202 +(% style="background-color:yellow" %)** USB TTL TXD  <~-~-~-~-> UART_RXD**
1178 1178  
1179 -= 5.  Trouble Shooting =
1204 +(% style="background-color:yellow" %)** USB TTL RXD  <~-~-~-~-> UART_TXD**
1180 1180  
1181 -== 5.1  Why I can’t join TTN V3 in US915 / AU915 bands? ==
1182 1182  
1183 -It is due to channel mapping. Please see below link:  [[Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1207 +(((
1208 +(((
1209 +In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LLDS12.
1210 +)))
1184 1184  
1212 +(((
1213 +LLDS12 will output system info once power on as below:
1214 +)))
1215 +)))
1185 1185  
1186 -== 5.2  AT Command input doesn't work ==
1187 1187  
1218 + [[image:1654593712276-618.png]]
1219 +
1220 +Valid AT Command please check [[Configure Device>>||anchor="H4.A0ConfigureLLDS12viaATCommandorLoRaWANDownlink"]].
1221 +
1222 +
1223 += 7.  FAQ =
1224 +
1225 +== 7.1  How to change the LoRa Frequency Bands/Region ==
1226 +
1227 +You can follow the instructions for [[how to upgrade image>>||anchor="H2.8A0200BFirmwareChangeLog"]].
1228 +When downloading the images, choose the required image file for download. ​
1229 +
1230 +
1231 += 8.  Trouble Shooting =
1232 +
1233 +== 8.1  AT Commands input doesn’t work ==
1234 +
1235 +
1236 +(((
1188 1188  In the case if user can see the console output but can’t type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn’t send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
1238 +)))
1189 1189  
1240 +
1241 +== 8.2  Significant error between the output distant value of LiDAR and actual distance ==
1242 +
1243 +
1190 1190  (((
1245 +(% 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.)
1246 +)))
1247 +
1248 +(((
1249 +Troubleshooting: Please avoid use of this product under such circumstance in practice.
1250 +)))
1251 +
1252 +(((
1191 1191  
1192 1192  )))
1193 1193  
1256 +(((
1257 +(% style="color:blue" %)**Cause ②**(%%)**: **The IR-pass filters are blocked.
1258 +)))
1194 1194  
1195 -= 6.  Order Info =
1260 +(((
1261 +Troubleshooting: please use dry dust-free cloth to gently remove the foreign matter.
1262 +)))
1196 1196  
1197 1197  
1198 -Part Number **:** (% style="color:blue" %)**LDDS75-XX-YY**
1199 1199  
1266 += 9.  Order Info =
1200 1200  
1201 -(% style="color:blue" %)**XX**(%%)**: **The default frequency band
1202 1202  
1203 -* (% style="color:red" %)**AS923 **(%%)**:** LoRaWAN AS923 band
1204 -* (% style="color:red" %)**AU915 **(%%)**:** LoRaWAN AU915 band
1205 -* (% style="color:red" %)**EU433 **(%%)**:** LoRaWAN EU433 band
1206 -* (% style="color:red" %)**EU868 **(%%)**:** LoRaWAN EU868 band
1207 -* (% style="color:red" %)**KR920 **(%%)**:** LoRaWAN KR920 band
1208 -* (% style="color:red" %)**US915 **(%%)**:** LoRaWAN US915 band
1209 -* (% style="color:red" %)**IN865 **(%%)**:**  LoRaWAN IN865 band
1210 -* (% style="color:red" %)**CN470 **(%%)**:** LoRaWAN CN470 band
1269 +Part Number: (% style="color:blue" %)**LLDS12-XX**
1211 1211  
1212 -(% style="color:blue" %)**YY**(%%): Battery Option
1213 1213  
1214 -* (% style="color:red" %)**4 **(%%)**: **4000mAh battery
1215 -* (% style="color:red" %)**8 **(%%)**:** 8500mAh battery
1272 +(% style="color:blue" %)**XX**(%%): The default frequency band
1216 1216  
1217 -= 7. ​ Packing Info =
1274 +* (% style="color:red" %)**AS923**(%%):  LoRaWAN AS923 band
1275 +* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
1276 +* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
1277 +* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
1278 +* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
1279 +* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
1280 +* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1281 +* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1218 1218  
1219 1219  
1284 += 10. ​ Packing Info =
1285 +
1286 +
1220 1220  **Package Includes**:
1221 1221  
1222 -* LDDS75 LoRaWAN Distance Detection Sensor x 1
1289 +* LLDS12 LoRaWAN LiDAR Distance Sensor x 1
1223 1223  
1224 1224  **Dimension and weight**:
1225 1225  
... ... @@ -1228,7 +1228,8 @@
1228 1228  * Package Size / pcs : cm
1229 1229  * Weight / pcs : g
1230 1230  
1231 -= 8.  ​Support =
1232 1232  
1299 += 11.  ​Support =
1300 +
1233 1233  * 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.
1234 1234  * 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]].
1654849068701-275.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -88.3 KB
Content
1654850511545-399.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -88.3 KB
Content
1654850829385-439.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -59.2 KB
Content
1654851029373-510.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -92.0 KB
Content
1654852175653-550.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -106.2 KB
Content
1654852253176-749.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -106.6 KB
Content
1655254599445-662.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -117.0 KB
Content
1655255122126-327.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -101.7 KB
Content
1655256160324-178.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -177.0 KB
Content
image-20220610161353-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -32.2 KB
Content
image-20220610161353-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -42.7 KB
Content
image-20220610161353-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.3 KB
Content
image-20220610161353-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.1 KB
Content
image-20220610161538-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.2 KB
Content
image-20220610161538-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -28.7 KB
Content
image-20220610161724-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -180.0 KB
Content
image-20220610165129-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -50.5 KB
Content
image-20220610172003-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -5.9 KB
Content
image-20220610172003-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -18.6 KB
Content
image-20220610172400-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -370.3 KB
Content
image-20220610172924-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -1.5 MB
Content
image-20220610172924-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -901.4 KB
Content
image-20220610172924-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -68.6 KB
Content
image-20220610173409-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.8 KB
Content
image-20220610174836-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -34.3 KB
Content
image-20220610174917-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -34.3 KB
Content
image-20220615090910-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.3 KB
Content
image-20220615090910-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -5.7 KB
Content
image-20220615091045-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -209.8 KB
Content
image-20220615091045-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.9 KB
Content
image-20220615091045-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.5 KB
Content
image-20220615091045-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -196.0 KB
Content
image-20220615091045-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -371.1 KB
Content
image-20220615091045-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -206.3 KB
Content
image-20220615091045-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -115.0 KB
Content
image-20220615091929-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -37.7 KB
Content
image-20220615092010-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -37.3 KB
Content
image-20220615092044-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -63.5 KB
Content
image-20220615092327-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -66.3 KB
Content