Last modified by Mengting Qiu on 2025/02/26 15:04
<
From version < 138.5 >
edited by Xiaoling
on 2022/06/10 17:04
To version < 125.1 >
edited by Xiaoling
on 2022/06/10 16:10
>
Change comment: Uploaded new attachment "1654848616367-242.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -33,7 +33,7 @@
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  
... ... @@ -58,7 +58,6 @@
58 58  * 4000mAh or 8500mAh Battery for long term use
59 59  
60 60  
61 -
62 62  == 1.3  Specification ==
63 63  
64 64  === 1.3.1  Rated environmental conditions ===
... ... @@ -82,7 +82,6 @@
82 82  (% style="display:none" %) (%%)
83 83  
84 84  
85 -
86 86  == 1.5 ​ Applications ==
87 87  
88 88  * Horizontal distance measurement
... ... @@ -103,7 +103,6 @@
103 103  [[image:1654847583902-256.png]]
104 104  
105 105  
106 -
107 107  = 2.  Configure LDDS75 to connect to LoRaWAN network =
108 108  
109 109  == 2.1  How it works ==
... ... @@ -117,7 +117,6 @@
117 117  )))
118 118  
119 119  
120 -
121 121  == 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
122 122  
123 123  (((
... ... @@ -125,7 +125,7 @@
125 125  )))
126 126  
127 127  (((
128 -[[image:1654848616367-242.png]]
124 +[[image:1654827857527-556.png]]
129 129  )))
130 130  
131 131  (((
... ... @@ -133,57 +133,57 @@
133 133  )))
134 134  
135 135  (((
136 -(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS75.
132 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSPH01.
137 137  )))
138 138  
139 139  (((
140 -Each LDDS75 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
136 +Each LSPH01 is shipped with a sticker with the default device EUI as below:
141 141  )))
142 142  
143 143  [[image:image-20220607170145-1.jpeg]]
144 144  
145 145  
146 -For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
147 147  
148 -Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
143 +You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
149 149  
150 -**Add APP EUI in the application**
151 151  
152 -[[image:image-20220610161353-4.png]]
146 +**Register the device**
153 153  
154 -[[image:image-20220610161353-5.png]]
155 155  
156 -[[image:image-20220610161353-6.png]]
149 +[[image:1654592600093-601.png]]
157 157  
158 158  
159 -[[image:image-20220610161353-7.png]]
160 160  
153 +**Add APP EUI and DEV EUI**
161 161  
162 -You can also choose to create the device manually.
155 +[[image:1654592619856-881.png]]
163 163  
164 - [[image:image-20220610161538-8.png]]
165 165  
166 166  
159 +**Add APP EUI in the application**
167 167  
168 -**Add APP KEY and DEV EUI**
161 +[[image:1654592632656-512.png]]
169 169  
170 -[[image:image-20220610161538-9.png]]
171 171  
172 172  
165 +**Add APP KEY**
173 173  
174 -(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
167 +[[image:1654592653453-934.png]]
175 175  
176 176  
170 +(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
171 +
172 +
177 177  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
178 178  
179 -[[image:image-20220610161724-10.png]]
175 +[[image:image-20220607170442-2.png]]
180 180  
181 181  
182 182  (((
183 -(% 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.
179 +(% 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.
184 184  )))
185 185  
186 -[[image:1654849068701-275.png]]
182 +[[image:1654833501679-968.png]]
187 187  
188 188  
189 189  
... ... @@ -190,10 +190,11 @@
190 190  == 2.3  ​Uplink Payload ==
191 191  
192 192  (((
193 -LDDS75 will uplink payload via LoRaWAN with below payload format: 
189 +LLDS12 will uplink payload via LoRaWAN with below payload format: 
190 +)))
194 194  
195 -Uplink payload includes in total 4 bytes.
196 -Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
192 +(((
193 +Uplink payload includes in total 11 bytes.
197 197  )))
198 198  
199 199  (((
... ... @@ -203,23 +203,23 @@
203 203  (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
204 204  |=(% style="width: 62.5px;" %)(((
205 205  **Size (bytes)**
206 -)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
207 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
208 -[[Distance>>||anchor="H2.3.3A0Distance"]]
203 +)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
204 +|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
205 +[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
206 +)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
207 +[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
208 +)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
209 +[[Message Type>>||anchor="H2.3.7A0MessageType"]]
210 +)))
209 209  
210 -(unit: mm)
211 -)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
212 -[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
213 -)))|[[Sensor Flag>>path:#Sensor_Flag]]
212 +[[image:1654833689380-972.png]]
214 214  
215 -[[image:1654850511545-399.png]]
216 216  
217 217  
218 -
219 219  === 2.3.1  Battery Info ===
220 220  
221 221  
222 -Check the battery voltage for LDDS75.
219 +Check the battery voltage for LLDS12.
223 223  
224 224  Ex1: 0x0B45 = 2885mV
225 225  
... ... @@ -227,20 +227,49 @@
227 227  
228 228  
229 229  
230 -=== 2.3.2  Distance ===
227 +=== 2.3.2  DS18B20 Temperature sensor ===
231 231  
232 -Get the distance. Flat object range 280mm - 7500mm.
229 +This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
233 233  
234 -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.**
235 235  
232 +**Example**:
236 236  
237 -* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
238 -* 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.
234 +If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
239 239  
240 -=== 2.3.3  Interrupt Pin ===
236 +If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
241 241  
238 +
239 +
240 +=== 2.3.3  Distance ===
241 +
242 +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.
243 +
244 +
245 +**Example**:
246 +
247 +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.
248 +
249 +
250 +
251 +=== 2.3.4  Distance signal strength ===
252 +
253 +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.
254 +
255 +
256 +**Example**:
257 +
258 +If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
259 +
260 +Customers can judge whether they need to adjust the environment based on the signal strength.
261 +
262 +
263 +
264 +=== 2.3.5  Interrupt Pin ===
265 +
242 242  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.
243 243  
268 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
269 +
244 244  **Example:**
245 245  
246 246  0x00: Normal uplink packet.
... ... @@ -248,44 +248,53 @@
248 248  0x01: Interrupt Uplink Packet.
249 249  
250 250  
251 -=== 2.3.4  DS18B20 Temperature sensor ===
252 252  
253 -This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
278 +=== 2.3.6  LiDAR temp ===
254 254  
255 -**Example**:
280 +Characterize the internal temperature value of the sensor.
256 256  
257 -If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
282 +**Example: **
283 +If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
284 +If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
258 258  
259 -If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
260 260  
261 -(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
262 262  
288 +=== 2.3.7  Message Type ===
263 263  
290 +(((
291 +For a normal uplink payload, the message type is always 0x01.
292 +)))
264 264  
265 -=== 2.3.5  Sensor Flag ===
294 +(((
295 +Valid Message Type:
296 +)))
266 266  
267 -0x01: Detect Ultrasonic Sensor
268 268  
269 -0x00: No Ultrasonic Sensor
299 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
300 +|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
301 +|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
302 +|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
270 270  
304 +=== 2.3.8  Decode payload in The Things Network ===
271 271  
272 -===
273 -(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
274 -
275 275  While using TTN network, you can add the payload format to decode the payload.
276 276  
277 277  
278 -[[image:1654850829385-439.png]]
309 +[[image:1654592762713-715.png]]
279 279  
280 -The payload decoder function for TTN V3 is here:
311 +(((
312 +The payload decoder function for TTN is here:
313 +)))
281 281  
282 -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 +(((
316 +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/]]
317 +)))
283 283  
284 284  
285 285  
286 286  == 2.4  Uplink Interval ==
287 287  
288 -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"]]
323 +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"]]
289 289  
290 290  
291 291  
... ... @@ -316,25 +316,47 @@
316 316  
317 317  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
318 318  
319 -(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
354 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
320 320  
321 -[[image:1654851029373-510.png]]
356 +[[image:1654832691989-514.png]]
322 322  
323 323  
324 -After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
359 +[[image:1654592833877-762.png]]
325 325  
326 -[[image:image-20220610165129-11.png||height="595" width="1088"]]
327 327  
362 +[[image:1654832740634-933.png]]
328 328  
329 329  
330 -== 2.6  Frequency Plans ==
331 331  
332 332  (((
333 -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.
367 +(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
334 334  )))
335 335  
370 +(((
371 +
372 +)))
336 336  
374 +[[image:1654833065139-942.png]]
337 337  
376 +
377 +
378 +[[image:1654833092678-390.png]]
379 +
380 +
381 +
382 +After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
383 +
384 +[[image:1654833163048-332.png]]
385 +
386 +
387 +
388 +== 2.6  Frequency Plans ==
389 +
390 +(((
391 +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.
392 +)))
393 +
394 +
338 338  === 2.6.1  EU863-870 (EU868) ===
339 339  
340 340  (((
... ... @@ -398,51 +398,20 @@
398 398  === 2.6.2  US902-928(US915) ===
399 399  
400 400  (((
401 -Used in USA, Canada and South America. Default use CHE=2
458 +Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
459 +)))
402 402  
403 -(% style="color:blue" %)**Uplink:**
461 +(((
462 +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.
463 +)))
404 404  
405 -903.9 - SF7BW125 to SF10BW125
406 -
407 -904.1 - SF7BW125 to SF10BW125
408 -
409 -904.3 - SF7BW125 to SF10BW125
410 -
411 -904.5 - SF7BW125 to SF10BW125
412 -
413 -904.7 - SF7BW125 to SF10BW125
414 -
415 -904.9 - SF7BW125 to SF10BW125
416 -
417 -905.1 - SF7BW125 to SF10BW125
418 -
419 -905.3 - SF7BW125 to SF10BW125
420 -
421 -
422 -(% style="color:blue" %)**Downlink:**
423 -
424 -923.3 - SF7BW500 to SF12BW500
425 -
426 -923.9 - SF7BW500 to SF12BW500
427 -
428 -924.5 - SF7BW500 to SF12BW500
429 -
430 -925.1 - SF7BW500 to SF12BW500
431 -
432 -925.7 - SF7BW500 to SF12BW500
433 -
434 -926.3 - SF7BW500 to SF12BW500
435 -
436 -926.9 - SF7BW500 to SF12BW500
437 -
438 -927.5 - SF7BW500 to SF12BW500
439 -
440 -923.3 - SF12BW500(RX2 downlink only)
441 -
442 -
443 -
465 +(((
466 +After Join success, the end node will switch to the correct sub band by:
444 444  )))
445 445  
469 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
470 +* 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)
471 +
446 446  === 2.6.3  CN470-510 (CN470) ===
447 447  
448 448  (((
... ... @@ -535,51 +535,24 @@
535 535  === 2.6.4  AU915-928(AU915) ===
536 536  
537 537  (((
538 -Default use CHE=2
564 +Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
565 +)))
539 539  
540 -(% style="color:blue" %)**Uplink:**
567 +(((
568 +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.
569 +)))
541 541  
542 -916.8 - SF7BW125 to SF12BW125
543 -
544 -917.0 - SF7BW125 to SF12BW125
545 -
546 -917.2 - SF7BW125 to SF12BW125
547 -
548 -917.4 - SF7BW125 to SF12BW125
549 -
550 -917.6 - SF7BW125 to SF12BW125
551 -
552 -917.8 - SF7BW125 to SF12BW125
553 -
554 -918.0 - SF7BW125 to SF12BW125
555 -
556 -918.2 - SF7BW125 to SF12BW125
557 -
558 -
559 -(% style="color:blue" %)**Downlink:**
560 -
561 -923.3 - SF7BW500 to SF12BW500
562 -
563 -923.9 - SF7BW500 to SF12BW500
564 -
565 -924.5 - SF7BW500 to SF12BW500
566 -
567 -925.1 - SF7BW500 to SF12BW500
568 -
569 -925.7 - SF7BW500 to SF12BW500
570 -
571 -926.3 - SF7BW500 to SF12BW500
572 -
573 -926.9 - SF7BW500 to SF12BW500
574 -
575 -927.5 - SF7BW500 to SF12BW500
576 -
577 -923.3 - SF12BW500(RX2 downlink only)
578 -
579 -
571 +(((
580 580  
581 581  )))
582 582  
575 +(((
576 +After Join success, the end node will switch to the correct sub band by:
577 +)))
578 +
579 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
580 +* 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)
581 +
583 583  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
584 584  
585 585  (((
... ... @@ -1281,6 +1281,7 @@
1281 1281  * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1282 1282  * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1283 1283  
1283 +
1284 1284  = 10. ​ Packing Info =
1285 1285  
1286 1286  
... ... @@ -1295,6 +1295,7 @@
1295 1295  * Package Size / pcs : cm
1296 1296  * Weight / pcs : g
1297 1297  
1298 +
1298 1298  = 11.  ​Support =
1299 1299  
1300 1300  * 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.
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
image-20220610161353-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -32.2 KB
Content
image-20220610161353-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -42.7 KB
Content
image-20220610161353-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.3 KB
Content
image-20220610161353-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.1 KB
Content
image-20220610161538-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.2 KB
Content
image-20220610161538-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -28.7 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