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, 18 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-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 ))) ... ... @@ -53,8 +53,6 @@ 53 53 * Micro SIM card slot for NB-IoT SIM 54 54 * 8500mAh Battery for long term use 55 55 56 - 57 - 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -74,7 +74,6 @@ 74 74 75 75 (% style="color:#037691" %)**Battery:** 76 76 77 - 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -81,10 +81,9 @@ 81 81 * Max continuously current: 130mA 82 82 * Max boost current: 2A, 1 second 83 83 84 - 85 - 86 86 == 1.4 Applications == 87 87 98 + 88 88 * Smart Buildings & Home Automation 89 89 * Logistics and Supply Chain Management 90 90 * Smart Metering ... ... @@ -96,15 +96,21 @@ 96 96 97 97 98 98 99 -== 1.5 Pin Definitions == 100 100 111 + 112 +== 1.5 Pin Definitions & Switch == 113 + 114 + 101 101 N95S31B use the mother board from NBSN95 which as below. 102 102 117 + 103 103 [[image:image-20220709144723-1.png]] 104 104 105 105 121 + 106 106 === 1.5.1 Jumper JP2 === 107 107 124 + 108 108 Power on Device when put this jumper. 109 109 110 110 ... ... @@ -111,14 +111,20 @@ 111 111 112 112 === 1.5.2 BOOT MODE / SW1 === 113 113 131 + 132 +((( 114 114 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. 134 +))) 115 115 136 +((( 116 116 2) Flash: work mode, device starts to work and send out console output for further debug 138 +))) 117 117 118 118 119 119 120 120 === 1.5.3 Reset Button === 121 121 144 + 122 122 Press to reboot the device. 123 123 124 124 ... ... @@ -125,16 +125,15 @@ 125 125 126 126 === 1.5.4 LED === 127 127 151 + 128 128 It will flash: 129 129 130 130 1. When boot the device in flash mode 131 131 1. Send an uplink packet 132 132 133 - 134 - 135 - 136 136 = 2. Use N95S31B to communicate with IoT Server = 137 137 159 + 138 138 == 2.1 How it works == 139 139 140 140 ... ... @@ -151,7 +151,7 @@ 151 151 152 152 ))) 153 153 154 -[[image:1657 328659945-416.png]]176 +[[image:1657520100595-569.png]] 155 155 156 156 ((( 157 157 ... ... @@ -158,30 +158,69 @@ 158 158 ))) 159 159 160 160 161 -== 2.2 Configure the N DDS75 ==183 +== 2.2 Configure the N95S31B == 162 162 163 163 186 +=== 2.2.1 Power On N95S31B === 187 + 188 + 189 +[[image:image-20220709150546-2.png]] 190 + 191 + 192 + 164 164 === 2.2.1 Test Requirement === 165 165 195 + 166 166 ((( 167 -To use N DDS75 in your city, make sure meet below requirements:197 +To use N95S31B in your city, make sure meet below requirements: 168 168 ))) 169 169 170 -* Your local operator has already distributed a NB-IoT Network there. 171 -* The local NB-IoT network used the band that NSE01 supports. 172 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 200 +* ((( 201 +Your local operator has already distributed a NB-IoT Network there. 202 +))) 203 +* ((( 204 +The local NB-IoT network used the band that N95S31B supports. 205 +))) 206 +* ((( 207 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 208 +))) 173 173 174 174 ((( 175 -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 server211 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 176 176 ))) 177 177 214 +((( 215 +N95S31B supports different communication protocol such as : 216 +))) 178 178 179 -[[image:1657328756309-230.png]] 218 +((( 219 +* ((( 220 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 221 +))) 222 +* ((( 223 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 224 +))) 225 +* ((( 226 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 227 +))) 228 +* ((( 229 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 230 +))) 180 180 232 +((( 233 +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. 234 +))) 181 181 236 + 237 +))) 182 182 183 - ===2.2.2 Insert SIM card ===239 +[[image:1657350625843-586.png]] 184 184 241 + 242 + 243 +=== 2.2.3 Insert SIM card === 244 + 245 + 185 185 ((( 186 186 Insert the NB-IoT Card get from your provider. 187 187 ))) ... ... @@ -191,20 +191,24 @@ 191 191 ))) 192 192 193 193 194 -[[image:165732 8884227-504.png]]255 +[[image:1657351240556-536.png]] 195 195 196 196 197 197 198 -=== 2.2. 3DDS75 to configure it ===259 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 199 199 261 + 200 200 ((( 201 201 ((( 202 -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. 264 +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. 265 + 266 + 203 203 ))) 204 204 ))) 205 205 206 -[[image: image-20220709092052-2.png]]270 +[[image:1657351312545-300.png]] 207 207 272 + 208 208 **Connection:** 209 209 210 210 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -223,22 +223,24 @@ 223 223 * Flow Control: (% style="color:green" %)**None** 224 224 225 225 ((( 226 -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.291 +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. 227 227 ))) 228 228 229 229 [[image:1657329814315-101.png]] 230 230 296 + 231 231 ((( 232 -(% 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/]]298 +(% 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]]** 233 233 ))) 234 234 235 235 236 236 237 -=== 2.2. 4303 +=== 2.2.5 Use CoAP protocol to uplink data === 238 238 239 -(% 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/]] 240 240 306 +(% 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/]]** 241 241 308 + 242 242 ((( 243 243 **Use below commands:** 244 244 ))) ... ... @@ -254,10 +254,12 @@ 254 254 ))) 255 255 256 256 ((( 324 + 325 + 257 257 For parameter description, please refer to AT command set 258 258 ))) 259 259 260 -[[image:16573 30452568-615.png]]329 +[[image:1657352146020-183.png]] 261 261 262 262 263 263 ((( ... ... @@ -264,11 +264,11 @@ 264 264 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. 265 265 ))) 266 266 267 -[[image:16573 30472797-498.png]]336 +[[image:1657352185396-303.png]] 268 268 269 269 270 270 271 -=== 2.2. 5340 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 272 272 273 273 274 274 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -275,109 +275,119 @@ 275 275 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 276 276 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 277 277 278 -[[image:16573 30501006-241.png]]347 +[[image:1657352391268-297.png]] 279 279 280 280 281 -[[image:16573 30533775-472.png]]350 +[[image:1657352403317-397.png]] 282 282 283 283 284 284 285 -=== 2.2. 6354 +=== 2.2.7 Use MQTT protocol to uplink data === 286 286 287 287 357 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 358 + 288 288 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 289 289 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 290 290 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 291 291 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 292 292 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 293 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT294 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT364 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 365 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 295 295 296 -[[image:165724 9978444-674.png]]367 +[[image:1657352634421-276.png]] 297 297 298 298 299 -[[image:16573 30723006-866.png]]370 +[[image:1657352645687-385.png]] 300 300 301 301 302 302 ((( 303 - MQTT protocolhas amuch higherpowerconsumptioncomparevsUDP / CoAPprotocol.Pleasecheckthe power analyzedocument and adjustthe uplinkperiodto asuitable interval.374 +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. 304 304 ))) 305 305 306 306 378 +((( 379 +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. 380 +))) 307 307 308 -=== 2.2.7 Use TCP protocol to uplink data === 309 309 310 310 384 +=== 2.2.8 Use TCP protocol to uplink data === 385 + 386 + 387 +This feature is supported since firmware version v110 388 + 311 311 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 312 312 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 313 313 314 -[[image: image-20220709093918-1.png]]392 +[[image:1657352898400-901.png]] 315 315 316 316 317 -[[image: image-20220709093918-2.png]]395 +[[image:1657352914475-252.png]] 318 318 319 319 320 320 321 -=== 2.2. 8399 +=== 2.2.9 Change Update Interval === 322 322 401 + 323 323 User can use below command to change the (% style="color:green" %)**uplink interval**. 324 324 325 325 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 326 326 327 327 ((( 328 - (%style="color:red" %)**NOTE:**407 + 329 329 ))) 330 330 331 331 ((( 332 -(% style="color:red" %) 1.By default, thedevicewillsend an uplinkmessageevery1hour.411 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 333 333 ))) 334 334 414 +((( 415 +(% 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).** 416 +))) 335 335 336 336 419 + 337 337 == 2.3 Uplink Payload == 338 338 339 -In this mode, uplink payload includes in total 14 bytes 340 340 423 +((( 424 +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. 425 +))) 341 341 342 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 343 -|=(% style="width: 60px;" %)((( 344 -**Size(bytes)** 345 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 346 -|(% 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"]] 347 347 348 348 ((( 349 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.429 +For example: 350 350 ))) 351 351 432 +((( 433 + (% 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. 434 +))) 352 352 353 -[[image:1657331036973-987.png]] 354 354 355 355 ((( 356 -The payload is ASCIIstring,representative sameHEX:438 +The uplink payloads are composed in ASCII String. For example: 357 357 ))) 358 358 359 359 ((( 360 -0 x72403155615900640c6c19029200where:442 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 361 361 ))) 362 362 363 - *(((364 - DeviceID:0x724031556159=724031556159445 +((( 446 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 365 365 ))) 366 -* ((( 367 -Version: 0x0064=100=1.0.0 448 + 449 + 450 +((( 451 +(% style="color:red" %)**NOTE:** 368 368 ))) 369 369 370 -* ((( 371 -BAT: 0x0c6c = 3180 mV = 3.180V 454 +(% style="color:red" %) 455 +1. ((( 456 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 372 372 ))) 373 -* ((( 374 -Signal: 0x19 = 25 375 -))) 376 -* ((( 377 -Distance: 0x0292= 658 mm 378 -))) 379 -* ((( 380 -Interrupt: 0x00 = 0 458 +1. ((( 459 +**By default, the device will send an uplink message every 1 hour.** 381 381 382 382 383 383 ... ... @@ -384,105 +384,186 @@ 384 384 385 385 ))) 386 386 387 -== 2. 4PayloadExplanation and SensorInterface==466 +=== 2.3.1 Payload Analyze === 388 388 389 389 390 -=== 2. 4.1DeviceID===469 +==== 2.3.1.1 Before Firmware v1.2 ==== 391 391 471 + 472 +N95S31B uplink payload includes in total 21 bytes 473 + 474 + 475 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %) 476 +|=(% style="width: 60px;" %)((( 477 +**Size(bytes)** 478 +)))|=(% 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** 479 +|(% 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" %)((( 392 392 ((( 393 - By default, theDeviceID equal to thelast6bytes of IMEI.481 +Reserve/ Same as NBSN95 CFGMOD=1 394 394 ))) 395 395 396 396 ((( 397 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID485 +No function here. 398 398 ))) 487 +)))|(% style="width:106px" %)((( 488 +((( 489 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 490 +))) 399 399 400 400 ((( 401 - **Example:**493 +By SHT31 402 402 ))) 495 +)))|(% style="width:85px" %)((( 496 +((( 497 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 498 +))) 403 403 404 404 ((( 405 - AT+DEUI=A84041F15612501 +By SHT31 406 406 ))) 503 +))) 407 407 408 408 ((( 409 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 506 + 507 + 508 +((( 509 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 410 410 ))) 511 +))) 411 411 412 412 514 +[[image:1657354294009-643.png]] 413 413 414 -=== 2.4.2 Version Info === 415 415 416 -((( 417 -Specify the software version: 0x64=100, means firmware version 1.00. 418 -))) 517 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 419 419 420 -((( 421 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 422 -))) 519 +* Device ID: 0x724031607457 = 724031607457 423 423 521 +* Version: 0x006e=110=1.1.0 424 424 523 +* BAT: 0x0ccd = 3277 mV = 3.277V 425 425 426 - ===2.4.3BatteryInfo===525 +* Signal: 0x1b = 27 427 427 428 -((( 429 -Ex1: 0x0B45 = 2885mV 430 -))) 527 +* Model: 0x01 = 1 431 431 529 +* 0x00dc000ccc= reserve, ignore in N95S31B 530 + 531 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 532 + 533 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 534 + 432 432 ((( 433 -Ex2: 0x0B49 = 2889mV 536 + 537 + 538 + 539 + 434 434 ))) 435 435 542 +==== 2.3.1.2 Since Firmware v1.2 ==== 436 436 437 437 438 - ===2.4.4SignalStrength===545 +In this mode, uplink payload includes 91 bytes in total by default. 439 439 440 -((( 441 -NB-IoT Network signal Strength. 442 -))) 547 +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. 443 443 444 -((( 445 -**Ex1: 0x1d = 29** 446 -))) 447 447 550 +(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %) 551 +|(% style="width:95px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:47px" %)**2**|(% style="width:124px" %)**1**|(% style="width:56px" %)**1**|(% style="width:109px" %)**2**|(% style="width:80px" %)**1**|(% style="width:51px" %)**2**|(% style="width:79px" %)**2**|(% style="width:84px" %)**2**|(% style="width:100px" %)**4**|(% style="width:76px" %)**2**|(% style="width:81px" %)**2**|(% style="width:121px" %)**4** 552 +|(% style="width:95px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp ..... 553 + 554 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 555 + 556 + 557 +[[image:image-20220908154949-1.png]] 558 + 559 + 560 +The payload is ASCII string, representative same HEX: 561 + 562 +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: 563 + 564 +* (% style="color:red" %)Device ID: f868411056758782 = f868411056758782 565 + 566 +* (% style="color:blue" %)Version: 0x000c=120=1.2 567 + 568 +* (% style="color:green" %)BAT: 0x0d0f = 3343 mV = 3.343V 569 + 570 +* (% style="color:red" %)Singal: 0x0c = 12 571 + 572 +* (% style="color:blue" %)Mod: 0x01 = 1 573 + 574 +* TemDS18B20: 0x0000= 0 = 0 575 + 576 +* (% style="color:green" %)Interrupt: 0x00= 0 577 + 578 +* (% style="color:green" %)adc: 0x0030= 48 579 + 580 +* SHTTEM: 0x0114= 276 = 27.6 581 + 582 +* SHTHUM:0x0231 =561=56.1% 583 + 584 +* (% style="color:red" %)Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 585 + 586 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 587 + 588 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 589 + 590 + 591 + 592 +=== 2.3.2 Device ID === 593 + 594 + 448 448 ((( 449 - (% style="color:blue"%)**0**(%%)-113dBmorless596 +By default, the Device ID equal to the last 6 bytes of IMEI. 450 450 ))) 451 451 452 452 ((( 453 -(% style="color:blue" %)**1**(%%) -111dBm 600 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 601 + 602 + 454 454 ))) 455 455 456 456 ((( 457 -(% style="color:blue" %) **2...30**(%%)-109dBm... -53dBm606 +**(% style="color:blue" %)Example:(%%)** 458 458 ))) 459 459 460 460 ((( 461 - (% style="color:blue" %)**31** (%%) -51dBm or greater610 +AT+DEUI=A84041F15612 462 462 ))) 463 463 464 464 ((( 465 -(% style="color:blue" %)**99** (%%) Not known or not detectable 614 +The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID. 615 + 616 + 466 466 ))) 467 467 619 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 468 468 469 469 470 - ===2.4.5Distance===622 +By default, the Device ID equal to the last 15 bits of IMEI. 471 471 472 - Getthedistance.Flatbjectrange280mm - 7500mm.624 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 473 473 626 + 627 +**(% style="color:blue" %)Example:(%%)** 628 + 629 +AT+DEUI=868411056754138 630 + 631 + 632 + 633 +=== 2.3.3 Version Info === 634 + 635 + 474 474 ((( 475 - Forexample,if the datayou getfrom theregisteris **__0x0B 0x05__**, the distancebetweenthesensorand the measuredobject is637 +These bytes include the hardware and software version. 476 476 ))) 477 477 478 478 ((( 479 -((( 480 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 641 +Higher byte: Specify hardware version: always 0x00 for N95S31B 481 481 ))) 482 -))) 483 483 484 484 ((( 485 - 645 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 486 486 ))) 487 487 488 488 ((( ... ... @@ -489,65 +489,85 @@ 489 489 490 490 ))) 491 491 492 -=== 2.4.6 Digital Interrupt === 493 - 494 494 ((( 495 - Digital Interruptrefers topin (% style="color:blue"%)**GPIO_EXTI**(%%),andtherearedifferent triggermethods. When thereisa trigger, theNDDS75 will send a packetto theserver.653 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 496 496 ))) 497 497 498 498 ((( 499 - Thecommand is:657 + 500 500 ))) 501 501 660 + 661 +=== 2.3.4 Battery Info === 662 + 663 + 502 502 ((( 503 - (% 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]])**.**665 +Ex1: 0x0B45 = 2885mV 504 504 ))) 505 505 506 - 507 507 ((( 508 - Thelowerfourbits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.669 +Ex2: 0x0B49 = 2889mV 509 509 ))) 510 510 511 511 673 + 674 +=== 2.3.5 Signal Strength === 675 + 676 + 512 512 ((( 513 - Example:678 +NB-IoT Network signal Strength. 514 514 ))) 515 515 516 516 ((( 517 - 0x(00):Normaluplinkpacket.682 +**Ex1: 0x1d = 29** 518 518 ))) 519 519 520 520 ((( 521 - 0x(01):InterruptUplinkPacket.686 +(% style="color:blue" %)**0**(%%) -113dBm or less 522 522 ))) 523 523 524 - 525 - 526 -=== 2.4.7 +5V Output === 527 - 528 528 ((( 529 - NDDS75willenable +5Voutputbeforeallsamplinganddisablethe+5vafterall sampling.690 +(% style="color:blue" %)**1**(%%) -111dBm 530 530 ))) 531 531 532 - 533 533 ((( 534 - The5V output timean be controlledbyAT Command.694 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 535 535 ))) 536 536 537 537 ((( 538 -(% style="color:blue" %)** AT+5VT=1000**698 +(% style="color:blue" %)**31** (%%) -51dBm or greater 539 539 ))) 540 540 541 541 ((( 542 - Meansset5V valid timetohave 1000ms. Sothereal5V outputwillactuallyhave1000ms+samplingtime for othersensors.702 +(% style="color:blue" %)**99** (%%) Not known or not detectable 543 543 ))) 544 544 545 545 546 546 547 -== 2. 5Downlink Payload ==707 +=== 2.3.6 Temperature & Humidity === 548 548 549 -By default, NDDS75 prints the downlink payload to console port. 550 550 710 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 711 + 712 +[[image:image-20220709161741-3.png]] 713 + 714 + 715 +Convert the read byte to decimal and divide it by ten. 716 + 717 + 718 +**Example:** 719 + 720 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 721 + 722 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 723 + 724 + 725 + 726 +== 2.4 Downlink Payload == 727 + 728 + 729 +By default, N95S31B prints the downlink payload to console port. 730 + 551 551 [[image:image-20220709100028-1.png]] 552 552 553 553 ... ... @@ -584,7 +584,7 @@ 584 584 ))) 585 585 586 586 ((( 587 -If payload = 0x04FF, it will reset the DDS75767 +If payload = 0x04FF, it will reset the N95S31B 588 588 ))) 589 589 590 590 ... ... @@ -596,48 +596,75 @@ 596 596 597 597 598 598 599 -== 2. 6LEDIndicator ==779 +== 2.5 Humidity and Temperature alarm function == 600 600 601 601 602 - TheNDDS75hasan internalLED which is toshow thestatusofdifferent state.782 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 603 603 604 604 605 -* 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) 606 -* Then the LED will be on for 1 second means device is boot normally. 607 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 608 -* For each uplink probe, LED will be on for 500ms. 785 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 609 609 610 -((( 611 - 612 -))) 613 613 788 +² When min=0, and max≠0, Alarm higher than max 614 614 790 +² When min≠0, and max=0, Alarm lower than min 615 615 616 - ==2.7FirmwareChangeLog==792 +² When min≠0 and max≠0, Alarm higher than max or lower than min 617 617 618 618 619 -((( 620 -Download URL & Firmware Change log 621 -))) 795 + (% style="color:blue" %)**Example:** 622 622 623 -((( 624 -[[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/]] 625 -))) 797 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 626 626 627 627 628 -((( 629 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 630 -))) 800 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 631 631 802 +² When min=0, and max≠0, Alarm higher than max 632 632 804 +² When min≠0, and max=0, Alarm lower than min 633 633 806 +² When min≠0 and max≠0, Alarm higher than max or lower than min 807 + 808 + 809 +**~ (% style="color:blue" %)Example:(%%)** 810 + 811 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 812 + 813 + 814 + 815 +== 2.6 Set the number of data to be uploaded and the recording time == 816 + 817 + 818 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 819 + 820 +* (% style="color:#037691" %)**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) 821 +* (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 822 + 823 + 824 + 825 + 826 +== 2.7 Read or Clear cached data == 827 + 828 + 829 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 830 + 831 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 832 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 833 + 834 + 835 + 836 +[[image:image-20220908163102-2.png]] 837 + 838 + 839 + 634 634 == 2.8 Battery Analysis == 635 635 842 + 636 636 === 2.8.1 Battery Type === 637 637 638 638 639 639 ((( 640 -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.847 +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. 641 641 ))) 642 642 643 643 ((( ... ... @@ -660,54 +660,35 @@ 660 660 661 661 === 2.8.2 Power consumption Analyze === 662 662 663 -((( 664 -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. 665 -))) 666 666 667 - 668 668 ((( 669 -Instruction to use as below:872 +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. 670 670 ))) 671 671 672 672 ((( 673 - (%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/]]876 + 674 674 ))) 675 675 676 676 677 -((( 678 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 679 -))) 880 +=== 2.8.3 Battery Note === 680 680 681 -* ((( 682 -Product Model 683 -))) 684 -* ((( 685 -Uplink Interval 686 -))) 687 -* ((( 688 -Working Mode 689 -))) 690 690 691 691 ((( 692 - And the Life expectation in difference casewillbe shownon theright.884 +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. 693 693 ))) 694 694 695 -[[image:image-20220709110451-3.png]] 696 696 697 697 889 +=== 2.8.4 Replace the battery === 698 698 699 -=== 2.8.3 Battery Note === 700 700 701 701 ((( 702 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.893 +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. 703 703 ))) 704 704 705 705 706 - 707 -=== 2.8.4 Replace the battery === 708 - 709 709 ((( 710 -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).898 +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). 711 711 ))) 712 712 713 713 ... ... @@ -714,6 +714,7 @@ 714 714 715 715 = 3. Access NB-IoT Module = 716 716 905 + 717 717 ((( 718 718 Users can directly access the AT command set of the NB-IoT module. 719 719 ))) ... ... @@ -720,6 +720,8 @@ 720 720 721 721 ((( 722 722 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/]] 912 + 913 + 723 723 ))) 724 724 725 725 [[image:1657333200519-600.png]] ... ... @@ -728,11 +728,13 @@ 728 728 729 729 = 4. Using the AT Commands = 730 730 922 + 731 731 == 4.1 Access AT Commands == 732 732 733 -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/]] 734 734 926 +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]] 735 735 928 + 736 736 AT+<CMD>? : Help on <CMD> 737 737 738 738 AT+<CMD> : Run <CMD> ... ... @@ -772,7 +772,24 @@ 772 772 773 773 AT+SERVADDR : Server Address 774 774 968 +AT+TR : Get or Set record time 775 775 970 +AT+APN : Get or set the APN 971 + 972 +AT+FBAND : Get or Set whether to automatically modify the frequency band 973 + 974 +AT+DNSCFG : Get or Set DNS Server 975 + 976 +AT+GETSENSORVALUE : Returns the current sensor measurement 977 + 978 +AT+NOUD : Get or Set the number of data to be uploaded 979 + 980 +AT+CDP : Read or Clear cached data 981 + 982 +AT+SHTEMP: Get or Set alarm of temp 983 + 984 +AT+SHHUM: Get or Set alarm of moisture 985 + 776 776 (% style="color:#037691" %)**COAP Management** 777 777 778 778 AT+URI : Resource parameters ... ... @@ -806,6 +806,7 @@ 806 806 807 807 = 5. FAQ = 808 808 1019 + 809 809 == 5.1 How to Upgrade Firmware == 810 810 811 811 ... ... @@ -818,13 +818,18 @@ 818 818 ))) 819 819 820 820 ((( 821 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 1032 + 1033 + 1034 +((( 1035 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 822 822 ))) 1037 +))) 823 823 824 824 825 825 826 826 = 6. Trouble Shooting = 827 827 1043 + 828 828 == 6.1 Connection problem when uploading firmware == 829 829 830 830 ... ... @@ -840,6 +840,7 @@ 840 840 841 841 == 6.2 AT Command input doesn't work == 842 842 1059 + 843 843 ((( 844 844 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. 845 845 ... ... @@ -850,7 +850,7 @@ 850 850 = 7. Order Info = 851 851 852 852 853 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**1070 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 854 854 855 855 856 856 (% class="wikigeneratedid" %) ... ... @@ -865,7 +865,7 @@ 865 865 866 866 (% style="color:#037691" %)**Package Includes**: 867 867 868 -* NS E01DistanceDetectSensorNode x 11085 +* N95S31B NB-IoT Temperature and Humidity Sensor 869 869 * External antenna x 1 870 870 ))) 871 871 ... ... @@ -874,11 +874,10 @@ 874 874 875 875 (% style="color:#037691" %)**Dimension and weight**: 876 876 877 - 878 878 * Device Size: 13.0 x 5 x 4.5 cm 879 879 * Device Weight: 150g 880 -* Package Size / pcs : 1 5x12x 5.5cm881 -* Weight / pcs : 220g1096 +* Package Size / pcs : 14.0 x 8x 5 cm 1097 +* Weight / pcs : 180g 882 882 ))) 883 883 884 884 ((( ... ... @@ -890,5 +890,10 @@ 890 890 891 891 = 9. Support = 892 892 1109 + 893 893 * 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. 894 894 * 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]] 1112 + 1113 + 1114 + 1115 +
- 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-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