Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Change comment:
Uploaded new attachment "1657352185396-303.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 11 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. David1 +XWiki.Xiaoling - 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 ))) ... ... @@ -70,7 +70,6 @@ 70 70 71 71 72 72 73 - 74 74 == 1.3 Specification == 75 75 76 76 ... ... @@ -79,8 +79,6 @@ 79 79 * Supply Voltage: 2.1v ~~ 3.6v 80 80 * Operating Temperature: -40 ~~ 85°C 81 81 82 - 83 - 84 84 (% style="color:#037691" %)**NB-IoT Spec:** 85 85 86 86 * - B1 @H-FDD: 2100MHz ... ... @@ -90,10 +90,9 @@ 90 90 * - B20 @H-FDD: 800MHz 91 91 * - B28 @H-FDD: 700MHz 92 92 93 - 94 - 95 95 (% style="color:#037691" %)**Battery:** 96 96 77 + 97 97 * Li/SOCI2 un-chargeable battery 98 98 * Capacity: 8500mAh 99 99 * Self Discharge: <1% / Year @ 25°C ... ... @@ -102,10 +102,8 @@ 102 102 103 103 104 104 105 - 106 106 == 1.4 Applications == 107 107 108 - 109 109 * Smart Buildings & Home Automation 110 110 * Logistics and Supply Chain Management 111 111 * Smart Metering ... ... @@ -117,20 +117,15 @@ 117 117 118 118 119 119 99 +== 1.5 Pin Definitions == 120 120 121 -== 1.5 Pin Definitions & Switch == 122 - 123 - 124 124 N95S31B use the mother board from NBSN95 which as below. 125 125 126 - 127 127 [[image:image-20220709144723-1.png]] 128 128 129 129 130 - 131 131 === 1.5.1 Jumper JP2 === 132 132 133 - 134 134 Power on Device when put this jumper. 135 135 136 136 ... ... @@ -137,20 +137,14 @@ 137 137 138 138 === 1.5.2 BOOT MODE / SW1 === 139 139 140 - 141 -((( 142 142 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. 143 -))) 144 144 145 -((( 146 146 2) Flash: work mode, device starts to work and send out console output for further debug 147 -))) 148 148 149 149 150 150 151 151 === 1.5.3 Reset Button === 152 152 153 - 154 154 Press to reboot the device. 155 155 156 156 ... ... @@ -157,7 +157,6 @@ 157 157 158 158 === 1.5.4 LED === 159 159 160 - 161 161 It will flash: 162 162 163 163 1. When boot the device in flash mode ... ... @@ -168,7 +168,6 @@ 168 168 169 169 = 2. Use N95S31B to communicate with IoT Server = 170 170 171 - 172 172 == 2.1 How it works == 173 173 174 174 ... ... @@ -185,7 +185,7 @@ 185 185 186 186 ))) 187 187 188 -[[image:16575 20100595-569.png]]154 +[[image:1657350248151-650.png]] 189 189 190 190 ((( 191 191 ... ... @@ -201,49 +201,27 @@ 201 201 [[image:image-20220709150546-2.png]] 202 202 203 203 204 - 205 205 === 2.2.1 Test Requirement === 206 206 207 207 208 -((( 209 209 To use N95S31B in your city, make sure meet below requirements: 210 -))) 211 211 212 -* ((( 213 -Your local operator has already distributed a NB-IoT Network there. 214 -))) 215 -* ((( 216 -The local NB-IoT network used the band that N95S31B supports. 217 -))) 218 -* ((( 219 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 220 -))) 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. 221 221 222 - (((179 + 223 223 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 224 -))) 225 225 226 -((( 227 227 N95S31B supports different communication protocol such as : 228 -))) 229 229 230 230 ((( 231 -* ((( 232 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 233 -))) 234 -* ((( 235 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 236 -))) 237 -* ((( 238 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 239 -))) 240 -* ((( 241 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 242 -))) 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(%%)) 243 243 244 -((( 245 245 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. 246 -))) 247 247 248 248 249 249 ))) ... ... @@ -254,7 +254,6 @@ 254 254 255 255 === 2.2.3 Insert SIM card === 256 256 257 - 258 258 ((( 259 259 Insert the NB-IoT Card get from your provider. 260 260 ))) ... ... @@ -268,20 +268,16 @@ 268 268 269 269 270 270 271 -=== 2.2. 4Connect USB – TTL to N95S31B to configure it ===214 +=== 2.2.3 Connect USB – TTL to N95S31B to configure it === 272 272 273 - 274 274 ((( 275 275 ((( 276 276 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. 277 - 278 - 279 279 ))) 280 280 ))) 281 281 282 282 [[image:1657351312545-300.png]] 283 283 284 - 285 285 **Connection:** 286 286 287 287 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -305,19 +305,17 @@ 305 305 306 306 [[image:1657329814315-101.png]] 307 307 308 - 309 309 ((( 310 -(% 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/]] 311 311 ))) 312 312 313 313 314 314 315 -=== 2.2. 5Use CoAP protocol to uplink data ===253 +=== 2.2.4 Use CoAP protocol to uplink data === 316 316 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/]] 317 317 318 -(% 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/]]** 319 319 320 - 321 321 ((( 322 322 **Use below commands:** 323 323 ))) ... ... @@ -333,12 +333,10 @@ 333 333 ))) 334 334 335 335 ((( 336 - 337 - 338 338 For parameter description, please refer to AT command set 339 339 ))) 340 340 341 -[[image:1657352 146020-183.png]]276 +[[image:1657330452568-615.png]] 342 342 343 343 344 344 ((( ... ... @@ -345,11 +345,11 @@ 345 345 After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server. 346 346 ))) 347 347 348 -[[image:16573 52185396-303.png]]283 +[[image:1657330472797-498.png]] 349 349 350 350 351 351 352 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===287 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 353 353 354 354 355 355 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -356,117 +356,109 @@ 356 356 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 357 357 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 358 358 294 +[[image:1657330501006-241.png]] 359 359 360 360 361 -[[image:165735 2391268-297.png]]297 +[[image:1657330533775-472.png]] 362 362 363 363 364 -[[image:1657352403317-397.png]] 365 365 301 +=== 2.2.6 Use MQTT protocol to uplink data === 366 366 367 367 368 -=== 2.2.7 Use MQTT protocol to uplink data === 369 - 370 - 371 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 372 - 373 373 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 374 374 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 375 375 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 376 376 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 377 377 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 378 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527379 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)309 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 310 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 380 380 312 +[[image:1657249978444-674.png]] 381 381 382 382 383 -[[image:16573 52634421-276.png]]315 +[[image:1657330723006-866.png]] 384 384 385 385 386 -[[image:1657352645687-385.png]] 387 - 388 - 389 389 ((( 390 -To savebatterylife,N95S31Bwillestablishasubscriptionbeforeeachuplinkandclose thesubscription3 secondsafteruplinksuccessful. Any downlink commandsfromserver will onlyarriveduringthesubscriptionperiod.319 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 391 391 ))) 392 392 393 393 394 -((( 395 -MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 396 -))) 397 397 324 +=== 2.2.7 Use TCP protocol to uplink data === 398 398 399 399 400 -=== 2.2.8 Use TCP protocol to uplink data === 401 - 402 - 403 -This feature is supported since firmware version v110 404 - 405 405 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 406 406 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 407 407 330 +[[image:image-20220709093918-1.png]] 408 408 409 409 410 -[[image: 1657352898400-901.png]]333 +[[image:image-20220709093918-2.png]] 411 411 412 412 413 -[[image:1657352914475-252.png]] 414 414 337 +=== 2.2.8 Change Update Interval === 415 415 416 - 417 -=== 2.2.9 Change Update Interval === 418 - 419 - 420 420 User can use below command to change the (% style="color:green" %)**uplink interval**. 421 421 422 422 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 423 423 424 424 ((( 425 - 344 +(% style="color:red" %)**NOTE:** 426 426 ))) 427 427 347 +((( 348 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 349 +))) 428 428 429 429 352 + 430 430 == 2.3 Uplink Payload == 431 431 355 +In this mode, uplink payload includes in total 14 bytes 432 432 433 -((( 434 -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. 435 -))) 436 436 358 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 359 +|=(% style="width: 60px;" %)((( 360 +**Size(bytes)** 361 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 362 +|(% 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"]] 437 437 438 438 ((( 439 - For example:365 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 440 440 ))) 441 441 442 -((( 443 - (% 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. 444 -))) 445 445 369 +[[image:1657331036973-987.png]] 446 446 447 447 ((( 448 -The uplink payloadsare composedinASCIIString.Forxample:372 +The payload is ASCII string, representative same HEX: 449 449 ))) 450 450 451 451 ((( 452 -0 a cd00ed0acc0ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:376 +0x72403155615900640c6c19029200 where: 453 453 ))) 454 454 455 -((( 456 - 0x 0acd 00ed0acc0000ef 02d21d Total12 bytes379 +* ((( 380 +Device ID: 0x724031556159 = 724031556159 457 457 ))) 458 - 459 - 460 -((( 461 -(% style="color:red" %)**NOTE:** 382 +* ((( 383 +Version: 0x0064=100=1.0.0 462 462 ))) 463 463 464 -(% style="color:red" %) 465 -1. ((( 466 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 386 +* ((( 387 +BAT: 0x0c6c = 3180 mV = 3.180V 467 467 ))) 468 -1. ((( 469 -**By default, the device will send an uplink message every 1 hour.** 389 +* ((( 390 +Signal: 0x19 = 25 391 +))) 392 +* ((( 393 +Distance: 0x0292= 658 mm 394 +))) 395 +* ((( 396 +Interrupt: 0x00 = 0 470 470 471 471 472 472 ... ... @@ -473,113 +473,105 @@ 473 473 474 474 ))) 475 475 476 -== =2.3.1PayloadAnalyze ===403 +== 2.4 Payload Explanation and Sensor Interface == 477 477 478 478 479 - N95S31Buplink payload includesintotal 21 bytes406 +=== 2.4.1 Device ID === 480 480 481 - 482 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 483 -|=(% style="width: 60px;" %)((( 484 -**Size(bytes)** 485 -)))|=(% 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** 486 -|(% 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" %)((( 487 487 ((( 488 - Reserve/Same asNBSN95CFGMOD=1409 +By default, the Device ID equal to the last 6 bytes of IMEI. 489 489 ))) 490 490 491 491 ((( 492 - Nofunctionhere.413 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 493 493 ))) 494 - )))|(% style="width:77px" %)(((415 + 495 495 ((( 496 - [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]417 +**Example:** 497 497 ))) 498 498 499 499 ((( 500 - By SHT31421 +AT+DEUI=A84041F15612 501 501 ))) 502 - )))|(% style="width:80px" %)(((423 + 503 503 ((( 504 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]425 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 505 505 ))) 506 506 428 + 429 + 430 +=== 2.4.2 Version Info === 431 + 507 507 ((( 508 - BySHT31433 +Specify the software version: 0x64=100, means firmware version 1.00. 509 509 ))) 510 -))) 511 511 512 512 ((( 513 - 514 - 515 -((( 516 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 437 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 517 517 ))) 518 -))) 519 519 520 520 521 -[[image:1657354294009-643.png]] 522 522 442 +=== 2.4.3 Battery Info === 523 523 524 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 525 - 526 -* Device ID: 0x724031607457 = 724031607457 527 -* Version: 0x006e=110=1.1.0 528 - 529 -* BAT: 0x0ccd = 3277 mV = 3.277V 530 -* Signal: 0x1b = 27 531 -* Model: 0x01 = 1 532 -* 0x00dc000ccc= reserve, ignore in N95S31B 533 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 534 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 535 - 536 536 ((( 537 - 445 +Ex1: 0x0B45 = 2885mV 538 538 ))) 539 539 540 540 ((( 541 - 449 +Ex2: 0x0B49 = 2889mV 542 542 ))) 543 543 544 544 545 -=== 2.3.2 Device ID === 546 546 454 +=== 2.4.4 Signal Strength === 547 547 548 548 ((( 549 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.457 +NB-IoT Network signal Strength. 550 550 ))) 551 551 552 552 ((( 553 - User can use (% style="color:blue" %)**AT+DEUI**(%%)tosetDevice ID461 +**Ex1: 0x1d = 29** 554 554 ))) 555 555 556 556 ((( 557 - **Example:**465 +(% style="color:blue" %)**0**(%%) -113dBm or less 558 558 ))) 559 559 560 560 ((( 561 - AT+DEUI=A84041F15612469 +(% style="color:blue" %)**1**(%%) -111dBm 562 562 ))) 563 563 564 564 ((( 565 - TheDevice ID isstored in a none-erase area, Upgrade the firmwareorrun**AT+FDR**won't erase Device ID.473 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 566 566 ))) 567 567 476 +((( 477 +(% style="color:blue" %)**31** (%%) -51dBm or greater 478 +))) 568 568 480 +((( 481 +(% style="color:blue" %)**99** (%%) Not known or not detectable 482 +))) 569 569 570 -=== 2.3.3 Version Info === 571 571 572 572 486 +=== 2.4.5 Distance === 487 + 488 +Get the distance. Flat object range 280mm - 7500mm. 489 + 573 573 ((( 574 - Thesebytes include the hardware andsoftwareversion.491 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 575 575 ))) 576 576 577 577 ((( 578 -Higher byte: Specify hardware version: always 0x00 for N95S31B 495 +((( 496 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 579 579 ))) 498 +))) 580 580 581 581 ((( 582 - Lowerbyte: Specify the software version: 0x6E=110, means firmware version 110501 + 583 583 ))) 584 584 585 585 ((( ... ... @@ -586,85 +586,65 @@ 586 586 587 587 ))) 588 588 508 +=== 2.4.6 Digital Interrupt === 509 + 589 589 ((( 590 - For example:0x00 6E:thisdevice isN95S31Bwithfirmwareversion110.511 +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. 591 591 ))) 592 592 593 593 ((( 594 - 515 +The command is: 595 595 ))) 596 596 597 - 598 -=== 2.3.4 Battery Info === 599 - 600 - 601 601 ((( 602 - Ex1:0x0B45=2885mV519 +(% 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]])**.** 603 603 ))) 604 604 522 + 605 605 ((( 606 - Ex2:0x0B49=2889mV524 +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. 607 607 ))) 608 608 609 609 610 - 611 -=== 2.3.5 Signal Strength === 612 - 613 - 614 614 ((( 615 - NB-IoT Network signalStrength.529 +Example: 616 616 ))) 617 617 618 618 ((( 619 - **Ex1:0x1d=29**533 +0x(00): Normal uplink packet. 620 620 ))) 621 621 622 622 ((( 623 -( %style="color:blue"%)**0**(%%) -113dBm orless537 +0x(01): Interrupt Uplink Packet. 624 624 ))) 625 625 540 + 541 + 542 +=== 2.4.7 +5V Output === 543 + 626 626 ((( 627 - (%style="color:blue"%)**1**(%%)-111dBm545 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 628 628 ))) 629 629 548 + 630 630 ((( 631 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm550 +The 5V output time can be controlled by AT Command. 632 632 ))) 633 633 634 634 ((( 635 -(% style="color:blue" %)** 31**(%%) -51dBm or greater554 +(% style="color:blue" %)**AT+5VT=1000** 636 636 ))) 637 637 638 638 ((( 639 - (%style="color:blue"%)**99**(%%)Notknownornotdetectable558 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 640 640 ))) 641 641 642 642 643 643 644 -== =2.3.6Temperature & Humidity ===563 +== 2.5 Downlink Payload == 645 645 565 +By default, NDDS75 prints the downlink payload to console port. 646 646 647 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 648 - 649 -[[image:image-20220709161741-3.png]] 650 - 651 - 652 -Convert the read byte to decimal and divide it by ten. 653 - 654 - 655 -**Example:** 656 - 657 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 658 - 659 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 660 - 661 - 662 - 663 -== 2.4 Downlink Payload == 664 - 665 - 666 -By default, N95S31B prints the downlink payload to console port. 667 - 668 668 [[image:image-20220709100028-1.png]] 669 669 670 670 ... ... @@ -701,7 +701,7 @@ 701 701 ))) 702 702 703 703 ((( 704 -If payload = 0x04FF, it will reset the 95S31B603 +If payload = 0x04FF, it will reset the NDDS75 705 705 ))) 706 706 707 707 ... ... @@ -713,17 +713,51 @@ 713 713 714 714 715 715 716 -== 2. 5BatteryAnalysis==615 +== 2.6 LED Indicator == 717 717 718 718 719 - ===2.5.1BatteryType===618 +The NDDS75 has an internal LED which is to show the status of different state. 720 720 721 721 621 +* 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) 622 +* Then the LED will be on for 1 second means device is boot normally. 623 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 624 +* For each uplink probe, LED will be on for 500ms. 625 + 722 722 ((( 723 - TheN95S31B 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.627 + 724 724 ))) 725 725 630 + 631 + 632 +== 2.7 Firmware Change Log == 633 + 634 + 726 726 ((( 636 +Download URL & Firmware Change log 637 +))) 638 + 639 +((( 640 +[[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/]] 641 +))) 642 + 643 + 644 +((( 645 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 646 +))) 647 + 648 + 649 + 650 +== 2.8 Battery Analysis == 651 + 652 +=== 2.8.1 Battery Type === 653 + 654 + 655 +((( 656 +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. 657 +))) 658 + 659 +((( 727 727 The battery is designed to last for several years depends on the actually use environment and update interval. 728 728 ))) 729 729 ... ... @@ -741,37 +741,56 @@ 741 741 742 742 743 743 744 -=== 2. 5.2 Power consumption Analyze ===677 +=== 2.8.2 Power consumption Analyze === 745 745 679 +((( 680 +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. 681 +))) 746 746 683 + 747 747 ((( 748 - 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.685 +Instruction to use as below: 749 749 ))) 750 750 751 751 ((( 752 - 689 +(% 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/]] 753 753 ))) 754 754 755 755 756 -=== 2.5.3 Battery Note === 693 +((( 694 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 695 +))) 757 757 697 +* ((( 698 +Product Model 699 +))) 700 +* ((( 701 +Uplink Interval 702 +))) 703 +* ((( 704 +Working Mode 705 +))) 758 758 759 759 ((( 760 - 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.708 +And the Life expectation in difference case will be shown on the right. 761 761 ))) 762 762 711 +[[image:image-20220709110451-3.png]] 763 763 764 764 765 -=== 2.5.4 Replace the battery === 766 766 715 +=== 2.8.3 Battery Note === 767 767 768 768 ((( 769 - 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.718 +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. 770 770 ))) 771 771 772 772 722 + 723 +=== 2.8.4 Replace the battery === 724 + 773 773 ((( 774 -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).726 +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). 775 775 ))) 776 776 777 777 ... ... @@ -778,7 +778,6 @@ 778 778 779 779 = 3. Access NB-IoT Module = 780 780 781 - 782 782 ((( 783 783 Users can directly access the AT command set of the NB-IoT module. 784 784 ))) ... ... @@ -785,8 +785,6 @@ 785 785 786 786 ((( 787 787 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/]] 788 - 789 - 790 790 ))) 791 791 792 792 [[image:1657333200519-600.png]] ... ... @@ -795,13 +795,11 @@ 795 795 796 796 = 4. Using the AT Commands = 797 797 798 - 799 799 == 4.1 Access AT Commands == 800 800 749 +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/]] 801 801 802 -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]] 803 803 804 - 805 805 AT+<CMD>? : Help on <CMD> 806 806 807 807 AT+<CMD> : Run <CMD> ... ... @@ -875,7 +875,6 @@ 875 875 876 876 = 5. FAQ = 877 877 878 - 879 879 == 5.1 How to Upgrade Firmware == 880 880 881 881 ... ... @@ -888,18 +888,13 @@ 888 888 ))) 889 889 890 890 ((( 891 - 892 - 893 -((( 894 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 837 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 895 895 ))) 896 -))) 897 897 898 898 899 899 900 900 = 6. Trouble Shooting = 901 901 902 - 903 903 == 6.1 Connection problem when uploading firmware == 904 904 905 905 ... ... @@ -915,7 +915,6 @@ 915 915 916 916 == 6.2 AT Command input doesn't work == 917 917 918 - 919 919 ((( 920 920 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. 921 921 ... ... @@ -926,7 +926,7 @@ 926 926 = 7. Order Info = 927 927 928 928 929 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**869 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 930 930 931 931 932 932 (% class="wikigeneratedid" %) ... ... @@ -941,7 +941,7 @@ 941 941 942 942 (% style="color:#037691" %)**Package Includes**: 943 943 944 -* N 95S31BNB-IoTTemperatureandHumiditySensor884 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 945 945 * External antenna x 1 946 946 ))) 947 947 ... ... @@ -950,10 +950,11 @@ 950 950 951 951 (% style="color:#037691" %)**Dimension and weight**: 952 952 893 + 953 953 * Device Size: 13.0 x 5 x 4.5 cm 954 954 * Device Weight: 150g 955 -* Package Size / pcs : 1 4.0x8x 5 cm956 -* Weight / pcs : 180g896 +* Package Size / pcs : 15 x 12x 5.5 cm 897 +* Weight / pcs : 220g 957 957 ))) 958 958 959 959 ((( ... ... @@ -965,9 +965,5 @@ 965 965 966 966 = 9. Support = 967 967 968 - 969 969 * 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. 970 970 * 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]] 971 - 972 - 973 -
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -144.8 KB - Content
- 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