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,21 +17,35 @@ 17 17 18 18 = 1. Introduction = 19 19 20 + 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 22 22 ((( 23 23 24 24 26 +((( 25 25 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*. 28 +))) 26 26 30 +((( 27 27 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. 32 +))) 28 28 34 +((( 29 29 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 +))) 30 30 38 +((( 31 31 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). 40 +))) 32 32 42 +((( 43 + 44 +))) 33 33 46 +((( 34 34 ~* make sure you have NB-IoT coverage locally. 48 +))) 35 35 36 36 37 37 ))) ... ... @@ -42,6 +42,7 @@ 42 42 43 43 == 1.2 Features == 44 44 59 + 45 45 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 46 * Monitor Temperature & Humidity via SHT31 47 47 * AT Commands to change parameters ... ... @@ -54,6 +54,7 @@ 54 54 * 8500mAh Battery for long term use 55 55 56 56 72 + 57 57 == 1.3 Specification == 58 58 59 59 ... ... @@ -73,7 +73,6 @@ 73 73 74 74 (% style="color:#037691" %)**Battery:** 75 75 76 - 77 77 * Li/SOCI2 un-chargeable battery 78 78 * Capacity: 8500mAh 79 79 * Self Discharge: <1% / Year @ 25°C ... ... @@ -81,8 +81,10 @@ 81 81 * Max boost current: 2A, 1 second 82 82 83 83 99 + 84 84 == 1.4 Applications == 85 85 102 + 86 86 * Smart Buildings & Home Automation 87 87 * Logistics and Supply Chain Management 88 88 * Smart Metering ... ... @@ -94,15 +94,20 @@ 94 94 95 95 96 96 97 -== 1.5 Pin Definitions == 98 98 115 +== 1.5 Pin Definitions & Switch == 116 + 117 + 99 99 N95S31B use the mother board from NBSN95 which as below. 100 100 120 + 101 101 [[image:image-20220709144723-1.png]] 102 102 103 103 124 + 104 104 === 1.5.1 Jumper JP2 === 105 105 127 + 106 106 Power on Device when put this jumper. 107 107 108 108 ... ... @@ -109,14 +109,20 @@ 109 109 110 110 === 1.5.2 BOOT MODE / SW1 === 111 111 112 -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. 113 113 114 -2) Flash: work mode, device starts to work and send out console output for further debug 135 +((( 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. 137 +))) 115 115 139 +((( 140 +**2) Flash:** work mode, device starts to work and send out console output for further debug 141 +))) 116 116 117 117 144 + 118 118 === 1.5.3 Reset Button === 119 119 147 + 120 120 Press to reboot the device. 121 121 122 122 ... ... @@ -123,13 +123,18 @@ 123 123 124 124 === 1.5.4 LED === 125 125 154 + 126 126 It will flash: 127 127 128 -1. When boot the device in flash mode 129 -1. Send an uplink packet 157 +1. When boot the device in flash mode 130 130 159 +2. Send an uplink packet 160 + 161 + 162 + 131 131 = 2. Use N95S31B to communicate with IoT Server = 132 132 165 + 133 133 == 2.1 How it works == 134 134 135 135 ... ... @@ -146,7 +146,7 @@ 146 146 147 147 ))) 148 148 149 -[[image:1657 350248151-650.png]]182 +[[image:1657520100595-569.png]] 150 150 151 151 ((( 152 152 ... ... @@ -162,26 +162,49 @@ 162 162 [[image:image-20220709150546-2.png]] 163 163 164 164 198 + 165 165 === 2.2.1 Test Requirement === 166 166 167 167 202 +((( 168 168 To use N95S31B in your city, make sure meet below requirements: 204 +))) 169 169 170 -* Your local operator has already distributed a NB-IoT Network there. 171 -* The local NB-IoT network used the band that N95S31B supports. 172 -* 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 +))) 173 173 216 +((( 174 174 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 218 +))) 175 175 220 +((( 176 176 N95S31B supports different communication protocol such as : 222 +))) 177 177 178 178 ((( 179 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 180 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 181 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 182 -* 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 +))) 183 183 238 +((( 184 184 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 +))) 185 185 186 186 187 187 ))) ... ... @@ -192,6 +192,7 @@ 192 192 193 193 === 2.2.3 Insert SIM card === 194 194 251 + 195 195 ((( 196 196 Insert the NB-IoT Card get from your provider. 197 197 ))) ... ... @@ -207,23 +207,27 @@ 207 207 208 208 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 209 209 267 + 210 210 ((( 211 211 ((( 212 212 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 + 213 213 ))) 214 214 ))) 215 215 216 216 [[image:1657351312545-300.png]] 217 217 218 -**Connection:** 219 219 220 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND279 +(% style="color:blue" %)**Connection:** 221 221 222 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD281 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 223 223 224 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD283 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 225 225 285 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 226 226 287 + 227 227 In the PC, use below serial tool settings: 228 228 229 229 * Baud: (% style="color:green" %)**9600** ... ... @@ -238,8 +238,9 @@ 238 238 239 239 [[image:1657329814315-101.png]] 240 240 302 + 241 241 ((( 242 -(% 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]]** 243 243 ))) 244 244 245 245 ... ... @@ -246,9 +246,10 @@ 246 246 247 247 === 2.2.5 Use CoAP protocol to uplink data === 248 248 249 -(% 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/]] 250 250 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/]]** 251 251 314 + 252 252 ((( 253 253 **Use below commands:** 254 254 ))) ... ... @@ -257,10 +257,10 @@ 257 257 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 258 258 ))) 259 259 * ((( 260 -(% 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 261 261 ))) 262 262 * ((( 263 -(% 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 264 264 ))) 265 265 266 266 ((( ... ... @@ -296,15 +296,16 @@ 296 296 297 297 === 2.2.7 Use MQTT protocol to uplink data === 298 298 362 + 299 299 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 300 300 301 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 302 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 303 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 304 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 305 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 306 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 307 -* (% 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 308 308 309 309 [[image:1657352634421-276.png]] 310 310 ... ... @@ -311,6 +311,7 @@ 311 311 312 312 [[image:1657352645687-385.png]] 313 313 378 + 314 314 ((( 315 315 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. 316 316 ))) ... ... @@ -324,6 +324,7 @@ 324 324 325 325 === 2.2.8 Use TCP protocol to uplink data === 326 326 392 + 327 327 This feature is supported since firmware version v110 328 328 329 329 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -338,6 +338,7 @@ 338 338 339 339 === 2.2.9 Change Update Interval === 340 340 407 + 341 341 User can use below command to change the (% style="color:green" %)**uplink interval**. 342 342 343 343 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -346,56 +346,102 @@ 346 346 347 347 ))) 348 348 416 +((( 417 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 418 +))) 349 349 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 +))) 350 350 424 + 425 + 351 351 == 2.3 Uplink Payload == 352 352 353 353 354 -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 +))) 355 355 356 356 434 +((( 357 357 For example: 436 +))) 358 358 359 - (% 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 +))) 360 360 361 361 443 +((( 362 362 The uplink payloads are composed in ASCII String. For example: 445 +))) 363 363 447 +((( 364 364 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 449 +))) 365 365 451 +((( 366 366 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 453 +))) 367 367 368 368 456 +((( 369 369 (% style="color:red" %)**NOTE:** 458 +))) 370 370 371 371 (% style="color:red" %) 372 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 373 -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.** 374 374 467 + 468 + 469 + 470 +))) 471 + 375 375 === 2.3.1 Payload Analyze === 376 376 474 + 475 +==== 2.3.1.1 Before Firmware v1.2 ==== 476 + 477 + 377 377 N95S31B uplink payload includes in total 21 bytes 378 378 379 379 380 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 381 -|=(% style="width: 60px;" %)((( 382 -**Size(bytes)** 383 -)))|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 384 -|(% 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" %)((( 484 +((( 385 385 Reserve/ Same as NBSN95 CFGMOD=1 486 +))) 386 386 488 +((( 387 387 No function here. 388 -)))|(% style="width:77px" %)((( 490 +))) 491 +)))|(% style="width:102px" %)((( 492 +((( 389 389 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 494 +))) 390 390 496 +((( 391 391 By SHT31 392 -)))|(% style="width:80px" %)((( 498 +))) 499 +)))|(% style="width:81px" %)((( 500 +((( 393 393 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 502 +))) 394 394 504 +((( 395 395 By SHT31 396 396 ))) 507 +))) 397 397 398 398 ((( 510 + 511 + 399 399 ((( 400 400 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 401 401 ))) ... ... @@ -405,29 +405,88 @@ 405 405 [[image:1657354294009-643.png]] 406 406 407 407 408 -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** 409 409 410 -* Device ID: 0x724031607457 = 724031607457 411 -* Version: 0x006e=110=1.1.0 523 +**where:** 412 412 413 -* BAT: 0x0ccd = 3277 mV = 3.277V 414 -* Signal: 0x1b = 27 415 -* Model: 0x01 = 1 416 -* 0x00dc000ccc= reserve, ignore in N95S31B 417 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 418 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 525 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 419 419 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 + 420 420 ((( 421 421 422 -))) 423 423 424 - (((544 + 425 425 426 426 ))) 427 427 548 +==== 2.3.1.2 Since Firmware v1.2 ==== 428 428 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 + 429 429 === 2.3.2 Device ID === 430 430 602 + 431 431 ((( 432 432 By default, the Device ID equal to the last 6 bytes of IMEI. 433 433 ))) ... ... @@ -434,10 +434,12 @@ 434 434 435 435 ((( 436 436 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 609 + 610 + 437 437 ))) 438 438 439 439 ((( 440 -**Example:** 614 +(% style="color:blue" %)**Example:** 441 441 ))) 442 442 443 443 ((( ... ... @@ -445,22 +445,47 @@ 445 445 ))) 446 446 447 447 ((( 448 -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 + 449 449 ))) 450 450 627 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 451 451 452 452 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 + 453 453 === 2.3.3 Version Info === 454 454 455 455 644 +((( 456 456 These bytes include the hardware and software version. 646 +))) 457 457 648 +((( 458 458 Higher byte: Specify hardware version: always 0x00 for N95S31B 650 +))) 459 459 652 +((( 460 460 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 654 +))) 461 461 656 +((( 657 + 658 +))) 462 462 660 +((( 463 463 For example: 0x00 6E: this device is N95S31B with firmware version 110. 662 +))) 464 464 465 465 ((( 466 466 ... ... @@ -469,6 +469,7 @@ 469 469 470 470 === 2.3.4 Battery Info === 471 471 671 + 472 472 ((( 473 473 Ex1: 0x0B45 = 2885mV 474 474 ))) ... ... @@ -481,6 +481,7 @@ 481 481 482 482 === 2.3.5 Signal Strength === 483 483 684 + 484 484 ((( 485 485 NB-IoT Network signal Strength. 486 486 ))) ... ... @@ -513,6 +513,7 @@ 513 513 514 514 === 2.3.6 Temperature & Humidity === 515 515 717 + 516 516 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 517 517 518 518 [[image:image-20220709161741-3.png]] ... ... @@ -531,8 +531,9 @@ 531 531 532 532 == 2.4 Downlink Payload == 533 533 534 -By default, NDDS75 prints the downlink payload to console port. 535 535 737 +By default, N95S31B prints the downlink payload to console port. 738 + 536 536 [[image:image-20220709100028-1.png]] 537 537 538 538 ... ... @@ -569,7 +569,7 @@ 569 569 ))) 570 570 571 571 ((( 572 -If payload = 0x04FF, it will reset the DDS75775 +If payload = 0x04FF, it will reset the N95S31B 573 573 ))) 574 574 575 575 ... ... @@ -581,11 +581,74 @@ 581 581 582 582 583 583 584 -== 2.5 BatteryAnalysis==787 +== 2.5 Humidity and Temperature alarm function == 585 585 586 -=== 2.5.1 Battery Type === 587 587 790 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 588 588 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 + 589 589 ((( 590 590 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. 591 591 ))) ... ... @@ -608,10 +608,11 @@ 608 608 609 609 610 610 611 -=== 2. 5.2 Power consumption Analyze ===877 +=== 2.8.2 Power consumption Analyze === 612 612 879 + 613 613 ((( 614 -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. 615 615 ))) 616 616 617 617 ((( ... ... @@ -619,8 +619,9 @@ 619 619 ))) 620 620 621 621 622 -=== 2. 5.3 Battery Note ===889 +=== 2.8.3 Battery Note === 623 623 891 + 624 624 ((( 625 625 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. 626 626 ))) ... ... @@ -627,7 +627,7 @@ 627 627 628 628 629 629 630 -=== 2. 5.4 Replace the battery ===898 +=== 2.8.4 Replace the battery === 631 631 632 632 633 633 ((( ... ... @@ -643,6 +643,7 @@ 643 643 644 644 = 3. Access NB-IoT Module = 645 645 914 + 646 646 ((( 647 647 Users can directly access the AT command set of the NB-IoT module. 648 648 ))) ... ... @@ -649,6 +649,8 @@ 649 649 650 650 ((( 651 651 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 + 652 652 ))) 653 653 654 654 [[image:1657333200519-600.png]] ... ... @@ -657,11 +657,13 @@ 657 657 658 658 = 4. Using the AT Commands = 659 659 931 + 660 660 == 4.1 Access AT Commands == 661 661 662 -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/]] 663 663 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]] 664 664 937 + 665 665 AT+<CMD>? : Help on <CMD> 666 666 667 667 AT+<CMD> : Run <CMD> ... ... @@ -701,7 +701,24 @@ 701 701 702 702 AT+SERVADDR : Server Address 703 703 977 +AT+TR : Get or Set record time 704 704 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 + 705 705 (% style="color:#037691" %)**COAP Management** 706 706 707 707 AT+URI : Resource parameters ... ... @@ -735,6 +735,7 @@ 735 735 736 736 = 5. FAQ = 737 737 1028 + 738 738 == 5.1 How to Upgrade Firmware == 739 739 740 740 ... ... @@ -749,13 +749,16 @@ 749 749 ((( 750 750 751 751 752 -(% 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.** 753 753 ))) 1046 +))) 754 754 755 755 756 756 757 757 = 6. Trouble Shooting = 758 758 1052 + 759 759 == 6.1 Connection problem when uploading firmware == 760 760 761 761 ... ... @@ -771,6 +771,7 @@ 771 771 772 772 == 6.2 AT Command input doesn't work == 773 773 1068 + 774 774 ((( 775 775 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. 776 776 ... ... @@ -820,5 +820,6 @@ 820 820 821 821 = 9. Support = 822 822 1118 + 823 823 * 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. 824 824 * 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