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 (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 19 added, 0 removed)
- 1657350248151-650.png
- 1657350625843-586.png
- 1657351240556-536.png
- 1657351312545-300.png
- 1657352146020-183.png
- 1657352185396-303.png
- 1657352391268-297.png
- 1657352403317-397.png
- 1657352634421-276.png
- 1657352645687-385.png
- 1657352898400-901.png
- 1657352914475-252.png
- 1657354294009-643.png
- 1657520100595-569.png
- image-20220709144723-1.png
- image-20220709150546-2.png
- image-20220709161741-3.png
- image-20220908154949-1.png
- image-20220908163102-2.png
Details
- Page properties
-
- Content
-
... ... @@ -9,6 +9,7 @@ 9 9 10 10 **Table of Contents:** 11 11 12 +{{toc/}} 12 12 13 13 14 14 ... ... @@ -16,21 +16,35 @@ 16 16 17 17 = 1. Introduction = 18 18 20 + 19 19 == 1.1 What is N95S31B NB-IoT Sensor Node == 20 20 21 21 ((( 22 22 23 23 26 +((( 24 24 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*. 28 +))) 25 25 30 +((( 26 26 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. 32 +))) 27 27 34 +((( 28 28 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 +))) 29 29 38 +((( 30 30 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). 40 +))) 31 31 42 +((( 43 + 44 +))) 32 32 46 +((( 33 33 ~* make sure you have NB-IoT coverage locally. 48 +))) 34 34 35 35 36 36 ))) ... ... @@ -41,19 +41,20 @@ 41 41 42 42 == 1.2 Features == 43 43 59 + 44 44 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 45 -* Ultra low power consumption 46 -* Distance Detection by Ultrasonic technology 47 -* Flat object range 280mm - 7500mm 48 -* Accuracy: ±(1cm+S*0.3%) (S: Distance) 49 -* Cable Length: 25cm 61 +* Monitor Temperature & Humidity via SHT31 50 50 * AT Commands to change parameters 51 51 * Uplink on periodically 52 52 * Downlink to change configure 53 53 * IP66 Waterproof Enclosure 66 +* Ultra-Low Power consumption 67 +* AT Commands to change parameters 54 54 * Micro SIM card slot for NB-IoT SIM 55 55 * 8500mAh Battery for long term use 56 56 71 + 72 + 57 57 == 1.3 Specification == 58 58 59 59 ... ... @@ -79,13 +79,11 @@ 79 79 * Max continuously current: 130mA 80 80 * Max boost current: 2A, 1 second 81 81 82 -(% style="color:#037691" %)**Power Consumption** 83 83 84 -* STOP Mode: 10uA @ 3.3v 85 -* Max transmit power: 350mA@3.3v 86 86 87 87 == 1.4 Applications == 88 88 102 + 89 89 * Smart Buildings & Home Automation 90 90 * Logistics and Supply Chain Management 91 91 * Smart Metering ... ... @@ -97,24 +97,68 @@ 97 97 98 98 99 99 100 -== 1.5 Pin Definitions == 101 101 102 102 103 - [[image:1657328609906-564.png]]116 +== 1.5 Pin Definitions & Switch == 104 104 105 105 119 +N95S31B use the mother board from NBSN95 which as below. 106 106 107 -= 2. Use NDDS75 to communicate with IoT Server = 108 108 122 +[[image:image-20220709144723-1.png]] 123 + 124 + 125 + 126 +=== 1.5.1 Jumper JP2 === 127 + 128 + 129 +Power on Device when put this jumper. 130 + 131 + 132 + 133 +=== 1.5.2 BOOT MODE / SW1 === 134 + 135 + 136 +((( 137 +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. 138 +))) 139 + 140 +((( 141 +2) Flash: work mode, device starts to work and send out console output for further debug 142 +))) 143 + 144 + 145 + 146 +=== 1.5.3 Reset Button === 147 + 148 + 149 +Press to reboot the device. 150 + 151 + 152 + 153 +=== 1.5.4 LED === 154 + 155 + 156 +It will flash: 157 + 158 +1. When boot the device in flash mode 159 +1. Send an uplink packet 160 + 161 + 162 + 163 += 2. Use N95S31B to communicate with IoT Server = 164 + 165 + 109 109 == 2.1 How it works == 110 110 168 + 111 111 ((( 112 -The N DDS75 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.170 +The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B 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 N95S31B. 113 113 ))) 114 114 115 115 116 116 ((( 117 -The diagram below shows the working flow in default firmware of N DDS75:175 +The diagram below shows the working flow in default firmware of N95S31B: 118 118 ))) 119 119 120 120 ((( ... ... @@ -121,7 +121,7 @@ 121 121 122 122 ))) 123 123 124 -[[image:1657 328659945-416.png]]182 +[[image:1657520100595-569.png]] 125 125 126 126 ((( 127 127 ... ... @@ -128,30 +128,69 @@ 128 128 ))) 129 129 130 130 131 -== 2.2 Configure the N DDS75 ==189 +== 2.2 Configure the N95S31B == 132 132 133 133 192 +=== 2.2.1 Power On N95S31B === 193 + 194 + 195 +[[image:image-20220709150546-2.png]] 196 + 197 + 198 + 134 134 === 2.2.1 Test Requirement === 135 135 201 + 136 136 ((( 137 -To use N DDS75 in your city, make sure meet below requirements:203 +To use N95S31B in your city, make sure meet below requirements: 138 138 ))) 139 139 140 -* Your local operator has already distributed a NB-IoT Network there. 141 -* The local NB-IoT network used the band that NSE01 supports. 142 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 206 +* ((( 207 +Your local operator has already distributed a NB-IoT Network there. 208 +))) 209 +* ((( 210 +The local NB-IoT network used the band that N95S31B supports. 211 +))) 212 +* ((( 213 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 214 +))) 143 143 144 144 ((( 145 -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 server217 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 146 146 ))) 147 147 220 +((( 221 +N95S31B supports different communication protocol such as : 222 +))) 148 148 149 -[[image:1657328756309-230.png]] 224 +((( 225 +* ((( 226 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 227 +))) 228 +* ((( 229 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 230 +))) 231 +* ((( 232 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 233 +))) 234 +* ((( 235 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 236 +))) 150 150 238 +((( 239 +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. 240 +))) 151 151 242 + 243 +))) 152 152 153 - ===2.2.2 Insert SIM card ===245 +[[image:1657350625843-586.png]] 154 154 247 + 248 + 249 +=== 2.2.3 Insert SIM card === 250 + 251 + 155 155 ((( 156 156 Insert the NB-IoT Card get from your provider. 157 157 ))) ... ... @@ -161,20 +161,24 @@ 161 161 ))) 162 162 163 163 164 -[[image:165732 8884227-504.png]]261 +[[image:1657351240556-536.png]] 165 165 166 166 167 167 168 -=== 2.2. 3DDS75 to configure it ===265 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 169 169 267 + 170 170 ((( 171 171 ((( 172 -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. 270 +User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below. 271 + 272 + 173 173 ))) 174 174 ))) 175 175 176 -[[image: image-20220709092052-2.png]]276 +[[image:1657351312545-300.png]] 177 177 278 + 178 178 **Connection:** 179 179 180 180 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -193,22 +193,24 @@ 193 193 * Flow Control: (% style="color:green" %)**None** 194 194 195 195 ((( 196 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N DDS75.DDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.297 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 197 197 ))) 198 198 199 199 [[image:1657329814315-101.png]] 200 200 302 + 201 201 ((( 202 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]304 +(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]** 203 203 ))) 204 204 205 205 206 206 207 -=== 2.2. 4309 +=== 2.2.5 Use CoAP protocol to uplink data === 208 208 209 -(% 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/]] 210 210 312 +(% 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/]]** 211 211 314 + 212 212 ((( 213 213 **Use below commands:** 214 214 ))) ... ... @@ -224,10 +224,12 @@ 224 224 ))) 225 225 226 226 ((( 330 + 331 + 227 227 For parameter description, please refer to AT command set 228 228 ))) 229 229 230 -[[image:16573 30452568-615.png]]335 +[[image:1657352146020-183.png]] 231 231 232 232 233 233 ((( ... ... @@ -234,11 +234,11 @@ 234 234 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. 235 235 ))) 236 236 237 -[[image:16573 30472797-498.png]]342 +[[image:1657352185396-303.png]] 238 238 239 239 240 240 241 -=== 2.2. 5346 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 242 242 243 243 244 244 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -245,109 +245,119 @@ 245 245 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 246 246 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 247 247 248 -[[image:16573 30501006-241.png]]353 +[[image:1657352391268-297.png]] 249 249 250 250 251 -[[image:16573 30533775-472.png]]356 +[[image:1657352403317-397.png]] 252 252 253 253 254 254 255 -=== 2.2. 6360 +=== 2.2.7 Use MQTT protocol to uplink data === 256 256 257 257 363 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 364 + 258 258 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 259 259 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 260 260 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 261 261 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 262 262 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 263 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT264 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT370 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 371 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 265 265 266 -[[image:165724 9978444-674.png]]373 +[[image:1657352634421-276.png]] 267 267 268 268 269 -[[image:16573 30723006-866.png]]376 +[[image:1657352645687-385.png]] 270 270 271 271 272 272 ((( 273 - MQTT protocolhas amuch higherpowerconsumptioncomparevsUDP / CoAPprotocol.Pleasecheckthe power analyzedocument and adjustthe uplinkperiodto asuitable interval.380 +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. 274 274 ))) 275 275 276 276 384 +((( 385 +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. 386 +))) 277 277 278 -=== 2.2.7 Use TCP protocol to uplink data === 279 279 280 280 390 +=== 2.2.8 Use TCP protocol to uplink data === 391 + 392 + 393 +This feature is supported since firmware version v110 394 + 281 281 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 282 282 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 283 283 284 -[[image: image-20220709093918-1.png]]398 +[[image:1657352898400-901.png]] 285 285 286 286 287 -[[image: image-20220709093918-2.png]]401 +[[image:1657352914475-252.png]] 288 288 289 289 290 290 291 -=== 2.2. 8405 +=== 2.2.9 Change Update Interval === 292 292 407 + 293 293 User can use below command to change the (% style="color:green" %)**uplink interval**. 294 294 295 295 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 296 296 297 297 ((( 298 - (%style="color:red" %)**NOTE:**413 + 299 299 ))) 300 300 301 301 ((( 302 -(% style="color:red" %) 1.By default, thedevicewillsend an uplinkmessageevery1hour.417 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 303 303 ))) 304 304 420 +((( 421 +(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).** 422 +))) 305 305 306 306 425 + 307 307 == 2.3 Uplink Payload == 308 308 309 -In this mode, uplink payload includes in total 14 bytes 310 310 429 +((( 430 +N95S31B has different working modes for the connections of different types 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. 431 +))) 311 311 312 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 313 -|=(% style="width: 60px;" %)((( 314 -**Size(bytes)** 315 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 316 -|(% 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:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]] 317 317 318 318 ((( 319 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.435 +For example: 320 320 ))) 321 321 438 +((( 439 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 440 +))) 322 322 323 -[[image:1657331036973-987.png]] 324 324 325 325 ((( 326 -The payload is ASCIIstring,representative sameHEX:444 +The uplink payloads are composed in ASCII String. For example: 327 327 ))) 328 328 329 329 ((( 330 -0 x72403155615900640c6c19029200where:448 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 331 331 ))) 332 332 333 - *(((334 - DeviceID:0x724031556159=724031556159451 +((( 452 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 335 335 ))) 336 -* ((( 337 -Version: 0x0064=100=1.0.0 454 + 455 + 456 +((( 457 +(% style="color:red" %)**NOTE:** 338 338 ))) 339 339 340 -* ((( 341 -BAT: 0x0c6c = 3180 mV = 3.180V 460 +(% style="color:red" %) 461 +1. ((( 462 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 342 342 ))) 343 -* ((( 344 -Signal: 0x19 = 25 345 -))) 346 -* ((( 347 -Distance: 0x0292= 658 mm 348 -))) 349 -* ((( 350 -Interrupt: 0x00 = 0 464 +1. ((( 465 +**By default, the device will send an uplink message every 1 hour.** 351 351 352 352 353 353 ... ... @@ -354,105 +354,163 @@ 354 354 355 355 ))) 356 356 357 -== 2. 4PayloadExplanation and SensorInterface==472 +=== 2.3.1 Payload Analyze === 358 358 359 359 360 -=== 2. 4.1DeviceID===475 +==== 2.3.1.1 Before Firmware v1.2 ==== 361 361 477 + 478 +N95S31B uplink payload includes in total 21 bytes 479 + 480 + 481 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %) 482 +|=(% style="width: 60px;" %)((( 483 +**Size(bytes)** 484 +)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 174px;" %)5|=(% style="width: 106px;" %)**2**|=(% style="width: 85px;" %)**2** 485 +|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:174px" %)((( 362 362 ((( 363 - By default, theDeviceID equal to thelast6bytes of IMEI.487 +Reserve/ Same as NBSN95 CFGMOD=1 364 364 ))) 365 365 366 366 ((( 367 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID491 +No function here. 368 368 ))) 493 +)))|(% style="width:106px" %)((( 494 +((( 495 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 496 +))) 369 369 370 370 ((( 371 - **Example:**499 +By SHT31 372 372 ))) 501 +)))|(% style="width:85px" %)((( 502 +((( 503 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 504 +))) 373 373 374 374 ((( 375 - AT+DEUI=A84041F15612507 +By SHT31 376 376 ))) 509 +))) 377 377 378 378 ((( 379 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 512 + 513 + 514 +((( 515 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 380 380 ))) 517 +))) 381 381 382 382 520 +[[image:1657354294009-643.png]] 383 383 384 -=== 2.4.2 Version Info === 385 385 386 -((( 387 -Specify the software version: 0x64=100, means firmware version 1.00. 388 -))) 523 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 389 389 390 -((( 391 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 392 -))) 525 +* Device ID: 0x724031607457 = 724031607457 393 393 527 +* Version: 0x006e=110=1.1.0 394 394 529 +* BAT: 0x0ccd = 3277 mV = 3.277V 395 395 396 - ===2.4.3BatteryInfo===531 +* Signal: 0x1b = 27 397 397 398 -((( 399 -Ex1: 0x0B45 = 2885mV 400 -))) 533 +* Model: 0x01 = 1 401 401 535 +* 0x00dc000ccc= reserve, ignore in N95S31B 536 + 537 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 538 + 539 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 540 + 402 402 ((( 403 -Ex2: 0x0B49 = 2889mV 542 + 543 + 544 + 545 + 404 404 ))) 405 405 548 +==== 2.3.1.2 Since Firmware v1.2 ==== 406 406 550 +In this mode, uplink payload includes 91 bytes in total by default. 407 407 408 - ===2.4.4SignalStrength===552 +Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded. 409 409 410 -((( 411 -NB-IoT Network signal Strength. 412 -))) 554 +|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4 555 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp ..... 413 413 414 -((( 415 -**Ex1: 0x1d = 29** 416 -))) 557 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 417 417 559 +[[image:image-20220908154949-1.png]] 560 + 561 +The payload is ASCII string, representative same HEX: 562 + 563 +0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where: 564 + 565 +* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782 566 +* (% style="color:blue" %) Version: 0x000c=120=1.2 567 +* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V 568 +* (% style="color:red" %) Singal: 0x0c = 12 569 +* (% style="color:blue" %) Mod: 0x01 = 1 570 +* TemDS18B20: 0x0000= 0 = 0 571 +* (% style="color:green" %)Interrupt: 0x00= 0 572 +* (% style="color:green" %)adc: 0x0030= 48 573 +* SHTTEM: 0x0114= 276 = 27.6 574 +* SHTHUM:0x0231 =561=56.1% 575 +* (% style="color:red" %) Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 576 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 577 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 578 + 579 +=== 2.3.2 Device ID === 580 + 581 + 418 418 ((( 419 - (% style="color:blue"%)**0**(%%)-113dBmorless583 +By default, the Device ID equal to the last 6 bytes of IMEI. 420 420 ))) 421 421 422 422 ((( 423 -(% style="color:blue" %)** 1**(%%)-111dBm587 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 424 424 ))) 425 425 426 426 ((( 427 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm591 +**Example:** 428 428 ))) 429 429 430 430 ((( 431 - (% style="color:blue" %)**31** (%%) -51dBm or greater595 +AT+DEUI=A84041F15612 432 432 ))) 433 433 434 434 ((( 435 -(% style="color:blue" %)**99** (%%) Not known or not detectable 599 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 600 + 601 + 436 436 ))) 437 437 604 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 438 438 439 439 440 - ===2.4.5Distance===607 +By default, the Device ID equal to the last 15 bits of IMEI. 441 441 442 - Getthe distance.Flatbjectrange280mm - 7500mm.609 +User can use **AT+DEUI** to set Device ID 443 443 611 +**Example:** 612 + 613 +AT+DEUI=868411056754138 614 + 615 + 616 +=== 2.3.3 Version Info === 617 + 618 + 444 444 ((( 445 - Forexample,if the datayou getfrom theregisteris **__0x0B 0x05__**, the distancebetweenthesensorand the measuredobject is620 +These bytes include the hardware and software version. 446 446 ))) 447 447 448 448 ((( 449 -((( 450 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 624 +Higher byte: Specify hardware version: always 0x00 for N95S31B 451 451 ))) 452 -))) 453 453 454 454 ((( 455 - 628 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 456 456 ))) 457 457 458 458 ((( ... ... @@ -459,65 +459,85 @@ 459 459 460 460 ))) 461 461 462 -=== 2.4.6 Digital Interrupt === 463 - 464 464 ((( 465 - Digital Interruptrefers topin (% style="color:blue"%)**GPIO_EXTI**(%%),andtherearedifferent triggermethods. When thereisa trigger, theNDDS75 will send a packetto theserver.636 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 466 466 ))) 467 467 468 468 ((( 469 - Thecommand is:640 + 470 470 ))) 471 471 643 + 644 +=== 2.3.4 Battery Info === 645 + 646 + 472 472 ((( 473 - (% 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]])**.**648 +Ex1: 0x0B45 = 2885mV 474 474 ))) 475 475 476 - 477 477 ((( 478 - Thelowerfourbits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.652 +Ex2: 0x0B49 = 2889mV 479 479 ))) 480 480 481 481 656 + 657 +=== 2.3.5 Signal Strength === 658 + 659 + 482 482 ((( 483 - Example:661 +NB-IoT Network signal Strength. 484 484 ))) 485 485 486 486 ((( 487 - 0x(00):Normaluplinkpacket.665 +**Ex1: 0x1d = 29** 488 488 ))) 489 489 490 490 ((( 491 - 0x(01):InterruptUplinkPacket.669 +(% style="color:blue" %)**0**(%%) -113dBm or less 492 492 ))) 493 493 494 - 495 - 496 -=== 2.4.7 +5V Output === 497 - 498 498 ((( 499 - NDDS75willenable +5Voutputbeforeallsamplinganddisablethe+5vafterall sampling.673 +(% style="color:blue" %)**1**(%%) -111dBm 500 500 ))) 501 501 502 - 503 503 ((( 504 - The5V output timean be controlledbyAT Command.677 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 505 505 ))) 506 506 507 507 ((( 508 -(% style="color:blue" %)** AT+5VT=1000**681 +(% style="color:blue" %)**31** (%%) -51dBm or greater 509 509 ))) 510 510 511 511 ((( 512 - Meansset5V valid timetohave 1000ms. Sothereal5V outputwillactuallyhave1000ms+samplingtime for othersensors.685 +(% style="color:blue" %)**99** (%%) Not known or not detectable 513 513 ))) 514 514 515 515 516 516 517 -== 2. 5Downlink Payload ==690 +=== 2.3.6 Temperature & Humidity === 518 518 519 -By default, NDDS75 prints the downlink payload to console port. 520 520 693 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 694 + 695 +[[image:image-20220709161741-3.png]] 696 + 697 + 698 +Convert the read byte to decimal and divide it by ten. 699 + 700 + 701 +**Example:** 702 + 703 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 704 + 705 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 706 + 707 + 708 + 709 +== 2.4 Downlink Payload == 710 + 711 + 712 +By default, N95S31B prints the downlink payload to console port. 713 + 521 521 [[image:image-20220709100028-1.png]] 522 522 523 523 ... ... @@ -554,7 +554,7 @@ 554 554 ))) 555 555 556 556 ((( 557 -If payload = 0x04FF, it will reset the DDS75750 +If payload = 0x04FF, it will reset the N95S31B 558 558 ))) 559 559 560 560 ... ... @@ -565,49 +565,61 @@ 565 565 ))) 566 566 567 567 761 +== 2.5 Humidity and Temperature alarm function == 568 568 569 - ==2.6LED Indicator ==763 +➢ AT Command: 570 570 765 +AT+ SHHUM=min,max 571 571 572 - TheNDDS75has an internalLED whichis to show thestatus of differentstate.767 +² When min=0, and max≠0, Alarm higher than max 573 573 769 +² When min≠0, and max=0, Alarm lower than min 574 574 575 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 576 -* Then the LED will be on for 1 second means device is boot normally. 577 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 578 -* For each uplink probe, LED will be on for 500ms. 771 +² When min≠0 and max≠0, Alarm higher than max or lower than min 579 579 580 -((( 581 - 582 -))) 773 +Example: 583 583 775 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 584 584 585 585 586 - ==2.7 Firmware Change Log ==778 +AT+ SHTEMP=min,max 587 587 780 +² When min=0, and max≠0, Alarm higher than max 588 588 589 -((( 590 -Download URL & Firmware Change log 591 -))) 782 +² When min≠0, and max=0, Alarm lower than min 592 592 593 -((( 594 -[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]] 595 -))) 784 +² When min≠0 and max≠0, Alarm higher than max or lower than min 596 596 786 +Example: 597 597 598 -((( 599 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 600 -))) 788 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 601 601 790 +== 2.6 Set the number of data to be uploaded and the recording time == 602 602 792 +➢ AT Command: 603 603 794 +AT+TR=900 ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds) 795 + 796 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 797 + 798 +== 2.7 Read or Clear cached data == 799 + 800 +➢ AT Command: 801 + 802 +AT+CDP ~/~/ Read cached data 803 + 804 +[[image:image-20220908163102-2.png]] 805 + 806 +AT+CDP=0 ~/~/ Clear cached data 807 + 604 604 == 2.8 Battery Analysis == 605 605 810 + 606 606 === 2.8.1 Battery Type === 607 607 608 608 609 609 ((( 610 -The N DDS75 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.815 +The N95S31B 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. 611 611 ))) 612 612 613 613 ((( ... ... @@ -630,54 +630,35 @@ 630 630 631 631 === 2.8.2 Power consumption Analyze === 632 632 633 -((( 634 -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. 635 -))) 636 636 637 - 638 638 ((( 639 -Instruction to use as below:840 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 640 640 ))) 641 641 642 642 ((( 643 - (%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/]]844 + 644 644 ))) 645 645 646 646 647 -((( 648 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 649 -))) 848 +=== 2.8.3 Battery Note === 650 650 651 -* ((( 652 -Product Model 653 -))) 654 -* ((( 655 -Uplink Interval 656 -))) 657 -* ((( 658 -Working Mode 659 -))) 660 660 661 661 ((( 662 - And the Life expectation in difference casewillbe shownon theright.852 +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 uplink data, then the battery life may be decreased. 663 663 ))) 664 664 665 -[[image:image-20220709110451-3.png]] 666 666 667 667 857 +=== 2.8.4 Replace the battery === 668 668 669 -=== 2.8.3 Battery Note === 670 670 671 671 ((( 672 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.861 +You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board. 673 673 ))) 674 674 675 675 676 - 677 -=== 2.8.4 Replace the battery === 678 - 679 679 ((( 680 -The default battery pack of N DDS75 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).866 +The default battery pack of N95S31B 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). 681 681 ))) 682 682 683 683 ... ... @@ -684,6 +684,7 @@ 684 684 685 685 = 3. Access NB-IoT Module = 686 686 873 + 687 687 ((( 688 688 Users can directly access the AT command set of the NB-IoT module. 689 689 ))) ... ... @@ -690,6 +690,8 @@ 690 690 691 691 ((( 692 692 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/]] 880 + 881 + 693 693 ))) 694 694 695 695 [[image:1657333200519-600.png]] ... ... @@ -698,11 +698,13 @@ 698 698 699 699 = 4. Using the AT Commands = 700 700 890 + 701 701 == 4.1 Access AT Commands == 702 702 703 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 704 704 894 +See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]] 705 705 896 + 706 706 AT+<CMD>? : Help on <CMD> 707 707 708 708 AT+<CMD> : Run <CMD> ... ... @@ -742,7 +742,24 @@ 742 742 743 743 AT+SERVADDR : Server Address 744 744 936 +AT+TR : Get or Set record time 745 745 938 +AT+APN : Get or set the APN 939 + 940 +AT+FBAND : Get or Set whether to automatically modify the frequency band 941 + 942 +AT+DNSCFG : Get or Set DNS Server 943 + 944 +AT+GETSENSORVALUE : Returns the current sensor measurement 945 + 946 +AT+NOUD : Get or Set the number of data to be uploaded 947 + 948 +AT+CDP : Read or Clear cached data 949 + 950 +AT+SHTEMP: Get or Set alarm of temp 951 + 952 +AT+SHHUM: Get or Set alarm of moisture 953 + 746 746 (% style="color:#037691" %)**COAP Management** 747 747 748 748 AT+URI : Resource parameters ... ... @@ -776,6 +776,7 @@ 776 776 777 777 = 5. FAQ = 778 778 987 + 779 779 == 5.1 How to Upgrade Firmware == 780 780 781 781 ... ... @@ -788,13 +788,18 @@ 788 788 ))) 789 789 790 790 ((( 791 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 1000 + 1001 + 1002 +((( 1003 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 792 792 ))) 1005 +))) 793 793 794 794 795 795 796 796 = 6. Trouble Shooting = 797 797 1011 + 798 798 == 6.1 Connection problem when uploading firmware == 799 799 800 800 ... ... @@ -810,6 +810,7 @@ 810 810 811 811 == 6.2 AT Command input doesn't work == 812 812 1027 + 813 813 ((( 814 814 In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. 815 815 ... ... @@ -820,7 +820,7 @@ 820 820 = 7. Order Info = 821 821 822 822 823 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**1038 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 824 824 825 825 826 826 (% class="wikigeneratedid" %) ... ... @@ -835,7 +835,7 @@ 835 835 836 836 (% style="color:#037691" %)**Package Includes**: 837 837 838 -* NS E01DistanceDetectSensorNode x 11053 +* N95S31B NB-IoT Temperature and Humidity Sensor 839 839 * External antenna x 1 840 840 ))) 841 841 ... ... @@ -844,11 +844,10 @@ 844 844 845 845 (% style="color:#037691" %)**Dimension and weight**: 846 846 847 - 848 848 * Device Size: 13.0 x 5 x 4.5 cm 849 849 * Device Weight: 150g 850 -* Package Size / pcs : 1 5x12x 5.5cm851 -* Weight / pcs : 220g1064 +* Package Size / pcs : 14.0 x 8x 5 cm 1065 +* Weight / pcs : 180g 852 852 ))) 853 853 854 854 ((( ... ... @@ -860,5 +860,6 @@ 860 860 861 861 = 9. Support = 862 862 1077 + 863 863 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 864 864 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
- 1657350248151-650.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- 1657350625843-586.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +93.3 KB - Content
- 1657351240556-536.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +483.6 KB - Content
- 1657351312545-300.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +675.8 KB - Content
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 KB - Content
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- image-20220709144723-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +413.1 KB - Content
- image-20220709150546-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +333.5 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.2 KB - Content
- image-20220908154949-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +58.5 KB - Content
- image-20220908163102-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.7 KB - Content