Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 104.7 >
edited by Xiaoling
on 2022/09/15 15:02
To version < 100.6 >
edited by Xiaoling
on 2022/09/06 17:42
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -73,6 +73,7 @@
73 73  
74 74  
75 75  
76 +
76 76  == 1.3  Specification ==
77 77  
78 78  
... ... @@ -81,6 +81,8 @@
81 81  * Supply Voltage: 2.1v ~~ 3.6v
82 82  * Operating Temperature: -40 ~~ 85°C
83 83  
85 +
86 +
84 84  (% style="color:#037691" %)**NB-IoT Spec:**
85 85  
86 86  * - B1 @H-FDD: 2100MHz
... ... @@ -90,6 +90,8 @@
90 90  * - B20 @H-FDD: 800MHz
91 91  * - B28 @H-FDD: 700MHz
92 92  
96 +
97 +
93 93  (% style="color:#037691" %)**Battery:**
94 94  
95 95  * Li/SOCI2 un-chargeable battery
... ... @@ -98,6 +98,8 @@
98 98  * Max continuously current: 130mA
99 99  * Max boost current: 2A, 1 second
100 100  
106 +
107 +
101 101  (% style="color:#037691" %)**Power Consumption**
102 102  
103 103  * STOP Mode: 10uA @ 3.3v
... ... @@ -105,6 +105,7 @@
105 105  
106 106  
107 107  
115 +
108 108  == ​1.4  Applications ==
109 109  
110 110  
... ... @@ -168,6 +168,8 @@
168 168  * The local NB-IoT network used the band that NDDS75 supports.
169 169  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
170 170  
179 +
180 +
171 171  (((
172 172  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.
173 173  )))
... ... @@ -205,13 +205,13 @@
205 205  [[image:image-20220709092052-2.png]]
206 206  
207 207  
208 -(% style="color:blue" %)**Connection:**
218 +**Connection:**
209 209  
210 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
220 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
211 211  
212 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
222 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
213 213  
214 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
224 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
215 215  
216 216  
217 217  In the PC, use below serial tool settings:
... ... @@ -249,10 +249,10 @@
249 249  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
250 250  )))
251 251  * (((
252 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
262 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
253 253  )))
254 254  * (((
255 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
265 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
256 256  
257 257  
258 258  
... ... @@ -260,8 +260,6 @@
260 260  
261 261  (((
262 262  For parameter description, please refer to AT command set
263 -
264 -
265 265  )))
266 266  
267 267  [[image:1657330452568-615.png]]
... ... @@ -270,8 +270,6 @@
270 270  
271 271  (((
272 272  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.
273 -
274 -
275 275  )))
276 276  
277 277  [[image:1657330472797-498.png]]
... ... @@ -281,9 +281,9 @@
281 281  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
282 282  
283 283  
284 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
285 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
286 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
290 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
291 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
292 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
287 287  
288 288  
289 289  
... ... @@ -297,14 +297,16 @@
297 297  === 2.2.6 Use MQTT protocol to uplink data ===
298 298  
299 299  
300 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
301 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
302 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
303 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
304 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
305 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
306 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
306 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
307 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
308 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
309 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
310 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
311 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
312 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
307 307  
314 +
315 +
308 308  [[image:1657249978444-674.png]]
309 309  
310 310  
... ... @@ -320,9 +320,11 @@
320 320  === 2.2.7 Use TCP protocol to uplink data ===
321 321  
322 322  
323 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
324 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
331 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
332 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
325 325  
334 +
335 +
326 326  [[image:image-20220709093918-1.png]]
327 327  
328 328  
... ... @@ -335,31 +335,22 @@
335 335  
336 336  User can use below command to change the (% style="color:green" %)**uplink interval**.
337 337  
338 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
348 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
339 339  
340 -(((
341 -
342 342  
343 343  
344 -(% style="color:red" %)**NOTE:**
345 -
346 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
347 -
348 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
352 +(((
353 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.**
349 349  )))
350 350  
351 -(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
352 352  
353 353  
354 -
355 355  == 2.3  Uplink Payload ==
356 356  
357 357  
358 -=== 2.3.1  Before Firmware v1.3.2 ===
359 -
360 -
361 361  In this mode, uplink payload includes in total 14 bytes
362 362  
363 +
363 363  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
364 364  |=(% style="width: 60px;" %)(((
365 365  **Size(bytes)**
... ... @@ -375,7 +375,7 @@
375 375  
376 376  
377 377  (((
378 -The payload is **ASCII** string, representative same HEX:
379 +The payload is ASCII string, representative same HEX:
379 379  )))
380 380  
381 381  (((
... ... @@ -386,11 +386,11 @@
386 386  Device ID: 0x724031556159 = 724031556159
387 387  )))
388 388  * (((
389 -Version:  0x0064=100=1.0.0
390 +Version: 0x0064=100=1.0.0
390 390  )))
391 391  
392 392  * (((
393 -BAT:  0x0c6c = 3180 mV = 3.180V
394 +BAT: 0x0c6c = 3180 mV = 3.180V
394 394  )))
395 395  * (((
396 396  Signal: 0x19 = 25
... ... @@ -403,43 +403,9 @@
403 403  
404 404  
405 405  
406 -
407 407  
408 408  )))
409 409  
410 -=== **2.3.2  Since firmware v1.3.2** ===
411 -
412 -
413 -In this mode, uplink payload includes 69 bytes in total by default.
414 -
415 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
416 -
417 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
418 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
419 -|(% style="width:95px" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
420 -
421 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
422 -
423 -[[image:image-20220908175246-1.png]]
424 -
425 -
426 -The payload is ASCII string, representative same HEX:
427 -
428 -0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
429 -
430 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
431 -* (% style="color:red" %)Version: 0x0084=132=1.3.2
432 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
433 -* (% style="color:blue" %)Singal: 0x1e = 30
434 -* (% style="color:red" %)Mod: 0x01 = 1
435 -* Interrupt: 0x00= 0
436 -* Distance: 0x0039= 57 = 57
437 -* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
438 -* Distance,Time stamp : 00396319baf0
439 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
440 -
441 -
442 -
443 443  == 2.4  Payload Explanation and Sensor Interface ==
444 444  
445 445  
... ... @@ -457,7 +457,7 @@
457 457  )))
458 458  
459 459  (((
460 -(% style="color:blue" %)**Example :**
427 +**Example:**
461 461  )))
462 462  
463 463  (((
... ... @@ -465,23 +465,11 @@
465 465  )))
466 466  
467 467  (((
468 -The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
435 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
469 469  )))
470 470  
471 471  
472 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
473 473  
474 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
475 -
476 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
477 -
478 -
479 -(% style="color:blue" %)**Example :**
480 -
481 -AT+DEUI=868411056754138
482 -
483 -
484 -
485 485  === 2.4.2  Version Info ===
486 486  
487 487  
... ... @@ -576,7 +576,7 @@
576 576  )))
577 577  
578 578  (((
579 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/  (more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
534 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
580 580  )))
581 581  
582 582  
... ... @@ -678,52 +678,9 @@
678 678  
679 679  
680 680  
681 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
636 +== 2.6  ​LED Indicator ==
682 682  
683 683  
684 -(% style="color:blue" %)** ➢ AT Command:**
685 -
686 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
687 -
688 -² When min=0, and max≠0, Alarm higher than max
689 -
690 -² When min≠0, and max=0, Alarm lower than min
691 -
692 -² When min≠0 and max≠0, Alarm higher than max or lower than min
693 -
694 -
695 -(% style="color:blue" %)** Example:**
696 -
697 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
698 -
699 -
700 -
701 -== 2.7  Set the number of data to be uploaded and the recording time ==
702 -
703 -
704 -(% style="color:blue" %)** ➢ AT Command:**
705 -
706 -* (% style="color:#037691" %)** AT+TR=900** (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
707 -* (% style="color:#037691" %)** AT+NOUD=8**  (%%) ~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
708 -
709 -
710 -
711 -
712 -== 2.8  Read or Clear cached data ==
713 -
714 -
715 -(% style="color:blue" %)** ➢ AT Command:**
716 -
717 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
718 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
719 -
720 -[[image:image-20220908175333-2.png]]
721 -
722 -
723 -
724 -== 2.9  ​LED Indicator ==
725 -
726 -
727 727  The NDDS75 has an internal LED which is to show the status of different state.
728 728  
729 729  
... ... @@ -738,7 +738,7 @@
738 738  
739 739  
740 740  
741 -== 2.10  ​Firmware Change Log ==
653 +== 2.7  ​Firmware Change Log ==
742 742  
743 743  
744 744  (((
... ... @@ -755,10 +755,10 @@
755 755  
756 756  
757 757  
758 -== 2.11  ​Battery Analysis ==
670 +== 2.8  ​Battery Analysis ==
759 759  
760 760  
761 -=== 2.11.1  ​Battery Type ===
673 +=== 2.8.1  ​Battery Type ===
762 762  
763 763  
764 764  (((
... ... @@ -783,7 +783,7 @@
783 783  
784 784  
785 785  
786 -=== 2.11.2  Power consumption Analyze ===
698 +=== 2.8.2  Power consumption Analyze ===
787 787  
788 788  
789 789  (((
... ... @@ -822,7 +822,7 @@
822 822  
823 823  
824 824  
825 -=== 2.11.3  ​Battery Note ===
737 +=== 2.8.3  ​Battery Note ===
826 826  
827 827  
828 828  (((
... ... @@ -831,7 +831,7 @@
831 831  
832 832  
833 833  
834 -=== 2.11.4  Replace the battery ===
746 +=== 2.8.4  Replace the battery ===
835 835  
836 836  
837 837  (((
... ... @@ -866,90 +866,74 @@
866 866  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]]
867 867  
868 868  
869 -AT+<CMD>?  :  Help on <CMD>
781 +AT+<CMD>?  : Help on <CMD>
870 870  
871 -AT+<CMD>         :  Run <CMD>
783 +AT+<CMD>         : Run <CMD>
872 872  
873 -AT+<CMD>=<value> :  Set the value
785 +AT+<CMD>=<value> : Set the value
874 874  
875 -AT+<CMD>=?  :  Get the value
787 +AT+<CMD>=?  : Get the value
876 876  
877 877  
878 878  (% style="color:#037691" %)**General Commands**(%%)      
879 879  
880 -AT  :  Attention       
792 +AT  : Attention       
881 881  
882 -AT?  :  Short Help     
794 +AT?  : Short Help     
883 883  
884 -ATZ  :  MCU Reset    
796 +ATZ  : MCU Reset    
885 885  
886 -AT+TDC  :  Application Data Transmission Interval
798 +AT+TDC  : Application Data Transmission Interval
887 887  
888 -AT+CFG  :  Print all configurations
800 +AT+CFG  : Print all configurations
889 889  
890 -AT+CFGMOD           :  Working mode selection
802 +AT+CFGMOD           : Working mode selection
891 891  
892 -AT+INTMOD            :  Set the trigger interrupt mode
804 +AT+INTMOD            : Set the trigger interrupt mode
893 893  
894 -AT+5VT  :  Set extend the time of 5V power  
806 +AT+5VT  : Set extend the time of 5V power  
895 895  
896 -AT+PRO  :  Choose agreement
808 +AT+PRO  : Choose agreement
897 897  
898 -AT+WEIGRE  :  Get weight or set weight to 0
810 +AT+WEIGRE  : Get weight or set weight to 0
899 899  
900 -AT+WEIGAP  :  Get or Set the GapValue of weight
812 +AT+WEIGAP  : Get or Set the GapValue of weight
901 901  
902 -AT+RXDL  :  Extend the sending and receiving time
814 +AT+RXDL  : Extend the sending and receiving time
903 903  
904 -AT+CNTFAC  :  Get or set counting parameters
816 +AT+CNTFAC  : Get or set counting parameters
905 905  
906 -AT+SERVADDR  :  Server Address
818 +AT+SERVADDR  : Server Address
907 907  
908 -AT+TR  :  Get or Set record time"
909 909  
910 -AT+APN     :  Get or set the APN
911 -
912 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
913 -
914 -AT+DNSCFG  : Get or Set DNS Server
915 -
916 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
917 -
918 -AT+NOUD  :  Get or Set the number of data to be uploaded
919 -
920 -AT+CDP     :  Read or Clear cached data
921 -
922 -AT+LDDSALARM :  Get or Set alarm of distance
923 -
924 -
925 925  (% style="color:#037691" %)**COAP Management**      
926 926  
927 -AT+URI            :  Resource parameters
823 +AT+URI            : Resource parameters
928 928  
929 929  
930 930  (% style="color:#037691" %)**UDP Management**
931 931  
932 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
828 +AT+CFM          : Upload confirmation mode (only valid for UDP)
933 933  
934 934  
935 935  (% style="color:#037691" %)**MQTT Management**
936 936  
937 -AT+CLIENT  :  Get or Set MQTT client
833 +AT+CLIENT               : Get or Set MQTT client
938 938  
939 -AT+UNAME  :  Get or Set MQTT Username
835 +AT+UNAME  : Get or Set MQTT Username
940 940  
941 -AT+PWD  :  Get or Set MQTT password
837 +AT+PWD                  : Get or Set MQTT password
942 942  
943 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
839 +AT+PUBTOPIC  : Get or Set MQTT publish topic
944 944  
945 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
841 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
946 946  
947 947  
948 948  (% style="color:#037691" %)**Information**          
949 949  
950 -AT+FDR  :  Factory Data Reset
846 +AT+FDR  : Factory Data Reset
951 951  
952 -AT+PWORD  :  Serial Access Password
848 +AT+PWORD  : Serial Access Password
953 953  
954 954  
955 955  
... ... @@ -1045,3 +1045,5 @@
1045 1045  
1046 1046  * 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.
1047 1047  * 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]]
944 +
945 +
image-20220908175246-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -31.1 KB
Content

Applications

Navigation

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