Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 4 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Bei - Content
-
... ... @@ -22,16 +22,29 @@ 22 22 ((( 23 23 24 24 25 +((( 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*. 27 +))) 26 26 29 +((( 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. 31 +))) 28 28 33 +((( 29 29 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 +))) 30 30 37 +((( 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). 39 +))) 32 32 41 +((( 42 + 43 +))) 33 33 45 +((( 34 34 ~* make sure you have NB-IoT coverage locally. 47 +))) 35 35 36 36 37 37 ))) ... ... @@ -42,6 +42,7 @@ 42 42 43 43 == 1.2 Features == 44 44 58 + 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,7 +54,6 @@ 54 54 * 8500mAh Battery for long term use 55 55 56 56 57 - 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -65,16 +65,15 @@ 65 65 66 66 (% style="color:#037691" %)**NB-IoT Spec:** 67 67 68 -* -B1 @H-FDD: 2100MHz69 -* -B3 @H-FDD: 1800MHz70 -* -B8 @H-FDD: 900MHz71 -* -B5 @H-FDD: 850MHz72 -* -B20 @H-FDD: 800MHz73 -* -B28 @H-FDD: 700MHz81 +* B1 @H-FDD: 2100MHz 82 +* B3 @H-FDD: 1800MHz 83 +* B8 @H-FDD: 900MHz 84 +* B5 @H-FDD: 850MHz 85 +* B20 @H-FDD: 800MHz 86 +* B28 @H-FDD: 700MHz 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,9 +82,9 @@ 82 82 * Max boost current: 2A, 1 second 83 83 84 84 85 - 86 86 == 1.4 Applications == 87 87 99 + 88 88 * Smart Buildings & Home Automation 89 89 * Logistics and Supply Chain Management 90 90 * Smart Metering ... ... @@ -96,40 +96,49 @@ 96 96 97 97 98 98 99 -== 1.5 Pin Definitions == 111 +== 1.5 Pin Definitions & Switch == 100 100 113 + 101 101 N95S31B use the mother board from NBSN95 which as below. 102 102 116 + 103 103 [[image:image-20220709144723-1.png]] 104 104 105 105 106 106 === 1.5.1 Jumper JP2 === 107 107 122 + 108 108 Power on Device when put this jumper. 109 109 110 110 111 - 112 112 === 1.5.2 BOOT MODE / SW1 === 113 113 114 -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. 115 115 116 -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 +))) 117 117 133 +((( 134 +**2) Flash:** work mode, device starts to work and send out console output for further debug 135 +))) 118 118 119 119 120 120 === 1.5.3 Reset Button === 121 121 140 + 122 122 Press to reboot the device. 123 123 124 124 125 - 126 126 === 1.5.4 LED === 127 127 146 + 128 128 It will flash: 129 129 130 -1. When boot the device in flash mode 131 -1. Send an uplink packet 149 +1. When boot the device in flash mode 132 132 151 +2. Send an uplink packet 152 + 153 + 133 133 = 2. Use N95S31B to communicate with IoT Server = 134 134 135 135 == 2.1 How it works == ... ... @@ -148,7 +148,7 @@ 148 148 149 149 ))) 150 150 151 -[[image:1657 350248151-650.png]]172 +[[image:1657520100595-569.png]] 152 152 153 153 ((( 154 154 ... ... @@ -157,7 +157,6 @@ 157 157 158 158 == 2.2 Configure the N95S31B == 159 159 160 - 161 161 === 2.2.1 Power On N95S31B === 162 162 163 163 ... ... @@ -164,26 +164,48 @@ 164 164 [[image:image-20220709150546-2.png]] 165 165 166 166 167 -=== 2.2. 1Test Requirement ===187 +=== 2.2.2 Test Requirement === 168 168 169 169 190 +((( 170 170 To use N95S31B in your city, make sure meet below requirements: 192 +))) 171 171 172 -* Your local operator has already distributed a NB-IoT Network there. 173 -* The local NB-IoT network used the band that N95S31B supports. 174 -* 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 +))) 175 175 204 +((( 176 176 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 206 +))) 177 177 208 +((( 178 178 N95S31B supports different communication protocol such as : 210 +))) 179 179 180 180 ((( 181 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 182 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 183 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 184 -* 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 +))) 185 185 226 +((( 186 186 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 +))) 187 187 188 188 189 189 ))) ... ... @@ -191,9 +191,9 @@ 191 191 [[image:1657350625843-586.png]] 192 192 193 193 194 - 195 195 === 2.2.3 Insert SIM card === 196 196 238 + 197 197 ((( 198 198 Insert the NB-IoT Card get from your provider. 199 199 ))) ... ... @@ -206,26 +206,29 @@ 206 206 [[image:1657351240556-536.png]] 207 207 208 208 209 - 210 210 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 211 211 253 + 212 212 ((( 213 213 ((( 214 214 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 + 215 215 ))) 216 216 ))) 217 217 218 218 [[image:1657351312545-300.png]] 219 219 220 -**Connection:** 221 221 222 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND265 +(% style="color:blue" %)**Connection:** 223 223 224 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD267 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 225 225 226 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD269 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 227 227 271 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 228 228 273 + 229 229 In the PC, use below serial tool settings: 230 230 231 231 * Baud: (% style="color:green" %)**9600** ... ... @@ -240,17 +240,18 @@ 240 240 241 241 [[image:1657329814315-101.png]] 242 242 288 + 243 243 ((( 244 -(% 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]]** 245 245 ))) 246 246 247 247 248 - 249 249 === 2.2.5 Use CoAP protocol to uplink data === 250 250 251 -(% 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/]] 252 252 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/]]** 253 253 299 + 254 254 ((( 255 255 **Use below commands:** 256 256 ))) ... ... @@ -259,10 +259,10 @@ 259 259 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 260 260 ))) 261 261 * ((( 262 -(% 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 263 263 ))) 264 264 * ((( 265 -(% 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 266 266 ))) 267 267 268 268 ((( ... ... @@ -281,7 +281,6 @@ 281 281 [[image:1657352185396-303.png]] 282 282 283 283 284 - 285 285 === 2.2.6 Use UDP protocol to uplink data(Default protocol) === 286 286 287 287 ... ... @@ -295,18 +295,18 @@ 295 295 [[image:1657352403317-397.png]] 296 296 297 297 298 - 299 299 === 2.2.7 Use MQTT protocol to uplink data === 300 300 345 + 301 301 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 302 302 303 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 304 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 305 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 306 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 307 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 308 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 309 -* (% 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 310 310 311 311 [[image:1657352634421-276.png]] 312 312 ... ... @@ -313,6 +313,7 @@ 313 313 314 314 [[image:1657352645687-385.png]] 315 315 361 + 316 316 ((( 317 317 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. 318 318 ))) ... ... @@ -323,9 +323,9 @@ 323 323 ))) 324 324 325 325 326 - 327 327 === 2.2.8 Use TCP protocol to uplink data === 328 328 374 + 329 329 This feature is supported since firmware version v110 330 330 331 331 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -337,9 +337,9 @@ 337 337 [[image:1657352914475-252.png]] 338 338 339 339 340 - 341 341 === 2.2.9 Change Update Interval === 342 342 388 + 343 343 User can use below command to change the (% style="color:green" %)**uplink interval**. 344 344 345 345 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -348,57 +348,99 @@ 348 348 349 349 ))) 350 350 397 +((( 398 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 399 +))) 351 351 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 +))) 352 352 405 + 353 353 == 2.3 Uplink Payload == 354 354 355 355 356 -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 +))) 357 357 358 358 414 +((( 359 359 For example: 416 +))) 360 360 361 - (% 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 +))) 362 362 363 363 423 +((( 364 364 The uplink payloads are composed in ASCII String. For example: 425 +))) 365 365 427 +((( 366 366 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 429 +))) 367 367 431 +((( 368 368 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 433 +))) 369 369 370 370 436 +((( 371 371 (% style="color:red" %)**NOTE:** 438 +))) 372 372 373 373 (% style="color:red" %) 374 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 375 -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.** 376 376 377 377 448 + 449 +))) 450 + 378 378 === 2.3.1 Payload Analyze === 379 379 453 +==== 2.3.1.1 Before Firmware v1.2 ==== 454 + 455 + 380 380 N95S31B uplink payload includes in total 21 bytes 381 381 382 382 383 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 384 -|=(% style="width: 50px;" %)((( 385 -**Size(bytes)** 386 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 60px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**2** 387 -|(% 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" %)((( 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 +((( 388 388 Reserve/ Same as NBSN95 CFGMOD=1 464 +))) 389 389 466 +((( 390 390 No function here. 391 -)))|(% style="width:77px" %)((( 468 +))) 469 +)))|(% style="width:102px" %)((( 470 +((( 392 392 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 472 +))) 393 393 474 +((( 394 394 By SHT31 395 -)))|(% style="width:80px" %)((( 476 +))) 477 +)))|(% style="width:81px" %)((( 478 +((( 396 396 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 480 +))) 397 397 482 +((( 398 398 By SHT31 399 399 ))) 485 +))) 400 400 401 401 ((( 488 + 489 + 402 402 ((( 403 403 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 404 404 ))) ... ... @@ -408,29 +408,88 @@ 408 408 [[image:1657354294009-643.png]] 409 409 410 410 411 -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** 412 412 413 -* Device ID: 0x724031607457 = 724031607457 414 -* Version: 0x006e=110=1.1.0 501 +**where:** 415 415 416 -* BAT: 0x0ccd = 3277 mV = 3.277V 417 -* Signal: 0x1b = 27 418 -* Model: 0x01 = 1 419 -* 0x00dc000ccc= reserve, ignore in N95S31B 420 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 421 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 503 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 422 422 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 + 423 423 ((( 424 424 425 -))) 426 426 427 -((( 428 428 429 429 ))) 430 430 525 +==== 2.3.1.2 Since Firmware v1.2 ==== 431 431 527 + 528 +In this mode, uplink payload includes 91 bytes in total by default. 529 + 530 +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. 531 + 532 + 533 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 534 +|=(% 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** 535 +|=(% 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 ..... 536 + 537 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 538 + 539 + 540 +[[image:image-20220908154949-1.png]] 541 + 542 + 543 +The payload is ASCII string, representative same HEX: 544 + 545 +**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__ ** 546 + 547 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 548 + 549 +**where:** 550 + 551 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 552 + 553 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 554 + 555 +* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 556 + 557 +* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 558 + 559 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 560 + 561 +* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 562 + 563 +* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 564 + 565 +* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 566 + 567 +* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 568 + 569 +* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 570 + 571 +* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 572 + 573 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 574 + 575 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 576 + 577 + 432 432 === 2.3.2 Device ID === 433 433 580 + 434 434 ((( 435 435 By default, the Device ID equal to the last 6 bytes of IMEI. 436 436 ))) ... ... @@ -437,10 +437,12 @@ 437 437 438 438 ((( 439 439 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 587 + 588 + 440 440 ))) 441 441 442 442 ((( 443 -**Example:** 592 +(% style="color:blue" %)**Example:** 444 444 ))) 445 445 446 446 ((( ... ... @@ -448,30 +448,54 @@ 448 448 ))) 449 449 450 450 ((( 451 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 600 +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. 601 + 602 + 452 452 ))) 453 453 605 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 454 454 455 455 608 +By default, the Device ID equal to the last 15 bits of IMEI. 609 + 610 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 611 + 612 + 613 +(% style="color:blue" %)**Example:** 614 + 615 +AT+DEUI=868411056754138 616 + 617 + 456 456 === 2.3.3 Version Info === 457 457 458 458 621 +((( 459 459 These bytes include the hardware and software version. 623 +))) 460 460 625 +((( 461 461 Higher byte: Specify hardware version: always 0x00 for N95S31B 627 +))) 462 462 629 +((( 463 463 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 631 +))) 464 464 633 +((( 634 + 635 +))) 465 465 637 +((( 466 466 For example: 0x00 6E: this device is N95S31B with firmware version 110. 639 +))) 467 467 468 468 ((( 469 469 470 470 ))) 471 471 472 - 473 473 === 2.3.4 Battery Info === 474 474 647 + 475 475 ((( 476 476 Ex1: 0x0B45 = 2885mV 477 477 ))) ... ... @@ -481,9 +481,9 @@ 481 481 ))) 482 482 483 483 484 - 485 485 === 2.3.5 Signal Strength === 486 486 659 + 487 487 ((( 488 488 NB-IoT Network signal Strength. 489 489 ))) ... ... @@ -513,9 +513,9 @@ 513 513 ))) 514 514 515 515 516 - 517 517 === 2.3.6 Temperature & Humidity === 518 518 691 + 519 519 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 520 520 521 521 [[image:image-20220709161741-3.png]] ... ... @@ -531,11 +531,11 @@ 531 531 Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 532 532 533 533 534 - 535 535 == 2.4 Downlink Payload == 536 536 537 -By default, NDDS75 prints the downlink payload to console port. 538 538 710 +By default, N95S31B prints the downlink payload to console port. 711 + 539 539 [[image:image-20220709100028-1.png]] 540 540 541 541 ... ... @@ -572,7 +572,7 @@ 572 572 ))) 573 573 574 574 ((( 575 -If payload = 0x04FF, it will reset the DDS75748 +If payload = 0x04FF, it will reset the N95S31B 576 576 ))) 577 577 578 578 ... ... @@ -583,69 +583,76 @@ 583 583 ))) 584 584 585 585 759 +== 2.5 Humidity and Temperature alarm function == 586 586 587 -== 2.5 Battery Analysis == 588 588 589 - ===2.5.1BatteryType===762 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 590 590 591 591 592 -((( 593 -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. 594 -))) 765 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 595 595 596 -((( 597 -The battery is designed to last for several years depends on the actually use environment and update interval. 598 -))) 599 599 600 -((( 601 -The battery related documents as below: 602 -))) 768 +² When min=0, and max≠0, Alarm higher than max 603 603 604 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 605 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 606 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 770 +² When min≠0, and max=0, Alarm lower than min 607 607 608 -((( 609 -[[image:image-20220709101450-2.png]] 610 -))) 772 +² When min≠0 and max≠0, Alarm higher than max or lower than min 611 611 612 612 775 + (% style="color:blue" %)**Example:** 613 613 614 - ===2.5.2PowerconsumptionAnalyze===777 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 615 615 616 -((( 617 -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. 618 -))) 619 619 620 -((( 621 - 622 -))) 780 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 623 623 782 +² When min=0, and max≠0, Alarm higher than max 624 624 625 - ===2.5.3BatteryNote===784 +² When min≠0, and max=0, Alarm lower than min 626 626 627 -((( 628 -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. 629 -))) 786 +² When min≠0 and max≠0, Alarm higher than max or lower than min 630 630 631 631 789 +**~ (% style="color:blue" %)Example:(%%)** 632 632 633 - ===2.5.4Replacethebattery===791 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 634 634 635 635 636 -((( 637 -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. 638 -))) 794 +== 2.6 Set the number of data to be uploaded and the recording time == 639 639 640 640 641 -((( 642 -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). 643 -))) 797 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 644 644 799 +* (% 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) 800 +* (% 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. 645 645 802 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 646 646 804 +[[image:image-20221009001045-1.png||height="726" width="1009"]] 805 + 806 + 807 +== 2.7 Read or Clear cached data == 808 + 809 + 810 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 811 + 812 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 813 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 814 + 815 +[[image:image-20220908163102-2.png]] 816 + 817 + 818 +== 2.8 Battery & Power Consumption == 819 + 820 + 821 +N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 822 + 823 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 824 + 825 + 647 647 = 3. Access NB-IoT Module = 648 648 828 + 649 649 ((( 650 650 Users can directly access the AT command set of the NB-IoT module. 651 651 ))) ... ... @@ -652,19 +652,21 @@ 652 652 653 653 ((( 654 654 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/]] 835 + 836 + 655 655 ))) 656 656 657 657 [[image:1657333200519-600.png]] 658 658 659 659 660 - 661 661 = 4. Using the AT Commands = 662 662 663 663 == 4.1 Access AT Commands == 664 664 665 -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/]] 666 666 847 +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]] 667 667 849 + 668 668 AT+<CMD>? : Help on <CMD> 669 669 670 670 AT+<CMD> : Run <CMD> ... ... @@ -704,7 +704,24 @@ 704 704 705 705 AT+SERVADDR : Server Address 706 706 889 +AT+TR : Get or Set record time 707 707 891 +AT+APN : Get or set the APN 892 + 893 +AT+FBAND : Get or Set whether to automatically modify the frequency band 894 + 895 +AT+DNSCFG : Get or Set DNS Server 896 + 897 +AT+GETSENSORVALUE : Returns the current sensor measurement 898 + 899 +AT+NOUD : Get or Set the number of data to be uploaded 900 + 901 +AT+CDP : Read or Clear cached data 902 + 903 +AT+SHTEMP: Get or Set alarm of temp 904 + 905 +AT+SHHUM: Get or Set alarm of moisture 906 + 708 708 (% style="color:#037691" %)**COAP Management** 709 709 710 710 AT+URI : Resource parameters ... ... @@ -735,7 +735,6 @@ 735 735 AT+PWORD : Serial Access Password 736 736 737 737 738 - 739 739 = 5. FAQ = 740 740 741 741 == 5.1 How to Upgrade Firmware == ... ... @@ -750,13 +750,14 @@ 750 750 ))) 751 751 752 752 ((( 753 - 951 +firmware:[[Dropbox - Firmware - 简化您的生活>>url:https://www.dropbox.com/sh/ap9k142hfnlh5w6/AACJeN_St0ryUl3AggrNB5x0a/N95S31B/Firmware?dl=0&subfolder_nav_tracking=1]] 754 754 755 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 953 +((( 954 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 756 756 ))) 956 +))) 757 757 758 758 759 - 760 760 = 6. Trouble Shooting = 761 761 762 762 == 6.1 Connection problem when uploading firmware == ... ... @@ -771,9 +771,9 @@ 771 771 772 772 ))) 773 773 774 - 775 775 == 6.2 AT Command input doesn't work == 776 776 975 + 777 777 ((( 778 778 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. 779 779 ... ... @@ -780,7 +780,6 @@ 780 780 781 781 ))) 782 782 783 - 784 784 = 7. Order Info = 785 785 786 786 ... ... @@ -787,11 +787,6 @@ 787 787 Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 788 788 789 789 790 -(% class="wikigeneratedid" %) 791 -((( 792 - 793 -))) 794 - 795 795 = 8. Packing Info = 796 796 797 797 ((( ... ... @@ -817,11 +817,13 @@ 817 817 ((( 818 818 819 819 820 - 821 821 822 822 ))) 823 823 824 824 = 9. Support = 825 825 1018 + 826 826 * 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. 827 827 * 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]] 1021 + 1022 +
- 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