Last modified by Mengting Qiu on 2024/03/07 08:41
<
From version < 137.3 >
edited by Xiaoling
on 2022/06/10 16:55
To version < 124.3 >
edited by Xiaoling
on 2022/06/10 16:00
>
Change comment: There is no comment for this version

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  
... ... @@ -57,6 +57,7 @@
57 57  * IP66 Waterproof Enclosure
58 58  * 4000mAh or 8500mAh Battery for long term use
59 59  
60 +
60 60  == 1.3  Specification ==
61 61  
62 62  === 1.3.1  Rated environmental conditions ===
... ... @@ -92,6 +92,8 @@
92 92  * Sewer
93 93  * Bottom water level monitoring
94 94  
96 +
97 +
95 95  == 1.6  Pin mapping and power on ==
96 96  
97 97  
... ... @@ -103,11 +103,11 @@
103 103  == 2.1  How it works ==
104 104  
105 105  (((
106 -The LDDS75 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LDDS75. If there is coverage of the LoRaWAN network, it will automatically join the network via OTAA and start to send the sensor value
109 +The LLDS12 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LLDS12. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.
107 107  )))
108 108  
109 109  (((
110 -In case you can't set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H3.A0ConfigureLDDS75viaATCommandorLoRaWANDownlink"]]to set the keys in the LDDS75.
113 +In case you can’t set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H6.A0UseATCommand"]]to set the keys in the LLDS12.
111 111  )))
112 112  
113 113  
... ... @@ -118,7 +118,7 @@
118 118  )))
119 119  
120 120  (((
121 -[[image:1654848616367-242.png]]
124 +[[image:1654827857527-556.png]]
122 122  )))
123 123  
124 124  (((
... ... @@ -126,57 +126,57 @@
126 126  )))
127 127  
128 128  (((
129 -(% 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.
130 130  )))
131 131  
132 132  (((
133 -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:
134 134  )))
135 135  
136 136  [[image:image-20220607170145-1.jpeg]]
137 137  
138 138  
139 -For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
140 140  
141 -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:
142 142  
143 -**Add APP EUI in the application**
144 144  
145 -[[image:image-20220610161353-4.png]]
146 +**Register the device**
146 146  
147 -[[image:image-20220610161353-5.png]]
148 148  
149 -[[image:image-20220610161353-6.png]]
149 +[[image:1654592600093-601.png]]
150 150  
151 151  
152 -[[image:image-20220610161353-7.png]]
153 153  
153 +**Add APP EUI and DEV EUI**
154 154  
155 -You can also choose to create the device manually.
155 +[[image:1654592619856-881.png]]
156 156  
157 - [[image:image-20220610161538-8.png]]
158 158  
159 159  
159 +**Add APP EUI in the application**
160 160  
161 -**Add APP KEY and DEV EUI**
161 +[[image:1654592632656-512.png]]
162 162  
163 -[[image:image-20220610161538-9.png]]
164 164  
165 165  
165 +**Add APP KEY**
166 166  
167 -(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
167 +[[image:1654592653453-934.png]]
168 168  
169 169  
170 +(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
171 +
172 +
170 170  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
171 171  
172 -[[image:image-20220610161724-10.png]]
175 +[[image:image-20220607170442-2.png]]
173 173  
174 174  
175 175  (((
176 -(% 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.
177 177  )))
178 178  
179 -[[image:1654849068701-275.png]]
182 +[[image:1654833501679-968.png]]
180 180  
181 181  
182 182  
... ... @@ -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: 
189 +LLDS12 will uplink payload via LoRaWAN with below payload format: 
190 +)))
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
192 +(((
193 +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"]]
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 +)))
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]]
212 +[[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.
219 +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 ===
227 +=== 2.3.2  DS18B20 Temperature sensor ===
224 224  
225 -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.
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  
232 +**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.
234 +If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
232 232  
236 +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  
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 +
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  
268 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
269 +
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.
278 +=== 2.3.6  LiDAR temp ===
249 249  
250 -**Example**:
280 +Characterize the internal temperature value of the sensor.
251 251  
252 -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℃.
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  
288 +=== 2.3.7  Message Type ===
258 258  
290 +(((
291 +For a normal uplink payload, the message type is always 0x01.
292 +)))
259 259  
260 -=== 2.3.5  Sensor Flag ===
294 +(((
295 +Valid Message Type:
296 +)))
261 261  
262 -0x01: Detect Ultrasonic Sensor
263 263  
264 -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"]]
265 265  
304 +=== 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]]
309 +[[image:1654592762713-715.png]]
274 274  
275 -The payload decoder function for TTN V3 is here:
311 +(((
312 +The payload decoder function for TTN is here:
313 +)))
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/]]
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 +)))
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"]]
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"]]
284 284  
285 285  
286 286  
... ... @@ -311,21 +311,44 @@
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.**
354 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
315 315  
316 -[[image:1654851029373-510.png]]
356 +[[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.
359 +[[image:1654592833877-762.png]]
320 320  
321 -[[image:image-20220610165129-11.png||height="595" width="1088"]]
322 322  
362 +[[image:1654832740634-933.png]]
323 323  
324 324  
365 +
366 +(((
367 +(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
368 +)))
369 +
370 +(((
371 +
372 +)))
373 +
374 +[[image:1654833065139-942.png]]
375 +
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 +
325 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.
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.
329 329  )))
330 330  
331 331  
... ... @@ -392,51 +392,20 @@
392 392  === 2.6.2  US902-928(US915) ===
393 393  
394 394  (((
395 -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 +)))
396 396  
397 -(% 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 +)))
398 398  
399 -903.9 - SF7BW125 to SF10BW125
400 -
401 -904.1 - SF7BW125 to SF10BW125
402 -
403 -904.3 - SF7BW125 to SF10BW125
404 -
405 -904.5 - SF7BW125 to SF10BW125
406 -
407 -904.7 - SF7BW125 to SF10BW125
408 -
409 -904.9 - SF7BW125 to SF10BW125
410 -
411 -905.1 - SF7BW125 to SF10BW125
412 -
413 -905.3 - SF7BW125 to SF10BW125
414 -
415 -
416 -(% style="color:blue" %)**Downlink:**
417 -
418 -923.3 - SF7BW500 to SF12BW500
419 -
420 -923.9 - SF7BW500 to SF12BW500
421 -
422 -924.5 - SF7BW500 to SF12BW500
423 -
424 -925.1 - SF7BW500 to SF12BW500
425 -
426 -925.7 - SF7BW500 to SF12BW500
427 -
428 -926.3 - SF7BW500 to SF12BW500
429 -
430 -926.9 - SF7BW500 to SF12BW500
431 -
432 -927.5 - SF7BW500 to SF12BW500
433 -
434 -923.3 - SF12BW500(RX2 downlink only)
435 -
436 -
437 -
465 +(((
466 +After Join success, the end node will switch to the correct sub band by:
438 438  )))
439 439  
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 +
440 440  === 2.6.3  CN470-510 (CN470) ===
441 441  
442 442  (((
... ... @@ -1248,6 +1248,7 @@
1248 1248  * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1249 1249  * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1250 1250  
1283 +
1251 1251  = 10. ​ Packing Info =
1252 1252  
1253 1253  
... ... @@ -1262,6 +1262,7 @@
1262 1262  * Package Size / pcs : cm
1263 1263  * Weight / pcs : g
1264 1264  
1298 +
1265 1265  = 11.  ​Support =
1266 1266  
1267 1267  * 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.
1654848616367-242.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.8 KB
Content
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