Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Change comment:
Uploaded new attachment "image-20220908154949-1.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +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 ... ... @@ -64,6 +64,8 @@ 64 64 * Supply Voltage: 2.1v ~~ 3.6v 65 65 * Operating Temperature: -40 ~~ 85°C 66 66 82 + 83 + 67 67 (% style="color:#037691" %)**NB-IoT Spec:** 68 68 69 69 * - B1 @H-FDD: 2100MHz ... ... @@ -73,9 +73,10 @@ 73 73 * - B20 @H-FDD: 800MHz 74 74 * - B28 @H-FDD: 700MHz 75 75 76 -(% style="color:#037691" %)**Battery:** 77 77 78 78 95 +(% style="color:#037691" %)**Battery:** 96 + 79 79 * Li/SOCI2 un-chargeable battery 80 80 * Capacity: 8500mAh 81 81 * Self Discharge: <1% / Year @ 25°C ... ... @@ -87,6 +87,7 @@ 87 87 88 88 == 1.4 Applications == 89 89 108 + 90 90 * Smart Buildings & Home Automation 91 91 * Logistics and Supply Chain Management 92 92 * Smart Metering ... ... @@ -98,15 +98,20 @@ 98 98 99 99 100 100 101 -== 1.5 Pin Definitions == 102 102 121 +== 1.5 Pin Definitions & Switch == 122 + 123 + 103 103 N95S31B use the mother board from NBSN95 which as below. 104 104 126 + 105 105 [[image:image-20220709144723-1.png]] 106 106 107 107 130 + 108 108 === 1.5.1 Jumper JP2 === 109 109 133 + 110 110 Power on Device when put this jumper. 111 111 112 112 ... ... @@ -113,14 +113,20 @@ 113 113 114 114 === 1.5.2 BOOT MODE / SW1 === 115 115 140 + 141 +((( 116 116 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 +))) 117 117 145 +((( 118 118 2) Flash: work mode, device starts to work and send out console output for further debug 147 +))) 119 119 120 120 121 121 122 122 === 1.5.3 Reset Button === 123 123 153 + 124 124 Press to reboot the device. 125 125 126 126 ... ... @@ -127,6 +127,7 @@ 127 127 128 128 === 1.5.4 LED === 129 129 160 + 130 130 It will flash: 131 131 132 132 1. When boot the device in flash mode ... ... @@ -133,8 +133,11 @@ 133 133 1. Send an uplink packet 134 134 135 135 167 + 168 + 136 136 = 2. Use N95S31B to communicate with IoT Server = 137 137 171 + 138 138 == 2.1 How it works == 139 139 140 140 ... ... @@ -151,7 +151,7 @@ 151 151 152 152 ))) 153 153 154 -[[image:1657 350248151-650.png]]188 +[[image:1657520100595-569.png]] 155 155 156 156 ((( 157 157 ... ... @@ -167,26 +167,49 @@ 167 167 [[image:image-20220709150546-2.png]] 168 168 169 169 204 + 170 170 === 2.2.1 Test Requirement === 171 171 172 172 208 +((( 173 173 To use N95S31B in your city, make sure meet below requirements: 210 +))) 174 174 175 -* Your local operator has already distributed a NB-IoT Network there. 176 -* The local NB-IoT network used the band that N95S31B supports. 177 -* 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 +))) 178 178 222 +((( 179 179 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 224 +))) 180 180 226 +((( 181 181 N95S31B supports different communication protocol such as : 228 +))) 182 182 183 183 ((( 184 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 185 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 186 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 187 -* 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 +))) 188 188 244 +((( 189 189 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 +))) 190 190 191 191 192 192 ))) ... ... @@ -197,6 +197,7 @@ 197 197 198 198 === 2.2.3 Insert SIM card === 199 199 257 + 200 200 ((( 201 201 Insert the NB-IoT Card get from your provider. 202 202 ))) ... ... @@ -212,14 +212,18 @@ 212 212 213 213 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 214 214 273 + 215 215 ((( 216 216 ((( 217 217 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 + 218 218 ))) 219 219 ))) 220 220 221 221 [[image:1657351312545-300.png]] 222 222 284 + 223 223 **Connection:** 224 224 225 225 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -243,8 +243,9 @@ 243 243 244 244 [[image:1657329814315-101.png]] 245 245 308 + 246 246 ((( 247 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dr agino.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]]** 248 248 ))) 249 249 250 250 ... ... @@ -251,9 +251,10 @@ 251 251 252 252 === 2.2.5 Use CoAP protocol to uplink data === 253 253 254 -(% 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/]] 255 255 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/]]** 256 256 320 + 257 257 ((( 258 258 **Use below commands:** 259 259 ))) ... ... @@ -292,6 +292,8 @@ 292 292 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 293 293 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 294 294 359 + 360 + 295 295 [[image:1657352391268-297.png]] 296 296 297 297 ... ... @@ -301,6 +301,7 @@ 301 301 302 302 === 2.2.7 Use MQTT protocol to uplink data === 303 303 370 + 304 304 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 305 305 306 306 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -311,11 +311,14 @@ 311 311 * (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 312 312 * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 313 313 381 + 382 + 314 314 [[image:1657352634421-276.png]] 315 315 316 316 317 317 [[image:1657352645687-385.png]] 318 318 388 + 319 319 ((( 320 320 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. 321 321 ))) ... ... @@ -329,11 +329,14 @@ 329 329 330 330 === 2.2.8 Use TCP protocol to uplink data === 331 331 402 + 332 332 This feature is supported since firmware version v110 333 333 334 334 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 335 335 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 336 336 408 + 409 + 337 337 [[image:1657352898400-901.png]] 338 338 339 339 ... ... @@ -343,6 +343,7 @@ 343 343 344 344 === 2.2.9 Change Update Interval === 345 345 419 + 346 346 User can use below command to change the (% style="color:green" %)**uplink interval**. 347 347 348 348 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -356,53 +356,88 @@ 356 356 == 2.3 Uplink Payload == 357 357 358 358 359 -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 +))) 360 360 361 361 438 +((( 362 362 For example: 440 +))) 363 363 364 - (% 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 +))) 365 365 366 366 447 +((( 367 367 The uplink payloads are composed in ASCII String. For example: 449 +))) 368 368 451 +((( 369 369 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 453 +))) 370 370 455 +((( 371 371 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 457 +))) 372 372 373 373 460 +((( 374 374 (% style="color:red" %)**NOTE:** 462 +))) 375 375 376 376 (% style="color:red" %) 377 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 378 -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.** 379 379 380 380 381 381 473 + 474 +))) 475 + 382 382 === 2.3.1 Payload Analyze === 383 383 478 + 384 384 N95S31B uplink payload includes in total 21 bytes 385 385 386 386 387 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 440px" %)482 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 388 388 |=(% style="width: 60px;" %)((( 389 389 **Size(bytes)** 390 -)))|=(% 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** 391 -|(% 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" %)((( 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** 486 +|(% 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 +((( 392 392 Reserve/ Same as NBSN95 CFGMOD=1 489 +))) 393 393 491 +((( 394 394 No function here. 493 +))) 395 395 )))|(% style="width:77px" %)((( 396 -[[Temperature >>||anchor="H2.4.5A0Distance"]] 495 +((( 496 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 497 +))) 397 397 499 +((( 398 398 By SHT31 501 +))) 399 399 )))|(% style="width:80px" %)((( 400 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 503 +((( 504 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 505 +))) 401 401 507 +((( 402 402 By SHT31 403 403 ))) 510 +))) 404 404 405 405 ((( 513 + 514 + 406 406 ((( 407 407 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 408 408 ))) ... ... @@ -435,6 +435,7 @@ 435 435 436 436 === 2.3.2 Device ID === 437 437 547 + 438 438 ((( 439 439 By default, the Device ID equal to the last 6 bytes of IMEI. 440 440 ))) ... ... @@ -460,14 +460,25 @@ 460 460 === 2.3.3 Version Info === 461 461 462 462 573 +((( 463 463 These bytes include the hardware and software version. 575 +))) 464 464 577 +((( 465 465 Higher byte: Specify hardware version: always 0x00 for N95S31B 579 +))) 466 466 581 +((( 467 467 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 583 +))) 468 468 585 +((( 586 + 587 +))) 469 469 589 +((( 470 470 For example: 0x00 6E: this device is N95S31B with firmware version 110. 591 +))) 471 471 472 472 ((( 473 473 ... ... @@ -476,6 +476,7 @@ 476 476 477 477 === 2.3.4 Battery Info === 478 478 600 + 479 479 ((( 480 480 Ex1: 0x0B45 = 2885mV 481 481 ))) ... ... @@ -488,6 +488,7 @@ 488 488 489 489 === 2.3.5 Signal Strength === 490 490 613 + 491 491 ((( 492 492 NB-IoT Network signal Strength. 493 493 ))) ... ... @@ -520,6 +520,7 @@ 520 520 521 521 === 2.3.6 Temperature & Humidity === 522 522 646 + 523 523 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 524 524 525 525 [[image:image-20220709161741-3.png]] ... ... @@ -538,8 +538,9 @@ 538 538 539 539 == 2.4 Downlink Payload == 540 540 541 -By default, NDDS75 prints the downlink payload to console port. 542 542 666 +By default, N95S31B prints the downlink payload to console port. 667 + 543 543 [[image:image-20220709100028-1.png]] 544 544 545 545 ... ... @@ -576,7 +576,7 @@ 576 576 ))) 577 577 578 578 ((( 579 -If payload = 0x04FF, it will reset the DDS75704 +If payload = 0x04FF, it will reset the N95S31B 580 580 ))) 581 581 582 582 ... ... @@ -590,6 +590,7 @@ 590 590 591 591 == 2.5 Battery Analysis == 592 592 718 + 593 593 === 2.5.1 Battery Type === 594 594 595 595 ... ... @@ -617,8 +617,9 @@ 617 617 618 618 === 2.5.2 Power consumption Analyze === 619 619 746 + 620 620 ((( 621 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]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. 622 622 ))) 623 623 624 624 ((( ... ... @@ -628,6 +628,7 @@ 628 628 629 629 === 2.5.3 Battery Note === 630 630 758 + 631 631 ((( 632 632 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. 633 633 ))) ... ... @@ -650,6 +650,7 @@ 650 650 651 651 = 3. Access NB-IoT Module = 652 652 781 + 653 653 ((( 654 654 Users can directly access the AT command set of the NB-IoT module. 655 655 ))) ... ... @@ -656,6 +656,8 @@ 656 656 657 657 ((( 658 658 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 + 659 659 ))) 660 660 661 661 [[image:1657333200519-600.png]] ... ... @@ -664,11 +664,13 @@ 664 664 665 665 = 4. Using the AT Commands = 666 666 798 + 667 667 == 4.1 Access AT Commands == 668 668 669 -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/]] 670 670 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]] 671 671 804 + 672 672 AT+<CMD>? : Help on <CMD> 673 673 674 674 AT+<CMD> : Run <CMD> ... ... @@ -742,6 +742,7 @@ 742 742 743 743 = 5. FAQ = 744 744 878 + 745 745 == 5.1 How to Upgrade Firmware == 746 746 747 747 ... ... @@ -756,13 +756,16 @@ 756 756 ((( 757 757 758 758 759 -(% 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.** 760 760 ))) 896 +))) 761 761 762 762 763 763 764 764 = 6. Trouble Shooting = 765 765 902 + 766 766 == 6.1 Connection problem when uploading firmware == 767 767 768 768 ... ... @@ -778,6 +778,7 @@ 778 778 779 779 == 6.2 AT Command input doesn't work == 780 780 918 + 781 781 ((( 782 782 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. 783 783 ... ... @@ -827,5 +827,9 @@ 827 827 828 828 = 9. Support = 829 829 968 + 830 830 * 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. 831 831 * 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