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 ... ... @@ -68,7 +68,6 @@ 68 68 69 69 70 70 71 - 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -77,7 +77,6 @@ 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 83 * - B1 @H-FDD: 2100MHz ... ... @@ -87,7 +87,6 @@ 87 87 * - B20 @H-FDD: 800MHz 88 88 * - B28 @H-FDD: 700MHz 89 89 90 - 91 91 (% style="color:#037691" %)**Battery:** 92 92 93 93 * Li/SOCI2 un-chargeable battery ... ... @@ -98,9 +98,9 @@ 98 98 99 99 100 100 101 - 102 102 == 1.4 Applications == 103 103 102 + 104 104 * Smart Buildings & Home Automation 105 105 * Logistics and Supply Chain Management 106 106 * Smart Metering ... ... @@ -112,15 +112,20 @@ 112 112 113 113 114 114 115 -== 1.5 Pin Definitions == 116 116 115 +== 1.5 Pin Definitions & Switch == 116 + 117 + 117 117 N95S31B use the mother board from NBSN95 which as below. 118 118 120 + 119 119 [[image:image-20220709144723-1.png]] 120 120 121 121 124 + 122 122 === 1.5.1 Jumper JP2 === 123 123 127 + 124 124 Power on Device when put this jumper. 125 125 126 126 ... ... @@ -127,12 +127,13 @@ 127 127 128 128 === 1.5.2 BOOT MODE / SW1 === 129 129 134 + 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. 136 +**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 140 +**2) Flash:** work mode, device starts to work and send out console output for further debug 136 136 ))) 137 137 138 138 ... ... @@ -139,6 +139,7 @@ 139 139 140 140 === 1.5.3 Reset Button === 141 141 147 + 142 142 Press to reboot the device. 143 143 144 144 ... ... @@ -145,16 +145,18 @@ 145 145 146 146 === 1.5.4 LED === 147 147 154 + 148 148 It will flash: 149 149 150 -1. When boot the device in flash mode 151 -1. Send an uplink packet 157 +1. When boot the device in flash mode 152 152 159 +2. Send an uplink packet 153 153 154 154 155 155 156 156 = 2. Use N95S31B to communicate with IoT Server = 157 157 165 + 158 158 == 2.1 How it works == 159 159 160 160 ... ... @@ -171,7 +171,7 @@ 171 171 172 172 ))) 173 173 174 -[[image:1657 350248151-650.png]]182 +[[image:1657520100595-569.png]] 175 175 176 176 ((( 177 177 ... ... @@ -187,26 +187,49 @@ 187 187 [[image:image-20220709150546-2.png]] 188 188 189 189 198 + 190 190 === 2.2.1 Test Requirement === 191 191 192 192 202 +((( 193 193 To use N95S31B in your city, make sure meet below requirements: 204 +))) 194 194 195 -* Your local operator has already distributed a NB-IoT Network there. 196 -* The local NB-IoT network used the band that N95S31B supports. 197 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 206 +* ((( 207 +Your local operator has already distributed a NB-IoT Network there. 208 +))) 209 +* ((( 210 +The local NB-IoT network used the band that N95S31B supports. 211 +))) 212 +* ((( 213 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 214 +))) 198 198 216 +((( 199 199 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 218 +))) 200 200 220 +((( 201 201 N95S31B supports different communication protocol such as : 222 +))) 202 202 203 203 ((( 204 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 205 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 206 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 207 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 225 +* ((( 226 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 227 +))) 228 +* ((( 229 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 230 +))) 231 +* ((( 232 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 233 +))) 234 +* ((( 235 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 236 +))) 208 208 238 +((( 209 209 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. 240 +))) 210 210 211 211 212 212 ))) ... ... @@ -217,6 +217,7 @@ 217 217 218 218 === 2.2.3 Insert SIM card === 219 219 251 + 220 220 ((( 221 221 Insert the NB-IoT Card get from your provider. 222 222 ))) ... ... @@ -232,23 +232,27 @@ 232 232 233 233 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 234 234 267 + 235 235 ((( 236 236 ((( 237 237 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. 271 + 272 + 238 238 ))) 239 239 ))) 240 240 241 241 [[image:1657351312545-300.png]] 242 242 243 -**Connection:** 244 244 245 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND279 +(% style="color:blue" %)**Connection:** 246 246 247 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD281 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 248 248 249 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD283 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 250 250 285 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 251 251 287 + 252 252 In the PC, use below serial tool settings: 253 253 254 254 * Baud: (% style="color:green" %)**9600** ... ... @@ -263,8 +263,9 @@ 263 263 264 264 [[image:1657329814315-101.png]] 265 265 302 + 266 266 ((( 267 -(% 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/]]304 +(% 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]]** 268 268 ))) 269 269 270 270 ... ... @@ -271,9 +271,10 @@ 271 271 272 272 === 2.2.5 Use CoAP protocol to uplink data === 273 273 274 -(% 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/]] 275 275 312 +(% 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/]]** 276 276 314 + 277 277 ((( 278 278 **Use below commands:** 279 279 ))) ... ... @@ -282,10 +282,10 @@ 282 282 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 283 283 ))) 284 284 * ((( 285 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 323 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 286 286 ))) 287 287 * ((( 288 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 326 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 289 289 ))) 290 290 291 291 ((( ... ... @@ -321,15 +321,16 @@ 321 321 322 322 === 2.2.7 Use MQTT protocol to uplink data === 323 323 362 + 324 324 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 325 325 326 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 327 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 328 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 329 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 330 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 331 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 332 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 365 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 366 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 367 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 368 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 369 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 370 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ Set the sending topic of MQTT 371 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ Set the subscription topic of MQTT 333 333 334 334 [[image:1657352634421-276.png]] 335 335 ... ... @@ -336,6 +336,7 @@ 336 336 337 337 [[image:1657352645687-385.png]] 338 338 378 + 339 339 ((( 340 340 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. 341 341 ))) ... ... @@ -349,6 +349,7 @@ 349 349 350 350 === 2.2.8 Use TCP protocol to uplink data === 351 351 392 + 352 352 This feature is supported since firmware version v110 353 353 354 354 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -363,6 +363,7 @@ 363 363 364 364 === 2.2.9 Change Update Interval === 365 365 407 + 366 366 User can use below command to change the (% style="color:green" %)**uplink interval**. 367 367 368 368 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -371,43 +371,74 @@ 371 371 372 372 ))) 373 373 416 +((( 417 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 418 +))) 374 374 420 +((( 421 +(% 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).** 422 +))) 375 375 424 + 425 + 376 376 == 2.3 Uplink Payload == 377 377 378 378 379 -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. 429 +((( 430 +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. 431 +))) 380 380 381 381 434 +((( 382 382 For example: 436 +))) 383 383 384 - (% 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. 438 +((( 439 + (% 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. 440 +))) 385 385 386 386 443 +((( 387 387 The uplink payloads are composed in ASCII String. For example: 445 +))) 388 388 447 +((( 389 389 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 449 +))) 390 390 451 +((( 391 391 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 453 +))) 392 392 393 393 456 +((( 394 394 (% style="color:red" %)**NOTE:** 458 +))) 395 395 396 396 (% style="color:red" %) 397 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 398 -1. By default, the device will send an uplink message every 1 hour. 461 +1. ((( 462 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 463 +))) 464 +1. ((( 465 +**By default, the device will send an uplink message every 1 hour.** 399 399 400 400 468 + 469 + 470 +))) 471 + 401 401 === 2.3.1 Payload Analyze === 402 402 474 + 475 +==== 2.3.1.1 Before Firmware v1.2 ==== 476 + 477 + 403 403 N95S31B uplink payload includes in total 21 bytes 404 404 405 405 406 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 407 -|=(% style="width: 60px;" %)((( 408 -**Size(bytes)** 409 -)))|=(% 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** 410 -|(% 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" %)((( 481 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 482 +|=(% 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** 483 +|(% 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" %)((( 411 411 ((( 412 412 Reserve/ Same as NBSN95 CFGMOD=1 413 413 ))) ... ... @@ -415,7 +415,7 @@ 415 415 ((( 416 416 No function here. 417 417 ))) 418 -)))|(% style="width: 77px" %)(((491 +)))|(% style="width:102px" %)((( 419 419 ((( 420 420 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 421 421 ))) ... ... @@ -423,7 +423,7 @@ 423 423 ((( 424 424 By SHT31 425 425 ))) 426 -)))|(% style="width:8 0px" %)(((499 +)))|(% style="width:81px" %)((( 427 427 ((( 428 428 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 429 429 ))) ... ... @@ -434,6 +434,8 @@ 434 434 ))) 435 435 436 436 ((( 510 + 511 + 437 437 ((( 438 438 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 439 439 ))) ... ... @@ -443,29 +443,88 @@ 443 443 [[image:1657354294009-643.png]] 444 444 445 445 446 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:521 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 447 447 448 -* Device ID: 0x724031607457 = 724031607457 449 -* Version: 0x006e=110=1.1.0 523 +**where:** 450 450 451 -* BAT: 0x0ccd = 3277 mV = 3.277V 452 -* Signal: 0x1b = 27 453 -* Model: 0x01 = 1 454 -* 0x00dc000ccc= reserve, ignore in N95S31B 455 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 456 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 525 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 457 457 527 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 528 + 529 +* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 530 + 531 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 532 + 533 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 534 + 535 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 536 + 537 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 538 + 539 +* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 540 + 458 458 ((( 459 459 460 -))) 461 461 462 - (((544 + 463 463 464 464 ))) 465 465 548 +==== 2.3.1.2 Since Firmware v1.2 ==== 466 466 550 + 551 +In this mode, uplink payload includes 91 bytes in total by default. 552 + 553 +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. 554 + 555 + 556 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 557 +|=(% 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** 558 +|=(% 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 ..... 559 + 560 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 561 + 562 + 563 +[[image:image-20220908154949-1.png]] 564 + 565 + 566 +The payload is ASCII string, representative same HEX: 567 + 568 +**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__ ** 569 + 570 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 571 + 572 +**where:** 573 + 574 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 575 + 576 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 577 + 578 +* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 579 + 580 +* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 581 + 582 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 583 + 584 +* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 585 + 586 +* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 587 + 588 +* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 589 + 590 +* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 591 + 592 +* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 593 + 594 +* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 595 + 596 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 597 + 598 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 599 + 467 467 === 2.3.2 Device ID === 468 468 602 + 469 469 ((( 470 470 By default, the Device ID equal to the last 6 bytes of IMEI. 471 471 ))) ... ... @@ -472,10 +472,12 @@ 472 472 473 473 ((( 474 474 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 609 + 610 + 475 475 ))) 476 476 477 477 ((( 478 -**Example:** 614 +(% style="color:blue" %)**Example:** 479 479 ))) 480 480 481 481 ((( ... ... @@ -483,22 +483,47 @@ 483 483 ))) 484 484 485 485 ((( 486 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 622 +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. 623 + 624 + 487 487 ))) 488 488 627 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 489 489 490 490 630 +By default, the Device ID equal to the last 15 bits of IMEI. 631 + 632 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 633 + 634 + 635 +(% style="color:blue" %)**Example:** 636 + 637 +AT+DEUI=868411056754138 638 + 639 + 640 + 491 491 === 2.3.3 Version Info === 492 492 493 493 644 +((( 494 494 These bytes include the hardware and software version. 646 +))) 495 495 648 +((( 496 496 Higher byte: Specify hardware version: always 0x00 for N95S31B 650 +))) 497 497 652 +((( 498 498 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 654 +))) 499 499 656 +((( 657 + 658 +))) 500 500 660 +((( 501 501 For example: 0x00 6E: this device is N95S31B with firmware version 110. 662 +))) 502 502 503 503 ((( 504 504 ... ... @@ -507,6 +507,7 @@ 507 507 508 508 === 2.3.4 Battery Info === 509 509 671 + 510 510 ((( 511 511 Ex1: 0x0B45 = 2885mV 512 512 ))) ... ... @@ -519,6 +519,7 @@ 519 519 520 520 === 2.3.5 Signal Strength === 521 521 684 + 522 522 ((( 523 523 NB-IoT Network signal Strength. 524 524 ))) ... ... @@ -551,6 +551,7 @@ 551 551 552 552 === 2.3.6 Temperature & Humidity === 553 553 717 + 554 554 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 555 555 556 556 [[image:image-20220709161741-3.png]] ... ... @@ -569,8 +569,9 @@ 569 569 570 570 == 2.4 Downlink Payload == 571 571 572 -By default, NDDS75 prints the downlink payload to console port. 573 573 737 +By default, N95S31B prints the downlink payload to console port. 738 + 574 574 [[image:image-20220709100028-1.png]] 575 575 576 576 ... ... @@ -607,7 +607,7 @@ 607 607 ))) 608 608 609 609 ((( 610 -If payload = 0x04FF, it will reset the DDS75775 +If payload = 0x04FF, it will reset the N95S31B 611 611 ))) 612 612 613 613 ... ... @@ -619,11 +619,74 @@ 619 619 620 620 621 621 622 -== 2.5 BatteryAnalysis==787 +== 2.5 Humidity and Temperature alarm function == 623 623 624 -=== 2.5.1 Battery Type === 625 625 790 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 626 626 792 + 793 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 794 + 795 + 796 +² When min=0, and max≠0, Alarm higher than max 797 + 798 +² When min≠0, and max=0, Alarm lower than min 799 + 800 +² When min≠0 and max≠0, Alarm higher than max or lower than min 801 + 802 + 803 + (% style="color:blue" %)**Example:** 804 + 805 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 806 + 807 + 808 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 809 + 810 +² When min=0, and max≠0, Alarm higher than max 811 + 812 +² When min≠0, and max=0, Alarm lower than min 813 + 814 +² When min≠0 and max≠0, Alarm higher than max or lower than min 815 + 816 + 817 +**~ (% style="color:blue" %)Example:(%%)** 818 + 819 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 820 + 821 + 822 + 823 +== 2.6 Set the number of data to be uploaded and the recording time == 824 + 825 + 826 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 827 + 828 +* (% 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) 829 +* (% 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. 830 + 831 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 832 + 833 +[[image:image-20221009001045-1.png||height="726" width="1009"]] 834 + 835 + 836 + 837 +== 2.7 Read or Clear cached data == 838 + 839 + 840 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 841 + 842 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 843 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 844 + 845 +[[image:image-20220908163102-2.png]] 846 + 847 + 848 + 849 +== 2.8 Battery Analysis == 850 + 851 + 852 +=== 2.8.1 Battery Type === 853 + 854 + 627 627 ((( 628 628 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. 629 629 ))) ... ... @@ -646,10 +646,11 @@ 646 646 647 647 648 648 649 -=== 2. 5.2 Power consumption Analyze ===877 +=== 2.8.2 Power consumption Analyze === 650 650 879 + 651 651 ((( 652 -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/]]881 +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. 653 653 ))) 654 654 655 655 ((( ... ... @@ -657,8 +657,9 @@ 657 657 ))) 658 658 659 659 660 -=== 2. 5.3 Battery Note ===889 +=== 2.8.3 Battery Note === 661 661 891 + 662 662 ((( 663 663 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. 664 664 ))) ... ... @@ -665,7 +665,7 @@ 665 665 666 666 667 667 668 -=== 2. 5.4 Replace the battery ===898 +=== 2.8.4 Replace the battery === 669 669 670 670 671 671 ((( ... ... @@ -681,6 +681,7 @@ 681 681 682 682 = 3. Access NB-IoT Module = 683 683 914 + 684 684 ((( 685 685 Users can directly access the AT command set of the NB-IoT module. 686 686 ))) ... ... @@ -687,6 +687,8 @@ 687 687 688 688 ((( 689 689 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/]] 921 + 922 + 690 690 ))) 691 691 692 692 [[image:1657333200519-600.png]] ... ... @@ -695,11 +695,13 @@ 695 695 696 696 = 4. Using the AT Commands = 697 697 931 + 698 698 == 4.1 Access AT Commands == 699 699 700 -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/]] 701 701 935 +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]] 702 702 937 + 703 703 AT+<CMD>? : Help on <CMD> 704 704 705 705 AT+<CMD> : Run <CMD> ... ... @@ -739,7 +739,24 @@ 739 739 740 740 AT+SERVADDR : Server Address 741 741 977 +AT+TR : Get or Set record time 742 742 979 +AT+APN : Get or set the APN 980 + 981 +AT+FBAND : Get or Set whether to automatically modify the frequency band 982 + 983 +AT+DNSCFG : Get or Set DNS Server 984 + 985 +AT+GETSENSORVALUE : Returns the current sensor measurement 986 + 987 +AT+NOUD : Get or Set the number of data to be uploaded 988 + 989 +AT+CDP : Read or Clear cached data 990 + 991 +AT+SHTEMP: Get or Set alarm of temp 992 + 993 +AT+SHHUM: Get or Set alarm of moisture 994 + 743 743 (% style="color:#037691" %)**COAP Management** 744 744 745 745 AT+URI : Resource parameters ... ... @@ -773,6 +773,7 @@ 773 773 774 774 = 5. FAQ = 775 775 1028 + 776 776 == 5.1 How to Upgrade Firmware == 777 777 778 778 ... ... @@ -787,13 +787,16 @@ 787 787 ((( 788 788 789 789 790 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 1043 +((( 1044 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 791 791 ))) 1046 +))) 792 792 793 793 794 794 795 795 = 6. Trouble Shooting = 796 796 1052 + 797 797 == 6.1 Connection problem when uploading firmware == 798 798 799 799 ... ... @@ -809,6 +809,7 @@ 809 809 810 810 == 6.2 AT Command input doesn't work == 811 811 1068 + 812 812 ((( 813 813 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. 814 814 ... ... @@ -858,5 +858,6 @@ 858 858 859 859 = 9. Support = 860 860 1118 + 861 861 * 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. 862 862 * 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