Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Change comment:
Uploaded new attachment "image-20220908163102-2.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 13 added, 0 removed)
- 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-20220709161741-3.png
- image-20220908154949-1.png
- image-20220908163102-2.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.David - 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 ))) ... ... @@ -55,6 +55,7 @@ 55 55 56 56 57 57 73 + 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -63,6 +63,8 @@ 63 63 * Supply Voltage: 2.1v ~~ 3.6v 64 64 * Operating Temperature: -40 ~~ 85°C 65 65 82 + 83 + 66 66 (% style="color:#037691" %)**NB-IoT Spec:** 67 67 68 68 * - B1 @H-FDD: 2100MHz ... ... @@ -72,9 +72,10 @@ 72 72 * - B20 @H-FDD: 800MHz 73 73 * - B28 @H-FDD: 700MHz 74 74 75 -(% style="color:#037691" %)**Battery:** 76 76 77 77 95 +(% style="color:#037691" %)**Battery:** 96 + 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -83,8 +83,10 @@ 83 83 84 84 85 85 105 + 86 86 == 1.4 Applications == 87 87 108 + 88 88 * Smart Buildings & Home Automation 89 89 * Logistics and Supply Chain Management 90 90 * Smart Metering ... ... @@ -96,15 +96,20 @@ 96 96 97 97 98 98 99 -== 1.5 Pin Definitions == 100 100 121 +== 1.5 Pin Definitions & Switch == 122 + 123 + 101 101 N95S31B use the mother board from NBSN95 which as below. 102 102 126 + 103 103 [[image:image-20220709144723-1.png]] 104 104 105 105 130 + 106 106 === 1.5.1 Jumper JP2 === 107 107 133 + 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 140 + 141 +((( 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. 143 +))) 115 115 145 +((( 116 116 2) Flash: work mode, device starts to work and send out console output for further debug 147 +))) 117 117 118 118 119 119 120 120 === 1.5.3 Reset Button === 121 121 153 + 122 122 Press to reboot the device. 123 123 124 124 ... ... @@ -125,6 +125,7 @@ 125 125 126 126 === 1.5.4 LED === 127 127 160 + 128 128 It will flash: 129 129 130 130 1. When boot the device in flash mode ... ... @@ -135,6 +135,7 @@ 135 135 136 136 = 2. Use N95S31B to communicate with IoT Server = 137 137 171 + 138 138 == 2.1 How it works == 139 139 140 140 ... ... @@ -151,7 +151,7 @@ 151 151 152 152 ))) 153 153 154 -[[image:1657 350248151-650.png]]188 +[[image:1657520100595-569.png]] 155 155 156 156 ((( 157 157 ... ... @@ -167,27 +167,49 @@ 167 167 [[image:image-20220709150546-2.png]] 168 168 169 169 204 + 170 170 === 2.2.1 Test Requirement === 171 171 172 172 208 +((( 173 173 To use N95S31B in your city, make sure meet below requirements: 210 +))) 174 174 175 -* Your local operator has already distributed a NB-IoT Network there. 176 -* The local NB-IoT network used the band that N95S31B supports. 177 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 212 +* ((( 213 +Your local operator has already distributed a NB-IoT Network there. 214 +))) 215 +* ((( 216 +The local NB-IoT network used the band that N95S31B supports. 217 +))) 218 +* ((( 219 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 220 +))) 178 178 179 - 222 +((( 180 180 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 224 +))) 181 181 226 +((( 182 182 N95S31B supports different communication protocol such as : 228 +))) 183 183 184 184 ((( 185 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 186 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 187 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 188 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 231 +* ((( 232 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 233 +))) 234 +* ((( 235 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 236 +))) 237 +* ((( 238 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 239 +))) 240 +* ((( 241 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 242 +))) 189 189 244 +((( 190 190 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. 246 +))) 191 191 192 192 193 193 ))) ... ... @@ -198,6 +198,7 @@ 198 198 199 199 === 2.2.3 Insert SIM card === 200 200 257 + 201 201 ((( 202 202 Insert the NB-IoT Card get from your provider. 203 203 ))) ... ... @@ -211,16 +211,20 @@ 211 211 212 212 213 213 214 -=== 2.2. 3DDS75 to configure it ===271 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 215 215 273 + 216 216 ((( 217 217 ((( 218 -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. 276 +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. 277 + 278 + 219 219 ))) 220 220 ))) 221 221 222 -[[image: image-20220709092052-2.png]]282 +[[image:1657351312545-300.png]] 223 223 284 + 224 224 **Connection:** 225 225 226 226 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -239,22 +239,24 @@ 239 239 * Flow Control: (% style="color:green" %)**None** 240 240 241 241 ((( 242 -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.303 +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. 243 243 ))) 244 244 245 245 [[image:1657329814315-101.png]] 246 246 308 + 247 247 ((( 248 -(% 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/]]310 +(% 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]]** 249 249 ))) 250 250 251 251 252 252 253 -=== 2.2. 4315 +=== 2.2.5 Use CoAP protocol to uplink data === 254 254 255 -(% 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/]] 256 256 318 +(% 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/]]** 257 257 320 + 258 258 ((( 259 259 **Use below commands:** 260 260 ))) ... ... @@ -270,10 +270,12 @@ 270 270 ))) 271 271 272 272 ((( 336 + 337 + 273 273 For parameter description, please refer to AT command set 274 274 ))) 275 275 276 -[[image:16573 30452568-615.png]]341 +[[image:1657352146020-183.png]] 277 277 278 278 279 279 ((( ... ... @@ -280,11 +280,11 @@ 280 280 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. 281 281 ))) 282 282 283 -[[image:16573 30472797-498.png]]348 +[[image:1657352185396-303.png]] 284 284 285 285 286 286 287 -=== 2.2. 5352 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 288 288 289 289 290 290 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -291,109 +291,117 @@ 291 291 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 292 292 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 293 293 294 -[[image:1657330501006-241.png]] 295 295 296 296 297 -[[image:16573 30533775-472.png]]361 +[[image:1657352391268-297.png]] 298 298 299 299 364 +[[image:1657352403317-397.png]] 300 300 301 -=== 2.2.6 Use MQTT protocol to uplink data === 302 302 303 303 368 +=== 2.2.7 Use MQTT protocol to uplink data === 369 + 370 + 371 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 372 + 304 304 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 305 305 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 306 306 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 307 307 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 308 308 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 309 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT310 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT378 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 379 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 311 311 312 -[[image:1657249978444-674.png]] 313 313 314 314 315 -[[image:16573 30723006-866.png]]383 +[[image:1657352634421-276.png]] 316 316 317 317 386 +[[image:1657352645687-385.png]] 387 + 388 + 318 318 ((( 319 - MQTT protocolhas amuch higherpowerconsumptioncomparevsUDP / CoAPprotocol.Pleasecheckthe power analyzedocument and adjustthe uplinkperiodto asuitable interval.390 +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. 320 320 ))) 321 321 322 322 394 +((( 395 +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. 396 +))) 323 323 324 -=== 2.2.7 Use TCP protocol to uplink data === 325 325 326 326 400 +=== 2.2.8 Use TCP protocol to uplink data === 401 + 402 + 403 +This feature is supported since firmware version v110 404 + 327 327 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 328 328 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 329 329 330 -[[image:image-20220709093918-1.png]] 331 331 332 332 333 -[[image: image-20220709093918-2.png]]410 +[[image:1657352898400-901.png]] 334 334 335 335 413 +[[image:1657352914475-252.png]] 336 336 337 -=== 2.2.8 Change Update Interval === 338 338 416 + 417 +=== 2.2.9 Change Update Interval === 418 + 419 + 339 339 User can use below command to change the (% style="color:green" %)**uplink interval**. 340 340 341 341 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 342 342 343 343 ((( 344 - (%style="color:red" %)**NOTE:**425 + 345 345 ))) 346 346 347 -((( 348 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 349 -))) 350 350 351 351 352 - 353 353 == 2.3 Uplink Payload == 354 354 355 -In this mode, uplink payload includes in total 14 bytes 356 356 433 +((( 434 +N95S31B 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. 435 +))) 357 357 358 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 359 -|=(% style="width: 60px;" %)((( 360 -**Size(bytes)** 361 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 362 -|(% 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"]] 363 363 364 364 ((( 365 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.439 +For example: 366 366 ))) 367 367 442 +((( 443 + (% 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. 444 +))) 368 368 369 -[[image:1657331036973-987.png]] 370 370 371 371 ((( 372 -The payload is ASCIIstring,representative sameHEX:448 +The uplink payloads are composed in ASCII String. For example: 373 373 ))) 374 374 375 375 ((( 376 -0 x72403155615900640c6c19029200where:452 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 377 377 ))) 378 378 379 - *(((380 - DeviceID:0x724031556159=724031556159455 +((( 456 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 381 381 ))) 382 -* ((( 383 -Version: 0x0064=100=1.0.0 458 + 459 + 460 +((( 461 +(% style="color:red" %)**NOTE:** 384 384 ))) 385 385 386 -* ((( 387 -BAT: 0x0c6c = 3180 mV = 3.180V 464 +(% style="color:red" %) 465 +1. ((( 466 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 388 388 ))) 389 -* ((( 390 -Signal: 0x19 = 25 391 -))) 392 -* ((( 393 -Distance: 0x0292= 658 mm 394 -))) 395 -* ((( 396 -Interrupt: 0x00 = 0 468 +1. ((( 469 +**By default, the device will send an uplink message every 1 hour.** 397 397 398 398 399 399 ... ... @@ -400,105 +400,113 @@ 400 400 401 401 ))) 402 402 403 -== 2. 4PayloadExplanation and SensorInterface==476 +=== 2.3.1 Payload Analyze === 404 404 405 405 406 - === 2.4.1DeviceID===479 +N95S31B uplink payload includes in total 21 bytes 407 407 481 + 482 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 483 +|=(% style="width: 60px;" %)((( 484 +**Size(bytes)** 485 +)))|=(% 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** 486 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 408 408 ((( 409 - By default, theDeviceID equal to thelast6bytes of IMEI.488 +Reserve/ Same as NBSN95 CFGMOD=1 410 410 ))) 411 411 412 412 ((( 413 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID492 +No function here. 414 414 ))) 415 - 494 +)))|(% style="width:77px" %)((( 416 416 ((( 417 - **Example:**496 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 418 418 ))) 419 419 420 420 ((( 421 - AT+DEUI=A84041F15612500 +By SHT31 422 422 ))) 423 - 502 +)))|(% style="width:80px" %)((( 424 424 ((( 425 - The Device ID is storednane-erasearea, Upgradethe firmwareor run **AT+FDR** won'terase Device ID.504 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 426 426 ))) 427 427 428 - 429 - 430 -=== 2.4.2 Version Info === 431 - 432 432 ((( 433 - Specifythe software version: 0x64=100, means firmware version 1.00.508 +By SHT31 434 434 ))) 510 +))) 435 435 436 436 ((( 437 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 513 + 514 + 515 +((( 516 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 438 438 ))) 518 +))) 439 439 440 440 521 +[[image:1657354294009-643.png]] 441 441 442 -=== 2.4.3 Battery Info === 443 443 524 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 525 + 526 +* Device ID: 0x724031607457 = 724031607457 527 +* Version: 0x006e=110=1.1.0 528 + 529 +* BAT: 0x0ccd = 3277 mV = 3.277V 530 +* Signal: 0x1b = 27 531 +* Model: 0x01 = 1 532 +* 0x00dc000ccc= reserve, ignore in N95S31B 533 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 534 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 535 + 444 444 ((( 445 - Ex1:0x0B45 = 2885mV537 + 446 446 ))) 447 447 448 448 ((( 449 - Ex2:0x0B49 = 2889mV541 + 450 450 ))) 451 451 452 452 545 +=== 2.3.2 Device ID === 453 453 454 -=== 2.4.4 Signal Strength === 455 455 456 456 ((( 457 - NB-IoTNetworksignalStrength.549 +By default, the Device ID equal to the last 6 bytes of IMEI. 458 458 ))) 459 459 460 460 ((( 461 - **Ex1:0x1d=29**553 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 462 462 ))) 463 463 464 464 ((( 465 - (% style="color:blue" %)**0**(%%) -113dBmorless557 +**Example:** 466 466 ))) 467 467 468 468 ((( 469 - (% style="color:blue" %)**1**(%%) -111dBm561 +AT+DEUI=A84041F15612 470 470 ))) 471 471 472 472 ((( 473 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm565 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 474 474 ))) 475 475 476 -((( 477 -(% style="color:blue" %)**31** (%%) -51dBm or greater 478 -))) 479 479 480 -((( 481 -(% style="color:blue" %)**99** (%%) Not known or not detectable 482 -))) 483 483 570 +=== 2.3.3 Version Info === 484 484 485 485 486 -=== 2.4.5 Distance === 487 - 488 -Get the distance. Flat object range 280mm - 7500mm. 489 - 490 490 ((( 491 - Forexample,if the datayou getfrom theregisteris **__0x0B 0x05__**, the distancebetweenthesensorand the measuredobject is574 +These bytes include the hardware and software version. 492 492 ))) 493 493 494 494 ((( 495 -((( 496 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 578 +Higher byte: Specify hardware version: always 0x00 for N95S31B 497 497 ))) 498 -))) 499 499 500 500 ((( 501 - 582 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 502 502 ))) 503 503 504 504 ((( ... ... @@ -505,65 +505,85 @@ 505 505 506 506 ))) 507 507 508 -=== 2.4.6 Digital Interrupt === 509 - 510 510 ((( 511 - Digital Interruptrefers topin (% style="color:blue"%)**GPIO_EXTI**(%%),andtherearedifferent triggermethods. When thereisa trigger, theNDDS75 will send a packetto theserver.590 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 512 512 ))) 513 513 514 514 ((( 515 - Thecommand is:594 + 516 516 ))) 517 517 597 + 598 +=== 2.3.4 Battery Info === 599 + 600 + 518 518 ((( 519 - (% 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]])**.**602 +Ex1: 0x0B45 = 2885mV 520 520 ))) 521 521 522 - 523 523 ((( 524 - Thelowerfourbits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.606 +Ex2: 0x0B49 = 2889mV 525 525 ))) 526 526 527 527 610 + 611 +=== 2.3.5 Signal Strength === 612 + 613 + 528 528 ((( 529 - Example:615 +NB-IoT Network signal Strength. 530 530 ))) 531 531 532 532 ((( 533 - 0x(00):Normaluplinkpacket.619 +**Ex1: 0x1d = 29** 534 534 ))) 535 535 536 536 ((( 537 - 0x(01):InterruptUplinkPacket.623 +(% style="color:blue" %)**0**(%%) -113dBm or less 538 538 ))) 539 539 540 - 541 - 542 -=== 2.4.7 +5V Output === 543 - 544 544 ((( 545 - NDDS75willenable +5Voutputbeforeallsamplinganddisablethe+5vafterall sampling.627 +(% style="color:blue" %)**1**(%%) -111dBm 546 546 ))) 547 547 548 - 549 549 ((( 550 - The5V output timean be controlledbyAT Command.631 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 551 551 ))) 552 552 553 553 ((( 554 -(% style="color:blue" %)** AT+5VT=1000**635 +(% style="color:blue" %)**31** (%%) -51dBm or greater 555 555 ))) 556 556 557 557 ((( 558 - Meansset5V valid timetohave 1000ms. Sothereal5V outputwillactuallyhave1000ms+samplingtime for othersensors.639 +(% style="color:blue" %)**99** (%%) Not known or not detectable 559 559 ))) 560 560 561 561 562 562 563 -== 2. 5Downlink Payload ==644 +=== 2.3.6 Temperature & Humidity === 564 564 565 -By default, NDDS75 prints the downlink payload to console port. 566 566 647 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 648 + 649 +[[image:image-20220709161741-3.png]] 650 + 651 + 652 +Convert the read byte to decimal and divide it by ten. 653 + 654 + 655 +**Example:** 656 + 657 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 658 + 659 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 660 + 661 + 662 + 663 +== 2.4 Downlink Payload == 664 + 665 + 666 +By default, N95S31B prints the downlink payload to console port. 667 + 567 567 [[image:image-20220709100028-1.png]] 568 568 569 569 ... ... @@ -600,7 +600,7 @@ 600 600 ))) 601 601 602 602 ((( 603 -If payload = 0x04FF, it will reset the DDS75704 +If payload = 0x04FF, it will reset the N95S31B 604 604 ))) 605 605 606 606 ... ... @@ -612,51 +612,17 @@ 612 612 613 613 614 614 615 -== 2. 6LED Indicator ==716 +== 2.5 Battery Analysis == 616 616 617 617 618 - TheNDDS75has an internal LED which isto show thestatus of differentstate.719 +=== 2.5.1 Battery Type === 619 619 620 620 621 -* 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) 622 -* Then the LED will be on for 1 second means device is boot normally. 623 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 624 -* For each uplink probe, LED will be on for 500ms. 625 - 626 626 ((( 627 - 723 +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. 628 628 ))) 629 629 630 - 631 - 632 -== 2.7 Firmware Change Log == 633 - 634 - 635 635 ((( 636 -Download URL & Firmware Change log 637 -))) 638 - 639 -((( 640 -[[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/]] 641 -))) 642 - 643 - 644 -((( 645 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 646 -))) 647 - 648 - 649 - 650 -== 2.8 Battery Analysis == 651 - 652 -=== 2.8.1 Battery Type === 653 - 654 - 655 -((( 656 -The NDDS75 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. 657 -))) 658 - 659 -((( 660 660 The battery is designed to last for several years depends on the actually use environment and update interval. 661 661 ))) 662 662 ... ... @@ -674,56 +674,37 @@ 674 674 675 675 676 676 677 -=== 2. 8.2 Power consumption Analyze ===744 +=== 2.5.2 Power consumption Analyze === 678 678 679 -((( 680 -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. 681 -))) 682 682 683 - 684 684 ((( 685 -Instruction to use as below:748 +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. 686 686 ))) 687 687 688 688 ((( 689 - (%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/]]752 + 690 690 ))) 691 691 692 692 693 -((( 694 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 695 -))) 756 +=== 2.5.3 Battery Note === 696 696 697 -* ((( 698 -Product Model 699 -))) 700 -* ((( 701 -Uplink Interval 702 -))) 703 -* ((( 704 -Working Mode 705 -))) 706 706 707 707 ((( 708 - And the Life expectation in difference casewillbe shownon theright.760 +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. 709 709 ))) 710 710 711 -[[image:image-20220709110451-3.png]] 712 712 713 713 765 +=== 2.5.4 Replace the battery === 714 714 715 -=== 2.8.3 Battery Note === 716 716 717 717 ((( 718 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.769 +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. 719 719 ))) 720 720 721 721 722 - 723 -=== 2.8.4 Replace the battery === 724 - 725 725 ((( 726 -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).774 +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). 727 727 ))) 728 728 729 729 ... ... @@ -730,6 +730,7 @@ 730 730 731 731 = 3. Access NB-IoT Module = 732 732 781 + 733 733 ((( 734 734 Users can directly access the AT command set of the NB-IoT module. 735 735 ))) ... ... @@ -736,6 +736,8 @@ 736 736 737 737 ((( 738 738 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/]] 788 + 789 + 739 739 ))) 740 740 741 741 [[image:1657333200519-600.png]] ... ... @@ -744,11 +744,13 @@ 744 744 745 745 = 4. Using the AT Commands = 746 746 798 + 747 747 == 4.1 Access AT Commands == 748 748 749 -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/]] 750 750 802 +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]] 751 751 804 + 752 752 AT+<CMD>? : Help on <CMD> 753 753 754 754 AT+<CMD> : Run <CMD> ... ... @@ -822,6 +822,7 @@ 822 822 823 823 = 5. FAQ = 824 824 878 + 825 825 == 5.1 How to Upgrade Firmware == 826 826 827 827 ... ... @@ -834,13 +834,18 @@ 834 834 ))) 835 835 836 836 ((( 837 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 891 + 892 + 893 +((( 894 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 838 838 ))) 896 +))) 839 839 840 840 841 841 842 842 = 6. Trouble Shooting = 843 843 902 + 844 844 == 6.1 Connection problem when uploading firmware == 845 845 846 846 ... ... @@ -856,6 +856,7 @@ 856 856 857 857 == 6.2 AT Command input doesn't work == 858 858 918 + 859 859 ((( 860 860 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. 861 861 ... ... @@ -866,7 +866,7 @@ 866 866 = 7. Order Info = 867 867 868 868 869 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**929 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 870 870 871 871 872 872 (% class="wikigeneratedid" %) ... ... @@ -881,7 +881,7 @@ 881 881 882 882 (% style="color:#037691" %)**Package Includes**: 883 883 884 -* NS E01DistanceDetectSensorNode x 1944 +* N95S31B NB-IoT Temperature and Humidity Sensor 885 885 * External antenna x 1 886 886 ))) 887 887 ... ... @@ -890,11 +890,10 @@ 890 890 891 891 (% style="color:#037691" %)**Dimension and weight**: 892 892 893 - 894 894 * Device Size: 13.0 x 5 x 4.5 cm 895 895 * Device Weight: 150g 896 -* Package Size / pcs : 1 5x12x 5.5cm897 -* Weight / pcs : 220g955 +* Package Size / pcs : 14.0 x 8x 5 cm 956 +* Weight / pcs : 180g 898 898 ))) 899 899 900 900 ((( ... ... @@ -906,5 +906,9 @@ 906 906 907 907 = 9. Support = 908 908 968 + 909 909 * 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. 910 910 * 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]] 971 + 972 + 973 +
- 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-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