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, 36 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
- 1657520100595-569.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,68 +1,57 @@ 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 ... ... @@ -85,6 +85,7 @@ 85 85 * - B20 @H-FDD: 800MHz 86 86 * - B28 @H-FDD: 700MHz 87 87 77 + 88 88 (% style="color:#037691" %)**Battery:** 89 89 90 90 * Li/SOCI2 un-chargeable battery ... ... @@ -94,7 +94,14 @@ 94 94 * Max boost current: 2A, 1 second 95 95 96 96 87 +(% style="color:#037691" %)**Power Consumption** 97 97 89 +* STOP Mode: 10uA @ 3.3v 90 +* Max transmit power: 350mA@3.3v 91 + 92 + 93 + 94 + 98 98 == 1.4 Applications == 99 99 100 100 * Smart Buildings & Home Automation ... ... @@ -108,58 +108,26 @@ 108 108 109 109 110 110 111 -== 1.5 Pin Definitions & Switch == 112 112 113 - N95S31Busethemother boardfrom NBSN95 which asbelow.109 +== 1.5 Pin Definitions == 114 114 115 -[[image:image-20220709144723-1.png]] 116 116 112 +[[image:1657328609906-564.png]] 117 117 118 -=== 1.5.1 Jumper JP2 === 119 119 120 -Power on Device when put this jumper. 121 121 122 122 117 += 2. Use NSE01 to communicate with IoT Server = 123 123 124 -=== 1.5.2 BOOT MODE / SW1 === 125 - 126 -((( 127 -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. 128 -))) 129 - 130 -((( 131 -2) Flash: work mode, device starts to work and send out console output for further debug 132 -))) 133 - 134 - 135 - 136 -=== 1.5.3 Reset Button === 137 - 138 -Press to reboot the device. 139 - 140 - 141 - 142 -=== 1.5.4 LED === 143 - 144 -It will flash: 145 - 146 -1. When boot the device in flash mode 147 -1. Send an uplink packet 148 - 149 - 150 - 151 -= 2. Use N95S31B to communicate with IoT Server = 152 - 153 153 == 2.1 How it works == 154 154 155 - 156 156 ((( 157 -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.122 +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. 158 158 ))) 159 159 160 160 161 161 ((( 162 -The diagram below shows the working flow in default firmware of N 95S31B:127 +The diagram below shows the working flow in default firmware of NDDS75: 163 163 ))) 164 164 165 165 ((( ... ... @@ -166,7 +166,7 @@ 166 166 167 167 ))) 168 168 169 -[[image:1657 520100595-569.png]]134 +[[image:1657328659945-416.png]] 170 170 171 171 ((( 172 172 ... ... @@ -173,67 +173,31 @@ 173 173 ))) 174 174 175 175 176 -== 2.2 Configure the N 95S31B==141 +== 2.2 Configure the NSE01 == 177 177 178 178 179 -=== 2.2.1 Power On N95S31B === 180 - 181 - 182 -[[image:image-20220709150546-2.png]] 183 - 184 - 185 185 === 2.2.1 Test Requirement === 186 186 187 187 188 188 ((( 189 -To use N 95S31Bin your city, make sure meet below requirements:148 +To use NSE01 in your city, make sure meet below requirements: 190 190 ))) 191 191 192 -* ((( 193 -Your local operator has already distributed a NB-IoT Network there. 194 -))) 195 -* ((( 196 -The local NB-IoT network used the band that N95S31B supports. 197 -))) 198 -* ((( 199 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 200 -))) 151 +* Your local operator has already distributed a NB-IoT Network there. 152 +* The local NB-IoT network used the band that NSE01 supports. 153 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 201 201 202 202 ((( 203 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 156 +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 204 204 ))) 205 205 206 -((( 207 -N95S31B supports different communication protocol such as : 208 -))) 209 209 210 -((( 211 -* ((( 212 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 213 -))) 214 -* ((( 215 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 216 -))) 217 -* ((( 218 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 219 -))) 220 -* ((( 221 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 222 -))) 160 +[[image:1657249419225-449.png]] 223 223 224 -((( 225 -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. 226 -))) 227 227 228 - 229 -))) 230 230 231 - [[image:1657350625843-586.png]]164 +=== 2.2.2 Insert SIM card === 232 232 233 - 234 - 235 -=== 2.2.3 Insert SIM card === 236 - 237 237 ((( 238 238 Insert the NB-IoT Card get from your provider. 239 239 ))) ... ... @@ -243,19 +243,18 @@ 243 243 ))) 244 244 245 245 246 -[[image:1657 351240556-536.png]]175 +[[image:1657249468462-536.png]] 247 247 248 248 249 249 250 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===179 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it === 251 251 252 252 ((( 253 253 ((( 254 -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.183 +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. 255 255 ))) 256 256 ))) 257 257 258 -[[image:1657351312545-300.png]] 259 259 260 260 **Connection:** 261 261 ... ... @@ -275,110 +275,96 @@ 275 275 * Flow Control: (% style="color:green" %)**None** 276 276 277 277 ((( 278 -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.206 +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. 279 279 ))) 280 280 281 -[[image: 1657329814315-101.png]]209 +[[image:image-20220708110657-3.png]] 282 282 283 283 ((( 284 -(% 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/]]212 +(% 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/]] 285 285 ))) 286 286 287 287 288 288 289 -=== 2.2. 5Use CoAP protocol to uplink data ===217 +=== 2.2.4 Use CoAP protocol to uplink data === 290 290 291 291 (% 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/]] 292 292 293 293 294 -((( 295 295 **Use below commands:** 296 -))) 297 297 298 -* ((( 299 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 300 -))) 301 -* ((( 302 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 303 -))) 304 -* ((( 305 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 306 -))) 224 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 225 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 226 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 307 307 308 -((( 309 - 310 - 311 311 For parameter description, please refer to AT command set 312 -))) 313 313 314 -[[image:1657 352146020-183.png]]230 +[[image:1657249793983-486.png]] 315 315 316 316 317 -((( 318 -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. 319 -))) 233 +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. 320 320 321 -[[image:1657 352185396-303.png]]235 +[[image:1657249831934-534.png]] 322 322 323 323 324 324 325 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===239 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 326 326 241 +This feature is supported since firmware version v1.0.1 327 327 328 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 243 + 244 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 329 329 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 330 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 246 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 331 331 332 -[[image:1657 352391268-297.png]]248 +[[image:1657249864775-321.png]] 333 333 334 334 335 -[[image:1657 352403317-397.png]]251 +[[image:1657249930215-289.png]] 336 336 337 337 338 338 339 -=== 2.2. 7Use MQTT protocol to uplink data ===255 +=== 2.2.6 Use MQTT protocol to uplink data === 340 340 341 - N95S31Bsupportsonly plain MQTT now itdoesn'tsupportTLS and otherlated encryption.257 +This feature is supported since firmware version v110 342 342 343 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 344 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 345 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 346 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 347 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 348 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 349 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 350 350 351 -[[image:1657352634421-276.png]] 260 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 261 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 262 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 263 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 264 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 265 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB **(%%)~/~/Set the sending topic of MQTT 266 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB **(%%) ~/~/Set the subscription topic of MQTT 352 352 268 +[[image:1657249978444-674.png]] 353 353 354 -[[image:1657352645687-385.png]] 355 355 356 -((( 357 -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. 358 -))) 271 +[[image:1657249990869-686.png]] 359 359 360 360 361 361 ((( 362 -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.275 +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. 363 363 ))) 364 364 365 365 366 366 367 -=== 2.2. 8Use TCP protocol to uplink data ===280 +=== 2.2.7 Use TCP protocol to uplink data === 368 368 369 369 This feature is supported since firmware version v110 370 370 284 + 371 371 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 372 372 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 373 373 374 -[[image:1657 352898400-901.png]]288 +[[image:1657250217799-140.png]] 375 375 376 376 377 -[[image:1657 352914475-252.png]]291 +[[image:1657250255956-604.png]] 378 378 379 379 380 380 381 -=== 2.2. 9Change Update Interval ===295 +=== 2.2.8 Change Update Interval === 382 382 383 383 User can use below command to change the (% style="color:green" %)**uplink interval**. 384 384 ... ... @@ -385,155 +385,190 @@ 385 385 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 386 386 387 387 ((( 388 - 302 +(% style="color:red" %)**NOTE:** 389 389 ))) 390 390 305 +((( 306 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 307 +))) 391 391 392 392 310 + 393 393 == 2.3 Uplink Payload == 394 394 313 +In this mode, uplink payload includes in total 18 bytes 395 395 315 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 316 +|=(% style="width: 60px;" %)((( 317 +**Size(bytes)** 318 +)))|=(% 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** 319 +|(% 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"]] 320 + 396 396 ((( 397 - NBSN95 has differentworkingmodeforthe connections of different typeofsensors. This section describesthesemodes.Usercanuse theAT Command (% style="color:blue"%)**AT+MOD**(%%)toset NBSN95to different workingmodes.322 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data. 398 398 ))) 399 399 400 400 326 +[[image:image-20220708111918-4.png]] 327 + 328 + 329 +The payload is ASCII string, representative same HEX: 330 + 331 +0x72403155615900640c7817075e0a8c02f900 where: 332 + 333 +* Device ID: 0x 724031556159 = 724031556159 334 +* Version: 0x0064=100=1.0.0 335 + 336 +* BAT: 0x0c78 = 3192 mV = 3.192V 337 +* Singal: 0x17 = 23 338 +* Soil Moisture: 0x075e= 1886 = 18.86 % 339 +* Soil Temperature:0x0a8c =2700=27 °C 340 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm 341 +* Interrupt: 0x00 = 0 342 + 343 +== 2.4 Payload Explanation and Sensor Interface == 344 + 345 + 346 +=== 2.4.1 Device ID === 347 + 401 401 ((( 402 - Forexample:349 +By default, the Device ID equal to the last 6 bytes of IMEI. 403 403 ))) 404 404 405 405 ((( 406 - (% style="color:blue" %)**AT+ CFGMOD=2**~/~/willsetthe NBSN95 towork in MOD=2 distancemode whichtargetto measure distancevia UltrasonicSensor.353 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 407 407 ))) 408 408 409 - 410 410 ((( 411 - The uplink payloads are composed in ASCII String. For example:357 +**Example:** 412 412 ))) 413 413 414 414 ((( 415 -0 a cd 00 ed 0a cc 00 00 ef 02 d21d (total24 ASCII Chars) . Representative the actually payload:361 +AT+DEUI=A84041F15612 416 416 ))) 417 417 418 418 ((( 419 - 0x0acd00ed0acc0000ef02d21dTotal12 bytes365 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 420 420 ))) 421 421 422 422 369 + 370 +=== 2.4.2 Version Info === 371 + 423 423 ((( 424 - (%style="color:red"%)**NOTE:**373 +Specify the software version: 0x64=100, means firmware version 1.00. 425 425 ))) 426 426 427 -(% style="color:red" %) 428 -1. ((( 429 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 376 +((( 377 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0. 430 430 ))) 431 -1. ((( 432 -By default, the device will send an uplink message every 1 hour. 433 -))) 434 434 435 -=== 2.3.1 Payload Analyze === 436 436 437 -N95S31B uplink payload includes in total 21 bytes 438 438 382 +=== 2.4.3 Battery Info === 439 439 440 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 441 -|=(% style="width: 60px;" %)((( 442 -**Size(bytes)** 443 -)))|=(% 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** 444 -|(% 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" %)((( 445 445 ((( 446 - Reserve/Same asNBSN95CFGMOD=1385 +Check the battery voltage for LSE01. 447 447 ))) 448 448 449 449 ((( 450 - Nofunctionhere.389 +Ex1: 0x0B45 = 2885mV 451 451 ))) 452 - )))|(% style="width:77px" %)(((391 + 453 453 ((( 454 - [[Temperature>>||anchor="H2.3.6A0Temperature26Humidity"]]393 +Ex2: 0x0B49 = 2889mV 455 455 ))) 456 456 396 + 397 + 398 +=== 2.4.4 Signal Strength === 399 + 457 457 ((( 458 -B ySHT31401 +NB-IoT Network signal Strength. 459 459 ))) 460 - )))|(% style="width:80px" %)(((403 + 461 461 ((( 462 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]405 +**Ex1: 0x1d = 29** 463 463 ))) 464 464 465 465 ((( 466 - BySHT31409 +(% style="color:blue" %)**0**(%%) -113dBm or less 467 467 ))) 411 + 412 +((( 413 +(% style="color:blue" %)**1**(%%) -111dBm 468 468 ))) 469 469 470 470 ((( 417 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 418 +))) 419 + 471 471 ((( 472 - Ifwe usetheMQTTclient tosubscribetothisMQTTtopic,wecansee the followinginformation when the NB sensoruplink data.421 +(% style="color:blue" %)**31** (%%) -51dBm or greater 473 473 ))) 423 + 424 +((( 425 +(% style="color:blue" %)**99** (%%) Not known or not detectable 474 474 ))) 475 475 476 476 477 -[[image:1657354294009-643.png]] 478 478 430 +=== 2.4.5 Soil Moisture === 479 479 480 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 432 +((( 433 +((( 434 +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. 435 +))) 436 +))) 481 481 482 -* Device ID: 0x724031607457 = 724031607457 483 -* Version: 0x006e=110=1.1.0 438 +((( 439 +((( 440 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is 441 +))) 442 +))) 484 484 485 -* BAT: 0x0ccd = 3277 mV = 3.277V 486 -* Signal: 0x1b = 27 487 -* Model: 0x01 = 1 488 -* 0x00dc000ccc= reserve, ignore in N95S31B 489 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 490 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 491 - 492 492 ((( 493 493 494 494 ))) 495 495 496 496 ((( 497 - 449 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.** 498 498 ))) 499 499 500 500 501 -=== 2.3.2 Device ID === 502 502 503 -((( 504 -By default, the Device ID equal to the last 6 bytes of IMEI. 505 -))) 454 +=== 2.4.6 Soil Temperature === 506 506 507 507 ((( 508 - Usercan use (%style="color:blue"%)**AT+DEUI**(%%)tosetDeviceID457 +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 509 509 ))) 510 510 511 511 ((( 512 -**Example :**461 +**Example**: 513 513 ))) 514 514 515 515 ((( 516 - AT+DEUI=A84041F15612465 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C 517 517 ))) 518 518 519 519 ((( 520 - The DeviceIDis stored inanone-erasearea,Upgradethefirmwareorrun **AT+FDR**won'terase Device ID.469 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C 521 521 ))) 522 522 523 523 524 524 525 -=== 2. 3.3VersionInfo===474 +=== 2.4.7 Soil Conductivity (EC) === 526 526 527 527 ((( 528 - These bytes include thehardware andsoftwareversion.477 +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). 529 529 ))) 530 530 531 531 ((( 532 - Higherbyte: Specifyhardwareversion: always 0x00forN95S31B481 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. 533 533 ))) 534 534 535 535 ((( 536 - Lowerbyte:Specifythesoftwareversion:0x6E=110, means firmwareversion110485 +Generally, the EC value of irrigation water is less than 800uS / cm. 537 537 ))) 538 538 539 539 ((( ... ... @@ -541,83 +541,71 @@ 541 541 ))) 542 542 543 543 ((( 544 - Forexample: 0x00 6E: this device is N95S31B with firmware version 110.493 + 545 545 ))) 546 546 496 +=== 2.4.8 Digital Interrupt === 497 + 547 547 ((( 548 - 499 +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. 549 549 ))) 550 550 551 - 552 -=== 2.3.4 Battery Info === 553 - 554 554 ((( 555 - Ex1:0x0B45 = 2885mV503 +The command is: 556 556 ))) 557 557 558 558 ((( 559 - Ex2:0x0B49=2889mV507 +(% 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]])**.** 560 560 ))) 561 561 562 562 511 +((( 512 +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. 513 +))) 563 563 564 -=== 2.3.5 Signal Strength === 565 565 566 566 ((( 567 - NB-IoT Network signalStrength.517 +Example: 568 568 ))) 569 569 570 570 ((( 571 - **Ex1:0x1d=29**521 +0x(00): Normal uplink packet. 572 572 ))) 573 573 574 574 ((( 575 -( %style="color:blue"%)**0**(%%) -113dBm orless525 +0x(01): Interrupt Uplink Packet. 576 576 ))) 577 577 528 + 529 + 530 +=== 2.4.9 +5V Output === 531 + 578 578 ((( 579 - (%style="color:blue"%)**1**(%%)-111dBm533 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 580 580 ))) 581 581 536 + 582 582 ((( 583 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm538 +The 5V output time can be controlled by AT Command. 584 584 ))) 585 585 586 586 ((( 587 -(% style="color:blue" %)** 31**(%%) -51dBm or greater542 +(% style="color:blue" %)**AT+5VT=1000** 588 588 ))) 589 589 590 590 ((( 591 - (%style="color:blue"%)**99**(%%)Notknownornotdetectable546 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 592 592 ))) 593 593 594 594 595 595 596 -== =2.3.6Temperature & Humidity ===551 +== 2.5 Downlink Payload == 597 597 598 - Thedevice will beabletoget theSHT31temperature and humiditydatanowandupload toIoT Server.553 +By default, NSE01 prints the downlink payload to console port. 599 599 600 -[[image:image-2022070 9161741-3.png]]555 +[[image:image-20220708133731-5.png]] 601 601 602 602 603 -Convert the read byte to decimal and divide it by ten. 604 - 605 - 606 -**Example:** 607 - 608 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 609 - 610 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 611 - 612 - 613 - 614 -== 2.4 Downlink Payload == 615 - 616 -By default, NDDS75 prints the downlink payload to console port. 617 - 618 -[[image:image-20220709100028-1.png]] 619 - 620 - 621 621 ((( 622 622 (% style="color:blue" %)**Examples:** 623 623 ))) ... ... @@ -651,7 +651,7 @@ 651 651 ))) 652 652 653 653 ((( 654 -If payload = 0x04FF, it will reset the N DDS75591 +If payload = 0x04FF, it will reset the NSE01 655 655 ))) 656 656 657 657 ... ... @@ -663,19 +663,78 @@ 663 663 664 664 665 665 666 -== 2. 5BatteryAnalysis==603 +== 2.6 LED Indicator == 667 667 668 -=== 2.5.1 Battery Type === 605 +((( 606 +The NSE01 has an internal LED which is to show the status of different state. 669 669 670 670 609 +* 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) 610 +* Then the LED will be on for 1 second means device is boot normally. 611 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds. 612 +* For each uplink probe, LED will be on for 500ms. 613 +))) 614 + 615 + 616 + 617 + 618 +== 2.7 Installation in Soil == 619 + 620 +__**Measurement the soil surface**__ 621 + 671 671 ((( 672 - TheN95S31B batteryisa combination ofan 8500mAhLi/SOCI2BatteryandaSuperCapacitor.Thebatteryisnone-rechargeablebatterytypewithaowdischargeate(<2%peryear).Thistype ofbatteryiscommonlyusedinIoT devicessuchaswatermeter.623 +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]] 673 673 ))) 674 674 626 +[[image:1657259653666-883.png]] 627 + 628 + 675 675 ((( 630 + 631 + 632 +((( 633 +Dig a hole with diameter > 20CM. 634 +))) 635 + 636 +((( 637 +Horizontal insert the probe to the soil and fill the hole for long term measurement. 638 +))) 639 +))) 640 + 641 +[[image:1654506665940-119.png]] 642 + 643 +((( 644 + 645 +))) 646 + 647 + 648 +== 2.8 Firmware Change Log == 649 + 650 + 651 +Download URL & Firmware Change log 652 + 653 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]] 654 + 655 + 656 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 657 + 658 + 659 + 660 +== 2.9 Battery Analysis == 661 + 662 +=== 2.9.1 Battery Type === 663 + 664 + 665 +((( 666 +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. 667 +))) 668 + 669 + 670 +((( 676 676 The battery is designed to last for several years depends on the actually use environment and update interval. 677 677 ))) 678 678 674 + 679 679 ((( 680 680 The battery related documents as below: 681 681 ))) ... ... @@ -685,40 +685,61 @@ 685 685 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 686 686 687 687 ((( 688 -[[image:image-2022070 9101450-2.png]]684 +[[image:image-20220708140453-6.png]] 689 689 ))) 690 690 691 691 692 692 693 -=== 2. 5.2 Power consumption Analyze ===689 +=== 2.9.2 Power consumption Analyze === 694 694 695 695 ((( 696 - 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.692 +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. 697 697 ))) 698 698 695 + 699 699 ((( 700 - 697 +Instruction to use as below: 701 701 ))) 702 702 700 +((( 701 +(% 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/]] 702 +))) 703 703 704 -=== 2.5.3 Battery Note === 705 705 706 706 ((( 707 - 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.706 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 708 708 ))) 709 709 709 +* ((( 710 +Product Model 711 +))) 712 +* ((( 713 +Uplink Interval 714 +))) 715 +* ((( 716 +Working Mode 717 +))) 710 710 719 +((( 720 +And the Life expectation in difference case will be shown on the right. 721 +))) 711 711 712 - ===2.5.4 Replacethe battery ===723 +[[image:image-20220708141352-7.jpeg]] 713 713 714 714 726 + 727 +=== 2.9.3 Battery Note === 728 + 715 715 ((( 716 - 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.730 +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. 717 717 ))) 718 718 719 719 734 + 735 +=== 2.9.4 Replace the battery === 736 + 720 720 ((( 721 -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).738 +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). 722 722 ))) 723 723 724 724 ... ... @@ -733,7 +733,7 @@ 733 733 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/]] 734 734 ))) 735 735 736 -[[image:1657 333200519-600.png]]753 +[[image:1657261278785-153.png]] 737 737 738 738 739 739 ... ... @@ -741,7 +741,7 @@ 741 741 742 742 == 4.1 Access AT Commands == 743 743 744 -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/]]761 +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/]] 745 745 746 746 747 747 AT+<CMD>? : Help on <CMD> ... ... @@ -829,15 +829,18 @@ 829 829 ))) 830 830 831 831 ((( 832 - 849 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update. 850 +))) 833 833 852 + 853 + 854 +== 5.2 Can I calibrate NSE01 to different soil types? == 855 + 834 834 ((( 835 - (%style="color:red"%)Notice,N95S31BandLSN50v2share thesamemotherboard.Theyuse thesameconnectionand method toupdate.857 +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]]. 836 836 ))) 837 -))) 838 838 839 839 840 - 841 841 = 6. Trouble Shooting = 842 842 843 843 == 6.1 Connection problem when uploading firmware == ... ... @@ -865,7 +865,7 @@ 865 865 = 7. Order Info = 866 866 867 867 868 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**888 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 869 869 870 870 871 871 (% class="wikigeneratedid" %) ... ... @@ -880,7 +880,7 @@ 880 880 881 881 (% style="color:#037691" %)**Package Includes**: 882 882 883 -* N 95S31BNB-IoTTemperatureandHumiditySensor903 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 884 884 * External antenna x 1 885 885 ))) 886 886 ... ... @@ -889,10 +889,8 @@ 889 889 890 890 (% style="color:#037691" %)**Dimension and weight**: 891 891 892 -* Device Size: 13.0 x 5 x 4.5 cm 893 -* Device Weight: 150g 894 -* Package Size / pcs : 14.0 x 8x 5 cm 895 -* Weight / pcs : 180g 912 +* Size: 195 x 125 x 55 mm 913 +* Weight: 420g 896 896 ))) 897 897 898 898 (((
- 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
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 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