Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 15 added, 0 removed)
- 1657348034241-728.png
- 1657348284168-431.png
- 1657350248151-650.png
- 1657350625843-586.png
- 1657351240556-536.png
- 1657351312545-300.png
- 1657352146020-183.png
- 1657352185396-303.png
- 1657352391268-297.png
- 1657352403317-397.png
- 1657352634421-276.png
- 1657352645687-385.png
- 1657352898400-901.png
- image-20220709144723-1.png
- image-20220709150546-2.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N DDS75 NB-IoTDistanceDetect Sensor User Manual1 +N95S31B NB-IoT Temperature & Humidity Sensor User Manual - Content
-
... ... @@ -1,61 +1,60 @@ 1 1 (% style="text-align:center" %) 2 -[[image: image-20220709085040-1.png||height="542" width="524"]]2 +[[image:1657348034241-728.png||height="470" width="470"]] 3 3 4 4 5 5 6 6 7 7 8 -**Table of Contents:** 9 9 10 -{{toc/}} 11 11 10 +**Table of Contents:** 12 12 13 13 14 14 15 15 16 16 16 + 17 17 = 1. Introduction = 18 18 19 -== 1.1 What is N DDS75Distance DetectionSensor ==19 +== 1.1 What is N95S31B NB-IoT Sensor Node == 20 20 21 21 ((( 22 22 23 23 24 -((( 25 -The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data. 26 -\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network. 27 -\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 29 -\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 30 -\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection. 31 -))) 24 +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*. 32 32 33 - 34 -))) 26 +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. 35 35 36 - [[image:1654503236291-817.png]]28 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 37 37 30 +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). 38 38 39 -[[image:1657327959271-447.png]] 40 40 33 +~* make sure you have NB-IoT coverage locally. 41 41 35 + 36 +))) 42 42 38 +[[image:1657348284168-431.png]] 39 + 40 + 41 + 43 43 == 1.2 Features == 44 44 45 45 46 46 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 47 -* Ultra low power consumption 48 -* Distance Detection by Ultrasonic technology 49 -* Flat object range 280mm - 7500mm 50 -* Accuracy: ±(1cm+S*0.3%) (S: Distance) 51 -* Cable Length: 25cm 46 +* Monitor Temperature & Humidity via SHT31 52 52 * AT Commands to change parameters 53 53 * Uplink on periodically 54 54 * Downlink to change configure 55 55 * IP66 Waterproof Enclosure 51 +* Ultra-Low Power consumption 52 +* AT Commands to change parameters 56 56 * Micro SIM card slot for NB-IoT SIM 57 57 * 8500mAh Battery for long term use 58 58 56 + 57 + 59 59 == 1.3 Specification == 60 60 61 61 ... ... @@ -75,6 +75,7 @@ 75 75 76 76 (% style="color:#037691" %)**Battery:** 77 77 77 + 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -81,12 +81,8 @@ 81 81 * Max continuously current: 130mA 82 82 * Max boost current: 2A, 1 second 83 83 84 -(% style="color:#037691" %)**Power Consumption** 85 85 86 -* STOP Mode: 10uA @ 3.3v 87 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 88 88 89 - 90 90 == 1.4 Applications == 91 91 92 92 * Smart Buildings & Home Automation ... ... @@ -100,25 +100,55 @@ 100 100 101 101 102 102 103 - 104 104 == 1.5 Pin Definitions == 105 105 101 +N95S31B use the mother board from NBSN95 which as below. 106 106 107 -[[image: 1657328609906-564.png]]103 +[[image:image-20220709144723-1.png]] 108 108 109 109 106 +=== 1.5.1 Jumper JP2 === 110 110 111 - = 2. UseNDDS75 tocommunicate withIoTServer =108 +Power on Device when put this jumper. 112 112 110 + 111 + 112 +=== 1.5.2 BOOT MODE / SW1 === 113 + 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. 115 + 116 +2) Flash: work mode, device starts to work and send out console output for further debug 117 + 118 + 119 + 120 +=== 1.5.3 Reset Button === 121 + 122 +Press to reboot the device. 123 + 124 + 125 + 126 +=== 1.5.4 LED === 127 + 128 +It will flash: 129 + 130 +1. When boot the device in flash mode 131 +1. Send an uplink packet 132 + 133 + 134 + 135 + 136 += 2. Use N95S31B to communicate with IoT Server = 137 + 113 113 == 2.1 How it works == 114 114 140 + 115 115 ((( 116 -The N DDS75 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.142 +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. 117 117 ))) 118 118 119 119 120 120 ((( 121 -The diagram below shows the working flow in default firmware of N DDS75:147 +The diagram below shows the working flow in default firmware of N95S31B: 122 122 ))) 123 123 124 124 ((( ... ... @@ -125,7 +125,7 @@ 125 125 126 126 ))) 127 127 128 -[[image:1657328 659945-416.png]]154 +[[image:1657350248151-650.png]] 129 129 130 130 ((( 131 131 ... ... @@ -132,30 +132,46 @@ 132 132 ))) 133 133 134 134 135 -== 2.2 Configure the N DDS75 ==161 +== 2.2 Configure the N95S31B == 136 136 137 137 164 +=== 2.2.1 Power On N95S31B === 165 + 166 + 167 +[[image:image-20220709150546-2.png]] 168 + 169 + 138 138 === 2.2.1 Test Requirement === 139 139 140 -((( 141 -To use NDDS75 in your city, make sure meet below requirements: 142 -))) 143 143 173 +To use N95S31B in your city, make sure meet below requirements: 174 + 144 144 * Your local operator has already distributed a NB-IoT Network there. 145 -* The local NB-IoT network used the band that NS E01 supports.176 +* The local NB-IoT network used the band that N95S31B supports. 146 146 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 147 147 179 + 180 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 181 + 182 +N95S31B supports different communication protocol such as : 183 + 148 148 ((( 149 -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 150 -))) 185 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 186 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 187 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 188 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 151 151 190 +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. 152 152 153 -[[image:1657328756309-230.png]] 192 + 193 +))) 154 154 195 +[[image:1657350625843-586.png]] 155 155 156 156 157 -=== 2.2.2 Insert SIM card === 158 158 199 +=== 2.2.3 Insert SIM card === 200 + 159 159 ((( 160 160 Insert the NB-IoT Card get from your provider. 161 161 ))) ... ... @@ -165,19 +165,19 @@ 165 165 ))) 166 166 167 167 168 -[[image:165732 8884227-504.png]]210 +[[image:1657351240556-536.png]] 169 169 170 170 171 171 172 -=== 2.2. 3DDS75 to configure it ===214 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 173 173 174 174 ((( 175 175 ((( 176 -User need to configure DDS75 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 toDDS75 and use AT Commands to configure it, as below.218 +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. 177 177 ))) 178 178 ))) 179 179 180 -[[image: image-20220709092052-2.png]]222 +[[image:1657351312545-300.png]] 181 181 182 182 **Connection:** 183 183 ... ... @@ -197,72 +197,91 @@ 197 197 * Flow Control: (% style="color:green" %)**None** 198 198 199 199 ((( 200 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N DDS75.DDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.242 +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. 201 201 ))) 202 202 203 203 [[image:1657329814315-101.png]] 204 204 205 205 ((( 206 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N DDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]248 +(% 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/]] 207 207 ))) 208 208 209 209 210 210 211 -=== 2.2. 4253 +=== 2.2.5 Use CoAP protocol to uplink data === 212 212 213 213 (% 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/]] 214 214 215 215 258 +((( 216 216 **Use below commands:** 260 +))) 217 217 218 -* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 219 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 220 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 262 +* ((( 263 +(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 264 +))) 265 +* ((( 266 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 267 +))) 268 +* ((( 269 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 270 +))) 221 221 272 +((( 273 + 274 + 222 222 For parameter description, please refer to AT command set 276 +))) 223 223 224 -[[image:16573 30452568-615.png]]278 +[[image:1657352146020-183.png]] 225 225 226 226 281 +((( 227 227 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. 283 +))) 228 228 229 -[[image:16573 30472797-498.png]]285 +[[image:1657352185396-303.png]] 230 230 231 231 232 232 233 -=== 2.2. 5289 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 234 234 235 235 236 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 292 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 237 237 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 238 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 294 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 239 239 240 -[[image:16573 30501006-241.png]]296 +[[image:1657352391268-297.png]] 241 241 242 242 243 -[[image:16573 30533775-472.png]]299 +[[image:1657352403317-397.png]] 244 244 245 245 246 246 247 -=== 2.2. 6303 +=== 2.2.7 Use MQTT protocol to uplink data === 248 248 305 +N95S31B supports only plain MQTT now it doesn’t support TLS and other related encryption. 249 249 250 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 251 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 252 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 253 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 254 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 255 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB256 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB307 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 308 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 309 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 310 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 311 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 312 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 313 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 257 257 258 -[[image:165724 9978444-674.png]]315 +[[image:1657352634421-276.png]] 259 259 260 260 261 -[[image:16573 30723006-866.png]]318 +[[image:1657352645687-385.png]] 262 262 320 +((( 321 +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. 322 +))) 263 263 324 + 264 264 ((( 265 -MQTT protocol has a much high erpower consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.326 +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. 266 266 ))) 267 267 268 268 ... ... @@ -301,11 +301,11 @@ 301 301 In this mode, uplink payload includes in total 14 bytes 302 302 303 303 304 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 510px" %)305 -|=(% style="width: 80px;" %)(((365 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 366 +|=(% style="width: 60px;" %)((( 306 306 **Size(bytes)** 307 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width:110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width:70px;" %)**1**308 -|(% 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. 8A0DigitalInterrupt"]]368 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 369 +|(% 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"]] 309 309 310 310 ((( 311 311 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. ... ... @@ -388,10 +388,6 @@ 388 388 === 2.4.3 Battery Info === 389 389 390 390 ((( 391 -Check the battery voltage for LSE01. 392 -))) 393 - 394 -((( 395 395 Ex1: 0x0B45 = 2885mV 396 396 ))) 397 397 ... ... @@ -437,7 +437,9 @@ 437 437 438 438 Get the distance. Flat object range 280mm - 7500mm. 439 439 497 +((( 440 440 For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 499 +))) 441 441 442 442 ((( 443 443 ((( ... ... @@ -580,7 +580,9 @@ 580 580 == 2.7 Firmware Change Log == 581 581 582 582 642 +((( 583 583 Download URL & Firmware Change log 644 +))) 584 584 585 585 ((( 586 586 [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]] ... ... @@ -587,7 +587,9 @@ 587 587 ))) 588 588 589 589 651 +((( 590 590 Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 653 +))) 591 591 592 592 593 593
- 1657348034241-728.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +127.8 KB - Content
- 1657348284168-431.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +93.5 KB - Content
- 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
- image-20220709144723-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +413.1 KB - Content
- image-20220709150546-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +333.5 KB - Content