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, 0 added, 4 removed)
Details
- Page properties
-
- Content
-
... ... @@ -19,6 +19,8 @@ 19 19 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 22 +((( 23 + 22 22 23 23 ((( 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*. ... ... @@ -37,16 +37,22 @@ 37 37 ))) 38 38 39 39 ((( 42 + 43 +))) 44 + 45 +((( 40 40 ~* make sure you have NB-IoT coverage locally. 41 41 ))) 42 42 49 + 50 +))) 43 43 44 44 [[image:1657348284168-431.png]] 45 45 46 46 55 + 47 47 == 1.2 Features == 48 48 49 - 50 50 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 51 51 * Monitor Temperature & Humidity via SHT31 52 52 * AT Commands to change parameters ... ... @@ -69,12 +69,12 @@ 69 69 70 70 (% style="color:#037691" %)**NB-IoT Spec:** 71 71 72 -* B1 @H-FDD: 2100MHz 73 -* B3 @H-FDD: 1800MHz 74 -* B8 @H-FDD: 900MHz 75 -* B5 @H-FDD: 850MHz 76 -* B20 @H-FDD: 800MHz 77 -* B28 @H-FDD: 700MHz 80 +* - B1 @H-FDD: 2100MHz 81 +* - B3 @H-FDD: 1800MHz 82 +* - B8 @H-FDD: 900MHz 83 +* - B5 @H-FDD: 850MHz 84 +* - B20 @H-FDD: 800MHz 85 +* - B28 @H-FDD: 700MHz 78 78 79 79 (% style="color:#037691" %)**Battery:** 80 80 ... ... @@ -87,7 +87,6 @@ 87 87 88 88 == 1.4 Applications == 89 89 90 - 91 91 * Smart Buildings & Home Automation 92 92 * Logistics and Supply Chain Management 93 93 * Smart Metering ... ... @@ -101,47 +101,43 @@ 101 101 102 102 == 1.5 Pin Definitions & Switch == 103 103 104 - 105 105 N95S31B use the mother board from NBSN95 which as below. 106 106 107 - 108 108 [[image:image-20220709144723-1.png]] 109 109 110 110 111 111 === 1.5.1 Jumper JP2 === 112 112 113 - 114 114 Power on Device when put this jumper. 115 115 116 116 121 + 117 117 === 1.5.2 BOOT MODE / SW1 === 118 118 119 - 120 120 ((( 121 - **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.125 +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. 122 122 ))) 123 123 124 124 ((( 125 - **2) Flash:**work mode, device starts to work and send out console output for further debug129 +2) Flash: work mode, device starts to work and send out console output for further debug 126 126 ))) 127 127 128 128 133 + 129 129 === 1.5.3 Reset Button === 130 130 131 - 132 132 Press to reboot the device. 133 133 134 134 139 + 135 135 === 1.5.4 LED === 136 136 137 - 138 138 It will flash: 139 139 140 -1. When boot the device in flash mode 144 +1. When boot the device in flash mode 145 +1. Send an uplink packet 141 141 142 -2. Send an uplink packet 143 143 144 - 145 145 = 2. Use N95S31B to communicate with IoT Server = 146 146 147 147 == 2.1 How it works == ... ... @@ -160,14 +160,16 @@ 160 160 161 161 ))) 162 162 163 -[[image:16575 20100595-569.png]]166 +[[image:1657350248151-650.png]] 164 164 165 165 ((( 166 166 167 167 ))) 168 168 172 + 169 169 == 2.2 Configure the N95S31B == 170 170 175 + 171 171 === 2.2.1 Power On N95S31B === 172 172 173 173 ... ... @@ -174,7 +174,7 @@ 174 174 [[image:image-20220709150546-2.png]] 175 175 176 176 177 -=== 2.2. 2Test Requirement ===182 +=== 2.2.1 Test Requirement === 178 178 179 179 180 180 ((( ... ... @@ -223,9 +223,9 @@ 223 223 [[image:1657350625843-586.png]] 224 224 225 225 231 + 226 226 === 2.2.3 Insert SIM card === 227 227 228 - 229 229 ((( 230 230 Insert the NB-IoT Card get from your provider. 231 231 ))) ... ... @@ -238,29 +238,26 @@ 238 238 [[image:1657351240556-536.png]] 239 239 240 240 246 + 241 241 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 242 242 243 - 244 244 ((( 245 245 ((( 246 246 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. 247 - 248 - 249 249 ))) 250 250 ))) 251 251 252 252 [[image:1657351312545-300.png]] 253 253 257 +**Connection:** 254 254 255 -(% style="color: blue" %)**Connection:**259 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 256 256 257 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**261 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 258 258 259 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**263 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 260 260 261 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 262 262 263 - 264 264 In the PC, use below serial tool settings: 265 265 266 266 * Baud: (% style="color:green" %)**9600** ... ... @@ -275,18 +275,17 @@ 275 275 276 276 [[image:1657329814315-101.png]] 277 277 278 - 279 279 ((( 280 -(% 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]]**281 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] 281 281 ))) 282 282 283 283 285 + 284 284 === 2.2.5 Use CoAP protocol to uplink data === 285 285 288 +(% 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/]] 286 286 287 -(% 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/]]** 288 288 289 - 290 290 ((( 291 291 **Use below commands:** 292 292 ))) ... ... @@ -295,10 +295,10 @@ 295 295 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 296 296 ))) 297 297 * ((( 298 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** 299 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 299 299 ))) 300 300 * ((( 301 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ 302 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 302 302 ))) 303 303 304 304 ((( ... ... @@ -317,6 +317,7 @@ 317 317 [[image:1657352185396-303.png]] 318 318 319 319 321 + 320 320 === 2.2.6 Use UDP protocol to uplink data(Default protocol) === 321 321 322 322 ... ... @@ -330,18 +330,18 @@ 330 330 [[image:1657352403317-397.png]] 331 331 332 332 335 + 333 333 === 2.2.7 Use MQTT protocol to uplink data === 334 334 335 - 336 336 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 337 337 338 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 339 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 340 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 341 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 342 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 343 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ 344 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ 340 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 341 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 342 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 343 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 344 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 345 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 346 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 345 345 346 346 [[image:1657352634421-276.png]] 347 347 ... ... @@ -348,19 +348,19 @@ 348 348 349 349 [[image:1657352645687-385.png]] 350 350 351 - 352 352 ((( 353 353 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. 354 354 ))) 355 355 357 + 356 356 ((( 357 357 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. 358 358 ))) 359 359 360 360 363 + 361 361 === 2.2.8 Use TCP protocol to uplink data === 362 362 363 - 364 364 This feature is supported since firmware version v110 365 365 366 366 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -372,9 +372,9 @@ 372 372 [[image:1657352914475-252.png]] 373 373 374 374 377 + 375 375 === 2.2.9 Change Update Interval === 376 376 377 - 378 378 User can use below command to change the (% style="color:green" %)**uplink interval**. 379 379 380 380 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -383,20 +383,13 @@ 383 383 384 384 ))) 385 385 386 -((( 387 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 388 -))) 389 389 390 -((( 391 -(% 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).** 392 -))) 393 393 394 - 395 395 == 2.3 Uplink Payload == 396 396 397 397 398 398 ((( 399 -N95 S31Bhas different working modesfor the connections of different typesof sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.394 +NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes. 400 400 ))) 401 401 402 402 ... ... @@ -405,7 +405,7 @@ 405 405 ))) 406 406 407 407 ((( 408 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/ S31Bto work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.403 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 409 409 ))) 410 410 411 411 ... ... @@ -428,26 +428,23 @@ 428 428 429 429 (% style="color:red" %) 430 430 1. ((( 431 - **All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**426 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 432 432 ))) 433 433 1. ((( 434 -**By default, the device will send an uplink message every 1 hour.** 435 - 436 - 437 - 429 +By default, the device will send an uplink message every 1 hour. 438 438 ))) 439 439 432 + 440 440 === 2.3.1 Payload Analyze === 441 441 442 -==== 2.3.1.1 Before Firmware v1.2 ==== 443 - 444 - 445 445 N95S31B uplink payload includes in total 21 bytes 446 446 447 447 448 -(% border="1" style="background-color:#f2f2f2; width:520px" %) 449 -|=(% style="width: 50px;background-color:#D9E2F3" %)**Size(bytes)**|=(% style="width: 45px;background-color:#D9E2F3" %)**6**|=(% style="width: 25px;background-color:#D9E2F3" %)2|=(% style="width: 25px;background-color:#D9E2F3" %)**2**|=(% style="width: 65px;background-color:#D9E2F3" %)**1**|=(% style="width: 50px;background-color:#D9E2F3" %)1|=(% style="width: 120px;background-color:#D9E2F3" %)5|=(% style="width: 70px;background-color:#D9E2F3" %)**2**|=(% style="width: 70px;background-color:#D9E2F3" %)**2** 450 -|(% 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:162px" %)((( 438 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 439 +|=(% style="width: 60px;" %)((( 440 +**Size(bytes)** 441 +)))|=(% 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** 442 +|(% 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" %)((( 451 451 ((( 452 452 Reserve/ Same as NBSN95 CFGMOD=1 453 453 ))) ... ... @@ -455,7 +455,7 @@ 455 455 ((( 456 456 No function here. 457 457 ))) 458 -)))|(% style="width: 102px" %)(((450 +)))|(% style="width:77px" %)((( 459 459 ((( 460 460 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 461 461 ))) ... ... @@ -463,7 +463,7 @@ 463 463 ((( 464 464 By SHT31 465 465 ))) 466 -)))|(% style="width:8 1px" %)(((458 +)))|(% style="width:80px" %)((( 467 467 ((( 468 468 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 469 469 ))) ... ... @@ -474,8 +474,6 @@ 474 474 ))) 475 475 476 476 ((( 477 - 478 - 479 479 ((( 480 480 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 481 481 ))) ... ... @@ -485,88 +485,29 @@ 485 485 [[image:1657354294009-643.png]] 486 486 487 487 488 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457**478 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 489 489 490 -**where:** 480 +* Device ID: 0x724031607457 = 724031607457 481 +* Version: 0x006e=110=1.1.0 491 491 492 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 483 +* BAT: 0x0ccd = 3277 mV = 3.277V 484 +* Signal: 0x1b = 27 485 +* Model: 0x01 = 1 486 +* 0x00dc000ccc= reserve, ignore in N95S31B 487 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 488 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 493 493 494 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 495 - 496 -* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 497 - 498 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 499 - 500 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 501 - 502 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 503 - 504 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 505 - 506 -* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 507 - 508 508 ((( 509 509 492 +))) 510 510 494 +((( 511 511 512 512 ))) 513 513 514 -==== 2.3.1.2 Since Firmware v1.2 ==== 515 515 516 - 517 -In this mode, uplink payload includes 91 bytes in total by default. 518 - 519 -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. 520 - 521 - 522 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 523 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:30px" %)**1**|(% style="width:20px" %)**1**|(% style="width:55px" %)**2**|(% style="width:35px" %)**1**|(% style="width:20px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:30px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:35px" %)**4** 524 -|=(% 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 ..... 525 - 526 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 527 - 528 - 529 -[[image:image-20220908154949-1.png]] 530 - 531 - 532 -The payload is ASCII string, representative same HEX: 533 - 534 -**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ ** 535 - 536 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 537 - 538 -**where:** 539 - 540 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 541 - 542 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 543 - 544 -* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 545 - 546 -* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 547 - 548 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 549 - 550 -* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 551 - 552 -* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 553 - 554 -* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 555 - 556 -* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 557 - 558 -* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 559 - 560 -* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 561 - 562 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 563 - 564 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 565 - 566 - 567 567 === 2.3.2 Device ID === 568 568 569 - 570 570 ((( 571 571 By default, the Device ID equal to the last 6 bytes of IMEI. 572 572 ))) ... ... @@ -573,12 +573,10 @@ 573 573 574 574 ((( 575 575 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 576 - 577 - 578 578 ))) 579 579 580 580 ((( 581 - (% style="color:blue" %)**Example:**510 +**Example:** 582 582 ))) 583 583 584 584 ((( ... ... @@ -586,37 +586,23 @@ 586 586 ))) 587 587 588 588 ((( 589 -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. 590 - 591 - 518 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 592 592 ))) 593 593 594 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 595 595 596 596 597 -By default, the Device ID equal to the last 15 bits of IMEI. 598 - 599 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 600 - 601 - 602 -(% style="color:blue" %)**Example:** 603 - 604 -AT+DEUI=868411056754138 605 - 606 - 607 607 === 2.3.3 Version Info === 608 608 609 - 610 610 ((( 611 611 These bytes include the hardware and software version. 612 612 ))) 613 613 614 614 ((( 615 - **Higher byte:**Specify hardware version: always 0x00 for N95S31B530 +Higher byte: Specify hardware version: always 0x00 for N95S31B 616 616 ))) 617 617 618 618 ((( 619 - **Lower byte:**Specify the software version: 0x6E=110, means firmware version 110534 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 620 620 ))) 621 621 622 622 ((( ... ... @@ -631,9 +631,9 @@ 631 631 632 632 ))) 633 633 549 + 634 634 === 2.3.4 Battery Info === 635 635 636 - 637 637 ((( 638 638 Ex1: 0x0B45 = 2885mV 639 639 ))) ... ... @@ -643,9 +643,9 @@ 643 643 ))) 644 644 645 645 561 + 646 646 === 2.3.5 Signal Strength === 647 647 648 - 649 649 ((( 650 650 NB-IoT Network signal Strength. 651 651 ))) ... ... @@ -675,9 +675,9 @@ 675 675 ))) 676 676 677 677 593 + 678 678 === 2.3.6 Temperature & Humidity === 679 679 680 - 681 681 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 682 682 683 683 [[image:image-20220709161741-3.png]] ... ... @@ -693,11 +693,11 @@ 693 693 Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 694 694 695 695 611 + 696 696 == 2.4 Downlink Payload == 697 697 614 +By default, NDDS75 prints the downlink payload to console port. 698 698 699 -By default, N95S31B prints the downlink payload to console port. 700 - 701 701 [[image:image-20220709100028-1.png]] 702 702 703 703 ... ... @@ -734,7 +734,7 @@ 734 734 ))) 735 735 736 736 ((( 737 -If payload = 0x04FF, it will reset the 95S31B652 +If payload = 0x04FF, it will reset the NDDS75 738 738 ))) 739 739 740 740 ... ... @@ -745,76 +745,69 @@ 745 745 ))) 746 746 747 747 748 -== 2.5 Humidity and Temperature alarm function == 749 749 664 +== 2.5 Battery Analysis == 750 750 751 - **~(%style="color:blue"%)➢ ATCommand:(%%)**666 +=== 2.5.1 Battery Type === 752 752 753 753 754 -(% style="color:#037691" %)**AT+ SHHUM=min,max** 669 +((( 670 +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. 671 +))) 755 755 673 +((( 674 +The battery is designed to last for several years depends on the actually use environment and update interval. 675 +))) 756 756 757 -² When min=0, and max≠0, Alarm higher than max 677 +((( 678 +The battery related documents as below: 679 +))) 758 758 759 -² When min≠0, and max=0, Alarm lower than min 681 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 682 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 683 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 760 760 761 -² When min≠0 and max≠0, Alarm higher than max or lower than min 685 +((( 686 +[[image:image-20220709101450-2.png]] 687 +))) 762 762 763 763 764 - (% style="color:blue" %)**Example:** 765 765 766 - AT+ SHHUM=50,80~/~/ Alarmwhenhumiditylowerthan 50.691 +=== 2.5.2 Power consumption Analyze === 767 767 693 +((( 694 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 695 +))) 768 768 769 -(% style="color:#037691" %)**AT+ SHTEMP=min,max** 697 +((( 698 + 699 +))) 770 770 771 -² When min=0, and max≠0, Alarm higher than max 772 772 773 - ²Whenmin≠0,and max=0, Alarmlowerthan min702 +=== 2.5.3 Battery Note === 774 774 775 -² When min≠0 and max≠0, Alarm higher than max or lower than min 704 +((( 705 +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. 706 +))) 776 776 777 777 778 -**~ (% style="color:blue" %)Example:(%%)** 779 779 780 - AT+ SHTEMP=20,30~/~/ Alarm whentemperaturelowerthan 20.710 +=== 2.5.4 Replace the battery === 781 781 782 782 783 -== 2.6 Set the number of data to be uploaded and the recording time == 713 +((( 714 +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. 715 +))) 784 784 785 785 786 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 718 +((( 719 +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). 720 +))) 787 787 788 -* (% 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) 789 -* (% 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. 790 790 791 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 792 792 793 -[[image:image-20221009001045-1.png||height="726" width="1009"]] 794 - 795 - 796 -== 2.7 Read or Clear cached data == 797 - 798 - 799 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 800 - 801 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 802 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 803 - 804 -[[image:image-20220908163102-2.png]] 805 - 806 - 807 -== 2.8 Battery & Power Consumption == 808 - 809 - 810 -N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 811 - 812 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 813 - 814 - 815 815 = 3. Access NB-IoT Module = 816 816 817 - 818 818 ((( 819 819 Users can directly access the AT command set of the NB-IoT module. 820 820 ))) ... ... @@ -821,21 +821,19 @@ 821 821 822 822 ((( 823 823 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/]] 824 - 825 - 826 826 ))) 827 827 828 828 [[image:1657333200519-600.png]] 829 829 830 830 737 + 831 831 = 4. Using the AT Commands = 832 832 833 833 == 4.1 Access AT Commands == 834 834 742 +See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]] 835 835 836 -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]] 837 837 838 - 839 839 AT+<CMD>? : Help on <CMD> 840 840 841 841 AT+<CMD> : Run <CMD> ... ... @@ -875,24 +875,7 @@ 875 875 876 876 AT+SERVADDR : Server Address 877 877 878 -AT+TR : Get or Set record time 879 879 880 -AT+APN : Get or set the APN 881 - 882 -AT+FBAND : Get or Set whether to automatically modify the frequency band 883 - 884 -AT+DNSCFG : Get or Set DNS Server 885 - 886 -AT+GETSENSORVALUE : Returns the current sensor measurement 887 - 888 -AT+NOUD : Get or Set the number of data to be uploaded 889 - 890 -AT+CDP : Read or Clear cached data 891 - 892 -AT+SHTEMP: Get or Set alarm of temp 893 - 894 -AT+SHHUM: Get or Set alarm of moisture 895 - 896 896 (% style="color:#037691" %)**COAP Management** 897 897 898 898 AT+URI : Resource parameters ... ... @@ -923,6 +923,7 @@ 923 923 AT+PWORD : Serial Access Password 924 924 925 925 815 + 926 926 = 5. FAQ = 927 927 928 928 == 5.1 How to Upgrade Firmware == ... ... @@ -937,12 +937,15 @@ 937 937 ))) 938 938 939 939 ((( 940 - FirmwareDownload:[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]]830 + 941 941 942 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 832 +((( 833 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 943 943 ))) 835 +))) 944 944 945 945 838 + 946 946 = 6. Trouble Shooting = 947 947 948 948 == 6.1 Connection problem when uploading firmware == ... ... @@ -952,10 +952,14 @@ 952 952 **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]] 953 953 ))) 954 954 848 +(% class="wikigeneratedid" %) 849 +((( 850 + 851 +))) 955 955 853 + 956 956 == 6.2 AT Command input doesn't work == 957 957 958 - 959 959 ((( 960 960 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. 961 961 ... ... @@ -962,12 +962,7 @@ 962 962 963 963 ))) 964 964 965 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 966 966 967 - 968 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 969 - 970 - 971 971 = 7. Order Info = 972 972 973 973 ... ... @@ -974,6 +974,11 @@ 974 974 Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 975 975 976 976 869 +(% class="wikigeneratedid" %) 870 +((( 871 + 872 +))) 873 + 977 977 = 8. Packing Info = 978 978 979 979 ((( ... ... @@ -996,13 +996,14 @@ 996 996 * Weight / pcs : 180g 997 997 ))) 998 998 896 +((( 897 + 999 999 1000 1000 900 + 901 +))) 902 + 1001 1001 = 9. Support = 1002 1002 1003 - 1004 1004 * 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. 1005 - 1006 1006 * 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]] 1007 - 1008 -
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220908154949-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -58.5 KB - Content
- image-20220908163102-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -29.7 KB - Content
- image-20221009001045-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content