Last modified by Mengting Qiu on 2025/02/26 15:04
<
From version < 133.4 >
edited by Xiaoling
on 2022/06/10 16:28
To version < 138.1 >
edited by Xiaoling
on 2022/06/10 17:03
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -92,7 +92,6 @@
92 92  * Sewer
93 93  * Bottom water level monitoring
94 94  
95 -
96 96  == 1.6  Pin mapping and power on ==
97 97  
98 98  
... ... @@ -184,7 +184,7 @@
184 184  == 2.3  ​Uplink Payload ==
185 185  
186 186  (((
187 -LDDS75 will uplink payload via LoRaWAN with below payload format:
186 +LDDS75 will uplink payload via LoRaWAN with below payload format: 
188 188  
189 189  Uplink payload includes in total 4 bytes.
190 190  Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
... ... @@ -206,7 +206,7 @@
206 206  [[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
207 207  )))|[[Sensor Flag>>path:#Sensor_Flag]]
208 208  
209 -[[image:1654833689380-972.png]]
208 +[[image:1654850511545-399.png]]
210 210  
211 211  
212 212  
... ... @@ -213,7 +213,7 @@
213 213  === 2.3.1  Battery Info ===
214 214  
215 215  
216 -Check the battery voltage for LLDS12.
215 +Check the battery voltage for LDDS75.
217 217  
218 218  Ex1: 0x0B45 = 2885mV
219 219  
... ... @@ -221,49 +221,22 @@
221 221  
222 222  
223 223  
224 -=== 2.3.2  DS18B20 Temperature sensor ===
223 +=== 2.3.2  Distance ===
225 225  
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.
225 +Get the distance. Flat object range 280mm - 7500mm.
227 227  
227 +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.**
228 228  
229 -**Example**:
230 230  
231 -If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
230 +* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
231 +* 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.
232 232  
233 -If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
234 234  
235 235  
235 +=== 2.3.3  Interrupt Pin ===
236 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 -
263 263  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.
264 264  
265 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
266 -
267 267  **Example:**
268 268  
269 269  0x00: Normal uplink packet.
... ... @@ -271,53 +271,44 @@
271 271  0x01: Interrupt Uplink Packet.
272 272  
273 273  
246 +=== 2.3.4  DS18B20 Temperature sensor ===
274 274  
275 -=== 2.3.6  LiDAR temp ===
248 +This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
276 276  
277 -Characterize the internal temperature value of the sensor.
250 +**Example**:
278 278  
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℃.
252 +If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
282 282  
254 +If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
283 283  
256 +(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
284 284  
285 -=== 2.3.7  Message Type ===
286 286  
287 -(((
288 -For a normal uplink payload, the message type is always 0x01.
289 -)))
290 290  
291 -(((
292 -Valid Message Type:
293 -)))
260 +=== 2.3.5  Sensor Flag ===
294 294  
262 +0x01: Detect Ultrasonic Sensor
295 295  
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"]]
264 +0x00: No Ultrasonic Sensor
300 300  
301 -=== 2.3.8  Decode payload in The Things Network ===
302 302  
267 +===
268 +(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
269 +
303 303  While using TTN network, you can add the payload format to decode the payload.
304 304  
305 305  
306 -[[image:1654592762713-715.png]]
273 +[[image:1654850829385-439.png]]
307 307  
308 -(((
309 -The payload decoder function for TTN is here:
310 -)))
275 +The payload decoder function for TTN V3 is here:
311 311  
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 -)))
277 +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/]]
315 315  
316 316  
317 317  
318 318  == 2.4  Uplink Interval ==
319 319  
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"]]
283 +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"]]
321 321  
322 322  
323 323  
... ... @@ -348,47 +348,25 @@
348 348  
349 349  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
350 350  
351 -(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
314 +(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
352 352  
353 -[[image:1654832691989-514.png]]
316 +[[image:1654851029373-510.png]]
354 354  
355 355  
356 -[[image:1654592833877-762.png]]
319 +After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
357 357  
321 +[[image:image-20220610165129-11.png||height="595" width="1088"]]
358 358  
359 -[[image:1654832740634-933.png]]
360 360  
361 361  
362 -
363 -(((
364 -(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
365 -)))
366 -
367 -(((
368 -
369 -)))
370 -
371 -[[image:1654833065139-942.png]]
372 -
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 385  == 2.6  Frequency Plans ==
386 386  
387 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.
328 +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.
389 389  )))
390 390  
391 391  
332 +
392 392  === 2.6.1  EU863-870 (EU868) ===
393 393  
394 394  (((
... ... @@ -452,20 +452,51 @@
452 452  === 2.6.2  US902-928(US915) ===
453 453  
454 454  (((
455 -Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
456 -)))
396 +Used in USA, Canada and South America. Default use CHE=2
457 457  
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 -)))
398 +(% style="color:blue" %)**Uplink:**
461 461  
462 -(((
463 -After Join success, the end node will switch to the correct sub band by:
464 -)))
400 +903.9 - SF7BW125 to SF10BW125
465 465  
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)
402 +904.1 - SF7BW125 to SF10BW125
468 468  
404 +904.3 - SF7BW125 to SF10BW125
405 +
406 +904.5 - SF7BW125 to SF10BW125
407 +
408 +904.7 - SF7BW125 to SF10BW125
409 +
410 +904.9 - SF7BW125 to SF10BW125
411 +
412 +905.1 - SF7BW125 to SF10BW125
413 +
414 +905.3 - SF7BW125 to SF10BW125
415 +
416 +
417 +(% style="color:blue" %)**Downlink:**
418 +
419 +923.3 - SF7BW500 to SF12BW500
420 +
421 +923.9 - SF7BW500 to SF12BW500
422 +
423 +924.5 - SF7BW500 to SF12BW500
424 +
425 +925.1 - SF7BW500 to SF12BW500
426 +
427 +925.7 - SF7BW500 to SF12BW500
428 +
429 +926.3 - SF7BW500 to SF12BW500
430 +
431 +926.9 - SF7BW500 to SF12BW500
432 +
433 +927.5 - SF7BW500 to SF12BW500
434 +
435 +923.3 - SF12BW500(RX2 downlink only)
436 +
437 +
438 +
439 +)))
440 +
469 469  === 2.6.3  CN470-510 (CN470) ===
470 470  
471 471  (((
... ... @@ -558,24 +558,51 @@
558 558  === 2.6.4  AU915-928(AU915) ===
559 559  
560 560  (((
561 -Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
562 -)))
533 +Default use CHE=2
563 563  
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 -)))
535 +(% style="color:blue" %)**Uplink:**
567 567  
568 -(((
569 -
570 -)))
537 +916.8 - SF7BW125 to SF12BW125
571 571  
572 -(((
573 -After Join success, the end node will switch to the correct sub band by:
574 -)))
539 +917.0 - SF7BW125 to SF12BW125
575 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)
541 +917.2 - SF7BW125 to SF12BW125
578 578  
543 +917.4 - SF7BW125 to SF12BW125
544 +
545 +917.6 - SF7BW125 to SF12BW125
546 +
547 +917.8 - SF7BW125 to SF12BW125
548 +
549 +918.0 - SF7BW125 to SF12BW125
550 +
551 +918.2 - SF7BW125 to SF12BW125
552 +
553 +
554 +(% style="color:blue" %)**Downlink:**
555 +
556 +923.3 - SF7BW500 to SF12BW500
557 +
558 +923.9 - SF7BW500 to SF12BW500
559 +
560 +924.5 - SF7BW500 to SF12BW500
561 +
562 +925.1 - SF7BW500 to SF12BW500
563 +
564 +925.7 - SF7BW500 to SF12BW500
565 +
566 +926.3 - SF7BW500 to SF12BW500
567 +
568 +926.9 - SF7BW500 to SF12BW500
569 +
570 +927.5 - SF7BW500 to SF12BW500
571 +
572 +923.3 - SF12BW500(RX2 downlink only)
573 +
574 +
575 +
576 +)))
577 +
579 579  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
580 580  
581 581  (((
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
image-20220610165129-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +50.5 KB
Content

Applications

Navigation

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