Last modified by Mengting Qiu on 2024/03/07 08:41
<
From version < 115.1 >
edited by Xiaoling
on 2022/06/10 15:11
To version < 138.7 >
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,47 +52,51 @@
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  
61 +== 1.3  Specification ==
67 67  
63 +=== 1.3.1  Rated environmental conditions ===
68 68  
69 -== 1.3  Probe Specification ==
65 +[[image:image-20220610154839-1.png]]
70 70  
71 -* Storage temperature ：-20℃~~75℃
72 -* Operating temperature - -20℃~~60℃
73 -* Operating Range - 0.1m~~12m①
74 -* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
75 -* Distance resolution - 5mm
76 -* Ambient light immunity - 70klux
77 -* Enclosure rating - IP65
78 -* Light source - LED
79 -* Central wavelength - 850nm
80 -* FOV - 3.6°
81 -* Material of enclosure - ABS+PC
82 -* Wire length - 25cm
67 +**Remarks: (1) a. When the ambient temperature is 0-39 ℃, the maximum humidity is 90% (non-condensing);**
83 83  
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)**
84 84  
85 85  
86 86  
87 -== 1.4  Probe Dimension ==
73 +=== 1.3.2  Effective measurement range Reference beam pattern ===
88 88  
75 +**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**[[image:image-20220610155021-2.png||height="377" width="1021"]]
89 89  
90 -[[image:1654827224480-952.png]]
91 91  
92 92  
79 +**(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.**
80 +
81 +(% style="display:none" %) (%%)
82 +
83 +(% style="display:none" %)** **[[image:image-20220610155021-3.png||height="374" width="1020"]]
84 +
85 +(% style="display:none" %) (%%)
86 +
87 +
88 +
93 93  == 1.5 ​ Applications ==
94 94  
95 95  * Horizontal distance measurement
92 +* Liquid level measurement
96 96  * Parking management system
97 97  * Object proximity and presence detection
98 98  * Intelligent trash can management system
... ... @@ -99,29 +99,30 @@
99 99  * Robot obstacle avoidance
100 100  * Automatic control
101 101  * Sewer
99 +* Bottom water level monitoring
102 102  
103 103  
104 -
105 -
106 106  == 1.6  Pin mapping and power on ==
107 107  
108 108  
109 -[[image:1654827332142-133.png]]
105 +[[image:1654847583902-256.png]]
110 110  
111 111  
112 -= 2.  Configure LLDS12 to connect to LoRaWAN network =
113 113  
109 += 2.  Configure LDDS75 to connect to LoRaWAN network =
110 +
114 114  == 2.1  How it works ==
115 115  
116 116  (((
117 -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.
114 +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
118 118  )))
119 119  
120 120  (((
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="H6.A0UseATCommand"]]to set the keys in the LLDS12.
118 +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.
122 122  )))
123 123  
124 124  
122 +
125 125  == 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
126 126  
127 127  (((
... ... @@ -129,7 +129,7 @@
129 129  )))
130 130  
131 131  (((
132 -[[image:1654827857527-556.png]]
130 +[[image:1654848616367-242.png]]
133 133  )))
134 134  
135 135  (((
... ... @@ -137,57 +137,57 @@
137 137  )))
138 138  
139 139  (((
140 -(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSPH01.
138 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS75.
141 141  )))
142 142  
143 143  (((
144 -Each LSPH01 is shipped with a sticker with the default device EUI as below:
142 +Each LDDS75 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
145 145  )))
146 146  
147 147  [[image:image-20220607170145-1.jpeg]]
148 148  
149 149  
148 +For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
150 150  
151 -You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
150 +Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
152 152  
152 +**Add APP EUI in the application**
153 153  
154 -**Register the device**
154 +[[image:image-20220610161353-4.png]]
155 155  
156 +[[image:image-20220610161353-5.png]]
156 156  
157 -[[image:1654592600093-601.png]]
158 +[[image:image-20220610161353-6.png]]
158 158  
159 159  
161 +[[image:image-20220610161353-7.png]]
160 160  
161 -**Add APP EUI and DEV EUI**
162 162  
163 -[[image:1654592619856-881.png]]
164 +You can also choose to create the device manually.
164 164  
166 + [[image:image-20220610161538-8.png]]
165 165  
166 166  
167 -**Add APP EUI in the application**
168 168  
169 -[[image:1654592632656-512.png]]
170 +**Add APP KEY and DEV EUI**
170 170  
172 +[[image:image-20220610161538-9.png]]
171 171  
172 172  
173 -**Add APP KEY**
174 174  
175 -[[image:1654592653453-934.png]]
176 +(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
176 176  
177 177  
178 -(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
179 -
180 -
181 181  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
182 182  
183 -[[image:image-20220607170442-2.png]]
181 +[[image:image-20220610161724-10.png]]
184 184  
185 185  
186 186  (((
187 -(% 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.
185 +(% 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.
188 188  )))
189 189  
190 -[[image:1654833501679-968.png]]
188 +[[image:1654849068701-275.png]]
191 191  
192 192  
193 193  
... ... @@ -194,11 +194,10 @@
194 194  == 2.3  ​Uplink Payload ==
195 195  
196 196  (((
197 -LLDS12 will uplink payload via LoRaWAN with below payload format: 
198 -)))
195 +LDDS75 will uplink payload via LoRaWAN with below payload format: 
199 199  
200 -(((
201 -Uplink payload includes in total 11 bytes.
197 +Uplink payload includes in total 4 bytes.
198 +Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
202 202  )))
203 203  
204 204  (((
... ... @@ -208,23 +208,23 @@
208 208  (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
209 209  |=(% style="width: 62.5px;" %)(((
210 210  **Size (bytes)**
211 -)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
212 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
213 -[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
214 -)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
215 -[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
216 -)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
217 -[[Message Type>>||anchor="H2.3.7A0MessageType"]]
218 -)))
208 +)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
209 +|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
210 +[[Distance>>||anchor="H2.3.3A0Distance"]]
219 219  
220 -[[image:1654833689380-972.png]]
212 +(unit: mm)
213 +)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
214 +[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
215 +)))|[[Sensor Flag>>path:#Sensor_Flag]]
221 221  
217 +[[image:1654850511545-399.png]]
222 222  
223 223  
220 +
224 224  === 2.3.1  Battery Info ===
225 225  
226 226  
227 -Check the battery voltage for LLDS12.
224 +Check the battery voltage for LDDS75.
228 228  
229 229  Ex1: 0x0B45 = 2885mV
230 230  
... ... @@ -232,49 +232,22 @@
232 232  
233 233  
234 234  
235 -=== 2.3.2  DS18B20 Temperature sensor ===
232 +=== 2.3.2  Distance ===
236 236  
237 -This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
234 +Get the distance. Flat object range 280mm - 7500mm.
238 238  
236 +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.**
239 239  
240 -**Example**:
241 241  
242 -If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
239 +* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
240 +* 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.
243 243  
244 -If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
245 245  
246 246  
244 +=== 2.3.3  Interrupt Pin ===
247 247  
248 -=== 2.3.3  Distance ===
249 -
250 -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.
251 -
252 -
253 -**Example**:
254 -
255 -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.
256 -
257 -
258 -
259 -=== 2.3.4  Distance signal strength ===
260 -
261 -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.
262 -
263 -
264 -**Example**:
265 -
266 -If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
267 -
268 -Customers can judge whether they need to adjust the environment based on the signal strength.
269 -
270 -
271 -
272 -=== 2.3.5  Interrupt Pin ===
273 -
274 274  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.
275 275  
276 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
277 -
278 278  **Example:**
279 279  
280 280  0x00: Normal uplink packet.
... ... @@ -283,55 +283,44 @@
283 283  
284 284  
285 285  
286 -=== 2.3.6  LiDAR temp ===
256 +=== 2.3.4  DS18B20 Temperature sensor ===
287 287  
288 -Characterize the internal temperature value of the sensor.
258 +This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
289 289  
290 -**Example: **
291 -If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
292 -If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
260 +**Example**:
293 293  
262 +If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
294 294  
264 +If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
295 295  
296 -=== 2.3.7  Message Type ===
266 +(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
297 297  
298 -(((
299 -For a normal uplink payload, the message type is always 0x01.
300 -)))
301 301  
302 -(((
303 -Valid Message Type:
304 -)))
305 305  
270 +=== 2.3.5  Sensor Flag ===
306 306  
307 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
308 -|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
309 -|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
310 -|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
272 +0x01: Detect Ultrasonic Sensor
311 311  
274 +0x00: No Ultrasonic Sensor
312 312  
313 313  
277 +===
278 +(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
314 314  
315 -=== 2.3.8  Decode payload in The Things Network ===
316 -
317 317  While using TTN network, you can add the payload format to decode the payload.
318 318  
319 319  
320 -[[image:1654592762713-715.png]]
283 +[[image:1654850829385-439.png]]
321 321  
322 -(((
323 -The payload decoder function for TTN is here:
324 -)))
285 +The payload decoder function for TTN V3 is here:
325 325  
326 -(((
327 -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/]]
328 -)))
287 +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/]]
329 329  
330 330  
331 331  
332 332  == 2.4  Uplink Interval ==
333 333  
334 -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"]]
293 +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"]]
335 335  
336 336  
337 337  
... ... @@ -362,47 +362,25 @@
362 362  
363 363  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
364 364  
365 -(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
324 +(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
366 366  
367 -[[image:1654832691989-514.png]]
326 +[[image:1654851029373-510.png]]
368 368  
369 369  
370 -[[image:1654592833877-762.png]]
329 +After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
371 371  
331 +[[image:image-20220610165129-11.png||height="595" width="1088"]]
372 372  
373 -[[image:1654832740634-933.png]]
374 374  
375 375  
376 -
377 -(((
378 -(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
379 -)))
380 -
381 -(((
382 -
383 -)))
384 -
385 -[[image:1654833065139-942.png]]
386 -
387 -
388 -
389 -[[image:1654833092678-390.png]]
390 -
391 -
392 -
393 -After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
394 -
395 -[[image:1654833163048-332.png]]
396 -
397 -
398 -
399 399  == 2.6  Frequency Plans ==
400 400  
401 401  (((
402 -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.
338 +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.
403 403  )))
404 404  
405 405  
342 +
406 406  === 2.6.1  EU863-870 (EU868) ===
407 407  
408 408  (((
... ... @@ -466,23 +466,51 @@
466 466  === 2.6.2  US902-928(US915) ===
467 467  
468 468  (((
469 -Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
470 -)))
406 +Used in USA, Canada and South America. Default use CHE=2
471 471  
472 -(((
473 -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.
474 -)))
408 +(% style="color:blue" %)**Uplink:**
475 475  
476 -(((
477 -After Join success, the end node will switch to the correct sub band by:
478 -)))
410 +903.9 - SF7BW125 to SF10BW125
479 479  
480 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
481 -* 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)
412 +904.1 - SF7BW125 to SF10BW125
482 482  
414 +904.3 - SF7BW125 to SF10BW125
483 483  
416 +904.5 - SF7BW125 to SF10BW125
484 484  
418 +904.7 - SF7BW125 to SF10BW125
485 485  
420 +904.9 - SF7BW125 to SF10BW125
421 +
422 +905.1 - SF7BW125 to SF10BW125
423 +
424 +905.3 - SF7BW125 to SF10BW125
425 +
426 +
427 +(% style="color:blue" %)**Downlink:**
428 +
429 +923.3 - SF7BW500 to SF12BW500
430 +
431 +923.9 - SF7BW500 to SF12BW500
432 +
433 +924.5 - SF7BW500 to SF12BW500
434 +
435 +925.1 - SF7BW500 to SF12BW500
436 +
437 +925.7 - SF7BW500 to SF12BW500
438 +
439 +926.3 - SF7BW500 to SF12BW500
440 +
441 +926.9 - SF7BW500 to SF12BW500
442 +
443 +927.5 - SF7BW500 to SF12BW500
444 +
445 +923.3 - SF12BW500(RX2 downlink only)
446 +
447 +
448 +
449 +)))
450 +
486 486  === 2.6.3  CN470-510 (CN470) ===
487 487  
488 488  (((
... ... @@ -575,27 +575,51 @@
575 575  === 2.6.4  AU915-928(AU915) ===
576 576  
577 577  (((
578 -Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
579 -)))
543 +Default use CHE=2
580 580  
581 -(((
582 -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.
583 -)))
545 +(% style="color:blue" %)**Uplink:**
584 584  
585 -(((
586 -
587 -)))
547 +916.8 - SF7BW125 to SF12BW125
588 588  
589 -(((
590 -After Join success, the end node will switch to the correct sub band by:
591 -)))
549 +917.0 - SF7BW125 to SF12BW125
592 592  
593 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
594 -* 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)
551 +917.2 - SF7BW125 to SF12BW125
595 595  
553 +917.4 - SF7BW125 to SF12BW125
596 596  
555 +917.6 - SF7BW125 to SF12BW125
597 597  
557 +917.8 - SF7BW125 to SF12BW125
598 598  
559 +918.0 - SF7BW125 to SF12BW125
560 +
561 +918.2 - SF7BW125 to SF12BW125
562 +
563 +
564 +(% style="color:blue" %)**Downlink:**
565 +
566 +923.3 - SF7BW500 to SF12BW500
567 +
568 +923.9 - SF7BW500 to SF12BW500
569 +
570 +924.5 - SF7BW500 to SF12BW500
571 +
572 +925.1 - SF7BW500 to SF12BW500
573 +
574 +925.7 - SF7BW500 to SF12BW500
575 +
576 +926.3 - SF7BW500 to SF12BW500
577 +
578 +926.9 - SF7BW500 to SF12BW500
579 +
580 +927.5 - SF7BW500 to SF12BW500
581 +
582 +923.3 - SF12BW500(RX2 downlink only)
583 +
584 +
585 +
586 +)))
587 +
599 599  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
600 600  
601 601  (((
... ... @@ -822,9 +822,6 @@
822 822  * The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
823 823  * Blink once when device transmit a packet.
824 824  
825 -
826 -
827 -
828 828  == 2.8  ​Firmware Change Log ==
829 829  
830 830  
... ... @@ -895,9 +895,6 @@
895 895  * The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
896 896  * The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
897 897  
898 -
899 -
900 -
901 901  = 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
902 902  
903 903  (((
... ... @@ -1002,14 +1002,8 @@
1002 1002  )))
1003 1003  * (((
1004 1004  Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
1005 -
1006 -
1007 -
1008 1008  )))
1009 1009  
1010 -
1011 -
1012 -
1013 1013  == 4.2  Set Interrupt Mode ==
1014 1014  
1015 1015  Feature, Set Interrupt mode for GPIO_EXIT.
... ... @@ -1038,9 +1038,6 @@
1038 1038  Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
1039 1039  )))
1040 1040  
1041 -
1042 -
1043 -
1044 1044  == 4.3  Get Firmware Version Info ==
1045 1045  
1046 1046  Feature: use downlink to get firmware version.
... ... @@ -1312,9 +1312,6 @@
1312 1312  * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1313 1313  * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1314 1314  
1315 -
1316 -
1317 -
1318 1318  = 10. ​ Packing Info =
1319 1319  
1320 1320  
... ... @@ -1329,9 +1329,6 @@
1329 1329  * Package Size / pcs : cm
1330 1330  * Weight / pcs : g
1331 1331  
1332 -
1333 -
1334 -
1335 1335  = 11.  ​Support =
1336 1336  
1337 1337  * 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