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

Summary

Details

Page properties
Content
... ... @@ -92,6 +92,7 @@
92 92  * Sewer
93 93  * Bottom water level monitoring
94 94  
95 +
95 95  == 1.6  Pin mapping and power on ==
96 96  
97 97  
... ... @@ -183,10 +183,11 @@
183 183  == 2.3  ​Uplink Payload ==
184 184  
185 185  (((
186 -LDDS75 will uplink payload via LoRaWAN with below payload format: 
187 +LLDS12 will uplink payload via LoRaWAN with below payload format: 
188 +)))
187 187  
188 -Uplink payload includes in total 4 bytes.
189 -Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
190 +(((
191 +Uplink payload includes in total 11 bytes.
190 190  )))
191 191  
192 192  (((
... ... @@ -196,23 +196,23 @@
196 196  (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
197 197  |=(% style="width: 62.5px;" %)(((
198 198  **Size (bytes)**
199 -)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
200 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
201 -[[Distance>>||anchor="H2.3.3A0Distance"]]
201 +)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
202 +|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
203 +[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
204 +)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
205 +[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
206 +)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
207 +[[Message Type>>||anchor="H2.3.7A0MessageType"]]
208 +)))
202 202  
203 -(unit: mm)
204 -)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
205 -[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
206 -)))|[[Sensor Flag>>path:#Sensor_Flag]]
210 +[[image:1654833689380-972.png]]
207 207  
208 -[[image:1654850511545-399.png]]
209 209  
210 210  
211 -
212 212  === 2.3.1  Battery Info ===
213 213  
214 214  
215 -Check the battery voltage for LDDS75.
217 +Check the battery voltage for LLDS12.
216 216  
217 217  Ex1: 0x0B45 = 2885mV
218 218  
... ... @@ -220,22 +220,49 @@
220 220  
221 221  
222 222  
223 -=== 2.3.2  Distance ===
225 +=== 2.3.2  DS18B20 Temperature sensor ===
224 224  
225 -Get the distance. Flat object range 280mm - 7500mm.
227 +This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
226 226  
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  
230 +**Example**:
229 229  
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 +If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
232 232  
234 +If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
233 233  
234 234  
235 -=== 2.3.3  Interrupt Pin ===
236 236  
238 +=== 2.3.3  Distance ===
239 +
240 +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.
241 +
242 +
243 +**Example**:
244 +
245 +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.
246 +
247 +
248 +
249 +=== 2.3.4  Distance signal strength ===
250 +
251 +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.
252 +
253 +
254 +**Example**:
255 +
256 +If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
257 +
258 +Customers can judge whether they need to adjust the environment based on the signal strength.
259 +
260 +
261 +
262 +=== 2.3.5  Interrupt Pin ===
263 +
237 237  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.
238 238  
266 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
267 +
239 239  **Example:**
240 240  
241 241  0x00: Normal uplink packet.
... ... @@ -243,44 +243,53 @@
243 243  0x01: Interrupt Uplink Packet.
244 244  
245 245  
246 -=== 2.3.4  DS18B20 Temperature sensor ===
247 247  
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 +=== 2.3.6  LiDAR temp ===
249 249  
250 -**Example**:
278 +Characterize the internal temperature value of the sensor.
251 251  
252 -If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
280 +**Example: **
281 +If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
282 +If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
253 253  
254 -If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
255 255  
256 -(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
257 257  
286 +=== 2.3.7  Message Type ===
258 258  
288 +(((
289 +For a normal uplink payload, the message type is always 0x01.
290 +)))
259 259  
260 -=== 2.3.5  Sensor Flag ===
292 +(((
293 +Valid Message Type:
294 +)))
261 261  
262 -0x01: Detect Ultrasonic Sensor
263 263  
264 -0x00: No Ultrasonic Sensor
297 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
298 +|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
299 +|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
300 +|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
265 265  
302 +=== 2.3.8  Decode payload in The Things Network ===
266 266  
267 -===
268 -(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
269 -
270 270  While using TTN network, you can add the payload format to decode the payload.
271 271  
272 272  
273 -[[image:1654850829385-439.png]]
307 +[[image:1654592762713-715.png]]
274 274  
275 -The payload decoder function for TTN V3 is here:
309 +(((
310 +The payload decoder function for TTN is here:
311 +)))
276 276  
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/]]
313 +(((
314 +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/]]
315 +)))
278 278  
279 279  
280 280  
281 281  == 2.4  Uplink Interval ==
282 282  
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 +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"]]
284 284  
285 285  
286 286  
... ... @@ -311,25 +311,47 @@
311 311  
312 312  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
313 313  
314 -(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
352 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
315 315  
316 -[[image:1654851029373-510.png]]
354 +[[image:1654832691989-514.png]]
317 317  
318 318  
319 -After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
357 +[[image:1654592833877-762.png]]
320 320  
321 -[[image:image-20220610165129-11.png||height="595" width="1088"]]
322 322  
360 +[[image:1654832740634-933.png]]
323 323  
324 324  
325 -== 2.6  Frequency Plans ==
326 326  
327 327  (((
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.
365 +(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
329 329  )))
330 330  
368 +(((
369 +
370 +)))
331 331  
372 +[[image:1654833065139-942.png]]
332 332  
374 +
375 +
376 +[[image:1654833092678-390.png]]
377 +
378 +
379 +
380 +After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
381 +
382 +[[image:1654833163048-332.png]]
383 +
384 +
385 +
386 +== 2.6  Frequency Plans ==
387 +
388 +(((
389 +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.
390 +)))
391 +
392 +
333 333  === 2.6.1  EU863-870 (EU868) ===
334 334  
335 335  (((
... ... @@ -393,51 +393,20 @@
393 393  === 2.6.2  US902-928(US915) ===
394 394  
395 395  (((
396 -Used in USA, Canada and South America. Default use CHE=2
456 +Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
457 +)))
397 397  
398 -(% style="color:blue" %)**Uplink:**
459 +(((
460 +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.
461 +)))
399 399  
400 -903.9 - SF7BW125 to SF10BW125
401 -
402 -904.1 - SF7BW125 to SF10BW125
403 -
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 -
463 +(((
464 +After Join success, the end node will switch to the correct sub band by:
439 439  )))
440 440  
467 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
468 +* 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)
469 +
441 441  === 2.6.3  CN470-510 (CN470) ===
442 442  
443 443  (((
... ... @@ -530,51 +530,24 @@
530 530  === 2.6.4  AU915-928(AU915) ===
531 531  
532 532  (((
533 -Default use CHE=2
562 +Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
563 +)))
534 534  
535 -(% style="color:blue" %)**Uplink:**
565 +(((
566 +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.
567 +)))
536 536  
537 -916.8 - SF7BW125 to SF12BW125
538 -
539 -917.0 - SF7BW125 to SF12BW125
540 -
541 -917.2 - SF7BW125 to SF12BW125
542 -
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 -
569 +(((
575 575  
576 576  )))
577 577  
573 +(((
574 +After Join success, the end node will switch to the correct sub band by:
575 +)))
576 +
577 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
578 +* 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)
579 +
578 578  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
579 579  
580 580  (((
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