Last modified by Mengting Qiu on 2024/03/07 08:41
<
From version < 116.1 >
edited by Xiaoling
on 2022/06/10 15:14
To version < 138.8 >
edited by Xiaoling
on 2022/06/10 17:07
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -LLDS12-LoRaWAN LiDAR ToF Distance Sensor User Manual
1 +LDDS75 - LoRaWAN Distance Detection Sensor User Manual
Content
... ... @@ -1,10 +1,8 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20220610095606-1.png]]
2 +[[image:1654846127817-788.png]]
3 3  
4 -
5 5  **Contents:**
6 6  
7 -{{toc/}}
8 8  
9 9  
10 10  
... ... @@ -14,38 +14,33 @@
14 14  
15 15  = 1.  Introduction =
16 16  
17 -== 1.1 ​ What is LoRaWAN LiDAR ToF Distance Sensor ==
15 +== 1.1 ​ What is LoRaWAN Distance Detection Sensor ==
18 18  
19 19  (((
20 20  
21 21  
22 22  (((
23 -The Dragino LLDS12 is a (% style="color:blue" %)**LoRaWAN LiDAR ToF (Time of Flight) Distance Sensor**(%%) for Internet of Things solution. It is capable to measure the distance to an object as close as 10 centimeters (+/- 5cm up to 6m) and as far as 12 meters (+/-1% starting at 6m)!. The LiDAR probe uses laser induction technology for distance measurement.
24 -)))
21 +The Dragino LDDS75 is a (% style="color:#4472c4" %)** LoRaWAN Distance Detection Sensor**(%%) for Internet of Things solution. It is used to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses (% style="color:#4472c4" %)** ultrasonic sensing** (%%)technology for distance measurement, and (% style="color:#4472c4" %)** temperature compensation**(%%) is performed internally to improve the reliability of data. The LDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc.
25 25  
26 -(((
27 -The LLDS12 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
28 -)))
29 29  
30 -(((
31 -It detects the distance between the measured object and the sensor, and uploads the value via wireless to LoRaWAN IoT Server.
32 -)))
24 +It detects the distance** (% style="color:#4472c4" %) between the measured object and the sensor(%%)**, and uploads the value via wireless to LoRaWAN IoT Server.
33 33  
34 -(((
35 -The LoRa wireless technology used in LLDS12 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.
36 -)))
37 37  
38 -(((
39 -LLDS12 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years.
40 -)))
27 +The LoRa wireless technology used in LDDS75 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.
41 41  
42 -(((
43 -Each LLDS12 is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on.
29 +
30 +LDDS75 is powered by (% style="color:#4472c4" %)** 4000mA or 8500mAh Li-SOCI2 battery**(%%); It is designed for long term use up to 10 years*.
31 +
32 +
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 +
35 +
36 +(% style="color:#4472c4" %) * (%%)Actually lifetime depends on network coverage and uplink interval and other factors
44 44  )))
45 45  )))
46 46  
47 47  
48 -[[image:1654826306458-414.png]]
41 +[[image:1654847051249-359.png]]
49 49  
50 50  
51 51  
... ... @@ -52,43 +52,54 @@
52 52  == ​1.2  Features ==
53 53  
54 54  * LoRaWAN 1.0.3 Class A
55 -* Ultra-low power consumption
56 -* Laser technology for distance detection
57 -* Operating Range - 0.1m~~12m①
58 -* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
59 -* Monitor Battery Level
48 +* Ultra low power consumption
49 +* Distance Detection by Ultrasonic technology
50 +* Flat object range 280mm - 7500mm
51 +* Accuracy: ±(1cm+S*0.3%) (S: Distance)
52 +* Cable Length : 25cm
60 60  * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
61 61  * AT Commands to change parameters
62 62  * Uplink on periodically
63 63  * Downlink to change configure
64 -* 8500mAh Battery for long term use
57 +* IP66 Waterproof Enclosure
58 +* 4000mAh or 8500mAh Battery for long term use
65 65  
66 66  
67 -== 1.3  Probe Specification ==
61 +== 1.3  Specification ==
68 68  
69 -* Storage temperature ：-20℃~~75℃
70 -* Operating temperature - -20℃~~60℃
71 -* Operating Range - 0.1m~~12m①
72 -* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
73 -* Distance resolution - 5mm
74 -* Ambient light immunity - 70klux
75 -* Enclosure rating - IP65
76 -* Light source - LED
77 -* Central wavelength - 850nm
78 -* FOV - 3.6°
79 -* Material of enclosure - ABS+PC
80 -* Wire length - 25cm
63 +=== 1.3.1  Rated environmental conditions ===
81 81  
65 +[[image:image-20220610154839-1.png]]
82 82  
83 -== 1.4  Probe Dimension ==
67 +**Remarks: (1) a. When the ambient temperature is 0-39 ℃, the maximum humidity is 90% (non-condensing);**
84 84  
69 +**b. When the ambient temperature is 40-50 ℃, the highest humidity is the highest humidity in the natural world at the current temperature (no condensation)**
85 85  
86 -[[image:1654827224480-952.png]]
87 87  
88 88  
73 +=== 1.3.2  Effective measurement range Reference beam pattern ===
74 +
75 +**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**
76 +
77 +
78 +[[image:image-20220610155021-2.png||height="377" width="1021"]]
79 +
80 +
81 +
82 +**(2)** **The object to be tested is a "corrugated cardboard box" perpendicular to the central axis of 0 °, and the length * width is 60cm * 50cm.**
83 +
84 +(% style="display:none" %) (%%)
85 +
86 +(% style="display:none" %)** **[[image:image-20220610155021-3.png||height="374" width="1020"]]
87 +
88 +(% style="display:none" %) (%%)
89 +
90 +
91 +
89 89  == 1.5 ​ Applications ==
90 90  
91 91  * Horizontal distance measurement
95 +* Liquid level measurement
92 92  * Parking management system
93 93  * Object proximity and presence detection
94 94  * Intelligent trash can management system
... ... @@ -95,27 +95,30 @@
95 95  * Robot obstacle avoidance
96 96  * Automatic control
97 97  * Sewer
102 +* Bottom water level monitoring
98 98  
99 99  
100 100  == 1.6  Pin mapping and power on ==
101 101  
102 102  
103 -[[image:1654827332142-133.png]]
108 +[[image:1654847583902-256.png]]
104 104  
105 105  
106 -= 2.  Configure LLDS12 to connect to LoRaWAN network =
107 107  
112 += 2.  Configure LDDS75 to connect to LoRaWAN network =
113 +
108 108  == 2.1  How it works ==
109 109  
110 110  (((
111 -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.
117 +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
112 112  )))
113 113  
114 114  (((
115 -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.
121 +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.
116 116  )))
117 117  
118 118  
125 +
119 119  == 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
120 120  
121 121  (((
... ... @@ -123,7 +123,7 @@
123 123  )))
124 124  
125 125  (((
126 -[[image:1654827857527-556.png]]
133 +[[image:1654848616367-242.png]]
127 127  )))
128 128  
129 129  (((
... ... @@ -131,57 +131,57 @@
131 131  )))
132 132  
133 133  (((
134 -(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSPH01.
141 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS75.
135 135  )))
136 136  
137 137  (((
138 -Each LSPH01 is shipped with a sticker with the default device EUI as below:
145 +Each LDDS75 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
139 139  )))
140 140  
141 141  [[image:image-20220607170145-1.jpeg]]
142 142  
143 143  
151 +For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
144 144  
145 -You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
153 +Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
146 146  
155 +**Add APP EUI in the application**
147 147  
148 -**Register the device**
157 +[[image:image-20220610161353-4.png]]
149 149  
159 +[[image:image-20220610161353-5.png]]
150 150  
151 -[[image:1654592600093-601.png]]
161 +[[image:image-20220610161353-6.png]]
152 152  
153 153  
164 +[[image:image-20220610161353-7.png]]
154 154  
155 -**Add APP EUI and DEV EUI**
156 156  
157 -[[image:1654592619856-881.png]]
167 +You can also choose to create the device manually.
158 158  
169 + [[image:image-20220610161538-8.png]]
159 159  
160 160  
161 -**Add APP EUI in the application**
162 162  
163 -[[image:1654592632656-512.png]]
173 +**Add APP KEY and DEV EUI**
164 164  
175 +[[image:image-20220610161538-9.png]]
165 165  
166 166  
167 -**Add APP KEY**
168 168  
169 -[[image:1654592653453-934.png]]
179 +(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
170 170  
171 171  
172 -(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
173 -
174 -
175 175  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
176 176  
177 -[[image:image-20220607170442-2.png]]
184 +[[image:image-20220610161724-10.png]]
178 178  
179 179  
180 180  (((
181 -(% 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.
188 +(% 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.
182 182  )))
183 183  
184 -[[image:1654833501679-968.png]]
191 +[[image:1654849068701-275.png]]
185 185  
186 186  
187 187  
... ... @@ -188,11 +188,10 @@
188 188  == 2.3  ​Uplink Payload ==
189 189  
190 190  (((
191 -LLDS12 will uplink payload via LoRaWAN with below payload format: 
192 -)))
198 +LDDS75 will uplink payload via LoRaWAN with below payload format: 
193 193  
194 -(((
195 -Uplink payload includes in total 11 bytes.
200 +Uplink payload includes in total 4 bytes.
201 +Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
196 196  )))
197 197  
198 198  (((
... ... @@ -202,23 +202,23 @@
202 202  (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
203 203  |=(% style="width: 62.5px;" %)(((
204 204  **Size (bytes)**
205 -)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
206 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
207 -[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
208 -)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
209 -[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
210 -)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
211 -[[Message Type>>||anchor="H2.3.7A0MessageType"]]
212 -)))
211 +)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
212 +|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
213 +[[Distance>>||anchor="H2.3.3A0Distance"]]
213 213  
214 -[[image:1654833689380-972.png]]
215 +(unit: mm)
216 +)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
217 +[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
218 +)))|[[Sensor Flag>>path:#Sensor_Flag]]
215 215  
220 +[[image:1654850511545-399.png]]
216 216  
217 217  
223 +
218 218  === 2.3.1  Battery Info ===
219 219  
220 220  
221 -Check the battery voltage for LLDS12.
227 +Check the battery voltage for LDDS75.
222 222  
223 223  Ex1: 0x0B45 = 2885mV
224 224  
... ... @@ -226,49 +226,22 @@
226 226  
227 227  
228 228  
229 -=== 2.3.2  DS18B20 Temperature sensor ===
235 +=== 2.3.2  Distance ===
230 230  
231 -This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
237 +Get the distance. Flat object range 280mm - 7500mm.
232 232  
239 +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.**
233 233  
234 -**Example**:
235 235  
236 -If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
242 +* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
243 +* 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.
237 237  
238 -If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
239 239  
240 240  
247 +=== 2.3.3  Interrupt Pin ===
241 241  
242 -=== 2.3.3  Distance ===
243 -
244 -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.
245 -
246 -
247 -**Example**:
248 -
249 -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.
250 -
251 -
252 -
253 -=== 2.3.4  Distance signal strength ===
254 -
255 -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.
256 -
257 -
258 -**Example**:
259 -
260 -If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
261 -
262 -Customers can judge whether they need to adjust the environment based on the signal strength.
263 -
264 -
265 -
266 -=== 2.3.5  Interrupt Pin ===
267 -
268 268  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.
269 269  
270 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
271 -
272 272  **Example:**
273 273  
274 274  0x00: Normal uplink packet.
... ... @@ -277,53 +277,44 @@
277 277  
278 278  
279 279  
280 -=== 2.3.6  LiDAR temp ===
259 +=== 2.3.4  DS18B20 Temperature sensor ===
281 281  
282 -Characterize the internal temperature value of the sensor.
261 +This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
283 283  
284 -**Example: **
285 -If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
286 -If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
263 +**Example**:
287 287  
265 +If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
288 288  
267 +If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
289 289  
290 -=== 2.3.7  Message Type ===
269 +(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
291 291  
292 -(((
293 -For a normal uplink payload, the message type is always 0x01.
294 -)))
295 295  
296 -(((
297 -Valid Message Type:
298 -)))
299 299  
273 +=== 2.3.5  Sensor Flag ===
300 300  
301 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
302 -|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
303 -|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
304 -|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
275 +0x01: Detect Ultrasonic Sensor
305 305  
277 +0x00: No Ultrasonic Sensor
306 306  
307 -=== 2.3.8  Decode payload in The Things Network ===
308 308  
280 +===
281 +(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
282 +
309 309  While using TTN network, you can add the payload format to decode the payload.
310 310  
311 311  
312 -[[image:1654592762713-715.png]]
286 +[[image:1654850829385-439.png]]
313 313  
314 -(((
315 -The payload decoder function for TTN is here:
316 -)))
288 +The payload decoder function for TTN V3 is here:
317 317  
318 -(((
319 -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/]]
320 -)))
290 +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/]]
321 321  
322 322  
323 323  
324 324  == 2.4  Uplink Interval ==
325 325  
326 -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"]]
296 +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"]]
327 327  
328 328  
329 329  
... ... @@ -354,47 +354,25 @@
354 354  
355 355  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
356 356  
357 -(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
327 +(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
358 358  
359 -[[image:1654832691989-514.png]]
329 +[[image:1654851029373-510.png]]
360 360  
361 361  
362 -[[image:1654592833877-762.png]]
332 +After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
363 363  
334 +[[image:image-20220610165129-11.png||height="595" width="1088"]]
364 364  
365 -[[image:1654832740634-933.png]]
366 366  
367 367  
368 -
369 -(((
370 -(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
371 -)))
372 -
373 -(((
374 -
375 -)))
376 -
377 -[[image:1654833065139-942.png]]
378 -
379 -
380 -
381 -[[image:1654833092678-390.png]]
382 -
383 -
384 -
385 -After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
386 -
387 -[[image:1654833163048-332.png]]
388 -
389 -
390 -
391 391  == 2.6  Frequency Plans ==
392 392  
393 393  (((
394 -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.
341 +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.
395 395  )))
396 396  
397 397  
345 +
398 398  === 2.6.1  EU863-870 (EU868) ===
399 399  
400 400  (((
... ... @@ -458,21 +458,51 @@
458 458  === 2.6.2  US902-928(US915) ===
459 459  
460 460  (((
461 -Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
462 -)))
409 +Used in USA, Canada and South America. Default use CHE=2
463 463  
464 -(((
465 -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.
466 -)))
411 +(% style="color:blue" %)**Uplink:**
467 467  
468 -(((
469 -After Join success, the end node will switch to the correct sub band by:
470 -)))
413 +903.9 - SF7BW125 to SF10BW125
471 471  
472 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
473 -* 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)
415 +904.1 - SF7BW125 to SF10BW125
474 474  
417 +904.3 - SF7BW125 to SF10BW125
475 475  
419 +904.5 - SF7BW125 to SF10BW125
420 +
421 +904.7 - SF7BW125 to SF10BW125
422 +
423 +904.9 - SF7BW125 to SF10BW125
424 +
425 +905.1 - SF7BW125 to SF10BW125
426 +
427 +905.3 - SF7BW125 to SF10BW125
428 +
429 +
430 +(% style="color:blue" %)**Downlink:**
431 +
432 +923.3 - SF7BW500 to SF12BW500
433 +
434 +923.9 - SF7BW500 to SF12BW500
435 +
436 +924.5 - SF7BW500 to SF12BW500
437 +
438 +925.1 - SF7BW500 to SF12BW500
439 +
440 +925.7 - SF7BW500 to SF12BW500
441 +
442 +926.3 - SF7BW500 to SF12BW500
443 +
444 +926.9 - SF7BW500 to SF12BW500
445 +
446 +927.5 - SF7BW500 to SF12BW500
447 +
448 +923.3 - SF12BW500(RX2 downlink only)
449 +
450 +
451 +
452 +)))
453 +
476 476  === 2.6.3  CN470-510 (CN470) ===
477 477  
478 478  (((
... ... @@ -565,25 +565,51 @@
565 565  === 2.6.4  AU915-928(AU915) ===
566 566  
567 567  (((
568 -Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
569 -)))
546 +Default use CHE=2
570 570  
571 -(((
572 -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.
573 -)))
548 +(% style="color:blue" %)**Uplink:**
574 574  
575 -(((
576 -
577 -)))
550 +916.8 - SF7BW125 to SF12BW125
578 578  
579 -(((
580 -After Join success, the end node will switch to the correct sub band by:
581 -)))
552 +917.0 - SF7BW125 to SF12BW125
582 582  
583 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
584 -* 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)
554 +917.2 - SF7BW125 to SF12BW125
585 585  
556 +917.4 - SF7BW125 to SF12BW125
586 586  
558 +917.6 - SF7BW125 to SF12BW125
559 +
560 +917.8 - SF7BW125 to SF12BW125
561 +
562 +918.0 - SF7BW125 to SF12BW125
563 +
564 +918.2 - SF7BW125 to SF12BW125
565 +
566 +
567 +(% style="color:blue" %)**Downlink:**
568 +
569 +923.3 - SF7BW500 to SF12BW500
570 +
571 +923.9 - SF7BW500 to SF12BW500
572 +
573 +924.5 - SF7BW500 to SF12BW500
574 +
575 +925.1 - SF7BW500 to SF12BW500
576 +
577 +925.7 - SF7BW500 to SF12BW500
578 +
579 +926.3 - SF7BW500 to SF12BW500
580 +
581 +926.9 - SF7BW500 to SF12BW500
582 +
583 +927.5 - SF7BW500 to SF12BW500
584 +
585 +923.3 - SF12BW500(RX2 downlink only)
586 +
587 +
588 +
589 +)))
590 +
587 587  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
588 588  
589 589  (((
... ... @@ -810,7 +810,6 @@
810 810  * The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
811 811  * Blink once when device transmit a packet.
812 812  
813 -
814 814  == 2.8  ​Firmware Change Log ==
815 815  
816 816  
... ... @@ -881,7 +881,6 @@
881 881  * The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
882 882  * The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
883 883  
884 -
885 885  = 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
886 886  
887 887  (((
... ... @@ -988,7 +988,6 @@
988 988  Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
989 989  )))
990 990  
991 -
992 992  == 4.2  Set Interrupt Mode ==
993 993  
994 994  Feature, Set Interrupt mode for GPIO_EXIT.
... ... @@ -1017,7 +1017,6 @@
1017 1017  Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
1018 1018  )))
1019 1019  
1020 -
1021 1021  == 4.3  Get Firmware Version Info ==
1022 1022  
1023 1023  Feature: use downlink to get firmware version.
... ... @@ -1289,7 +1289,6 @@
1289 1289  * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1290 1290  * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1291 1291  
1292 -
1293 1293  = 10. ​ Packing Info =
1294 1294  
1295 1295  
... ... @@ -1304,7 +1304,6 @@
1304 1304  * Package Size / pcs : cm
1305 1305  * Weight / pcs : g
1306 1306  
1307 -
1308 1308  = 11.  ​Support =
1309 1309  
1310 1310  * 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.
1654846127817-788.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +107.3 KB
Content
1654847051249-359.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.8 KB
Content
1654847583902-256.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +492.6 KB
Content
1654848616367-242.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.8 KB
Content
1654849068701-275.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +88.3 KB
Content
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-20220610154839-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +11.3 KB
Content
image-20220610155021-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +164.8 KB
Content
image-20220610155021-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +181.8 KB
Content
image-20220610161353-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +32.2 KB
Content
image-20220610161353-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +42.7 KB
Content
image-20220610161353-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +36.3 KB
Content
image-20220610161353-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.1 KB
Content
image-20220610161538-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.2 KB
Content
image-20220610161538-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +28.7 KB
Content
image-20220610161724-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +180.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