Skip to Content
Last modified by Xiaoling on 2025/04/27 13:54
From version 150.44
edited by Xiaoling
on 2022/06/11 09:16
Change comment: There is no comment for this version
To version 111.27
edited by Xiaoling
on 2022/06/10 14:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -LDDS75 - LoRaWAN Distance Detection Sensor User Manual
1 +LLDS12-LoRaWAN LiDAR ToF Distance Sensor User Manual
Content
... ... @@ -1,6 +1,7 @@
1 1  (% style="text-align:center" %)
2 -[[image:1654846127817-788.png]]
2 +[[image:image-20220610095606-1.png]]
3 3  
4 +
4 4  **Contents:**
5 5  
6 6  {{toc/}}
... ... @@ -11,117 +11,81 @@
11 11  
12 12  
13 13  
14 -
15 15  = 1.  Introduction =
16 16  
17 -== 1.1 ​ What is LoRaWAN Distance Detection Sensor ==
17 +== 1.1 ​ What is LoRaWAN LiDAR ToF Distance Sensor ==
18 18  
19 19  (((
20 20  
21 21  
22 22  (((
23 -(((
24 -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.
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.
25 25  )))
26 26  
27 27  (((
28 -
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.
29 29  )))
30 30  
31 31  (((
32 -It detects the distance** (% style="color:#4472c4" %) between the measured object and the sensor(%%)**, and uploads the value via wireless to LoRaWAN IoT Server.
31 +It detects the distance between the measured object and the sensor, and uploads the value via wireless to LoRaWAN IoT Server.
33 33  )))
34 34  
35 35  (((
36 -
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.
37 37  )))
38 38  
39 39  (((
40 -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.
39 +LLDS12 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years.
41 41  )))
42 42  
43 43  (((
44 -
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.
45 45  )))
46 -
47 -(((
48 -LDDS75 is powered by (% style="color:#4472c4" %)** 4000mA or 8500mAh Li-SOCI2 battery**(%%); It is designed for long term use up to 10 years*.
49 49  )))
50 50  
51 -(((
52 -
53 -)))
54 54  
55 -(((
56 -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.
57 -)))
48 +[[image:1654826306458-414.png]]
58 58  
59 -(((
60 -
61 -)))
62 62  
63 -(((
64 -(% style="color:#4472c4" %) * (%%)Actually lifetime depends on network coverage and uplink interval and other factors.
65 -)))
66 -)))
67 -)))
68 68  
69 -
70 -[[image:1654847051249-359.png]]
71 -
72 -
73 -
74 74  == ​1.2  Features ==
75 75  
76 76  * LoRaWAN 1.0.3 Class A
77 -* Ultra low power consumption
78 -* Distance Detection by Ultrasonic technology
79 -* Flat object range 280mm - 7500mm
80 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
81 -* Cable Length : 25cm
55 +* Ultra-low power consumption
56 +* Laser technology for distance detection
57 +* Operating Range - 0.1m~~12m①
58 +* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
59 +* Monitor Battery Level
82 82  * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
83 83  * AT Commands to change parameters
84 84  * Uplink on periodically
85 85  * Downlink to change configure
86 -* IP66 Waterproof Enclosure
87 -* 4000mAh or 8500mAh Battery for long term use
64 +* 8500mAh Battery for long term use
88 88  
66 +== 1.3  Probe Specification ==
89 89  
90 -== 1.3  Specification ==
68 +* Storage temperature ：-20℃~~75℃
69 +* Operating temperature - -20℃~~60℃
70 +* Operating Range - 0.1m~~12m①
71 +* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
72 +* Distance resolution - 5mm
73 +* Ambient light immunity - 70klux
74 +* Enclosure rating - IP65
75 +* Light source - LED
76 +* Central wavelength - 850nm
77 +* FOV - 3.6°
78 +* Material of enclosure - ABS+PC
79 +* Wire length - 25cm
91 91  
92 -=== 1.3.1  Rated environmental conditions ===
81 +== 1.4  Probe Dimension ==
93 93  
94 -[[image:image-20220610154839-1.png]]
95 95  
96 -(((
97 -**Remarks: (1) a. When the ambient temperature is 0-39 ℃, the maximum humidity is 90% (non-condensing);  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)**
98 -)))
84 +[[image:1654827224480-952.png]]
99 99  
100 100  
101 -
102 -=== 1.3.2  Effective measurement range Reference beam pattern ===
103 -
104 -**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**
105 -
106 -
107 -
108 -[[image:1654852253176-749.png]]
109 -
110 -
111 -
112 -(((
113 -**(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.**
114 -)))
115 -
116 -
117 -[[image:1654852175653-550.png]](% style="display:none" %) ** **
118 -
119 -
120 -
121 121  == 1.5 ​ Applications ==
122 122  
123 123  * Horizontal distance measurement
124 -* Liquid level measurement
125 125  * Parking management system
126 126  * Object proximity and presence detection
127 127  * Intelligent trash can management system
... ... @@ -128,31 +128,26 @@
128 128  * Robot obstacle avoidance
129 129  * Automatic control
130 130  * Sewer
131 -* Bottom water level monitoring
132 132  
133 -
134 -
135 135  == 1.6  Pin mapping and power on ==
136 136  
137 137  
138 -[[image:1654847583902-256.png]]
100 +[[image:1654827332142-133.png]]
139 139  
140 140  
103 += 2.  Configure LLDS12 to connect to LoRaWAN network =
141 141  
142 -= 2.  Configure LDDS75 to connect to LoRaWAN network =
143 -
144 144  == 2.1  How it works ==
145 145  
146 146  (((
147 -The LDDS75 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LDDS75. If there is coverage of the LoRaWAN network, it will automatically join the network via OTAA and start to send the sensor value
108 +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.
148 148  )))
149 149  
150 150  (((
151 -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="H3.A0ConfigureLDDS75viaATCommandorLoRaWANDownlink"]]to set the keys in the LDDS75.
112 +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.
152 152  )))
153 153  
154 154  
155 -
156 156  == 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
157 157  
158 158  (((
... ... @@ -160,7 +160,7 @@
160 160  )))
161 161  
162 162  (((
163 -[[image:1654848616367-242.png]]
123 +[[image:1654827857527-556.png]]
164 164  )))
165 165  
166 166  (((
... ... @@ -168,63 +168,57 @@
168 168  )))
169 169  
170 170  (((
171 -(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS75.
131 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSPH01.
172 172  )))
173 173  
174 174  (((
175 -Each LDDS75 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
135 +Each LSPH01 is shipped with a sticker with the default device EUI as below:
176 176  )))
177 177  
178 178  [[image:image-20220607170145-1.jpeg]]
179 179  
180 180  
181 -(((
182 -For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
183 -)))
184 184  
185 -(((
186 -Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
187 -)))
142 +You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
188 188  
189 -(((
190 -**Add APP EUI in the application**
191 -)))
192 192  
193 -[[image:image-20220610161353-4.png]]
145 +**Register the device**
194 194  
195 -[[image:image-20220610161353-5.png]]
196 196  
197 -[[image:image-20220610161353-6.png]]
148 +[[image:1654592600093-601.png]]
198 198  
199 199  
200 -[[image:image-20220610161353-7.png]]
201 201  
152 +**Add APP EUI and DEV EUI**
202 202  
203 -You can also choose to create the device manually.
154 +[[image:1654592619856-881.png]]
204 204  
205 - [[image:image-20220610161538-8.png]]
206 206  
207 207  
158 +**Add APP EUI in the application**
208 208  
209 -**Add APP KEY and DEV EUI**
160 +[[image:1654592632656-512.png]]
210 210  
211 -[[image:image-20220610161538-9.png]]
212 212  
213 213  
164 +**Add APP KEY**
214 214  
215 -(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
166 +[[image:1654592653453-934.png]]
216 216  
217 217  
169 +(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
170 +
171 +
218 218  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
219 219  
220 -[[image:image-20220610161724-10.png]]
174 +[[image:image-20220607170442-2.png]]
221 221  
222 222  
223 223  (((
224 -(% 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.
178 +(% 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.
225 225  )))
226 226  
227 -[[image:1654849068701-275.png]]
181 +[[image:1654833501679-968.png]]
228 228  
229 229  
230 230  
... ... @@ -231,10 +231,11 @@
231 231  == 2.3  ​Uplink Payload ==
232 232  
233 233  (((
234 -LDDS75 will uplink payload via LoRaWAN with below payload format: 
188 +LLDS12 will uplink payload via LoRaWAN with below payload format: 
189 +)))
235 235  
236 -Uplink payload includes in total 4 bytes.
237 -Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
191 +(((
192 +Uplink payload includes in total 11 bytes.
238 238  )))
239 239  
240 240  (((
... ... @@ -244,23 +244,23 @@
244 244  (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
245 245  |=(% style="width: 62.5px;" %)(((
246 246  **Size (bytes)**
247 -)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
248 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
249 -[[Distance>>||anchor="H2.3.2A0Distance"]]
202 +)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
203 +|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
204 +[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
205 +)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
206 +[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
207 +)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
208 +[[Message Type>>||anchor="H2.3.7A0MessageType"]]
209 +)))
250 250  
251 -(unit: mm)
252 -)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.3A0InterruptPin"]]|(((
253 -[[Temperature (Optional )>>||anchor="H2.3.4A0DS18B20Temperaturesensor"]]
254 -)))|[[Sensor Flag>>||anchor="H2.3.5A0SensorFlag"]]
211 +[[image:1654833689380-972.png]]
255 255  
256 -[[image:1654850511545-399.png]]
257 257  
258 258  
259 -
260 260  === 2.3.1  Battery Info ===
261 261  
262 262  
263 -Check the battery voltage for LDDS75.
218 +Check the battery voltage for LLDS12.
264 264  
265 265  Ex1: 0x0B45 = 2885mV
266 266  
... ... @@ -268,66 +268,103 @@
268 268  
269 269  
270 270  
271 -=== 2.3.2  Distance ===
226 +=== 2.3.2  DS18B20 Temperature sensor ===
272 272  
273 -Get the distance. Flat object range 280mm - 7500mm.
228 +This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
274 274  
275 -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.**
276 276  
231 +**Example**:
277 277  
278 -* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
279 -* 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.
233 +If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
280 280  
281 -=== 2.3.3  Interrupt Pin ===
235 +If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
282 282  
283 -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.
284 284  
285 -**Example:**
286 286  
287 -0x00: Normal uplink packet.
239 +=== 2.3.3  Distance ===
288 288  
289 -0x01: Interrupt Uplink Packet.
241 +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.
290 290  
291 291  
244 +**Example**:
292 292  
293 -=== 2.3.4  DS18B20 Temperature sensor ===
246 +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.
294 294  
295 -This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
296 296  
249 +
250 +=== 2.3.4  Distance signal strength ===
251 +
252 +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.
253 +
254 +
297 297  **Example**:
298 298  
299 -If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
257 +If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
300 300  
301 -If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
259 +Customers can judge whether they need to adjust the environment based on the signal strength.
302 302  
303 -(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
304 304  
305 305  
263 +=== 2.3.5  Interrupt Pin ===
306 306  
307 -=== 2.3.5  Sensor Flag ===
265 +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.
308 308  
309 -0x01: Detect Ultrasonic Sensor
267 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
310 310  
311 -0x00: No Ultrasonic Sensor
269 +**Example:**
312 312  
271 +0x00: Normal uplink packet.
313 313  
273 +0x01: Interrupt Uplink Packet.
314 314  
315 -=== 2.3.6  Decode payload in The Things Network ===
316 316  
276 +
277 +=== 2.3.6  LiDAR temp ===
278 +
279 +Characterize the internal temperature value of the sensor.
280 +
281 +**Example: **
282 +If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
283 +If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
284 +
285 +
286 +
287 +=== 2.3.7  Message Type ===
288 +
289 +(((
290 +For a normal uplink payload, the message type is always 0x01.
291 +)))
292 +
293 +(((
294 +Valid Message Type:
295 +)))
296 +
297 +
298 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
299 +|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
300 +|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
301 +|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
302 +
303 +=== 2.3.8  Decode payload in The Things Network ===
304 +
317 317  While using TTN network, you can add the payload format to decode the payload.
318 318  
319 319  
320 -[[image:1654850829385-439.png]]
308 +[[image:1654592762713-715.png]]
321 321  
322 -The payload decoder function for TTN V3 is here:
310 +(((
311 +The payload decoder function for TTN is here:
312 +)))
323 323  
324 -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/]]
314 +(((
315 +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/]]
316 +)))
325 325  
326 326  
327 327  
328 328  == 2.4  Uplink Interval ==
329 329  
330 -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"]]
322 +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"]]
331 331  
332 332  
333 333  
... ... @@ -358,25 +358,47 @@
358 358  
359 359  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
360 360  
361 -(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
353 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
362 362  
363 -[[image:1654851029373-510.png]]
355 +[[image:1654832691989-514.png]]
364 364  
365 365  
366 -After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
358 +[[image:1654592833877-762.png]]
367 367  
368 -[[image:image-20220610165129-11.png||height="595" width="1088"]]
369 369  
361 +[[image:1654832740634-933.png]]
370 370  
371 371  
372 -== 2.6  Frequency Plans ==
373 373  
374 374  (((
375 -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.
366 +(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
376 376  )))
377 377  
369 +(((
370 +
371 +)))
378 378  
373 +[[image:1654833065139-942.png]]
379 379  
375 +
376 +
377 +[[image:1654833092678-390.png]]
378 +
379 +
380 +
381 +After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
382 +
383 +[[image:1654833163048-332.png]]
384 +
385 +
386 +
387 +== 2.6  Frequency Plans ==
388 +
389 +(((
390 +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.
391 +)))
392 +
393 +
380 380  === 2.6.1  EU863-870 (EU868) ===
381 381  
382 382  (((
... ... @@ -440,51 +440,21 @@
440 440  === 2.6.2  US902-928(US915) ===
441 441  
442 442  (((
443 -Used in USA, Canada and South America. Default use CHE=2
457 +Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
458 +)))
444 444  
445 -(% style="color:blue" %)**Uplink:**
460 +(((
461 +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.
462 +)))
446 446  
447 -903.9 - SF7BW125 to SF10BW125
464 +(((
465 +After Join success, the end node will switch to the correct sub band by:
466 +)))
448 448  
449 -904.1 - SF7BW125 to SF10BW125
468 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
469 +* 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)
450 450  
451 -904.3 - SF7BW125 to SF10BW125
452 452  
453 -904.5 - SF7BW125 to SF10BW125
454 -
455 -904.7 - SF7BW125 to SF10BW125
456 -
457 -904.9 - SF7BW125 to SF10BW125
458 -
459 -905.1 - SF7BW125 to SF10BW125
460 -
461 -905.3 - SF7BW125 to SF10BW125
462 -
463 -
464 -(% style="color:blue" %)**Downlink:**
465 -
466 -923.3 - SF7BW500 to SF12BW500
467 -
468 -923.9 - SF7BW500 to SF12BW500
469 -
470 -924.5 - SF7BW500 to SF12BW500
471 -
472 -925.1 - SF7BW500 to SF12BW500
473 -
474 -925.7 - SF7BW500 to SF12BW500
475 -
476 -926.3 - SF7BW500 to SF12BW500
477 -
478 -926.9 - SF7BW500 to SF12BW500
479 -
480 -927.5 - SF7BW500 to SF12BW500
481 -
482 -923.3 - SF12BW500(RX2 downlink only)
483 -
484 -
485 -
486 -)))
487 -
488 488  === 2.6.3  CN470-510 (CN470) ===
489 489  
490 490  (((
... ... @@ -573,54 +573,29 @@
573 573  
574 574  
575 575  
560 +
576 576  === 2.6.4  AU915-928(AU915) ===
577 577  
578 578  (((
579 -Default use CHE=2
564 +Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
565 +)))
580 580  
581 -(% 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 +)))
582 582  
583 -916.8 - SF7BW125 to SF12BW125
571 +(((
572 +
573 +)))
584 584  
585 -917.0 - SF7BW125 to SF12BW125
575 +(((
576 +After Join success, the end node will switch to the correct sub band by:
577 +)))
586 586  
587 -917.2 - SF7BW125 to SF12BW125
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)
588 588  
589 -917.4 - SF7BW125 to SF12BW125
590 590  
591 -917.6 - SF7BW125 to SF12BW125
592 -
593 -917.8 - SF7BW125 to SF12BW125
594 -
595 -918.0 - SF7BW125 to SF12BW125
596 -
597 -918.2 - SF7BW125 to SF12BW125
598 -
599 -
600 -(% style="color:blue" %)**Downlink:**
601 -
602 -923.3 - SF7BW500 to SF12BW500
603 -
604 -923.9 - SF7BW500 to SF12BW500
605 -
606 -924.5 - SF7BW500 to SF12BW500
607 -
608 -925.1 - SF7BW500 to SF12BW500
609 -
610 -925.7 - SF7BW500 to SF12BW500
611 -
612 -926.3 - SF7BW500 to SF12BW500
613 -
614 -926.9 - SF7BW500 to SF12BW500
615 -
616 -927.5 - SF7BW500 to SF12BW500
617 -
618 -923.3 - SF12BW500(RX2 downlink only)
619 -
620 -
621 -
622 -)))
623 -
624 624  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
625 625  
626 626  (((
... ... @@ -729,6 +729,7 @@
729 729  
730 730  
731 731  
691 +
732 732  === 2.6.6  KR920-923 (KR920) ===
733 733  
734 734  (((
... ... @@ -801,6 +801,7 @@
801 801  
802 802  
803 803  
764 +
804 804  === 2.6.7  IN865-867 (IN865) ===
805 805  
806 806  (((
... ... @@ -837,20 +837,18 @@
837 837  
838 838  
839 839  
801 +
840 840  == 2.7  LED Indicator ==
841 841  
842 -The LDDS75 has an internal LED which is to show the status of different state.
804 +The LLDS12 has an internal LED which is to show the status of different state.
843 843  
844 -
845 -* Blink once when device power on.
846 -* The device detects the sensor and flashes 5 times.
847 -* Solid ON for 5 seconds once device successful Join the network.
806 +* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
848 848  * Blink once when device transmit a packet.
849 849  
850 850  == 2.8  ​Firmware Change Log ==
851 851  
852 852  
853 -**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/]]
812 +**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/]]
854 854  
855 855  
856 856  **Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
... ... @@ -857,43 +857,91 @@
857 857  
858 858  
859 859  
860 -== 2.9  Mechanical ==
819 += 3.  LiDAR ToF Measurement =
861 861  
821 +== 3.1 Principle of Distance Measurement ==
862 862  
863 -[[image:image-20220610172003-1.png]]
823 +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.
864 864  
825 +[[image:1654831757579-263.png]]
865 865  
866 -[[image:image-20220610172003-2.png]]
867 867  
868 868  
829 +== 3.2 Distance Measurement Characteristics ==
869 869  
870 -== 2.10  Battery Analysis ==
831 +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:
871 871  
872 -=== 2.10.1  Battery Type ===
833 +[[image:1654831774373-275.png]]
873 873  
874 -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.
875 875  
836 +①Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
876 876  
877 -The battery related documents as below:
838 +②Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
878 878  
879 -* (((
880 -[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
840 +③Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
841 +
842 +
843 +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:
844 +
845 +
846 +[[image:1654831797521-720.png]]
847 +
848 +
849 +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.
850 +
851 +[[image:1654831810009-716.png]]
852 +
853 +
854 +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.
855 +
856 +
857 +
858 +== 3.3 Notice of usage: ==
859 +
860 +Possible invalid /wrong reading for LiDAR ToF tech:
861 +
862 +* Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
863 +* While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might wrong.
864 +* The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
865 +* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
866 +
867 +
868 += 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
869 +
870 +(((
871 +Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
881 881  )))
873 +
882 882  * (((
883 -[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
875 +AT Command Connection: See [[FAQ>>||anchor="H7.A0FAQ"]].
884 884  )))
885 885  * (((
886 -[[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]]
878 +LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
887 887  )))
888 888  
889 - [[image:image-20220610172400-3.png]]
881 +(((
882 +
890 890  
884 +There are two kinds of commands to configure LLDS12, they are:
885 +)))
891 891  
887 +* (((
888 +(% style="color:#4f81bd" %)** General Commands**.
889 +)))
892 892  
893 -=== 2.10.2  Replace the battery ===
891 +(((
892 +These commands are to configure:
893 +)))
894 894  
895 +* (((
896 +General system settings like: uplink interval.
897 +)))
898 +* (((
899 +LoRaWAN protocol & radio related command.
900 +)))
901 +
895 895  (((
896 -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.
903 +They are same for all Dragino Device which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
897 897  )))
898 898  
899 899  (((
... ... @@ -900,220 +900,351 @@
900 900  
901 901  )))
902 902  
910 +* (((
911 +(% style="color:#4f81bd" %)** Commands special design for LLDS12**
912 +)))
913 +
903 903  (((
904 -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)
915 +These commands only valid for LLDS12, as below:
905 905  )))
906 906  
907 907  
908 908  
909 -= 3.  Configure LDDS75 via AT Command or LoRaWAN Downlink =
920 +== 4.1  Set Transmit Interval Time ==
910 910  
922 +Feature: Change LoRaWAN End Node Transmit Interval.
923 +
924 +(% style="color:#037691" %)**AT Command: AT+TDC**
925 +
926 +[[image:image-20220607171554-8.png]]
927 +
928 +
929 +
911 911  (((
931 +(% style="color:#037691" %)**Downlink Command: 0x01**
932 +)))
933 +
912 912  (((
913 -Use can configure LDDS75 via AT Command or LoRaWAN Downlink.
935 +Format: Command Code (0x01) followed by 3 bytes time value.
914 914  )))
915 -)))
916 916  
917 -* (((
918 918  (((
919 -AT Command Connection: See [[FAQ>>||anchor="H4.A0FAQ"]].
939 +If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
920 920  )))
921 -)))
941 +
922 922  * (((
923 -(((
924 -LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
943 +Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
925 925  )))
926 -)))
945 +* (((
946 +Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
927 927  
928 -(((
929 -(((
948 +
930 930  
931 931  )))
932 932  
952 +== 4.2  Set Interrupt Mode ==
953 +
954 +Feature, Set Interrupt mode for GPIO_EXIT.
955 +
956 +(% style="color:#037691" %)**AT Command: AT+INTMOD**
957 +
958 +[[image:image-20220610105806-2.png]]
959 +
960 +
933 933  (((
934 -There are two kinds of commands to configure LDDS75, they are:
962 +(% style="color:#037691" %)**Downlink Command: 0x06**
935 935  )))
936 -)))
937 937  
938 -* (((
939 939  (((
940 -(% style="color:#4f81bd" %)** General Commands**.
966 +Format: Command Code (0x06) followed by 3 bytes.
941 941  )))
942 -)))
943 943  
944 944  (((
945 -(((
946 -These commands are to configure:
970 +This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
947 947  )))
948 -)))
949 949  
950 950  * (((
951 -(((
952 -General system settings like: uplink interval.
974 +Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
953 953  )))
954 -)))
955 955  * (((
956 -(((
957 -LoRaWAN protocol & radio related command.
977 +Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
958 958  )))
979 +
980 +
981 +
982 +== 4.3  Get Firmware Version Info ==
983 +
984 +Feature: use downlink to get firmware version.
985 +
986 +(% style="color:#037691" %)**Downlink Command: 0x26**
987 +
988 +[[image:image-20220607171917-10.png]]
989 +
990 +* Reply to the confirmation package: 26 01
991 +* Reply to non-confirmed packet: 26 00
992 +
993 +Device will send an uplink after got this downlink command. With below payload:
994 +
995 +Configures info payload:
996 +
997 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
998 +|=(((
999 +**Size(bytes)**
1000 +)))|=**1**|=**1**|=**1**|=**1**|=**1**|=**5**|=**1**
1001 +|**Value**|Software Type|(((
1002 +Frequency
1003 +
1004 +Band
1005 +)))|Sub-band|(((
1006 +Firmware
1007 +
1008 +Version
1009 +)))|Sensor Type|Reserve|(((
1010 +[[Message Type>>||anchor="H2.3.7A0MessageType"]]
1011 +Always 0x02
959 959  )))
960 960  
1014 +**Software Type**: Always 0x03 for LLDS12
1015 +
1016 +
1017 +**Frequency Band**:
1018 +
1019 +*0x01: EU868
1020 +
1021 +*0x02: US915
1022 +
1023 +*0x03: IN865
1024 +
1025 +*0x04: AU915
1026 +
1027 +*0x05: KZ865
1028 +
1029 +*0x06: RU864
1030 +
1031 +*0x07: AS923
1032 +
1033 +*0x08: AS923-1
1034 +
1035 +*0x09: AS923-2
1036 +
1037 +*0xa0: AS923-3
1038 +
1039 +
1040 +**Sub-Band**: value 0x00 ~~ 0x08
1041 +
1042 +
1043 +**Firmware Version**: 0x0100, Means: v1.0.0 version
1044 +
1045 +
1046 +**Sensor Type**:
1047 +
1048 +0x01: LSE01
1049 +
1050 +0x02: LDDS75
1051 +
1052 +0x03: LDDS20
1053 +
1054 +0x04: LLMS01
1055 +
1056 +0x05: LSPH01
1057 +
1058 +0x06: LSNPK01
1059 +
1060 +0x07: LLDS12
1061 +
1062 +
1063 +
1064 += 5.  Battery & How to replace =
1065 +
1066 +== 5.1  Battery Type ==
1067 +
961 961  (((
1069 +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.
1070 +)))
1071 +
962 962  (((
963 -They are same for all Dragino Device which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
1073 +The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
964 964  )))
1075 +
1076 +[[image:1654593587246-335.png]]
1077 +
1078 +
1079 +Minimum Working Voltage for the LLDS12:
1080 +
1081 +LLDS12:  2.45v ~~ 3.6v
1082 +
1083 +
1084 +
1085 +== 5.2  Replace Battery ==
1086 +
1087 +(((
1088 +Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
965 965  )))
966 966  
967 967  (((
968 -(((
969 -
1092 +And make sure the positive and negative pins match.
970 970  )))
971 -)))
972 972  
973 -* (((
1095 +
1096 +
1097 +== 5.3  Power Consumption Analyze ==
1098 +
974 974  (((
975 -(% style="color:#4f81bd" %)** Commands special design for LDDS75**
1100 +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.
976 976  )))
977 -)))
978 978  
979 979  (((
980 -(((
981 -These commands only valid for LDDS75, as below:
1104 +Instruction to use as below:
982 982  )))
983 -)))
984 984  
985 985  
1108 +**Step 1**: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
986 986  
987 -== 3.1  Access AT Commands ==
1110 +[[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/]]
988 988  
989 -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.
990 990  
991 -[[image:image-20220610172924-4.png||height="483" width="988"]]
1113 +**Step 2**: Open it and choose
992 992  
1115 +* Product Model
1116 +* Uplink Interval
1117 +* Working Mode
993 993  
994 -Or if you have below board, use below connection:
1119 +And the Life expectation in difference case will be shown on the right.
995 995  
1121 +[[image:1654593605679-189.png]]
996 996  
997 -[[image:image-20220610172924-5.png]]
998 998  
1124 +The battery related documents as below:
999 999  
1000 -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:
1126 +* (((
1127 +[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
1128 +)))
1129 +* (((
1130 +[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
1131 +)))
1132 +* (((
1133 +[[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]]
1134 +)))
1001 1001  
1136 +[[image:image-20220607172042-11.png]]
1002 1002  
1003 - [[image:image-20220610172924-6.png||height="601" width="860"]]
1004 1004  
1005 1005  
1140 +=== 5.3.1  ​Battery Note ===
1006 1006  
1007 -== 3.2  Set Transmit Interval Time ==
1142 +(((
1143 +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.
1144 +)))
1008 1008  
1009 -Feature: Change LoRaWAN End Node Transmit Interval.
1010 1010  
1011 -(% style="color:#037691" %)**AT Command: AT+TDC**
1012 1012  
1013 -[[image:image-20220610173409-7.png]]
1148 +=== ​5.3.2  Replace the battery ===
1014 1014  
1015 -
1016 1016  (((
1017 -(% style="color:#037691" %)**Downlink Command: 0x01**
1151 +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.
1018 1018  )))
1019 1019  
1020 1020  (((
1021 -(((
1022 -Format: Command Code (0x01) followed by 3 bytes time value.
1155 +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)
1156 +)))
1023 1023  
1024 -If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
1025 1025  
1026 -* Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
1027 -* Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
1028 -)))
1029 1029  
1160 += 6.  Use AT Command =
1030 1030  
1031 -
1032 -)))
1162 +== 6.1  Access AT Commands ==
1033 1033  
1034 -== 3.3  Set Interrupt Mode ==
1164 +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.
1035 1035  
1036 -Feature, Set Interrupt mode for GPIO_EXIT.
1166 +[[image:1654593668970-604.png]]
1037 1037  
1038 -(% style="color:#037691" %)**Downlink Command: AT+INTMOD**
1168 +**Connection:**
1039 1039  
1040 -[[image:image-20220610174917-9.png]]
1170 +(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
1041 1041  
1172 +(% style="background-color:yellow" %)** USB TTL TXD  <~-~-~-~-> UART_RXD**
1042 1042  
1043 -(% style="color:#037691" %)**Downlink Command: 0x06**
1174 +(% style="background-color:yellow" %)** USB TTL RXD  <~-~-~-~-> UART_TXD**
1044 1044  
1045 -Format: Command Code (0x06) followed by 3 bytes.
1046 1046  
1047 -This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
1177 +(((
1178 +In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LLDS12.
1048 1048  
1049 -* Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
1050 -* Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
1180 +LLDS12 will output system info once power on as below:
1181 +)))
1051 1051  
1052 -= 4.  FAQ =
1053 1053  
1054 -== 4.1  What is the frequency plan for LDDS75? ==
1184 + [[image:1654593712276-618.png]]
1055 1055  
1056 -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"]]
1186 +Valid AT Command please check [[Configure Device>>||anchor="H4.A0ConfigureLLDS12viaATCommandorLoRaWANDownlink"]].
1057 1057  
1058 1058  
1189 += 7.  FAQ =
1059 1059  
1060 -== 4.2  How to change the LoRa Frequency Bands/Region ==
1191 +== 7.1  How to change the LoRa Frequency Bands/Region ==
1061 1061  
1062 1062  You can follow the instructions for [[how to upgrade image>>||anchor="H2.8A0200BFirmwareChangeLog"]].
1063 1063  When downloading the images, choose the required image file for download. ​
1064 1064  
1065 1065  
1197 += 8.  Trouble Shooting =
1066 1066  
1067 -== 4.3  Can I use LDDS75 in condensation environment? ==
1199 +== 8.1  AT Commands input doesn’t work ==
1068 1068  
1069 -LDDS75 is not suitable to be used in condensation environment. Condensation on the LDDS75 probe will affect the reading and always got 0.
1070 1070  
1202 +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.
1071 1071  
1072 1072  
1073 -= 5.  Trouble Shooting =
1205 +== 8.2  Significant error between the output distant value of LiDAR and actual distance ==
1074 1074  
1075 -== 5.1  Why I can’t join TTN V3 in US915 / AU915 bands? ==
1076 1076  
1077 -It is due to channel mapping. Please see below link:  [[Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1208 +(((
1209 +(% 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.)
1210 +)))
1078 1078  
1212 +(((
1213 +Troubleshooting: Please avoid use of this product under such circumstance in practice.
1214 +)))
1079 1079  
1080 -== 5.2  AT Command input doesn't work ==
1216 +(((
1217 +
1218 +)))
1081 1081  
1082 -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.
1220 +(((
1221 +(% style="color:blue" %)**Cause ②**(%%)**: **The IR-pass filters are blocked.
1222 +)))
1083 1083  
1084 1084  (((
1085 -
1225 +Troubleshooting: please use dry dust-free cloth to gently remove the foreign matter.
1086 1086  )))
1087 1087  
1088 1088  
1089 -= 6.  Order Info =
1090 1090  
1230 += 9.  Order Info =
1091 1091  
1092 -Part Number **:** (% style="color:blue" %)**LDDS75-XX-YY**
1093 1093  
1233 +Part Number: (% style="color:blue" %)**LLDS12-XX**
1094 1094  
1095 -(% style="color:blue" %)**XX**(%%)**: **The default frequency band
1096 1096  
1097 -* (% style="color:red" %)**AS923 **(%%)**:** LoRaWAN AS923 band
1098 -* (% style="color:red" %)**AU915 **(%%)**:** LoRaWAN AU915 band
1099 -* (% style="color:red" %)**EU433 **(%%)**:** LoRaWAN EU433 band
1100 -* (% style="color:red" %)**EU868 **(%%)**:** LoRaWAN EU868 band
1101 -* (% style="color:red" %)**KR920 **(%%)**:** LoRaWAN KR920 band
1102 -* (% style="color:red" %)**US915 **(%%)**:** LoRaWAN US915 band
1103 -* (% style="color:red" %)**IN865 **(%%)**:**  LoRaWAN IN865 band
1104 -* (% style="color:red" %)**CN470 **(%%)**:** LoRaWAN CN470 band
1236 +(% style="color:blue" %)**XX**(%%): The default frequency band
1105 1105  
1106 -(% style="color:blue" %)**YY**(%%): Battery Option
1238 +* (% style="color:red" %)**AS923**(%%):  LoRaWAN AS923 band
1239 +* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
1240 +* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
1241 +* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
1242 +* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
1243 +* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
1244 +* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1245 +* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1107 1107  
1108 -* (% style="color:red" %)**4 **(%%)**: **4000mAh battery
1109 -* (% style="color:red" %)**8 **(%%)**:** 8500mAh battery
1110 1110  
1111 -= 7. ​ Packing Info =
1112 1112  
1249 += 10. ​ Packing Info =
1113 1113  
1251 +
1114 1114  **Package Includes**:
1115 1115  
1116 -* LDDS75 LoRaWAN Distance Detection Sensor x 1
1254 +* LLDS12 LoRaWAN LiDAR Distance Sensor x 1
1117 1117  
1118 1118  **Dimension and weight**:
1119 1119  
... ... @@ -1122,7 +1122,9 @@
1122 1122  * Package Size / pcs : cm
1123 1123  * Weight / pcs : g
1124 1124  
1125 -= 8.  ​Support =
1126 1126  
1264 +
1265 += 11.  ​Support =
1266 +
1127 1127  * 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.
1128 1128  * 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]].
1654846127817-788.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -107.3 KB
Content
1654847051249-359.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.8 KB
Content
1654847583902-256.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1654848616367-242.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.8 KB
Content
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
image-20220610154839-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.3 KB
Content
image-20220610155021-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -164.8 KB
Content
image-20220610155021-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.8 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