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, 4 added, 0 removed)
Details
- Page properties
-
- 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,9 +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 - 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -77,17 +77,15 @@ 77 77 * Supply Voltage: 2.1v ~~ 3.6v 78 78 * Operating Temperature: -40 ~~ 85°C 79 79 80 - 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 -* -B1 @H-FDD: 2100MHz84 -* -B3 @H-FDD: 1800MHz85 -* -B8 @H-FDD: 900MHz86 -* -B5 @H-FDD: 850MHz87 -* -B20 @H-FDD: 800MHz88 -* -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 89 89 90 - 91 91 (% style="color:#037691" %)**Battery:** 92 92 93 93 * Li/SOCI2 un-chargeable battery ... ... @@ -96,11 +96,9 @@ 96 96 * Max continuously current: 130mA 97 97 * Max boost current: 2A, 1 second 98 98 99 - 100 - 101 - 102 102 == 1.4 Applications == 103 103 88 + 104 104 * Smart Buildings & Home Automation 105 105 * Logistics and Supply Chain Management 106 106 * Smart Metering ... ... @@ -112,47 +112,49 @@ 112 112 113 113 114 114 115 -== 1.5 Pin Definitions == 100 +== 1.5 Pin Definitions & Switch == 116 116 102 + 117 117 N95S31B use the mother board from NBSN95 which as below. 118 118 105 + 119 119 [[image:image-20220709144723-1.png]] 120 120 121 121 122 122 === 1.5.1 Jumper JP2 === 123 123 111 + 124 124 Power on Device when put this jumper. 125 125 126 126 127 - 128 128 === 1.5.2 BOOT MODE / SW1 === 129 129 117 + 130 130 ((( 131 -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. 132 132 ))) 133 133 134 134 ((( 135 -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 136 136 ))) 137 137 138 138 139 - 140 140 === 1.5.3 Reset Button === 141 141 129 + 142 142 Press to reboot the device. 143 143 144 144 145 - 146 146 === 1.5.4 LED === 147 147 135 + 148 148 It will flash: 149 149 150 -1. When boot the device in flash mode 151 -1. Send an uplink packet 138 +1. When boot the device in flash mode 152 152 140 +2. Send an uplink packet 153 153 154 154 155 - 156 156 = 2. Use N95S31B to communicate with IoT Server = 157 157 158 158 == 2.1 How it works == ... ... @@ -171,16 +171,14 @@ 171 171 172 172 ))) 173 173 174 -[[image:1657 350248151-650.png]]161 +[[image:1657520100595-569.png]] 175 175 176 176 ((( 177 177 178 178 ))) 179 179 180 - 181 181 == 2.2 Configure the N95S31B == 182 182 183 - 184 184 === 2.2.1 Power On N95S31B === 185 185 186 186 ... ... @@ -187,7 +187,7 @@ 187 187 [[image:image-20220709150546-2.png]] 188 188 189 189 190 -=== 2.2. 1Test Requirement ===175 +=== 2.2.2 Test Requirement === 191 191 192 192 193 193 ((( ... ... @@ -236,9 +236,9 @@ 236 236 [[image:1657350625843-586.png]] 237 237 238 238 239 - 240 240 === 2.2.3 Insert SIM card === 241 241 226 + 242 242 ((( 243 243 Insert the NB-IoT Card get from your provider. 244 244 ))) ... ... @@ -251,26 +251,29 @@ 251 251 [[image:1657351240556-536.png]] 252 252 253 253 254 - 255 255 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 256 256 241 + 257 257 ((( 258 258 ((( 259 259 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 + 260 260 ))) 261 261 ))) 262 262 263 263 [[image:1657351312545-300.png]] 264 264 265 -**Connection:** 266 266 267 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND253 +(% style="color:blue" %)**Connection:** 268 268 269 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD255 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 270 270 271 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD257 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 272 272 259 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 273 273 261 + 274 274 In the PC, use below serial tool settings: 275 275 276 276 * Baud: (% style="color:green" %)**9600** ... ... @@ -285,17 +285,18 @@ 285 285 286 286 [[image:1657329814315-101.png]] 287 287 276 + 288 288 ((( 289 -(% 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]]** 290 290 ))) 291 291 292 292 293 - 294 294 === 2.2.5 Use CoAP protocol to uplink data === 295 295 296 -(% 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/]] 297 297 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/]]** 298 298 287 + 299 299 ((( 300 300 **Use below commands:** 301 301 ))) ... ... @@ -304,10 +304,10 @@ 304 304 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 305 305 ))) 306 306 * ((( 307 -(% 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 308 308 ))) 309 309 * ((( 310 -(% 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 311 311 ))) 312 312 313 313 ((( ... ... @@ -326,7 +326,6 @@ 326 326 [[image:1657352185396-303.png]] 327 327 328 328 329 - 330 330 === 2.2.6 Use UDP protocol to uplink data(Default protocol) === 331 331 332 332 ... ... @@ -340,18 +340,18 @@ 340 340 [[image:1657352403317-397.png]] 341 341 342 342 343 - 344 344 === 2.2.7 Use MQTT protocol to uplink data === 345 345 333 + 346 346 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 347 347 348 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 349 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 350 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 351 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 352 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 353 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 354 -* (% 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 355 355 356 356 [[image:1657352634421-276.png]] 357 357 ... ... @@ -358,19 +358,19 @@ 358 358 359 359 [[image:1657352645687-385.png]] 360 360 349 + 361 361 ((( 362 362 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. 363 363 ))) 364 364 365 - 366 366 ((( 367 367 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. 368 368 ))) 369 369 370 370 371 - 372 372 === 2.2.8 Use TCP protocol to uplink data === 373 373 361 + 374 374 This feature is supported since firmware version v110 375 375 376 376 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -382,9 +382,9 @@ 382 382 [[image:1657352914475-252.png]] 383 383 384 384 385 - 386 386 === 2.2.9 Change Update Interval === 387 387 375 + 388 388 User can use below command to change the (% style="color:green" %)**uplink interval**. 389 389 390 390 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -393,43 +393,71 @@ 393 393 394 394 ))) 395 395 384 +((( 385 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 386 +))) 396 396 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 +))) 397 397 392 + 398 398 == 2.3 Uplink Payload == 399 399 400 400 401 -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. 396 +((( 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 +))) 402 402 403 403 401 +((( 404 404 For example: 403 +))) 405 405 406 - (% 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. 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. 407 +))) 407 407 408 408 410 +((( 409 409 The uplink payloads are composed in ASCII String. For example: 412 +))) 410 410 414 +((( 411 411 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 416 +))) 412 412 418 +((( 413 413 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 420 +))) 414 414 415 415 423 +((( 416 416 (% style="color:red" %)**NOTE:** 425 +))) 417 417 418 418 (% style="color:red" %) 419 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 420 -1. By default, the device will send an uplink message every 1 hour. 428 +1. ((( 429 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 430 +))) 431 +1. ((( 432 +**By default, the device will send an uplink message every 1 hour.** 421 421 422 422 435 + 436 +))) 437 + 423 423 === 2.3.1 Payload Analyze === 424 424 440 +==== 2.3.1.1 Before Firmware v1.2 ==== 441 + 442 + 425 425 N95S31B uplink payload includes in total 21 bytes 426 426 427 427 428 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 429 -|=(% style="width: 60px;" %)((( 430 -**Size(bytes)** 431 -)))|=(% 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** 432 -|(% 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" %)((( 446 +(% border="1" style="background-color:#f2f2f2; width:520px" %) 447 +|=(% 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** 448 +|(% 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" %)((( 433 433 ((( 434 434 Reserve/ Same as NBSN95 CFGMOD=1 435 435 ))) ... ... @@ -437,7 +437,7 @@ 437 437 ((( 438 438 No function here. 439 439 ))) 440 -)))|(% style="width: 77px" %)(((456 +)))|(% style="width:102px" %)((( 441 441 ((( 442 442 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 443 443 ))) ... ... @@ -445,7 +445,7 @@ 445 445 ((( 446 446 By SHT31 447 447 ))) 448 -)))|(% style="width:8 0px" %)(((464 +)))|(% style="width:81px" %)((( 449 449 ((( 450 450 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 451 451 ))) ... ... @@ -456,6 +456,8 @@ 456 456 ))) 457 457 458 458 ((( 475 + 476 + 459 459 ((( 460 460 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 461 461 ))) ... ... @@ -465,29 +465,87 @@ 465 465 [[image:1657354294009-643.png]] 466 466 467 467 468 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:486 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 469 469 470 -* Device ID: 0x724031607457 = 724031607457 471 -* Version: 0x006e=110=1.1.0 488 +**where:** 472 472 473 -* BAT: 0x0ccd = 3277 mV = 3.277V 474 -* Signal: 0x1b = 27 475 -* Model: 0x01 = 1 476 -* 0x00dc000ccc= reserve, ignore in N95S31B 477 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 478 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 490 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 479 479 492 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 493 + 494 +* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 495 + 496 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 497 + 498 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 499 + 500 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 501 + 502 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 503 + 504 +* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 505 + 480 480 ((( 481 481 482 -))) 483 483 484 -((( 485 485 486 486 ))) 487 487 512 +==== 2.3.1.2 Since Firmware v1.2 ==== 488 488 514 + 515 +In this mode, uplink payload includes 91 bytes in total by default. 516 + 517 +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. 518 + 519 + 520 +(% border="1" style="background-color:#f2f2f2; width:520px" %) 521 +|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**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:35px" %)**4** 522 +|=(% 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 ..... 523 + 524 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 525 + 526 + 527 +[[image:image-20220908154949-1.png]] 528 + 529 + 530 +The payload is ASCII string, representative same HEX: 531 + 532 +**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__ ** 533 + 534 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 535 + 536 +**where:** 537 + 538 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 539 + 540 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 541 + 542 +* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 543 + 544 +* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 545 + 546 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 547 + 548 +* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 549 + 550 +* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 551 + 552 +* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 553 + 554 +* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 555 + 556 +* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 557 + 558 +* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 559 + 560 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 561 + 562 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 563 + 489 489 === 2.3.2 Device ID === 490 490 566 + 491 491 ((( 492 492 By default, the Device ID equal to the last 6 bytes of IMEI. 493 493 ))) ... ... @@ -494,10 +494,12 @@ 494 494 495 495 ((( 496 496 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 573 + 574 + 497 497 ))) 498 498 499 499 ((( 500 -**Example:** 578 +(% style="color:blue" %)**Example:** 501 501 ))) 502 502 503 503 ((( ... ... @@ -505,30 +505,54 @@ 505 505 ))) 506 506 507 507 ((( 508 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 586 +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. 587 + 588 + 509 509 ))) 510 510 591 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 511 511 512 512 594 +By default, the Device ID equal to the last 15 bits of IMEI. 595 + 596 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 597 + 598 + 599 +(% style="color:blue" %)**Example:** 600 + 601 +AT+DEUI=868411056754138 602 + 603 + 513 513 === 2.3.3 Version Info === 514 514 515 515 607 +((( 516 516 These bytes include the hardware and software version. 609 +))) 517 517 518 -Higher byte: Specify hardware version: always 0x00 for N95S31B 611 +((( 612 +**Higher byte:** Specify hardware version: always 0x00 for N95S31B 613 +))) 519 519 520 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 615 +((( 616 +**Lower byte:** Specify the software version: 0x6E=110, means firmware version 110 617 +))) 521 521 619 +((( 620 + 621 +))) 522 522 623 +((( 523 523 For example: 0x00 6E: this device is N95S31B with firmware version 110. 625 +))) 524 524 525 525 ((( 526 526 527 527 ))) 528 528 529 - 530 530 === 2.3.4 Battery Info === 531 531 633 + 532 532 ((( 533 533 Ex1: 0x0B45 = 2885mV 534 534 ))) ... ... @@ -538,9 +538,9 @@ 538 538 ))) 539 539 540 540 541 - 542 542 === 2.3.5 Signal Strength === 543 543 645 + 544 544 ((( 545 545 NB-IoT Network signal Strength. 546 546 ))) ... ... @@ -570,9 +570,9 @@ 570 570 ))) 571 571 572 572 573 - 574 574 === 2.3.6 Temperature & Humidity === 575 575 677 + 576 576 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 577 577 578 578 [[image:image-20220709161741-3.png]] ... ... @@ -588,11 +588,17 @@ 588 588 Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 589 589 590 590 591 - 592 592 == 2.4 Downlink Payload == 593 593 594 -By default, NDDS75 prints the downlink payload to console port. 595 595 696 +By default, N95S31B prints the downlink payload to console port. 697 + 698 +(% border="1" style="background-color:#f2f2f2; width:531.818px" %) 699 +|(% style="background-color:#d9e2f3; color:#0070c0; width:204px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:80px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:94px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:150px" %)**Downlink payload size(bytes)** 700 +|(% style="width:204px" %)TDC(Transmit Time Interval)|(% style="width:80px" %)Any|(% style="width:94px" %)01|(% style="width:150px" %)4 701 +|(% style="width:204px" %)RESET|(% style="width:80px" %)Any|(% style="width:94px" %)04|(% style="width:150px" %)2 702 +|(% style="width:204px" %)INTMOD|(% style="width:80px" %)Any|(% style="width:94px" %)06|(% style="width:150px" %)4 703 + 596 596 [[image:image-20220709100028-1.png]] 597 597 598 598 ... ... @@ -629,7 +629,7 @@ 629 629 ))) 630 630 631 631 ((( 632 -If payload = 0x04FF, it will reset the DDS75740 +If payload = 0x04FF, it will reset the N95S31B 633 633 ))) 634 634 635 635 ... ... @@ -640,69 +640,76 @@ 640 640 ))) 641 641 642 642 751 +== 2.5 Humidity and Temperature alarm function == 643 643 644 -== 2.5 Battery Analysis == 645 645 646 - ===2.5.1BatteryType===754 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 647 647 648 648 649 -((( 650 -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. 651 -))) 757 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 652 652 653 -((( 654 -The battery is designed to last for several years depends on the actually use environment and update interval. 655 -))) 656 656 657 -((( 658 -The battery related documents as below: 659 -))) 760 +² When min=0, and max≠0, Alarm higher than max 660 660 661 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 662 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 663 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 762 +² When min≠0, and max=0, Alarm lower than min 664 664 665 -((( 666 -[[image:image-20220709101450-2.png]] 667 -))) 764 +² When min≠0 and max≠0, Alarm higher than max or lower than min 668 668 669 669 767 + (% style="color:blue" %)**Example:** 670 670 671 - ===2.5.2PowerconsumptionAnalyze===769 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 672 672 673 -((( 674 -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. 675 -))) 676 676 677 -((( 678 - 679 -))) 772 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 680 680 774 +² When min=0, and max≠0, Alarm higher than max 681 681 682 - ===2.5.3BatteryNote===776 +² When min≠0, and max=0, Alarm lower than min 683 683 684 -((( 685 -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. 686 -))) 778 +² When min≠0 and max≠0, Alarm higher than max or lower than min 687 687 688 688 781 +**~ (% style="color:blue" %)Example:(%%)** 689 689 690 - ===2.5.4Replacethebattery===783 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 691 691 692 692 693 -((( 694 -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. 695 -))) 786 +== 2.6 Set the number of data to be uploaded and the recording time == 696 696 697 697 698 -((( 699 -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). 700 -))) 789 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 701 701 791 +* (% 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) 792 +* (% 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. 702 702 794 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 703 703 796 +[[image:image-20221009001045-1.png||height="726" width="1009"]] 797 + 798 + 799 +== 2.7 Read or Clear cached data == 800 + 801 + 802 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 803 + 804 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 805 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 806 + 807 +[[image:image-20220908163102-2.png]] 808 + 809 + 810 +== 2.8 Battery & Power Consumption == 811 + 812 + 813 +N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 814 + 815 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 816 + 817 + 704 704 = 3. Access NB-IoT Module = 705 705 820 + 706 706 ((( 707 707 Users can directly access the AT command set of the NB-IoT module. 708 708 ))) ... ... @@ -709,19 +709,21 @@ 709 709 710 710 ((( 711 711 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/]] 827 + 828 + 712 712 ))) 713 713 714 714 [[image:1657333200519-600.png]] 715 715 716 716 717 - 718 718 = 4. Using the AT Commands = 719 719 720 720 == 4.1 Access AT Commands == 721 721 722 -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/]] 723 723 839 +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]] 724 724 841 + 725 725 AT+<CMD>? : Help on <CMD> 726 726 727 727 AT+<CMD> : Run <CMD> ... ... @@ -761,7 +761,24 @@ 761 761 762 762 AT+SERVADDR : Server Address 763 763 881 +AT+TR : Get or Set record time 764 764 883 +AT+APN : Get or set the APN 884 + 885 +AT+FBAND : Get or Set whether to automatically modify the frequency band 886 + 887 +AT+DNSCFG : Get or Set DNS Server 888 + 889 +AT+GETSENSORVALUE : Returns the current sensor measurement 890 + 891 +AT+NOUD : Get or Set the number of data to be uploaded 892 + 893 +AT+CDP : Read or Clear cached data 894 + 895 +AT+SHTEMP: Get or Set alarm of temp 896 + 897 +AT+SHHUM: Get or Set alarm of moisture 898 + 765 765 (% style="color:#037691" %)**COAP Management** 766 766 767 767 AT+URI : Resource parameters ... ... @@ -792,7 +792,6 @@ 792 792 AT+PWORD : Serial Access Password 793 793 794 794 795 - 796 796 = 5. FAQ = 797 797 798 798 == 5.1 How to Upgrade Firmware == ... ... @@ -807,13 +807,12 @@ 807 807 ))) 808 808 809 809 ((( 810 - 943 +Firmware Download:[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]] 811 811 812 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 945 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 813 813 ))) 814 814 815 815 816 - 817 817 = 6. Trouble Shooting = 818 818 819 819 == 6.1 Connection problem when uploading firmware == ... ... @@ -823,14 +823,10 @@ 823 823 **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]] 824 824 ))) 825 825 826 -(% class="wikigeneratedid" %) 827 -((( 828 - 829 -))) 830 830 831 - 832 832 == 6.2 AT Command input doesn't work == 833 833 961 + 834 834 ((( 835 835 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. 836 836 ... ... @@ -837,7 +837,12 @@ 837 837 838 838 ))) 839 839 968 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 840 840 970 + 971 +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]]//**. 972 + 973 + 841 841 = 7. Order Info = 842 842 843 843 ... ... @@ -844,11 +844,6 @@ 844 844 Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 845 845 846 846 847 -(% class="wikigeneratedid" %) 848 -((( 849 - 850 -))) 851 - 852 852 = 8. Packing Info = 853 853 854 854 ((( ... ... @@ -871,14 +871,13 @@ 871 871 * Weight / pcs : 180g 872 872 ))) 873 873 874 -((( 875 - 876 876 877 877 878 - 879 -))) 880 - 881 881 = 9. Support = 882 882 1006 + 883 883 * 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. 1008 + 884 884 * 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]] 1010 + 1011 +
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 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
- image-20221009001045-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content