Last modified by Mengting Qiu on 2024/03/07 08:41
<
From version < 139.2 >
edited by Xiaoling
on 2022/06/10 17:09
To version < 131.1 >
edited by Xiaoling
on 2022/06/10 16:15
>
Change comment: Uploaded new attachment "image-20220610161538-9.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -57,7 +57,6 @@
57 57  * IP66 Waterproof Enclosure
58 58  * 4000mAh or 8500mAh Battery for long term use
59 59  
60 -
61 61  == 1.3  Specification ==
62 62  
63 63  === 1.3.1  Rated environmental conditions ===
... ... @@ -72,22 +72,15 @@
72 72  
73 73  === 1.3.2  Effective measurement range Reference beam pattern ===
74 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.**
74 +**(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"]]
76 76  
77 77  
78 -[[image:image-20220610155021-2.png||height="377" width="1021"]]
79 79  
78 +**(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"]]
80 80  
80 +(% style="display:none" %) (%%)
81 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 83  
84 -
85 -[[image:1654852175653-550.png]]
86 -
87 -(% style="display:none" %) ** **
88 -
89 -
90 -
91 91  == 1.5 ​ Applications ==
92 92  
93 93  * Horizontal distance measurement
... ... @@ -107,7 +107,6 @@
107 107  [[image:1654847583902-256.png]]
108 108  
109 109  
110 -
111 111  = 2.  Configure LDDS75 to connect to LoRaWAN network =
112 112  
113 113  == 2.1  How it works ==
... ... @@ -121,7 +121,6 @@
121 121  )))
122 122  
123 123  
124 -
125 125  == 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
126 126  
127 127  (((
... ... @@ -151,43 +151,44 @@
151 151  
152 152  Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
153 153  
154 -**Add APP EUI in the application**
155 155  
156 -[[image:image-20220610161353-4.png]]
145 +**Register the device**
157 157  
158 -[[image:image-20220610161353-5.png]]
159 159  
160 -[[image:image-20220610161353-6.png]]
148 +[[image:1654592600093-601.png]]
161 161  
162 162  
163 -[[image:image-20220610161353-7.png]]
164 164  
152 +**Add APP EUI and DEV EUI**
165 165  
166 -You can also choose to create the device manually.
154 +[[image:1654592619856-881.png]]
167 167  
168 - [[image:image-20220610161538-8.png]]
169 169  
170 170  
158 +**Add APP EUI in the application**
171 171  
172 -**Add APP KEY and DEV EUI**
160 +[[image:1654592632656-512.png]]
173 173  
174 -[[image:image-20220610161538-9.png]]
175 175  
176 176  
164 +**Add APP KEY**
177 177  
178 -(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
166 +[[image:1654592653453-934.png]]
179 179  
180 180  
169 +(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
170 +
171 +
181 181  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
182 182  
183 -[[image:image-20220610161724-10.png]]
174 +[[image:image-20220607170442-2.png]]
184 184  
185 185  
186 186  (((
187 -(% 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.
188 188  )))
189 189  
190 -[[image:1654849068701-275.png]]
181 +[[image:1654833501679-968.png]]
191 191  
192 192  
193 193  
... ... @@ -194,10 +194,11 @@
194 194  == 2.3  ​Uplink Payload ==
195 195  
196 196  (((
197 -LDDS75 will uplink payload via LoRaWAN with below payload format: 
188 +LLDS12 will uplink payload via LoRaWAN with below payload format: 
189 +)))
198 198  
199 -Uplink payload includes in total 4 bytes.
200 -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.
201 201  )))
202 202  
203 203  (((
... ... @@ -207,23 +207,23 @@
207 207  (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
208 208  |=(% style="width: 62.5px;" %)(((
209 209  **Size (bytes)**
210 -)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
211 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
212 -[[Distance>>||anchor="H2.3.3A0Distance"]]
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 +)))
213 213  
214 -(unit: mm)
215 -)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
216 -[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
217 -)))|[[Sensor Flag>>path:#Sensor_Flag]]
211 +[[image:1654833689380-972.png]]
218 218  
219 -[[image:1654850511545-399.png]]
220 220  
221 221  
222 -
223 223  === 2.3.1  Battery Info ===
224 224  
225 225  
226 -Check the battery voltage for LDDS75.
218 +Check the battery voltage for LLDS12.
227 227  
228 228  Ex1: 0x0B45 = 2885mV
229 229  
... ... @@ -231,22 +231,49 @@
231 231  
232 232  
233 233  
234 -=== 2.3.2  Distance ===
226 +=== 2.3.2  DS18B20 Temperature sensor ===
235 235  
236 -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.
237 237  
238 -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.**
239 239  
231 +**Example**:
240 240  
241 -* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
242 -* 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
243 243  
235 +If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
244 244  
245 245  
246 -=== 2.3.3  Interrupt Pin ===
247 247  
239 +=== 2.3.3  Distance ===
240 +
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.
242 +
243 +
244 +**Example**:
245 +
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.
247 +
248 +
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 +
255 +**Example**:
256 +
257 +If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
258 +
259 +Customers can judge whether they need to adjust the environment based on the signal strength.
260 +
261 +
262 +
263 +=== 2.3.5  Interrupt Pin ===
264 +
248 248  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.
249 249  
267 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
268 +
250 250  **Example:**
251 251  
252 252  0x00: Normal uplink packet.
... ... @@ -255,44 +255,52 @@
255 255  
256 256  
257 257  
258 -=== 2.3.4  DS18B20 Temperature sensor ===
277 +=== 2.3.6  LiDAR temp ===
259 259  
260 -This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
279 +Characterize the internal temperature value of the sensor.
261 261  
262 -**Example**:
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℃.
263 263  
264 -If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
265 265  
266 -If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
267 267  
268 -(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
287 +=== 2.3.7  Message Type ===
269 269  
289 +(((
290 +For a normal uplink payload, the message type is always 0x01.
291 +)))
270 270  
293 +(((
294 +Valid Message Type:
295 +)))
271 271  
272 -=== 2.3.5  Sensor Flag ===
273 273  
274 -0x01: Detect Ultrasonic Sensor
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"]]
275 275  
276 -0x00: No Ultrasonic Sensor
303 +=== 2.3.8  Decode payload in The Things Network ===
277 277  
278 -
279 -===
280 -(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
281 -
282 282  While using TTN network, you can add the payload format to decode the payload.
283 283  
284 284  
285 -[[image:1654850829385-439.png]]
308 +[[image:1654592762713-715.png]]
286 286  
287 -The payload decoder function for TTN V3 is here:
310 +(((
311 +The payload decoder function for TTN is here:
312 +)))
288 288  
289 -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 +)))
290 290  
291 291  
292 292  
293 293  == 2.4  Uplink Interval ==
294 294  
295 -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"]]
296 296  
297 297  
298 298  
... ... @@ -323,25 +323,47 @@
323 323  
324 324  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
325 325  
326 -(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
353 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
327 327  
328 -[[image:1654851029373-510.png]]
355 +[[image:1654832691989-514.png]]
329 329  
330 330  
331 -After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
358 +[[image:1654592833877-762.png]]
332 332  
333 -[[image:image-20220610165129-11.png||height="595" width="1088"]]
334 334  
361 +[[image:1654832740634-933.png]]
335 335  
336 336  
337 -== 2.6  Frequency Plans ==
338 338  
339 339  (((
340 -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**
341 341  )))
342 342  
369 +(((
370 +
371 +)))
343 343  
373 +[[image:1654833065139-942.png]]
344 344  
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 +
345 345  === 2.6.1  EU863-870 (EU868) ===
346 346  
347 347  (((
... ... @@ -405,51 +405,20 @@
405 405  === 2.6.2  US902-928(US915) ===
406 406  
407 407  (((
408 -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 +)))
409 409  
410 -(% 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 +)))
411 411  
412 -903.9 - SF7BW125 to SF10BW125
413 -
414 -904.1 - SF7BW125 to SF10BW125
415 -
416 -904.3 - SF7BW125 to SF10BW125
417 -
418 -904.5 - SF7BW125 to SF10BW125
419 -
420 -904.7 - SF7BW125 to SF10BW125
421 -
422 -904.9 - SF7BW125 to SF10BW125
423 -
424 -905.1 - SF7BW125 to SF10BW125
425 -
426 -905.3 - SF7BW125 to SF10BW125
427 -
428 -
429 -(% style="color:blue" %)**Downlink:**
430 -
431 -923.3 - SF7BW500 to SF12BW500
432 -
433 -923.9 - SF7BW500 to SF12BW500
434 -
435 -924.5 - SF7BW500 to SF12BW500
436 -
437 -925.1 - SF7BW500 to SF12BW500
438 -
439 -925.7 - SF7BW500 to SF12BW500
440 -
441 -926.3 - SF7BW500 to SF12BW500
442 -
443 -926.9 - SF7BW500 to SF12BW500
444 -
445 -927.5 - SF7BW500 to SF12BW500
446 -
447 -923.3 - SF12BW500(RX2 downlink only)
448 -
449 -
450 -
464 +(((
465 +After Join success, the end node will switch to the correct sub band by:
451 451  )))
452 452  
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)
470 +
453 453  === 2.6.3  CN470-510 (CN470) ===
454 454  
455 455  (((
... ... @@ -542,51 +542,24 @@
542 542  === 2.6.4  AU915-928(AU915) ===
543 543  
544 544  (((
545 -Default use CHE=2
563 +Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
564 +)))
546 546  
547 -(% style="color:blue" %)**Uplink:**
566 +(((
567 +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.
568 +)))
548 548  
549 -916.8 - SF7BW125 to SF12BW125
550 -
551 -917.0 - SF7BW125 to SF12BW125
552 -
553 -917.2 - SF7BW125 to SF12BW125
554 -
555 -917.4 - SF7BW125 to SF12BW125
556 -
557 -917.6 - SF7BW125 to SF12BW125
558 -
559 -917.8 - SF7BW125 to SF12BW125
560 -
561 -918.0 - SF7BW125 to SF12BW125
562 -
563 -918.2 - SF7BW125 to SF12BW125
564 -
565 -
566 -(% style="color:blue" %)**Downlink:**
567 -
568 -923.3 - SF7BW500 to SF12BW500
569 -
570 -923.9 - SF7BW500 to SF12BW500
571 -
572 -924.5 - SF7BW500 to SF12BW500
573 -
574 -925.1 - SF7BW500 to SF12BW500
575 -
576 -925.7 - SF7BW500 to SF12BW500
577 -
578 -926.3 - SF7BW500 to SF12BW500
579 -
580 -926.9 - SF7BW500 to SF12BW500
581 -
582 -927.5 - SF7BW500 to SF12BW500
583 -
584 -923.3 - SF12BW500(RX2 downlink only)
585 -
586 -
570 +(((
587 587  
588 588  )))
589 589  
574 +(((
575 +After Join success, the end node will switch to the correct sub band by:
576 +)))
577 +
578 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
579 +* 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)
580 +
590 590  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
591 591  
592 592  (((
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
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

Applications

Navigation

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