Last modified by Mengting Qiu on 2024/03/07 08:41
<
From version < 119.6 >
edited by Xiaoling
on 2022/06/10 15:43
To version < 147.2 >
edited by Xiaoling
on 2022/06/10 17:34
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -33,12 +33,12 @@
33 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.
34 34  
35 35  
36 -(% style="color:#4472c4" %) ***** (%%)Actually lifetime depends on network coverage and uplink interval and other factors
36 +(% style="color:#4472c4" %) * (%%)Actually lifetime depends on network coverage and uplink interval and other factors
37 37  )))
38 38  )))
39 39  
40 40  
41 -[[image:1654826306458-414.png]]
41 +[[image:1654847051249-359.png]]
42 42  
43 43  
44 44  
... ... @@ -45,41 +45,51 @@
45 45  == ​1.2  Features ==
46 46  
47 47  * LoRaWAN 1.0.3 Class A
48 -* Ultra-low power consumption
49 -* Laser technology for distance detection
50 -* Operating Range - 0.1m~~12m①
51 -* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
52 -* Monitor Battery Level
48 +* Ultra low power consumption
49 +* Distance Detection by Ultrasonic technology
50 +* Flat object range 280mm - 7500mm
51 +* Accuracy: ±(1cm+S*0.3%) (S: Distance)
52 +* Cable Length : 25cm
53 53  * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
54 54  * AT Commands to change parameters
55 55  * Uplink on periodically
56 56  * Downlink to change configure
57 -* 8500mAh Battery for long term use
57 +* IP66 Waterproof Enclosure
58 +* 4000mAh or 8500mAh Battery for long term use
58 58  
59 -== 1.3  Probe Specification ==
60 60  
61 -* Storage temperature ：-20℃~~75℃
62 -* Operating temperature - -20℃~~60℃
63 -* Operating Range - 0.1m~~12m①
64 -* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
65 -* Distance resolution - 5mm
66 -* Ambient light immunity - 70klux
67 -* Enclosure rating - IP65
68 -* Light source - LED
69 -* Central wavelength - 850nm
70 -* FOV - 3.6°
71 -* Material of enclosure - ABS+PC
72 -* Wire length - 25cm
61 +== 1.3  Specification ==
73 73  
74 -== 1.4  Probe Dimension ==
63 +=== 1.3.1  Rated environmental conditions ===
75 75  
65 +[[image:image-20220610154839-1.png]]
76 76  
77 -[[image:1654827224480-952.png]]
67 +**Remarks: (1) a. When the ambient temperature is 0-39 ℃, the maximum humidity is 90% (non-condensing);**
78 78  
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)**
79 79  
71 +
72 +
73 +=== 1.3.2  Effective measurement range Reference beam pattern ===
74 +
75 +**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**
76 +
77 +
78 +
79 +[[image:1654852253176-749.png]]
80 +
81 +
82 +**(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.**
83 +
84 +
85 +[[image:1654852175653-550.png]](% style="display:none" %) ** **
86 +
87 +
88 +
80 80  == 1.5 ​ Applications ==
81 81  
82 82  * Horizontal distance measurement
92 +* Liquid level measurement
83 83  * Parking management system
84 84  * Object proximity and presence detection
85 85  * Intelligent trash can management system
... ... @@ -86,26 +86,30 @@
86 86  * Robot obstacle avoidance
87 87  * Automatic control
88 88  * Sewer
99 +* Bottom water level monitoring
89 89  
101 +
90 90  == 1.6  Pin mapping and power on ==
91 91  
92 92  
93 -[[image:1654827332142-133.png]]
105 +[[image:1654847583902-256.png]]
94 94  
95 95  
96 -= 2.  Configure LLDS12 to connect to LoRaWAN network =
97 97  
109 += 2.  Configure LDDS75 to connect to LoRaWAN network =
110 +
98 98  == 2.1  How it works ==
99 99  
100 100  (((
101 -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.
114 +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
102 102  )))
103 103  
104 104  (((
105 -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.
118 +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.
106 106  )))
107 107  
108 108  
122 +
109 109  == 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
110 110  
111 111  (((
... ... @@ -113,7 +113,7 @@
113 113  )))
114 114  
115 115  (((
116 -[[image:1654827857527-556.png]]
130 +[[image:1654848616367-242.png]]
117 117  )))
118 118  
119 119  (((
... ... @@ -121,57 +121,57 @@
121 121  )))
122 122  
123 123  (((
124 -(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSPH01.
138 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS75.
125 125  )))
126 126  
127 127  (((
128 -Each LSPH01 is shipped with a sticker with the default device EUI as below:
142 +Each LDDS75 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
129 129  )))
130 130  
131 131  [[image:image-20220607170145-1.jpeg]]
132 132  
133 133  
148 +For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
134 134  
135 -You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
150 +Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
136 136  
152 +**Add APP EUI in the application**
137 137  
138 -**Register the device**
154 +[[image:image-20220610161353-4.png]]
139 139  
156 +[[image:image-20220610161353-5.png]]
140 140  
141 -[[image:1654592600093-601.png]]
158 +[[image:image-20220610161353-6.png]]
142 142  
143 143  
161 +[[image:image-20220610161353-7.png]]
144 144  
145 -**Add APP EUI and DEV EUI**
146 146  
147 -[[image:1654592619856-881.png]]
164 +You can also choose to create the device manually.
148 148  
166 + [[image:image-20220610161538-8.png]]
149 149  
150 150  
151 -**Add APP EUI in the application**
152 152  
153 -[[image:1654592632656-512.png]]
170 +**Add APP KEY and DEV EUI**
154 154  
172 +[[image:image-20220610161538-9.png]]
155 155  
156 156  
157 -**Add APP KEY**
158 158  
159 -[[image:1654592653453-934.png]]
176 +(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
160 160  
161 161  
162 -(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
163 -
164 -
165 165  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
166 166  
167 -[[image:image-20220607170442-2.png]]
181 +[[image:image-20220610161724-10.png]]
168 168  
169 169  
170 170  (((
171 -(% 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.
185 +(% 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.
172 172  )))
173 173  
174 -[[image:1654833501679-968.png]]
188 +[[image:1654849068701-275.png]]
175 175  
176 176  
177 177  
... ... @@ -178,11 +178,10 @@
178 178  == 2.3  ​Uplink Payload ==
179 179  
180 180  (((
181 -LLDS12 will uplink payload via LoRaWAN with below payload format: 
182 -)))
195 +LDDS75 will uplink payload via LoRaWAN with below payload format: 
183 183  
184 -(((
185 -Uplink payload includes in total 11 bytes.
197 +Uplink payload includes in total 4 bytes.
198 +Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
186 186  )))
187 187  
188 188  (((
... ... @@ -192,23 +192,23 @@
192 192  (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
193 193  |=(% style="width: 62.5px;" %)(((
194 194  **Size (bytes)**
195 -)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
196 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
197 -[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
198 -)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
199 -[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
200 -)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
201 -[[Message Type>>||anchor="H2.3.7A0MessageType"]]
202 -)))
208 +)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
209 +|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
210 +[[Distance>>||anchor="H2.3.3A0Distance"]]
203 203  
204 -[[image:1654833689380-972.png]]
212 +(unit: mm)
213 +)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
214 +[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
215 +)))|[[Sensor Flag>>path:#Sensor_Flag]]
205 205  
217 +[[image:1654850511545-399.png]]
206 206  
207 207  
220 +
208 208  === 2.3.1  Battery Info ===
209 209  
210 210  
211 -Check the battery voltage for LLDS12.
224 +Check the battery voltage for LDDS75.
212 212  
213 213  Ex1: 0x0B45 = 2885mV
214 214  
... ... @@ -216,49 +216,21 @@
216 216  
217 217  
218 218  
219 -=== 2.3.2  DS18B20 Temperature sensor ===
232 +=== 2.3.2  Distance ===
220 220  
221 -This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
234 +Get the distance. Flat object range 280mm - 7500mm.
222 222  
236 +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.**
223 223  
224 -**Example**:
225 225  
226 -If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
239 +* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
240 +* 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.
227 227  
228 -If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
229 229  
243 +=== 2.3.3  Interrupt Pin ===
230 230  
231 -
232 -=== 2.3.3  Distance ===
233 -
234 -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.
235 -
236 -
237 -**Example**:
238 -
239 -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.
240 -
241 -
242 -
243 -=== 2.3.4  Distance signal strength ===
244 -
245 -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.
246 -
247 -
248 -**Example**:
249 -
250 -If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
251 -
252 -Customers can judge whether they need to adjust the environment based on the signal strength.
253 -
254 -
255 -
256 -=== 2.3.5  Interrupt Pin ===
257 -
258 258  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.
259 259  
260 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
261 -
262 262  **Example:**
263 263  
264 264  0x00: Normal uplink packet.
... ... @@ -267,52 +267,44 @@
267 267  
268 268  
269 269  
270 -=== 2.3.6  LiDAR temp ===
255 +=== 2.3.4  DS18B20 Temperature sensor ===
271 271  
272 -Characterize the internal temperature value of the sensor.
257 +This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
273 273  
274 -**Example: **
275 -If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
276 -If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
259 +**Example**:
277 277  
261 +If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
278 278  
263 +If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
279 279  
280 -=== 2.3.7  Message Type ===
265 +(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
281 281  
282 -(((
283 -For a normal uplink payload, the message type is always 0x01.
284 -)))
285 285  
286 -(((
287 -Valid Message Type:
288 -)))
289 289  
269 +=== 2.3.5  Sensor Flag ===
290 290  
291 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
292 -|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
293 -|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
294 -|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
271 +0x01: Detect Ultrasonic Sensor
295 295  
296 -=== 2.3.8  Decode payload in The Things Network ===
273 +0x00: No Ultrasonic Sensor
297 297  
275 +
276 +===
277 +(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
278 +
298 298  While using TTN network, you can add the payload format to decode the payload.
299 299  
300 300  
301 -[[image:1654592762713-715.png]]
282 +[[image:1654850829385-439.png]]
302 302  
303 -(((
304 -The payload decoder function for TTN is here:
305 -)))
284 +The payload decoder function for TTN V3 is here:
306 306  
307 -(((
308 -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/]]
309 -)))
286 +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/]]
310 310  
311 311  
312 312  
313 313  == 2.4  Uplink Interval ==
314 314  
315 -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"]]
292 +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"]]
316 316  
317 317  
318 318  
... ... @@ -343,47 +343,25 @@
343 343  
344 344  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
345 345  
346 -(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
323 +(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
347 347  
348 -[[image:1654832691989-514.png]]
325 +[[image:1654851029373-510.png]]
349 349  
350 350  
351 -[[image:1654592833877-762.png]]
328 +After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
352 352  
330 +[[image:image-20220610165129-11.png||height="595" width="1088"]]
353 353  
354 -[[image:1654832740634-933.png]]
355 355  
356 356  
357 -
358 -(((
359 -(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
360 -)))
361 -
362 -(((
363 -
364 -)))
365 -
366 -[[image:1654833065139-942.png]]
367 -
368 -
369 -
370 -[[image:1654833092678-390.png]]
371 -
372 -
373 -
374 -After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
375 -
376 -[[image:1654833163048-332.png]]
377 -
378 -
379 -
380 380  == 2.6  Frequency Plans ==
381 381  
382 382  (((
383 -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.
337 +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.
384 384  )))
385 385  
386 386  
341 +
387 387  === 2.6.1  EU863-870 (EU868) ===
388 388  
389 389  (((
... ... @@ -447,20 +447,51 @@
447 447  === 2.6.2  US902-928(US915) ===
448 448  
449 449  (((
450 -Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
451 -)))
405 +Used in USA, Canada and South America. Default use CHE=2
452 452  
453 -(((
454 -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.
455 -)))
407 +(% style="color:blue" %)**Uplink:**
456 456  
457 -(((
458 -After Join success, the end node will switch to the correct sub band by:
459 -)))
409 +903.9 - SF7BW125 to SF10BW125
460 460  
461 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
462 -* 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)
411 +904.1 - SF7BW125 to SF10BW125
463 463  
413 +904.3 - SF7BW125 to SF10BW125
414 +
415 +904.5 - SF7BW125 to SF10BW125
416 +
417 +904.7 - SF7BW125 to SF10BW125
418 +
419 +904.9 - SF7BW125 to SF10BW125
420 +
421 +905.1 - SF7BW125 to SF10BW125
422 +
423 +905.3 - SF7BW125 to SF10BW125
424 +
425 +
426 +(% style="color:blue" %)**Downlink:**
427 +
428 +923.3 - SF7BW500 to SF12BW500
429 +
430 +923.9 - SF7BW500 to SF12BW500
431 +
432 +924.5 - SF7BW500 to SF12BW500
433 +
434 +925.1 - SF7BW500 to SF12BW500
435 +
436 +925.7 - SF7BW500 to SF12BW500
437 +
438 +926.3 - SF7BW500 to SF12BW500
439 +
440 +926.9 - SF7BW500 to SF12BW500
441 +
442 +927.5 - SF7BW500 to SF12BW500
443 +
444 +923.3 - SF12BW500(RX2 downlink only)
445 +
446 +
447 +
448 +)))
449 +
464 464  === 2.6.3  CN470-510 (CN470) ===
465 465  
466 466  (((
... ... @@ -549,28 +549,54 @@
549 549  
550 550  
551 551  
552 -
553 553  === 2.6.4  AU915-928(AU915) ===
554 554  
555 555  (((
556 -Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
557 -)))
541 +Default use CHE=2
558 558  
559 -(((
560 -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.
561 -)))
543 +(% style="color:blue" %)**Uplink:**
562 562  
563 -(((
564 -
565 -)))
545 +916.8 - SF7BW125 to SF12BW125
566 566  
567 -(((
568 -After Join success, the end node will switch to the correct sub band by:
569 -)))
547 +917.0 - SF7BW125 to SF12BW125
570 570  
571 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
572 -* 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)
549 +917.2 - SF7BW125 to SF12BW125
573 573  
551 +917.4 - SF7BW125 to SF12BW125
552 +
553 +917.6 - SF7BW125 to SF12BW125
554 +
555 +917.8 - SF7BW125 to SF12BW125
556 +
557 +918.0 - SF7BW125 to SF12BW125
558 +
559 +918.2 - SF7BW125 to SF12BW125
560 +
561 +
562 +(% style="color:blue" %)**Downlink:**
563 +
564 +923.3 - SF7BW500 to SF12BW500
565 +
566 +923.9 - SF7BW500 to SF12BW500
567 +
568 +924.5 - SF7BW500 to SF12BW500
569 +
570 +925.1 - SF7BW500 to SF12BW500
571 +
572 +925.7 - SF7BW500 to SF12BW500
573 +
574 +926.3 - SF7BW500 to SF12BW500
575 +
576 +926.9 - SF7BW500 to SF12BW500
577 +
578 +927.5 - SF7BW500 to SF12BW500
579 +
580 +923.3 - SF12BW500(RX2 downlink only)
581 +
582 +
583 +
584 +)))
585 +
574 574  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
575 575  
576 576  (((
... ... @@ -679,7 +679,6 @@
679 679  
680 680  
681 681  
682 -
683 683  === 2.6.6  KR920-923 (KR920) ===
684 684  
685 685  (((
... ... @@ -752,7 +752,6 @@
752 752  
753 753  
754 754  
755 -
756 756  === 2.6.7  IN865-867 (IN865) ===
757 757  
758 758  (((
... ... @@ -789,18 +789,21 @@
789 789  
790 790  
791 791  
792 -
793 793  == 2.7  LED Indicator ==
794 794  
795 -The LLDS12 has an internal LED which is to show the status of different state.
804 +The LDDS75 has an internal LED which is to show the status of different state.
796 796  
797 -* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
806 +
807 +* Blink once when device power on.
808 +* The device detects the sensor and flashes 5 times.
809 +* Solid ON for 5 seconds once device successful Join the network.
798 798  * Blink once when device transmit a packet.
799 799  
812 +
800 800  == 2.8  ​Firmware Change Log ==
801 801  
802 802  
803 -**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/]]
816 +**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/]]
804 804  
805 805  
806 806  **Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
... ... @@ -807,71 +807,58 @@
807 807  
808 808  
809 809  
810 -= 3.  LiDAR ToF Measurement =
823 +== 2.9  Mechanical ==
811 811  
812 -== 3.1 Principle of Distance Measurement ==
813 813  
814 -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.
826 +[[image:image-20220610172003-1.png]]
815 815  
816 -[[image:1654831757579-263.png]]
828 +[[image:image-20220610172003-2.png]]
817 817  
818 818  
831 +== 2.10  Battery Analysis ==
819 819  
820 -== 3.2 Distance Measurement Characteristics ==
833 +=== 2.10.1  Battery Type ===
821 821  
822 -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:
835 +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.
823 823  
824 -[[image:1654831774373-275.png]]
825 825  
838 +The battery related documents as below:
826 826  
827 -(((
828 -(% style="color:blue" %)**① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
840 +* (((
841 +[[ Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
829 829  )))
830 -
831 -(((
832 -(% style="color:blue" %)**② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
843 +* (((
844 +[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
833 833  )))
834 -
835 -(((
836 -(% style="color:blue" %)**③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
846 +* (((
847 +[[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]]
837 837  )))
838 838  
850 + [[image:image-20220610172400-3.png]]
839 839  
840 -(((
841 -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:
842 -)))
843 843  
844 844  
845 -[[image:1654831797521-720.png]]
854 +=== 2.10.2  Replace the battery ===
846 846  
856 +(((
857 +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.
858 +)))
847 847  
848 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.
861 +
850 850  )))
851 851  
852 -[[image:1654831810009-716.png]]
853 -
854 -
855 855  (((
856 -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.
865 +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)
857 857  )))
858 858  
859 859  
860 860  
861 -== 3.3 Notice of usage: ==
870 += 3.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
862 862  
863 -Possible invalid /wrong reading for LiDAR ToF tech:
864 -
865 -* Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
866 -* While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might wrong.
867 -* The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
868 -* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
869 -
870 -= 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
871 -
872 872  (((
873 873  (((
874 -Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
874 +Use can configure LDDS75 via AT Command or LoRaWAN Downlink.
875 875  )))
876 876  )))
877 877  
... ... @@ -892,7 +892,7 @@
892 892  )))
893 893  
894 894  (((
895 -There are two kinds of commands to configure LLDS12, they are:
895 +There are two kinds of commands to configure LDDS75, they are:
896 896  )))
897 897  )))
898 898  
... ... @@ -933,55 +933,49 @@
933 933  
934 934  * (((
935 935  (((
936 -(% style="color:#4f81bd" %)** Commands special design for LLDS12**
936 +(% style="color:#4f81bd" %)** Commands special design for LDDS75**
937 937  )))
938 938  )))
939 939  
940 940  (((
941 941  (((
942 -These commands only valid for LLDS12, as below:
942 +These commands only valid for LDDS75, as below:
943 943  )))
944 944  )))
945 945  
946 946  
947 947  
948 -== 4.1  Set Transmit Interval Time ==
948 +== 3.1  Access AT Commands ==
949 949  
950 -Feature: Change LoRaWAN End Node Transmit Interval.
950 +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.
951 951  
952 -(% style="color:#037691" %)**AT Command: AT+TDC**
952 +[[image:image-20220610172924-4.png||height="483" width="988"]]
953 953  
954 -[[image:image-20220607171554-8.png]]
955 955  
955 +Or if you have below board, use below connection:
956 956  
957 -(((
958 -(% style="color:#037691" %)**Downlink Command: 0x01**
959 -)))
960 960  
961 -(((
962 -Format: Command Code (0x01) followed by 3 bytes time value.
963 -)))
958 +[[image:image-20220610172924-5.png]]
964 964  
965 -(((
966 -If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
967 -)))
968 968  
969 -* (((
970 -Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
971 -)))
972 -* (((
973 -Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
974 -)))
961 +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:
975 975  
976 -== 4.2  Set Interrupt Mode ==
977 977  
978 -Feature, Set Interrupt mode for GPIO_EXIT.
964 + [[image:image-20220610172924-6.png||height="601" width="860"]]
979 979  
980 -(% style="color:#037691" %)**AT Command: AT+INTMOD**
981 981  
982 -[[image:image-20220610105806-2.png]]
983 983  
968 +== 3.2  Set Transmit Interval Time ==
984 984  
970 +Feature: Change LoRaWAN End Node Transmit Interval.
971 +
972 +(% style="color:#037691" %)**AT Command: AT+TDC**
973 +
974 +[[image:image-20220610173409-7.png]]
975 +
976 +
977 +
978 +
985 985  (((
986 986  (% style="color:#037691" %)**Downlink Command: 0x06**
987 987  )))
... ... @@ -1001,7 +1001,7 @@
1001 1001  Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
1002 1002  )))
1003 1003  
1004 -== 4.3  Get Firmware Version Info ==
998 +== 3.3  Get Firmware Version Info ==
1005 1005  
1006 1006  Feature: use downlink to get firmware version.
1007 1007  
... ... @@ -1272,7 +1272,6 @@
1272 1272  * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1273 1273  * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1274 1274  
1275 -
1276 1276  = 10. ​ Packing Info =
1277 1277  
1278 1278  
... ... @@ -1287,7 +1287,6 @@
1287 1287  * Package Size / pcs : cm
1288 1288  * Weight / pcs : g
1289 1289  
1290 -
1291 1291  = 11.  ​Support =
1292 1292  
1293 1293  * 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.
1654847051249-359.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.8 KB
Content
1654847583902-256.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +492.6 KB
Content
1654848616367-242.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.8 KB
Content
1654849068701-275.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +88.3 KB
Content
1654850511545-399.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +88.3 KB
Content
1654850829385-439.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +59.2 KB
Content
1654851029373-510.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +92.0 KB
Content
1654852175653-550.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +106.2 KB
Content
1654852253176-749.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +106.6 KB
Content
image-20220610154839-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +11.3 KB
Content
image-20220610155021-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +164.8 KB
Content
image-20220610155021-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +181.8 KB
Content
image-20220610161353-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +32.2 KB
Content
image-20220610161353-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +42.7 KB
Content
image-20220610161353-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +36.3 KB
Content
image-20220610161353-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.1 KB
Content
image-20220610161538-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.2 KB
Content
image-20220610161538-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +28.7 KB
Content
image-20220610161724-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +180.0 KB
Content
image-20220610165129-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +50.5 KB
Content
image-20220610172003-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +5.9 KB
Content
image-20220610172003-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +18.6 KB
Content
image-20220610172400-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +370.3 KB
Content
image-20220610172924-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.5 MB
Content
image-20220610172924-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +901.4 KB
Content
image-20220610172924-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +68.6 KB
Content
image-20220610173409-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +11.8 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0