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
-
... ... @@ -17,6 +17,7 @@ 17 17 18 18 = 1. Introduction = 19 19 20 + 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 22 22 ((( ... ... @@ -55,6 +55,7 @@ 55 55 56 56 == 1.2 Features == 57 57 59 + 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 ... ... @@ -85,7 +85,6 @@ 85 85 86 86 (% style="color:#037691" %)**Battery:** 87 87 88 - 89 89 * Li/SOCI2 un-chargeable battery 90 90 * Capacity: 8500mAh 91 91 * Self Discharge: <1% / Year @ 25°C ... ... @@ -94,6 +94,7 @@ 94 94 95 95 == 1.4 Applications == 96 96 98 + 97 97 * Smart Buildings & Home Automation 98 98 * Logistics and Supply Chain Management 99 99 * Smart Metering ... ... @@ -105,15 +105,20 @@ 105 105 106 106 107 107 108 -== 1.5 Pin Definitions == 109 109 111 +== 1.5 Pin Definitions & Switch == 112 + 113 + 110 110 N95S31B use the mother board from NBSN95 which as below. 111 111 116 + 112 112 [[image:image-20220709144723-1.png]] 113 113 114 114 120 + 115 115 === 1.5.1 Jumper JP2 === 116 116 123 + 117 117 Power on Device when put this jumper. 118 118 119 119 ... ... @@ -120,14 +120,20 @@ 120 120 121 121 === 1.5.2 BOOT MODE / SW1 === 122 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 124 125 -2) Flash: work mode, device starts to work and send out console output for further debug 131 +((( 132 +**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. 133 +))) 126 126 135 +((( 136 +**2) Flash:** work mode, device starts to work and send out console output for further debug 137 +))) 127 127 128 128 140 + 129 129 === 1.5.3 Reset Button === 130 130 143 + 131 131 Press to reboot the device. 132 132 133 133 ... ... @@ -134,13 +134,18 @@ 134 134 135 135 === 1.5.4 LED === 136 136 150 + 137 137 It will flash: 138 138 139 -1. When boot the device in flash mode 140 -1. Send an uplink packet 153 +1. When boot the device in flash mode 141 141 155 +2. Send an uplink packet 156 + 157 + 158 + 142 142 = 2. Use N95S31B to communicate with IoT Server = 143 143 161 + 144 144 == 2.1 How it works == 145 145 146 146 ... ... @@ -157,7 +157,7 @@ 157 157 158 158 ))) 159 159 160 -[[image:1657 350248151-650.png]]178 +[[image:1657520100595-569.png]] 161 161 162 162 ((( 163 163 ... ... @@ -173,26 +173,49 @@ 173 173 [[image:image-20220709150546-2.png]] 174 174 175 175 194 + 176 176 === 2.2.1 Test Requirement === 177 177 178 178 198 +((( 179 179 To use N95S31B in your city, make sure meet below requirements: 200 +))) 180 180 181 -* Your local operator has already distributed a NB-IoT Network there. 182 -* The local NB-IoT network used the band that N95S31B supports. 183 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 202 +* ((( 203 +Your local operator has already distributed a NB-IoT Network there. 204 +))) 205 +* ((( 206 +The local NB-IoT network used the band that N95S31B supports. 207 +))) 208 +* ((( 209 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 210 +))) 184 184 212 +((( 185 185 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 214 +))) 186 186 216 +((( 187 187 N95S31B supports different communication protocol such as : 218 +))) 188 188 189 189 ((( 190 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 191 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 192 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 193 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 221 +* ((( 222 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 223 +))) 224 +* ((( 225 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 226 +))) 227 +* ((( 228 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 229 +))) 230 +* ((( 231 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 232 +))) 194 194 234 +((( 195 195 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. 236 +))) 196 196 197 197 198 198 ))) ... ... @@ -203,6 +203,7 @@ 203 203 204 204 === 2.2.3 Insert SIM card === 205 205 247 + 206 206 ((( 207 207 Insert the NB-IoT Card get from your provider. 208 208 ))) ... ... @@ -218,23 +218,27 @@ 218 218 219 219 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 220 220 263 + 221 221 ((( 222 222 ((( 223 223 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. 267 + 268 + 224 224 ))) 225 225 ))) 226 226 227 227 [[image:1657351312545-300.png]] 228 228 229 -**Connection:** 230 230 231 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND275 +(% style="color:blue" %)**Connection:** 232 232 233 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD277 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 234 234 235 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD279 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 236 236 281 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 237 237 283 + 238 238 In the PC, use below serial tool settings: 239 239 240 240 * Baud: (% style="color:green" %)**9600** ... ... @@ -249,8 +249,9 @@ 249 249 250 250 [[image:1657329814315-101.png]] 251 251 298 + 252 252 ((( 253 -(% 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/]]300 +(% 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]]** 254 254 ))) 255 255 256 256 ... ... @@ -257,9 +257,10 @@ 257 257 258 258 === 2.2.5 Use CoAP protocol to uplink data === 259 259 260 -(% 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/]] 261 261 308 +(% 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/]]** 262 262 310 + 263 263 ((( 264 264 **Use below commands:** 265 265 ))) ... ... @@ -268,10 +268,10 @@ 268 268 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 269 269 ))) 270 270 * ((( 271 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 319 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 272 272 ))) 273 273 * ((( 274 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 322 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 275 275 ))) 276 276 277 277 ((( ... ... @@ -307,15 +307,16 @@ 307 307 308 308 === 2.2.7 Use MQTT protocol to uplink data === 309 309 358 + 310 310 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 311 311 312 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 313 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 314 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 315 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 316 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 317 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 318 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 361 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 362 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 363 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 364 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 365 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 366 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ Set the sending topic of MQTT 367 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ Set the subscription topic of MQTT 319 319 320 320 [[image:1657352634421-276.png]] 321 321 ... ... @@ -322,6 +322,7 @@ 322 322 323 323 [[image:1657352645687-385.png]] 324 324 374 + 325 325 ((( 326 326 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. 327 327 ))) ... ... @@ -335,6 +335,7 @@ 335 335 336 336 === 2.2.8 Use TCP protocol to uplink data === 337 337 388 + 338 338 This feature is supported since firmware version v110 339 339 340 340 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -349,6 +349,7 @@ 349 349 350 350 === 2.2.9 Change Update Interval === 351 351 403 + 352 352 User can use below command to change the (% style="color:green" %)**uplink interval**. 353 353 354 354 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -357,43 +357,74 @@ 357 357 358 358 ))) 359 359 412 +((( 413 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 414 +))) 360 360 416 +((( 417 +(% 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).** 418 +))) 361 361 420 + 421 + 362 362 == 2.3 Uplink Payload == 363 363 364 364 365 -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. 425 +((( 426 +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. 427 +))) 366 366 367 367 430 +((( 368 368 For example: 432 +))) 369 369 370 - (% 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. 434 +((( 435 + (% 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. 436 +))) 371 371 372 372 439 +((( 373 373 The uplink payloads are composed in ASCII String. For example: 441 +))) 374 374 443 +((( 375 375 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 445 +))) 376 376 447 +((( 377 377 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 449 +))) 378 378 379 379 452 +((( 380 380 (% style="color:red" %)**NOTE:** 454 +))) 381 381 382 382 (% style="color:red" %) 383 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 384 -1. By default, the device will send an uplink message every 1 hour. 457 +1. ((( 458 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 459 +))) 460 +1. ((( 461 +**By default, the device will send an uplink message every 1 hour.** 385 385 386 386 464 + 465 + 466 +))) 467 + 387 387 === 2.3.1 Payload Analyze === 388 388 470 + 471 +==== 2.3.1.1 Before Firmware v1.2 ==== 472 + 473 + 389 389 N95S31B uplink payload includes in total 21 bytes 390 390 391 391 392 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 393 -|=(% style="width: 60px;" %)((( 394 -**Size(bytes)** 395 -)))|=(% 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** 396 -|(% 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" %)((( 477 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 478 +|=(% style="width: 50px;" %)**Size(bytes)**|=(% style="width: 40px;" %)**6**|=(% style="width: 20px;" %)2|=(% style="width: 20px;" %)**2**|=(% style="width: 60px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 150px;" %)5|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**2** 479 +|(% 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" %)((( 397 397 ((( 398 398 Reserve/ Same as NBSN95 CFGMOD=1 399 399 ))) ... ... @@ -401,7 +401,7 @@ 401 401 ((( 402 402 No function here. 403 403 ))) 404 -)))|(% style="width: 77px" %)(((487 +)))|(% style="width:102px" %)((( 405 405 ((( 406 406 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 407 407 ))) ... ... @@ -409,7 +409,7 @@ 409 409 ((( 410 410 By SHT31 411 411 ))) 412 -)))|(% style="width:8 0px" %)(((495 +)))|(% style="width:81px" %)((( 413 413 ((( 414 414 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 415 415 ))) ... ... @@ -420,6 +420,8 @@ 420 420 ))) 421 421 422 422 ((( 506 + 507 + 423 423 ((( 424 424 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 425 425 ))) ... ... @@ -429,29 +429,88 @@ 429 429 [[image:1657354294009-643.png]] 430 430 431 431 432 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:517 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 433 433 434 -* Device ID: 0x724031607457 = 724031607457 435 -* Version: 0x006e=110=1.1.0 519 +**where:** 436 436 437 -* BAT: 0x0ccd = 3277 mV = 3.277V 438 -* Signal: 0x1b = 27 439 -* Model: 0x01 = 1 440 -* 0x00dc000ccc= reserve, ignore in N95S31B 441 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 442 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 521 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 443 443 523 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 524 + 525 +* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 526 + 527 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 528 + 529 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 530 + 531 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 532 + 533 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 534 + 535 +* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 536 + 444 444 ((( 445 445 446 -))) 447 447 448 - (((540 + 449 449 450 450 ))) 451 451 544 +==== 2.3.1.2 Since Firmware v1.2 ==== 452 452 546 + 547 +In this mode, uplink payload includes 91 bytes in total by default. 548 + 549 +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. 550 + 551 + 552 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 553 +|=(% 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** 554 +|=(% 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 ..... 555 + 556 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 557 + 558 + 559 +[[image:image-20220908154949-1.png]] 560 + 561 + 562 +The payload is ASCII string, representative same HEX: 563 + 564 +**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__ ** 565 + 566 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 567 + 568 +**where:** 569 + 570 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 571 + 572 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 573 + 574 +* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 575 + 576 +* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 577 + 578 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 579 + 580 +* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 581 + 582 +* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 583 + 584 +* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 585 + 586 +* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 587 + 588 +* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 589 + 590 +* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 591 + 592 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 593 + 594 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 595 + 453 453 === 2.3.2 Device ID === 454 454 598 + 455 455 ((( 456 456 By default, the Device ID equal to the last 6 bytes of IMEI. 457 457 ))) ... ... @@ -458,10 +458,12 @@ 458 458 459 459 ((( 460 460 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 605 + 606 + 461 461 ))) 462 462 463 463 ((( 464 -**Example:** 610 +(% style="color:blue" %)**Example:** 465 465 ))) 466 466 467 467 ((( ... ... @@ -469,22 +469,47 @@ 469 469 ))) 470 470 471 471 ((( 472 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 618 +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. 619 + 620 + 473 473 ))) 474 474 623 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 475 475 476 476 626 +By default, the Device ID equal to the last 15 bits of IMEI. 627 + 628 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 629 + 630 + 631 +(% style="color:blue" %)**Example:** 632 + 633 +AT+DEUI=868411056754138 634 + 635 + 636 + 477 477 === 2.3.3 Version Info === 478 478 479 479 640 +((( 480 480 These bytes include the hardware and software version. 642 +))) 481 481 644 +((( 482 482 Higher byte: Specify hardware version: always 0x00 for N95S31B 646 +))) 483 483 648 +((( 484 484 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 650 +))) 485 485 652 +((( 653 + 654 +))) 486 486 656 +((( 487 487 For example: 0x00 6E: this device is N95S31B with firmware version 110. 658 +))) 488 488 489 489 ((( 490 490 ... ... @@ -493,6 +493,7 @@ 493 493 494 494 === 2.3.4 Battery Info === 495 495 667 + 496 496 ((( 497 497 Ex1: 0x0B45 = 2885mV 498 498 ))) ... ... @@ -505,6 +505,7 @@ 505 505 506 506 === 2.3.5 Signal Strength === 507 507 680 + 508 508 ((( 509 509 NB-IoT Network signal Strength. 510 510 ))) ... ... @@ -537,6 +537,7 @@ 537 537 538 538 === 2.3.6 Temperature & Humidity === 539 539 713 + 540 540 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 541 541 542 542 [[image:image-20220709161741-3.png]] ... ... @@ -555,8 +555,9 @@ 555 555 556 556 == 2.4 Downlink Payload == 557 557 558 -By default, NDDS75 prints the downlink payload to console port. 559 559 733 +By default, N95S31B prints the downlink payload to console port. 734 + 560 560 [[image:image-20220709100028-1.png]] 561 561 562 562 ... ... @@ -593,7 +593,7 @@ 593 593 ))) 594 594 595 595 ((( 596 -If payload = 0x04FF, it will reset the DDS75771 +If payload = 0x04FF, it will reset the N95S31B 597 597 ))) 598 598 599 599 ... ... @@ -605,11 +605,74 @@ 605 605 606 606 607 607 608 -== 2.5 BatteryAnalysis==783 +== 2.5 Humidity and Temperature alarm function == 609 609 610 -=== 2.5.1 Battery Type === 611 611 786 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 612 612 788 + 789 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 790 + 791 + 792 +² When min=0, and max≠0, Alarm higher than max 793 + 794 +² When min≠0, and max=0, Alarm lower than min 795 + 796 +² When min≠0 and max≠0, Alarm higher than max or lower than min 797 + 798 + 799 + (% style="color:blue" %)**Example:** 800 + 801 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 802 + 803 + 804 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 805 + 806 +² When min=0, and max≠0, Alarm higher than max 807 + 808 +² When min≠0, and max=0, Alarm lower than min 809 + 810 +² When min≠0 and max≠0, Alarm higher than max or lower than min 811 + 812 + 813 +**~ (% style="color:blue" %)Example:(%%)** 814 + 815 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 816 + 817 + 818 + 819 +== 2.6 Set the number of data to be uploaded and the recording time == 820 + 821 + 822 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 823 + 824 +* (% 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) 825 +* (% 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. 826 + 827 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 828 + 829 +[[image:image-20221009001045-1.png||height="726" width="1009"]] 830 + 831 + 832 + 833 +== 2.7 Read or Clear cached data == 834 + 835 + 836 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 837 + 838 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 839 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 840 + 841 +[[image:image-20220908163102-2.png]] 842 + 843 + 844 + 845 +== 2.8 Battery Analysis == 846 + 847 + 848 +=== 2.8.1 Battery Type === 849 + 850 + 613 613 ((( 614 614 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. 615 615 ))) ... ... @@ -632,10 +632,11 @@ 632 632 633 633 634 634 635 -=== 2. 5.2 Power consumption Analyze ===873 +=== 2.8.2 Power consumption Analyze === 636 636 875 + 637 637 ((( 638 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]877 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 639 639 ))) 640 640 641 641 ((( ... ... @@ -643,8 +643,9 @@ 643 643 ))) 644 644 645 645 646 -=== 2. 5.3 Battery Note ===885 +=== 2.8.3 Battery Note === 647 647 887 + 648 648 ((( 649 649 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. 650 650 ))) ... ... @@ -651,7 +651,7 @@ 651 651 652 652 653 653 654 -=== 2. 5.4 Replace the battery ===894 +=== 2.8.4 Replace the battery === 655 655 656 656 657 657 ((( ... ... @@ -667,6 +667,7 @@ 667 667 668 668 = 3. Access NB-IoT Module = 669 669 910 + 670 670 ((( 671 671 Users can directly access the AT command set of the NB-IoT module. 672 672 ))) ... ... @@ -673,6 +673,8 @@ 673 673 674 674 ((( 675 675 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/]] 917 + 918 + 676 676 ))) 677 677 678 678 [[image:1657333200519-600.png]] ... ... @@ -681,11 +681,13 @@ 681 681 682 682 = 4. Using the AT Commands = 683 683 927 + 684 684 == 4.1 Access AT Commands == 685 685 686 -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/]] 687 687 931 +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]] 688 688 933 + 689 689 AT+<CMD>? : Help on <CMD> 690 690 691 691 AT+<CMD> : Run <CMD> ... ... @@ -725,7 +725,24 @@ 725 725 726 726 AT+SERVADDR : Server Address 727 727 973 +AT+TR : Get or Set record time 728 728 975 +AT+APN : Get or set the APN 976 + 977 +AT+FBAND : Get or Set whether to automatically modify the frequency band 978 + 979 +AT+DNSCFG : Get or Set DNS Server 980 + 981 +AT+GETSENSORVALUE : Returns the current sensor measurement 982 + 983 +AT+NOUD : Get or Set the number of data to be uploaded 984 + 985 +AT+CDP : Read or Clear cached data 986 + 987 +AT+SHTEMP: Get or Set alarm of temp 988 + 989 +AT+SHHUM: Get or Set alarm of moisture 990 + 729 729 (% style="color:#037691" %)**COAP Management** 730 730 731 731 AT+URI : Resource parameters ... ... @@ -759,6 +759,7 @@ 759 759 760 760 = 5. FAQ = 761 761 1024 + 762 762 == 5.1 How to Upgrade Firmware == 763 763 764 764 ... ... @@ -773,13 +773,16 @@ 773 773 ((( 774 774 775 775 776 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 1039 +((( 1040 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 777 777 ))) 1042 +))) 778 778 779 779 780 780 781 781 = 6. Trouble Shooting = 782 782 1048 + 783 783 == 6.1 Connection problem when uploading firmware == 784 784 785 785 ... ... @@ -795,6 +795,7 @@ 795 795 796 796 == 6.2 AT Command input doesn't work == 797 797 1064 + 798 798 ((( 799 799 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. 800 800 ... ... @@ -844,5 +844,6 @@ 844 844 845 845 = 9. Support = 846 846 1114 + 847 847 * 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. 848 848 * 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]]
- 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