Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 100.2 >
edited by Xiaoling
on 2022/07/09 14:53
To version < 115.3 >
edited by Xiaoling
on 2022/07/09 16:59
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -41,7 +41,6 @@
41 41  
42 42  == 1.2 ​ Features ==
43 43  
44 -
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  
57 +
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -83,6 +83,7 @@
83 83  
84 84  
85 85  
86 +
86 86  == ​1.4  Applications ==
87 87  
88 88  * Smart Buildings & Home Automation
... ... @@ -131,19 +131,18 @@
131 131  1. Send an uplink packet
132 132  
133 133  
134 -
135 -
136 136  = 2.  Use N95S31B to communicate with IoT Server =
137 137  
138 138  == 2.1  How it works ==
139 139  
139 +
140 140  (((
141 -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.
141 +The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B 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 N95S31B.
142 142  )))
143 143  
144 144  
145 145  (((
146 -The diagram below shows the working flow in default firmware of NDDS75:
146 +The diagram below shows the working flow in default firmware of N95S31B:
147 147  )))
148 148  
149 149  (((
... ... @@ -150,7 +150,7 @@
150 150  
151 151  )))
152 152  
153 -[[image:1657328659945-416.png]]
153 +[[image:1657350248151-650.png]]
154 154  
155 155  (((
156 156  
... ... @@ -157,30 +157,45 @@
157 157  )))
158 158  
159 159  
160 -== 2.2 ​ Configure the NDDS75 ==
160 +== 2.2 ​ Configure the N95S31B ==
161 161  
162 162  
163 +=== 2.2.1  Power On N95S31B ===
164 +
165 +
166 +[[image:image-20220709150546-2.png]]
167 +
168 +
163 163  === 2.2.1 Test Requirement ===
164 164  
165 -(((
166 -To use NDDS75 in your city, make sure meet below requirements:
167 -)))
168 168  
172 +To use N95S31B in your city, make sure meet below requirements:
173 +
169 169  * Your local operator has already distributed a NB-IoT Network there.
170 -* The local NB-IoT network used the band that NSE01 supports.
175 +* The local NB-IoT network used the band that N95S31B supports.
171 171  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
172 172  
178 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
179 +
180 +N95S31B supports different communication protocol such as :
181 +
173 173  (((
174 -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
175 -)))
183 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
184 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
185 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
186 +* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
176 176  
188 +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.
177 177  
178 -[[image:1657328756309-230.png]]
190 +
191 +)))
179 179  
193 +[[image:1657350625843-586.png]]
180 180  
181 181  
182 -=== 2.2.2 Insert SIM card ===
183 183  
197 +=== 2.2.3  Insert SIM card ===
198 +
184 184  (((
185 185  Insert the NB-IoT Card get from your provider.
186 186  )))
... ... @@ -190,19 +190,19 @@
190 190  )))
191 191  
192 192  
193 -[[image:1657328884227-504.png]]
208 +[[image:1657351240556-536.png]]
194 194  
195 195  
196 196  
197 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
212 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
198 198  
199 199  (((
200 200  (((
201 -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.
216 +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.
202 202  )))
203 203  )))
204 204  
205 -[[image:image-20220709092052-2.png]]
220 +[[image:1657351312545-300.png]]
206 206  
207 207  **Connection:**
208 208  
... ... @@ -222,18 +222,18 @@
222 222  * Flow Control: (% style="color:green" %)**None**
223 223  
224 224  (((
225 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
240 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
226 226  )))
227 227  
228 228  [[image:1657329814315-101.png]]
229 229  
230 230  (((
231 -(% 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/]]
246 +(% 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/]]
232 232  )))
233 233  
234 234  
235 235  
236 -=== 2.2.4 Use CoAP protocol to uplink data ===
251 +=== 2.2.5  Use CoAP protocol to uplink data ===
237 237  
238 238  (% 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/]]
239 239  
... ... @@ -253,10 +253,12 @@
253 253  )))
254 254  
255 255  (((
271 +
272 +
256 256  For parameter description, please refer to AT command set
257 257  )))
258 258  
259 -[[image:1657330452568-615.png]]
276 +[[image:1657352146020-183.png]]
260 260  
261 261  
262 262  (((
... ... @@ -263,11 +263,11 @@
263 263  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.
264 264  )))
265 265  
266 -[[image:1657330472797-498.png]]
283 +[[image:1657352185396-303.png]]
267 267  
268 268  
269 269  
270 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
287 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
271 271  
272 272  
273 273  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
... ... @@ -274,15 +274,16 @@
274 274  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
275 275  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
276 276  
277 -[[image:1657330501006-241.png]]
294 +[[image:1657352391268-297.png]]
278 278  
279 279  
280 -[[image:1657330533775-472.png]]
297 +[[image:1657352403317-397.png]]
281 281  
282 282  
283 283  
284 -=== 2.2.6 Use MQTT protocol to uplink data ===
301 +=== 2.2.7  Use MQTT protocol to uplink data ===
285 285  
303 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
286 286  
287 287  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
288 288  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -289,35 +289,40 @@
289 289  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
290 290  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
291 291  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
292 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
293 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
310 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
311 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
294 294  
295 -[[image:1657249978444-674.png]]
313 +[[image:1657352634421-276.png]]
296 296  
297 297  
298 -[[image:1657330723006-866.png]]
316 +[[image:1657352645687-385.png]]
299 299  
318 +(((
319 +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.
320 +)))
300 300  
322 +
301 301  (((
302 -MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
324 +MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
303 303  )))
304 304  
305 305  
306 306  
307 -=== 2.2.7 Use TCP protocol to uplink data ===
329 +=== 2.2.8  Use TCP protocol to uplink data ===
308 308  
331 +This feature is supported since firmware version v110
309 309  
310 310  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
311 311  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
312 312  
313 -[[image:image-20220709093918-1.png]]
336 +[[image:1657352898400-901.png]]
314 314  
315 315  
316 -[[image:image-20220709093918-2.png]]
339 +[[image:1657352914475-252.png]]
317 317  
318 318  
319 319  
320 -=== 2.2.8 Change Update Interval ===
343 +=== 2.2.9  Change Update Interval ===
321 321  
322 322  User can use below command to change the (% style="color:green" %)**uplink interval**.
323 323  
... ... @@ -324,69 +324,92 @@
324 324  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
325 325  
326 326  (((
327 -(% style="color:red" %)**NOTE:**
350 +
328 328  )))
329 329  
330 -(((
331 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
332 -)))
333 333  
334 334  
335 -
336 336  == 2.3  Uplink Payload ==
337 337  
338 -In this mode, uplink payload includes in total 14 bytes
339 339  
358 +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.
340 340  
360 +
361 +For example:
362 +
363 + (% 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.
364 +
365 +
366 +The uplink payloads are composed in  ASCII String. For example:
367 +
368 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
369 +
370 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
371 +
372 +
373 +(% style="color:red" %)**NOTE:**
374 +
375 +(% style="color:red" %)
376 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
377 +1. By default, the device will send an uplink message every 1 hour.
378 +
379 +
380 +
381 +=== 2.3.1  Payload Analyze ===
382 +
383 +N95S31B uplink payload includes in total 21 bytes
384 +
385 +
341 341  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
342 342  |=(% style="width: 60px;" %)(((
343 343  **Size(bytes)**
344 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
345 -|(% 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"]]
389 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
390 +|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)(((
391 +Reserve/ Same as NBSN95 CFGMOD=1
346 346  
347 -(((
348 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
349 -)))
393 +No function here.
394 +)))|(% style="width:77px" %)(((
395 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
350 350  
397 +By SHT31
398 +)))|(% style="width:80px" %)(((
399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
351 351  
352 -[[image:1657331036973-987.png]]
353 -
354 -(((
355 -The payload is ASCII string, representative same HEX:
401 +By SHT31
356 356  )))
357 357  
358 358  (((
359 -0x72403155615900640c6c19029200 where:
405 +(((
406 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
360 360  )))
361 -
362 -* (((
363 -Device ID: 0x724031556159 = 724031556159
364 364  )))
365 -* (((
366 -Version: 0x0064=100=1.0.0
367 -)))
368 368  
369 -* (((
370 -BAT: 0x0c6c = 3180 mV = 3.180V
371 -)))
372 -* (((
373 -Signal: 0x19 = 25
374 -)))
375 -* (((
376 -Distance: 0x0292= 658 mm
377 -)))
378 -* (((
379 -Interrupt: 0x00 = 0
380 380  
411 +[[image:1657354294009-643.png]]
381 381  
382 382  
414 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
415 +
416 +* Device ID: 0x724031607457 = 724031607457
417 +* Version: 0x006e=110=1.1.0
418 +
419 +* BAT: 0x0ccd = 3277 mV = 3.277V
420 +* Signal: 0x1b = 27
421 +* Model: 0x01 = 1
422 +* 0x00dc000ccc= reserve, ignore in N95S31B
423 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
424 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
425 +
426 +(((
383 383  
384 384  )))
385 385  
386 -== 2.4  Payload Explanation and Sensor Interface ==
430 +(((
431 +
432 +)))
387 387  
388 388  
389 -=== 2.4.1  Device ID ===
435 +=== 2.3.2  Device ID ===
390 390  
391 391  (((
392 392  By default, the Device ID equal to the last 6 bytes of IMEI.
... ... @@ -410,20 +410,25 @@
410 410  
411 411  
412 412  
413 -=== 2.4.2  Version Info ===
459 +=== 2.3.3  Version Info ===
414 414  
415 -(((
416 -Specify the software version: 0x64=100, means firmware version 1.00.
417 -)))
418 418  
462 +These bytes include the hardware and software version.
463 +
464 +Higher byte: Specify hardware version: always 0x00 for N95S31B
465 +
466 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
467 +
468 +
469 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
470 +
419 419  (((
420 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
472 +
421 421  )))
422 422  
423 423  
476 +=== 2.3.4  Battery Info ===
424 424  
425 -=== 2.4.3  Battery Info ===
426 -
427 427  (((
428 428  Ex1: 0x0B45 = 2885mV
429 429  )))
... ... @@ -434,7 +434,7 @@
434 434  
435 435  
436 436  
437 -=== 2.4.4  Signal Strength ===
488 +=== 2.3.5  Signal Strength ===
438 438  
439 439  (((
440 440  NB-IoT Network signal Strength.
... ... @@ -466,83 +466,24 @@
466 466  
467 467  
468 468  
469 -=== 2.4.5  Distance ===
520 +=== 2.3.6  Temperature & Humidity ===
470 470  
471 -Get the distance. Flat object range 280mm - 7500mm.
522 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
472 472  
473 -(((
474 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
475 -)))
524 +[[image:image-20220709161741-3.png]]
476 476  
477 -(((
478 -(((
479 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
480 -)))
481 -)))
482 482  
483 -(((
484 -
485 -)))
527 +Convert the read byte to decimal and divide it by ten.
486 486  
487 -(((
488 -
489 -)))
490 490  
491 -=== 2.4.6  Digital Interrupt ===
530 +**Example:**
492 492  
493 -(((
494 -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.
495 -)))
532 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
496 496  
497 -(((
498 -The command is:
499 -)))
534 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
500 500  
501 -(((
502 -(% 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]])**.**
503 -)))
504 504  
505 505  
506 -(((
507 -The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
508 -)))
509 -
510 -
511 -(((
512 -Example:
513 -)))
514 -
515 -(((
516 -0x(00): Normal uplink packet.
517 -)))
518 -
519 -(((
520 -0x(01): Interrupt Uplink Packet.
521 -)))
522 -
523 -
524 -
525 -=== 2.4.7  ​+5V Output ===
526 -
527 -(((
528 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
529 -)))
530 -
531 -
532 -(((
533 -The 5V output time can be controlled by AT Command.
534 -)))
535 -
536 -(((
537 -(% style="color:blue" %)**AT+5VT=1000**
538 -)))
539 -
540 -(((
541 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
542 -)))
543 -
544 -
545 -
546 546  == 2.5  Downlink Payload ==
547 547  
548 548  By default, NDDS75 prints the downlink payload to console port.
1657350248151-650.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
1657350625843-586.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +93.3 KB
Content
1657351240556-536.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657351312545-300.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +675.8 KB
Content
1657352146020-183.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +264.0 KB
Content
1657352185396-303.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.3 KB
Content
1657352391268-297.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +238.0 KB
Content
1657352403317-397.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
image-20220709150546-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +333.5 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +111.2 KB
Content

Applications

Navigation

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