Last modified by Mengting Qiu on 2025/02/26 15:04
<
From version < 120.2 >
edited by Xiaoling
on 2022/06/10 15:44
To version < 137.4 >
edited by Xiaoling
on 2022/06/10 16:57
>
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  
... ... @@ -45,41 +45,45 @@
45 45  == ​1.2  Features ==
46 46  
47 47  * LoRaWAN 1.0.3 Class A
48 -* Ultra-low power consumption
49 -* Laser technology for distance detection
50 -* Operating Range - 0.1m~~12m①
51 -* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
52 -* 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
53 53  * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
54 54  * AT Commands to change parameters
55 55  * Uplink on periodically
56 56  * Downlink to change configure
57 -* 8500mAh Battery for long term use
57 +* IP66 Waterproof Enclosure
58 +* 4000mAh or 8500mAh Battery for long term use
58 58  
59 -== 1.3  Probe Specification ==
60 +== 1.3  Specification ==
60 60  
61 -* Storage temperature ：-20℃~~75℃
62 -* Operating temperature - -20℃~~60℃
63 -* Operating Range - 0.1m~~12m①
64 -* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
65 -* Distance resolution - 5mm
66 -* Ambient light immunity - 70klux
67 -* Enclosure rating - IP65
68 -* Light source - LED
69 -* Central wavelength - 850nm
70 -* FOV - 3.6°
71 -* Material of enclosure - ABS+PC
72 -* Wire length - 25cm
62 +=== 1.3.1  Rated environmental conditions ===
73 73  
74 -== 1.4  Probe Dimension ==
64 +[[image:image-20220610154839-1.png]]
75 75  
66 +**Remarks: (1) a. When the ambient temperature is 0-39 ℃, the maximum humidity is 90% (non-condensing);**
76 76  
77 -[[image:1654827224480-952.png]]
68 +**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)**
78 78  
79 79  
71 +
72 +=== 1.3.2  Effective measurement range Reference beam pattern ===
73 +
74 +**(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="440" width="1189"]]
75 +
76 +
77 +
78 +**(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.[[image:image-20220610155021-3.png||height="437" width="1192"]]
79 +
80 +(% style="display:none" %) (%%)
81 +
82 +
80 80  == 1.5 ​ Applications ==
81 81  
82 82  * Horizontal distance measurement
86 +* Liquid level measurement
83 83  * Parking management system
84 84  * Object proximity and presence detection
85 85  * Intelligent trash can management system
... ... @@ -86,23 +86,24 @@
86 86  * Robot obstacle avoidance
87 87  * Automatic control
88 88  * Sewer
93 +* Bottom water level monitoring
89 89  
90 90  == 1.6  Pin mapping and power on ==
91 91  
92 92  
93 -[[image:1654827332142-133.png]]
98 +[[image:1654847583902-256.png]]
94 94  
95 95  
96 -= 2.  Configure LLDS12 to connect to LoRaWAN network =
101 += 2.  Configure LDDS75 to connect to LoRaWAN network =
97 97  
98 98  == 2.1  How it works ==
99 99  
100 100  (((
101 -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.
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
102 102  )))
103 103  
104 104  (((
105 -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.
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.
106 106  )))
107 107  
108 108  
... ... @@ -113,7 +113,7 @@
113 113  )))
114 114  
115 115  (((
116 -[[image:1654827857527-556.png]]
121 +[[image:1654848616367-242.png]]
117 117  )))
118 118  
119 119  (((
... ... @@ -121,57 +121,57 @@
121 121  )))
122 122  
123 123  (((
124 -(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSPH01.
129 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS75.
125 125  )))
126 126  
127 127  (((
128 -Each LSPH01 is shipped with a sticker with the default device EUI as below:
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.
129 129  )))
130 130  
131 131  [[image:image-20220607170145-1.jpeg]]
132 132  
133 133  
139 +For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
134 134  
135 -You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
141 +Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
136 136  
143 +**Add APP EUI in the application**
137 137  
138 -**Register the device**
145 +[[image:image-20220610161353-4.png]]
139 139  
147 +[[image:image-20220610161353-5.png]]
140 140  
141 -[[image:1654592600093-601.png]]
149 +[[image:image-20220610161353-6.png]]
142 142  
143 143  
152 +[[image:image-20220610161353-7.png]]
144 144  
145 -**Add APP EUI and DEV EUI**
146 146  
147 -[[image:1654592619856-881.png]]
155 +You can also choose to create the device manually.
148 148  
157 + [[image:image-20220610161538-8.png]]
149 149  
150 150  
151 -**Add APP EUI in the application**
152 152  
153 -[[image:1654592632656-512.png]]
161 +**Add APP KEY and DEV EUI**
154 154  
163 +[[image:image-20220610161538-9.png]]
155 155  
156 156  
157 -**Add APP KEY**
158 158  
159 -[[image:1654592653453-934.png]]
167 +(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
160 160  
161 161  
162 -(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
163 -
164 -
165 165  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
166 166  
167 -[[image:image-20220607170442-2.png]]
172 +[[image:image-20220610161724-10.png]]
168 168  
169 169  
170 170  (((
171 -(% 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.
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.
172 172  )))
173 173  
174 -[[image:1654833501679-968.png]]
179 +[[image:1654849068701-275.png]]
175 175  
176 176  
177 177  
... ... @@ -178,11 +178,10 @@
178 178  == 2.3  ​Uplink Payload ==
179 179  
180 180  (((
181 -LLDS12 will uplink payload via LoRaWAN with below payload format: 
182 -)))
186 +LDDS75 will uplink payload via LoRaWAN with below payload format: 
183 183  
184 -(((
185 -Uplink payload includes in total 11 bytes.
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
186 186  )))
187 187  
188 188  (((
... ... @@ -192,23 +192,23 @@
192 192  (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
193 193  |=(% style="width: 62.5px;" %)(((
194 194  **Size (bytes)**
195 -)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
196 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
197 -[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
198 -)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
199 -[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
200 -)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
201 -[[Message Type>>||anchor="H2.3.7A0MessageType"]]
202 -)))
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 203  
204 -[[image:1654833689380-972.png]]
203 +(unit: mm)
204 +)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
205 +[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
206 +)))|[[Sensor Flag>>path:#Sensor_Flag]]
205 205  
208 +[[image:1654850511545-399.png]]
206 206  
207 207  
211 +
208 208  === 2.3.1  Battery Info ===
209 209  
210 210  
211 -Check the battery voltage for LLDS12.
215 +Check the battery voltage for LDDS75.
212 212  
213 213  Ex1: 0x0B45 = 2885mV
214 214  
... ... @@ -216,49 +216,22 @@
216 216  
217 217  
218 218  
219 -=== 2.3.2  DS18B20 Temperature sensor ===
223 +=== 2.3.2  Distance ===
220 220  
221 -This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
225 +Get the distance. Flat object range 280mm - 7500mm.
222 222  
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.**
223 223  
224 -**Example**:
225 225  
226 -If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
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.
227 227  
228 -If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
229 229  
230 230  
235 +=== 2.3.3  Interrupt Pin ===
231 231  
232 -=== 2.3.3  Distance ===
233 -
234 -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.
235 -
236 -
237 -**Example**:
238 -
239 -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.
240 -
241 -
242 -
243 -=== 2.3.4  Distance signal strength ===
244 -
245 -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.
246 -
247 -
248 -**Example**:
249 -
250 -If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
251 -
252 -Customers can judge whether they need to adjust the environment based on the signal strength.
253 -
254 -
255 -
256 -=== 2.3.5  Interrupt Pin ===
257 -
258 258  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.
259 259  
260 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
261 -
262 262  **Example:**
263 263  
264 264  0x00: Normal uplink packet.
... ... @@ -266,53 +266,44 @@
266 266  0x01: Interrupt Uplink Packet.
267 267  
268 268  
246 +=== 2.3.4  DS18B20 Temperature sensor ===
269 269  
270 -=== 2.3.6  LiDAR temp ===
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.
271 271  
272 -Characterize the internal temperature value of the sensor.
250 +**Example**:
273 273  
274 -**Example: **
275 -If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
276 -If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
252 +If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
277 277  
254 +If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
278 278  
256 +(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
279 279  
280 -=== 2.3.7  Message Type ===
281 281  
282 -(((
283 -For a normal uplink payload, the message type is always 0x01.
284 -)))
285 285  
286 -(((
287 -Valid Message Type:
288 -)))
260 +=== 2.3.5  Sensor Flag ===
289 289  
262 +0x01: Detect Ultrasonic Sensor
290 290  
291 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
292 -|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
293 -|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
294 -|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
264 +0x00: No Ultrasonic Sensor
295 295  
296 -=== 2.3.8  Decode payload in The Things Network ===
297 297  
267 +===
268 +(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
269 +
298 298  While using TTN network, you can add the payload format to decode the payload.
299 299  
300 300  
301 -[[image:1654592762713-715.png]]
273 +[[image:1654850829385-439.png]]
302 302  
303 -(((
304 -The payload decoder function for TTN is here:
305 -)))
275 +The payload decoder function for TTN V3 is here:
306 306  
307 -(((
308 -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/]]
309 -)))
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/]]
310 310  
311 311  
312 312  
313 313  == 2.4  Uplink Interval ==
314 314  
315 -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"]]
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"]]
316 316  
317 317  
318 318  
... ... @@ -343,44 +343,21 @@
343 343  
344 344  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
345 345  
346 -(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
314 +(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
347 347  
348 -[[image:1654832691989-514.png]]
316 +[[image:1654851029373-510.png]]
349 349  
350 350  
351 -[[image:1654592833877-762.png]]
319 +After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
352 352  
321 +[[image:image-20220610165129-11.png||height="595" width="1088"]]
353 353  
354 -[[image:1654832740634-933.png]]
355 355  
356 356  
357 -
358 -(((
359 -(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
360 -)))
361 -
362 -(((
363 -
364 -)))
365 -
366 -[[image:1654833065139-942.png]]
367 -
368 -
369 -
370 -[[image:1654833092678-390.png]]
371 -
372 -
373 -
374 -After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
375 -
376 -[[image:1654833163048-332.png]]
377 -
378 -
379 -
380 380  == 2.6  Frequency Plans ==
381 381  
382 382  (((
383 -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.
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.
384 384  )))
385 385  
386 386  
... ... @@ -447,20 +447,51 @@
447 447  === 2.6.2  US902-928(US915) ===
448 448  
449 449  (((
450 -Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
451 -)))
395 +Used in USA, Canada and South America. Default use CHE=2
452 452  
453 -(((
454 -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.
455 -)))
397 +(% style="color:blue" %)**Uplink:**
456 456  
457 -(((
458 -After Join success, the end node will switch to the correct sub band by:
459 -)))
399 +903.9 - SF7BW125 to SF10BW125
460 460  
461 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
462 -* 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)
401 +904.1 - SF7BW125 to SF10BW125
463 463  
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 +
438 +)))
439 +
464 464  === 2.6.3  CN470-510 (CN470) ===
465 465  
466 466  (((
... ... @@ -553,24 +553,51 @@
553 553  === 2.6.4  AU915-928(AU915) ===
554 554  
555 555  (((
556 -Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
557 -)))
532 +Default use CHE=2
558 558  
559 -(((
560 -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.
561 -)))
534 +(% style="color:blue" %)**Uplink:**
562 562  
563 -(((
564 -
565 -)))
536 +916.8 - SF7BW125 to SF12BW125
566 566  
567 -(((
568 -After Join success, the end node will switch to the correct sub band by:
569 -)))
538 +917.0 - SF7BW125 to SF12BW125
570 570  
571 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
572 -* 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)
540 +917.2 - SF7BW125 to SF12BW125
573 573  
542 +917.4 - SF7BW125 to SF12BW125
543 +
544 +917.6 - SF7BW125 to SF12BW125
545 +
546 +917.8 - SF7BW125 to SF12BW125
547 +
548 +918.0 - SF7BW125 to SF12BW125
549 +
550 +918.2 - SF7BW125 to SF12BW125
551 +
552 +
553 +(% style="color:blue" %)**Downlink:**
554 +
555 +923.3 - SF7BW500 to SF12BW500
556 +
557 +923.9 - SF7BW500 to SF12BW500
558 +
559 +924.5 - SF7BW500 to SF12BW500
560 +
561 +925.1 - SF7BW500 to SF12BW500
562 +
563 +925.7 - SF7BW500 to SF12BW500
564 +
565 +926.3 - SF7BW500 to SF12BW500
566 +
567 +926.9 - SF7BW500 to SF12BW500
568 +
569 +927.5 - SF7BW500 to SF12BW500
570 +
571 +923.3 - SF12BW500(RX2 downlink only)
572 +
573 +
574 +
575 +)))
576 +
574 574  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
575 575  
576 576  (((
... ... @@ -1272,7 +1272,6 @@
1272 1272  * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1273 1273  * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1274 1274  
1275 -
1276 1276  = 10. ​ Packing Info =
1277 1277  
1278 1278  
... ... @@ -1287,7 +1287,6 @@
1287 1287  * Package Size / pcs : cm
1288 1288  * Weight / pcs : g
1289 1289  
1290 -
1291 1291  = 11.  ​Support =
1292 1292  
1293 1293  * 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.
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