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, 0 added, 35 removed)
- 1657328756309-230.png
- 1657328884227-504.png
- 1657329814315-101.png
- 1657330452568-615.png
- 1657330472797-498.png
- 1657330501006-241.png
- 1657330533775-472.png
- 1657330723006-866.png
- 1657331036973-987.png
- 1657332990863-496.png
- 1657333200519-600.png
- 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
- 1657352914475-252.png
- 1657354294009-643.png
- image-20220709092052-2.png
- image-20220709093918-1.png
- image-20220709093918-2.png
- image-20220709100028-1.png
- image-20220709101450-2.png
- image-20220709110451-3.png
- image-20220709144723-1.png
- image-20220709150546-2.png
- image-20220709161741-3.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N 95S31BNB-IoTTemperature& HumiditySensor User Manual1 +NDDS75 NB-IoT Distance Detect Sensor User Manual - Content
-
... ... @@ -1,72 +1,62 @@ 1 1 (% style="text-align:center" %) 2 -[[image: 1657348034241-728.png||height="470" width="470"]]2 +[[image:image-20220709085040-1.png||height="542" width="524"]] 3 3 4 4 5 5 6 6 7 7 8 - 9 - 10 10 **Table of Contents:** 11 11 12 -{{toc/}} 13 13 14 14 15 15 16 16 17 17 15 + 18 18 = 1. Introduction = 19 19 20 -== 1.1 What is N 95S31BNB-IoTSensorNode==18 +== 1.1 What is NDDS75 Distance Detection Sensor == 21 21 22 22 ((( 23 23 24 24 25 25 ((( 26 -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*. 24 +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. 25 +\\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. 26 +\\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. 27 +\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 28 +\\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) 29 +\\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. 27 27 ))) 28 28 29 -((( 30 -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. 31 -))) 32 - 33 -((( 34 -N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 -))) 36 - 37 -((( 38 -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). 39 -))) 40 - 41 -((( 42 42 43 43 ))) 44 44 45 -((( 46 -~* make sure you have NB-IoT coverage locally. 47 -))) 35 +[[image:1654503236291-817.png]] 48 48 49 - 50 -))) 51 51 52 -[[image:16573 48284168-431.png]]38 +[[image:1657327959271-447.png]] 53 53 54 54 55 55 56 56 == 1.2 Features == 57 57 44 + 58 58 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 59 -* Monitor Temperature & Humidity via SHT31 46 +* Ultra low power consumption 47 +* Distance Detection by Ultrasonic technology 48 +* Flat object range 280mm - 7500mm 49 +* Accuracy: ±(1cm+S*0.3%) (S: Distance) 50 +* Cable Length: 25cm 60 60 * AT Commands to change parameters 61 61 * Uplink on periodically 62 62 * Downlink to change configure 63 63 * IP66 Waterproof Enclosure 64 -* Ultra-Low Power consumption 65 -* AT Commands to change parameters 66 66 * Micro SIM card slot for NB-IoT SIM 67 67 * 8500mAh Battery for long term use 68 68 69 69 59 + 70 70 == 1.3 Specification == 71 71 72 72 ... ... @@ -84,6 +84,7 @@ 84 84 * - B20 @H-FDD: 800MHz 85 85 * - B28 @H-FDD: 700MHz 86 86 77 + 87 87 (% style="color:#037691" %)**Battery:** 88 88 89 89 * Li/SOCI2 un-chargeable battery ... ... @@ -93,6 +93,14 @@ 93 93 * Max boost current: 2A, 1 second 94 94 95 95 87 +(% style="color:#037691" %)**Power Consumption** 88 + 89 +* STOP Mode: 10uA @ 3.3v 90 +* Max transmit power: 350mA@3.3v 91 + 92 + 93 + 94 + 96 96 == 1.4 Applications == 97 97 98 98 * Smart Buildings & Home Automation ... ... @@ -106,131 +106,62 @@ 106 106 107 107 108 108 109 -== 1.5 Pin Definitions & Switch == 110 110 111 - N95S31Busethemother boardfrom NBSN95 which asbelow.109 +== 1.5 Pin Definitions == 112 112 113 -[[image:image-20220709144723-1.png]] 114 114 112 +[[image:1657328609906-564.png]] 115 115 116 -=== 1.5.1 Jumper JP2 === 117 117 118 -Power on Device when put this jumper. 119 119 120 120 117 += 2. Use NSE01 to communicate with IoT Server = 121 121 122 -=== 1.5.2 BOOT MODE / SW1 === 123 - 124 -((( 125 -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. 126 -))) 127 - 128 -((( 129 -2) Flash: work mode, device starts to work and send out console output for further debug 130 -))) 131 - 132 - 133 - 134 -=== 1.5.3 Reset Button === 135 - 136 -Press to reboot the device. 137 - 138 - 139 - 140 -=== 1.5.4 LED === 141 - 142 -It will flash: 143 - 144 -1. When boot the device in flash mode 145 -1. Send an uplink packet 146 - 147 - 148 -= 2. Use N95S31B to communicate with IoT Server = 149 - 150 150 == 2.1 How it works == 151 151 152 152 153 153 ((( 154 -The N 95S31Bis equipped with a NB-IoT module, the pre-loaded firmware in N95S31Bwill 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.123 +The NSE01 is equipped with a NB-IoT module, the pre-loaded firmware in NSE01 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 NSE01. 155 155 ))) 156 156 157 157 158 158 ((( 159 -The diagram below shows the working flow in default firmware of N 95S31B:128 +The diagram below shows the working flow in default firmware of NSE01: 160 160 ))) 161 161 162 -((( 163 - 164 -))) 131 +[[image:image-20220708101605-2.png]] 165 165 166 -[[image:1657350248151-650.png]] 167 - 168 168 ((( 169 169 170 170 ))) 171 171 172 172 173 -== 2.2 Configure the N95S31B == 174 174 139 +== 2.2 Configure the NSE01 == 175 175 176 -=== 2.2.1 Power On N95S31B === 177 177 178 - 179 -[[image:image-20220709150546-2.png]] 180 - 181 - 182 182 === 2.2.1 Test Requirement === 183 183 184 184 185 185 ((( 186 -To use N 95S31Bin your city, make sure meet below requirements:146 +To use NSE01 in your city, make sure meet below requirements: 187 187 ))) 188 188 189 -* ((( 190 -Your local operator has already distributed a NB-IoT Network there. 191 -))) 192 -* ((( 193 -The local NB-IoT network used the band that N95S31B supports. 194 -))) 195 -* ((( 196 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 197 -))) 149 +* Your local operator has already distributed a NB-IoT Network there. 150 +* The local NB-IoT network used the band that NSE01 supports. 151 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 198 198 199 199 ((( 200 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 154 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NSE01 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 201 201 ))) 202 202 203 -((( 204 -N95S31B supports different communication protocol such as : 205 -))) 206 206 207 -((( 208 -* ((( 209 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 210 -))) 211 -* ((( 212 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 213 -))) 214 -* ((( 215 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 216 -))) 217 -* ((( 218 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 219 -))) 158 +[[image:1657249419225-449.png]] 220 220 221 -((( 222 -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. 223 -))) 224 224 225 - 226 -))) 227 227 228 - [[image:1657350625843-586.png]]162 +=== 2.2.2 Insert SIM card === 229 229 230 - 231 - 232 -=== 2.2.3 Insert SIM card === 233 - 234 234 ((( 235 235 Insert the NB-IoT Card get from your provider. 236 236 ))) ... ... @@ -240,19 +240,18 @@ 240 240 ))) 241 241 242 242 243 -[[image:1657 351240556-536.png]]173 +[[image:1657249468462-536.png]] 244 244 245 245 246 246 247 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===177 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it === 248 248 249 249 ((( 250 250 ((( 251 -User need to configure 95S31Bvia serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31Bsupport AT Commands, user can use a USB to TTL adapter to connect to95S31Band use AT Commands to configure it, as below.181 +User need to configure NSE01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below. 252 252 ))) 253 253 ))) 254 254 255 -[[image:1657351312545-300.png]] 256 256 257 257 **Connection:** 258 258 ... ... @@ -272,110 +272,96 @@ 272 272 * Flow Control: (% style="color:green" %)**None** 273 273 274 274 ((( 275 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N 95S31B.95S31Bwill output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.204 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 276 276 ))) 277 277 278 -[[image: 1657329814315-101.png]]207 +[[image:image-20220708110657-3.png]] 279 279 280 280 ((( 281 -(% style="color:red" %)Note: the valid AT Commands can be found at: s:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]210 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 282 282 ))) 283 283 284 284 285 285 286 -=== 2.2. 5Use CoAP protocol to uplink data ===215 +=== 2.2.4 Use CoAP protocol to uplink data === 287 287 288 288 (% 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/]] 289 289 290 290 291 -((( 292 292 **Use below commands:** 293 -))) 294 294 295 -* ((( 296 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 297 -))) 298 -* ((( 299 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 300 -))) 301 -* ((( 302 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 303 -))) 222 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 223 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 224 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 304 304 305 -((( 306 - 307 - 308 308 For parameter description, please refer to AT command set 309 -))) 310 310 311 -[[image:1657 352146020-183.png]]228 +[[image:1657249793983-486.png]] 312 312 313 313 314 -((( 315 -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. 316 -))) 231 +After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server. 317 317 318 -[[image:1657 352185396-303.png]]233 +[[image:1657249831934-534.png]] 319 319 320 320 321 321 322 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===237 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 323 323 239 +This feature is supported since firmware version v1.0.1 324 324 325 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 241 + 242 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 326 326 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 327 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 244 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 328 328 329 -[[image:1657 352391268-297.png]]246 +[[image:1657249864775-321.png]] 330 330 331 331 332 -[[image:1657 352403317-397.png]]249 +[[image:1657249930215-289.png]] 333 333 334 334 335 335 336 -=== 2.2. 7Use MQTT protocol to uplink data ===253 +=== 2.2.6 Use MQTT protocol to uplink data === 337 337 338 - N95S31Bsupportsonly plain MQTT now itdoesn'tsupportTLS and otherlated encryption.255 +This feature is supported since firmware version v110 339 339 340 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 341 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 342 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 343 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 344 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 345 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 346 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 347 347 348 -[[image:1657352634421-276.png]] 258 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 259 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 260 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 261 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 262 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 263 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB **(%%)~/~/Set the sending topic of MQTT 264 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB **(%%) ~/~/Set the subscription topic of MQTT 349 349 266 +[[image:1657249978444-674.png]] 350 350 351 -[[image:1657352645687-385.png]] 352 352 353 -((( 354 -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. 355 -))) 269 +[[image:1657249990869-686.png]] 356 356 357 357 358 358 ((( 359 -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.273 +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. 360 360 ))) 361 361 362 362 363 363 364 -=== 2.2. 8Use TCP protocol to uplink data ===278 +=== 2.2.7 Use TCP protocol to uplink data === 365 365 366 366 This feature is supported since firmware version v110 367 367 282 + 368 368 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 369 369 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 370 370 371 -[[image:1657 352898400-901.png]]286 +[[image:1657250217799-140.png]] 372 372 373 373 374 -[[image:1657 352914475-252.png]]289 +[[image:1657250255956-604.png]] 375 375 376 376 377 377 378 -=== 2.2. 9Change Update Interval ===293 +=== 2.2.8 Change Update Interval === 379 379 380 380 User can use below command to change the (% style="color:green" %)**uplink interval**. 381 381 ... ... @@ -382,156 +382,190 @@ 382 382 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 383 383 384 384 ((( 385 - 300 +(% style="color:red" %)**NOTE:** 386 386 ))) 387 387 303 +((( 304 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 305 +))) 388 388 389 389 308 + 390 390 == 2.3 Uplink Payload == 391 391 311 +In this mode, uplink payload includes in total 18 bytes 392 392 313 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 314 +|=(% style="width: 60px;" %)((( 315 +**Size(bytes)** 316 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 50px;" %)**1** 317 +|(% 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:108px" %)[[Soil Moisture>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H2.4.6A0SoilTemperature"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H2.4.7A0SoilConductivity28EC29"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]] 318 + 393 393 ((( 394 - NBSN95 has differentworkingmodeforthe connections of different typeofsensors. This section describesthesemodes.Usercanuse theAT Command (% style="color:blue"%)**AT+MOD**(%%)toset NBSN95to different workingmodes.320 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data. 395 395 ))) 396 396 397 397 324 +[[image:image-20220708111918-4.png]] 325 + 326 + 327 +The payload is ASCII string, representative same HEX: 328 + 329 +0x72403155615900640c7817075e0a8c02f900 where: 330 + 331 +* Device ID: 0x 724031556159 = 724031556159 332 +* Version: 0x0064=100=1.0.0 333 + 334 +* BAT: 0x0c78 = 3192 mV = 3.192V 335 +* Singal: 0x17 = 23 336 +* Soil Moisture: 0x075e= 1886 = 18.86 % 337 +* Soil Temperature:0x0a8c =2700=27 °C 338 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm 339 +* Interrupt: 0x00 = 0 340 + 341 +== 2.4 Payload Explanation and Sensor Interface == 342 + 343 + 344 +=== 2.4.1 Device ID === 345 + 398 398 ((( 399 - Forexample:347 +By default, the Device ID equal to the last 6 bytes of IMEI. 400 400 ))) 401 401 402 402 ((( 403 - (% style="color:blue" %)**AT+ CFGMOD=2**~/~/willsetthe NBSN95 towork in MOD=2 distancemode whichtargetto measure distancevia UltrasonicSensor.351 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 404 404 ))) 405 405 406 - 407 407 ((( 408 - The uplink payloads are composed in ASCII String. For example:355 +**Example:** 409 409 ))) 410 410 411 411 ((( 412 -0 a cd 00 ed 0a cc 00 00 ef 02 d21d (total24 ASCII Chars) . Representative the actually payload:359 +AT+DEUI=A84041F15612 413 413 ))) 414 414 415 415 ((( 416 - 0x0acd00ed0acc0000ef02d21dTotal12 bytes363 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 417 417 ))) 418 418 419 419 367 + 368 +=== 2.4.2 Version Info === 369 + 420 420 ((( 421 - (%style="color:red"%)**NOTE:**371 +Specify the software version: 0x64=100, means firmware version 1.00. 422 422 ))) 423 423 424 -(% style="color:red" %) 425 -1. ((( 426 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 374 +((( 375 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0. 427 427 ))) 428 -1. ((( 429 -By default, the device will send an uplink message every 1 hour. 430 -))) 431 431 432 432 433 -=== 2.3.1 Payload Analyze === 434 434 435 - N95S31Buplink payloadincludes in total21 bytes380 +=== 2.4.3 Battery Info === 436 436 382 +((( 383 +Check the battery voltage for LSE01. 384 +))) 437 437 438 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 439 -|=(% style="width: 60px;" %)((( 440 -**Size(bytes)** 441 -)))|=(% 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** 442 -|(% 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" %)((( 443 443 ((( 444 - Reserve/Same as NBSN95CFGMOD=1387 +Ex1: 0x0B45 = 2885mV 445 445 ))) 446 446 447 447 ((( 448 - Nofunctionhere.391 +Ex2: 0x0B49 = 2889mV 449 449 ))) 450 -)))|(% style="width:77px" %)((( 393 + 394 + 395 + 396 +=== 2.4.4 Signal Strength === 397 + 451 451 ((( 452 - [[Temperature>>||anchor="H2.3.6A0Temperature26Humidity"]]399 +NB-IoT Network signal Strength. 453 453 ))) 454 454 455 455 ((( 456 - BySHT31403 +**Ex1: 0x1d = 29** 457 457 ))) 458 - )))|(% style="width:80px" %)(((405 + 459 459 ((( 460 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]407 +(% style="color:blue" %)**0**(%%) -113dBm or less 461 461 ))) 462 462 463 463 ((( 464 - BySHT31411 +(% style="color:blue" %)**1**(%%) -111dBm 465 465 ))) 413 + 414 +((( 415 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 466 466 ))) 467 467 468 468 ((( 419 +(% style="color:blue" %)**31** (%%) -51dBm or greater 420 +))) 421 + 469 469 ((( 470 - Ifwe usetheMQTTclient tosubscribetothisMQTTtopic,we can seethefollowinginformationwhenheNB sensor uplinkdata.423 +(% style="color:blue" %)**99** (%%) Not known or not detectable 471 471 ))) 472 -))) 473 473 474 474 475 -[[image:1657354294009-643.png]] 476 476 428 +=== 2.4.5 Soil Moisture === 477 477 478 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 430 +((( 431 +((( 432 +Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil. 433 +))) 434 +))) 479 479 480 -* Device ID: 0x724031607457 = 724031607457 481 -* Version: 0x006e=110=1.1.0 436 +((( 437 +((( 438 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is 439 +))) 440 +))) 482 482 483 -* BAT: 0x0ccd = 3277 mV = 3.277V 484 -* Signal: 0x1b = 27 485 -* Model: 0x01 = 1 486 -* 0x00dc000ccc= reserve, ignore in N95S31B 487 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 488 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 489 - 490 490 ((( 491 491 492 492 ))) 493 493 494 494 ((( 495 - 447 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.** 496 496 ))) 497 497 498 498 499 -=== 2.3.2 Device ID === 500 500 501 -((( 502 -By default, the Device ID equal to the last 6 bytes of IMEI. 503 -))) 452 +=== 2.4.6 Soil Temperature === 504 504 505 505 ((( 506 - Usercan use (%style="color:blue"%)**AT+DEUI**(%%)tosetDeviceID455 +Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __**0x09 0xEC**__, the temperature content in the soil is 507 507 ))) 508 508 509 509 ((( 510 -**Example :**459 +**Example**: 511 511 ))) 512 512 513 513 ((( 514 - AT+DEUI=A84041F15612463 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C 515 515 ))) 516 516 517 517 ((( 518 - The DeviceIDis stored inanone-erasearea,Upgradethefirmwareorrun **AT+FDR**won'terase Device ID.467 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C 519 519 ))) 520 520 521 521 522 522 523 -=== 2. 3.3VersionInfo===472 +=== 2.4.7 Soil Conductivity (EC) === 524 524 525 525 ((( 526 - These bytes include thehardware andsoftwareversion.475 +Obtain (% style="color:#4f81bd" %)**__soluble salt concentration__**(%%) in soil or (% style="color:#4f81bd" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:#4f81bd" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000). 527 527 ))) 528 528 529 529 ((( 530 - Higherbyte: Specifyhardwareversion: always 0x00forN95S31B479 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. 531 531 ))) 532 532 533 533 ((( 534 - Lowerbyte:Specifythesoftwareversion:0x6E=110, means firmwareversion110483 +Generally, the EC value of irrigation water is less than 800uS / cm. 535 535 ))) 536 536 537 537 ((( ... ... @@ -539,83 +539,71 @@ 539 539 ))) 540 540 541 541 ((( 542 - Forexample: 0x00 6E: this device is N95S31B with firmware version 110.491 + 543 543 ))) 544 544 494 +=== 2.4.8 Digital Interrupt === 495 + 545 545 ((( 546 - 497 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server. 547 547 ))) 548 548 549 - 550 -=== 2.3.4 Battery Info === 551 - 552 552 ((( 553 - Ex1:0x0B45 = 2885mV501 +The command is: 554 554 ))) 555 555 556 556 ((( 557 - Ex2:0x0B49=2889mV505 +(% 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]])**.** 558 558 ))) 559 559 560 560 509 +((( 510 +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. 511 +))) 561 561 562 -=== 2.3.5 Signal Strength === 563 563 564 564 ((( 565 - NB-IoT Network signalStrength.515 +Example: 566 566 ))) 567 567 568 568 ((( 569 - **Ex1:0x1d=29**519 +0x(00): Normal uplink packet. 570 570 ))) 571 571 572 572 ((( 573 -( %style="color:blue"%)**0**(%%) -113dBm orless523 +0x(01): Interrupt Uplink Packet. 574 574 ))) 575 575 526 + 527 + 528 +=== 2.4.9 +5V Output === 529 + 576 576 ((( 577 - (%style="color:blue"%)**1**(%%)-111dBm531 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 578 578 ))) 579 579 534 + 580 580 ((( 581 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm536 +The 5V output time can be controlled by AT Command. 582 582 ))) 583 583 584 584 ((( 585 -(% style="color:blue" %)** 31**(%%) -51dBm or greater540 +(% style="color:blue" %)**AT+5VT=1000** 586 586 ))) 587 587 588 588 ((( 589 - (%style="color:blue"%)**99**(%%)Notknownornotdetectable544 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 590 590 ))) 591 591 592 592 593 593 594 -== =2.3.6Temperature & Humidity ===549 +== 2.5 Downlink Payload == 595 595 596 - Thedevice will beabletoget theSHT31temperature and humiditydatanowandupload toIoT Server.551 +By default, NSE01 prints the downlink payload to console port. 597 597 598 -[[image:image-2022070 9161741-3.png]]553 +[[image:image-20220708133731-5.png]] 599 599 600 600 601 -Convert the read byte to decimal and divide it by ten. 602 - 603 - 604 -**Example:** 605 - 606 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 607 - 608 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 609 - 610 - 611 - 612 -== 2.4 Downlink Payload == 613 - 614 -By default, NDDS75 prints the downlink payload to console port. 615 - 616 -[[image:image-20220709100028-1.png]] 617 - 618 - 619 619 ((( 620 620 (% style="color:blue" %)**Examples:** 621 621 ))) ... ... @@ -649,7 +649,7 @@ 649 649 ))) 650 650 651 651 ((( 652 -If payload = 0x04FF, it will reset the N DDS75589 +If payload = 0x04FF, it will reset the NSE01 653 653 ))) 654 654 655 655 ... ... @@ -661,19 +661,78 @@ 661 661 662 662 663 663 664 -== 2. 5BatteryAnalysis==601 +== 2.6 LED Indicator == 665 665 666 -=== 2.5.1 Battery Type === 603 +((( 604 +The NSE01 has an internal LED which is to show the status of different state. 667 667 668 668 607 +* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 608 +* Then the LED will be on for 1 second means device is boot normally. 609 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds. 610 +* For each uplink probe, LED will be on for 500ms. 611 +))) 612 + 613 + 614 + 615 + 616 +== 2.7 Installation in Soil == 617 + 618 +__**Measurement the soil surface**__ 619 + 669 669 ((( 670 - TheN95S31B batteryisa combination ofan 8500mAhLi/SOCI2BatteryandaSuperCapacitor.Thebatteryisnone-rechargeablebatterytypewithaowdischargeate(<2%peryear).Thistype ofbatteryiscommonlyusedinIoT devicessuchaswatermeter.621 +Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]] 671 671 ))) 672 672 624 +[[image:1657259653666-883.png]] 625 + 626 + 673 673 ((( 628 + 629 + 630 +((( 631 +Dig a hole with diameter > 20CM. 632 +))) 633 + 634 +((( 635 +Horizontal insert the probe to the soil and fill the hole for long term measurement. 636 +))) 637 +))) 638 + 639 +[[image:1654506665940-119.png]] 640 + 641 +((( 642 + 643 +))) 644 + 645 + 646 +== 2.8 Firmware Change Log == 647 + 648 + 649 +Download URL & Firmware Change log 650 + 651 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]] 652 + 653 + 654 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 655 + 656 + 657 + 658 +== 2.9 Battery Analysis == 659 + 660 +=== 2.9.1 Battery Type === 661 + 662 + 663 +((( 664 +The NSE01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 665 +))) 666 + 667 + 668 +((( 674 674 The battery is designed to last for several years depends on the actually use environment and update interval. 675 675 ))) 676 676 672 + 677 677 ((( 678 678 The battery related documents as below: 679 679 ))) ... ... @@ -683,40 +683,61 @@ 683 683 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 684 684 685 685 ((( 686 -[[image:image-2022070 9101450-2.png]]682 +[[image:image-20220708140453-6.png]] 687 687 ))) 688 688 689 689 690 690 691 -=== 2. 5.2 Power consumption Analyze ===687 +=== 2.9.2 Power consumption Analyze === 692 692 693 693 ((( 694 - 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/]] describesadetailmeasurementtoanalyzethepowerconsumption indifferentcase. User can useitfordesignguideline fortheirproject.690 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 695 695 ))) 696 696 693 + 697 697 ((( 698 - 695 +Instruction to use as below: 699 699 ))) 700 700 698 +((( 699 +(% style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 700 +))) 701 701 702 -=== 2.5.3 Battery Note === 703 703 704 704 ((( 705 - TheLi-SICO batteryis designed for small current / long period application. It is not good tousea high current, short periodtransmitmethod.Therecommendedminimum period for use ofthisbattery is 5 minutes.If you use a shorter period time to uplink data, then the battery life may be decreased.704 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 706 706 ))) 707 707 707 +* ((( 708 +Product Model 709 +))) 710 +* ((( 711 +Uplink Interval 712 +))) 713 +* ((( 714 +Working Mode 715 +))) 708 708 717 +((( 718 +And the Life expectation in difference case will be shown on the right. 719 +))) 709 709 710 - ===2.5.4 Replacethe battery ===721 +[[image:image-20220708141352-7.jpeg]] 711 711 712 712 724 + 725 +=== 2.9.3 Battery Note === 726 + 713 713 ((( 714 - You can changethebattery intheN95S31B.Thetype ofbatteryis notlimitedaslongas theutput isbetween3vto3.6v.Onthemainboard,there isa diode(D1)betweenthebatteryandthemaincircuit. If youneed touse abatterywith less than 3.3v,pleaseremove the D1 andshortcut the twopadsofitso there won'tbe voltagedropbetween batteryandmainboard.728 +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 transmit LoRa, then the battery life may be decreased. 715 715 ))) 716 716 717 717 732 + 733 +=== 2.9.4 Replace the battery === 734 + 718 718 ((( 719 -The default battery pack of N 95S31Bincludes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).736 +The default battery pack of NSE01 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 720 720 ))) 721 721 722 722 ... ... @@ -731,7 +731,7 @@ 731 731 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/]] 732 732 ))) 733 733 734 -[[image:1657 333200519-600.png]]751 +[[image:1657261278785-153.png]] 735 735 736 736 737 737 ... ... @@ -739,7 +739,7 @@ 739 739 740 740 == 4.1 Access AT Commands == 741 741 742 -See NBSN95 AT Command inthis link for detail:s:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]759 +See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 743 743 744 744 745 745 AT+<CMD>? : Help on <CMD> ... ... @@ -827,15 +827,18 @@ 827 827 ))) 828 828 829 829 ((( 830 - 847 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update. 848 +))) 831 831 850 + 851 + 852 +== 5.2 Can I calibrate NSE01 to different soil types? == 853 + 832 832 ((( 833 - (%style="color:red"%)Notice,N95S31BandLSN50v2share thesamemotherboard.Theyuse thesameconnectionand method toupdate.855 +NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]]. 834 834 ))) 835 -))) 836 836 837 837 838 - 839 839 = 6. Trouble Shooting = 840 840 841 841 == 6.1 Connection problem when uploading firmware == ... ... @@ -863,7 +863,7 @@ 863 863 = 7. Order Info = 864 864 865 865 866 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**886 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 867 867 868 868 869 869 (% class="wikigeneratedid" %) ... ... @@ -878,7 +878,7 @@ 878 878 879 879 (% style="color:#037691" %)**Package Includes**: 880 880 881 -* N 95S31BNB-IoTTemperatureandHumiditySensor901 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 882 882 * External antenna x 1 883 883 ))) 884 884 ... ... @@ -887,10 +887,8 @@ 887 887 888 888 (% style="color:#037691" %)**Dimension and weight**: 889 889 890 -* Device Size: 13.0 x 5 x 4.5 cm 891 -* Device Weight: 150g 892 -* Package Size / pcs : 14.0 x 8x 5 cm 893 -* Weight / pcs : 180g 910 +* Size: 195 x 125 x 55 mm 911 +* Weight: 420g 894 894 ))) 895 895 896 896 (((
- 1657328756309-230.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -78.5 KB - Content
- 1657328884227-504.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -483.6 KB - Content
- 1657329814315-101.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -85.3 KB - Content
- 1657330452568-615.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -71.3 KB - Content
- 1657330472797-498.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -68.9 KB - Content
- 1657330501006-241.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -119.2 KB - Content
- 1657330533775-472.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.9 KB - Content
- 1657330723006-866.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.1 KB - Content
- 1657331036973-987.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -83.8 KB - Content
- 1657332990863-496.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.2 KB - Content
- 1657333200519-600.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- 1657348034241-728.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -127.8 KB - Content
- 1657348284168-431.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.5 KB - Content
- 1657350248151-650.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- 1657350625843-586.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.3 KB - Content
- 1657351240556-536.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -483.6 KB - Content
- 1657351312545-300.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -675.8 KB - Content
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- image-20220709092052-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -247.3 KB - Content
- image-20220709093918-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -42.2 KB - Content
- image-20220709093918-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -61.9 KB - Content
- image-20220709100028-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -8.8 KB - Content
- image-20220709101450-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.5 KB - Content
- image-20220709110451-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -611.5 KB - Content
- image-20220709144723-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -413.1 KB - Content
- image-20220709150546-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -333.5 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content