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
-
... ... @@ -9,6 +9,7 @@ 9 9 10 10 **Table of Contents:** 11 11 12 +{{toc/}} 12 12 13 13 14 14 ... ... @@ -21,16 +21,29 @@ 21 21 ((( 22 22 23 23 25 +((( 24 24 The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*. 27 +))) 25 25 29 +((( 26 26 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. 31 +))) 27 27 33 +((( 28 28 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 +))) 29 29 37 +((( 30 30 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). 39 +))) 31 31 41 +((( 42 + 43 +))) 32 32 45 +((( 33 33 ~* make sure you have NB-IoT coverage locally. 47 +))) 34 34 35 35 36 36 ))) ... ... @@ -41,6 +41,7 @@ 41 41 42 42 == 1.2 Features == 43 43 58 + 44 44 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 45 45 * Monitor Temperature & Humidity via SHT31 46 46 * AT Commands to change parameters ... ... @@ -53,8 +53,6 @@ 53 53 * 8500mAh Battery for long term use 54 54 55 55 56 - 57 - 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -74,7 +74,6 @@ 74 74 75 75 (% style="color:#037691" %)**Battery:** 76 76 77 - 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -82,10 +82,9 @@ 82 82 * Max boost current: 2A, 1 second 83 83 84 84 85 - 86 - 87 87 == 1.4 Applications == 88 88 99 + 89 89 * Smart Buildings & Home Automation 90 90 * Logistics and Supply Chain Management 91 91 * Smart Metering ... ... @@ -97,41 +97,49 @@ 97 97 98 98 99 99 100 -== 1.5 Pin Definitions == 111 +== 1.5 Pin Definitions & Switch == 101 101 113 + 102 102 N95S31B use the mother board from NBSN95 which as below. 103 103 116 + 104 104 [[image:image-20220709144723-1.png]] 105 105 106 106 107 107 === 1.5.1 Jumper JP2 === 108 108 122 + 109 109 Power on Device when put this jumper. 110 110 111 111 112 - 113 113 === 1.5.2 BOOT MODE / SW1 === 114 114 115 -1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 116 116 117 -2) Flash: work mode, device starts to work and send out console output for further debug 129 +((( 130 +**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. 131 +))) 118 118 133 +((( 134 +**2) Flash:** work mode, device starts to work and send out console output for further debug 135 +))) 119 119 120 120 121 121 === 1.5.3 Reset Button === 122 122 140 + 123 123 Press to reboot the device. 124 124 125 125 126 - 127 127 === 1.5.4 LED === 128 128 146 + 129 129 It will flash: 130 130 131 -1. When boot the device in flash mode 132 -1. Send an uplink packet 149 +1. When boot the device in flash mode 133 133 151 +2. Send an uplink packet 134 134 153 + 135 135 = 2. Use N95S31B to communicate with IoT Server = 136 136 137 137 == 2.1 How it works == ... ... @@ -150,7 +150,7 @@ 150 150 151 151 ))) 152 152 153 -[[image:1657 350248151-650.png]]172 +[[image:1657520100595-569.png]] 154 154 155 155 ((( 156 156 ... ... @@ -159,7 +159,6 @@ 159 159 160 160 == 2.2 Configure the N95S31B == 161 161 162 - 163 163 === 2.2.1 Power On N95S31B === 164 164 165 165 ... ... @@ -166,26 +166,48 @@ 166 166 [[image:image-20220709150546-2.png]] 167 167 168 168 169 -=== 2.2. 1Test Requirement ===187 +=== 2.2.2 Test Requirement === 170 170 171 171 190 +((( 172 172 To use N95S31B in your city, make sure meet below requirements: 192 +))) 173 173 174 -* Your local operator has already distributed a NB-IoT Network there. 175 -* The local NB-IoT network used the band that N95S31B supports. 176 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 194 +* ((( 195 +Your local operator has already distributed a NB-IoT Network there. 196 +))) 197 +* ((( 198 +The local NB-IoT network used the band that N95S31B supports. 199 +))) 200 +* ((( 201 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 202 +))) 177 177 204 +((( 178 178 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 206 +))) 179 179 208 +((( 180 180 N95S31B supports different communication protocol such as : 210 +))) 181 181 182 182 ((( 183 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 184 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 185 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 186 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 213 +* ((( 214 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 215 +))) 216 +* ((( 217 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 218 +))) 219 +* ((( 220 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 221 +))) 222 +* ((( 223 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 224 +))) 187 187 226 +((( 188 188 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. 228 +))) 189 189 190 190 191 191 ))) ... ... @@ -193,9 +193,9 @@ 193 193 [[image:1657350625843-586.png]] 194 194 195 195 196 - 197 197 === 2.2.3 Insert SIM card === 198 198 238 + 199 199 ((( 200 200 Insert the NB-IoT Card get from your provider. 201 201 ))) ... ... @@ -208,26 +208,29 @@ 208 208 [[image:1657351240556-536.png]] 209 209 210 210 211 - 212 212 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 213 213 253 + 214 214 ((( 215 215 ((( 216 216 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. 257 + 258 + 217 217 ))) 218 218 ))) 219 219 220 220 [[image:1657351312545-300.png]] 221 221 222 -**Connection:** 223 223 224 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND265 +(% style="color:blue" %)**Connection:** 225 225 226 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD267 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 227 227 228 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD269 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 229 229 271 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 230 230 273 + 231 231 In the PC, use below serial tool settings: 232 232 233 233 * Baud: (% style="color:green" %)**9600** ... ... @@ -242,17 +242,18 @@ 242 242 243 243 [[image:1657329814315-101.png]] 244 244 288 + 245 245 ((( 246 -(% 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/]]290 +(% 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]]** 247 247 ))) 248 248 249 249 250 - 251 251 === 2.2.5 Use CoAP protocol to uplink data === 252 252 253 -(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 254 254 297 +(% 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/]]** 255 255 299 + 256 256 ((( 257 257 **Use below commands:** 258 258 ))) ... ... @@ -261,10 +261,10 @@ 261 261 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 262 262 ))) 263 263 * ((( 264 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 308 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 265 265 ))) 266 266 * ((( 267 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 311 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 268 268 ))) 269 269 270 270 ((( ... ... @@ -283,7 +283,6 @@ 283 283 [[image:1657352185396-303.png]] 284 284 285 285 286 - 287 287 === 2.2.6 Use UDP protocol to uplink data(Default protocol) === 288 288 289 289 ... ... @@ -297,18 +297,18 @@ 297 297 [[image:1657352403317-397.png]] 298 298 299 299 300 - 301 301 === 2.2.7 Use MQTT protocol to uplink data === 302 302 345 + 303 303 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 304 304 305 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 306 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 307 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 308 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 309 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 310 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 311 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 348 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 349 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 350 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 351 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 352 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 353 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ Set the sending topic of MQTT 354 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ Set the subscription topic of MQTT 312 312 313 313 [[image:1657352634421-276.png]] 314 314 ... ... @@ -315,6 +315,7 @@ 315 315 316 316 [[image:1657352645687-385.png]] 317 317 361 + 318 318 ((( 319 319 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. 320 320 ))) ... ... @@ -325,9 +325,9 @@ 325 325 ))) 326 326 327 327 328 - 329 329 === 2.2.8 Use TCP protocol to uplink data === 330 330 374 + 331 331 This feature is supported since firmware version v110 332 332 333 333 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -339,9 +339,9 @@ 339 339 [[image:1657352914475-252.png]] 340 340 341 341 342 - 343 343 === 2.2.9 Change Update Interval === 344 344 388 + 345 345 User can use below command to change the (% style="color:green" %)**uplink interval**. 346 346 347 347 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -350,58 +350,99 @@ 350 350 351 351 ))) 352 352 397 +((( 398 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 399 +))) 353 353 401 +((( 402 +(% 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).** 403 +))) 354 354 405 + 355 355 == 2.3 Uplink Payload == 356 356 357 357 358 -NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes. 409 +((( 410 +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. 411 +))) 359 359 360 360 414 +((( 361 361 For example: 416 +))) 362 362 363 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 418 +((( 419 + (% 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. 420 +))) 364 364 365 365 423 +((( 366 366 The uplink payloads are composed in ASCII String. For example: 425 +))) 367 367 427 +((( 368 368 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 429 +))) 369 369 431 +((( 370 370 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 433 +))) 371 371 372 372 436 +((( 373 373 (% style="color:red" %)**NOTE:** 438 +))) 374 374 375 375 (% style="color:red" %) 376 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 377 -1. By default, the device will send an uplink message every 1 hour. 441 +1. ((( 442 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 443 +))) 444 +1. ((( 445 +**By default, the device will send an uplink message every 1 hour.** 378 378 379 379 448 + 449 +))) 380 380 381 381 === 2.3.1 Payload Analyze === 382 382 453 +==== 2.3.1.1 Before Firmware v1.2 ==== 454 + 455 + 383 383 N95S31B uplink payload includes in total 21 bytes 384 384 385 385 386 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 387 -|=(% style="width: 60px;" %)((( 388 -**Size(bytes)** 389 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1** 390 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 459 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 460 +|=(% 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** 461 +|(% 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" %)((( 462 +((( 391 391 Reserve/ Same as NBSN95 CFGMOD=1 464 +))) 392 392 466 +((( 393 393 No function here. 394 -)))|(% style="width:77px" %)((( 395 -[[Temperature >>||anchor="H2.4.5A0Distance"]] 468 +))) 469 +)))|(% style="width:102px" %)((( 470 +((( 471 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 472 +))) 396 396 474 +((( 397 397 By SHT31 398 -)))|(% style="width:80px" %)((( 399 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 476 +))) 477 +)))|(% style="width:81px" %)((( 478 +((( 479 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 480 +))) 400 400 482 +((( 401 401 By SHT31 402 402 ))) 485 +))) 403 403 404 404 ((( 488 + 489 + 405 405 ((( 406 406 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 407 407 ))) ... ... @@ -411,29 +411,89 @@ 411 411 [[image:1657354294009-643.png]] 412 412 413 413 414 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:499 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 415 415 416 -* Device ID: 0x724031607457 = 724031607457 417 -* Version: 0x006e=110=1.1.0 501 +**where:** 418 418 419 -* BAT: 0x0ccd = 3277 mV = 3.277V 420 -* Signal: 0x1b = 27 421 -* Model: 0x01 = 1 422 -* 0x00dc000ccc= reserve, ignore in N95S31B 423 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 424 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 503 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 425 425 505 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 506 + 507 +* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 508 + 509 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 510 + 511 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 512 + 513 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 514 + 515 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 516 + 517 +* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 518 + 426 426 ((( 427 427 428 -))) 429 429 430 - (((522 + 431 431 432 432 ))) 433 433 526 +==== 2.3.1.2 Since Firmware v1.2 ==== 434 434 528 + 529 +In this mode, uplink payload includes 91 bytes in total by default. 530 + 531 +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. 532 + 533 + 534 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 535 +|=(% 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** 536 +|=(% 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 ..... 537 + 538 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 539 + 540 + 541 +[[image:image-20220908154949-1.png]] 542 + 543 + 544 +The payload is ASCII string, representative same HEX: 545 + 546 +**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__ ** 547 + 548 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 549 + 550 +**where:** 551 + 552 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 553 + 554 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 555 + 556 +* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 557 + 558 +* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 559 + 560 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 561 + 562 +* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 563 + 564 +* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 565 + 566 +* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 567 + 568 +* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 569 + 570 +* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 571 + 572 +* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 573 + 574 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 575 + 576 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 577 + 578 + 435 435 === 2.3.2 Device ID === 436 436 581 + 437 437 ((( 438 438 By default, the Device ID equal to the last 6 bytes of IMEI. 439 439 ))) ... ... @@ -440,10 +440,12 @@ 440 440 441 441 ((( 442 442 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 588 + 589 + 443 443 ))) 444 444 445 445 ((( 446 -**Example:** 593 +(% style="color:blue" %)**Example:** 447 447 ))) 448 448 449 449 ((( ... ... @@ -451,30 +451,54 @@ 451 451 ))) 452 452 453 453 ((( 454 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 601 +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. 602 + 603 + 455 455 ))) 456 456 606 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 457 457 458 458 609 +By default, the Device ID equal to the last 15 bits of IMEI. 610 + 611 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 612 + 613 + 614 +(% style="color:blue" %)**Example:** 615 + 616 +AT+DEUI=868411056754138 617 + 618 + 459 459 === 2.3.3 Version Info === 460 460 461 461 622 +((( 462 462 These bytes include the hardware and software version. 624 +))) 463 463 626 +((( 464 464 Higher byte: Specify hardware version: always 0x00 for N95S31B 628 +))) 465 465 630 +((( 466 466 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 632 +))) 467 467 634 +((( 635 + 636 +))) 468 468 638 +((( 469 469 For example: 0x00 6E: this device is N95S31B with firmware version 110. 640 +))) 470 470 471 471 ((( 472 472 473 473 ))) 474 474 475 - 476 476 === 2.3.4 Battery Info === 477 477 648 + 478 478 ((( 479 479 Ex1: 0x0B45 = 2885mV 480 480 ))) ... ... @@ -484,9 +484,9 @@ 484 484 ))) 485 485 486 486 487 - 488 488 === 2.3.5 Signal Strength === 489 489 660 + 490 490 ((( 491 491 NB-IoT Network signal Strength. 492 492 ))) ... ... @@ -516,9 +516,9 @@ 516 516 ))) 517 517 518 518 519 - 520 520 === 2.3.6 Temperature & Humidity === 521 521 692 + 522 522 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 523 523 524 524 [[image:image-20220709161741-3.png]] ... ... @@ -534,10 +534,10 @@ 534 534 Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 535 535 536 536 708 +== 2.4 Downlink Payload == 537 537 538 -== 2.5 Downlink Payload == 539 539 540 -By default, DDS75 prints the downlink payload to console port.711 +By default, N95S31B prints the downlink payload to console port. 541 541 542 542 [[image:image-20220709100028-1.png]] 543 543 ... ... @@ -575,7 +575,7 @@ 575 575 ))) 576 576 577 577 ((( 578 -If payload = 0x04FF, it will reset the DDS75749 +If payload = 0x04FF, it will reset the N95S31B 579 579 ))) 580 580 581 581 ... ... @@ -586,69 +586,78 @@ 586 586 ))) 587 587 588 588 760 +== 2.5 Humidity and Temperature alarm function == 589 589 590 -== 2.5 Battery Analysis == 591 591 592 - ===2.5.1BatteryType===763 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 593 593 594 594 595 -((( 596 -The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 597 -))) 766 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 598 598 599 -((( 600 -The battery is designed to last for several years depends on the actually use environment and update interval. 601 -))) 602 602 603 -((( 604 -The battery related documents as below: 605 -))) 769 +² When min=0, and max≠0, Alarm higher than max 606 606 607 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 608 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 609 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 771 +² When min≠0, and max=0, Alarm lower than min 610 610 611 -((( 612 -[[image:image-20220709101450-2.png]] 613 -))) 773 +² When min≠0 and max≠0, Alarm higher than max or lower than min 614 614 615 615 776 + (% style="color:blue" %)**Example:** 616 616 617 - ===2.5.2PowerconsumptionAnalyze===778 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 618 618 619 -((( 620 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 621 -))) 622 622 623 -((( 624 - 625 -))) 781 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 626 626 783 +² When min=0, and max≠0, Alarm higher than max 627 627 628 - ===2.5.3BatteryNote===785 +² When min≠0, and max=0, Alarm lower than min 629 629 630 -((( 631 -The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased. 632 -))) 787 +² When min≠0 and max≠0, Alarm higher than max or lower than min 633 633 634 634 790 +**~ (% style="color:blue" %)Example:(%%)** 635 635 636 - ===2.5.4Replacethebattery===792 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 637 637 638 638 639 -((( 640 -You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board. 641 -))) 795 +== 2.6 Set the number of data to be uploaded and the recording time == 642 642 643 643 644 -((( 645 -The default battery pack of N95S31B includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 646 -))) 798 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 647 647 800 +* (% 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) 801 +* (% 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. 648 648 803 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 649 649 805 +[[image:image-20221009001045-1.png||height="726" width="1009"]] 806 + 807 + 808 +== 2.7 Read or Clear cached data == 809 + 810 + 811 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 812 + 813 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 814 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 815 + 816 +[[image:image-20220908163102-2.png]] 817 + 818 + 819 += 2.8 Battery & Power Consumption = 820 + 821 + 822 +N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 823 + 824 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 825 + 826 + 827 + 828 + 650 650 = 3. Access NB-IoT Module = 651 651 831 + 652 652 ((( 653 653 Users can directly access the AT command set of the NB-IoT module. 654 654 ))) ... ... @@ -655,19 +655,21 @@ 655 655 656 656 ((( 657 657 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/]] 838 + 839 + 658 658 ))) 659 659 660 660 [[image:1657333200519-600.png]] 661 661 662 662 663 - 664 664 = 4. Using the AT Commands = 665 665 666 666 == 4.1 Access AT Commands == 667 667 668 -See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]] 669 669 850 +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]] 670 670 852 + 671 671 AT+<CMD>? : Help on <CMD> 672 672 673 673 AT+<CMD> : Run <CMD> ... ... @@ -707,7 +707,24 @@ 707 707 708 708 AT+SERVADDR : Server Address 709 709 892 +AT+TR : Get or Set record time 710 710 894 +AT+APN : Get or set the APN 895 + 896 +AT+FBAND : Get or Set whether to automatically modify the frequency band 897 + 898 +AT+DNSCFG : Get or Set DNS Server 899 + 900 +AT+GETSENSORVALUE : Returns the current sensor measurement 901 + 902 +AT+NOUD : Get or Set the number of data to be uploaded 903 + 904 +AT+CDP : Read or Clear cached data 905 + 906 +AT+SHTEMP: Get or Set alarm of temp 907 + 908 +AT+SHHUM: Get or Set alarm of moisture 909 + 711 711 (% style="color:#037691" %)**COAP Management** 712 712 713 713 AT+URI : Resource parameters ... ... @@ -738,7 +738,6 @@ 738 738 AT+PWORD : Serial Access Password 739 739 740 740 741 - 742 742 = 5. FAQ = 743 743 744 744 == 5.1 How to Upgrade Firmware == ... ... @@ -755,11 +755,12 @@ 755 755 ((( 756 756 757 757 758 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 956 +((( 957 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 759 759 ))) 959 +))) 760 760 761 761 762 - 763 763 = 6. Trouble Shooting = 764 764 765 765 == 6.1 Connection problem when uploading firmware == ... ... @@ -774,9 +774,9 @@ 774 774 775 775 ))) 776 776 777 - 778 778 == 6.2 AT Command input doesn't work == 779 779 978 + 780 780 ((( 781 781 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. 782 782 ... ... @@ -783,18 +783,12 @@ 783 783 784 784 ))) 785 785 786 - 787 787 = 7. Order Info = 788 788 789 789 790 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B** 988 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 791 791 792 792 793 -(% class="wikigeneratedid" %) 794 -((( 795 - 796 -))) 797 - 798 798 = 8. Packing Info = 799 799 800 800 ((( ... ... @@ -802,7 +802,7 @@ 802 802 803 803 (% style="color:#037691" %)**Package Includes**: 804 804 805 -* NS E01DistanceDetectSensorNode x 1998 +* N95S31B NB-IoT Temperature and Humidity Sensor 806 806 * External antenna x 1 807 807 ))) 808 808 ... ... @@ -811,21 +811,24 @@ 811 811 812 812 (% style="color:#037691" %)**Dimension and weight**: 813 813 814 - 815 815 * Device Size: 13.0 x 5 x 4.5 cm 816 816 * Device Weight: 150g 817 -* Package Size / pcs : 1 5x12x 5.5cm818 -* Weight / pcs : 220g1009 +* Package Size / pcs : 14.0 x 8x 5 cm 1010 +* Weight / pcs : 180g 819 819 ))) 820 820 821 821 ((( 822 822 823 823 824 - 825 825 826 826 ))) 827 827 828 828 = 9. Support = 829 829 1021 + 830 830 * 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. 831 831 * 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]] 1024 + 1025 + 1026 + 1027 +
- 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