Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.19 >
edited by Xiaoling
on 2022/07/09 18:14
To version < 119.3 >
edited by Xiaoling
on 2022/08/22 15:05
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,21 +17,35 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 +
20 20  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21 21  
22 22  (((
23 23  
24 24  
26 +(((
25 25  The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
28 +)))
26 26  
30 +(((
27 27  The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
32 +)))
28 28  
34 +(((
29 29  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
36 +)))
30 30  
38 +(((
31 31  N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
40 +)))
32 32  
42 +(((
43 +
44 +)))
33 33  
46 +(((
34 34  ~* make sure you have NB-IoT coverage locally.
48 +)))
35 35  
36 36  
37 37  )))
... ... @@ -42,6 +42,7 @@
42 42  
43 43  == 1.2 ​ Features ==
44 44  
59 +
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 46  * Monitor Temperature & Humidity via SHT31
47 47  * AT Commands to change parameters
... ... @@ -54,6 +54,8 @@
54 54  * 8500mAh Battery for long term use
55 55  
56 56  
72 +
73 +
57 57  == 1.3  Specification ==
58 58  
59 59  
... ... @@ -62,6 +62,8 @@
62 62  * Supply Voltage: 2.1v ~~ 3.6v
63 63  * Operating Temperature: -40 ~~ 85°C
64 64  
82 +
83 +
65 65  (% style="color:#037691" %)**NB-IoT Spec:**
66 66  
67 67  * - B1 @H-FDD: 2100MHz
... ... @@ -71,9 +71,10 @@
71 71  * - B20 @H-FDD: 800MHz
72 72  * - B28 @H-FDD: 700MHz
73 73  
74 -(% style="color:#037691" %)**Battery:**
75 75  
76 76  
95 +(% style="color:#037691" %)**Battery:**
96 +
77 77  * Li/SOCI2 un-chargeable battery
78 78  * Capacity: 8500mAh
79 79  * Self Discharge: <1% / Year @ 25°C
... ... @@ -81,8 +81,11 @@
81 81  * Max boost current: 2A, 1 second
82 82  
83 83  
104 +
105 +
84 84  == ​1.4  Applications ==
85 85  
108 +
86 86  * Smart Buildings & Home Automation
87 87  * Logistics and Supply Chain Management
88 88  * Smart Metering
... ... @@ -94,15 +94,20 @@
94 94  ​
95 95  
96 96  
97 -== 1.5  Pin Definitions ==
98 98  
121 +== 1.5  Pin Definitions & Switch ==
122 +
123 +
99 99  N95S31B use the mother board from NBSN95 which as below.
100 100  
126 +
101 101  [[image:image-20220709144723-1.png]]
102 102  
103 103  
130 +
104 104  === 1.5.1 Jumper JP2 ===
105 105  
133 +
106 106  Power on Device when put this jumper.
107 107  
108 108  
... ... @@ -109,14 +109,20 @@
109 109  
110 110  === 1.5.2 BOOT MODE / SW1 ===
111 111  
140 +
141 +(((
112 112  1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
143 +)))
113 113  
145 +(((
114 114  2) Flash: work mode, device starts to work and send out console output for further debug
147 +)))
115 115  
116 116  
117 117  
118 118  === 1.5.3 Reset Button ===
119 119  
153 +
120 120  Press to reboot the device.
121 121  
122 122  
... ... @@ -123,13 +123,18 @@
123 123  
124 124  === 1.5.4 LED ===
125 125  
160 +
126 126  It will flash:
127 127  
128 128  1. When boot the device in flash mode
129 129  1. Send an uplink packet
130 130  
166 +
167 +
168 +
131 131  = 2.  Use N95S31B to communicate with IoT Server =
132 132  
171 +
133 133  == 2.1  How it works ==
134 134  
135 135  
... ... @@ -146,7 +146,7 @@
146 146  
147 147  )))
148 148  
149 -[[image:1657350248151-650.png]]
188 +[[image:1657520100595-569.png]]
150 150  
151 151  (((
152 152  
... ... @@ -162,26 +162,49 @@
162 162  [[image:image-20220709150546-2.png]]
163 163  
164 164  
204 +
165 165  === 2.2.1 Test Requirement ===
166 166  
167 167  
208 +(((
168 168  To use N95S31B in your city, make sure meet below requirements:
210 +)))
169 169  
170 -* Your local operator has already distributed a NB-IoT Network there.
171 -* The local NB-IoT network used the band that N95S31B supports.
172 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
212 +* (((
213 +Your local operator has already distributed a NB-IoT Network there.
214 +)))
215 +* (((
216 +The local NB-IoT network used the band that N95S31B supports.
217 +)))
218 +* (((
219 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
220 +)))
173 173  
222 +(((
174 174  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
224 +)))
175 175  
226 +(((
176 176  N95S31B supports different communication protocol such as :
228 +)))
177 177  
178 178  (((
179 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
180 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
181 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
182 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
231 +* (((
232 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
233 +)))
234 +* (((
235 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
236 +)))
237 +* (((
238 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
239 +)))
240 +* (((
241 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
242 +)))
183 183  
244 +(((
184 184  We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
246 +)))
185 185  
186 186  
187 187  )))
... ... @@ -192,6 +192,7 @@
192 192  
193 193  === 2.2.3  Insert SIM card ===
194 194  
257 +
195 195  (((
196 196  Insert the NB-IoT Card get from your provider.
197 197  )))
... ... @@ -207,14 +207,18 @@
207 207  
208 208  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
209 209  
273 +
210 210  (((
211 211  (((
212 212  User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
277 +
278 +
213 213  )))
214 214  )))
215 215  
216 216  [[image:1657351312545-300.png]]
217 217  
284 +
218 218  **Connection:**
219 219  
220 220   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -238,8 +238,9 @@
238 238  
239 239  [[image:1657329814315-101.png]]
240 240  
308 +
241 241  (((
242 -(% style="color:red" %)Note: the valid AT Commands can be found at:  (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]
310 +(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
243 243  )))
244 244  
245 245  
... ... @@ -246,9 +246,10 @@
246 246  
247 247  === 2.2.5  Use CoAP protocol to uplink data ===
248 248  
249 -(% 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/]]
250 250  
318 +(% 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/]]**
251 251  
320 +
252 252  (((
253 253  **Use below commands:**
254 254  )))
... ... @@ -287,6 +287,8 @@
287 287  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
288 288  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
289 289  
359 +
360 +
290 290  [[image:1657352391268-297.png]]
291 291  
292 292  
... ... @@ -296,6 +296,7 @@
296 296  
297 297  === 2.2.7  Use MQTT protocol to uplink data ===
298 298  
370 +
299 299  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
300 300  
301 301  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
... ... @@ -306,11 +306,14 @@
306 306  * (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
307 307  * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
308 308  
381 +
382 +
309 309  [[image:1657352634421-276.png]]
310 310  
311 311  
312 312  [[image:1657352645687-385.png]]
313 313  
388 +
314 314  (((
315 315  To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period.
316 316  )))
... ... @@ -324,11 +324,14 @@
324 324  
325 325  === 2.2.8  Use TCP protocol to uplink data ===
326 326  
402 +
327 327  This feature is supported since firmware version v110
328 328  
329 329  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
330 330  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
331 331  
408 +
409 +
332 332  [[image:1657352898400-901.png]]
333 333  
334 334  
... ... @@ -338,6 +338,7 @@
338 338  
339 339  === 2.2.9  Change Update Interval ===
340 340  
419 +
341 341  User can use below command to change the (% style="color:green" %)**uplink interval**.
342 342  
343 343  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -351,29 +351,52 @@
351 351  == 2.3  Uplink Payload ==
352 352  
353 353  
354 -NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
433 +(((
434 +N95S31B has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
435 +)))
355 355  
356 356  
438 +(((
357 357  For example:
440 +)))
358 358  
359 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
442 +(((
443 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
444 +)))
360 360  
361 361  
447 +(((
362 362  The uplink payloads are composed in  ASCII String. For example:
449 +)))
363 363  
451 +(((
364 364  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
453 +)))
365 365  
455 +(((
366 366  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
457 +)))
367 367  
368 368  
460 +(((
369 369  (% style="color:red" %)**NOTE:**
462 +)))
370 370  
371 371  (% style="color:red" %)
372 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
373 -1. By default, the device will send an uplink message every 1 hour.
465 +1. (((
466 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
467 +)))
468 +1. (((
469 +**By default, the device will send an uplink message every 1 hour.**
374 374  
471 +
472 +
473 +
474 +)))
475 +
375 375  === 2.3.1  Payload Analyze ===
376 376  
478 +
377 377  N95S31B uplink payload includes in total 21 bytes
378 378  
379 379  
... ... @@ -380,22 +380,36 @@
380 380  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
381 381  |=(% style="width: 60px;" %)(((
382 382  **Size(bytes)**
383 -)))|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
485 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
384 384  |(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
487 +(((
385 385  Reserve/ Same as NBSN95 CFGMOD=1
489 +)))
386 386  
491 +(((
387 387  No function here.
493 +)))
388 388  )))|(% style="width:77px" %)(((
495 +(((
389 389  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
497 +)))
390 390  
499 +(((
391 391  By SHT31
501 +)))
392 392  )))|(% style="width:80px" %)(((
503 +(((
393 393  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
505 +)))
394 394  
507 +(((
395 395  By SHT31
396 396  )))
510 +)))
397 397  
398 398  (((
513 +
514 +
399 399  (((
400 400  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
401 401  )))
... ... @@ -428,6 +428,7 @@
428 428  
429 429  === 2.3.2  Device ID ===
430 430  
547 +
431 431  (((
432 432  By default, the Device ID equal to the last 6 bytes of IMEI.
433 433  )))
... ... @@ -453,14 +453,25 @@
453 453  === 2.3.3  Version Info ===
454 454  
455 455  
573 +(((
456 456  These bytes include the hardware and software version.
575 +)))
457 457  
577 +(((
458 458  Higher byte: Specify hardware version: always 0x00 for N95S31B
579 +)))
459 459  
581 +(((
460 460  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
583 +)))
461 461  
585 +(((
586 +
587 +)))
462 462  
589 +(((
463 463  For example: 0x00 6E: this device is N95S31B with firmware version 110.
591 +)))
464 464  
465 465  (((
466 466  
... ... @@ -469,6 +469,7 @@
469 469  
470 470  === 2.3.4  Battery Info ===
471 471  
600 +
472 472  (((
473 473  Ex1: 0x0B45 = 2885mV
474 474  )))
... ... @@ -481,6 +481,7 @@
481 481  
482 482  === 2.3.5  Signal Strength ===
483 483  
613 +
484 484  (((
485 485  NB-IoT Network signal Strength.
486 486  )))
... ... @@ -513,6 +513,7 @@
513 513  
514 514  === 2.3.6  Temperature & Humidity ===
515 515  
646 +
516 516  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
517 517  
518 518  [[image:image-20220709161741-3.png]]
... ... @@ -531,8 +531,9 @@
531 531  
532 532  == 2.4  Downlink Payload ==
533 533  
534 -By default, NDDS75 prints the downlink payload to console port.
535 535  
666 +By default, N95S31B prints the downlink payload to console port.
667 +
536 536  [[image:image-20220709100028-1.png]]
537 537  
538 538  
... ... @@ -569,7 +569,7 @@
569 569  )))
570 570  
571 571  (((
572 -If payload = 0x04FF, it will reset the NDDS75
704 +If payload = 0x04FF, it will reset the N95S31B
573 573  )))
574 574  
575 575  
... ... @@ -583,6 +583,7 @@
583 583  
584 584  == 2.5  ​Battery Analysis ==
585 585  
718 +
586 586  === 2.5.1  ​Battery Type ===
587 587  
588 588  
... ... @@ -610,8 +610,9 @@
610 610  
611 611  === 2.5.2  Power consumption Analyze ===
612 612  
746 +
613 613  (((
614 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
748 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
615 615  )))
616 616  
617 617  (((
... ... @@ -621,6 +621,7 @@
621 621  
622 622  === 2.5.3  ​Battery Note ===
623 623  
758 +
624 624  (((
625 625  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 uplink data, then the battery life may be decreased.
626 626  )))
... ... @@ -643,6 +643,7 @@
643 643  
644 644  = 3. ​ Access NB-IoT Module =
645 645  
781 +
646 646  (((
647 647  Users can directly access the AT command set of the NB-IoT module.
648 648  )))
... ... @@ -649,6 +649,8 @@
649 649  
650 650  (((
651 651  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/]] 
788 +
789 +
652 652  )))
653 653  
654 654  [[image:1657333200519-600.png]]
... ... @@ -657,11 +657,13 @@
657 657  
658 658  = 4.  Using the AT Commands =
659 659  
798 +
660 660  == 4.1  Access AT Commands ==
661 661  
662 -See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
663 663  
802 +See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
664 664  
804 +
665 665  AT+<CMD>?  : Help on <CMD>
666 666  
667 667  AT+<CMD>         : Run <CMD>
... ... @@ -735,6 +735,7 @@
735 735  
736 736  = ​5.  FAQ =
737 737  
878 +
738 738  == 5.1 ​ How to Upgrade Firmware ==
739 739  
740 740  
... ... @@ -749,13 +749,16 @@
749 749  (((
750 750  
751 751  
752 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
893 +(((
894 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
753 753  )))
896 +)))
754 754  
755 755  
756 756  
757 757  = 6.  Trouble Shooting =
758 758  
902 +
759 759  == 6.1  ​Connection problem when uploading firmware ==
760 760  
761 761  
... ... @@ -771,6 +771,7 @@
771 771  
772 772  == 6.2  AT Command input doesn't work ==
773 773  
918 +
774 774  (((
775 775  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.
776 776  
... ... @@ -820,5 +820,9 @@
820 820  
821 821  = 9.  Support =
822 822  
968 +
823 823  * 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.
824 824  * 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]]
971 +
972 +
973 +
1657520100595-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0