Last modified by Mengting Qiu on 2024/03/07 08:41
<
From version < 138.3 >
edited by Xiaoling
on 2022/06/10 17:04
To version < 133.4 >
edited by Xiaoling
on 2022/06/10 16:28
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -57,9 +57,6 @@
57 57  * IP66 Waterproof Enclosure
58 58  * 4000mAh or 8500mAh Battery for long term use
59 59  
60 -
61 -
62 -
63 63  == 1.3  Specification ==
64 64  
65 65  === 1.3.1  Rated environmental conditions ===
... ... @@ -83,7 +83,6 @@
83 83  (% style="display:none" %) (%%)
84 84  
85 85  
86 -
87 87  == 1.5 ​ Applications ==
88 88  
89 89  * Horizontal distance measurement
... ... @@ -97,8 +97,6 @@
97 97  * Bottom water level monitoring
98 98  
99 99  
100 -
101 -
102 102  == 1.6  Pin mapping and power on ==
103 103  
104 104  
... ... @@ -105,7 +105,6 @@
105 105  [[image:1654847583902-256.png]]
106 106  
107 107  
108 -
109 109  = 2.  Configure LDDS75 to connect to LoRaWAN network =
110 110  
111 111  == 2.1  How it works ==
... ... @@ -191,7 +191,7 @@
191 191  == 2.3  ​Uplink Payload ==
192 192  
193 193  (((
194 -LDDS75 will uplink payload via LoRaWAN with below payload format: 
187 +LDDS75 will uplink payload via LoRaWAN with below payload format:
195 195  
196 196  Uplink payload includes in total 4 bytes.
197 197  Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
... ... @@ -213,7 +213,7 @@
213 213  [[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
214 214  )))|[[Sensor Flag>>path:#Sensor_Flag]]
215 215  
216 -[[image:1654850511545-399.png]]
209 +[[image:1654833689380-972.png]]
217 217  
218 218  
219 219  
... ... @@ -220,7 +220,7 @@
220 220  === 2.3.1  Battery Info ===
221 221  
222 222  
223 -Check the battery voltage for LDDS75.
216 +Check the battery voltage for LLDS12.
224 224  
225 225  Ex1: 0x0B45 = 2885mV
226 226  
... ... @@ -228,21 +228,49 @@
228 228  
229 229  
230 230  
231 -=== 2.3.2  Distance ===
224 +=== 2.3.2  DS18B20 Temperature sensor ===
232 232  
233 -Get the distance. Flat object range 280mm - 7500mm.
226 +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 234  
235 -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.**
236 236  
229 +**Example**:
237 237  
238 -* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
239 -* 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.
231 +If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
240 240  
233 +If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
241 241  
242 -=== 2.3.3  Interrupt Pin ===
243 243  
236 +
237 +=== 2.3.3  Distance ===
238 +
239 +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.
240 +
241 +
242 +**Example**:
243 +
244 +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.
245 +
246 +
247 +
248 +=== 2.3.4  Distance signal strength ===
249 +
250 +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.
251 +
252 +
253 +**Example**:
254 +
255 +If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
256 +
257 +Customers can judge whether they need to adjust the environment based on the signal strength.
258 +
259 +
260 +
261 +=== 2.3.5  Interrupt Pin ===
262 +
244 244  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.
245 245  
265 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
266 +
246 246  **Example:**
247 247  
248 248  0x00: Normal uplink packet.
... ... @@ -250,44 +250,53 @@
250 250  0x01: Interrupt Uplink Packet.
251 251  
252 252  
253 -=== 2.3.4  DS18B20 Temperature sensor ===
254 254  
255 -This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
275 +=== 2.3.6  LiDAR temp ===
256 256  
257 -**Example**:
277 +Characterize the internal temperature value of the sensor.
258 258  
259 -If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
279 +**Example: **
280 +If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
281 +If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
260 260  
261 -If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
262 262  
263 -(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
264 264  
285 +=== 2.3.7  Message Type ===
265 265  
287 +(((
288 +For a normal uplink payload, the message type is always 0x01.
289 +)))
266 266  
267 -=== 2.3.5  Sensor Flag ===
291 +(((
292 +Valid Message Type:
293 +)))
268 268  
269 -0x01: Detect Ultrasonic Sensor
270 270  
271 -0x00: No Ultrasonic Sensor
296 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
297 +|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
298 +|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
299 +|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
272 272  
301 +=== 2.3.8  Decode payload in The Things Network ===
273 273  
274 -===
275 -(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
276 -
277 277  While using TTN network, you can add the payload format to decode the payload.
278 278  
279 279  
280 -[[image:1654850829385-439.png]]
306 +[[image:1654592762713-715.png]]
281 281  
282 -The payload decoder function for TTN V3 is here:
308 +(((
309 +The payload decoder function for TTN is here:
310 +)))
283 283  
284 -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/]]
312 +(((
313 +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/]]
314 +)))
285 285  
286 286  
287 287  
288 288  == 2.4  Uplink Interval ==
289 289  
290 -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"]]
320 +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"]]
291 291  
292 292  
293 293  
... ... @@ -318,25 +318,47 @@
318 318  
319 319  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
320 320  
321 -(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
351 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
322 322  
323 -[[image:1654851029373-510.png]]
353 +[[image:1654832691989-514.png]]
324 324  
325 325  
326 -After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
356 +[[image:1654592833877-762.png]]
327 327  
328 -[[image:image-20220610165129-11.png||height="595" width="1088"]]
329 329  
359 +[[image:1654832740634-933.png]]
330 330  
331 331  
332 -== 2.6  Frequency Plans ==
333 333  
334 334  (((
335 -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.
364 +(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
336 336  )))
337 337  
367 +(((
368 +
369 +)))
338 338  
371 +[[image:1654833065139-942.png]]
339 339  
373 +
374 +
375 +[[image:1654833092678-390.png]]
376 +
377 +
378 +
379 +After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
380 +
381 +[[image:1654833163048-332.png]]
382 +
383 +
384 +
385 +== 2.6  Frequency Plans ==
386 +
387 +(((
388 +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.
389 +)))
390 +
391 +
340 340  === 2.6.1  EU863-870 (EU868) ===
341 341  
342 342  (((
... ... @@ -400,51 +400,20 @@
400 400  === 2.6.2  US902-928(US915) ===
401 401  
402 402  (((
403 -Used in USA, Canada and South America. Default use CHE=2
455 +Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
456 +)))
404 404  
405 -(% style="color:blue" %)**Uplink:**
458 +(((
459 +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.
460 +)))
406 406  
407 -903.9 - SF7BW125 to SF10BW125
408 -
409 -904.1 - SF7BW125 to SF10BW125
410 -
411 -904.3 - SF7BW125 to SF10BW125
412 -
413 -904.5 - SF7BW125 to SF10BW125
414 -
415 -904.7 - SF7BW125 to SF10BW125
416 -
417 -904.9 - SF7BW125 to SF10BW125
418 -
419 -905.1 - SF7BW125 to SF10BW125
420 -
421 -905.3 - SF7BW125 to SF10BW125
422 -
423 -
424 -(% style="color:blue" %)**Downlink:**
425 -
426 -923.3 - SF7BW500 to SF12BW500
427 -
428 -923.9 - SF7BW500 to SF12BW500
429 -
430 -924.5 - SF7BW500 to SF12BW500
431 -
432 -925.1 - SF7BW500 to SF12BW500
433 -
434 -925.7 - SF7BW500 to SF12BW500
435 -
436 -926.3 - SF7BW500 to SF12BW500
437 -
438 -926.9 - SF7BW500 to SF12BW500
439 -
440 -927.5 - SF7BW500 to SF12BW500
441 -
442 -923.3 - SF12BW500(RX2 downlink only)
443 -
444 -
445 -
462 +(((
463 +After Join success, the end node will switch to the correct sub band by:
446 446  )))
447 447  
466 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
467 +* 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)
468 +
448 448  === 2.6.3  CN470-510 (CN470) ===
449 449  
450 450  (((
... ... @@ -537,51 +537,24 @@
537 537  === 2.6.4  AU915-928(AU915) ===
538 538  
539 539  (((
540 -Default use CHE=2
561 +Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
562 +)))
541 541  
542 -(% style="color:blue" %)**Uplink:**
564 +(((
565 +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.
566 +)))
543 543  
544 -916.8 - SF7BW125 to SF12BW125
545 -
546 -917.0 - SF7BW125 to SF12BW125
547 -
548 -917.2 - SF7BW125 to SF12BW125
549 -
550 -917.4 - SF7BW125 to SF12BW125
551 -
552 -917.6 - SF7BW125 to SF12BW125
553 -
554 -917.8 - SF7BW125 to SF12BW125
555 -
556 -918.0 - SF7BW125 to SF12BW125
557 -
558 -918.2 - SF7BW125 to SF12BW125
559 -
560 -
561 -(% style="color:blue" %)**Downlink:**
562 -
563 -923.3 - SF7BW500 to SF12BW500
564 -
565 -923.9 - SF7BW500 to SF12BW500
566 -
567 -924.5 - SF7BW500 to SF12BW500
568 -
569 -925.1 - SF7BW500 to SF12BW500
570 -
571 -925.7 - SF7BW500 to SF12BW500
572 -
573 -926.3 - SF7BW500 to SF12BW500
574 -
575 -926.9 - SF7BW500 to SF12BW500
576 -
577 -927.5 - SF7BW500 to SF12BW500
578 -
579 -923.3 - SF12BW500(RX2 downlink only)
580 -
581 -
568 +(((
582 582  
583 583  )))
584 584  
572 +(((
573 +After Join success, the end node will switch to the correct sub band by:
574 +)))
575 +
576 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
577 +* 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)
578 +
585 585  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
586 586  
587 587  (((
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
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