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, 15 removed)
- 1657350625843-586.png
- 1657351240556-536.png
- 1657351312545-300.png
- 1657352146020-183.png
- 1657352185396-303.png
- 1657352391268-297.png
- 1657352403317-397.png
- 1657352634421-276.png
- 1657352645687-385.png
- 1657352898400-901.png
- 1657352914475-252.png
- 1657354294009-643.png
- 1657520100595-569.png
- image-20220709150546-2.png
- image-20220709161741-3.png
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 ... ... @@ -22,29 +22,16 @@ 22 22 ((( 23 23 24 24 25 -((( 26 26 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*. 27 -))) 28 28 29 -((( 30 30 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. 31 -))) 32 32 33 -((( 34 34 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 -))) 36 36 37 -((( 38 38 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). 39 -))) 40 40 41 -((( 42 - 43 -))) 44 44 45 -((( 46 46 ~* make sure you have NB-IoT coverage locally. 47 -))) 48 48 49 49 50 50 ))) ... ... @@ -55,6 +55,7 @@ 55 55 56 56 == 1.2 Features == 57 57 44 + 58 58 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 59 59 * Monitor Temperature & Humidity via SHT31 60 60 * AT Commands to change parameters ... ... @@ -87,6 +87,7 @@ 87 87 88 88 (% style="color:#037691" %)**Battery:** 89 89 77 + 90 90 * Li/SOCI2 un-chargeable battery 91 91 * Capacity: 8500mAh 92 92 * Self Discharge: <1% / Year @ 25°C ... ... @@ -108,7 +108,7 @@ 108 108 109 109 110 110 111 -== 1.5 Pin Definitions & Switch==99 +== 1.5 Pin Definitions == 112 112 113 113 N95S31B use the mother board from NBSN95 which as below. 114 114 ... ... @@ -123,13 +123,9 @@ 123 123 124 124 === 1.5.2 BOOT MODE / SW1 === 125 125 126 -((( 127 127 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. 128 -))) 129 129 130 -((( 131 131 2) Flash: work mode, device starts to work and send out console output for further debug 132 -))) 133 133 134 134 135 135 ... ... @@ -148,6 +148,7 @@ 148 148 149 149 150 150 135 + 151 151 = 2. Use N95S31B to communicate with IoT Server = 152 152 153 153 == 2.1 How it works == ... ... @@ -166,7 +166,7 @@ 166 166 167 167 ))) 168 168 169 -[[image:1657 520100595-569.png]]154 +[[image:1657328659945-416.png]] 170 170 171 171 ((( 172 172 ... ... @@ -173,67 +173,30 @@ 173 173 ))) 174 174 175 175 176 -== 2.2 Configure the N 95S31B==161 +== 2.2 Configure the NDDS75 == 177 177 178 178 179 -=== 2.2.1 Power On N95S31B === 180 - 181 - 182 -[[image:image-20220709150546-2.png]] 183 - 184 - 185 185 === 2.2.1 Test Requirement === 186 186 187 - 188 188 ((( 189 -To use N 95S31Bin your city, make sure meet below requirements:167 +To use NDDS75 in your city, make sure meet below requirements: 190 190 ))) 191 191 192 -* ((( 193 -Your local operator has already distributed a NB-IoT Network there. 194 -))) 195 -* ((( 196 -The local NB-IoT network used the band that N95S31B supports. 197 -))) 198 -* ((( 199 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 200 -))) 170 +* Your local operator has already distributed a NB-IoT Network there. 171 +* The local NB-IoT network used the band that NSE01 supports. 172 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 201 201 202 202 ((( 203 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 175 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server 204 204 ))) 205 205 206 -((( 207 -N95S31B supports different communication protocol such as : 208 -))) 209 209 210 -((( 211 -* ((( 212 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 213 -))) 214 -* ((( 215 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 216 -))) 217 -* ((( 218 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 219 -))) 220 -* ((( 221 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 222 -))) 179 +[[image:1657328756309-230.png]] 223 223 224 -((( 225 -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. 226 -))) 227 227 228 - 229 -))) 230 230 231 - [[image:1657350625843-586.png]]183 +=== 2.2.2 Insert SIM card === 232 232 233 - 234 - 235 -=== 2.2.3 Insert SIM card === 236 - 237 237 ((( 238 238 Insert the NB-IoT Card get from your provider. 239 239 ))) ... ... @@ -243,19 +243,19 @@ 243 243 ))) 244 244 245 245 246 -[[image:16573 51240556-536.png]]194 +[[image:1657328884227-504.png]] 247 247 248 248 249 249 250 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===198 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 251 251 252 252 ((( 253 253 ((( 254 -User need to configure 95S31Bvia serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31Bsupport AT Commands, user can use a USB to TTL adapter to connect to95S31Band use AT Commands to configure it, as below.202 +User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below. 255 255 ))) 256 256 ))) 257 257 258 -[[image: 1657351312545-300.png]]206 +[[image:image-20220709092052-2.png]] 259 259 260 260 **Connection:** 261 261 ... ... @@ -275,18 +275,18 @@ 275 275 * Flow Control: (% style="color:green" %)**None** 276 276 277 277 ((( 278 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N 95S31B.95S31Bwill output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.226 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 279 279 ))) 280 280 281 281 [[image:1657329814315-101.png]] 282 282 283 283 ((( 284 -(% style="color:red" %)Note: the valid AT Commands can be found at: 95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]232 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]] 285 285 ))) 286 286 287 287 288 288 289 -=== 2.2. 5Use CoAP protocol to uplink data ===237 +=== 2.2.4 Use CoAP protocol to uplink data === 290 290 291 291 (% 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/]] 292 292 ... ... @@ -306,12 +306,10 @@ 306 306 ))) 307 307 308 308 ((( 309 - 310 - 311 311 For parameter description, please refer to AT command set 312 312 ))) 313 313 314 -[[image:1657352 146020-183.png]]260 +[[image:1657330452568-615.png]] 315 315 316 316 317 317 ((( ... ... @@ -318,11 +318,11 @@ 318 318 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. 319 319 ))) 320 320 321 -[[image:16573 52185396-303.png]]267 +[[image:1657330472797-498.png]] 322 322 323 323 324 324 325 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===271 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 326 326 327 327 328 328 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -329,16 +329,15 @@ 329 329 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 330 330 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 331 331 332 -[[image:16573 52391268-297.png]]278 +[[image:1657330501006-241.png]] 333 333 334 334 335 -[[image:16573 52403317-397.png]]281 +[[image:1657330533775-472.png]] 336 336 337 337 338 338 339 -=== 2.2. 7Use MQTT protocol to uplink data ===285 +=== 2.2.6 Use MQTT protocol to uplink data === 340 340 341 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 342 342 343 343 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 344 344 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -345,40 +345,35 @@ 345 345 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 346 346 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 347 347 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 348 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527349 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)293 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 294 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 350 350 351 -[[image:1657 352634421-276.png]]296 +[[image:1657249978444-674.png]] 352 352 353 353 354 -[[image:16573 52645687-385.png]]299 +[[image:1657330723006-866.png]] 355 355 356 -((( 357 -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. 358 -))) 359 359 360 - 361 361 ((( 362 -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.303 +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. 363 363 ))) 364 364 365 365 366 366 367 -=== 2.2. 8Use TCP protocol to uplink data ===308 +=== 2.2.7 Use TCP protocol to uplink data === 368 368 369 -This feature is supported since firmware version v110 370 370 371 371 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 372 372 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 373 373 374 -[[image: 1657352898400-901.png]]314 +[[image:image-20220709093918-1.png]] 375 375 376 376 377 -[[image: 1657352914475-252.png]]317 +[[image:image-20220709093918-2.png]] 378 378 379 379 380 380 381 -=== 2.2. 9Change Update Interval ===321 +=== 2.2.8 Change Update Interval === 382 382 383 383 User can use below command to change the (% style="color:green" %)**uplink interval**. 384 384 ... ... @@ -385,155 +385,164 @@ 385 385 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 386 386 387 387 ((( 388 - 328 +(% style="color:red" %)**NOTE:** 389 389 ))) 390 390 331 +((( 332 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 333 +))) 391 391 392 392 336 + 393 393 == 2.3 Uplink Payload == 394 394 339 +In this mode, uplink payload includes in total 14 bytes 395 395 396 -((( 397 -NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes. 398 -))) 399 399 342 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 343 +|=(% style="width: 60px;" %)((( 344 +**Size(bytes)** 345 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 346 +|(% 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"]] 400 400 401 401 ((( 402 - For example:349 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 403 403 ))) 404 404 405 -((( 406 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 407 -))) 408 408 353 +[[image:1657331036973-987.png]] 409 409 410 410 ((( 411 -The uplink payloadsare composedinASCIIString.Forxample:356 +The payload is ASCII string, representative same HEX: 412 412 ))) 413 413 414 414 ((( 415 -0 a cd00ed0acc0ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:360 +0x72403155615900640c6c19029200 where: 416 416 ))) 417 417 418 -((( 419 - 0x 0acd 00ed0acc0000ef 02d21d Total12 bytes363 +* ((( 364 +Device ID: 0x724031556159 = 724031556159 420 420 ))) 421 - 422 - 423 -((( 424 -(% style="color:red" %)**NOTE:** 366 +* ((( 367 +Version: 0x0064=100=1.0.0 425 425 ))) 426 426 427 -(% style="color:red" %) 428 -1. ((( 429 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 370 +* ((( 371 +BAT: 0x0c6c = 3180 mV = 3.180V 430 430 ))) 431 - 1.(((432 - By default, the device will sendan uplinkmessage every1hour.373 +* ((( 374 +Signal: 0x19 = 25 433 433 ))) 376 +* ((( 377 +Distance: 0x0292= 658 mm 378 +))) 379 +* ((( 380 +Interrupt: 0x00 = 0 434 434 435 -=== 2.3.1 Payload Analyze === 436 436 437 -N95S31B uplink payload includes in total 21 bytes 438 438 384 + 385 +))) 439 439 440 - (%border="1"cellspacing="10"style="background-color:#ffffcc;color:green;width:520px" %)441 - |=(% style="width: 60px;" %)(((442 - **Size(bytes)**443 - )))|=(% 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**444 - |(% 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" %)(((387 +== 2.4 Payload Explanation and Sensor Interface == 388 + 389 + 390 +=== 2.4.1 Device ID === 391 + 445 445 ((( 446 - Reserve/Same asNBSN95CFGMOD=1393 +By default, the Device ID equal to the last 6 bytes of IMEI. 447 447 ))) 448 448 449 449 ((( 450 - Nofunctionhere.397 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 451 451 ))) 452 - )))|(% style="width:77px" %)(((399 + 453 453 ((( 454 - [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]401 +**Example:** 455 455 ))) 456 456 457 457 ((( 458 - By SHT31405 +AT+DEUI=A84041F15612 459 459 ))) 460 - )))|(% style="width:80px" %)(((407 + 461 461 ((( 462 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]409 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 463 463 ))) 464 464 412 + 413 + 414 +=== 2.4.2 Version Info === 415 + 465 465 ((( 466 - BySHT31417 +Specify the software version: 0x64=100, means firmware version 1.00. 467 467 ))) 468 -))) 469 469 470 470 ((( 471 -((( 472 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 421 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 473 473 ))) 474 -))) 475 475 476 476 477 -[[image:1657354294009-643.png]] 478 478 426 +=== 2.4.3 Battery Info === 479 479 480 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 428 +((( 429 +Ex1: 0x0B45 = 2885mV 430 +))) 481 481 482 -* Device ID: 0x724031607457 = 724031607457 483 -* Version: 0x006e=110=1.1.0 432 +((( 433 +Ex2: 0x0B49 = 2889mV 434 +))) 484 484 485 -* BAT: 0x0ccd = 3277 mV = 3.277V 486 -* Signal: 0x1b = 27 487 -* Model: 0x01 = 1 488 -* 0x00dc000ccc= reserve, ignore in N95S31B 489 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 490 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 491 491 437 + 438 +=== 2.4.4 Signal Strength === 439 + 492 492 ((( 493 - 441 +NB-IoT Network signal Strength. 494 494 ))) 495 495 496 496 ((( 497 - 445 +**Ex1: 0x1d = 29** 498 498 ))) 499 499 500 - 501 -=== 2.3.2 Device ID === 502 - 503 503 ((( 504 - Bydefault, theDeviceIDequaltothelast6bytesofIMEI.449 +(% style="color:blue" %)**0**(%%) -113dBm or less 505 505 ))) 506 506 507 507 ((( 508 - User can use(% style="color:blue" %)**AT+DEUI**(%%)tosetDeviceID453 +(% style="color:blue" %)**1**(%%) -111dBm 509 509 ))) 510 510 511 511 ((( 512 - **Example:**457 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 513 513 ))) 514 514 515 515 ((( 516 - AT+DEUI=A84041F15612461 +(% style="color:blue" %)**31** (%%) -51dBm or greater 517 517 ))) 518 518 519 519 ((( 520 - TheDevice ID isstoredinanone-erasearea,Upgradethefirmwareorrun**AT+FDR** won't eraseDeviceID.465 +(% style="color:blue" %)**99** (%%) Not known or not detectable 521 521 ))) 522 522 523 523 524 524 525 -=== 2. 3.3VersionInfo===470 +=== 2.4.5 Distance === 526 526 472 +Get the distance. Flat object range 280mm - 7500mm. 473 + 527 527 ((( 528 - Thesebytes include the hardware andsoftwareversion.475 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 529 529 ))) 530 530 531 531 ((( 532 -Higher byte: Specify hardware version: always 0x00 for N95S31B 479 +((( 480 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 533 533 ))) 482 +))) 534 534 535 535 ((( 536 - Lowerbyte: Specify the software version: 0x6E=110, means firmware version 110485 + 537 537 ))) 538 538 539 539 ((( ... ... @@ -540,79 +540,63 @@ 540 540 541 541 ))) 542 542 492 +=== 2.4.6 Digital Interrupt === 493 + 543 543 ((( 544 - For example:0x00 6E:thisdevice isN95S31Bwithfirmwareversion110.495 +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. 545 545 ))) 546 546 547 547 ((( 548 - 499 +The command is: 549 549 ))) 550 550 551 - 552 -=== 2.3.4 Battery Info === 553 - 554 554 ((( 555 - Ex1:0x0B45=2885mV503 +(% 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]])**.** 556 556 ))) 557 557 506 + 558 558 ((( 559 - Ex2:0x0B49=2889mV508 +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. 560 560 ))) 561 561 562 562 563 - 564 -=== 2.3.5 Signal Strength === 565 - 566 566 ((( 567 - NB-IoT Network signalStrength.513 +Example: 568 568 ))) 569 569 570 570 ((( 571 - **Ex1:0x1d=29**517 +0x(00): Normal uplink packet. 572 572 ))) 573 573 574 574 ((( 575 -( %style="color:blue"%)**0**(%%) -113dBm orless521 +0x(01): Interrupt Uplink Packet. 576 576 ))) 577 577 524 + 525 + 526 +=== 2.4.7 +5V Output === 527 + 578 578 ((( 579 - (%style="color:blue"%)**1**(%%)-111dBm529 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 580 580 ))) 581 581 532 + 582 582 ((( 583 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm534 +The 5V output time can be controlled by AT Command. 584 584 ))) 585 585 586 586 ((( 587 -(% style="color:blue" %)** 31**(%%) -51dBm or greater538 +(% style="color:blue" %)**AT+5VT=1000** 588 588 ))) 589 589 590 590 ((( 591 - (%style="color:blue"%)**99**(%%)Notknownornotdetectable542 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 592 592 ))) 593 593 594 594 595 595 596 -== =2.3.6Temperature & Humidity ===547 +== 2.5 Downlink Payload == 597 597 598 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 599 - 600 -[[image:image-20220709161741-3.png]] 601 - 602 - 603 -Convert the read byte to decimal and divide it by ten. 604 - 605 - 606 -**Example:** 607 - 608 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 609 - 610 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 611 - 612 - 613 - 614 -== 2.4 Downlink Payload == 615 - 616 616 By default, NDDS75 prints the downlink payload to console port. 617 617 618 618 [[image:image-20220709100028-1.png]] ... ... @@ -663,16 +663,51 @@ 663 663 664 664 665 665 666 -== 2. 5BatteryAnalysis==599 +== 2.6 LED Indicator == 667 667 668 -=== 2.5.1 Battery Type === 669 669 602 +The NDDS75 has an internal LED which is to show the status of different state. 670 670 604 + 605 +* 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) 606 +* Then the LED will be on for 1 second means device is boot normally. 607 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 608 +* For each uplink probe, LED will be on for 500ms. 609 + 671 671 ((( 672 - 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.611 + 673 673 ))) 674 674 614 + 615 + 616 +== 2.7 Firmware Change Log == 617 + 618 + 675 675 ((( 620 +Download URL & Firmware Change log 621 +))) 622 + 623 +((( 624 +[[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/]] 625 +))) 626 + 627 + 628 +((( 629 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 630 +))) 631 + 632 + 633 + 634 +== 2.8 Battery Analysis == 635 + 636 +=== 2.8.1 Battery Type === 637 + 638 + 639 +((( 640 +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. 641 +))) 642 + 643 +((( 676 676 The battery is designed to last for several years depends on the actually use environment and update interval. 677 677 ))) 678 678 ... ... @@ -690,35 +690,56 @@ 690 690 691 691 692 692 693 -=== 2. 5.2 Power consumption Analyze ===661 +=== 2.8.2 Power consumption Analyze === 694 694 695 695 ((( 696 - The file**DRAGINO_N95S31B-Power-Analyzer.pdf**from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describesadetailmeasurementtoanalyzethepowerconsumption indifferentcase. User can useitfordesignguideline fortheirproject.664 +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. 697 697 ))) 698 698 667 + 699 699 ((( 700 - 669 +Instruction to use as below: 701 701 ))) 702 702 672 +((( 673 +(% 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/]] 674 +))) 703 703 704 -=== 2.5.3 Battery Note === 705 705 706 706 ((( 707 - TheLi-SICO batteryis designed for small current / long period application. It is not good tousea high current, short periodtransmitmethod.Therecommendedminimum period for use ofthisbattery is 5 minutes.If you use a shorter period time to uplink data, then the battery life may be decreased.678 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 708 708 ))) 709 709 681 +* ((( 682 +Product Model 683 +))) 684 +* ((( 685 +Uplink Interval 686 +))) 687 +* ((( 688 +Working Mode 689 +))) 710 710 691 +((( 692 +And the Life expectation in difference case will be shown on the right. 693 +))) 711 711 712 - === 2.5.4 Replacethe battery ===695 +[[image:image-20220709110451-3.png]] 713 713 714 714 698 + 699 +=== 2.8.3 Battery Note === 700 + 715 715 ((( 716 - 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.702 +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. 717 717 ))) 718 718 719 719 706 + 707 +=== 2.8.4 Replace the battery === 708 + 720 720 ((( 721 -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).710 +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). 722 722 ))) 723 723 724 724 ... ... @@ -741,7 +741,7 @@ 741 741 742 742 == 4.1 Access AT Commands == 743 743 744 -See NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]733 +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/]] 745 745 746 746 747 747 AT+<CMD>? : Help on <CMD> ... ... @@ -829,12 +829,8 @@ 829 829 ))) 830 830 831 831 ((( 832 - 833 - 834 -((( 835 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 821 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 836 836 ))) 837 -))) 838 838 839 839 840 840 ... ... @@ -865,7 +865,7 @@ 865 865 = 7. Order Info = 866 866 867 867 868 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**853 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 869 869 870 870 871 871 (% class="wikigeneratedid" %) ... ... @@ -880,7 +880,7 @@ 880 880 881 881 (% style="color:#037691" %)**Package Includes**: 882 882 883 -* N 95S31BNB-IoTTemperatureandHumiditySensor868 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 884 884 * External antenna x 1 885 885 ))) 886 886 ... ... @@ -889,10 +889,11 @@ 889 889 890 890 (% style="color:#037691" %)**Dimension and weight**: 891 891 877 + 892 892 * Device Size: 13.0 x 5 x 4.5 cm 893 893 * Device Weight: 150g 894 -* Package Size / pcs : 1 4.0x8x 5 cm895 -* Weight / pcs : 180g880 +* Package Size / pcs : 15 x 12x 5.5 cm 881 +* Weight / pcs : 220g 896 896 ))) 897 897 898 898 (((
- 1657350625843-586.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.3 KB - Content
- 1657351240556-536.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -483.6 KB - Content
- 1657351312545-300.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -675.8 KB - Content
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -98.3 KB - Content
- 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-20220709150546-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -333.5 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content