Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 106.1 >
edited by Edwin Chen
on 2022/10/09 00:06
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -71,6 +71,9 @@
71 71  * Micro SIM card slot for NB-IoT SIM
72 72  * 8500mAh Battery for long term use
73 73  
74 +
75 +
76 +
74 74  == 1.3  Specification ==
75 75  
76 76  
... ... @@ -79,6 +79,8 @@
79 79  * Supply Voltage: 2.1v ~~ 3.6v
80 80  * Operating Temperature: -40 ~~ 85°C
81 81  
85 +
86 +
82 82  (% style="color:#037691" %)**NB-IoT Spec:**
83 83  
84 84  * - B1 @H-FDD: 2100MHz
... ... @@ -88,6 +88,8 @@
88 88  * - B20 @H-FDD: 800MHz
89 89  * - B28 @H-FDD: 700MHz
90 90  
96 +
97 +
91 91  (% style="color:#037691" %)**Battery:**
92 92  
93 93  * Li/SOCI2 un-chargeable battery
... ... @@ -96,11 +96,16 @@
96 96  * Max continuously current: 130mA
97 97  * Max boost current: 2A, 1 second
98 98  
106 +
107 +
99 99  (% style="color:#037691" %)**Power Consumption**
100 100  
101 101  * STOP Mode: 10uA @ 3.3v
102 102  * Max transmit power: 350mA@3.3v
103 103  
113 +
114 +
115 +
104 104  == ​1.4  Applications ==
105 105  
106 106  
... ... @@ -164,6 +164,8 @@
164 164  * The local NB-IoT network used the band that NDDS75 supports.
165 165  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
166 166  
179 +
180 +
167 167  (((
168 168  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.
169 169  )))
... ... @@ -201,13 +201,13 @@
201 201  [[image:image-20220709092052-2.png]]
202 202  
203 203  
204 -(% style="color:blue" %)**Connection:**
218 +**Connection:**
205 205  
206 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
220 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
207 207  
208 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
222 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
209 209  
210 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
224 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
211 211  
212 212  
213 213  In the PC, use below serial tool settings:
... ... @@ -245,10 +245,10 @@
245 245  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
246 246  )))
247 247  * (((
248 -(% 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
249 249  )))
250 250  * (((
251 -(% 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
252 252  
253 253  
254 254  
... ... @@ -256,8 +256,6 @@
256 256  
257 257  (((
258 258  For parameter description, please refer to AT command set
259 -
260 -
261 261  )))
262 262  
263 263  [[image:1657330452568-615.png]]
... ... @@ -266,8 +266,6 @@
266 266  
267 267  (((
268 268  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.
269 -
270 -
271 271  )))
272 272  
273 273  [[image:1657330472797-498.png]]
... ... @@ -277,10 +277,12 @@
277 277  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
278 278  
279 279  
280 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
281 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
282 -* (% 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
283 283  
294 +
295 +
284 284  [[image:1657330501006-241.png]]
285 285  
286 286  
... ... @@ -291,14 +291,16 @@
291 291  === 2.2.6 Use MQTT protocol to uplink data ===
292 292  
293 293  
294 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
295 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
296 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
297 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
298 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
299 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
300 -* (% 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
301 301  
314 +
315 +
302 302  [[image:1657249978444-674.png]]
303 303  
304 304  
... ... @@ -314,9 +314,11 @@
314 314  === 2.2.7 Use TCP protocol to uplink data ===
315 315  
316 316  
317 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
318 -* (% 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
319 319  
334 +
335 +
320 320  [[image:image-20220709093918-1.png]]
321 321  
322 322  
... ... @@ -329,31 +329,22 @@
329 329  
330 330  User can use below command to change the (% style="color:green" %)**uplink interval**.
331 331  
332 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
348 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
333 333  
334 -(((
335 -
336 336  
337 337  
338 -(% style="color:red" %)**NOTE:**
339 -
340 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
341 -
342 -(% 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.**
343 343  )))
344 344  
345 -(% 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).**
346 346  
347 347  
348 -
349 349  == 2.3  Uplink Payload ==
350 350  
351 351  
352 -=== 2.3.1  Before Firmware v1.3.2 ===
353 -
354 -
355 355  In this mode, uplink payload includes in total 14 bytes
356 356  
363 +
357 357  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
358 358  |=(% style="width: 60px;" %)(((
359 359  **Size(bytes)**
... ... @@ -369,7 +369,7 @@
369 369  
370 370  
371 371  (((
372 -The payload is **ASCII** string, representative same HEX:
379 +The payload is ASCII string, representative same HEX:
373 373  )))
374 374  
375 375  (((
... ... @@ -380,11 +380,11 @@
380 380  Device ID: 0x724031556159 = 724031556159
381 381  )))
382 382  * (((
383 -Version:  0x0064=100=1.0.0
390 +Version: 0x0064=100=1.0.0
384 384  )))
385 385  
386 386  * (((
387 -BAT:  0x0c6c = 3180 mV = 3.180V
394 +BAT: 0x0c6c = 3180 mV = 3.180V
388 388  )))
389 389  * (((
390 390  Signal: 0x19 = 25
... ... @@ -397,41 +397,9 @@
397 397  
398 398  
399 399  
400 -
401 401  
402 402  )))
403 403  
404 -=== **2.3.2  Since firmware v1.3.2** ===
405 -
406 -
407 -In this mode, uplink payload includes 69 bytes in total by default.
408 -
409 -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.
410 -
411 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
412 -|(% 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
413 -|(% 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.......
414 -
415 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
416 -
417 -[[image:image-20220908175246-1.png]]
418 -
419 -
420 -The payload is ASCII string, representative same HEX:
421 -
422 -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:
423 -
424 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
425 -* (% style="color:red" %)Version: 0x0084=132=1.3.2
426 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
427 -* (% style="color:blue" %)Singal: 0x1e = 30
428 -* (% style="color:red" %)Mod: 0x01 = 1
429 -* Interrupt: 0x00= 0
430 -* Distance: 0x0039= 57 = 57
431 -* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
432 -* Distance,Time stamp : 00396319baf0
433 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
434 -
435 435  == 2.4  Payload Explanation and Sensor Interface ==
436 436  
437 437  
... ... @@ -449,7 +449,7 @@
449 449  )))
450 450  
451 451  (((
452 -(% style="color:blue" %)**Example :**
427 +**Example:**
453 453  )))
454 454  
455 455  (((
... ... @@ -457,23 +457,11 @@
457 457  )))
458 458  
459 459  (((
460 -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.
461 461  )))
462 462  
463 463  
464 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
465 465  
466 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
467 -
468 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
469 -
470 -
471 -(% style="color:blue" %)**Example :**
472 -
473 -AT+DEUI=868411056754138
474 -
475 -
476 -
477 477  === 2.4.2  Version Info ===
478 478  
479 479  
... ... @@ -568,7 +568,7 @@
568 568  )))
569 569  
570 570  (((
571 -(% 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]])**.**
572 572  )))
573 573  
574 574  
... ... @@ -670,55 +670,9 @@
670 670  
671 671  
672 672  
673 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
636 +== 2.6  ​LED Indicator ==
674 674  
675 675  
676 -(% style="color:blue" %)** ➢ AT Command:**
677 -
678 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
679 -
680 -² When min=0, and max≠0, Alarm higher than max
681 -
682 -² When min≠0, and max=0, Alarm lower than min
683 -
684 -² When min≠0 and max≠0, Alarm higher than max or lower than min
685 -
686 -
687 -(% style="color:blue" %)** Example:**
688 -
689 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
690 -
691 -
692 -
693 -== 2.7  Set the number of data to be uploaded and the recording time ==
694 -
695 -
696 -(% style="color:blue" %)** ➢ AT Command:**
697 -
698 -* (% 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)
699 -* (% 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.
700 -
701 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
702 -
703 -[[image:image-20221009000513-1.png||height="732" width="1018"]]
704 -
705 -
706 -
707 -== 2.8  Read or Clear cached data ==
708 -
709 -
710 -(% style="color:blue" %)** ➢ AT Command:**
711 -
712 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
713 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
714 -
715 -[[image:image-20220908175333-2.png]]
716 -
717 -
718 -
719 -== 2.9  ​LED Indicator ==
720 -
721 -
722 722  The NDDS75 has an internal LED which is to show the status of different state.
723 723  
724 724  
... ... @@ -733,7 +733,7 @@
733 733  
734 734  
735 735  
736 -== 2.10  ​Firmware Change Log ==
653 +== 2.7  ​Firmware Change Log ==
737 737  
738 738  
739 739  (((
... ... @@ -750,10 +750,10 @@
750 750  
751 751  
752 752  
753 -== 2.11  ​Battery Analysis ==
670 +== 2.8  ​Battery Analysis ==
754 754  
755 755  
756 -=== 2.11.1  ​Battery Type ===
673 +=== 2.8.1  ​Battery Type ===
757 757  
758 758  
759 759  (((
... ... @@ -778,7 +778,7 @@
778 778  
779 779  
780 780  
781 -=== 2.11.2  Power consumption Analyze ===
698 +=== 2.8.2  Power consumption Analyze ===
782 782  
783 783  
784 784  (((
... ... @@ -817,7 +817,7 @@
817 817  
818 818  
819 819  
820 -=== 2.11.3  ​Battery Note ===
737 +=== 2.8.3  ​Battery Note ===
821 821  
822 822  
823 823  (((
... ... @@ -826,7 +826,7 @@
826 826  
827 827  
828 828  
829 -=== 2.11.4  Replace the battery ===
746 +=== 2.8.4  Replace the battery ===
830 830  
831 831  
832 832  (((
... ... @@ -861,90 +861,74 @@
861 861  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]]
862 862  
863 863  
864 -AT+<CMD>?  :  Help on <CMD>
781 +AT+<CMD>?  : Help on <CMD>
865 865  
866 -AT+<CMD>         :  Run <CMD>
783 +AT+<CMD>         : Run <CMD>
867 867  
868 -AT+<CMD>=<value> :  Set the value
785 +AT+<CMD>=<value> : Set the value
869 869  
870 -AT+<CMD>=?  :  Get the value
787 +AT+<CMD>=?  : Get the value
871 871  
872 872  
873 873  (% style="color:#037691" %)**General Commands**(%%)      
874 874  
875 -AT  :  Attention       
792 +AT  : Attention       
876 876  
877 -AT?  :  Short Help     
794 +AT?  : Short Help     
878 878  
879 -ATZ  :  MCU Reset    
796 +ATZ  : MCU Reset    
880 880  
881 -AT+TDC  :  Application Data Transmission Interval
798 +AT+TDC  : Application Data Transmission Interval
882 882  
883 -AT+CFG  :  Print all configurations
800 +AT+CFG  : Print all configurations
884 884  
885 -AT+CFGMOD           :  Working mode selection
802 +AT+CFGMOD           : Working mode selection
886 886  
887 -AT+INTMOD            :  Set the trigger interrupt mode
804 +AT+INTMOD            : Set the trigger interrupt mode
888 888  
889 -AT+5VT  :  Set extend the time of 5V power  
806 +AT+5VT  : Set extend the time of 5V power  
890 890  
891 -AT+PRO  :  Choose agreement
808 +AT+PRO  : Choose agreement
892 892  
893 -AT+WEIGRE  :  Get weight or set weight to 0
810 +AT+WEIGRE  : Get weight or set weight to 0
894 894  
895 -AT+WEIGAP  :  Get or Set the GapValue of weight
812 +AT+WEIGAP  : Get or Set the GapValue of weight
896 896  
897 -AT+RXDL  :  Extend the sending and receiving time
814 +AT+RXDL  : Extend the sending and receiving time
898 898  
899 -AT+CNTFAC  :  Get or set counting parameters
816 +AT+CNTFAC  : Get or set counting parameters
900 900  
901 -AT+SERVADDR  :  Server Address
818 +AT+SERVADDR  : Server Address
902 902  
903 -AT+TR  :  Get or Set record time"
904 904  
905 -AT+APN     :  Get or set the APN
906 -
907 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
908 -
909 -AT+DNSCFG  : Get or Set DNS Server
910 -
911 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
912 -
913 -AT+NOUD  :  Get or Set the number of data to be uploaded
914 -
915 -AT+CDP     :  Read or Clear cached data
916 -
917 -AT+LDDSALARM :  Get or Set alarm of distance
918 -
919 -
920 920  (% style="color:#037691" %)**COAP Management**      
921 921  
922 -AT+URI            :  Resource parameters
823 +AT+URI            : Resource parameters
923 923  
924 924  
925 925  (% style="color:#037691" %)**UDP Management**
926 926  
927 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
828 +AT+CFM          : Upload confirmation mode (only valid for UDP)
928 928  
929 929  
930 930  (% style="color:#037691" %)**MQTT Management**
931 931  
932 -AT+CLIENT  :  Get or Set MQTT client
833 +AT+CLIENT               : Get or Set MQTT client
933 933  
934 -AT+UNAME  :  Get or Set MQTT Username
835 +AT+UNAME  : Get or Set MQTT Username
935 935  
936 -AT+PWD  :  Get or Set MQTT password
837 +AT+PWD                  : Get or Set MQTT password
937 937  
938 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
839 +AT+PUBTOPIC  : Get or Set MQTT publish topic
939 939  
940 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
841 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
941 941  
942 942  
943 943  (% style="color:#037691" %)**Information**          
944 944  
945 -AT+FDR  :  Factory Data Reset
846 +AT+FDR  : Factory Data Reset
946 946  
947 -AT+PWORD  :  Serial Access Password
848 +AT+PWORD  : Serial Access Password
948 948  
949 949  
950 950  
... ... @@ -1040,3 +1040,5 @@
1040 1040  
1041 1041  * 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.
1042 1042  * 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