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, 0 added, 4 removed)
Details
- Page properties
-
- Content
-
... ... @@ -55,7 +55,6 @@ 55 55 56 56 == 1.2 Features == 57 57 58 - 59 59 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 60 60 * Monitor Temperature & Humidity via SHT31 61 61 * AT Commands to change parameters ... ... @@ -69,6 +69,7 @@ 69 69 70 70 71 71 71 + 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -77,6 +77,7 @@ 77 77 * Supply Voltage: 2.1v ~~ 3.6v 78 78 * Operating Temperature: -40 ~~ 85°C 79 79 80 + 80 80 (% style="color:#037691" %)**NB-IoT Spec:** 81 81 82 82 * - B1 @H-FDD: 2100MHz ... ... @@ -86,6 +86,7 @@ 86 86 * - B20 @H-FDD: 800MHz 87 87 * - B28 @H-FDD: 700MHz 88 88 90 + 89 89 (% style="color:#037691" %)**Battery:** 90 90 91 91 * Li/SOCI2 un-chargeable battery ... ... @@ -96,9 +96,9 @@ 96 96 97 97 98 98 101 + 99 99 == 1.4 Applications == 100 100 101 - 102 102 * Smart Buildings & Home Automation 103 103 * Logistics and Supply Chain Management 104 104 * Smart Metering ... ... @@ -110,49 +110,47 @@ 110 110 111 111 112 112 113 -== 1.5 Pin Definitions & Switch==115 +== 1.5 Pin Definitions == 114 114 115 - 116 116 N95S31B use the mother board from NBSN95 which as below. 117 117 118 - 119 119 [[image:image-20220709144723-1.png]] 120 120 121 121 122 122 === 1.5.1 Jumper JP2 === 123 123 124 - 125 125 Power on Device when put this jumper. 126 126 127 127 127 + 128 128 === 1.5.2 BOOT MODE / SW1 === 129 129 130 - 131 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.131 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 133 133 ))) 134 134 135 135 ((( 136 - **2) Flash:**work mode, device starts to work and send out console output for further debug135 +2) Flash: work mode, device starts to work and send out console output for further debug 137 137 ))) 138 138 139 139 139 + 140 140 === 1.5.3 Reset Button === 141 141 142 - 143 143 Press to reboot the device. 144 144 145 145 145 + 146 146 === 1.5.4 LED === 147 147 148 - 149 149 It will flash: 150 150 151 -1. When boot the device in flash mode 150 +1. When boot the device in flash mode 151 +1. Send an uplink packet 152 152 153 -2. Send an uplink packet 154 154 155 155 155 + 156 156 = 2. Use N95S31B to communicate with IoT Server = 157 157 158 158 == 2.1 How it works == ... ... @@ -171,7 +171,7 @@ 171 171 172 172 ))) 173 173 174 -[[image:16575 20100595-569.png]]174 +[[image:1657350248151-650.png]] 175 175 176 176 ((( 177 177 ... ... @@ -180,6 +180,7 @@ 180 180 181 181 == 2.2 Configure the N95S31B == 182 182 183 + 183 183 === 2.2.1 Power On N95S31B === 184 184 185 185 ... ... @@ -186,48 +186,26 @@ 186 186 [[image:image-20220709150546-2.png]] 187 187 188 188 189 -=== 2.2. 2Test Requirement ===190 +=== 2.2.1 Test Requirement === 190 190 191 191 192 -((( 193 193 To use N95S31B in your city, make sure meet below requirements: 194 -))) 195 195 196 -* ((( 197 -Your local operator has already distributed a NB-IoT Network there. 198 -))) 199 -* ((( 200 -The local NB-IoT network used the band that N95S31B supports. 201 -))) 202 -* ((( 203 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 204 -))) 195 +* Your local operator has already distributed a NB-IoT Network there. 196 +* The local NB-IoT network used the band that N95S31B supports. 197 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 205 205 206 -((( 207 207 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 208 -))) 209 209 210 -((( 211 211 N95S31B supports different communication protocol such as : 212 -))) 213 213 214 214 ((( 215 -* ((( 216 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 217 -))) 218 -* ((( 219 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 220 -))) 221 -* ((( 222 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 223 -))) 224 -* ((( 225 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 226 -))) 204 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 205 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 206 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 207 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 227 227 228 -((( 229 229 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. 230 -))) 231 231 232 232 233 233 ))) ... ... @@ -235,9 +235,9 @@ 235 235 [[image:1657350625843-586.png]] 236 236 237 237 217 + 238 238 === 2.2.3 Insert SIM card === 239 239 240 - 241 241 ((( 242 242 Insert the NB-IoT Card get from your provider. 243 243 ))) ... ... @@ -250,29 +250,26 @@ 250 250 [[image:1657351240556-536.png]] 251 251 252 252 232 + 253 253 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 254 254 255 - 256 256 ((( 257 257 ((( 258 258 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. 259 - 260 - 261 261 ))) 262 262 ))) 263 263 264 264 [[image:1657351312545-300.png]] 265 265 243 +**Connection:** 266 266 267 -(% style="color: blue" %)**Connection:**245 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 268 268 269 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**247 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 270 270 271 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**249 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 272 272 273 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 274 274 275 - 276 276 In the PC, use below serial tool settings: 277 277 278 278 * Baud: (% style="color:green" %)**9600** ... ... @@ -287,18 +287,17 @@ 287 287 288 288 [[image:1657329814315-101.png]] 289 289 290 - 291 291 ((( 292 -(% 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]]**267 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] 293 293 ))) 294 294 295 295 271 + 296 296 === 2.2.5 Use CoAP protocol to uplink data === 297 297 274 +(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 298 298 299 -(% 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/]]** 300 300 301 - 302 302 ((( 303 303 **Use below commands:** 304 304 ))) ... ... @@ -307,10 +307,10 @@ 307 307 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 308 308 ))) 309 309 * ((( 310 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** 285 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 311 311 ))) 312 312 * ((( 313 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ 288 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 314 314 ))) 315 315 316 316 ((( ... ... @@ -329,6 +329,7 @@ 329 329 [[image:1657352185396-303.png]] 330 330 331 331 307 + 332 332 === 2.2.6 Use UDP protocol to uplink data(Default protocol) === 333 333 334 334 ... ... @@ -342,18 +342,18 @@ 342 342 [[image:1657352403317-397.png]] 343 343 344 344 321 + 345 345 === 2.2.7 Use MQTT protocol to uplink data === 346 346 347 - 348 348 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 349 349 350 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 351 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 352 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 353 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 354 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 355 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ 356 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ 326 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 327 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 328 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 329 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 330 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 331 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 332 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 357 357 358 358 [[image:1657352634421-276.png]] 359 359 ... ... @@ -360,7 +360,6 @@ 360 360 361 361 [[image:1657352645687-385.png]] 362 362 363 - 364 364 ((( 365 365 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. 366 366 ))) ... ... @@ -371,9 +371,9 @@ 371 371 ))) 372 372 373 373 349 + 374 374 === 2.2.8 Use TCP protocol to uplink data === 375 375 376 - 377 377 This feature is supported since firmware version v110 378 378 379 379 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -385,9 +385,9 @@ 385 385 [[image:1657352914475-252.png]] 386 386 387 387 363 + 388 388 === 2.2.9 Change Update Interval === 389 389 390 - 391 391 User can use below command to change the (% style="color:green" %)**uplink interval**. 392 392 393 393 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -396,71 +396,43 @@ 396 396 397 397 ))) 398 398 399 -((( 400 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 401 -))) 402 402 403 -((( 404 -(% 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).** 405 -))) 406 406 407 - 408 408 == 2.3 Uplink Payload == 409 409 410 410 411 -((( 412 -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. 413 -))) 379 +NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes. 414 414 415 415 416 -((( 417 417 For example: 418 -))) 419 419 420 -((( 421 - (% 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. 422 -))) 384 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 423 423 424 424 425 -((( 426 426 The uplink payloads are composed in ASCII String. For example: 427 -))) 428 428 429 -((( 430 430 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 431 -))) 432 432 433 -((( 434 434 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 435 -))) 436 436 437 437 438 -((( 439 439 (% style="color:red" %)**NOTE:** 440 -))) 441 441 442 442 (% style="color:red" %) 443 -1. ((( 444 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 445 -))) 446 -1. ((( 447 -**By default, the device will send an uplink message every 1 hour.** 397 +1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 398 +1. By default, the device will send an uplink message every 1 hour. 448 448 449 449 450 - 451 -))) 452 - 453 453 === 2.3.1 Payload Analyze === 454 454 455 -==== 2.3.1.1 Before Firmware v1.2 ==== 456 - 457 - 458 458 N95S31B uplink payload includes in total 21 bytes 459 459 460 460 461 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 462 -|=(% 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** 463 -|(% 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" %)((( 406 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 407 +|=(% style="width: 60px;" %)((( 408 +**Size(bytes)** 409 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 410 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 464 464 ((( 465 465 Reserve/ Same as NBSN95 CFGMOD=1 466 466 ))) ... ... @@ -468,7 +468,7 @@ 468 468 ((( 469 469 No function here. 470 470 ))) 471 -)))|(% style="width: 102px" %)(((418 +)))|(% style="width:77px" %)((( 472 472 ((( 473 473 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 474 474 ))) ... ... @@ -476,7 +476,7 @@ 476 476 ((( 477 477 By SHT31 478 478 ))) 479 -)))|(% style="width:8 1px" %)(((426 +)))|(% style="width:80px" %)((( 480 480 ((( 481 481 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 482 482 ))) ... ... @@ -487,8 +487,6 @@ 487 487 ))) 488 488 489 489 ((( 490 - 491 - 492 492 ((( 493 493 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 494 494 ))) ... ... @@ -498,90 +498,29 @@ 498 498 [[image:1657354294009-643.png]] 499 499 500 500 501 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457**446 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 502 502 503 -**where:** 448 +* Device ID: 0x724031607457 = 724031607457 449 +* Version: 0x006e=110=1.1.0 504 504 505 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 451 +* BAT: 0x0ccd = 3277 mV = 3.277V 452 +* Signal: 0x1b = 27 453 +* Model: 0x01 = 1 454 +* 0x00dc000ccc= reserve, ignore in N95S31B 455 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 456 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 506 506 507 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 508 - 509 -* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 510 - 511 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 512 - 513 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 514 - 515 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 516 - 517 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 518 - 519 -* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 520 - 521 521 ((( 522 522 460 +))) 523 523 524 - 462 +((( 525 525 526 526 ))) 527 527 528 -==== 2.3.1.2 Since Firmware v1.2 ==== 529 529 530 - 531 -In this mode, uplink payload includes 91 bytes in total by default. 532 - 533 -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. 534 - 535 - 536 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 537 -|=(% 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** 538 -|=(% 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 ..... 539 - 540 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 541 - 542 - 543 -[[image:image-20220908154949-1.png]] 544 - 545 - 546 -The payload is ASCII string, representative same HEX: 547 - 548 -**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__ ** 549 - 550 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 551 - 552 -**where:** 553 - 554 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 555 - 556 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 557 - 558 -* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 559 - 560 -* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 561 - 562 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 563 - 564 -* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 565 - 566 -* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 567 - 568 -* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 569 - 570 -* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 571 - 572 -* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 573 - 574 -* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 575 - 576 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 577 - 578 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 579 - 580 - 581 - 582 582 === 2.3.2 Device ID === 583 583 584 - 585 585 ((( 586 586 By default, the Device ID equal to the last 6 bytes of IMEI. 587 587 ))) ... ... @@ -588,12 +588,10 @@ 588 588 589 589 ((( 590 590 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 591 - 592 - 593 593 ))) 594 594 595 595 ((( 596 - (% style="color:blue" %)**Example:**478 +**Example:** 597 597 ))) 598 598 599 599 ((( ... ... @@ -601,54 +601,30 @@ 601 601 ))) 602 602 603 603 ((( 604 -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. 605 - 606 - 486 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 607 607 ))) 608 608 609 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 610 610 611 611 612 -By default, the Device ID equal to the last 15 bits of IMEI. 613 - 614 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 615 - 616 - 617 -(% style="color:blue" %)**Example:** 618 - 619 -AT+DEUI=868411056754138 620 - 621 - 622 622 === 2.3.3 Version Info === 623 623 624 624 625 -((( 626 626 These bytes include the hardware and software version. 627 -))) 628 628 629 -((( 630 630 Higher byte: Specify hardware version: always 0x00 for N95S31B 631 -))) 632 632 633 -((( 634 634 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 635 -))) 636 636 637 -((( 638 - 639 -))) 640 640 641 -((( 642 642 For example: 0x00 6E: this device is N95S31B with firmware version 110. 643 -))) 644 644 645 645 ((( 646 646 647 647 ))) 648 648 507 + 649 649 === 2.3.4 Battery Info === 650 650 651 - 652 652 ((( 653 653 Ex1: 0x0B45 = 2885mV 654 654 ))) ... ... @@ -658,9 +658,9 @@ 658 658 ))) 659 659 660 660 519 + 661 661 === 2.3.5 Signal Strength === 662 662 663 - 664 664 ((( 665 665 NB-IoT Network signal Strength. 666 666 ))) ... ... @@ -690,9 +690,9 @@ 690 690 ))) 691 691 692 692 551 + 693 693 === 2.3.6 Temperature & Humidity === 694 694 695 - 696 696 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 697 697 698 698 [[image:image-20220709161741-3.png]] ... ... @@ -708,11 +708,11 @@ 708 708 Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 709 709 710 710 569 + 711 711 == 2.4 Downlink Payload == 712 712 572 +By default, NDDS75 prints the downlink payload to console port. 713 713 714 -By default, N95S31B prints the downlink payload to console port. 715 - 716 716 [[image:image-20220709100028-1.png]] 717 717 718 718 ... ... @@ -749,7 +749,7 @@ 749 749 ))) 750 750 751 751 ((( 752 -If payload = 0x04FF, it will reset the 95S31B610 +If payload = 0x04FF, it will reset the NDDS75 753 753 ))) 754 754 755 755 ... ... @@ -760,70 +760,12 @@ 760 760 ))) 761 761 762 762 763 -== 2.5 Humidity and Temperature alarm function == 764 764 622 +== 2.5 Battery Analysis == 765 765 766 - **~(%style="color:blue"%)➢ ATCommand:(%%)**624 +=== 2.5.1 Battery Type === 767 767 768 768 769 -(% style="color:#037691" %)**AT+ SHHUM=min,max** 770 - 771 - 772 -² When min=0, and max≠0, Alarm higher than max 773 - 774 -² When min≠0, and max=0, Alarm lower than min 775 - 776 -² When min≠0 and max≠0, Alarm higher than max or lower than min 777 - 778 - 779 - (% style="color:blue" %)**Example:** 780 - 781 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 782 - 783 - 784 -(% style="color:#037691" %)**AT+ SHTEMP=min,max** 785 - 786 -² When min=0, and max≠0, Alarm higher than max 787 - 788 -² When min≠0, and max=0, Alarm lower than min 789 - 790 -² When min≠0 and max≠0, Alarm higher than max or lower than min 791 - 792 - 793 -**~ (% style="color:blue" %)Example:(%%)** 794 - 795 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 796 - 797 - 798 -== 2.6 Set the number of data to be uploaded and the recording time == 799 - 800 - 801 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 802 - 803 -* (% 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) 804 -* (% 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. 805 - 806 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 807 - 808 -[[image:image-20221009001045-1.png||height="726" width="1009"]] 809 - 810 - 811 -== 2.7 Read or Clear cached data == 812 - 813 - 814 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 815 - 816 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 817 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 818 - 819 -[[image:image-20220908163102-2.png]] 820 - 821 - 822 -== 2.8 Battery Analysis == 823 - 824 -=== 2.8.1 Battery Type === 825 - 826 - 827 827 ((( 828 828 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. 829 829 ))) ... ... @@ -845,11 +845,11 @@ 845 845 ))) 846 846 847 847 848 -=== 2.8.2 Power consumption Analyze === 849 849 649 +=== 2.5.2 Power consumption Analyze === 850 850 851 851 ((( 852 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dro pbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]652 +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. 853 853 ))) 854 854 855 855 ((( ... ... @@ -856,8 +856,8 @@ 856 856 857 857 ))) 858 858 859 -=== 2.8.3 Battery Note === 860 860 660 +=== 2.5.3 Battery Note === 861 861 862 862 ((( 863 863 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. ... ... @@ -864,9 +864,10 @@ 864 864 ))) 865 865 866 866 867 -=== 2.8.4 Replace the battery === 868 868 668 +=== 2.5.4 Replace the battery === 869 869 670 + 870 870 ((( 871 871 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. 872 872 ))) ... ... @@ -877,9 +877,9 @@ 877 877 ))) 878 878 879 879 681 + 880 880 = 3. Access NB-IoT Module = 881 881 882 - 883 883 ((( 884 884 Users can directly access the AT command set of the NB-IoT module. 885 885 ))) ... ... @@ -886,21 +886,19 @@ 886 886 887 887 ((( 888 888 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/]] 889 - 890 - 891 891 ))) 892 892 893 893 [[image:1657333200519-600.png]] 894 894 895 895 695 + 896 896 = 4. Using the AT Commands = 897 897 898 898 == 4.1 Access AT Commands == 899 899 700 +See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]] 900 900 901 -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]] 902 902 903 - 904 904 AT+<CMD>? : Help on <CMD> 905 905 906 906 AT+<CMD> : Run <CMD> ... ... @@ -940,24 +940,7 @@ 940 940 941 941 AT+SERVADDR : Server Address 942 942 943 -AT+TR : Get or Set record time 944 944 945 -AT+APN : Get or set the APN 946 - 947 -AT+FBAND : Get or Set whether to automatically modify the frequency band 948 - 949 -AT+DNSCFG : Get or Set DNS Server 950 - 951 -AT+GETSENSORVALUE : Returns the current sensor measurement 952 - 953 -AT+NOUD : Get or Set the number of data to be uploaded 954 - 955 -AT+CDP : Read or Clear cached data 956 - 957 -AT+SHTEMP: Get or Set alarm of temp 958 - 959 -AT+SHHUM: Get or Set alarm of moisture 960 - 961 961 (% style="color:#037691" %)**COAP Management** 962 962 963 963 AT+URI : Resource parameters ... ... @@ -988,6 +988,7 @@ 988 988 AT+PWORD : Serial Access Password 989 989 990 990 773 + 991 991 = 5. FAQ = 992 992 993 993 == 5.1 How to Upgrade Firmware == ... ... @@ -1004,12 +1004,11 @@ 1004 1004 ((( 1005 1005 1006 1006 1007 -((( 1008 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 790 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 1009 1009 ))) 1010 -))) 1011 1011 1012 1012 794 + 1013 1013 = 6. Trouble Shooting = 1014 1014 1015 1015 == 6.1 Connection problem when uploading firmware == ... ... @@ -1024,9 +1024,9 @@ 1024 1024 1025 1025 ))) 1026 1026 809 + 1027 1027 == 6.2 AT Command input doesn't work == 1028 1028 1029 - 1030 1030 ((( 1031 1031 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. 1032 1032 ... ... @@ -1033,6 +1033,7 @@ 1033 1033 1034 1034 ))) 1035 1035 818 + 1036 1036 = 7. Order Info = 1037 1037 1038 1038 ... ... @@ -1039,6 +1039,11 @@ 1039 1039 Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 1040 1040 1041 1041 825 +(% class="wikigeneratedid" %) 826 +((( 827 + 828 +))) 829 + 1042 1042 = 8. Packing Info = 1043 1043 1044 1044 ((( ... ... @@ -1064,16 +1064,11 @@ 1064 1064 ((( 1065 1065 1066 1066 855 + 1067 1067 1068 1068 ))) 1069 1069 1070 1070 = 9. Support = 1071 1071 1072 - 1073 1073 * 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. 1074 1074 * 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]] 1075 - 1076 - 1077 - 1078 - 1079 -
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220908154949-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -58.5 KB - Content
- image-20220908163102-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -29.7 KB - Content
- image-20221009001045-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content