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, 31 removed)
- 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-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,74 +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 70 70 71 - 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -77,7 +77,6 @@ 77 77 * Supply Voltage: 2.1v ~~ 3.6v 78 78 * Operating Temperature: -40 ~~ 85°C 79 79 80 - 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 83 * - B1 @H-FDD: 2100MHz ... ... @@ -97,8 +97,14 @@ 97 97 * Max boost current: 2A, 1 second 98 98 99 99 87 +(% style="color:#037691" %)**Power Consumption** 100 100 89 +* STOP Mode: 10uA @ 3.3v 90 +* Max transmit power: 350mA@3.3v 101 101 92 + 93 + 94 + 102 102 == 1.4 Applications == 103 103 104 104 * Smart Buildings & Home Automation ... ... @@ -112,56 +112,26 @@ 112 112 113 113 114 114 108 + 115 115 == 1.5 Pin Definitions == 116 116 117 -N95S31B use the mother board from NBSN95 which as below. 118 118 119 -[[image: image-20220709144723-1.png]]112 +[[image:1657328609906-564.png]] 120 120 121 121 122 -=== 1.5.1 Jumper JP2 === 123 123 124 -Power on Device when put this jumper. 125 125 117 += 2. Use NDDS75 to communicate with IoT Server = 126 126 127 - 128 -=== 1.5.2 BOOT MODE / SW1 === 129 - 130 -((( 131 -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. 132 -))) 133 - 134 -((( 135 -2) Flash: work mode, device starts to work and send out console output for further debug 136 -))) 137 - 138 - 139 - 140 -=== 1.5.3 Reset Button === 141 - 142 -Press to reboot the device. 143 - 144 - 145 - 146 -=== 1.5.4 LED === 147 - 148 -It will flash: 149 - 150 -1. When boot the device in flash mode 151 -1. Send an uplink packet 152 - 153 -= 2. Use N95S31B to communicate with IoT Server = 154 - 155 155 == 2.1 How it works == 156 156 157 - 158 158 ((( 159 -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. 160 160 ))) 161 161 162 162 163 163 ((( 164 -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: 165 165 ))) 166 166 167 167 ((( ... ... @@ -168,7 +168,7 @@ 168 168 169 169 ))) 170 170 171 -[[image:16573 50248151-650.png]]134 +[[image:1657328659945-416.png]] 172 172 173 173 ((( 174 174 ... ... @@ -175,45 +175,30 @@ 175 175 ))) 176 176 177 177 178 -== 2.2 Configure the N 95S31B==141 +== 2.2 Configure the NDDS75 == 179 179 180 180 181 -=== 2.2.1 Power On N95S31B === 182 - 183 - 184 -[[image:image-20220709150546-2.png]] 185 - 186 - 187 187 === 2.2.1 Test Requirement === 188 188 146 +((( 147 +To use NDDS75 in your city, make sure meet below requirements: 148 +))) 189 189 190 -To use N95S31B in your city, make sure meet below requirements: 191 - 192 192 * Your local operator has already distributed a NB-IoT Network there. 193 -* The local NB-IoT network used the band that N 95S31Bsupports.151 +* The local NB-IoT network used the band that NSE01 supports. 194 194 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 195 195 196 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 197 - 198 -N95S31B supports different communication protocol such as : 199 - 200 200 ((( 201 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 202 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 203 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 204 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 205 - 206 -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. 207 - 208 - 155 +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 209 209 ))) 210 210 211 -[[image:1657350625843-586.png]] 212 212 159 +[[image:1657328756309-230.png]] 213 213 214 214 215 -=== 2.2.3 Insert SIM card === 216 216 163 +=== 2.2.2 Insert SIM card === 164 + 217 217 ((( 218 218 Insert the NB-IoT Card get from your provider. 219 219 ))) ... ... @@ -223,19 +223,19 @@ 223 223 ))) 224 224 225 225 226 -[[image:16573 51240556-536.png]]174 +[[image:1657328884227-504.png]] 227 227 228 228 229 229 230 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===178 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 231 231 232 232 ((( 233 233 ((( 234 -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.182 +User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below. 235 235 ))) 236 236 ))) 237 237 238 -[[image: 1657351312545-300.png]]186 +[[image:image-20220709092052-2.png]] 239 239 240 240 **Connection:** 241 241 ... ... @@ -255,110 +255,96 @@ 255 255 * Flow Control: (% style="color:green" %)**None** 256 256 257 257 ((( 258 -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 NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 259 259 ))) 260 260 261 261 [[image:1657329814315-101.png]] 262 262 263 263 ((( 264 -(% style="color:red" %)Note: the valid AT Commands can be found at: 95S31B/>>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: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]] 265 265 ))) 266 266 267 267 268 268 269 -=== 2.2. 5Use CoAP protocol to uplink data ===217 +=== 2.2.4 Use CoAP protocol to uplink data === 270 270 271 271 (% 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/]] 272 272 273 273 274 -((( 275 275 **Use below commands:** 276 -))) 277 277 278 -* ((( 279 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 280 -))) 281 -* ((( 282 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 283 -))) 284 -* ((( 285 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 286 -))) 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 287 287 288 -((( 289 - 290 - 291 291 For parameter description, please refer to AT command set 292 -))) 293 293 294 -[[image:1657 352146020-183.png]]230 +[[image:1657249793983-486.png]] 295 295 296 296 297 -((( 298 -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. 299 -))) 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. 300 300 301 -[[image:1657 352185396-303.png]]235 +[[image:1657249831934-534.png]] 302 302 303 303 304 304 305 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===239 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 306 306 241 +This feature is supported since firmware version v1.0.1 307 307 308 -* (% 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 309 309 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 310 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 246 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 311 311 312 -[[image:1657 352391268-297.png]]248 +[[image:1657249864775-321.png]] 313 313 314 314 315 -[[image:1657 352403317-397.png]]251 +[[image:1657249930215-289.png]] 316 316 317 317 318 318 319 -=== 2.2. 7Use MQTT protocol to uplink data ===255 +=== 2.2.6 Use MQTT protocol to uplink data === 320 320 321 - N95S31Bsupportsonly plain MQTT now itdoesn'tsupportTLS and otherlated encryption.257 +This feature is supported since firmware version v110 322 322 323 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 324 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 325 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 326 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 327 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 328 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 329 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 330 330 331 -[[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 332 332 268 +[[image:1657249978444-674.png]] 333 333 334 -[[image:1657352645687-385.png]] 335 335 336 -((( 337 -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. 338 -))) 271 +[[image:1657249990869-686.png]] 339 339 340 340 341 341 ((( 342 -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. 343 343 ))) 344 344 345 345 346 346 347 -=== 2.2. 8Use TCP protocol to uplink data ===280 +=== 2.2.7 Use TCP protocol to uplink data === 348 348 349 349 This feature is supported since firmware version v110 350 350 284 + 351 351 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 352 352 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 353 353 354 -[[image:1657 352898400-901.png]]288 +[[image:1657250217799-140.png]] 355 355 356 356 357 -[[image:1657 352914475-252.png]]291 +[[image:1657250255956-604.png]] 358 358 359 359 360 360 361 -=== 2.2. 9Change Update Interval ===295 +=== 2.2.8 Change Update Interval === 362 362 363 363 User can use below command to change the (% style="color:green" %)**uplink interval**. 364 364 ... ... @@ -365,212 +365,262 @@ 365 365 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 366 366 367 367 ((( 368 - 302 +(% style="color:red" %)**NOTE:** 369 369 ))) 370 370 305 +((( 306 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 307 +))) 371 371 372 372 310 + 373 373 == 2.3 Uplink Payload == 374 374 313 +In this mode, uplink payload includes in total 18 bytes 375 375 376 -NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes. 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"]] 377 377 321 +((( 322 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data. 323 +))) 378 378 379 -For example: 380 380 381 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distancemode which target tomeasuredistance via Ultrasonic Sensor.326 +[[image:image-20220708111918-4.png]] 382 382 383 383 384 -The uplink payloadsare composedinASCIIString.Forxample:329 +The payload is ASCII string, representative same HEX: 385 385 386 -0 a cd00d0ac000ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:331 +0x72403155615900640c7817075e0a8c02f900 where: 387 387 388 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 333 +* Device ID: 0x 724031556159 = 724031556159 334 +* Version: 0x0064=100=1.0.0 389 389 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 390 390 391 - (%style="color:red"%)**NOTE:**343 +== 2.4 Payload Explanation and Sensor Interface == 392 392 393 -(% style="color:red" %) 394 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 395 -1. By default, the device will send an uplink message every 1 hour. 396 396 346 +=== 2.4.1 Device ID === 397 397 398 -=== 2.3.1 Payload Analyze === 399 - 400 -N95S31B uplink payload includes in total 21 bytes 401 - 402 - 403 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 404 -|=(% style="width: 60px;" %)((( 405 -**Size(bytes)** 406 -)))|=(% 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** 407 -|(% 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" %)((( 408 408 ((( 409 - Reserve/Same asNBSN95CFGMOD=1349 +By default, the Device ID equal to the last 6 bytes of IMEI. 410 410 ))) 411 411 412 412 ((( 413 - Nofunctionhere.353 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 414 414 ))) 415 - )))|(% style="width:77px" %)(((355 + 416 416 ((( 417 - [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]357 +**Example:** 418 418 ))) 419 419 420 420 ((( 421 - By SHT31361 +AT+DEUI=A84041F15612 422 422 ))) 423 - )))|(% style="width:80px" %)(((363 + 424 424 ((( 425 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]365 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 426 426 ))) 427 427 368 + 369 + 370 +=== 2.4.2 Version Info === 371 + 428 428 ((( 429 - BySHT31373 +Specify the software version: 0x64=100, means firmware version 1.00. 430 430 ))) 431 -))) 432 432 433 433 ((( 434 -((( 435 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 377 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0. 436 436 ))) 437 -))) 438 438 439 439 440 -[[image:1657354294009-643.png]] 441 441 382 +=== 2.4.3 Battery Info === 442 442 443 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 384 +((( 385 +Check the battery voltage for LSE01. 386 +))) 444 444 445 -* Device ID: 0x724031607457 = 724031607457 446 -* Version: 0x006e=110=1.1.0 447 - 448 -* BAT: 0x0ccd = 3277 mV = 3.277V 449 -* Signal: 0x1b = 27 450 -* Model: 0x01 = 1 451 -* 0x00dc000ccc= reserve, ignore in N95S31B 452 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 453 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 454 - 455 455 ((( 456 - 389 +Ex1: 0x0B45 = 2885mV 457 457 ))) 458 458 459 459 ((( 460 - 393 +Ex2: 0x0B49 = 2889mV 461 461 ))) 462 462 463 463 464 -=== 2.3.2 Device ID === 465 465 398 +=== 2.4.4 Signal Strength === 399 + 466 466 ((( 467 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.401 +NB-IoT Network signal Strength. 468 468 ))) 469 469 470 470 ((( 471 - User can use (% style="color:blue" %)**AT+DEUI**(%%)tosetDevice ID405 +**Ex1: 0x1d = 29** 472 472 ))) 473 473 474 474 ((( 475 - **Example:**409 +(% style="color:blue" %)**0**(%%) -113dBm or less 476 476 ))) 477 477 478 478 ((( 479 - AT+DEUI=A84041F15612413 +(% style="color:blue" %)**1**(%%) -111dBm 480 480 ))) 481 481 482 482 ((( 483 - TheDevice ID isstored in a none-erase area, Upgrade the firmwareorrun**AT+FDR**won't erase Device ID.417 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 484 484 ))) 485 485 420 +((( 421 +(% style="color:blue" %)**31** (%%) -51dBm or greater 422 +))) 486 486 424 +((( 425 +(% style="color:blue" %)**99** (%%) Not known or not detectable 426 +))) 487 487 488 -=== 2.3.3 Version Info === 489 489 490 490 491 - Thesebytesincludethe hardware and softwareversion.430 +=== 2.4.5 Soil Moisture === 492 492 493 -Higher byte: Specify hardware version: always 0x00 for N95S31B 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 +))) 494 494 495 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 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 +))) 496 496 497 - 498 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 499 - 500 500 ((( 501 501 502 502 ))) 503 503 448 +((( 449 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.** 450 +))) 504 504 505 -=== 2.3.4 Battery Info === 506 506 453 + 454 +=== 2.4.6 Soil Temperature === 455 + 507 507 ((( 508 - Ex1:0x0B45=2885mV457 +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 -Ex 2: 0x0B49 = 2889mV461 +**Example**: 513 513 ))) 514 514 464 +((( 465 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C 466 +))) 515 515 468 +((( 469 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C 470 +))) 516 516 517 -=== 2.3.5 Signal Strength === 518 518 473 + 474 +=== 2.4.7 Soil Conductivity (EC) === 475 + 519 519 ((( 520 - NB-IoTNetworksignalStrength.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). 521 521 ))) 522 522 523 523 ((( 524 -** Ex1:0x1d = 29**481 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. 525 525 ))) 526 526 527 527 ((( 528 - (%style="color:blue"%)**0**(%%)-113dBmor less485 +Generally, the EC value of irrigation water is less than 800uS / cm. 529 529 ))) 530 530 531 531 ((( 532 - (%style="color:blue" %)**1**(%%) -111dBm489 + 533 533 ))) 534 534 535 535 ((( 536 - (%style="color:blue" %)**2...30**(%%) -109dBm... -53dBm493 + 537 537 ))) 538 538 496 +=== 2.4.8 Digital Interrupt === 497 + 539 539 ((( 540 -(% style="color:blue" %)** 31**-51dBmor greater499 +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. 541 541 ))) 542 542 543 543 ((( 544 - (% style="color:blue" %)**99** (%%) Not known or notdetectable503 +The command is: 545 545 ))) 546 546 506 +((( 507 +(% 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]])**.** 508 +))) 547 547 548 548 549 -=== 2.3.6 Temperature & Humidity === 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 +))) 550 550 551 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 552 552 553 -[[image:image-20220709161741-3.png]] 516 +((( 517 +Example: 518 +))) 554 554 520 +((( 521 +0x(00): Normal uplink packet. 522 +))) 555 555 556 -Convert the read byte to decimal and divide it by ten. 524 +((( 525 +0x(01): Interrupt Uplink Packet. 526 +))) 557 557 558 558 559 -**Example:** 560 560 561 - Temperature: Read:00ec (H)= 236(D)Value:236 /10=23.6℃530 +=== 2.4.9 +5V Output === 562 562 563 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 532 +((( 533 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 534 +))) 564 564 565 565 537 +((( 538 +The 5V output time can be controlled by AT Command. 539 +))) 566 566 567 -== 2.4 Downlink Payload == 541 +((( 542 +(% style="color:blue" %)**AT+5VT=1000** 543 +))) 568 568 569 -By default, NDDS75 prints the downlink payload to console port. 545 +((( 546 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 547 +))) 570 570 571 -[[image:image-20220709100028-1.png]] 572 572 573 573 551 +== 2.5 Downlink Payload == 552 + 553 +By default, NSE01 prints the downlink payload to console port. 554 + 555 +[[image:image-20220708133731-5.png]] 556 + 557 + 574 574 ((( 575 575 (% style="color:blue" %)**Examples:** 576 576 ))) ... ... @@ -604,7 +604,7 @@ 604 604 ))) 605 605 606 606 ((( 607 -If payload = 0x04FF, it will reset the N DDS75591 +If payload = 0x04FF, it will reset the NSE01 608 608 ))) 609 609 610 610 ... ... @@ -616,19 +616,78 @@ 616 616 617 617 618 618 619 -== 2. 5BatteryAnalysis==603 +== 2.6 LED Indicator == 620 620 621 -=== 2.5.1 Battery Type === 605 +((( 606 +The NSE01 has an internal LED which is to show the status of different state. 622 622 623 623 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 + 624 624 ((( 625 - 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]] 626 626 ))) 627 627 626 +[[image:1657259653666-883.png]] 627 + 628 + 628 628 ((( 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 +((( 629 629 The battery is designed to last for several years depends on the actually use environment and update interval. 630 630 ))) 631 631 674 + 632 632 ((( 633 633 The battery related documents as below: 634 634 ))) ... ... @@ -638,40 +638,61 @@ 638 638 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 639 639 640 640 ((( 641 -[[image:image-2022070 9101450-2.png]]684 +[[image:image-20220708140453-6.png]] 642 642 ))) 643 643 644 644 645 645 646 -=== 2. 5.2 Power consumption Analyze ===689 +=== 2.9.2 Power consumption Analyze === 647 647 648 648 ((( 649 - 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. 650 650 ))) 651 651 695 + 652 652 ((( 653 - 697 +Instruction to use as below: 654 654 ))) 655 655 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 +))) 656 656 657 -=== 2.5.3 Battery Note === 658 658 659 659 ((( 660 - 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 661 661 ))) 662 662 709 +* ((( 710 +Product Model 711 +))) 712 +* ((( 713 +Uplink Interval 714 +))) 715 +* ((( 716 +Working Mode 717 +))) 663 663 719 +((( 720 +And the Life expectation in difference case will be shown on the right. 721 +))) 664 664 665 - ===2.5.4 Replacethe battery ===723 +[[image:image-20220708141352-7.jpeg]] 666 666 667 667 726 + 727 +=== 2.9.3 Battery Note === 728 + 668 668 ((( 669 - 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. 670 670 ))) 671 671 672 672 734 + 735 +=== 2.9.4 Replace the battery === 736 + 673 673 ((( 674 -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). 675 675 ))) 676 676 677 677 ... ... @@ -686,7 +686,7 @@ 686 686 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/]] 687 687 ))) 688 688 689 -[[image:1657 333200519-600.png]]753 +[[image:1657261278785-153.png]] 690 690 691 691 692 692 ... ... @@ -694,7 +694,7 @@ 694 694 695 695 == 4.1 Access AT Commands == 696 696 697 -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/]] 698 698 699 699 700 700 AT+<CMD>? : Help on <CMD> ... ... @@ -782,13 +782,18 @@ 782 782 ))) 783 783 784 784 ((( 785 - 786 - 787 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 849 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update. 788 788 ))) 789 789 790 790 791 791 854 +== 5.2 Can I calibrate NSE01 to different soil types? == 855 + 856 +((( 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]]. 858 +))) 859 + 860 + 792 792 = 6. Trouble Shooting = 793 793 794 794 == 6.1 Connection problem when uploading firmware == ... ... @@ -816,7 +816,7 @@ 816 816 = 7. Order Info = 817 817 818 818 819 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**888 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 820 820 821 821 822 822 (% class="wikigeneratedid" %) ... ... @@ -831,7 +831,7 @@ 831 831 832 832 (% style="color:#037691" %)**Package Includes**: 833 833 834 -* N 95S31BNB-IoTTemperatureandHumiditySensor903 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 835 835 * External antenna x 1 836 836 ))) 837 837 ... ... @@ -840,10 +840,8 @@ 840 840 841 841 (% style="color:#037691" %)**Dimension and weight**: 842 842 843 -* Device Size: 13.0 x 5 x 4.5 cm 844 -* Device Weight: 150g 845 -* Package Size / pcs : 14.0 x 8x 5 cm 846 -* Weight / pcs : 180g 912 +* Size: 195 x 125 x 55 mm 913 +* Weight: 420g 847 847 ))) 848 848 849 849 (((
- 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-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