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, 23 removed)
- 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-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 ... ... @@ -87,7 +87,6 @@ 87 87 * - B20 @H-FDD: 800MHz 88 88 * - B28 @H-FDD: 700MHz 89 89 90 - 91 91 (% style="color:#037691" %)**Battery:** 92 92 93 93 * Li/SOCI2 un-chargeable battery ... ... @@ -96,9 +96,14 @@ 96 96 * Max continuously current: 130mA 97 97 * Max boost current: 2A, 1 second 98 98 85 +(% style="color:#037691" %)**Power Consumption** 99 99 87 +* STOP Mode: 10uA @ 3.3v 88 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 100 100 101 101 91 + 92 + 102 102 == 1.4 Applications == 103 103 104 104 * Smart Buildings & Home Automation ... ... @@ -112,59 +112,25 @@ 112 112 113 113 114 114 106 + 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]]110 +[[image:1657328609906-564.png]] 120 120 121 121 122 -=== 1.5.1 Jumper JP2 === 123 123 124 - PoweronDevice when putthisjumper.114 += 2. Use NDDS75 to communicate with IoT Server = 125 125 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 - 154 - 155 - 156 -= 2. Use N95S31B to communicate with IoT Server = 157 - 158 158 == 2.1 How it works == 159 159 160 - 161 161 ((( 162 -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.119 +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. 163 163 ))) 164 164 165 165 166 166 ((( 167 -The diagram below shows the working flow in default firmware of N 95S31B:124 +The diagram below shows the working flow in default firmware of NDDS75: 168 168 ))) 169 169 170 170 ((( ... ... @@ -171,7 +171,7 @@ 171 171 172 172 ))) 173 173 174 -[[image:16573 50248151-650.png]]131 +[[image:1657328659945-416.png]] 175 175 176 176 ((( 177 177 ... ... @@ -178,67 +178,30 @@ 178 178 ))) 179 179 180 180 181 -== 2.2 Configure the N 95S31B==138 +== 2.2 Configure the NDDS75 == 182 182 183 183 184 -=== 2.2.1 Power On N95S31B === 185 - 186 - 187 -[[image:image-20220709150546-2.png]] 188 - 189 - 190 190 === 2.2.1 Test Requirement === 191 191 192 - 193 193 ((( 194 -To use N 95S31Bin your city, make sure meet below requirements:144 +To use NDDS75 in your city, make sure meet below requirements: 195 195 ))) 196 196 197 -* ((( 198 -Your local operator has already distributed a NB-IoT Network there. 199 -))) 200 -* ((( 201 -The local NB-IoT network used the band that N95S31B supports. 202 -))) 203 -* ((( 204 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 205 -))) 147 +* Your local operator has already distributed a NB-IoT Network there. 148 +* The local NB-IoT network used the band that NSE01 supports. 149 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 206 206 207 207 ((( 208 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 152 +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 -((( 212 -N95S31B supports different communication protocol such as : 213 -))) 214 214 215 -((( 216 -* ((( 217 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 218 -))) 219 -* ((( 220 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 221 -))) 222 -* ((( 223 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 224 -))) 225 -* ((( 226 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 227 -))) 156 +[[image:1657328756309-230.png]] 228 228 229 -((( 230 -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. 231 -))) 232 232 233 - 234 -))) 235 235 236 - [[image:1657350625843-586.png]]160 +=== 2.2.2 Insert SIM card === 237 237 238 - 239 - 240 -=== 2.2.3 Insert SIM card === 241 - 242 242 ((( 243 243 Insert the NB-IoT Card get from your provider. 244 244 ))) ... ... @@ -248,19 +248,19 @@ 248 248 ))) 249 249 250 250 251 -[[image:16573 51240556-536.png]]171 +[[image:1657328884227-504.png]] 252 252 253 253 254 254 255 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===175 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 256 256 257 257 ((( 258 258 ((( 259 -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.179 +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. 260 260 ))) 261 261 ))) 262 262 263 -[[image: 1657351312545-300.png]]183 +[[image:image-20220709092052-2.png]] 264 264 265 265 **Connection:** 266 266 ... ... @@ -280,110 +280,90 @@ 280 280 * Flow Control: (% style="color:green" %)**None** 281 281 282 282 ((( 283 -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.203 +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. 284 284 ))) 285 285 286 286 [[image:1657329814315-101.png]] 287 287 288 288 ((( 289 -(% 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/]]209 +(% 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/]] 290 290 ))) 291 291 292 292 293 293 294 -=== 2.2. 5Use CoAP protocol to uplink data ===214 +=== 2.2.4 Use CoAP protocol to uplink data === 295 295 296 296 (% 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/]] 297 297 298 298 299 -((( 300 300 **Use below commands:** 301 -))) 302 302 303 -* ((( 304 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 305 -))) 306 -* ((( 307 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 308 -))) 309 -* ((( 310 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 311 -))) 221 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 222 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 223 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 312 312 313 -((( 314 - 315 - 316 316 For parameter description, please refer to AT command set 317 -))) 318 318 319 -[[image:1657352 146020-183.png]]227 +[[image:1657330452568-615.png]] 320 320 321 321 322 -((( 323 323 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. 324 -))) 325 325 326 -[[image:16573 52185396-303.png]]232 +[[image:1657330472797-498.png]] 327 327 328 328 329 329 330 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===236 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 331 331 332 332 333 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) 239 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 334 334 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 335 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 241 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 336 336 337 -[[image:16573 52391268-297.png]]243 +[[image:1657330501006-241.png]] 338 338 339 339 340 -[[image:16573 52403317-397.png]]246 +[[image:1657330533775-472.png]] 341 341 342 342 343 343 344 -=== 2.2. 7Use MQTT protocol to uplink data ===250 +=== 2.2.6 Use MQTT protocol to uplink data === 345 345 346 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 347 347 348 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) 349 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) 350 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** 351 -* (% style="color:blue" %)**AT+UNAME=UNAME 352 -* (% style="color:blue" %)**AT+PWD=PWD 353 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527354 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)253 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 254 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 255 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 256 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 257 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 258 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 259 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 355 355 356 -[[image:1657 352634421-276.png]]261 +[[image:1657249978444-674.png]] 357 357 358 358 359 -[[image:16573 52645687-385.png]]264 +[[image:1657330723006-866.png]] 360 360 361 -((( 362 -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. 363 -))) 364 364 365 - 366 366 ((( 367 -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.268 +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. 368 368 ))) 369 369 370 370 371 371 372 -=== 2.2. 8Use TCP protocol to uplink data ===273 +=== 2.2.7 Use TCP protocol to uplink data === 373 373 374 -This feature is supported since firmware version v110 375 375 376 376 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 377 377 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 378 378 379 -[[image: 1657352898400-901.png]]279 +[[image:image-20220709093918-1.png]] 380 380 381 381 382 -[[image: 1657352914475-252.png]]282 +[[image:image-20220709093918-2.png]] 383 383 384 384 385 385 386 -=== 2.2. 9Change Update Interval ===286 +=== 2.2.8 Change Update Interval === 387 387 388 388 User can use below command to change the (% style="color:green" %)**uplink interval**. 389 389 ... ... @@ -390,230 +390,232 @@ 390 390 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 391 391 392 392 ((( 393 - 293 +(% style="color:red" %)**NOTE:** 394 394 ))) 395 395 296 +((( 297 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 298 +))) 396 396 397 397 301 + 398 398 == 2.3 Uplink Payload == 399 399 304 +In this mode, uplink payload includes in total 14 bytes 400 400 401 -((( 402 -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. 403 -))) 404 404 307 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 308 +|=(% style="width: 60px;" %)((( 309 +**Size(bytes)** 310 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1** 311 +|(% 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" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]] 405 405 406 406 ((( 407 - For example:314 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 408 408 ))) 409 409 410 -((( 411 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 412 -))) 413 413 318 +[[image:1657331036973-987.png]] 414 414 415 415 ((( 416 -The uplink payloadsare composedinASCIIString.Forxample:321 +The payload is ASCII string, representative same HEX: 417 417 ))) 418 418 419 419 ((( 420 -0 a cd00ed0acc0ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:325 +0x72403155615900640c6c19029200 where: 421 421 ))) 422 422 423 -((( 424 - 0x 0acd 00ed0acc0000ef 02d21d Total12 bytes328 +* ((( 329 +Device ID: 0x724031556159 = 724031556159 425 425 ))) 426 - 427 - 428 -((( 429 -(% style="color:red" %)**NOTE:** 331 +* ((( 332 +Version: 0x0064=100=1.0.0 430 430 ))) 431 431 432 -(% style="color:red" %) 433 -1. ((( 434 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 335 +* ((( 336 +BAT: 0x0c6c = 3180 mV = 3.180V 435 435 ))) 436 - 1.(((437 - By default, the device will sendan uplinkmessage every1hour.338 +* ((( 339 +Signal: 0x19 = 25 438 438 ))) 341 +* ((( 342 +Distance: 0x0292= 658 mm 343 +))) 344 +* ((( 345 +Interrupt: 0x00 = 0 346 +))) 439 439 440 440 441 -=== 2.3.1 Payload Analyze === 442 442 443 - N95S31Buplinkpayload includesinotal 21 bytes350 +== 2.4 Payload Explanation and Sensor Interface == 444 444 445 445 446 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 447 -|=(% style="width: 60px;" %)((( 448 -**Size(bytes)** 449 -)))|=(% 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** 450 -|(% 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" %)((( 353 +=== 2.4.1 Device ID === 354 + 451 451 ((( 452 - Reserve/Same asNBSN95CFGMOD=1356 +By default, the Device ID equal to the last 6 bytes of IMEI. 453 453 ))) 454 454 455 455 ((( 456 - Nofunctionhere.360 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 457 457 ))) 458 - )))|(% style="width:77px" %)(((362 + 459 459 ((( 460 - [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]364 +**Example:** 461 461 ))) 462 462 463 463 ((( 464 - By SHT31368 +AT+DEUI=A84041F15612 465 465 ))) 466 - )))|(% style="width:80px" %)(((370 + 467 467 ((( 468 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]372 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 469 469 ))) 470 470 375 + 376 + 377 +=== 2.4.2 Version Info === 378 + 471 471 ((( 472 - BySHT31380 +Specify the software version: 0x64=100, means firmware version 1.00. 473 473 ))) 474 -))) 475 475 476 476 ((( 477 -((( 478 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 384 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 479 479 ))) 480 -))) 481 481 482 482 483 -[[image:1657354294009-643.png]] 484 484 389 +=== 2.4.3 Battery Info === 485 485 486 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 391 +((( 392 +Check the battery voltage for LSE01. 393 +))) 487 487 488 -* Device ID: 0x724031607457 = 724031607457 489 -* Version: 0x006e=110=1.1.0 490 - 491 -* BAT: 0x0ccd = 3277 mV = 3.277V 492 -* Signal: 0x1b = 27 493 -* Model: 0x01 = 1 494 -* 0x00dc000ccc= reserve, ignore in N95S31B 495 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 496 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 497 - 498 498 ((( 499 - 396 +Ex1: 0x0B45 = 2885mV 500 500 ))) 501 501 502 502 ((( 503 - 400 +Ex2: 0x0B49 = 2889mV 504 504 ))) 505 505 506 506 507 -=== 2.3.2 Device ID === 508 508 405 +=== 2.4.4 Signal Strength === 406 + 509 509 ((( 510 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.408 +NB-IoT Network signal Strength. 511 511 ))) 512 512 513 513 ((( 514 - User can use (% style="color:blue" %)**AT+DEUI**(%%)tosetDevice ID412 +**Ex1: 0x1d = 29** 515 515 ))) 516 516 517 517 ((( 518 - **Example:**416 +(% style="color:blue" %)**0**(%%) -113dBm or less 519 519 ))) 520 520 521 521 ((( 522 - AT+DEUI=A84041F15612420 +(% style="color:blue" %)**1**(%%) -111dBm 523 523 ))) 524 524 525 525 ((( 526 - TheDevice ID isstored in a none-erase area, Upgrade the firmwareorrun**AT+FDR**won't erase Device ID.424 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 527 527 ))) 528 528 427 +((( 428 +(% style="color:blue" %)**31** (%%) -51dBm or greater 429 +))) 529 529 431 +((( 432 +(% style="color:blue" %)**99** (%%) Not known or not detectable 433 +))) 530 530 531 -=== 2.3.3 Version Info === 532 532 533 533 534 - Thesebytesincludethe hardware and softwareversion.437 +=== 2.4.5 Soil Moisture === 535 535 536 - Higherbyte:Specifyhardwareversion: always0x00forN95S31B439 +Get the distance. Flat object range 280mm - 7500mm. 537 537 538 - Lowerbyte: Specifythesoftwareversion:0x6E=110,meansfirmwareversion110441 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 539 539 540 - 541 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 542 - 543 543 ((( 544 - 444 +((( 445 +(% style="color:#4f81bd" %)** 0B05(H) = 2821(D) = 2821mm.** 545 545 ))) 447 +))) 546 546 547 - 548 -=== 2.3.4 Battery Info === 549 - 550 550 ((( 551 - Ex1:0x0B45 = 2885mV450 + 552 552 ))) 553 553 554 554 ((( 555 - Ex2:0x0B49 = 2889mV454 + 556 556 ))) 557 557 457 +=== 2.4.6 Digital Interrupt === 558 558 559 - 560 -=== 2.3.5 Signal Strength === 561 - 562 562 ((( 563 - NB-IoTNetworksignalStrength.460 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server. 564 564 ))) 565 565 566 566 ((( 567 - **Ex1:0x1d= 29**464 +The command is: 568 568 ))) 569 569 570 570 ((( 571 -(% style="color:blue" %)** 0**(%%)-113dBmor less468 +(% 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]])**.** 572 572 ))) 573 573 471 + 574 574 ((( 575 - (%style="color:blue"%)**1**(%%)-111dBm473 +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. 576 576 ))) 577 577 476 + 578 578 ((( 579 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm478 +Example: 580 580 ))) 581 581 582 582 ((( 583 -( %style="color:blue"%)**31** (%%) -51dBm or greater482 +0x(00): Normal uplink packet. 584 584 ))) 585 585 586 586 ((( 587 -( %style="color:blue" %)**99** (%%) Notknownor not detectable486 +0x(01): Interrupt Uplink Packet. 588 588 ))) 589 589 590 590 591 591 592 -=== 2. 3.6Temperature& Humidity===491 +=== 2.4.7 +5V Output === 593 593 594 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 493 +((( 494 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 495 +))) 595 595 596 -[[image:image-20220709161741-3.png]] 597 597 498 +((( 499 +The 5V output time can be controlled by AT Command. 500 +))) 598 598 599 -Convert the read byte to decimal and divide it by ten. 502 +((( 503 +(% style="color:blue" %)**AT+5VT=1000** 504 +))) 600 600 506 +((( 507 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 508 +))) 601 601 602 -**Example:** 603 603 604 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 605 605 606 - Humidity:Read:0295(H)=661(D)Value:661 / 10=66.1, So66.1%512 +== 2.5 Downlink Payload == 607 607 514 +By default, NSE01 prints the downlink payload to console port. 608 608 516 +[[image:image-20220708133731-5.png]] 609 609 610 -== 2.4 Downlink Payload == 611 611 612 -By default, NDDS75 prints the downlink payload to console port. 613 - 614 -[[image:image-20220709100028-1.png]] 615 - 616 - 617 617 ((( 618 618 (% style="color:blue" %)**Examples:** 619 619 ))) ... ... @@ -647,7 +647,7 @@ 647 647 ))) 648 648 649 649 ((( 650 -If payload = 0x04FF, it will reset the N DDS75552 +If payload = 0x04FF, it will reset the NSE01 651 651 ))) 652 652 653 653 ... ... @@ -659,19 +659,78 @@ 659 659 660 660 661 661 662 -== 2. 5BatteryAnalysis==564 +== 2.6 LED Indicator == 663 663 664 -=== 2.5.1 Battery Type === 566 +((( 567 +The NSE01 has an internal LED which is to show the status of different state. 665 665 666 666 570 +* 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) 571 +* Then the LED will be on for 1 second means device is boot normally. 572 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds. 573 +* For each uplink probe, LED will be on for 500ms. 574 +))) 575 + 576 + 577 + 578 + 579 +== 2.7 Installation in Soil == 580 + 581 +__**Measurement the soil surface**__ 582 + 667 667 ((( 668 - TheN95S31B batteryisa combination ofan 8500mAhLi/SOCI2BatteryandaSuperCapacitor.Thebatteryisnone-rechargeablebatterytypewithaowdischargeate(<2%peryear).Thistype ofbatteryiscommonlyusedinIoT devicessuchaswatermeter.584 +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]] 669 669 ))) 670 670 587 +[[image:1657259653666-883.png]] 588 + 589 + 671 671 ((( 591 + 592 + 593 +((( 594 +Dig a hole with diameter > 20CM. 595 +))) 596 + 597 +((( 598 +Horizontal insert the probe to the soil and fill the hole for long term measurement. 599 +))) 600 +))) 601 + 602 +[[image:1654506665940-119.png]] 603 + 604 +((( 605 + 606 +))) 607 + 608 + 609 +== 2.8 Firmware Change Log == 610 + 611 + 612 +Download URL & Firmware Change log 613 + 614 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]] 615 + 616 + 617 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 618 + 619 + 620 + 621 +== 2.9 Battery Analysis == 622 + 623 +=== 2.9.1 Battery Type === 624 + 625 + 626 +((( 627 +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. 628 +))) 629 + 630 + 631 +((( 672 672 The battery is designed to last for several years depends on the actually use environment and update interval. 673 673 ))) 674 674 635 + 675 675 ((( 676 676 The battery related documents as below: 677 677 ))) ... ... @@ -681,40 +681,61 @@ 681 681 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 682 682 683 683 ((( 684 -[[image:image-2022070 9101450-2.png]]645 +[[image:image-20220708140453-6.png]] 685 685 ))) 686 686 687 687 688 688 689 -=== 2. 5.2 Power consumption Analyze ===650 +=== 2.9.2 Power consumption Analyze === 690 690 691 691 ((( 692 - 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.653 +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. 693 693 ))) 694 694 656 + 695 695 ((( 696 - 658 +Instruction to use as below: 697 697 ))) 698 698 661 +((( 662 +(% 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/]] 663 +))) 699 699 700 -=== 2.5.3 Battery Note === 701 701 702 702 ((( 703 - 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.667 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 704 704 ))) 705 705 670 +* ((( 671 +Product Model 672 +))) 673 +* ((( 674 +Uplink Interval 675 +))) 676 +* ((( 677 +Working Mode 678 +))) 706 706 680 +((( 681 +And the Life expectation in difference case will be shown on the right. 682 +))) 707 707 708 - ===2.5.4 Replacethe battery ===684 +[[image:image-20220708141352-7.jpeg]] 709 709 710 710 687 + 688 +=== 2.9.3 Battery Note === 689 + 711 711 ((( 712 - 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.691 +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. 713 713 ))) 714 714 715 715 695 + 696 +=== 2.9.4 Replace the battery === 697 + 716 716 ((( 717 -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).699 +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). 718 718 ))) 719 719 720 720 ... ... @@ -729,7 +729,7 @@ 729 729 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/]] 730 730 ))) 731 731 732 -[[image:1657 333200519-600.png]]714 +[[image:1657261278785-153.png]] 733 733 734 734 735 735 ... ... @@ -737,7 +737,7 @@ 737 737 738 738 == 4.1 Access AT Commands == 739 739 740 -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/]]722 +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/]] 741 741 742 742 743 743 AT+<CMD>? : Help on <CMD> ... ... @@ -825,13 +825,18 @@ 825 825 ))) 826 826 827 827 ((( 828 - 829 - 830 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 810 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update. 831 831 ))) 832 832 833 833 834 834 815 +== 5.2 Can I calibrate NSE01 to different soil types? == 816 + 817 +((( 818 +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]]. 819 +))) 820 + 821 + 835 835 = 6. Trouble Shooting = 836 836 837 837 == 6.1 Connection problem when uploading firmware == ... ... @@ -859,7 +859,7 @@ 859 859 = 7. Order Info = 860 860 861 861 862 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**849 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 863 863 864 864 865 865 (% class="wikigeneratedid" %) ... ... @@ -874,7 +874,7 @@ 874 874 875 875 (% style="color:#037691" %)**Package Includes**: 876 876 877 -* N 95S31BNB-IoTTemperatureandHumiditySensor864 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 878 878 * External antenna x 1 879 879 ))) 880 880 ... ... @@ -883,10 +883,8 @@ 883 883 884 884 (% style="color:#037691" %)**Dimension and weight**: 885 885 886 -* Device Size: 13.0 x 5 x 4.5 cm 887 -* Device Weight: 150g 888 -* Package Size / pcs : 14.0 x 8x 5 cm 889 -* Weight / pcs : 180g 873 +* Size: 195 x 125 x 55 mm 874 +* Weight: 420g 890 890 ))) 891 891 892 892 (((
- 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-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