Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 3 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N95S31B NB-IoT Temperature & Humidity Sensor User Manual 1 +N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual - Content
-
... ... @@ -19,8 +19,6 @@ 19 19 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 22 -((( 23 - 24 24 25 25 ((( 26 26 The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*. ... ... @@ -39,22 +39,16 @@ 39 39 ))) 40 40 41 41 ((( 42 - 43 -))) 44 - 45 -((( 46 46 ~* make sure you have NB-IoT coverage locally. 47 47 ))) 48 48 49 - 50 -))) 51 51 52 52 [[image:1657348284168-431.png]] 53 53 54 54 55 - 56 56 == 1.2 Features == 57 57 49 + 58 58 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 59 59 * Monitor Temperature & Humidity via SHT31 60 60 * AT Commands to change parameters ... ... @@ -66,8 +66,6 @@ 66 66 * Micro SIM card slot for NB-IoT SIM 67 67 * 8500mAh Battery for long term use 68 68 69 - 70 - 71 71 == 1.3 Specification == 72 72 73 73 ... ... @@ -78,12 +78,12 @@ 78 78 79 79 (% style="color:#037691" %)**NB-IoT Spec:** 80 80 81 -* -B1 @H-FDD: 2100MHz82 -* -B3 @H-FDD: 1800MHz83 -* -B8 @H-FDD: 900MHz84 -* -B5 @H-FDD: 850MHz85 -* -B20 @H-FDD: 800MHz86 -* -B28 @H-FDD: 700MHz71 +* B1 @H-FDD: 2100MHz 72 +* B3 @H-FDD: 1800MHz 73 +* B8 @H-FDD: 900MHz 74 +* B5 @H-FDD: 850MHz 75 +* B20 @H-FDD: 800MHz 76 +* B28 @H-FDD: 700MHz 87 87 88 88 (% style="color:#037691" %)**Battery:** 89 89 ... ... @@ -93,10 +93,9 @@ 93 93 * Max continuously current: 130mA 94 94 * Max boost current: 2A, 1 second 95 95 96 - 97 - 98 98 == 1.4 Applications == 99 99 88 + 100 100 * Smart Buildings & Home Automation 101 101 * Logistics and Supply Chain Management 102 102 * Smart Metering ... ... @@ -110,42 +110,45 @@ 110 110 111 111 == 1.5 Pin Definitions & Switch == 112 112 102 + 113 113 N95S31B use the mother board from NBSN95 which as below. 114 114 105 + 115 115 [[image:image-20220709144723-1.png]] 116 116 117 117 118 118 === 1.5.1 Jumper JP2 === 119 119 111 + 120 120 Power on Device when put this jumper. 121 121 122 122 123 - 124 124 === 1.5.2 BOOT MODE / SW1 === 125 125 117 + 126 126 ((( 127 -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. 119 +**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. 128 128 ))) 129 129 130 130 ((( 131 -2) Flash: work mode, device starts to work and send out console output for further debug 123 +**2) Flash:** work mode, device starts to work and send out console output for further debug 132 132 ))) 133 133 134 134 135 - 136 136 === 1.5.3 Reset Button === 137 137 129 + 138 138 Press to reboot the device. 139 139 140 140 141 - 142 142 === 1.5.4 LED === 143 143 135 + 144 144 It will flash: 145 145 146 -1. When boot the device in flash mode 147 -1. Send an uplink packet 138 +1. When boot the device in flash mode 148 148 140 +2. Send an uplink packet 149 149 150 150 151 151 = 2. Use N95S31B to communicate with IoT Server = ... ... @@ -172,10 +172,8 @@ 172 172 173 173 ))) 174 174 175 - 176 176 == 2.2 Configure the N95S31B == 177 177 178 - 179 179 === 2.2.1 Power On N95S31B === 180 180 181 181 ... ... @@ -182,7 +182,7 @@ 182 182 [[image:image-20220709150546-2.png]] 183 183 184 184 185 -=== 2.2. 1Test Requirement ===175 +=== 2.2.2 Test Requirement === 186 186 187 187 188 188 ((( ... ... @@ -231,9 +231,9 @@ 231 231 [[image:1657350625843-586.png]] 232 232 233 233 234 - 235 235 === 2.2.3 Insert SIM card === 236 236 226 + 237 237 ((( 238 238 Insert the NB-IoT Card get from your provider. 239 239 ))) ... ... @@ -246,26 +246,29 @@ 246 246 [[image:1657351240556-536.png]] 247 247 248 248 249 - 250 250 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 251 251 241 + 252 252 ((( 253 253 ((( 254 254 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. 245 + 246 + 255 255 ))) 256 256 ))) 257 257 258 258 [[image:1657351312545-300.png]] 259 259 260 -**Connection:** 261 261 262 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND253 +(% style="color:blue" %)**Connection:** 263 263 264 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD255 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 265 265 266 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD257 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 267 267 259 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 268 268 261 + 269 269 In the PC, use below serial tool settings: 270 270 271 271 * Baud: (% style="color:green" %)**9600** ... ... @@ -280,17 +280,18 @@ 280 280 281 281 [[image:1657329814315-101.png]] 282 282 276 + 283 283 ((( 284 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]278 +(% 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]]** 285 285 ))) 286 286 287 287 288 - 289 289 === 2.2.5 Use CoAP protocol to uplink data === 290 290 291 -(% 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/]] 292 292 285 +(% 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/]]** 293 293 287 + 294 294 ((( 295 295 **Use below commands:** 296 296 ))) ... ... @@ -299,10 +299,10 @@ 299 299 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 300 300 ))) 301 301 * ((( 302 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 296 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 303 303 ))) 304 304 * ((( 305 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 299 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 306 306 ))) 307 307 308 308 ((( ... ... @@ -321,7 +321,6 @@ 321 321 [[image:1657352185396-303.png]] 322 322 323 323 324 - 325 325 === 2.2.6 Use UDP protocol to uplink data(Default protocol) === 326 326 327 327 ... ... @@ -335,18 +335,18 @@ 335 335 [[image:1657352403317-397.png]] 336 336 337 337 338 - 339 339 === 2.2.7 Use MQTT protocol to uplink data === 340 340 333 + 341 341 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 342 342 343 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 344 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 345 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 346 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 347 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 348 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 349 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 336 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 337 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 338 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 339 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 340 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 341 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ Set the sending topic of MQTT 342 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ Set the subscription topic of MQTT 350 350 351 351 [[image:1657352634421-276.png]] 352 352 ... ... @@ -353,19 +353,19 @@ 353 353 354 354 [[image:1657352645687-385.png]] 355 355 349 + 356 356 ((( 357 357 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. 358 358 ))) 359 359 360 - 361 361 ((( 362 362 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. 363 363 ))) 364 364 365 365 366 - 367 367 === 2.2.8 Use TCP protocol to uplink data === 368 368 361 + 369 369 This feature is supported since firmware version v110 370 370 371 371 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -377,9 +377,9 @@ 377 377 [[image:1657352914475-252.png]] 378 378 379 379 380 - 381 381 === 2.2.9 Change Update Interval === 382 382 375 + 383 383 User can use below command to change the (% style="color:green" %)**uplink interval**. 384 384 385 385 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -388,13 +388,20 @@ 388 388 389 389 ))) 390 390 384 +((( 385 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 386 +))) 391 391 388 +((( 389 +(% 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).** 390 +))) 392 392 392 + 393 393 == 2.3 Uplink Payload == 394 394 395 395 396 396 ((( 397 -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. 397 +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. 398 398 ))) 399 399 400 400 ... ... @@ -403,7 +403,7 @@ 403 403 ))) 404 404 405 405 ((( 406 - (% 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. 406 + (% 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. 407 407 ))) 408 408 409 409 ... ... @@ -426,26 +426,25 @@ 426 426 427 427 (% style="color:red" %) 428 428 1. ((( 429 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 429 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 430 430 ))) 431 431 1. ((( 432 -By default, the device will send an uplink message every 1 hour. 432 +**By default, the device will send an uplink message every 1 hour.** 433 433 434 434 435 - 436 436 437 437 ))) 438 438 439 439 === 2.3.1 Payload Analyze === 440 440 441 - N95S31Buplink payload includesin total21bytes440 +==== 2.3.1.1 Before Firmware v1.2 ==== 442 442 443 443 444 - (% border="1"cellspacing="10"style="background-color:#ffffcc;color:green;width:520px"%)445 - |=(% style="width: 60px;" %)(((446 - **Size(bytes)**447 -)) )|=(% 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**448 -|(% 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" %)(((443 +N95S31B uplink payload includes in total 21 bytes. 444 + 445 +(% border="1" style="background-color:#f2f2f2; width:520px" %) 446 +|=(% 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** 447 +|(% 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" %)((( 449 449 ((( 450 450 Reserve/ Same as NBSN95 CFGMOD=1 451 451 ))) ... ... @@ -453,7 +453,7 @@ 453 453 ((( 454 454 No function here. 455 455 ))) 456 -)))|(% style="width: 77px" %)(((455 +)))|(% style="width:102px" %)((( 457 457 ((( 458 458 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 459 459 ))) ... ... @@ -461,7 +461,7 @@ 461 461 ((( 462 462 By SHT31 463 463 ))) 464 -)))|(% style="width:8 0px" %)(((463 +)))|(% style="width:81px" %)((( 465 465 ((( 466 466 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 467 467 ))) ... ... @@ -472,6 +472,8 @@ 472 472 ))) 473 473 474 474 ((( 474 + 475 + 475 475 ((( 476 476 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 477 477 ))) ... ... @@ -481,29 +481,86 @@ 481 481 [[image:1657354294009-643.png]] 482 482 483 483 484 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:485 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 485 485 486 -* Device ID: 0x724031607457 = 724031607457 487 -* Version: 0x006e=110=1.1.0 487 +**where:** 488 488 489 -* BAT: 0x0ccd = 3277 mV = 3.277V 490 -* Signal: 0x1b = 27 491 -* Model: 0x01 = 1 492 -* 0x00dc000ccc= reserve, ignore in N95S31B 493 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 494 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 489 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 495 495 491 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 492 + 493 +* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 494 + 495 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 496 + 497 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 498 + 499 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 500 + 501 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 502 + 503 +* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 504 + 496 496 ((( 497 497 498 -))) 499 499 500 -((( 501 501 502 502 ))) 503 503 511 +==== 2.3.1.2 Since Firmware v1.2 ==== 504 504 513 + 514 +In this mode, uplink payload includes 91 bytes in total by default. 515 + 516 +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. 517 + 518 +(% border="1" style="background-color:#f2f2f2; width:520px" %) 519 +|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:55px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:35px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**4** 520 +|(% 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 ..... 521 + 522 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 523 + 524 + 525 +[[image:image-20220908154949-1.png]] 526 + 527 + 528 +The payload is ASCII string, representative same HEX: 529 + 530 +**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__ ** 531 + 532 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 533 + 534 +**where:** 535 + 536 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 537 + 538 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 539 + 540 +* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 541 + 542 +* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 543 + 544 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 545 + 546 +* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 547 + 548 +* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 549 + 550 +* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 551 + 552 +* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 553 + 554 +* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 555 + 556 +* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 557 + 558 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 559 + 560 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 561 + 505 505 === 2.3.2 Device ID === 506 506 564 + 507 507 ((( 508 508 By default, the Device ID equal to the last 6 bytes of IMEI. 509 509 ))) ... ... @@ -510,10 +510,12 @@ 510 510 511 511 ((( 512 512 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 571 + 572 + 513 513 ))) 514 514 515 515 ((( 516 -**Example:** 576 +(% style="color:blue" %)**Example:** 517 517 ))) 518 518 519 519 ((( ... ... @@ -521,23 +521,37 @@ 521 521 ))) 522 522 523 523 ((( 524 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 584 +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. 585 + 586 + 525 525 ))) 526 526 589 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 527 527 528 528 592 +By default, the Device ID equal to the last 15 bits of IMEI. 593 + 594 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 595 + 596 + 597 +(% style="color:blue" %)**Example:** 598 + 599 +AT+DEUI=868411056754138 600 + 601 + 529 529 === 2.3.3 Version Info === 530 530 604 + 531 531 ((( 532 532 These bytes include the hardware and software version. 533 533 ))) 534 534 535 535 ((( 536 -Higher byte: Specify hardware version: always 0x00 for N95S31B 610 +**Higher byte:** Specify hardware version: always 0x00 for N95S31B 537 537 ))) 538 538 539 539 ((( 540 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 614 +**Lower byte:** Specify the software version: 0x6E=110, means firmware version 110 541 541 ))) 542 542 543 543 ((( ... ... @@ -552,9 +552,9 @@ 552 552 553 553 ))) 554 554 555 - 556 556 === 2.3.4 Battery Info === 557 557 631 + 558 558 ((( 559 559 Ex1: 0x0B45 = 2885mV 560 560 ))) ... ... @@ -564,9 +564,9 @@ 564 564 ))) 565 565 566 566 567 - 568 568 === 2.3.5 Signal Strength === 569 569 643 + 570 570 ((( 571 571 NB-IoT Network signal Strength. 572 572 ))) ... ... @@ -596,9 +596,9 @@ 596 596 ))) 597 597 598 598 599 - 600 600 === 2.3.6 Temperature & Humidity === 601 601 675 + 602 602 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 603 603 604 604 [[image:image-20220709161741-3.png]] ... ... @@ -614,14 +614,17 @@ 614 614 Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 615 615 616 616 617 - 618 618 == 2.4 Downlink Payload == 619 619 693 + 620 620 By default, N95S31B prints the downlink payload to console port. 621 621 622 -[[image:image-20220709100028-1.png]] 696 +(% border="1" style="background-color:#f2f2f2; width:520px" %) 697 +|(% style="background-color:#d9e2f3; color:#0070c0; width:200px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:170px" %)**Downlink payload size(bytes)** 698 +|(% style="width:204px" %)TDC(Transmit Time Interval)|(% style="width:80px" %)Any|(% style="width:94px" %)01|(% style="width:150px" %)4 699 +|(% style="width:204px" %)RESET|(% style="width:80px" %)Any|(% style="width:94px" %)04|(% style="width:150px" %)2 700 +|(% style="width:204px" %)INTMOD|(% style="width:80px" %)Any|(% style="width:94px" %)06|(% style="width:150px" %)4 623 623 624 - 625 625 ((( 626 626 (% style="color:blue" %)**Examples:** 627 627 ))) ... ... @@ -666,69 +666,76 @@ 666 666 ))) 667 667 668 668 746 +== 2.5 Humidity and Temperature alarm function == 669 669 670 -== 2.5 Battery Analysis == 671 671 672 - ===2.5.1BatteryType===749 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 673 673 674 674 675 -((( 676 -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. 677 -))) 752 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 678 678 679 -((( 680 -The battery is designed to last for several years depends on the actually use environment and update interval. 681 -))) 682 682 683 -((( 684 -The battery related documents as below: 685 -))) 755 +² When min=0, and max≠0, Alarm higher than max 686 686 687 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 688 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 689 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 757 +² When min≠0, and max=0, Alarm lower than min 690 690 691 -((( 692 -[[image:image-20220709101450-2.png]] 693 -))) 759 +² When min≠0 and max≠0, Alarm higher than max or lower than min 694 694 695 695 762 + (% style="color:blue" %)**Example:** 696 696 697 - ===2.5.2PowerconsumptionAnalyze===764 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 698 698 699 -((( 700 -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. 701 -))) 702 702 703 -((( 704 - 705 -))) 767 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 706 706 769 +² When min=0, and max≠0, Alarm higher than max 707 707 708 - ===2.5.3BatteryNote===771 +² When min≠0, and max=0, Alarm lower than min 709 709 710 -((( 711 -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. 712 -))) 773 +² When min≠0 and max≠0, Alarm higher than max or lower than min 713 713 714 714 776 +**~ (% style="color:blue" %)Example:(%%)** 715 715 716 - ===2.5.4Replacethebattery===778 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 717 717 718 718 719 -((( 720 -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. 721 -))) 781 +== 2.6 Set the number of data to be uploaded and the recording time == 722 722 723 723 724 -((( 725 -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). 726 -))) 784 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 727 727 786 +* (% 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) 787 +* (% 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. 728 728 789 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 729 729 791 +[[image:image-20221009001045-1.png||height="726" width="1009"]] 792 + 793 + 794 +== 2.7 Read or Clear cached data == 795 + 796 + 797 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 798 + 799 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 800 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 801 + 802 +[[image:image-20220908163102-2.png]] 803 + 804 + 805 +== 2.8 Battery & Power Consumption == 806 + 807 + 808 +N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 809 + 810 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 811 + 812 + 730 730 = 3. Access NB-IoT Module = 731 731 815 + 732 732 ((( 733 733 Users can directly access the AT command set of the NB-IoT module. 734 734 ))) ... ... @@ -735,19 +735,21 @@ 735 735 736 736 ((( 737 737 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/]] 822 + 823 + 738 738 ))) 739 739 740 740 [[image:1657333200519-600.png]] 741 741 742 742 743 - 744 744 = 4. Using the AT Commands = 745 745 746 746 == 4.1 Access AT Commands == 747 747 748 -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/]] 749 749 834 +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]] 750 750 836 + 751 751 AT+<CMD>? : Help on <CMD> 752 752 753 753 AT+<CMD> : Run <CMD> ... ... @@ -787,7 +787,24 @@ 787 787 788 788 AT+SERVADDR : Server Address 789 789 876 +AT+TR : Get or Set record time 790 790 878 +AT+APN : Get or set the APN 879 + 880 +AT+FBAND : Get or Set whether to automatically modify the frequency band 881 + 882 +AT+DNSCFG : Get or Set DNS Server 883 + 884 +AT+GETSENSORVALUE : Returns the current sensor measurement 885 + 886 +AT+NOUD : Get or Set the number of data to be uploaded 887 + 888 +AT+CDP : Read or Clear cached data 889 + 890 +AT+SHTEMP: Get or Set alarm of temp 891 + 892 +AT+SHHUM: Get or Set alarm of moisture 893 + 791 791 (% style="color:#037691" %)**COAP Management** 792 792 793 793 AT+URI : Resource parameters ... ... @@ -818,7 +818,6 @@ 818 818 AT+PWORD : Serial Access Password 819 819 820 820 821 - 822 822 = 5. FAQ = 823 823 824 824 == 5.1 How to Upgrade Firmware == ... ... @@ -833,15 +833,12 @@ 833 833 ))) 834 834 835 835 ((( 836 - 938 +Firmware Download:[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]] 837 837 838 -((( 839 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 940 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 840 840 ))) 841 -))) 842 842 843 843 844 - 845 845 = 6. Trouble Shooting = 846 846 847 847 == 6.1 Connection problem when uploading firmware == ... ... @@ -851,14 +851,10 @@ 851 851 **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]] 852 852 ))) 853 853 854 -(% class="wikigeneratedid" %) 855 -((( 856 - 857 -))) 858 858 859 - 860 860 == 6.2 AT Command input doesn't work == 861 861 956 + 862 862 ((( 863 863 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. 864 864 ... ... @@ -865,7 +865,12 @@ 865 865 866 866 ))) 867 867 963 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 868 868 965 + 966 +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]]//**. 967 + 968 + 869 869 = 7. Order Info = 870 870 871 871 ... ... @@ -872,11 +872,6 @@ 872 872 Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 873 873 874 874 875 -(% class="wikigeneratedid" %) 876 -((( 877 - 878 -))) 879 - 880 880 = 8. Packing Info = 881 881 882 882 ((( ... ... @@ -899,14 +899,12 @@ 899 899 * Weight / pcs : 180g 900 900 ))) 901 901 902 -((( 903 - 904 904 905 905 906 - 907 -))) 908 - 909 909 = 9. Support = 910 910 1001 + 911 911 * 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. 1003 + 912 912 * 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]] 1005 +
- 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
- image-20221009001045-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content