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, 26 removed)
- 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,55 +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 -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*. 23 +((( 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. 30 +))) 26 26 27 -The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use. 28 - 29 -N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 30 - 31 -N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report). 32 - 33 - 34 -~* make sure you have NB-IoT coverage locally. 35 - 36 36 37 37 ))) 38 38 39 -[[image:165 7348284168-431.png]]35 +[[image:1654503236291-817.png]] 40 40 41 41 38 +[[image:1657327959271-447.png]] 42 42 40 + 41 + 43 43 == 1.2 Features == 44 44 44 + 45 45 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 -* 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 47 47 * AT Commands to change parameters 48 48 * Uplink on periodically 49 49 * Downlink to change configure 50 50 * IP66 Waterproof Enclosure 51 -* Ultra-Low Power consumption 52 -* AT Commands to change parameters 53 53 * Micro SIM card slot for NB-IoT SIM 54 54 * 8500mAh Battery for long term use 55 55 ... ... @@ -73,7 +73,6 @@ 73 73 74 74 (% style="color:#037691" %)**Battery:** 75 75 76 - 77 77 * Li/SOCI2 un-chargeable battery 78 78 * Capacity: 8500mAh 79 79 * Self Discharge: <1% / Year @ 25°C ... ... @@ -80,7 +80,13 @@ 80 80 * Max continuously current: 130mA 81 81 * Max boost current: 2A, 1 second 82 82 84 +(% style="color:#037691" %)**Power Consumption** 83 83 86 +* STOP Mode: 10uA @ 3.3v 87 +* Max transmit power: 350mA@3.3v 88 + 89 + 90 + 84 84 == 1.4 Applications == 85 85 86 86 * Smart Buildings & Home Automation ... ... @@ -94,52 +94,25 @@ 94 94 95 95 96 96 104 + 97 97 == 1.5 Pin Definitions == 98 98 99 -N95S31B use the mother board from NBSN95 which as below. 100 100 101 -[[image: image-20220709144723-1.png]]108 +[[image:1657328609906-564.png]] 102 102 103 103 104 -=== 1.5.1 Jumper JP2 === 105 105 106 - PoweronDevice when putthisjumper.112 += 2. Use NDDS75 to communicate with IoT Server = 107 107 108 - 109 - 110 -=== 1.5.2 BOOT MODE / SW1 === 111 - 112 -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. 113 - 114 -2) Flash: work mode, device starts to work and send out console output for further debug 115 - 116 - 117 - 118 -=== 1.5.3 Reset Button === 119 - 120 -Press to reboot the device. 121 - 122 - 123 - 124 -=== 1.5.4 LED === 125 - 126 -It will flash: 127 - 128 -1. When boot the device in flash mode 129 -1. Send an uplink packet 130 - 131 -= 2. Use N95S31B to communicate with IoT Server = 132 - 133 133 == 2.1 How it works == 134 134 135 - 136 136 ((( 137 -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.117 +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. 138 138 ))) 139 139 140 140 141 141 ((( 142 -The diagram below shows the working flow in default firmware of N 95S31B:122 +The diagram below shows the working flow in default firmware of NDDS75: 143 143 ))) 144 144 145 145 ((( ... ... @@ -146,7 +146,7 @@ 146 146 147 147 ))) 148 148 149 -[[image:16573 50248151-650.png]]129 +[[image:1657328659945-416.png]] 150 150 151 151 ((( 152 152 ... ... @@ -153,45 +153,30 @@ 153 153 ))) 154 154 155 155 156 -== 2.2 Configure the N 95S31B==136 +== 2.2 Configure the NDDS75 == 157 157 158 158 159 -=== 2.2.1 Power On N95S31B === 160 - 161 - 162 -[[image:image-20220709150546-2.png]] 163 - 164 - 165 165 === 2.2.1 Test Requirement === 166 166 141 +((( 142 +To use NDDS75 in your city, make sure meet below requirements: 143 +))) 167 167 168 -To use N95S31B in your city, make sure meet below requirements: 169 - 170 170 * Your local operator has already distributed a NB-IoT Network there. 171 -* The local NB-IoT network used the band that N 95S31Bsupports.146 +* The local NB-IoT network used the band that NSE01 supports. 172 172 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 173 173 174 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 175 - 176 -N95S31B supports different communication protocol such as : 177 - 178 178 ((( 179 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 180 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 181 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 182 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 183 - 184 -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. 185 - 186 - 150 +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 187 187 ))) 188 188 189 -[[image:1657350625843-586.png]] 190 190 154 +[[image:1657328756309-230.png]] 191 191 192 192 193 -=== 2.2.3 Insert SIM card === 194 194 158 +=== 2.2.2 Insert SIM card === 159 + 195 195 ((( 196 196 Insert the NB-IoT Card get from your provider. 197 197 ))) ... ... @@ -201,19 +201,19 @@ 201 201 ))) 202 202 203 203 204 -[[image:16573 51240556-536.png]]169 +[[image:1657328884227-504.png]] 205 205 206 206 207 207 208 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===173 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 209 209 210 210 ((( 211 211 ((( 212 -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.177 +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. 213 213 ))) 214 214 ))) 215 215 216 -[[image: 1657351312545-300.png]]181 +[[image:image-20220709092052-2.png]] 217 217 218 218 **Connection:** 219 219 ... ... @@ -233,110 +233,95 @@ 233 233 * Flow Control: (% style="color:green" %)**None** 234 234 235 235 ((( 236 -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.201 +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. 237 237 ))) 238 238 239 239 [[image:1657329814315-101.png]] 240 240 241 241 ((( 242 -(% 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/]]207 +(% 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/]] 243 243 ))) 244 244 245 245 246 246 247 -=== 2.2. 5Use CoAP protocol to uplink data ===212 +=== 2.2.4 Use CoAP protocol to uplink data === 248 248 249 249 (% 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/]] 250 250 251 251 252 -((( 253 253 **Use below commands:** 254 -))) 255 255 256 -* ((( 257 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 258 -))) 259 -* ((( 260 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 261 -))) 262 -* ((( 263 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 264 -))) 219 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 220 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 221 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 265 265 266 -((( 267 - 268 - 269 269 For parameter description, please refer to AT command set 270 -))) 271 271 272 -[[image:1657352 146020-183.png]]225 +[[image:1657330452568-615.png]] 273 273 274 274 275 -((( 276 276 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. 277 -))) 278 278 279 -[[image:16573 52185396-303.png]]230 +[[image:1657330472797-498.png]] 280 280 281 281 282 282 283 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===234 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 284 284 285 285 286 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) 237 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 287 287 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 288 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 239 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 289 289 290 -[[image:1657352391268-297.png]] 291 291 242 +[[image:1657330501006-241.png]] 292 292 293 -[[image:1657352403317-397.png]] 294 294 245 +[[image:1657330533775-472.png]] 295 295 296 296 297 -=== 2.2.7 Use MQTT protocol to uplink data === 298 298 299 - N95S31BsupportsonlyplainMQTTnow itdoesn'tsupport TLS andother related encryption.249 +=== 2.2.6 Use MQTT protocol to uplink data === 300 300 301 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 302 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 303 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 304 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 305 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 306 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 307 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 251 +This feature is supported since firmware version v110 308 308 309 -[[image:1657352634421-276.png]] 310 310 254 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 255 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 256 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 257 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 258 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 259 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB **(%%)~/~/Set the sending topic of MQTT 260 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB **(%%) ~/~/Set the subscription topic of MQTT 311 311 312 -[[image:1657 352645687-385.png]]262 +[[image:1657249978444-674.png]] 313 313 314 -((( 315 -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. 316 -))) 317 317 265 +[[image:1657249990869-686.png]] 318 318 267 + 319 319 ((( 320 -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.269 +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. 321 321 ))) 322 322 323 323 324 324 325 -=== 2.2. 8Use TCP protocol to uplink data ===274 +=== 2.2.7 Use TCP protocol to uplink data === 326 326 327 327 This feature is supported since firmware version v110 328 328 278 + 329 329 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 330 330 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 331 331 332 -[[image:1657 352898400-901.png]]282 +[[image:1657250217799-140.png]] 333 333 334 334 335 -[[image:1657 352914475-252.png]]285 +[[image:1657250255956-604.png]] 336 336 337 337 338 338 339 -=== 2.2. 9Change Update Interval ===289 +=== 2.2.8 Change Update Interval === 340 340 341 341 User can use below command to change the (% style="color:green" %)**uplink interval**. 342 342 ... ... @@ -343,199 +343,262 @@ 343 343 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 344 344 345 345 ((( 346 - 296 +(% style="color:red" %)**NOTE:** 347 347 ))) 348 348 299 +((( 300 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 301 +))) 349 349 350 350 304 + 351 351 == 2.3 Uplink Payload == 352 352 307 +In this mode, uplink payload includes in total 18 bytes 353 353 354 -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. 309 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 310 +|=(% style="width: 60px;" %)((( 311 +**Size(bytes)** 312 +)))|=(% 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** 313 +|(% 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"]] 355 355 315 +((( 316 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data. 317 +))) 356 356 357 -For example: 358 358 359 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distancemode which target tomeasuredistance via Ultrasonic Sensor.320 +[[image:image-20220708111918-4.png]] 360 360 361 361 362 -The uplink payloadsare composedinASCIIString.Forxample:323 +The payload is ASCII string, representative same HEX: 363 363 364 -0 a cd00d0ac000ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:325 +0x72403155615900640c7817075e0a8c02f900 where: 365 365 366 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 327 +* Device ID: 0x 724031556159 = 724031556159 328 +* Version: 0x0064=100=1.0.0 367 367 330 +* BAT: 0x0c78 = 3192 mV = 3.192V 331 +* Singal: 0x17 = 23 332 +* Soil Moisture: 0x075e= 1886 = 18.86 % 333 +* Soil Temperature:0x0a8c =2700=27 °C 334 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm 335 +* Interrupt: 0x00 = 0 368 368 369 - (%style="color:red"%)**NOTE:**337 +== 2.4 Payload Explanation and Sensor Interface == 370 370 371 -(% style="color:red" %) 372 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 373 -1. By default, the device will send an uplink message every 1 hour. 374 374 375 -=== 2. 3.1Payload Analyze ===340 +=== 2.4.1 Device ID === 376 376 377 -N95S31B uplink payload includes in total 21 bytes 342 +((( 343 +By default, the Device ID equal to the last 6 bytes of IMEI. 344 +))) 378 378 346 +((( 347 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 348 +))) 379 379 380 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 381 -|=(% style="width: 60px;" %)((( 382 -**Size(bytes)** 383 -)))|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 384 -|(% 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" %)((( 385 -Reserve/ Same as NBSN95 CFGMOD=1 350 +((( 351 +**Example:** 352 +))) 386 386 387 -No function here. 388 -)))|(% style="width:77px" %)((( 389 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 390 - 391 -By SHT31 392 -)))|(% style="width:80px" %)((( 393 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 394 - 395 -By SHT31 354 +((( 355 +AT+DEUI=A84041F15612 396 396 ))) 397 397 398 398 ((( 399 -((( 400 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 359 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 401 401 ))) 402 -))) 403 403 404 404 405 -[[image:1657354294009-643.png]] 406 406 364 +=== 2.4.2 Version Info === 407 407 408 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 366 +((( 367 +Specify the software version: 0x64=100, means firmware version 1.00. 368 +))) 409 409 410 -* Device ID: 0x724031607457 = 724031607457 411 -* Version: 0x006e=110=1.1.0 370 +((( 371 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0. 372 +))) 412 412 413 -* BAT: 0x0ccd = 3277 mV = 3.277V 414 -* Signal: 0x1b = 27 415 -* Model: 0x01 = 1 416 -* 0x00dc000ccc= reserve, ignore in N95S31B 417 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 418 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 419 419 375 + 376 +=== 2.4.3 Battery Info === 377 + 420 420 ((( 421 - 379 +Check the battery voltage for LSE01. 422 422 ))) 423 423 424 424 ((( 425 - 383 +Ex1: 0x0B45 = 2885mV 426 426 ))) 427 427 386 +((( 387 +Ex2: 0x0B49 = 2889mV 388 +))) 428 428 429 -=== 2.3.2 Device ID === 430 430 391 + 392 +=== 2.4.4 Signal Strength === 393 + 431 431 ((( 432 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.395 +NB-IoT Network signal Strength. 433 433 ))) 434 434 435 435 ((( 436 - User can use (% style="color:blue" %)**AT+DEUI**(%%)tosetDevice ID399 +**Ex1: 0x1d = 29** 437 437 ))) 438 438 439 439 ((( 440 - **Example:**403 +(% style="color:blue" %)**0**(%%) -113dBm or less 441 441 ))) 442 442 443 443 ((( 444 - AT+DEUI=A84041F15612407 +(% style="color:blue" %)**1**(%%) -111dBm 445 445 ))) 446 446 447 447 ((( 448 - TheDevice ID isstored in a none-erase area, Upgrade the firmwareorrun**AT+FDR**won't erase Device ID.411 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 449 449 ))) 450 450 414 +((( 415 +(% style="color:blue" %)**31** (%%) -51dBm or greater 416 +))) 451 451 418 +((( 419 +(% style="color:blue" %)**99** (%%) Not known or not detectable 420 +))) 452 452 453 -=== 2.3.3 Version Info === 454 454 455 455 456 - Thesebytesincludethe hardware and softwareversion.424 +=== 2.4.5 Soil Moisture === 457 457 458 -Higher byte: Specify hardware version: always 0x00 for N95S31B 426 +((( 427 +((( 428 +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. 429 +))) 430 +))) 459 459 460 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 432 +((( 433 +((( 434 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is 435 +))) 436 +))) 461 461 462 - 463 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 464 - 465 465 ((( 466 466 467 467 ))) 468 468 442 +((( 443 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.** 444 +))) 469 469 470 -=== 2.3.4 Battery Info === 471 471 447 + 448 +=== 2.4.6 Soil Temperature === 449 + 472 472 ((( 473 - Ex1:0x0B45=2885mV451 +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 474 474 ))) 475 475 476 476 ((( 477 -Ex 2: 0x0B49 = 2889mV455 +**Example**: 478 478 ))) 479 479 458 +((( 459 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C 460 +))) 480 480 462 +((( 463 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C 464 +))) 481 481 482 -=== 2.3.5 Signal Strength === 483 483 467 + 468 +=== 2.4.7 Soil Conductivity (EC) === 469 + 484 484 ((( 485 - NB-IoTNetworksignalStrength.471 +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). 486 486 ))) 487 487 488 488 ((( 489 -** Ex1:0x1d = 29**475 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. 490 490 ))) 491 491 492 492 ((( 493 - (%style="color:blue"%)**0**(%%)-113dBmor less479 +Generally, the EC value of irrigation water is less than 800uS / cm. 494 494 ))) 495 495 496 496 ((( 497 - (%style="color:blue" %)**1**(%%) -111dBm483 + 498 498 ))) 499 499 500 500 ((( 501 - (%style="color:blue" %)**2...30**(%%) -109dBm... -53dBm487 + 502 502 ))) 503 503 490 +=== 2.4.8 Digital Interrupt === 491 + 504 504 ((( 505 -(% style="color:blue" %)** 31**-51dBmor greater493 +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. 506 506 ))) 507 507 508 508 ((( 509 - (% style="color:blue" %)**99** (%%) Not known or notdetectable497 +The command is: 510 510 ))) 511 511 500 +((( 501 +(% 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]])**.** 502 +))) 512 512 513 513 514 -=== 2.3.6 Temperature & Humidity === 505 +((( 506 +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. 507 +))) 515 515 516 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 517 517 518 -[[image:image-20220709161741-3.png]] 510 +((( 511 +Example: 512 +))) 519 519 514 +((( 515 +0x(00): Normal uplink packet. 516 +))) 520 520 521 -Convert the read byte to decimal and divide it by ten. 518 +((( 519 +0x(01): Interrupt Uplink Packet. 520 +))) 522 522 523 523 524 -**Example:** 525 525 526 - Temperature: Read:00ec (H)= 236(D)Value:236 /10=23.6℃524 +=== 2.4.9 +5V Output === 527 527 528 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 526 +((( 527 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 528 +))) 529 529 530 530 531 +((( 532 +The 5V output time can be controlled by AT Command. 533 +))) 531 531 532 -== 2.4 Downlink Payload == 535 +((( 536 +(% style="color:blue" %)**AT+5VT=1000** 537 +))) 533 533 534 -By default, NDDS75 prints the downlink payload to console port. 539 +((( 540 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 541 +))) 535 535 536 -[[image:image-20220709100028-1.png]] 537 537 538 538 545 +== 2.5 Downlink Payload == 546 + 547 +By default, NSE01 prints the downlink payload to console port. 548 + 549 +[[image:image-20220708133731-5.png]] 550 + 551 + 539 539 ((( 540 540 (% style="color:blue" %)**Examples:** 541 541 ))) ... ... @@ -569,7 +569,7 @@ 569 569 ))) 570 570 571 571 ((( 572 -If payload = 0x04FF, it will reset the N DDS75585 +If payload = 0x04FF, it will reset the NSE01 573 573 ))) 574 574 575 575 ... ... @@ -581,19 +581,78 @@ 581 581 582 582 583 583 584 -== 2. 5BatteryAnalysis==597 +== 2.6 LED Indicator == 585 585 586 -=== 2.5.1 Battery Type === 599 +((( 600 +The NSE01 has an internal LED which is to show the status of different state. 587 587 588 588 603 +* 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) 604 +* Then the LED will be on for 1 second means device is boot normally. 605 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds. 606 +* For each uplink probe, LED will be on for 500ms. 607 +))) 608 + 609 + 610 + 611 + 612 +== 2.7 Installation in Soil == 613 + 614 +__**Measurement the soil surface**__ 615 + 589 589 ((( 590 - TheN95S31B batteryisa combination ofan 8500mAhLi/SOCI2BatteryandaSuperCapacitor.Thebatteryisnone-rechargeablebatterytypewithaowdischargeate(<2%peryear).Thistype ofbatteryiscommonlyusedinIoT devicessuchaswatermeter.617 +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]] 591 591 ))) 592 592 620 +[[image:1657259653666-883.png]] 621 + 622 + 593 593 ((( 624 + 625 + 626 +((( 627 +Dig a hole with diameter > 20CM. 628 +))) 629 + 630 +((( 631 +Horizontal insert the probe to the soil and fill the hole for long term measurement. 632 +))) 633 +))) 634 + 635 +[[image:1654506665940-119.png]] 636 + 637 +((( 638 + 639 +))) 640 + 641 + 642 +== 2.8 Firmware Change Log == 643 + 644 + 645 +Download URL & Firmware Change log 646 + 647 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]] 648 + 649 + 650 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 651 + 652 + 653 + 654 +== 2.9 Battery Analysis == 655 + 656 +=== 2.9.1 Battery Type === 657 + 658 + 659 +((( 660 +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. 661 +))) 662 + 663 + 664 +((( 594 594 The battery is designed to last for several years depends on the actually use environment and update interval. 595 595 ))) 596 596 668 + 597 597 ((( 598 598 The battery related documents as below: 599 599 ))) ... ... @@ -603,40 +603,61 @@ 603 603 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 604 604 605 605 ((( 606 -[[image:image-2022070 9101450-2.png]]678 +[[image:image-20220708140453-6.png]] 607 607 ))) 608 608 609 609 610 610 611 -=== 2. 5.2 Power consumption Analyze ===683 +=== 2.9.2 Power consumption Analyze === 612 612 613 613 ((( 614 - 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.686 +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. 615 615 ))) 616 616 689 + 617 617 ((( 618 - 691 +Instruction to use as below: 619 619 ))) 620 620 694 +((( 695 +(% 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/]] 696 +))) 621 621 622 -=== 2.5.3 Battery Note === 623 623 624 624 ((( 625 - 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.700 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 626 626 ))) 627 627 703 +* ((( 704 +Product Model 705 +))) 706 +* ((( 707 +Uplink Interval 708 +))) 709 +* ((( 710 +Working Mode 711 +))) 628 628 713 +((( 714 +And the Life expectation in difference case will be shown on the right. 715 +))) 629 629 630 - ===2.5.4 Replacethe battery ===717 +[[image:image-20220708141352-7.jpeg]] 631 631 632 632 720 + 721 +=== 2.9.3 Battery Note === 722 + 633 633 ((( 634 - 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.724 +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. 635 635 ))) 636 636 637 637 728 + 729 +=== 2.9.4 Replace the battery === 730 + 638 638 ((( 639 -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).732 +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). 640 640 ))) 641 641 642 642 ... ... @@ -651,7 +651,7 @@ 651 651 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/]] 652 652 ))) 653 653 654 -[[image:1657 333200519-600.png]]747 +[[image:1657261278785-153.png]] 655 655 656 656 657 657 ... ... @@ -659,7 +659,7 @@ 659 659 660 660 == 4.1 Access AT Commands == 661 661 662 -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/]]755 +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/]] 663 663 664 664 665 665 AT+<CMD>? : Help on <CMD> ... ... @@ -747,13 +747,18 @@ 747 747 ))) 748 748 749 749 ((( 750 - 751 - 752 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 843 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update. 753 753 ))) 754 754 755 755 756 756 848 +== 5.2 Can I calibrate NSE01 to different soil types? == 849 + 850 +((( 851 +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]]. 852 +))) 853 + 854 + 757 757 = 6. Trouble Shooting = 758 758 759 759 == 6.1 Connection problem when uploading firmware == ... ... @@ -781,7 +781,7 @@ 781 781 = 7. Order Info = 782 782 783 783 784 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**882 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 785 785 786 786 787 787 (% class="wikigeneratedid" %) ... ... @@ -796,7 +796,7 @@ 796 796 797 797 (% style="color:#037691" %)**Package Includes**: 798 798 799 -* N 95S31BNB-IoTTemperatureandHumiditySensor897 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 800 800 * External antenna x 1 801 801 ))) 802 802 ... ... @@ -805,10 +805,8 @@ 805 805 806 806 (% style="color:#037691" %)**Dimension and weight**: 807 807 808 -* Device Size: 13.0 x 5 x 4.5 cm 809 -* Device Weight: 150g 810 -* Package Size / pcs : 14.0 x 8x 5 cm 811 -* Weight / pcs : 180g 906 +* Size: 195 x 125 x 55 mm 907 +* Weight: 420g 812 812 ))) 813 813 814 814 (((
- 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