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, 12 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 ))) ... ... @@ -89,6 +89,7 @@ 89 89 90 90 (% style="color:#037691" %)**Battery:** 91 91 77 + 92 92 * Li/SOCI2 un-chargeable battery 93 93 * Capacity: 8500mAh 94 94 * Self Discharge: <1% / Year @ 25°C ... ... @@ -99,7 +99,6 @@ 99 99 100 100 == 1.4 Applications == 101 101 102 - 103 103 * Smart Buildings & Home Automation 104 104 * Logistics and Supply Chain Management 105 105 * Smart Metering ... ... @@ -111,20 +111,15 @@ 111 111 112 112 113 113 99 +== 1.5 Pin Definitions == 114 114 115 -== 1.5 Pin Definitions & Switch == 116 - 117 - 118 118 N95S31B use the mother board from NBSN95 which as below. 119 119 120 - 121 121 [[image:image-20220709144723-1.png]] 122 122 123 123 124 - 125 125 === 1.5.1 Jumper JP2 === 126 126 127 - 128 128 Power on Device when put this jumper. 129 129 130 130 ... ... @@ -131,20 +131,14 @@ 131 131 132 132 === 1.5.2 BOOT MODE / SW1 === 133 133 134 - 135 -((( 136 136 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. 137 -))) 138 138 139 -((( 140 140 2) Flash: work mode, device starts to work and send out console output for further debug 141 -))) 142 142 143 143 144 144 145 145 === 1.5.3 Reset Button === 146 146 147 - 148 148 Press to reboot the device. 149 149 150 150 ... ... @@ -151,7 +151,6 @@ 151 151 152 152 === 1.5.4 LED === 153 153 154 - 155 155 It will flash: 156 156 157 157 1. When boot the device in flash mode ... ... @@ -159,9 +159,9 @@ 159 159 160 160 161 161 135 + 162 162 = 2. Use N95S31B to communicate with IoT Server = 163 163 164 - 165 165 == 2.1 How it works == 166 166 167 167 ... ... @@ -178,7 +178,7 @@ 178 178 179 179 ))) 180 180 181 -[[image:16575 20100595-569.png]]154 +[[image:1657350248151-650.png]] 182 182 183 183 ((( 184 184 ... ... @@ -194,49 +194,27 @@ 194 194 [[image:image-20220709150546-2.png]] 195 195 196 196 197 - 198 198 === 2.2.1 Test Requirement === 199 199 200 200 201 -((( 202 202 To use N95S31B in your city, make sure meet below requirements: 203 -))) 204 204 205 -* ((( 206 -Your local operator has already distributed a NB-IoT Network there. 207 -))) 208 -* ((( 209 -The local NB-IoT network used the band that N95S31B supports. 210 -))) 211 -* ((( 212 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 213 -))) 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. 214 214 215 - (((179 + 216 216 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 217 -))) 218 218 219 -((( 220 220 N95S31B supports different communication protocol such as : 221 -))) 222 222 223 223 ((( 224 -* ((( 225 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 226 -))) 227 -* ((( 228 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 229 -))) 230 -* ((( 231 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 232 -))) 233 -* ((( 234 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 235 -))) 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(%%)) 236 236 237 -((( 238 238 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. 239 -))) 240 240 241 241 242 242 ))) ... ... @@ -247,7 +247,6 @@ 247 247 248 248 === 2.2.3 Insert SIM card === 249 249 250 - 251 251 ((( 252 252 Insert the NB-IoT Card get from your provider. 253 253 ))) ... ... @@ -263,18 +263,14 @@ 263 263 264 264 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 265 265 266 - 267 267 ((( 268 268 ((( 269 269 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. 270 - 271 - 272 272 ))) 273 273 ))) 274 274 275 275 [[image:1657351312545-300.png]] 276 276 277 - 278 278 **Connection:** 279 279 280 280 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -298,9 +298,8 @@ 298 298 299 299 [[image:1657329814315-101.png]] 300 300 301 - 302 302 ((( 303 -(% 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/]] 304 304 ))) 305 305 306 306 ... ... @@ -307,10 +307,9 @@ 307 307 308 308 === 2.2.5 Use CoAP protocol to uplink data === 309 309 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/]] 310 310 311 -(% 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/]]** 312 312 313 - 314 314 ((( 315 315 **Use below commands:** 316 316 ))) ... ... @@ -319,10 +319,10 @@ 319 319 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 320 320 ))) 321 321 * ((( 322 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** 266 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 323 323 ))) 324 324 * ((( 325 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ 269 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 326 326 ))) 327 327 328 328 ((( ... ... @@ -349,119 +349,109 @@ 349 349 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 350 350 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 351 351 352 -[[image:16573 52391268-297.png]]296 +[[image:1657330501006-241.png]] 353 353 354 354 355 -[[image:16573 52403317-397.png]]299 +[[image:1657330533775-472.png]] 356 356 357 357 358 358 359 -=== 2.2. 7Use MQTT protocol to uplink data ===303 +=== 2.2.6 Use MQTT protocol to uplink data === 360 360 361 361 362 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 363 - 364 364 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 365 365 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 366 366 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 367 367 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 368 368 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 369 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527370 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)311 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 312 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 371 371 372 -[[image:1657 352634421-276.png]]314 +[[image:1657249978444-674.png]] 373 373 374 374 375 -[[image:16573 52645687-385.png]]317 +[[image:1657330723006-866.png]] 376 376 377 377 378 378 ((( 379 -To savebatterylife,N95S31Bwillestablishasubscriptionbeforeeachuplinkandclose thesubscription3 secondsafteruplinksuccessful. Any downlink commandsfromserver will onlyarriveduringthesubscriptionperiod.321 +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. 380 380 ))) 381 381 382 382 383 -((( 384 -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. 385 -))) 386 386 326 +=== 2.2.7 Use TCP protocol to uplink data === 387 387 388 388 389 -=== 2.2.8 Use TCP protocol to uplink data === 390 - 391 - 392 -This feature is supported since firmware version v110 393 - 394 394 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 395 395 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 396 396 397 -[[image: 1657352898400-901.png]]332 +[[image:image-20220709093918-1.png]] 398 398 399 399 400 -[[image: 1657352914475-252.png]]335 +[[image:image-20220709093918-2.png]] 401 401 402 402 403 403 404 -=== 2.2. 9Change Update Interval ===339 +=== 2.2.8 Change Update Interval === 405 405 406 - 407 407 User can use below command to change the (% style="color:green" %)**uplink interval**. 408 408 409 409 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 410 410 411 411 ((( 412 - 346 +(% style="color:red" %)**NOTE:** 413 413 ))) 414 414 415 415 ((( 416 -(% style="color:red" %) **NOTE:Sincefirmware version is v1.2:**350 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 417 417 ))) 418 418 419 -((( 420 -(% 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).** 421 -))) 422 422 423 423 424 - 425 425 == 2.3 Uplink Payload == 426 426 357 +In this mode, uplink payload includes in total 14 bytes 427 427 428 -((( 429 -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. 430 -))) 431 431 360 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 361 +|=(% style="width: 60px;" %)((( 362 +**Size(bytes)** 363 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 364 +|(% 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"]] 432 432 433 433 ((( 434 - For example:367 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 435 435 ))) 436 436 437 -((( 438 - (% 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. 439 -))) 440 440 371 +[[image:1657331036973-987.png]] 441 441 442 442 ((( 443 -The uplink payloadsare composedinASCIIString.Forxample:374 +The payload is ASCII string, representative same HEX: 444 444 ))) 445 445 446 446 ((( 447 -0 a cd00ed0acc0ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:378 +0x72403155615900640c6c19029200 where: 448 448 ))) 449 449 450 -((( 451 - 0x 0acd 00ed0acc0000ef 02d21d Total12 bytes381 +* ((( 382 +Device ID: 0x724031556159 = 724031556159 452 452 ))) 453 - 454 - 455 -((( 456 -(% style="color:red" %)**NOTE:** 384 +* ((( 385 +Version: 0x0064=100=1.0.0 457 457 ))) 458 458 459 -(% style="color:red" %) 460 -1. ((( 461 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 388 +* ((( 389 +BAT: 0x0c6c = 3180 mV = 3.180V 462 462 ))) 463 -1. ((( 464 -**By default, the device will send an uplink message every 1 hour.** 391 +* ((( 392 +Signal: 0x19 = 25 393 +))) 394 +* ((( 395 +Distance: 0x0292= 658 mm 396 +))) 397 +* ((( 398 +Interrupt: 0x00 = 0 465 465 466 466 467 467 ... ... @@ -468,191 +468,105 @@ 468 468 469 469 ))) 470 470 471 -== =2.3.1PayloadAnalyze ===405 +== 2.4 Payload Explanation and Sensor Interface == 472 472 473 473 474 -=== =2.3.1.1Before Firmwarev1.2====408 +=== 2.4.1 Device ID === 475 475 476 - 477 -N95S31B uplink payload includes in total 21 bytes 478 - 479 - 480 -(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:745px" %) 481 -|=(% style="width: 60px;" %)((( 482 -**Size(bytes)** 483 -)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 162px;" %)5|=(% style="width: 102px;" %)**2**|=(% style="width: 81px;" %)**2** 484 -|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)((( 485 485 ((( 486 - Reserve/Same asNBSN95CFGMOD=1411 +By default, the Device ID equal to the last 6 bytes of IMEI. 487 487 ))) 488 488 489 489 ((( 490 - Nofunctionhere.415 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 491 491 ))) 492 -)))|(% style="width:102px" %)((( 493 -((( 494 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 495 -))) 496 496 497 497 ((( 498 - By SHT31419 +**Example:** 499 499 ))) 500 -)))|(% style="width:81px" %)((( 501 -((( 502 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 503 -))) 504 504 505 505 ((( 506 - By SHT31423 +AT+DEUI=A84041F15612 507 507 ))) 508 -))) 509 509 510 510 ((( 511 - 512 - 513 -((( 514 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 427 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 515 515 ))) 516 -))) 517 517 518 518 519 -[[image:1657354294009-643.png]] 520 520 432 +=== 2.4.2 Version Info === 521 521 522 -The payload is ASCII string, representative same HEX: **0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 434 +((( 435 +Specify the software version: 0x64=100, means firmware version 1.00. 436 +))) 523 523 524 -**where:** 438 +((( 439 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 440 +))) 525 525 526 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 527 527 528 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 529 529 530 - *(%style="color:#037691"%)**BAT:**(%%) 0x0ccd=3277 mV=3.277V444 +=== 2.4.3 Battery Info === 531 531 532 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 533 - 534 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 535 - 536 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 537 - 538 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 539 - 540 -* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 541 - 542 542 ((( 543 - 447 +Ex1: 0x0B45 = 2885mV 448 +))) 544 544 545 - 546 - 450 +((( 451 +Ex2: 0x0B49 = 2889mV 547 547 ))) 548 548 549 -==== 2.3.1.2 Since Firmware v1.2 ==== 550 550 551 551 552 - Inthismode, uplink payloadincludes 91 bytes inotalby default.456 +=== 2.4.4 Signal Strength === 553 553 554 -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. 555 - 556 - 557 -(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %) 558 -|(% 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** 559 -|(% 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 ..... 560 - 561 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 562 - 563 - 564 -[[image:image-20220908154949-1.png]] 565 - 566 - 567 -The payload is ASCII string, representative same HEX: 568 - 569 -**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ __0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 570 - 571 -**where:** 572 - 573 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 574 - 575 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 576 - 577 -* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 578 - 579 -* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 580 - 581 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 582 - 583 -* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 584 - 585 -* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 586 - 587 -* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 588 - 589 -* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 590 - 591 -* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 592 - 593 -* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 594 - 595 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 596 - 597 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 598 - 599 - 600 - 601 - 602 -=== 2.3.2 Device ID === 603 - 604 - 605 605 ((( 606 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.459 +NB-IoT Network signal Strength. 607 607 ))) 608 608 609 609 ((( 610 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 463 +**Ex1: 0x1d = 29** 464 +))) 611 611 612 - 466 +((( 467 +(% style="color:blue" %)**0**(%%) -113dBm or less 613 613 ))) 614 614 615 615 ((( 616 -(% style="color:blue" %)** Example:**471 +(% style="color:blue" %)**1**(%%) -111dBm 617 617 ))) 618 618 619 619 ((( 620 - AT+DEUI=A84041F15612475 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 621 621 ))) 622 622 623 623 ((( 624 -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. 479 +(% style="color:blue" %)**31** (%%) -51dBm or greater 480 +))) 625 625 626 - 482 +((( 483 +(% style="color:blue" %)**99** (%%) Not known or not detectable 627 627 ))) 628 628 629 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 630 630 631 631 632 - Bydefault,theDeviceID equal to the last 15 bits of IMEI.488 +=== 2.4.5 Distance === 633 633 634 - Usercan use**(%style="color:blue"%)AT+DEUI(%%)**tosetDeviceID490 +Get the distance. Flat object range 280mm - 7500mm. 635 635 636 - 637 -(% style="color:blue" %)**Example:** 638 - 639 -AT+DEUI=868411056754138 640 - 641 - 642 - 643 -=== 2.3.3 Version Info === 644 - 645 - 646 646 ((( 647 - Thesebytes include the hardware andsoftwareversion.493 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 648 648 ))) 649 649 650 650 ((( 651 -Higher byte: Specify hardware version: always 0x00 for N95S31B 497 +((( 498 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 652 652 ))) 500 +))) 653 653 654 654 ((( 655 - Lowerbyte: Specify the software version: 0x6E=110, means firmware version 110503 + 656 656 ))) 657 657 658 658 ((( ... ... @@ -659,85 +659,65 @@ 659 659 660 660 ))) 661 661 510 +=== 2.4.6 Digital Interrupt === 511 + 662 662 ((( 663 - For example:0x00 6E:thisdevice isN95S31Bwithfirmwareversion110.513 +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. 664 664 ))) 665 665 666 666 ((( 667 - 517 +The command is: 668 668 ))) 669 669 670 - 671 -=== 2.3.4 Battery Info === 672 - 673 - 674 674 ((( 675 - Ex1:0x0B45=2885mV521 +(% 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]])**.** 676 676 ))) 677 677 524 + 678 678 ((( 679 - Ex2:0x0B49=2889mV526 +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. 680 680 ))) 681 681 682 682 683 - 684 -=== 2.3.5 Signal Strength === 685 - 686 - 687 687 ((( 688 - NB-IoT Network signalStrength.531 +Example: 689 689 ))) 690 690 691 691 ((( 692 - **Ex1:0x1d=29**535 +0x(00): Normal uplink packet. 693 693 ))) 694 694 695 695 ((( 696 -( %style="color:blue"%)**0**(%%) -113dBm orless539 +0x(01): Interrupt Uplink Packet. 697 697 ))) 698 698 542 + 543 + 544 +=== 2.4.7 +5V Output === 545 + 699 699 ((( 700 - (%style="color:blue"%)**1**(%%)-111dBm547 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 701 701 ))) 702 702 550 + 703 703 ((( 704 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm552 +The 5V output time can be controlled by AT Command. 705 705 ))) 706 706 707 707 ((( 708 -(% style="color:blue" %)** 31**(%%) -51dBm or greater556 +(% style="color:blue" %)**AT+5VT=1000** 709 709 ))) 710 710 711 711 ((( 712 - (%style="color:blue"%)**99**(%%)Notknownornotdetectable560 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 713 713 ))) 714 714 715 715 716 716 717 -== =2.3.6Temperature & Humidity ===565 +== 2.5 Downlink Payload == 718 718 567 +By default, NDDS75 prints the downlink payload to console port. 719 719 720 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 721 - 722 -[[image:image-20220709161741-3.png]] 723 - 724 - 725 -Convert the read byte to decimal and divide it by ten. 726 - 727 - 728 -**Example:** 729 - 730 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 731 - 732 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 733 - 734 - 735 - 736 -== 2.4 Downlink Payload == 737 - 738 - 739 -By default, N95S31B prints the downlink payload to console port. 740 - 741 741 [[image:image-20220709100028-1.png]] 742 742 743 743 ... ... @@ -774,7 +774,7 @@ 774 774 ))) 775 775 776 776 ((( 777 -If payload = 0x04FF, it will reset the 95S31B605 +If payload = 0x04FF, it will reset the NDDS75 778 778 ))) 779 779 780 780 ... ... @@ -786,76 +786,48 @@ 786 786 787 787 788 788 789 -== 2. 5HumidityandTemperaturealarm function==617 +== 2.6 LED Indicator == 790 790 791 791 792 - **~(%style="color:blue"%)➢ATCommand:(%%)**620 +The NDDS75 has an internal LED which is to show the status of different state. 793 793 794 794 795 -(% style="color:#037691" %)**AT+ SHHUM=min,max** 623 +* 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) 624 +* Then the LED will be on for 1 second means device is boot normally. 625 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 626 +* For each uplink probe, LED will be on for 500ms. 796 796 628 +((( 629 + 630 +))) 797 797 798 -² When min=0, and max≠0, Alarm higher than max 799 799 800 -² When min≠0, and max=0, Alarm lower than min 801 801 802 - ²Whenmin≠0 andmax≠0, Alarm higherthanmaxorlower than min634 +== 2.7 Firmware Change Log == 803 803 804 804 805 - (% style="color:blue" %)**Example:** 637 +((( 638 +Download URL & Firmware Change log 639 +))) 806 806 807 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 641 +((( 642 +[[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/]] 643 +))) 808 808 809 809 810 -(% style="color:#037691" %)**AT+ SHTEMP=min,max** 646 +((( 647 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 648 +))) 811 811 812 -² When min=0, and max≠0, Alarm higher than max 813 813 814 -² When min≠0, and max=0, Alarm lower than min 815 815 816 -² When min≠0 and max≠0, Alarm higher than max or lower than min 817 - 818 - 819 -**~ (% style="color:blue" %)Example:(%%)** 820 - 821 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 822 - 823 - 824 - 825 -== 2.6 Set the number of data to be uploaded and the recording time == 826 - 827 - 828 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 829 - 830 -* (% style="color:#037691" %)**AT+TR=900** (%%)~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds) 831 -* (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 832 - 833 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 834 - 835 -[[image:image-20221009001045-1.png||height="726" width="1009"]] 836 - 837 - 838 - 839 -== 2.7 Read or Clear cached data == 840 - 841 - 842 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 843 - 844 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 845 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 846 - 847 -[[image:image-20220908163102-2.png]] 848 - 849 - 850 - 851 851 == 2.8 Battery Analysis == 852 852 853 - 854 854 === 2.8.1 Battery Type === 855 855 856 856 857 857 ((( 858 -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.658 +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. 859 859 ))) 860 860 861 861 ((( ... ... @@ -878,35 +878,54 @@ 878 878 879 879 === 2.8.2 Power consumption Analyze === 880 880 681 +((( 682 +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. 683 +))) 881 881 685 + 882 882 ((( 883 - 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.687 +Instruction to use as below: 884 884 ))) 885 885 886 886 ((( 887 - 691 +(% 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/]] 888 888 ))) 889 889 890 890 891 -=== 2.8.3 Battery Note === 695 +((( 696 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 697 +))) 892 892 699 +* ((( 700 +Product Model 701 +))) 702 +* ((( 703 +Uplink Interval 704 +))) 705 +* ((( 706 +Working Mode 707 +))) 893 893 894 894 ((( 895 - 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.710 +And the Life expectation in difference case will be shown on the right. 896 896 ))) 897 897 713 +[[image:image-20220709110451-3.png]] 898 898 899 899 900 -=== 2.8.4 Replace the battery === 901 901 717 +=== 2.8.3 Battery Note === 902 902 903 903 ((( 904 - 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.720 +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. 905 905 ))) 906 906 907 907 724 + 725 +=== 2.8.4 Replace the battery === 726 + 908 908 ((( 909 -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).728 +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). 910 910 ))) 911 911 912 912 ... ... @@ -913,7 +913,6 @@ 913 913 914 914 = 3. Access NB-IoT Module = 915 915 916 - 917 917 ((( 918 918 Users can directly access the AT command set of the NB-IoT module. 919 919 ))) ... ... @@ -920,8 +920,6 @@ 920 920 921 921 ((( 922 922 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/]] 923 - 924 - 925 925 ))) 926 926 927 927 [[image:1657333200519-600.png]] ... ... @@ -930,13 +930,11 @@ 930 930 931 931 = 4. Using the AT Commands = 932 932 933 - 934 934 == 4.1 Access AT Commands == 935 935 751 +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/]] 936 936 937 -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]] 938 938 939 - 940 940 AT+<CMD>? : Help on <CMD> 941 941 942 942 AT+<CMD> : Run <CMD> ... ... @@ -976,24 +976,7 @@ 976 976 977 977 AT+SERVADDR : Server Address 978 978 979 -AT+TR : Get or Set record time 980 980 981 -AT+APN : Get or set the APN 982 - 983 -AT+FBAND : Get or Set whether to automatically modify the frequency band 984 - 985 -AT+DNSCFG : Get or Set DNS Server 986 - 987 -AT+GETSENSORVALUE : Returns the current sensor measurement 988 - 989 -AT+NOUD : Get or Set the number of data to be uploaded 990 - 991 -AT+CDP : Read or Clear cached data 992 - 993 -AT+SHTEMP: Get or Set alarm of temp 994 - 995 -AT+SHHUM: Get or Set alarm of moisture 996 - 997 997 (% style="color:#037691" %)**COAP Management** 998 998 999 999 AT+URI : Resource parameters ... ... @@ -1027,7 +1027,6 @@ 1027 1027 1028 1028 = 5. FAQ = 1029 1029 1030 - 1031 1031 == 5.1 How to Upgrade Firmware == 1032 1032 1033 1033 ... ... @@ -1040,18 +1040,13 @@ 1040 1040 ))) 1041 1041 1042 1042 ((( 1043 - 1044 - 1045 -((( 1046 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 839 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 1047 1047 ))) 1048 -))) 1049 1049 1050 1050 1051 1051 1052 1052 = 6. Trouble Shooting = 1053 1053 1054 - 1055 1055 == 6.1 Connection problem when uploading firmware == 1056 1056 1057 1057 ... ... @@ -1067,7 +1067,6 @@ 1067 1067 1068 1068 == 6.2 AT Command input doesn't work == 1069 1069 1070 - 1071 1071 ((( 1072 1072 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. 1073 1073 ... ... @@ -1078,7 +1078,7 @@ 1078 1078 = 7. Order Info = 1079 1079 1080 1080 1081 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**871 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 1082 1082 1083 1083 1084 1084 (% class="wikigeneratedid" %) ... ... @@ -1093,7 +1093,7 @@ 1093 1093 1094 1094 (% style="color:#037691" %)**Package Includes**: 1095 1095 1096 -* N 95S31BNB-IoTTemperatureandHumiditySensor886 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 1097 1097 * External antenna x 1 1098 1098 ))) 1099 1099 ... ... @@ -1102,10 +1102,11 @@ 1102 1102 1103 1103 (% style="color:#037691" %)**Dimension and weight**: 1104 1104 895 + 1105 1105 * Device Size: 13.0 x 5 x 4.5 cm 1106 1106 * Device Weight: 150g 1107 -* Package Size / pcs : 1 4.0x8x 5 cm1108 -* Weight / pcs : 180g898 +* Package Size / pcs : 15 x 12x 5.5 cm 899 +* Weight / pcs : 220g 1109 1109 ))) 1110 1110 1111 1111 ((( ... ... @@ -1117,6 +1117,5 @@ 1117 1117 1118 1118 = 9. Support = 1119 1119 1120 - 1121 1121 * 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. 1122 1122 * 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]]
- 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
- image-20221009001045-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content