Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.18 >
edited by Xiaoling
on 2022/07/09 18:08
To version < 121.1 >
edited by David Huang
on 2022/09/08 16:31
>
Change comment: Uploaded new attachment "image-20220908163102-2.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.David
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
... ... @@ -55,6 +55,7 @@
55 55  
56 56  
57 57  
73 +
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -63,6 +63,8 @@
63 63  * Supply Voltage: 2.1v ~~ 3.6v
64 64  * Operating Temperature: -40 ~~ 85°C
65 65  
82 +
83 +
66 66  (% style="color:#037691" %)**NB-IoT Spec:**
67 67  
68 68  * - B1 @H-FDD: 2100MHz
... ... @@ -72,9 +72,10 @@
72 72  * - B20 @H-FDD: 800MHz
73 73  * - B28 @H-FDD: 700MHz
74 74  
75 -(% style="color:#037691" %)**Battery:**
76 76  
77 77  
95 +(% style="color:#037691" %)**Battery:**
96 +
78 78  * Li/SOCI2 un-chargeable battery
79 79  * Capacity: 8500mAh
80 80  * Self Discharge: <1% / Year @ 25°C
... ... @@ -83,8 +83,10 @@
83 83  
84 84  
85 85  
105 +
86 86  == ​1.4  Applications ==
87 87  
108 +
88 88  * Smart Buildings & Home Automation
89 89  * Logistics and Supply Chain Management
90 90  * Smart Metering
... ... @@ -96,15 +96,20 @@
96 96  ​
97 97  
98 98  
99 -== 1.5  Pin Definitions ==
100 100  
121 +== 1.5  Pin Definitions & Switch ==
122 +
123 +
101 101  N95S31B use the mother board from NBSN95 which as below.
102 102  
126 +
103 103  [[image:image-20220709144723-1.png]]
104 104  
105 105  
130 +
106 106  === 1.5.1 Jumper JP2 ===
107 107  
133 +
108 108  Power on Device when put this jumper.
109 109  
110 110  
... ... @@ -111,14 +111,20 @@
111 111  
112 112  === 1.5.2 BOOT MODE / SW1 ===
113 113  
140 +
141 +(((
114 114  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 +)))
115 115  
145 +(((
116 116  2) Flash: work mode, device starts to work and send out console output for further debug
147 +)))
117 117  
118 118  
119 119  
120 120  === 1.5.3 Reset Button ===
121 121  
153 +
122 122  Press to reboot the device.
123 123  
124 124  
... ... @@ -125,13 +125,18 @@
125 125  
126 126  === 1.5.4 LED ===
127 127  
160 +
128 128  It will flash:
129 129  
130 130  1. When boot the device in flash mode
131 131  1. Send an uplink packet
132 132  
166 +
167 +
168 +
133 133  = 2.  Use N95S31B to communicate with IoT Server =
134 134  
171 +
135 135  == 2.1  How it works ==
136 136  
137 137  
... ... @@ -148,7 +148,7 @@
148 148  
149 149  )))
150 150  
151 -[[image:1657350248151-650.png]]
188 +[[image:1657520100595-569.png]]
152 152  
153 153  (((
154 154  
... ... @@ -164,26 +164,49 @@
164 164  [[image:image-20220709150546-2.png]]
165 165  
166 166  
204 +
167 167  === 2.2.1 Test Requirement ===
168 168  
169 169  
208 +(((
170 170  To use N95S31B in your city, make sure meet below requirements:
210 +)))
171 171  
172 -* Your local operator has already distributed a NB-IoT Network there.
173 -* The local NB-IoT network used the band that N95S31B supports.
174 -* 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 +)))
175 175  
222 +(((
176 176  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
224 +)))
177 177  
226 +(((
178 178  N95S31B supports different communication protocol such as :
228 +)))
179 179  
180 180  (((
181 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
182 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
183 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
184 -* 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 +)))
185 185  
244 +(((
186 186  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 +)))
187 187  
188 188  
189 189  )))
... ... @@ -194,6 +194,7 @@
194 194  
195 195  === 2.2.3  Insert SIM card ===
196 196  
257 +
197 197  (((
198 198  Insert the NB-IoT Card get from your provider.
199 199  )))
... ... @@ -209,14 +209,18 @@
209 209  
210 210  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
211 211  
273 +
212 212  (((
213 213  (((
214 214  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 +
215 215  )))
216 216  )))
217 217  
218 218  [[image:1657351312545-300.png]]
219 219  
284 +
220 220  **Connection:**
221 221  
222 222   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -240,8 +240,9 @@
240 240  
241 241  [[image:1657329814315-101.png]]
242 242  
308 +
243 243  (((
244 -(% 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]]**
245 245  )))
246 246  
247 247  
... ... @@ -248,9 +248,10 @@
248 248  
249 249  === 2.2.5  Use CoAP protocol to uplink data ===
250 250  
251 -(% 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/]]
252 252  
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/]]**
253 253  
320 +
254 254  (((
255 255  **Use below commands:**
256 256  )))
... ... @@ -289,6 +289,8 @@
289 289  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
290 290  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
291 291  
359 +
360 +
292 292  [[image:1657352391268-297.png]]
293 293  
294 294  
... ... @@ -298,6 +298,7 @@
298 298  
299 299  === 2.2.7  Use MQTT protocol to uplink data ===
300 300  
370 +
301 301  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
302 302  
303 303  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
... ... @@ -308,11 +308,14 @@
308 308  * (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
309 309  * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
310 310  
381 +
382 +
311 311  [[image:1657352634421-276.png]]
312 312  
313 313  
314 314  [[image:1657352645687-385.png]]
315 315  
388 +
316 316  (((
317 317  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.
318 318  )))
... ... @@ -326,11 +326,14 @@
326 326  
327 327  === 2.2.8  Use TCP protocol to uplink data ===
328 328  
402 +
329 329  This feature is supported since firmware version v110
330 330  
331 331  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
332 332  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
333 333  
408 +
409 +
334 334  [[image:1657352898400-901.png]]
335 335  
336 336  
... ... @@ -340,6 +340,7 @@
340 340  
341 341  === 2.2.9  Change Update Interval ===
342 342  
419 +
343 343  User can use below command to change the (% style="color:green" %)**uplink interval**.
344 344  
345 345  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -353,52 +353,88 @@
353 353  == 2.3  Uplink Payload ==
354 354  
355 355  
356 -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 +)))
357 357  
358 358  
438 +(((
359 359  For example:
440 +)))
360 360  
361 - (% 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 +)))
362 362  
363 363  
447 +(((
364 364  The uplink payloads are composed in  ASCII String. For example:
449 +)))
365 365  
451 +(((
366 366  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
453 +)))
367 367  
455 +(((
368 368  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
457 +)))
369 369  
370 370  
460 +(((
371 371  (% style="color:red" %)**NOTE:**
462 +)))
372 372  
373 373  (% style="color:red" %)
374 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
375 -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.**
376 376  
377 377  
472 +
473 +
474 +)))
475 +
378 378  === 2.3.1  Payload Analyze ===
379 379  
478 +
380 380  N95S31B uplink payload includes in total 21 bytes
381 381  
382 382  
383 383  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
384 -|=(% style="width: 50px;" %)(((
483 +|=(% style="width: 60px;" %)(((
385 385  **Size(bytes)**
386 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 60px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**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**
387 387  |(% 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 +(((
388 388  Reserve/ Same as NBSN95 CFGMOD=1
489 +)))
389 389  
491 +(((
390 390  No function here.
493 +)))
391 391  )))|(% style="width:77px" %)(((
495 +(((
392 392  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
497 +)))
393 393  
499 +(((
394 394  By SHT31
501 +)))
395 395  )))|(% style="width:80px" %)(((
503 +(((
396 396  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
505 +)))
397 397  
507 +(((
398 398  By SHT31
399 399  )))
510 +)))
400 400  
401 401  (((
513 +
514 +
402 402  (((
403 403  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
404 404  )))
... ... @@ -431,6 +431,7 @@
431 431  
432 432  === 2.3.2  Device ID ===
433 433  
547 +
434 434  (((
435 435  By default, the Device ID equal to the last 6 bytes of IMEI.
436 436  )))
... ... @@ -456,14 +456,25 @@
456 456  === 2.3.3  Version Info ===
457 457  
458 458  
573 +(((
459 459  These bytes include the hardware and software version.
575 +)))
460 460  
577 +(((
461 461  Higher byte: Specify hardware version: always 0x00 for N95S31B
579 +)))
462 462  
581 +(((
463 463  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
583 +)))
464 464  
585 +(((
586 +
587 +)))
465 465  
589 +(((
466 466  For example: 0x00 6E: this device is N95S31B with firmware version 110.
591 +)))
467 467  
468 468  (((
469 469  
... ... @@ -472,6 +472,7 @@
472 472  
473 473  === 2.3.4  Battery Info ===
474 474  
600 +
475 475  (((
476 476  Ex1: 0x0B45 = 2885mV
477 477  )))
... ... @@ -484,6 +484,7 @@
484 484  
485 485  === 2.3.5  Signal Strength ===
486 486  
613 +
487 487  (((
488 488  NB-IoT Network signal Strength.
489 489  )))
... ... @@ -516,6 +516,7 @@
516 516  
517 517  === 2.3.6  Temperature & Humidity ===
518 518  
646 +
519 519  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
520 520  
521 521  [[image:image-20220709161741-3.png]]
... ... @@ -534,8 +534,9 @@
534 534  
535 535  == 2.4  Downlink Payload ==
536 536  
537 -By default, NDDS75 prints the downlink payload to console port.
538 538  
666 +By default, N95S31B prints the downlink payload to console port.
667 +
539 539  [[image:image-20220709100028-1.png]]
540 540  
541 541  
... ... @@ -572,7 +572,7 @@
572 572  )))
573 573  
574 574  (((
575 -If payload = 0x04FF, it will reset the NDDS75
704 +If payload = 0x04FF, it will reset the N95S31B
576 576  )))
577 577  
578 578  
... ... @@ -586,6 +586,7 @@
586 586  
587 587  == 2.5  ​Battery Analysis ==
588 588  
718 +
589 589  === 2.5.1  ​Battery Type ===
590 590  
591 591  
... ... @@ -613,8 +613,9 @@
613 613  
614 614  === 2.5.2  Power consumption Analyze ===
615 615  
746 +
616 616  (((
617 -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.
618 618  )))
619 619  
620 620  (((
... ... @@ -624,6 +624,7 @@
624 624  
625 625  === 2.5.3  ​Battery Note ===
626 626  
758 +
627 627  (((
628 628  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.
629 629  )))
... ... @@ -646,6 +646,7 @@
646 646  
647 647  = 3. ​ Access NB-IoT Module =
648 648  
781 +
649 649  (((
650 650  Users can directly access the AT command set of the NB-IoT module.
651 651  )))
... ... @@ -652,6 +652,8 @@
652 652  
653 653  (((
654 654  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 +
655 655  )))
656 656  
657 657  [[image:1657333200519-600.png]]
... ... @@ -660,11 +660,13 @@
660 660  
661 661  = 4.  Using the AT Commands =
662 662  
798 +
663 663  == 4.1  Access AT Commands ==
664 664  
665 -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/]]
666 666  
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]]
667 667  
804 +
668 668  AT+<CMD>?  : Help on <CMD>
669 669  
670 670  AT+<CMD>         : Run <CMD>
... ... @@ -738,6 +738,7 @@
738 738  
739 739  = ​5.  FAQ =
740 740  
878 +
741 741  == 5.1 ​ How to Upgrade Firmware ==
742 742  
743 743  
... ... @@ -752,13 +752,16 @@
752 752  (((
753 753  
754 754  
755 -(% 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.**
756 756  )))
896 +)))
757 757  
758 758  
759 759  
760 760  = 6.  Trouble Shooting =
761 761  
902 +
762 762  == 6.1  ​Connection problem when uploading firmware ==
763 763  
764 764  
... ... @@ -774,6 +774,7 @@
774 774  
775 775  == 6.2  AT Command input doesn't work ==
776 776  
918 +
777 777  (((
778 778  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.
779 779  
... ... @@ -823,5 +823,9 @@
823 823  
824 824  = 9.  Support =
825 825  
968 +
826 826  * 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.
827 827  * 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
image-20220908154949-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +58.5 KB
Content
image-20220908163102-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +29.7 KB
Content

Applications

Navigation

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