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, 5 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.David - Content
-
... ... @@ -9,6 +9,7 @@ 9 9 10 10 **Table of Contents:** 11 11 12 +{{toc/}} 12 12 13 13 14 14 ... ... @@ -16,21 +16,35 @@ 16 16 17 17 = 1. Introduction = 18 18 20 + 19 19 == 1.1 What is N95S31B NB-IoT Sensor Node == 20 20 21 21 ((( 22 22 23 23 26 +((( 24 24 The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*. 28 +))) 25 25 30 +((( 26 26 The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use. 32 +))) 27 27 34 +((( 28 28 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 +))) 29 29 38 +((( 30 30 N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report). 40 +))) 31 31 42 +((( 43 + 44 +))) 32 32 46 +((( 33 33 ~* make sure you have NB-IoT coverage locally. 48 +))) 34 34 35 35 36 36 ))) ... ... @@ -53,8 +53,6 @@ 53 53 * Micro SIM card slot for NB-IoT SIM 54 54 * 8500mAh Battery for long term use 55 55 56 - 57 - 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -74,7 +74,6 @@ 74 74 75 75 (% style="color:#037691" %)**Battery:** 76 76 77 - 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -81,10 +81,9 @@ 81 81 * Max continuously current: 130mA 82 82 * Max boost current: 2A, 1 second 83 83 84 - 85 - 86 86 == 1.4 Applications == 87 87 98 + 88 88 * Smart Buildings & Home Automation 89 89 * Logistics and Supply Chain Management 90 90 * Smart Metering ... ... @@ -96,15 +96,20 @@ 96 96 97 97 98 98 99 -== 1.5 Pin Definitions == 100 100 111 +== 1.5 Pin Definitions & Switch == 112 + 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 120 + 106 106 === 1.5.1 Jumper JP2 === 107 107 123 + 108 108 Power on Device when put this jumper. 109 109 110 110 ... ... @@ -111,14 +111,20 @@ 111 111 112 112 === 1.5.2 BOOT MODE / SW1 === 113 113 130 + 131 +((( 114 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. 133 +))) 115 115 135 +((( 116 116 2) Flash: work mode, device starts to work and send out console output for further debug 137 +))) 117 117 118 118 119 119 120 120 === 1.5.3 Reset Button === 121 121 143 + 122 122 Press to reboot the device. 123 123 124 124 ... ... @@ -125,16 +125,15 @@ 125 125 126 126 === 1.5.4 LED === 127 127 150 + 128 128 It will flash: 129 129 130 130 1. When boot the device in flash mode 131 131 1. Send an uplink packet 132 132 133 - 134 - 135 - 136 136 = 2. Use N95S31B to communicate with IoT Server = 137 137 158 + 138 138 == 2.1 How it works == 139 139 140 140 ... ... @@ -151,7 +151,7 @@ 151 151 152 152 ))) 153 153 154 -[[image:1657 350248151-650.png]]175 +[[image:1657520100595-569.png]] 155 155 156 156 ((( 157 157 ... ... @@ -167,27 +167,49 @@ 167 167 [[image:image-20220709150546-2.png]] 168 168 169 169 191 + 170 170 === 2.2.1 Test Requirement === 171 171 172 172 195 +((( 173 173 To use N95S31B in your city, make sure meet below requirements: 197 +))) 174 174 175 -* Your local operator has already distributed a NB-IoT Network there. 176 -* The local NB-IoT network used the band that N95S31B supports. 177 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 199 +* ((( 200 +Your local operator has already distributed a NB-IoT Network there. 201 +))) 202 +* ((( 203 +The local NB-IoT network used the band that N95S31B supports. 204 +))) 205 +* ((( 206 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 207 +))) 178 178 179 - 209 +((( 180 180 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 211 +))) 181 181 213 +((( 182 182 N95S31B supports different communication protocol such as : 215 +))) 183 183 184 184 ((( 185 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 186 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 187 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 188 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 218 +* ((( 219 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 220 +))) 221 +* ((( 222 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 223 +))) 224 +* ((( 225 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 226 +))) 227 +* ((( 228 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 229 +))) 189 189 231 +((( 190 190 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. 233 +))) 191 191 192 192 193 193 ))) ... ... @@ -198,6 +198,7 @@ 198 198 199 199 === 2.2.3 Insert SIM card === 200 200 244 + 201 201 ((( 202 202 Insert the NB-IoT Card get from your provider. 203 203 ))) ... ... @@ -213,14 +213,18 @@ 213 213 214 214 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 215 215 260 + 216 216 ((( 217 217 ((( 218 218 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. 264 + 265 + 219 219 ))) 220 220 ))) 221 221 222 222 [[image:1657351312545-300.png]] 223 223 271 + 224 224 **Connection:** 225 225 226 226 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -244,8 +244,9 @@ 244 244 245 245 [[image:1657329814315-101.png]] 246 246 295 + 247 247 ((( 248 -(% 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/]]297 +(% 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]]** 249 249 ))) 250 250 251 251 ... ... @@ -252,9 +252,10 @@ 252 252 253 253 === 2.2.5 Use CoAP protocol to uplink data === 254 254 255 -(% 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/]] 256 256 305 +(% 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/]]** 257 257 307 + 258 258 ((( 259 259 **Use below commands:** 260 260 ))) ... ... @@ -302,6 +302,7 @@ 302 302 303 303 === 2.2.7 Use MQTT protocol to uplink data === 304 304 355 + 305 305 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 306 306 307 307 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -309,8 +309,8 @@ 309 309 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 310 310 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 311 311 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 312 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 313 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 363 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 364 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 314 314 315 315 [[image:1657352634421-276.png]] 316 316 ... ... @@ -317,6 +317,7 @@ 317 317 318 318 [[image:1657352645687-385.png]] 319 319 371 + 320 320 ((( 321 321 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. 322 322 ))) ... ... @@ -330,6 +330,7 @@ 330 330 331 331 === 2.2.8 Use TCP protocol to uplink data === 332 332 385 + 333 333 This feature is supported since firmware version v110 334 334 335 335 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -344,6 +344,7 @@ 344 344 345 345 === 2.2.9 Change Update Interval === 346 346 400 + 347 347 User can use below command to change the (% style="color:green" %)**uplink interval**. 348 348 349 349 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -352,52 +352,51 @@ 352 352 353 353 ))) 354 354 409 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 355 355 411 +**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).** 356 356 413 + 357 357 == 2.3 Uplink Payload == 358 358 359 -In this mode, uplink payload includes in total 14 bytes 360 360 417 +((( 418 +N95S31B 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. 419 +))) 361 361 362 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 363 -|=(% style="width: 60px;" %)((( 364 -**Size(bytes)** 365 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 366 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]] 367 367 368 368 ((( 369 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.423 +For example: 370 370 ))) 371 371 426 +((( 427 + (% 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. 428 +))) 372 372 373 -[[image:1657331036973-987.png]] 374 374 375 375 ((( 376 -The payload is ASCIIstring,representative sameHEX:432 +The uplink payloads are composed in ASCII String. For example: 377 377 ))) 378 378 379 379 ((( 380 -0 x72403155615900640c6c19029200where:436 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 381 381 ))) 382 382 383 - *(((384 - DeviceID:0x724031556159=724031556159439 +((( 440 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 385 385 ))) 386 -* ((( 387 -Version: 0x0064=100=1.0.0 442 + 443 + 444 +((( 445 +(% style="color:red" %)**NOTE:** 388 388 ))) 389 389 390 -* ((( 391 -BAT: 0x0c6c = 3180 mV = 3.180V 448 +(% style="color:red" %) 449 +1. ((( 450 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 392 392 ))) 393 -* ((( 394 -Signal: 0x19 = 25 395 -))) 396 -* ((( 397 -Distance: 0x0292= 658 mm 398 -))) 399 -* ((( 400 -Interrupt: 0x00 = 0 452 +1. ((( 453 +**By default, the device will send an uplink message every 1 hour.** 401 401 402 402 403 403 ... ... @@ -404,105 +404,153 @@ 404 404 405 405 ))) 406 406 407 -== 2. 4PayloadExplanation and SensorInterface==460 +=== 2.3.1 Payload Analyze === 408 408 409 409 410 - === 2.4.1DeviceID===463 +N95S31B uplink payload includes in total 21 bytes 411 411 465 + 466 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 467 +|=(% style="width: 60px;" %)((( 468 +**Size(bytes)** 469 +)))|=(% 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** 470 +|(% 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" %)((( 412 412 ((( 413 - By default, theDeviceID equal to thelast6bytes of IMEI.472 +Reserve/ Same as NBSN95 CFGMOD=1 414 414 ))) 415 415 416 416 ((( 417 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID476 +No function here. 418 418 ))) 478 +)))|(% style="width:77px" %)((( 479 +((( 480 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 481 +))) 419 419 420 420 ((( 421 - **Example:**484 +By SHT31 422 422 ))) 486 +)))|(% style="width:80px" %)((( 487 +((( 488 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 489 +))) 423 423 424 424 ((( 425 - AT+DEUI=A84041F15612492 +By SHT31 426 426 ))) 494 +))) 427 427 428 428 ((( 429 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 497 + 498 + 499 +((( 500 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 430 430 ))) 502 +))) 431 431 432 432 505 +[[image:1657354294009-643.png]] 433 433 434 -=== 2.4.2 Version Info === 435 435 508 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 509 + 510 +* Device ID: 0x724031607457 = 724031607457 511 +* Version: 0x006e=110=1.1.0 512 + 513 +* BAT: 0x0ccd = 3277 mV = 3.277V 514 +* Signal: 0x1b = 27 515 +* Model: 0x01 = 1 516 +* 0x00dc000ccc= reserve, ignore in N95S31B 517 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 518 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 519 + 436 436 ((( 437 - Specifythe software version: 0x64=100, means firmware version 1.00.521 + 438 438 ))) 439 439 440 440 ((( 441 - Forexample:0x00 64:this deviceis NDDS75 with firmware version 1.0.0.525 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 442 442 ))) 443 443 528 +In this mode, uplink payload includes 91 bytes in total by default. 444 444 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. 445 445 446 -=== 2.4.3 Battery Info === 532 +|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4 533 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp ..... 447 447 448 -((( 449 -Ex1: 0x0B45 = 2885mV 450 -))) 535 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 451 451 452 -((( 453 -Ex2: 0x0B49 = 2889mV 454 -))) 537 +[[image:image-20220908154949-1.png]] 455 455 539 +The payload is ASCII string, representative same HEX: 456 456 541 +0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where: 457 457 458 -=== 2.4.4 Signal Strength === 543 +* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782 544 +* (% style="color:blue" %) Version: 0x000c=120=1.2 545 +* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V 546 +* (% style="color:red" %) Singal: 0x0c = 12 547 +* (% style="color:blue" %) Mod: 0x01 = 1 548 +* TemDS18B20: 0x0000= 0 = 0 549 +* (% style="color:green" %)Interrupt: 0x00= 0 550 +* (% style="color:green" %)adc: 0x0030= 48 551 +* SHTTEM: 0x0114= 276 = 27.6 552 +* SHTHUM:0x0231 =561=56.1% 553 +* (% style="color:red" %) Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 554 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 555 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 459 459 460 -((( 461 -NB-IoT Network signal Strength. 462 -))) 557 +=== 2.3.2 Device ID === 463 463 464 -((( 465 -**Ex1: 0x1d = 29** 466 -))) 467 467 468 468 ((( 469 - (% style="color:blue"%)**0**(%%)-113dBmorless561 +By default, the Device ID equal to the last 6 bytes of IMEI. 470 470 ))) 471 471 472 472 ((( 473 -(% style="color:blue" %)** 1**(%%)-111dBm565 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 474 474 ))) 475 475 476 476 ((( 477 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm569 +**Example:** 478 478 ))) 479 479 480 480 ((( 481 - (% style="color:blue" %)**31** (%%) -51dBm or greater573 +AT+DEUI=A84041F15612 482 482 ))) 483 483 484 484 ((( 485 -(% style="color:blue" %)**99** (%%) Not known or not detectable 577 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 578 + 579 + 486 486 ))) 487 487 582 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 488 488 489 489 490 - ===2.4.5Distance===585 +By default, the Device ID equal to the last 15 bits of IMEI. 491 491 492 - Getthe distance.Flatbjectrange280mm - 7500mm.587 +User can use **AT+DEUI** to set Device ID 493 493 589 +**Example:** 590 + 591 +AT+DEUI=868411056754138 592 + 593 + 594 +=== 2.3.3 Version Info === 595 + 596 + 494 494 ((( 495 - Forexample,if the datayou getfrom theregisteris **__0x0B 0x05__**, the distancebetweenthesensorand the measuredobject is598 +These bytes include the hardware and software version. 496 496 ))) 497 497 498 498 ((( 499 -((( 500 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 602 +Higher byte: Specify hardware version: always 0x00 for N95S31B 501 501 ))) 502 -))) 503 503 504 504 ((( 505 - 606 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 506 506 ))) 507 507 508 508 ((( ... ... @@ -509,65 +509,85 @@ 509 509 510 510 ))) 511 511 512 -=== 2.4.6 Digital Interrupt === 513 - 514 514 ((( 515 - Digital Interruptrefers topin (% style="color:blue"%)**GPIO_EXTI**(%%),andtherearedifferent triggermethods. When thereisa trigger, theNDDS75 will send a packetto theserver.614 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 516 516 ))) 517 517 518 518 ((( 519 - Thecommand is:618 + 520 520 ))) 521 521 621 + 622 +=== 2.3.4 Battery Info === 623 + 624 + 522 522 ((( 523 - (% style="color:blue"%)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**626 +Ex1: 0x0B45 = 2885mV 524 524 ))) 525 525 526 - 527 527 ((( 528 - Thelowerfourbits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.630 +Ex2: 0x0B49 = 2889mV 529 529 ))) 530 530 531 531 634 + 635 +=== 2.3.5 Signal Strength === 636 + 637 + 532 532 ((( 533 - Example:639 +NB-IoT Network signal Strength. 534 534 ))) 535 535 536 536 ((( 537 - 0x(00):Normaluplinkpacket.643 +**Ex1: 0x1d = 29** 538 538 ))) 539 539 540 540 ((( 541 - 0x(01):InterruptUplinkPacket.647 +(% style="color:blue" %)**0**(%%) -113dBm or less 542 542 ))) 543 543 544 - 545 - 546 -=== 2.4.7 +5V Output === 547 - 548 548 ((( 549 - NDDS75willenable +5Voutputbeforeallsamplinganddisablethe+5vafterall sampling.651 +(% style="color:blue" %)**1**(%%) -111dBm 550 550 ))) 551 551 552 - 553 553 ((( 554 - The5V output timean be controlledbyAT Command.655 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 555 555 ))) 556 556 557 557 ((( 558 -(% style="color:blue" %)** AT+5VT=1000**659 +(% style="color:blue" %)**31** (%%) -51dBm or greater 559 559 ))) 560 560 561 561 ((( 562 - Meansset5V valid timetohave 1000ms. Sothereal5V outputwillactuallyhave1000ms+samplingtime for othersensors.663 +(% style="color:blue" %)**99** (%%) Not known or not detectable 563 563 ))) 564 564 565 565 566 566 567 -== 2. 5Downlink Payload ==668 +=== 2.3.6 Temperature & Humidity === 568 568 569 -By default, NDDS75 prints the downlink payload to console port. 570 570 671 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 672 + 673 +[[image:image-20220709161741-3.png]] 674 + 675 + 676 +Convert the read byte to decimal and divide it by ten. 677 + 678 + 679 +**Example:** 680 + 681 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 682 + 683 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 684 + 685 + 686 + 687 +== 2.4 Downlink Payload == 688 + 689 + 690 +By default, N95S31B prints the downlink payload to console port. 691 + 571 571 [[image:image-20220709100028-1.png]] 572 572 573 573 ... ... @@ -604,7 +604,7 @@ 604 604 ))) 605 605 606 606 ((( 607 -If payload = 0x04FF, it will reset the DDS75728 +If payload = 0x04FF, it will reset the N95S31B 608 608 ))) 609 609 610 610 ... ... @@ -615,49 +615,61 @@ 615 615 ))) 616 616 617 617 739 +== 2.5 Humidity and Temperature alarm function == 618 618 619 - ==2.6LED Indicator ==741 +➢ AT Command: 620 620 743 +AT+ SHHUM=min,max 621 621 622 - TheNDDS75has an internalLED whichis to show thestatus of differentstate.745 +² When min=0, and max≠0, Alarm higher than max 623 623 747 +² When min≠0, and max=0, Alarm lower than min 624 624 625 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 626 -* Then the LED will be on for 1 second means device is boot normally. 627 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 628 -* For each uplink probe, LED will be on for 500ms. 749 +² When min≠0 and max≠0, Alarm higher than max or lower than min 629 629 630 -((( 631 - 632 -))) 751 +Example: 633 633 753 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 634 634 635 635 636 - ==2.7 Firmware Change Log ==756 +AT+ SHTEMP=min,max 637 637 758 +² When min=0, and max≠0, Alarm higher than max 638 638 639 -((( 640 -Download URL & Firmware Change log 641 -))) 760 +² When min≠0, and max=0, Alarm lower than min 642 642 643 -((( 644 -[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]] 645 -))) 762 +² When min≠0 and max≠0, Alarm higher than max or lower than min 646 646 764 +Example: 647 647 648 -((( 649 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 650 -))) 766 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 651 651 768 +== 2.6 Set the number of data to be uploaded and the recording time == 652 652 770 +➢ AT Command: 653 653 772 +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) 773 + 774 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 775 + 776 +== 2.7 Read or Clear cached data == 777 + 778 +➢ AT Command: 779 + 780 +AT+CDP ~/~/ Read cached data 781 + 782 +[[image:image-20220908163102-2.png]] 783 + 784 +AT+CDP=0 ~/~/ Clear cached data 785 + 654 654 == 2.8 Battery Analysis == 655 655 788 + 656 656 === 2.8.1 Battery Type === 657 657 658 658 659 659 ((( 660 -The N DDS75 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.793 +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. 661 661 ))) 662 662 663 663 ((( ... ... @@ -680,54 +680,35 @@ 680 680 681 681 === 2.8.2 Power consumption Analyze === 682 682 683 -((( 684 -Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 685 -))) 686 686 687 - 688 688 ((( 689 -Instruction to use as below:818 +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. 690 690 ))) 691 691 692 692 ((( 693 - (%style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]822 + 694 694 ))) 695 695 696 696 697 -((( 698 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 699 -))) 826 +=== 2.8.3 Battery Note === 700 700 701 -* ((( 702 -Product Model 703 -))) 704 -* ((( 705 -Uplink Interval 706 -))) 707 -* ((( 708 -Working Mode 709 -))) 710 710 711 711 ((( 712 - And the Life expectation in difference casewillbe shownon theright.830 +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. 713 713 ))) 714 714 715 -[[image:image-20220709110451-3.png]] 716 716 717 717 835 +=== 2.8.4 Replace the battery === 718 718 719 -=== 2.8.3 Battery Note === 720 720 721 721 ((( 722 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.839 +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. 723 723 ))) 724 724 725 725 726 - 727 -=== 2.8.4 Replace the battery === 728 - 729 729 ((( 730 -The default battery pack of N DDS75 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).844 +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). 731 731 ))) 732 732 733 733 ... ... @@ -734,6 +734,7 @@ 734 734 735 735 = 3. Access NB-IoT Module = 736 736 851 + 737 737 ((( 738 738 Users can directly access the AT command set of the NB-IoT module. 739 739 ))) ... ... @@ -740,6 +740,8 @@ 740 740 741 741 ((( 742 742 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/]] 858 + 859 + 743 743 ))) 744 744 745 745 [[image:1657333200519-600.png]] ... ... @@ -748,11 +748,13 @@ 748 748 749 749 = 4. Using the AT Commands = 750 750 868 + 751 751 == 4.1 Access AT Commands == 752 752 753 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 754 754 872 +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]] 755 755 874 + 756 756 AT+<CMD>? : Help on <CMD> 757 757 758 758 AT+<CMD> : Run <CMD> ... ... @@ -792,7 +792,24 @@ 792 792 793 793 AT+SERVADDR : Server Address 794 794 914 +AT+TR : Get or Set record time 795 795 916 +AT+APN : Get or set the APN 917 + 918 +AT+FBAND : Get or Set whether to automatically modify the frequency band 919 + 920 +AT+DNSCFG : Get or Set DNS Server 921 + 922 +AT+GETSENSORVALUE : Returns the current sensor measurement 923 + 924 +AT+NOUD : Get or Set the number of data to be uploaded 925 + 926 +AT+CDP : Read or Clear cached data 927 + 928 +AT+SHTEMP: Get or Set alarm of temp 929 + 930 +AT+SHHUM: Get or Set alarm of moisture 931 + 796 796 (% style="color:#037691" %)**COAP Management** 797 797 798 798 AT+URI : Resource parameters ... ... @@ -826,6 +826,7 @@ 826 826 827 827 = 5. FAQ = 828 828 965 + 829 829 == 5.1 How to Upgrade Firmware == 830 830 831 831 ... ... @@ -838,13 +838,18 @@ 838 838 ))) 839 839 840 840 ((( 841 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 978 + 979 + 980 +((( 981 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 842 842 ))) 983 +))) 843 843 844 844 845 845 846 846 = 6. Trouble Shooting = 847 847 989 + 848 848 == 6.1 Connection problem when uploading firmware == 849 849 850 850 ... ... @@ -860,6 +860,7 @@ 860 860 861 861 == 6.2 AT Command input doesn't work == 862 862 1005 + 863 863 ((( 864 864 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. 865 865 ... ... @@ -870,7 +870,7 @@ 870 870 = 7. Order Info = 871 871 872 872 873 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**1016 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 874 874 875 875 876 876 (% class="wikigeneratedid" %) ... ... @@ -885,7 +885,7 @@ 885 885 886 886 (% style="color:#037691" %)**Package Includes**: 887 887 888 -* NS E01DistanceDetectSensorNode x 11031 +* N95S31B NB-IoT Temperature and Humidity Sensor 889 889 * External antenna x 1 890 890 ))) 891 891 ... ... @@ -894,11 +894,10 @@ 894 894 895 895 (% style="color:#037691" %)**Dimension and weight**: 896 896 897 - 898 898 * Device Size: 13.0 x 5 x 4.5 cm 899 899 * Device Weight: 150g 900 -* Package Size / pcs : 1 5x12x 5.5cm901 -* Weight / pcs : 220g1042 +* Package Size / pcs : 14.0 x 8x 5 cm 1043 +* Weight / pcs : 180g 902 902 ))) 903 903 904 904 ((( ... ... @@ -910,5 +910,8 @@ 910 910 911 911 = 9. Support = 912 912 1055 + 913 913 * 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. 914 914 * 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]] 1058 + 1059 +
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 KB - Content
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.2 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