<
From version < 97.10 >
edited by Xiaoling
on 2022/07/09 11:30
To version < 100.5 >
edited by Xiaoling
on 2022/08/22 14:39
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,6 +16,7 @@
16 16  
17 17  = 1.  Introduction =
18 18  
19 +
19 19  == 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20 20  
21 21  (((
... ... @@ -22,14 +22,31 @@
22 22  
23 23  
24 24  (((
26 +(((
25 25  The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
26 -\\The NDDS75 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. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
27 -\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
29 -\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
30 -\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
31 31  )))
32 32  
30 +(((
31 +The NDDS75 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. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
32 +)))
33 +
34 +(((
35 +NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
36 +)))
37 +
38 +(((
39 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
40 +)))
41 +
42 +(((
43 +NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
44 +)))
45 +
46 +(((
47 +To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
48 +)))
49 +)))
50 +
33 33  
34 34  )))
35 35  
... ... @@ -55,6 +55,7 @@
55 55  
56 56  
57 57  
76 +
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -63,6 +63,7 @@
63 63  * Supply Voltage: 2.1v ~~ 3.6v
64 64  * Operating Temperature: -40 ~~ 85°C
65 65  
85 +
66 66  (% style="color:#037691" %)**NB-IoT Spec:**
67 67  
68 68  * - B1 @H-FDD: 2100MHz
... ... @@ -72,6 +72,7 @@
72 72  * - B20 @H-FDD: 800MHz
73 73  * - B28 @H-FDD: 700MHz
74 74  
95 +
75 75  (% style="color:#037691" %)**Battery:**
76 76  
77 77  * Li/SOCI2 un-chargeable battery
... ... @@ -80,6 +80,7 @@
80 80  * Max continuously current: 130mA
81 81  * Max boost current: 2A, 1 second
82 82  
104 +
83 83  (% style="color:#037691" %)**Power Consumption**
84 84  
85 85  * STOP Mode: 10uA @ 3.3v
... ... @@ -87,8 +87,10 @@
87 87  
88 88  
89 89  
112 +
90 90  == ​1.4  Applications ==
91 91  
115 +
92 92  * Smart Buildings & Home Automation
93 93  * Logistics and Supply Chain Management
94 94  * Smart Metering
... ... @@ -100,6 +100,8 @@
100 100  ​
101 101  
102 102  
127 +
128 +
103 103  == 1.5  Pin Definitions ==
104 104  
105 105  
... ... @@ -109,8 +109,10 @@
109 109  
110 110  = 2.  Use NDDS75 to communicate with IoT Server =
111 111  
138 +
112 112  == 2.1  How it works ==
113 113  
141 +
114 114  (((
115 115  The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
116 116  )))
... ... @@ -136,16 +136,17 @@
136 136  
137 137  === 2.2.1 Test Requirement ===
138 138  
167 +
139 139  (((
140 140  To use NDDS75 in your city, make sure meet below requirements:
141 141  )))
142 142  
143 143  * Your local operator has already distributed a NB-IoT Network there.
144 -* The local NB-IoT network used the band that NSE01 supports.
173 +* The local NB-IoT network used the band that NDDS75 supports.
145 145  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
146 146  
147 147  (((
148 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
177 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server.
149 149  )))
150 150  
151 151  
... ... @@ -155,6 +155,7 @@
155 155  
156 156  === 2.2.2 Insert SIM card ===
157 157  
187 +
158 158  (((
159 159  Insert the NB-IoT Card get from your provider.
160 160  )))
... ... @@ -170,6 +170,7 @@
170 170  
171 171  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
172 172  
203 +
173 173  (((
174 174  (((
175 175  User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
... ... @@ -178,6 +178,7 @@
178 178  
179 179  [[image:image-20220709092052-2.png]]
180 180  
212 +
181 181  **Connection:**
182 182  
183 183   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -201,8 +201,9 @@
201 201  
202 202  [[image:1657329814315-101.png]]
203 203  
236 +
204 204  (((
205 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
238 +(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**
206 206  )))
207 207  
208 208  
... ... @@ -209,9 +209,10 @@
209 209  
210 210  === 2.2.4 Use CoAP protocol to uplink data ===
211 211  
212 -(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
213 213  
246 +(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
214 214  
248 +
215 215  (((
216 216  **Use below commands:**
217 217  )))
... ... @@ -233,6 +233,7 @@
233 233  [[image:1657330452568-615.png]]
234 234  
235 235  
270 +
236 236  (((
237 237  After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
238 238  )))
... ... @@ -248,6 +248,7 @@
248 248  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
249 249  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
250 250  
286 +
251 251  [[image:1657330501006-241.png]]
252 252  
253 253  
... ... @@ -258,14 +258,15 @@
258 258  === 2.2.6 Use MQTT protocol to uplink data ===
259 259  
260 260  
261 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
262 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
263 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
264 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
265 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
297 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
298 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
299 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
300 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
301 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
266 266  * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
267 267  * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
268 268  
305 +
269 269  [[image:1657249978444-674.png]]
270 270  
271 271  
... ... @@ -284,6 +284,7 @@
284 284  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
285 285  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
286 286  
324 +
287 287  [[image:image-20220709093918-1.png]]
288 288  
289 289  
... ... @@ -293,6 +293,7 @@
293 293  
294 294  === 2.2.8 Change Update Interval ===
295 295  
334 +
296 296  User can use below command to change the (% style="color:green" %)**uplink interval**.
297 297  
298 298  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -302,7 +302,7 @@
302 302  )))
303 303  
304 304  (((
305 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
344 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
306 306  )))
307 307  
308 308  
... ... @@ -309,13 +309,14 @@
309 309  
310 310  == 2.3  Uplink Payload ==
311 311  
351 +
312 312  In this mode, uplink payload includes in total 14 bytes
313 313  
314 314  
315 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
316 -|=(% style="width: 80px;" %)(((
355 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
356 +|=(% style="width: 60px;" %)(((
317 317  **Size(bytes)**
318 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1**
358 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
319 319  |(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
320 320  
321 321  (((
... ... @@ -325,6 +325,7 @@
325 325  
326 326  [[image:1657331036973-987.png]]
327 327  
368 +
328 328  (((
329 329  The payload is ASCII string, representative same HEX:
330 330  )))
... ... @@ -362,6 +362,7 @@
362 362  
363 363  === 2.4.1  Device ID ===
364 364  
406 +
365 365  (((
366 366  By default, the Device ID equal to the last 6 bytes of IMEI.
367 367  )))
... ... @@ -368,6 +368,8 @@
368 368  
369 369  (((
370 370  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
413 +
414 +
371 371  )))
372 372  
373 373  (((
... ... @@ -386,6 +386,7 @@
386 386  
387 387  === 2.4.2  Version Info ===
388 388  
433 +
389 389  (((
390 390  Specify the software version: 0x64=100, means firmware version 1.00.
391 391  )))
... ... @@ -398,6 +398,7 @@
398 398  
399 399  === 2.4.3  Battery Info ===
400 400  
446 +
401 401  (((
402 402  Ex1: 0x0B45 = 2885mV
403 403  )))
... ... @@ -410,6 +410,7 @@
410 410  
411 411  === 2.4.4  Signal Strength ===
412 412  
459 +
413 413  (((
414 414  NB-IoT Network signal Strength.
415 415  )))
... ... @@ -442,9 +442,12 @@
442 442  
443 443  === 2.4.5  Distance ===
444 444  
492 +
445 445  Get the distance. Flat object range 280mm - 7500mm.
446 446  
495 +(((
447 447  For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
497 +)))
448 448  
449 449  (((
450 450  (((
... ... @@ -462,6 +462,7 @@
462 462  
463 463  === 2.4.6  Digital Interrupt ===
464 464  
515 +
465 465  (((
466 466  Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
467 467  )))
... ... @@ -496,6 +496,7 @@
496 496  
497 497  === 2.4.7  ​+5V Output ===
498 498  
550 +
499 499  (((
500 500  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
501 501  )))
... ... @@ -503,10 +503,14 @@
503 503  
504 504  (((
505 505  The 5V output time can be controlled by AT Command.
558 +
559 +
506 506  )))
507 507  
508 508  (((
509 509  (% style="color:blue" %)**AT+5VT=1000**
564 +
565 +
510 510  )))
511 511  
512 512  (((
... ... @@ -517,6 +517,7 @@
517 517  
518 518  == 2.5  Downlink Payload ==
519 519  
576 +
520 520  By default, NDDS75 prints the downlink payload to console port.
521 521  
522 522  [[image:image-20220709100028-1.png]]
... ... @@ -587,19 +587,23 @@
587 587  == 2.7  ​Firmware Change Log ==
588 588  
589 589  
590 -Download URL & Firmware Change log
647 +(((
648 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]
649 +)))
591 591  
592 592  (((
593 -[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
652 +
594 594  )))
595 595  
655 +(((
656 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
657 +)))
596 596  
597 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
598 598  
599 599  
600 -
601 601  == 2.8  ​Battery Analysis ==
602 602  
663 +
603 603  === 2.8.1  ​Battery Type ===
604 604  
605 605  
... ... @@ -627,6 +627,7 @@
627 627  
628 628  === 2.8.2  Power consumption Analyze ===
629 629  
691 +
630 630  (((
631 631  Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
632 632  )))
... ... @@ -665,6 +665,7 @@
665 665  
666 666  === 2.8.3  ​Battery Note ===
667 667  
730 +
668 668  (((
669 669  The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
670 670  )))
... ... @@ -673,6 +673,7 @@
673 673  
674 674  === 2.8.4  Replace the battery ===
675 675  
739 +
676 676  (((
677 677  The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
678 678  )))
... ... @@ -681,6 +681,7 @@
681 681  
682 682  = 3. ​ Access NB-IoT Module =
683 683  
748 +
684 684  (((
685 685  Users can directly access the AT command set of the NB-IoT module.
686 686  )))
... ... @@ -687,6 +687,8 @@
687 687  
688 688  (((
689 689  The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
755 +
756 +
690 690  )))
691 691  
692 692  [[image:1657333200519-600.png]]
... ... @@ -695,11 +695,13 @@
695 695  
696 696  = 4.  Using the AT Commands =
697 697  
765 +
698 698  == 4.1  Access AT Commands ==
699 699  
700 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
701 701  
769 +See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]
702 702  
771 +
703 703  AT+<CMD>?  : Help on <CMD>
704 704  
705 705  AT+<CMD>         : Run <CMD>
... ... @@ -773,6 +773,7 @@
773 773  
774 774  = ​5.  FAQ =
775 775  
845 +
776 776  == 5.1 ​ How to Upgrade Firmware ==
777 777  
778 778  
... ... @@ -785,7 +785,7 @@
785 785  )))
786 786  
787 787  (((
788 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
858 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
789 789  )))
790 790  
791 791  
... ... @@ -792,6 +792,7 @@
792 792  
793 793  = 6.  Trouble Shooting =
794 794  
865 +
795 795  == 6.1  ​Connection problem when uploading firmware ==
796 796  
797 797  
... ... @@ -807,6 +807,7 @@
807 807  
808 808  == 6.2  AT Command input doesn't work ==
809 809  
881 +
810 810  (((
811 811  In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
812 812  
... ... @@ -832,7 +832,7 @@
832 832  
833 833  (% style="color:#037691" %)**Package Includes**:
834 834  
835 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
907 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
836 836  * External antenna x 1
837 837  )))
838 838  
... ... @@ -841,7 +841,6 @@
841 841  
842 842  (% style="color:#037691" %)**Dimension and weight**:
843 843  
844 -
845 845  * Device Size: 13.0 x 5 x 4.5 cm
846 846  * Device Weight: 150g
847 847  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -857,5 +857,8 @@
857 857  
858 858  = 9.  Support =
859 859  
931 +
860 860  * 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.
861 861  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
934 +
935 +
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0