Last modified by Mengting Qiu on 2024/03/07 08:41
<
From version < 138.2 >
edited by Xiaoling
on 2022/06/10 17:03
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,8 +58,6 @@
58 58  * 4000mAh or 8500mAh Battery for long term use
59 59  
60 60  
61 -
62 -
63 63  == 1.3  Specification ==
64 64  
65 65  === 1.3.1  Rated environmental conditions ===
... ... @@ -95,6 +95,8 @@
95 95  * Sewer
96 96  * Bottom water level monitoring
97 97  
96 +
97 +
98 98  == 1.6  Pin mapping and power on ==
99 99  
100 100  
... ... @@ -121,7 +121,7 @@
121 121  )))
122 122  
123 123  (((
124 -[[image:1654848616367-242.png]]
124 +[[image:1654827857527-556.png]]
125 125  )))
126 126  
127 127  (((
... ... @@ -129,57 +129,57 @@
129 129  )))
130 130  
131 131  (((
132 -(% 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.
133 133  )))
134 134  
135 135  (((
136 -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:
137 137  )))
138 138  
139 139  [[image:image-20220607170145-1.jpeg]]
140 140  
141 141  
142 -For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
143 143  
144 -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:
145 145  
146 -**Add APP EUI in the application**
147 147  
148 -[[image:image-20220610161353-4.png]]
146 +**Register the device**
149 149  
150 -[[image:image-20220610161353-5.png]]
151 151  
152 -[[image:image-20220610161353-6.png]]
149 +[[image:1654592600093-601.png]]
153 153  
154 154  
155 -[[image:image-20220610161353-7.png]]
156 156  
153 +**Add APP EUI and DEV EUI**
157 157  
158 -You can also choose to create the device manually.
155 +[[image:1654592619856-881.png]]
159 159  
160 - [[image:image-20220610161538-8.png]]
161 161  
162 162  
159 +**Add APP EUI in the application**
163 163  
164 -**Add APP KEY and DEV EUI**
161 +[[image:1654592632656-512.png]]
165 165  
166 -[[image:image-20220610161538-9.png]]
167 167  
168 168  
165 +**Add APP KEY**
169 169  
170 -(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
167 +[[image:1654592653453-934.png]]
171 171  
172 172  
170 +(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
171 +
172 +
173 173  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
174 174  
175 -[[image:image-20220610161724-10.png]]
175 +[[image:image-20220607170442-2.png]]
176 176  
177 177  
178 178  (((
179 -(% 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.
180 180  )))
181 181  
182 -[[image:1654849068701-275.png]]
182 +[[image:1654833501679-968.png]]
183 183  
184 184  
185 185  
... ... @@ -186,10 +186,11 @@
186 186  == 2.3  ​Uplink Payload ==
187 187  
188 188  (((
189 -LDDS75 will uplink payload via LoRaWAN with below payload format: 
189 +LLDS12 will uplink payload via LoRaWAN with below payload format: 
190 +)))
190 190  
191 -Uplink payload includes in total 4 bytes.
192 -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.
193 193  )))
194 194  
195 195  (((
... ... @@ -199,23 +199,23 @@
199 199  (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
200 200  |=(% style="width: 62.5px;" %)(((
201 201  **Size (bytes)**
202 -)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
203 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
204 -[[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 +)))
205 205  
206 -(unit: mm)
207 -)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
208 -[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
209 -)))|[[Sensor Flag>>path:#Sensor_Flag]]
212 +[[image:1654833689380-972.png]]
210 210  
211 -[[image:1654850511545-399.png]]
212 212  
213 213  
214 -
215 215  === 2.3.1  Battery Info ===
216 216  
217 217  
218 -Check the battery voltage for LDDS75.
219 +Check the battery voltage for LLDS12.
219 219  
220 220  Ex1: 0x0B45 = 2885mV
221 221  
... ... @@ -223,21 +223,49 @@
223 223  
224 224  
225 225  
226 -=== 2.3.2  Distance ===
227 +=== 2.3.2  DS18B20 Temperature sensor ===
227 227  
228 -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.
229 229  
230 -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.**
231 231  
232 +**Example**:
232 232  
233 -* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
234 -* 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
235 235  
236 +If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
236 236  
237 -=== 2.3.3  Interrupt Pin ===
238 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 +
239 239  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.
240 240  
268 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
269 +
241 241  **Example:**
242 242  
243 243  0x00: Normal uplink packet.
... ... @@ -245,44 +245,53 @@
245 245  0x01: Interrupt Uplink Packet.
246 246  
247 247  
248 -=== 2.3.4  DS18B20 Temperature sensor ===
249 249  
250 -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 ===
251 251  
252 -**Example**:
280 +Characterize the internal temperature value of the sensor.
253 253  
254 -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℃.
255 255  
256 -If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
257 257  
258 -(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
259 259  
288 +=== 2.3.7  Message Type ===
260 260  
290 +(((
291 +For a normal uplink payload, the message type is always 0x01.
292 +)))
261 261  
262 -=== 2.3.5  Sensor Flag ===
294 +(((
295 +Valid Message Type:
296 +)))
263 263  
264 -0x01: Detect Ultrasonic Sensor
265 265  
266 -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"]]
267 267  
304 +=== 2.3.8  Decode payload in The Things Network ===
268 268  
269 -===
270 -(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
271 -
272 272  While using TTN network, you can add the payload format to decode the payload.
273 273  
274 274  
275 -[[image:1654850829385-439.png]]
309 +[[image:1654592762713-715.png]]
276 276  
277 -The payload decoder function for TTN V3 is here:
311 +(((
312 +The payload decoder function for TTN is here:
313 +)))
278 278  
279 -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 +)))
280 280  
281 281  
282 282  
283 283  == 2.4  Uplink Interval ==
284 284  
285 -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"]]
286 286  
287 287  
288 288  
... ... @@ -313,25 +313,47 @@
313 313  
314 314  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
315 315  
316 -(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
354 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
317 317  
318 -[[image:1654851029373-510.png]]
356 +[[image:1654832691989-514.png]]
319 319  
320 320  
321 -After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
359 +[[image:1654592833877-762.png]]
322 322  
323 -[[image:image-20220610165129-11.png||height="595" width="1088"]]
324 324  
362 +[[image:1654832740634-933.png]]
325 325  
326 326  
327 -== 2.6  Frequency Plans ==
328 328  
329 329  (((
330 -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**
331 331  )))
332 332  
370 +(((
371 +
372 +)))
333 333  
374 +[[image:1654833065139-942.png]]
334 334  
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 +
335 335  === 2.6.1  EU863-870 (EU868) ===
336 336  
337 337  (((
... ... @@ -395,51 +395,20 @@
395 395  === 2.6.2  US902-928(US915) ===
396 396  
397 397  (((
398 -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 +)))
399 399  
400 -(% 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 +)))
401 401  
402 -903.9 - SF7BW125 to SF10BW125
403 -
404 -904.1 - SF7BW125 to SF10BW125
405 -
406 -904.3 - SF7BW125 to SF10BW125
407 -
408 -904.5 - SF7BW125 to SF10BW125
409 -
410 -904.7 - SF7BW125 to SF10BW125
411 -
412 -904.9 - SF7BW125 to SF10BW125
413 -
414 -905.1 - SF7BW125 to SF10BW125
415 -
416 -905.3 - SF7BW125 to SF10BW125
417 -
418 -
419 -(% style="color:blue" %)**Downlink:**
420 -
421 -923.3 - SF7BW500 to SF12BW500
422 -
423 -923.9 - SF7BW500 to SF12BW500
424 -
425 -924.5 - SF7BW500 to SF12BW500
426 -
427 -925.1 - SF7BW500 to SF12BW500
428 -
429 -925.7 - SF7BW500 to SF12BW500
430 -
431 -926.3 - SF7BW500 to SF12BW500
432 -
433 -926.9 - SF7BW500 to SF12BW500
434 -
435 -927.5 - SF7BW500 to SF12BW500
436 -
437 -923.3 - SF12BW500(RX2 downlink only)
438 -
439 -
440 -
465 +(((
466 +After Join success, the end node will switch to the correct sub band by:
441 441  )))
442 442  
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 +
443 443  === 2.6.3  CN470-510 (CN470) ===
444 444  
445 445  (((
... ... @@ -532,51 +532,24 @@
532 532  === 2.6.4  AU915-928(AU915) ===
533 533  
534 534  (((
535 -Default use CHE=2
564 +Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
565 +)))
536 536  
537 -(% 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 +)))
538 538  
539 -916.8 - SF7BW125 to SF12BW125
540 -
541 -917.0 - SF7BW125 to SF12BW125
542 -
543 -917.2 - SF7BW125 to SF12BW125
544 -
545 -917.4 - SF7BW125 to SF12BW125
546 -
547 -917.6 - SF7BW125 to SF12BW125
548 -
549 -917.8 - SF7BW125 to SF12BW125
550 -
551 -918.0 - SF7BW125 to SF12BW125
552 -
553 -918.2 - SF7BW125 to SF12BW125
554 -
555 -
556 -(% style="color:blue" %)**Downlink:**
557 -
558 -923.3 - SF7BW500 to SF12BW500
559 -
560 -923.9 - SF7BW500 to SF12BW500
561 -
562 -924.5 - SF7BW500 to SF12BW500
563 -
564 -925.1 - SF7BW500 to SF12BW500
565 -
566 -925.7 - SF7BW500 to SF12BW500
567 -
568 -926.3 - SF7BW500 to SF12BW500
569 -
570 -926.9 - SF7BW500 to SF12BW500
571 -
572 -927.5 - SF7BW500 to SF12BW500
573 -
574 -923.3 - SF12BW500(RX2 downlink only)
575 -
576 -
571 +(((
577 577  
578 578  )))
579 579  
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 +
580 580  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
581 581  
582 582  (((
... ... @@ -1278,6 +1278,7 @@
1278 1278  * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1279 1279  * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1280 1280  
1283 +
1281 1281  = 10. ​ Packing Info =
1282 1282  
1283 1283  
... ... @@ -1292,6 +1292,7 @@
1292 1292  * Package Size / pcs : cm
1293 1293  * Weight / pcs : g
1294 1294  
1298 +
1295 1295  = 11.  ​Support =
1296 1296  
1297 1297  * 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