Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 4 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -17,6 +17,7 @@ 17 17 18 18 = 1. Introduction = 19 19 20 + 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 22 22 ((( ... ... @@ -55,6 +55,7 @@ 55 55 56 56 == 1.2 Features == 57 57 59 + 58 58 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 59 59 * Monitor Temperature & Humidity via SHT31 60 60 * AT Commands to change parameters ... ... @@ -66,9 +66,6 @@ 66 66 * Micro SIM card slot for NB-IoT SIM 67 67 * 8500mAh Battery for long term use 68 68 69 - 70 - 71 - 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -77,7 +77,6 @@ 77 77 * Supply Voltage: 2.1v ~~ 3.6v 78 78 * Operating Temperature: -40 ~~ 85°C 79 79 80 - 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 83 * - B1 @H-FDD: 2100MHz ... ... @@ -87,7 +87,6 @@ 87 87 * - B20 @H-FDD: 800MHz 88 88 * - B28 @H-FDD: 700MHz 89 89 90 - 91 91 (% style="color:#037691" %)**Battery:** 92 92 93 93 * Li/SOCI2 un-chargeable battery ... ... @@ -96,11 +96,9 @@ 96 96 * Max continuously current: 130mA 97 97 * Max boost current: 2A, 1 second 98 98 99 - 100 - 101 - 102 102 == 1.4 Applications == 103 103 98 + 104 104 * Smart Buildings & Home Automation 105 105 * Logistics and Supply Chain Management 106 106 * Smart Metering ... ... @@ -112,15 +112,20 @@ 112 112 113 113 114 114 115 -== 1.5 Pin Definitions == 116 116 111 +== 1.5 Pin Definitions & Switch == 112 + 113 + 117 117 N95S31B use the mother board from NBSN95 which as below. 118 118 116 + 119 119 [[image:image-20220709144723-1.png]] 120 120 121 121 120 + 122 122 === 1.5.1 Jumper JP2 === 123 123 123 + 124 124 Power on Device when put this jumper. 125 125 126 126 ... ... @@ -127,14 +127,20 @@ 127 127 128 128 === 1.5.2 BOOT MODE / SW1 === 129 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 131 132 -2) Flash: work mode, device starts to work and send out console output for further debug 131 +((( 132 +**1) ISP: ** upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 133 +))) 133 133 135 +((( 136 +**2) Flash:** work mode, device starts to work and send out console output for further debug 137 +))) 134 134 135 135 140 + 136 136 === 1.5.3 Reset Button === 137 137 143 + 138 138 Press to reboot the device. 139 139 140 140 ... ... @@ -141,13 +141,18 @@ 141 141 142 142 === 1.5.4 LED === 143 143 150 + 144 144 It will flash: 145 145 146 -1. When boot the device in flash mode 147 -1. Send an uplink packet 153 +1. When boot the device in flash mode 148 148 155 +2. Send an uplink packet 156 + 157 + 158 + 149 149 = 2. Use N95S31B to communicate with IoT Server = 150 150 161 + 151 151 == 2.1 How it works == 152 152 153 153 ... ... @@ -164,7 +164,7 @@ 164 164 165 165 ))) 166 166 167 -[[image:1657 350248151-650.png]]178 +[[image:1657520100595-569.png]] 168 168 169 169 ((( 170 170 ... ... @@ -180,26 +180,49 @@ 180 180 [[image:image-20220709150546-2.png]] 181 181 182 182 194 + 183 183 === 2.2.1 Test Requirement === 184 184 185 185 198 +((( 186 186 To use N95S31B in your city, make sure meet below requirements: 200 +))) 187 187 188 -* Your local operator has already distributed a NB-IoT Network there. 189 -* The local NB-IoT network used the band that N95S31B supports. 190 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 202 +* ((( 203 +Your local operator has already distributed a NB-IoT Network there. 204 +))) 205 +* ((( 206 +The local NB-IoT network used the band that N95S31B supports. 207 +))) 208 +* ((( 209 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 210 +))) 191 191 212 +((( 192 192 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 214 +))) 193 193 216 +((( 194 194 N95S31B supports different communication protocol such as : 218 +))) 195 195 196 196 ((( 197 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 198 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 199 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 200 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 221 +* ((( 222 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 223 +))) 224 +* ((( 225 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 226 +))) 227 +* ((( 228 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 229 +))) 230 +* ((( 231 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 232 +))) 201 201 234 +((( 202 202 We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server. 236 +))) 203 203 204 204 205 205 ))) ... ... @@ -210,6 +210,7 @@ 210 210 211 211 === 2.2.3 Insert SIM card === 212 212 247 + 213 213 ((( 214 214 Insert the NB-IoT Card get from your provider. 215 215 ))) ... ... @@ -225,23 +225,27 @@ 225 225 226 226 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 227 227 263 + 228 228 ((( 229 229 ((( 230 230 User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below. 267 + 268 + 231 231 ))) 232 232 ))) 233 233 234 234 [[image:1657351312545-300.png]] 235 235 236 -**Connection:** 237 237 238 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND275 +(% style="color:blue" %)**Connection:** 239 239 240 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD277 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 241 241 242 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD279 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 243 243 281 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 244 244 283 + 245 245 In the PC, use below serial tool settings: 246 246 247 247 * Baud: (% style="color:green" %)**9600** ... ... @@ -256,8 +256,9 @@ 256 256 257 257 [[image:1657329814315-101.png]] 258 258 298 + 259 259 ((( 260 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]300 +(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]** 261 261 ))) 262 262 263 263 ... ... @@ -264,9 +264,10 @@ 264 264 265 265 === 2.2.5 Use CoAP protocol to uplink data === 266 266 267 -(% 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/]] 268 268 308 +(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]** 269 269 310 + 270 270 ((( 271 271 **Use below commands:** 272 272 ))) ... ... @@ -275,10 +275,10 @@ 275 275 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 276 276 ))) 277 277 * ((( 278 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 319 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 279 279 ))) 280 280 * ((( 281 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 322 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 282 282 ))) 283 283 284 284 ((( ... ... @@ -314,15 +314,16 @@ 314 314 315 315 === 2.2.7 Use MQTT protocol to uplink data === 316 316 358 + 317 317 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 318 318 319 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 320 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 321 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 322 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 323 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 324 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 325 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 361 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 362 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 363 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 364 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 365 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 366 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ Set the sending topic of MQTT 367 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ Set the subscription topic of MQTT 326 326 327 327 [[image:1657352634421-276.png]] 328 328 ... ... @@ -329,6 +329,7 @@ 329 329 330 330 [[image:1657352645687-385.png]] 331 331 374 + 332 332 ((( 333 333 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. 334 334 ))) ... ... @@ -342,6 +342,7 @@ 342 342 343 343 === 2.2.8 Use TCP protocol to uplink data === 344 344 388 + 345 345 This feature is supported since firmware version v110 346 346 347 347 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -356,6 +356,7 @@ 356 356 357 357 === 2.2.9 Change Update Interval === 358 358 403 + 359 359 User can use below command to change the (% style="color:green" %)**uplink interval**. 360 360 361 361 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -364,43 +364,74 @@ 364 364 365 365 ))) 366 366 412 +((( 413 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 414 +))) 367 367 416 +((( 417 +(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).** 418 +))) 368 368 420 + 421 + 369 369 == 2.3 Uplink Payload == 370 370 371 371 372 -NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes. 425 +((( 426 +N95S31B has different working modes for the connections of different types of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes. 427 +))) 373 373 374 374 430 +((( 375 375 For example: 432 +))) 376 376 377 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 434 +((( 435 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 436 +))) 378 378 379 379 439 +((( 380 380 The uplink payloads are composed in ASCII String. For example: 441 +))) 381 381 443 +((( 382 382 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 445 +))) 383 383 447 +((( 384 384 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 449 +))) 385 385 386 386 452 +((( 387 387 (% style="color:red" %)**NOTE:** 454 +))) 388 388 389 389 (% style="color:red" %) 390 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 391 -1. By default, the device will send an uplink message every 1 hour. 457 +1. ((( 458 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 459 +))) 460 +1. ((( 461 +**By default, the device will send an uplink message every 1 hour.** 392 392 393 393 464 + 465 + 466 +))) 467 + 394 394 === 2.3.1 Payload Analyze === 395 395 470 + 471 +==== 2.3.1.1 Before Firmware v1.2 ==== 472 + 473 + 396 396 N95S31B uplink payload includes in total 21 bytes 397 397 398 398 399 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 400 -|=(% style="width: 60px;" %)((( 401 -**Size(bytes)** 402 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 403 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 477 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 478 +|=(% style="width: 50px;" %)**Size(bytes)**|=(% style="width: 40px;" %)**6**|=(% style="width: 20px;" %)2|=(% style="width: 20px;" %)**2**|=(% style="width: 60px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 150px;" %)5|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2** 479 +|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)((( 404 404 ((( 405 405 Reserve/ Same as NBSN95 CFGMOD=1 406 406 ))) ... ... @@ -408,7 +408,7 @@ 408 408 ((( 409 409 No function here. 410 410 ))) 411 -)))|(% style="width: 77px" %)(((487 +)))|(% style="width:102px" %)((( 412 412 ((( 413 413 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 414 414 ))) ... ... @@ -416,7 +416,7 @@ 416 416 ((( 417 417 By SHT31 418 418 ))) 419 -)))|(% style="width:8 0px" %)(((495 +)))|(% style="width:81px" %)((( 420 420 ((( 421 421 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 422 422 ))) ... ... @@ -427,6 +427,8 @@ 427 427 ))) 428 428 429 429 ((( 506 + 507 + 430 430 ((( 431 431 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 432 432 ))) ... ... @@ -436,29 +436,88 @@ 436 436 [[image:1657354294009-643.png]] 437 437 438 438 439 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:517 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 440 440 441 -* Device ID: 0x724031607457 = 724031607457 442 -* Version: 0x006e=110=1.1.0 519 +**where:** 443 443 444 -* BAT: 0x0ccd = 3277 mV = 3.277V 445 -* Signal: 0x1b = 27 446 -* Model: 0x01 = 1 447 -* 0x00dc000ccc= reserve, ignore in N95S31B 448 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 449 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 521 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 450 450 523 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 524 + 525 +* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 526 + 527 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 528 + 529 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 530 + 531 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 532 + 533 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 534 + 535 +* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 536 + 451 451 ((( 452 452 453 -))) 454 454 455 - (((540 + 456 456 457 457 ))) 458 458 544 +==== 2.3.1.2 Since Firmware v1.2 ==== 459 459 546 + 547 +In this mode, uplink payload includes 91 bytes in total by default. 548 + 549 +Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded. 550 + 551 + 552 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 553 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:30px" %)**1**|(% style="width:20px" %)**1**|(% style="width:55px" %)**2**|(% style="width:35px" %)**1**|(% style="width:20px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:30px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:35px" %)**4** 554 +|=(% style="width: 95px;" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp ..... 555 + 556 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 557 + 558 + 559 +[[image:image-20220908154949-1.png]] 560 + 561 + 562 +The payload is ASCII string, representative same HEX: 563 + 564 +**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ ** 565 + 566 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 567 + 568 +**where:** 569 + 570 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 571 + 572 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 573 + 574 +* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 575 + 576 +* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 577 + 578 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 579 + 580 +* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 581 + 582 +* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 583 + 584 +* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 585 + 586 +* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 587 + 588 +* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 589 + 590 +* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 591 + 592 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 593 + 594 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 595 + 460 460 === 2.3.2 Device ID === 461 461 598 + 462 462 ((( 463 463 By default, the Device ID equal to the last 6 bytes of IMEI. 464 464 ))) ... ... @@ -465,10 +465,12 @@ 465 465 466 466 ((( 467 467 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 605 + 606 + 468 468 ))) 469 469 470 470 ((( 471 -**Example:** 610 +(% style="color:blue" %)**Example:** 472 472 ))) 473 473 474 474 ((( ... ... @@ -476,22 +476,47 @@ 476 476 ))) 477 477 478 478 ((( 479 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 618 +The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID. 619 + 620 + 480 480 ))) 481 481 623 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 482 482 483 483 626 +By default, the Device ID equal to the last 15 bits of IMEI. 627 + 628 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 629 + 630 + 631 +(% style="color:blue" %)**Example:** 632 + 633 +AT+DEUI=868411056754138 634 + 635 + 636 + 484 484 === 2.3.3 Version Info === 485 485 486 486 640 +((( 487 487 These bytes include the hardware and software version. 642 +))) 488 488 644 +((( 489 489 Higher byte: Specify hardware version: always 0x00 for N95S31B 646 +))) 490 490 648 +((( 491 491 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 650 +))) 492 492 652 +((( 653 + 654 +))) 493 493 656 +((( 494 494 For example: 0x00 6E: this device is N95S31B with firmware version 110. 658 +))) 495 495 496 496 ((( 497 497 ... ... @@ -500,6 +500,7 @@ 500 500 501 501 === 2.3.4 Battery Info === 502 502 667 + 503 503 ((( 504 504 Ex1: 0x0B45 = 2885mV 505 505 ))) ... ... @@ -512,6 +512,7 @@ 512 512 513 513 === 2.3.5 Signal Strength === 514 514 680 + 515 515 ((( 516 516 NB-IoT Network signal Strength. 517 517 ))) ... ... @@ -544,6 +544,7 @@ 544 544 545 545 === 2.3.6 Temperature & Humidity === 546 546 713 + 547 547 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 548 548 549 549 [[image:image-20220709161741-3.png]] ... ... @@ -562,8 +562,9 @@ 562 562 563 563 == 2.4 Downlink Payload == 564 564 565 -By default, NDDS75 prints the downlink payload to console port. 566 566 733 +By default, N95S31B prints the downlink payload to console port. 734 + 567 567 [[image:image-20220709100028-1.png]] 568 568 569 569 ... ... @@ -600,7 +600,7 @@ 600 600 ))) 601 601 602 602 ((( 603 -If payload = 0x04FF, it will reset the DDS75771 +If payload = 0x04FF, it will reset the N95S31B 604 604 ))) 605 605 606 606 ... ... @@ -612,11 +612,74 @@ 612 612 613 613 614 614 615 -== 2.5 BatteryAnalysis==783 +== 2.5 Humidity and Temperature alarm function == 616 616 617 -=== 2.5.1 Battery Type === 618 618 786 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 619 619 788 + 789 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 790 + 791 + 792 +² When min=0, and max≠0, Alarm higher than max 793 + 794 +² When min≠0, and max=0, Alarm lower than min 795 + 796 +² When min≠0 and max≠0, Alarm higher than max or lower than min 797 + 798 + 799 + (% style="color:blue" %)**Example:** 800 + 801 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 802 + 803 + 804 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 805 + 806 +² When min=0, and max≠0, Alarm higher than max 807 + 808 +² When min≠0, and max=0, Alarm lower than min 809 + 810 +² When min≠0 and max≠0, Alarm higher than max or lower than min 811 + 812 + 813 +**~ (% style="color:blue" %)Example:(%%)** 814 + 815 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 816 + 817 + 818 + 819 +== 2.6 Set the number of data to be uploaded and the recording time == 820 + 821 + 822 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 823 + 824 +* (% style="color:#037691" %)**AT+TR=900** (%%)~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds) 825 +* (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 826 + 827 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 828 + 829 +[[image:image-20221009001045-1.png||height="726" width="1009"]] 830 + 831 + 832 + 833 +== 2.7 Read or Clear cached data == 834 + 835 + 836 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 837 + 838 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 839 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 840 + 841 +[[image:image-20220908163102-2.png]] 842 + 843 + 844 + 845 +== 2.8 Battery Analysis == 846 + 847 + 848 +=== 2.8.1 Battery Type === 849 + 850 + 620 620 ((( 621 621 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. 622 622 ))) ... ... @@ -639,10 +639,11 @@ 639 639 640 640 641 641 642 -=== 2. 5.2 Power consumption Analyze ===873 +=== 2.8.2 Power consumption Analyze === 643 643 875 + 644 644 ((( 645 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]877 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 646 646 ))) 647 647 648 648 ((( ... ... @@ -650,8 +650,9 @@ 650 650 ))) 651 651 652 652 653 -=== 2. 5.3 Battery Note ===885 +=== 2.8.3 Battery Note === 654 654 887 + 655 655 ((( 656 656 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. 657 657 ))) ... ... @@ -658,7 +658,7 @@ 658 658 659 659 660 660 661 -=== 2. 5.4 Replace the battery ===894 +=== 2.8.4 Replace the battery === 662 662 663 663 664 664 ((( ... ... @@ -674,6 +674,7 @@ 674 674 675 675 = 3. Access NB-IoT Module = 676 676 910 + 677 677 ((( 678 678 Users can directly access the AT command set of the NB-IoT module. 679 679 ))) ... ... @@ -680,6 +680,8 @@ 680 680 681 681 ((( 682 682 The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 917 + 918 + 683 683 ))) 684 684 685 685 [[image:1657333200519-600.png]] ... ... @@ -688,11 +688,13 @@ 688 688 689 689 = 4. Using the AT Commands = 690 690 927 + 691 691 == 4.1 Access AT Commands == 692 692 693 -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/]] 694 694 931 +See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]] 695 695 933 + 696 696 AT+<CMD>? : Help on <CMD> 697 697 698 698 AT+<CMD> : Run <CMD> ... ... @@ -732,7 +732,24 @@ 732 732 733 733 AT+SERVADDR : Server Address 734 734 973 +AT+TR : Get or Set record time 735 735 975 +AT+APN : Get or set the APN 976 + 977 +AT+FBAND : Get or Set whether to automatically modify the frequency band 978 + 979 +AT+DNSCFG : Get or Set DNS Server 980 + 981 +AT+GETSENSORVALUE : Returns the current sensor measurement 982 + 983 +AT+NOUD : Get or Set the number of data to be uploaded 984 + 985 +AT+CDP : Read or Clear cached data 986 + 987 +AT+SHTEMP: Get or Set alarm of temp 988 + 989 +AT+SHHUM: Get or Set alarm of moisture 990 + 736 736 (% style="color:#037691" %)**COAP Management** 737 737 738 738 AT+URI : Resource parameters ... ... @@ -766,6 +766,7 @@ 766 766 767 767 = 5. FAQ = 768 768 1024 + 769 769 == 5.1 How to Upgrade Firmware == 770 770 771 771 ... ... @@ -780,13 +780,16 @@ 780 780 ((( 781 781 782 782 783 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 1039 +((( 1040 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 784 784 ))) 1042 +))) 785 785 786 786 787 787 788 788 = 6. Trouble Shooting = 789 789 1048 + 790 790 == 6.1 Connection problem when uploading firmware == 791 791 792 792 ... ... @@ -802,6 +802,7 @@ 802 802 803 803 == 6.2 AT Command input doesn't work == 804 804 1064 + 805 805 ((( 806 806 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. 807 807 ... ... @@ -851,5 +851,6 @@ 851 851 852 852 = 9. Support = 853 853 1114 + 854 854 * 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. 855 855 * 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