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
-
... ... @@ -9,7 +9,6 @@ 9 9 10 10 **Table of Contents:** 11 11 12 -{{toc/}} 13 13 14 14 15 15 ... ... @@ -19,34 +19,29 @@ 19 19 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 22 - 23 23 ((( 22 + 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*. 25 -))) 26 26 27 -((( 28 28 The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use. 29 -))) 30 30 31 -((( 32 32 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 33 -))) 34 34 35 -((( 36 36 N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report). 37 -))) 38 38 39 - (((32 + 40 40 ~* make sure you have NB-IoT coverage locally. 34 + 35 + 41 41 ))) 42 42 43 - 44 44 [[image:1657348284168-431.png]] 45 45 46 46 41 + 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 ... ... @@ -60,6 +60,7 @@ 60 60 61 61 62 62 57 + 63 63 == 1.3 Specification == 64 64 65 65 ... ... @@ -70,15 +70,16 @@ 70 70 71 71 (% style="color:#037691" %)**NB-IoT Spec:** 72 72 73 -* B1 @H-FDD: 2100MHz 74 -* B3 @H-FDD: 1800MHz 75 -* B8 @H-FDD: 900MHz 76 -* B5 @H-FDD: 850MHz 77 -* B20 @H-FDD: 800MHz 78 -* B28 @H-FDD: 700MHz 68 +* - B1 @H-FDD: 2100MHz 69 +* - B3 @H-FDD: 1800MHz 70 +* - B8 @H-FDD: 900MHz 71 +* - B5 @H-FDD: 850MHz 72 +* - B20 @H-FDD: 800MHz 73 +* - B28 @H-FDD: 700MHz 79 79 80 80 (% style="color:#037691" %)**Battery:** 81 81 77 + 82 82 * Li/SOCI2 un-chargeable battery 83 83 * Capacity: 8500mAh 84 84 * Self Discharge: <1% / Year @ 25°C ... ... @@ -87,9 +87,9 @@ 87 87 88 88 89 89 86 + 90 90 == 1.4 Applications == 91 91 92 - 93 93 * Smart Buildings & Home Automation 94 94 * Logistics and Supply Chain Management 95 95 * Smart Metering ... ... @@ -101,49 +101,41 @@ 101 101 102 102 103 103 104 -== 1.5 Pin Definitions & Switch==100 +== 1.5 Pin Definitions == 105 105 106 - 107 107 N95S31B use the mother board from NBSN95 which as below. 108 108 109 - 110 110 [[image:image-20220709144723-1.png]] 111 111 112 112 113 113 === 1.5.1 Jumper JP2 === 114 114 115 - 116 116 Power on Device when put this jumper. 117 117 118 118 112 + 119 119 === 1.5.2 BOOT MODE / SW1 === 120 120 115 +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. 121 121 122 -((( 123 -**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. 124 -))) 117 +2) Flash: work mode, device starts to work and send out console output for further debug 125 125 126 -((( 127 -**2) Flash:** work mode, device starts to work and send out console output for further debug 128 -))) 129 129 130 130 131 131 === 1.5.3 Reset Button === 132 132 133 - 134 134 Press to reboot the device. 135 135 136 136 126 + 137 137 === 1.5.4 LED === 138 138 139 - 140 140 It will flash: 141 141 142 -1. When boot the device in flash mode 131 +1. When boot the device in flash mode 132 +1. Send an uplink packet 143 143 144 -2. Send an uplink packet 145 145 146 - 147 147 = 2. Use N95S31B to communicate with IoT Server = 148 148 149 149 == 2.1 How it works == ... ... @@ -162,14 +162,16 @@ 162 162 163 163 ))) 164 164 165 -[[image:16575 20100595-569.png]]153 +[[image:1657350248151-650.png]] 166 166 167 167 ((( 168 168 169 169 ))) 170 170 159 + 171 171 == 2.2 Configure the N95S31B == 172 172 162 + 173 173 === 2.2.1 Power On N95S31B === 174 174 175 175 ... ... @@ -176,48 +176,26 @@ 176 176 [[image:image-20220709150546-2.png]] 177 177 178 178 179 -=== 2.2. 2Test Requirement ===169 +=== 2.2.1 Test Requirement === 180 180 181 181 182 -((( 183 183 To use N95S31B in your city, make sure meet below requirements: 184 -))) 185 185 186 -* ((( 187 -Your local operator has already distributed a NB-IoT Network there. 188 -))) 189 -* ((( 190 -The local NB-IoT network used the band that N95S31B supports. 191 -))) 192 -* ((( 193 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 194 -))) 174 +* Your local operator has already distributed a NB-IoT Network there. 175 +* The local NB-IoT network used the band that N95S31B supports. 176 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 195 195 196 -((( 197 197 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 198 -))) 199 199 200 -((( 201 201 N95S31B supports different communication protocol such as : 202 -))) 203 203 204 204 ((( 205 -* ((( 206 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 207 -))) 208 -* ((( 209 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 210 -))) 211 -* ((( 212 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 213 -))) 214 -* ((( 215 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 216 -))) 183 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 184 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 185 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 186 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 217 217 218 -((( 219 219 We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server. 220 -))) 221 221 222 222 223 223 ))) ... ... @@ -225,9 +225,9 @@ 225 225 [[image:1657350625843-586.png]] 226 226 227 227 196 + 228 228 === 2.2.3 Insert SIM card === 229 229 230 - 231 231 ((( 232 232 Insert the NB-IoT Card get from your provider. 233 233 ))) ... ... @@ -240,29 +240,26 @@ 240 240 [[image:1657351240556-536.png]] 241 241 242 242 211 + 243 243 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 244 244 245 - 246 246 ((( 247 247 ((( 248 248 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. 249 - 250 - 251 251 ))) 252 252 ))) 253 253 254 254 [[image:1657351312545-300.png]] 255 255 222 +**Connection:** 256 256 257 -(% style="color: blue" %)**Connection:**224 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 258 258 259 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**226 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 260 260 261 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**228 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 262 262 263 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 264 264 265 - 266 266 In the PC, use below serial tool settings: 267 267 268 268 * Baud: (% style="color:green" %)**9600** ... ... @@ -277,18 +277,17 @@ 277 277 278 278 [[image:1657329814315-101.png]] 279 279 280 - 281 281 ((( 282 -(% 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]]**246 +(% 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/]] 283 283 ))) 284 284 285 285 250 + 286 286 === 2.2.5 Use CoAP protocol to uplink data === 287 287 253 +(% 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 -(% 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/]]** 290 290 291 - 292 292 ((( 293 293 **Use below commands:** 294 294 ))) ... ... @@ -297,10 +297,10 @@ 297 297 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 298 298 ))) 299 299 * ((( 300 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** 264 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 301 301 ))) 302 302 * ((( 303 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ 267 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 304 304 ))) 305 305 306 306 ((( ... ... @@ -319,6 +319,7 @@ 319 319 [[image:1657352185396-303.png]] 320 320 321 321 286 + 322 322 === 2.2.6 Use UDP protocol to uplink data(Default protocol) === 323 323 324 324 ... ... @@ -332,18 +332,18 @@ 332 332 [[image:1657352403317-397.png]] 333 333 334 334 300 + 335 335 === 2.2.7 Use MQTT protocol to uplink data === 336 336 337 - 338 338 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 339 339 340 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 341 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 342 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 343 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 344 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 345 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ 346 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ 305 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 306 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 307 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 308 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 309 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 310 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 311 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 347 347 348 348 [[image:1657352634421-276.png]] 349 349 ... ... @@ -350,19 +350,19 @@ 350 350 351 351 [[image:1657352645687-385.png]] 352 352 353 - 354 354 ((( 355 355 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. 356 356 ))) 357 357 322 + 358 358 ((( 359 359 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. 360 360 ))) 361 361 362 362 328 + 363 363 === 2.2.8 Use TCP protocol to uplink data === 364 364 365 - 366 366 This feature is supported since firmware version v110 367 367 368 368 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -374,9 +374,9 @@ 374 374 [[image:1657352914475-252.png]] 375 375 376 376 342 + 377 377 === 2.2.9 Change Update Interval === 378 378 379 - 380 380 User can use below command to change the (% style="color:green" %)**uplink interval**. 381 381 382 382 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -385,99 +385,58 @@ 385 385 386 386 ))) 387 387 388 -((( 389 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 390 -))) 391 391 392 -((( 393 -(% 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).** 394 -))) 395 395 396 - 397 397 == 2.3 Uplink Payload == 398 398 399 399 400 -((( 401 -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. 402 -))) 358 +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. 403 403 404 404 405 -((( 406 406 For example: 407 -))) 408 408 409 -((( 410 - (% 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. 411 -))) 363 + (% 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. 412 412 413 413 414 -((( 415 415 The uplink payloads are composed in ASCII String. For example: 416 -))) 417 417 418 -((( 419 419 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 420 -))) 421 421 422 -((( 423 423 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 424 -))) 425 425 426 426 427 -((( 428 428 (% style="color:red" %)**NOTE:** 429 -))) 430 430 431 431 (% style="color:red" %) 432 -1. ((( 433 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 434 -))) 435 -1. ((( 436 -**By default, the device will send an uplink message every 1 hour.** 376 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 377 +1. By default, the device will send an uplink message every 1 hour. 437 437 438 438 439 - 440 -))) 441 441 442 442 === 2.3.1 Payload Analyze === 443 443 444 -==== 2.3.1.1 Before Firmware v1.2 ==== 445 - 446 - 447 447 N95S31B uplink payload includes in total 21 bytes 448 448 449 449 450 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 451 -|=(% style="width: 50px;" %)**Size(bytes)**|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 65px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**2** 452 -|(% 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" %)((( 453 -((( 386 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 387 +|=(% style="width: 60px;" %)((( 388 +**Size(bytes)** 389 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1** 390 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 454 454 Reserve/ Same as NBSN95 CFGMOD=1 455 -))) 456 456 457 -((( 458 458 No function here. 459 -))) 460 -)))|(% style="width:102px" %)((( 461 -((( 462 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 463 -))) 394 +)))|(% style="width:77px" %)((( 395 +[[Temperature >>||anchor="H2.4.5A0Distance"]] 464 464 465 -((( 466 466 By SHT31 467 -))) 468 -)))|(% style="width:81px" %)((( 469 -((( 470 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 471 -))) 398 +)))|(% style="width:80px" %)((( 399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 472 472 473 -((( 474 474 By SHT31 475 475 ))) 476 -))) 477 477 478 478 ((( 479 - 480 - 481 481 ((( 482 482 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 483 483 ))) ... ... @@ -487,89 +487,29 @@ 487 487 [[image:1657354294009-643.png]] 488 488 489 489 490 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457**414 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 491 491 492 -**where:** 416 +* Device ID: 0x724031607457 = 724031607457 417 +* Version: 0x006e=110=1.1.0 493 493 494 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 419 +* BAT: 0x0ccd = 3277 mV = 3.277V 420 +* Signal: 0x1b = 27 421 +* Model: 0x01 = 1 422 +* 0x00dc000ccc= reserve, ignore in N95S31B 423 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 424 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 495 495 496 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 497 - 498 -* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 499 - 500 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 501 - 502 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 503 - 504 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 505 - 506 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 507 - 508 -* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 509 - 510 510 ((( 511 511 428 +))) 512 512 430 +((( 513 513 514 514 ))) 515 515 516 -==== 2.3.1.2 Since Firmware v1.2 ==== 517 517 518 - 519 -In this mode, uplink payload includes 91 bytes in total by default. 520 - 521 -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. 522 - 523 - 524 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 525 -|=(% 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** 526 -|=(% 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 ..... 527 - 528 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 529 - 530 - 531 -[[image:image-20220908154949-1.png]] 532 - 533 - 534 -The payload is ASCII string, representative same HEX: 535 - 536 -**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__ ** 537 - 538 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 539 - 540 -**where:** 541 - 542 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 543 - 544 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 545 - 546 -* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 547 - 548 -* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 549 - 550 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 551 - 552 -* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 553 - 554 -* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 555 - 556 -* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 557 - 558 -* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 559 - 560 -* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 561 - 562 -* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 563 - 564 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 565 - 566 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 567 - 568 - 569 - 570 570 === 2.3.2 Device ID === 571 571 572 - 573 573 ((( 574 574 By default, the Device ID equal to the last 6 bytes of IMEI. 575 575 ))) ... ... @@ -576,12 +576,10 @@ 576 576 577 577 ((( 578 578 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 579 - 580 - 581 581 ))) 582 582 583 583 ((( 584 - (% style="color:blue" %)**Example:**446 +**Example:** 585 585 ))) 586 586 587 587 ((( ... ... @@ -589,54 +589,30 @@ 589 589 ))) 590 590 591 591 ((( 592 -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. 593 - 594 - 454 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 595 595 ))) 596 596 597 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 598 598 599 599 600 -By default, the Device ID equal to the last 15 bits of IMEI. 601 - 602 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 603 - 604 - 605 -(% style="color:blue" %)**Example:** 606 - 607 -AT+DEUI=868411056754138 608 - 609 - 610 610 === 2.3.3 Version Info === 611 611 612 612 613 -((( 614 614 These bytes include the hardware and software version. 615 -))) 616 616 617 -((( 618 -**Higher byte:** Specify hardware version: always 0x00 for N95S31B 619 -))) 464 +Higher byte: Specify hardware version: always 0x00 for N95S31B 620 620 621 -((( 622 -**Lower byte:** Specify the software version: 0x6E=110, means firmware version 110 623 -))) 466 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 624 624 625 -((( 626 - 627 -))) 628 628 629 -((( 630 630 For example: 0x00 6E: this device is N95S31B with firmware version 110. 631 -))) 632 632 633 633 ((( 634 634 635 635 ))) 636 636 475 + 637 637 === 2.3.4 Battery Info === 638 638 639 - 640 640 ((( 641 641 Ex1: 0x0B45 = 2885mV 642 642 ))) ... ... @@ -646,9 +646,9 @@ 646 646 ))) 647 647 648 648 487 + 649 649 === 2.3.5 Signal Strength === 650 650 651 - 652 652 ((( 653 653 NB-IoT Network signal Strength. 654 654 ))) ... ... @@ -678,9 +678,9 @@ 678 678 ))) 679 679 680 680 519 + 681 681 === 2.3.6 Temperature & Humidity === 682 682 683 - 684 684 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 685 685 686 686 [[image:image-20220709161741-3.png]] ... ... @@ -696,10 +696,10 @@ 696 696 Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 697 697 698 698 699 -== 2.4 Downlink Payload == 700 700 538 +== 2.5 Downlink Payload == 701 701 702 -By default, 95S31Bprints the downlink payload to console port.540 +By default, NDDS75 prints the downlink payload to console port. 703 703 704 704 [[image:image-20220709100028-1.png]] 705 705 ... ... @@ -737,7 +737,7 @@ 737 737 ))) 738 738 739 739 ((( 740 -If payload = 0x04FF, it will reset the 95S31B578 +If payload = 0x04FF, it will reset the NDDS75 741 741 ))) 742 742 743 743 ... ... @@ -748,76 +748,69 @@ 748 748 ))) 749 749 750 750 751 -== 2.5 Humidity and Temperature alarm function == 752 752 590 +== 2.5 Battery Analysis == 753 753 754 - **~(%style="color:blue"%)➢ ATCommand:(%%)**592 +=== 2.5.1 Battery Type === 755 755 756 756 757 -(% style="color:#037691" %)**AT+ SHHUM=min,max** 595 +((( 596 +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. 597 +))) 758 758 599 +((( 600 +The battery is designed to last for several years depends on the actually use environment and update interval. 601 +))) 759 759 760 -² When min=0, and max≠0, Alarm higher than max 603 +((( 604 +The battery related documents as below: 605 +))) 761 761 762 -² When min≠0, and max=0, Alarm lower than min 607 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 608 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 609 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 763 763 764 -² When min≠0 and max≠0, Alarm higher than max or lower than min 611 +((( 612 +[[image:image-20220709101450-2.png]] 613 +))) 765 765 766 766 767 - (% style="color:blue" %)**Example:** 768 768 769 - AT+ SHHUM=50,80~/~/ Alarmwhenhumiditylowerthan 50.617 +=== 2.5.2 Power consumption Analyze === 770 770 619 +((( 620 +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. 621 +))) 771 771 772 -(% style="color:#037691" %)**AT+ SHTEMP=min,max** 623 +((( 624 + 625 +))) 773 773 774 -² When min=0, and max≠0, Alarm higher than max 775 775 776 - ²Whenmin≠0,and max=0, Alarmlowerthan min628 +=== 2.5.3 Battery Note === 777 777 778 -² When min≠0 and max≠0, Alarm higher than max or lower than min 630 +((( 631 +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. 632 +))) 779 779 780 780 781 -**~ (% style="color:blue" %)Example:(%%)** 782 782 783 - AT+ SHTEMP=20,30~/~/ Alarm whentemperaturelowerthan 20.636 +=== 2.5.4 Replace the battery === 784 784 785 785 786 -== 2.6 Set the number of data to be uploaded and the recording time == 639 +((( 640 +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. 641 +))) 787 787 788 788 789 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 644 +((( 645 +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). 646 +))) 790 790 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. 793 793 794 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 795 795 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 - 818 818 = 3. Access NB-IoT Module = 819 819 820 - 821 821 ((( 822 822 Users can directly access the AT command set of the NB-IoT module. 823 823 ))) ... ... @@ -824,21 +824,19 @@ 824 824 825 825 ((( 826 826 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 - 829 829 ))) 830 830 831 831 [[image:1657333200519-600.png]] 832 832 833 833 663 + 834 834 = 4. Using the AT Commands = 835 835 836 836 == 4.1 Access AT Commands == 837 837 668 +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/]] 838 838 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]] 840 840 841 - 842 842 AT+<CMD>? : Help on <CMD> 843 843 844 844 AT+<CMD> : Run <CMD> ... ... @@ -878,24 +878,7 @@ 878 878 879 879 AT+SERVADDR : Server Address 880 880 881 -AT+TR : Get or Set record time 882 882 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 - 899 899 (% style="color:#037691" %)**COAP Management** 900 900 901 901 AT+URI : Resource parameters ... ... @@ -926,6 +926,7 @@ 926 926 AT+PWORD : Serial Access Password 927 927 928 928 741 + 929 929 = 5. FAQ = 930 930 931 931 == 5.1 How to Upgrade Firmware == ... ... @@ -940,12 +940,13 @@ 940 940 ))) 941 941 942 942 ((( 943 - FirmwareDownload:[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]]756 + 944 944 945 -(% style="color:red" %) **Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**758 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 946 946 ))) 947 947 948 948 762 + 949 949 = 6. Trouble Shooting = 950 950 951 951 == 6.1 Connection problem when uploading firmware == ... ... @@ -955,10 +955,14 @@ 955 955 **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]] 956 956 ))) 957 957 772 +(% class="wikigeneratedid" %) 773 +((( 774 + 775 +))) 958 958 777 + 959 959 == 6.2 AT Command input doesn't work == 960 960 961 - 962 962 ((( 963 963 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. 964 964 ... ... @@ -965,18 +965,18 @@ 965 965 966 966 ))) 967 967 968 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 969 969 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 - 974 974 = 7. Order Info = 975 975 976 976 977 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B -YY**790 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B** 978 978 979 979 793 +(% class="wikigeneratedid" %) 794 +((( 795 + 796 +))) 797 + 980 980 = 8. Packing Info = 981 981 982 982 ((( ... ... @@ -984,7 +984,7 @@ 984 984 985 985 (% style="color:#037691" %)**Package Includes**: 986 986 987 -* N 95S31BNB-IoTTemperatureandHumiditySensor805 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 988 988 * External antenna x 1 989 989 ))) 990 990 ... ... @@ -993,19 +993,21 @@ 993 993 994 994 (% style="color:#037691" %)**Dimension and weight**: 995 995 814 + 996 996 * Device Size: 13.0 x 5 x 4.5 cm 997 997 * Device Weight: 150g 998 -* Package Size / pcs : 1 4.0x8x 5 cm999 -* Weight / pcs : 180g817 +* Package Size / pcs : 15 x 12x 5.5 cm 818 +* Weight / pcs : 220g 1000 1000 ))) 1001 1001 821 +((( 822 + 1002 1002 1003 1003 825 + 826 +))) 827 + 1004 1004 = 9. Support = 1005 1005 1006 - 1007 1007 * 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 - 1009 1009 * 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,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