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, 6 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,7 +9,6 @@ 9 9 10 10 **Table of Contents:** 11 11 12 -{{toc/}} 13 13 14 14 15 15 ... ... @@ -17,35 +17,21 @@ 17 17 18 18 = 1. Introduction = 19 19 20 - 21 21 == 1.1 What is N95S31B NB-IoT Sensor Node == 22 22 23 23 ((( 24 24 25 25 26 -((( 27 27 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 -))) 29 29 30 -((( 31 31 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 -))) 33 33 34 -((( 35 35 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 -))) 37 37 38 -((( 39 39 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 -))) 41 41 42 -((( 43 - 44 -))) 45 45 46 -((( 47 47 ~* make sure you have NB-IoT coverage locally. 48 -))) 49 49 50 50 51 51 ))) ... ... @@ -69,6 +69,7 @@ 69 69 * 8500mAh Battery for long term use 70 70 71 71 57 + 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -88,6 +88,7 @@ 88 88 89 89 (% style="color:#037691" %)**Battery:** 90 90 77 + 91 91 * Li/SOCI2 un-chargeable battery 92 92 * Capacity: 8500mAh 93 93 * Self Discharge: <1% / Year @ 25°C ... ... @@ -95,9 +95,9 @@ 95 95 * Max boost current: 2A, 1 second 96 96 97 97 85 + 98 98 == 1.4 Applications == 99 99 100 - 101 101 * Smart Buildings & Home Automation 102 102 * Logistics and Supply Chain Management 103 103 * Smart Metering ... ... @@ -109,21 +109,15 @@ 109 109 110 110 111 111 99 +== 1.5 Pin Definitions == 112 112 113 - 114 -== 1.5 Pin Definitions & Switch == 115 - 116 - 117 117 N95S31B use the mother board from NBSN95 which as below. 118 118 119 - 120 120 [[image:image-20220709144723-1.png]] 121 121 122 122 123 - 124 124 === 1.5.1 Jumper JP2 === 125 125 126 - 127 127 Power on Device when put this jumper. 128 128 129 129 ... ... @@ -130,20 +130,14 @@ 130 130 131 131 === 1.5.2 BOOT MODE / SW1 === 132 132 133 - 134 -((( 135 135 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. 136 -))) 137 137 138 -((( 139 139 2) Flash: work mode, device starts to work and send out console output for further debug 140 -))) 141 141 142 142 143 143 144 144 === 1.5.3 Reset Button === 145 145 146 - 147 147 Press to reboot the device. 148 148 149 149 ... ... @@ -150,7 +150,6 @@ 150 150 151 151 === 1.5.4 LED === 152 152 153 - 154 154 It will flash: 155 155 156 156 1. When boot the device in flash mode ... ... @@ -157,9 +157,10 @@ 157 157 1. Send an uplink packet 158 158 159 159 160 -= 2. Use N95S31B to communicate with IoT Server = 161 161 162 162 136 += 2. Use N95S31B to communicate with IoT Server = 137 + 163 163 == 2.1 How it works == 164 164 165 165 ... ... @@ -176,7 +176,7 @@ 176 176 177 177 ))) 178 178 179 -[[image:16575 20100595-569.png]]154 +[[image:1657350248151-650.png]] 180 180 181 181 ((( 182 182 ... ... @@ -192,49 +192,27 @@ 192 192 [[image:image-20220709150546-2.png]] 193 193 194 194 195 - 196 196 === 2.2.1 Test Requirement === 197 197 198 198 199 -((( 200 200 To use N95S31B in your city, make sure meet below requirements: 201 -))) 202 202 203 -* ((( 204 -Your local operator has already distributed a NB-IoT Network there. 205 -))) 206 -* ((( 207 -The local NB-IoT network used the band that N95S31B supports. 208 -))) 209 -* ((( 210 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 211 -))) 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. 212 212 213 - (((179 + 214 214 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 215 -))) 216 216 217 -((( 218 218 N95S31B supports different communication protocol such as : 219 -))) 220 220 221 221 ((( 222 -* ((( 223 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 224 -))) 225 -* ((( 226 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 227 -))) 228 -* ((( 229 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 230 -))) 231 -* ((( 232 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 233 -))) 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(%%)) 234 234 235 -((( 236 236 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. 237 -))) 238 238 239 239 240 240 ))) ... ... @@ -245,7 +245,6 @@ 245 245 246 246 === 2.2.3 Insert SIM card === 247 247 248 - 249 249 ((( 250 250 Insert the NB-IoT Card get from your provider. 251 251 ))) ... ... @@ -261,18 +261,14 @@ 261 261 262 262 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 263 263 264 - 265 265 ((( 266 266 ((( 267 267 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. 268 - 269 - 270 270 ))) 271 271 ))) 272 272 273 273 [[image:1657351312545-300.png]] 274 274 275 - 276 276 **Connection:** 277 277 278 278 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -296,9 +296,8 @@ 296 296 297 297 [[image:1657329814315-101.png]] 298 298 299 - 300 300 ((( 301 -(% 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]]**248 +(% 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/]] 302 302 ))) 303 303 304 304 ... ... @@ -305,10 +305,9 @@ 305 305 306 306 === 2.2.5 Use CoAP protocol to uplink data === 307 307 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/]] 308 308 309 -(% 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/]]** 310 310 311 - 312 312 ((( 313 313 **Use below commands:** 314 314 ))) ... ... @@ -356,16 +356,15 @@ 356 356 357 357 === 2.2.7 Use MQTT protocol to uplink data === 358 358 305 +N95S31B supports only plain MQTT now it doesn’t support TLS and other related encryption. 359 359 360 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 361 - 362 362 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 363 363 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 364 364 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 365 365 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 366 366 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 367 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 368 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 312 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 313 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 369 369 370 370 [[image:1657352634421-276.png]] 371 371 ... ... @@ -372,7 +372,6 @@ 372 372 373 373 [[image:1657352645687-385.png]] 374 374 375 - 376 376 ((( 377 377 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. 378 378 ))) ... ... @@ -384,82 +384,79 @@ 384 384 385 385 386 386 387 -=== 2.2. 8Use TCP protocol to uplink data ===331 +=== 2.2.7 Use TCP protocol to uplink data === 388 388 389 389 390 -This feature is supported since firmware version v110 391 - 392 392 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 393 393 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 394 394 395 -[[image: 1657352898400-901.png]]337 +[[image:image-20220709093918-1.png]] 396 396 397 397 398 -[[image: 1657352914475-252.png]]340 +[[image:image-20220709093918-2.png]] 399 399 400 400 401 401 402 -=== 2.2. 9Change Update Interval ===344 +=== 2.2.8 Change Update Interval === 403 403 404 - 405 405 User can use below command to change the (% style="color:green" %)**uplink interval**. 406 406 407 407 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 408 408 409 409 ((( 410 - 351 +(% style="color:red" %)**NOTE:** 411 411 ))) 412 412 413 413 ((( 414 -(% style="color:red" %) **NOTE:Sincefirmware version is v1.2:**355 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 415 415 ))) 416 416 417 -((( 418 -(% 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).** 419 -))) 420 420 421 421 422 - 423 423 == 2.3 Uplink Payload == 424 424 362 +In this mode, uplink payload includes in total 14 bytes 425 425 426 -((( 427 -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. 428 -))) 429 429 365 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 366 +|=(% style="width: 60px;" %)((( 367 +**Size(bytes)** 368 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 369 +|(% 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"]] 430 430 431 431 ((( 432 - For example:372 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 433 433 ))) 434 434 435 -((( 436 - (% 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. 437 -))) 438 438 376 +[[image:1657331036973-987.png]] 439 439 440 440 ((( 441 -The uplink payloadsare composedinASCIIString.Forxample:379 +The payload is ASCII string, representative same HEX: 442 442 ))) 443 443 444 444 ((( 445 -0 a cd00ed0acc0ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:383 +0x72403155615900640c6c19029200 where: 446 446 ))) 447 447 448 -((( 449 - 0x 0acd 00ed0acc0000ef 02d21d Total12 bytes386 +* ((( 387 +Device ID: 0x724031556159 = 724031556159 450 450 ))) 451 - 452 - 453 -((( 454 -(% style="color:red" %)**NOTE:** 389 +* ((( 390 +Version: 0x0064=100=1.0.0 455 455 ))) 456 456 457 -(% style="color:red" %) 458 -1. ((( 459 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 393 +* ((( 394 +BAT: 0x0c6c = 3180 mV = 3.180V 460 460 ))) 461 -1. ((( 462 -**By default, the device will send an uplink message every 1 hour.** 396 +* ((( 397 +Signal: 0x19 = 25 398 +))) 399 +* ((( 400 +Distance: 0x0292= 658 mm 401 +))) 402 +* ((( 403 +Interrupt: 0x00 = 0 463 463 464 464 465 465 ... ... @@ -466,187 +466,105 @@ 466 466 467 467 ))) 468 468 469 -== =2.3.1PayloadAnalyze ===410 +== 2.4 Payload Explanation and Sensor Interface == 470 470 471 471 472 -=== =2.3.1.1Before Firmwarev1.2====413 +=== 2.4.1 Device ID === 473 473 474 - 475 -N95S31B uplink payload includes in total 21 bytes 476 - 477 - 478 -(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %) 479 -|=(% style="width: 60px;" %)((( 480 -**Size(bytes)** 481 -)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 174px;" %)5|=(% style="width: 106px;" %)**2**|=(% style="width: 85px;" %)**2** 482 -|(% 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:174px" %)((( 483 483 ((( 484 - Reserve/Same asNBSN95CFGMOD=1416 +By default, the Device ID equal to the last 6 bytes of IMEI. 485 485 ))) 486 486 487 487 ((( 488 - Nofunctionhere.420 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 489 489 ))) 490 -)))|(% style="width:106px" %)((( 491 -((( 492 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 493 -))) 494 494 495 495 ((( 496 - By SHT31424 +**Example:** 497 497 ))) 498 -)))|(% style="width:85px" %)((( 499 -((( 500 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 501 -))) 502 502 503 503 ((( 504 - By SHT31428 +AT+DEUI=A84041F15612 505 505 ))) 506 -))) 507 507 508 508 ((( 509 - 510 - 511 -((( 512 -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 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 513 513 ))) 514 -))) 515 515 516 516 517 -[[image:1657354294009-643.png]] 518 518 437 +=== 2.4.2 Version Info === 519 519 520 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 439 +((( 440 +Specify the software version: 0x64=100, means firmware version 1.00. 441 +))) 521 521 522 -* Device ID: 0x724031607457 = 724031607457 443 +((( 444 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 445 +))) 523 523 524 -* Version: 0x006e=110=1.1.0 525 525 526 -* BAT: 0x0ccd = 3277 mV = 3.277V 527 527 528 - *Signal:0x1b=27449 +=== 2.4.3 Battery Info === 529 529 530 -* Model: 0x01 = 1 531 - 532 -* 0x00dc000ccc= reserve, ignore in N95S31B 533 - 534 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 535 - 536 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 537 - 538 538 ((( 539 - 452 +Ex1: 0x0B45 = 2885mV 453 +))) 540 540 541 - 542 - 455 +((( 456 +Ex2: 0x0B49 = 2889mV 543 543 ))) 544 544 545 -==== 2.3.1.2 Since Firmware v1.2 ==== 546 546 547 547 548 - Inthismode, uplink payloadincludes 91 bytes inotalby default.461 +=== 2.4.4 Signal Strength === 549 549 550 -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. 551 - 552 - 553 -(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %) 554 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:47px" %)**2**|(% style="width:124px" %)**1**|(% style="width:56px" %)**1**|(% style="width:109px" %)**2**|(% style="width:80px" %)**1**|(% style="width:51px" %)**2**|(% style="width:79px" %)**2**|(% style="width:84px" %)**2**|(% style="width:100px" %)**4**|(% style="width:76px" %)**2**|(% style="width:81px" %)**2**|(% style="width:121px" %)**4** 555 -|(% 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 ..... 556 - 557 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 558 - 559 - 560 -[[image:image-20220908154949-1.png]] 561 - 562 - 563 -The payload is ASCII string, representative same HEX: 564 - 565 -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: 566 - 567 -* (% style="color:red" %)Device ID: f868411056758782 = f868411056758782 568 - 569 -* (% style="color:blue" %)Version: 0x000c=120=1.2 570 - 571 -* (% style="color:green" %)BAT: 0x0d0f = 3343 mV = 3.343V 572 - 573 -* (% style="color:red" %)Singal: 0x0c = 12 574 - 575 -* (% style="color:blue" %)Mod: 0x01 = 1 576 - 577 -* TemDS18B20: 0x0000= 0 = 0 578 - 579 -* (% style="color:green" %)Interrupt: 0x00= 0 580 - 581 -* (% style="color:green" %)adc: 0x0030= 48 582 - 583 -* SHTTEM: 0x0114= 276 = 27.6 584 - 585 -* SHTHUM:0x0231 =561=56.1% 586 - 587 -* (% style="color:red" %)Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 588 - 589 -* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 590 - 591 -* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 592 - 593 - 594 - 595 - 596 -=== 2.3.2 Device ID === 597 - 598 - 599 599 ((( 600 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.464 +NB-IoT Network signal Strength. 601 601 ))) 602 602 603 603 ((( 604 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 468 +**Ex1: 0x1d = 29** 469 +))) 605 605 606 - 471 +((( 472 +(% style="color:blue" %)**0**(%%) -113dBm or less 607 607 ))) 608 608 609 609 ((( 610 - **(% style="color:blue" %)Example:**476 +(% style="color:blue" %)**1**(%%) -111dBm 611 611 ))) 612 612 613 613 ((( 614 - AT+DEUI=A84041F15612480 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 615 615 ))) 616 616 617 617 ((( 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. 484 +(% style="color:blue" %)**31** (%%) -51dBm or greater 485 +))) 619 619 620 - 487 +((( 488 +(% style="color:blue" %)**99** (%%) Not known or not detectable 621 621 ))) 622 622 623 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 624 624 625 625 626 - Bydefault,theDeviceID equal to the last 15 bits of IMEI.493 +=== 2.4.5 Distance === 627 627 628 - Usercan use**(%style="color:blue"%)AT+DEUI**(%%)tosetDeviceID495 +Get the distance. Flat object range 280mm - 7500mm. 629 629 630 - 631 -** (% style="color:blue" %)Example:** 632 - 633 -AT+DEUI=868411056754138 634 - 635 - 636 - 637 -=== 2.3.3 Version Info === 638 - 639 - 640 640 ((( 641 - Thesebytes include the hardware andsoftwareversion.498 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 642 642 ))) 643 643 644 644 ((( 645 -Higher byte: Specify hardware version: always 0x00 for N95S31B 502 +((( 503 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 646 646 ))) 505 +))) 647 647 648 648 ((( 649 - Lowerbyte: Specify the software version: 0x6E=110, means firmware version 110508 + 650 650 ))) 651 651 652 652 ((( ... ... @@ -653,85 +653,65 @@ 653 653 654 654 ))) 655 655 515 +=== 2.4.6 Digital Interrupt === 516 + 656 656 ((( 657 - For example:0x00 6E:thisdevice isN95S31Bwithfirmwareversion110.518 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server. 658 658 ))) 659 659 660 660 ((( 661 - 522 +The command is: 662 662 ))) 663 663 664 - 665 -=== 2.3.4 Battery Info === 666 - 667 - 668 668 ((( 669 - Ex1:0x0B45=2885mV526 +(% 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]])**.** 670 670 ))) 671 671 529 + 672 672 ((( 673 - Ex2:0x0B49=2889mV531 +The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 674 674 ))) 675 675 676 676 677 - 678 -=== 2.3.5 Signal Strength === 679 - 680 - 681 681 ((( 682 - NB-IoT Network signalStrength.536 +Example: 683 683 ))) 684 684 685 685 ((( 686 - **Ex1:0x1d=29**540 +0x(00): Normal uplink packet. 687 687 ))) 688 688 689 689 ((( 690 -( %style="color:blue"%)**0**(%%) -113dBm orless544 +0x(01): Interrupt Uplink Packet. 691 691 ))) 692 692 547 + 548 + 549 +=== 2.4.7 +5V Output === 550 + 693 693 ((( 694 - (%style="color:blue"%)**1**(%%)-111dBm552 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 695 695 ))) 696 696 555 + 697 697 ((( 698 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm557 +The 5V output time can be controlled by AT Command. 699 699 ))) 700 700 701 701 ((( 702 -(% style="color:blue" %)** 31**(%%) -51dBm or greater561 +(% style="color:blue" %)**AT+5VT=1000** 703 703 ))) 704 704 705 705 ((( 706 - (%style="color:blue"%)**99**(%%)Notknownornotdetectable565 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 707 707 ))) 708 708 709 709 710 710 711 -== =2.3.6Temperature & Humidity ===570 +== 2.5 Downlink Payload == 712 712 572 +By default, NDDS75 prints the downlink payload to console port. 713 713 714 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 715 - 716 -[[image:image-20220709161741-3.png]] 717 - 718 - 719 -Convert the read byte to decimal and divide it by ten. 720 - 721 - 722 -**Example:** 723 - 724 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 725 - 726 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 727 - 728 - 729 - 730 -== 2.4 Downlink Payload == 731 - 732 - 733 -By default, N95S31B prints the downlink payload to console port. 734 - 735 735 [[image:image-20220709100028-1.png]] 736 736 737 737 ... ... @@ -768,7 +768,7 @@ 768 768 ))) 769 769 770 770 ((( 771 -If payload = 0x04FF, it will reset the 95S31B610 +If payload = 0x04FF, it will reset the NDDS75 772 772 ))) 773 773 774 774 ... ... @@ -779,61 +779,49 @@ 779 779 ))) 780 780 781 781 782 -== 2.5 Humidity and Temperature alarm function == 783 783 784 - ➢ATCommand:622 +== 2.6 LED Indicator == 785 785 786 -AT+ SHHUM=min,max 787 787 788 - ² Whenmin=0,andmax≠0,Alarmhigherthanmax625 +The NDDS75 has an internal LED which is to show the status of different state. 789 789 790 -² When min≠0, and max=0, Alarm lower than min 791 791 792 -² When min≠0 and max≠0, Alarm higher than max or lower than min 628 +* 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) 629 +* Then the LED will be on for 1 second means device is boot normally. 630 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 631 +* For each uplink probe, LED will be on for 500ms. 793 793 794 -Example: 633 +((( 634 + 635 +))) 795 795 796 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 797 797 798 798 799 - AT+ SHTEMP=min,max639 +== 2.7 Firmware Change Log == 800 800 801 -² When min=0, and max≠0, Alarm higher than max 802 802 803 -² When min≠0, and max=0, Alarm lower than min 642 +((( 643 +Download URL & Firmware Change log 644 +))) 804 804 805 -² When min≠0 and max≠0, Alarm higher than max or lower than min 646 +((( 647 +[[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/]] 648 +))) 806 806 807 -Example: 808 808 809 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 651 +((( 652 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 653 +))) 810 810 811 -== 2.6 Set the number of data to be uploaded and the recording time == 812 812 813 -➢ AT Command: 814 814 815 -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) 816 - 817 -AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 818 - 819 -== 2.7 Read or Clear cached data == 820 - 821 -➢ AT Command: 822 - 823 -AT+CDP ~/~/ Read cached data 824 - 825 -[[image:image-20220908163102-2.png]] 826 - 827 -AT+CDP=0 ~/~/ Clear cached data 828 - 829 829 == 2.8 Battery Analysis == 830 830 831 - 832 832 === 2.8.1 Battery Type === 833 833 834 834 835 835 ((( 836 -The N 95S31Bbattery 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.663 +The NDDS75 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. 837 837 ))) 838 838 839 839 ((( ... ... @@ -856,35 +856,54 @@ 856 856 857 857 === 2.8.2 Power consumption Analyze === 858 858 686 +((( 687 +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. 688 +))) 859 859 690 + 860 860 ((( 861 - 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 toanalyzethe powerconsumption in different case.User can useit for design guideline for their project.692 +Instruction to use as below: 862 862 ))) 863 863 864 864 ((( 865 - 696 +(% 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/]] 866 866 ))) 867 867 868 868 869 -=== 2.8.3 Battery Note === 700 +((( 701 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 702 +))) 870 870 704 +* ((( 705 +Product Model 706 +))) 707 +* ((( 708 +Uplink Interval 709 +))) 710 +* ((( 711 +Working Mode 712 +))) 871 871 872 872 ((( 873 - The Li-SICO batteryis designed for smallcurrent/ long periodapplication.Itisnotgoodto use a high current, short period transmit method. The recommendedminimum period for useof thisbatteryis5 minutes. If you use a shorterperiod time to uplinkdata, thenthe battery life may be decreased.715 +And the Life expectation in difference case will be shown on the right. 874 874 ))) 875 875 718 +[[image:image-20220709110451-3.png]] 876 876 877 877 878 -=== 2.8.4 Replace the battery === 879 879 722 +=== 2.8.3 Battery Note === 880 880 881 881 ((( 882 - You can changethebattery intheN95S31B.Thetype ofbatteryis notlimitedaslongas theutput isbetween3vto3.6v.Onthemainboard,there isa diode(D1)betweenthebatteryandthemaincircuit. If youneed touse abatterywith less than 3.3v,pleaseremove the D1 andshortcut the twopadsofitso there won'tbe voltagedropbetween batteryandmainboard.725 +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 transmit LoRa, then the battery life may be decreased. 883 883 ))) 884 884 885 885 729 + 730 +=== 2.8.4 Replace the battery === 731 + 886 886 ((( 887 -The default battery pack of N 95S31Bincludes 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).733 +The default battery pack of NDDS75 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). 888 888 ))) 889 889 890 890 ... ... @@ -891,7 +891,6 @@ 891 891 892 892 = 3. Access NB-IoT Module = 893 893 894 - 895 895 ((( 896 896 Users can directly access the AT command set of the NB-IoT module. 897 897 ))) ... ... @@ -898,8 +898,6 @@ 898 898 899 899 ((( 900 900 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/]] 901 - 902 - 903 903 ))) 904 904 905 905 [[image:1657333200519-600.png]] ... ... @@ -908,13 +908,11 @@ 908 908 909 909 = 4. Using the AT Commands = 910 910 911 - 912 912 == 4.1 Access AT Commands == 913 913 756 +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/]] 914 914 915 -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]] 916 916 917 - 918 918 AT+<CMD>? : Help on <CMD> 919 919 920 920 AT+<CMD> : Run <CMD> ... ... @@ -954,24 +954,7 @@ 954 954 955 955 AT+SERVADDR : Server Address 956 956 957 -AT+TR : Get or Set record time 958 958 959 -AT+APN : Get or set the APN 960 - 961 -AT+FBAND : Get or Set whether to automatically modify the frequency band 962 - 963 -AT+DNSCFG : Get or Set DNS Server 964 - 965 -AT+GETSENSORVALUE : Returns the current sensor measurement 966 - 967 -AT+NOUD : Get or Set the number of data to be uploaded 968 - 969 -AT+CDP : Read or Clear cached data 970 - 971 -AT+SHTEMP: Get or Set alarm of temp 972 - 973 -AT+SHHUM: Get or Set alarm of moisture 974 - 975 975 (% style="color:#037691" %)**COAP Management** 976 976 977 977 AT+URI : Resource parameters ... ... @@ -1005,7 +1005,6 @@ 1005 1005 1006 1006 = 5. FAQ = 1007 1007 1008 - 1009 1009 == 5.1 How to Upgrade Firmware == 1010 1010 1011 1011 ... ... @@ -1018,18 +1018,13 @@ 1018 1018 ))) 1019 1019 1020 1020 ((( 1021 - 1022 - 1023 -((( 1024 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 844 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 1025 1025 ))) 1026 -))) 1027 1027 1028 1028 1029 1029 1030 1030 = 6. Trouble Shooting = 1031 1031 1032 - 1033 1033 == 6.1 Connection problem when uploading firmware == 1034 1034 1035 1035 ... ... @@ -1045,7 +1045,6 @@ 1045 1045 1046 1046 == 6.2 AT Command input doesn't work == 1047 1047 1048 - 1049 1049 ((( 1050 1050 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. 1051 1051 ... ... @@ -1056,7 +1056,7 @@ 1056 1056 = 7. Order Info = 1057 1057 1058 1058 1059 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**876 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 1060 1060 1061 1061 1062 1062 (% class="wikigeneratedid" %) ... ... @@ -1071,7 +1071,7 @@ 1071 1071 1072 1072 (% style="color:#037691" %)**Package Includes**: 1073 1073 1074 -* N 95S31BNB-IoTTemperatureandHumiditySensor891 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 1075 1075 * External antenna x 1 1076 1076 ))) 1077 1077 ... ... @@ -1080,10 +1080,11 @@ 1080 1080 1081 1081 (% style="color:#037691" %)**Dimension and weight**: 1082 1082 900 + 1083 1083 * Device Size: 13.0 x 5 x 4.5 cm 1084 1084 * Device Weight: 150g 1085 -* Package Size / pcs : 1 4.0x8x 5 cm1086 -* Weight / pcs : 180g903 +* Package Size / pcs : 15 x 12x 5.5 cm 904 +* Weight / pcs : 220g 1087 1087 ))) 1088 1088 1089 1089 ((( ... ... @@ -1095,6 +1095,5 @@ 1095 1095 1096 1096 = 9. Support = 1097 1097 1098 - 1099 1099 * 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. 1100 1100 * 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]]
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 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