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, 8 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 ... ... @@ -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 ))) ... ... @@ -68,6 +68,7 @@ 68 68 * 8500mAh Battery for long term use 69 69 70 70 57 + 71 71 == 1.3 Specification == 72 72 73 73 ... ... @@ -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 ... ... @@ -94,9 +94,9 @@ 94 94 * Max boost current: 2A, 1 second 95 95 96 96 85 + 97 97 == 1.4 Applications == 98 98 99 - 100 100 * Smart Buildings & Home Automation 101 101 * Logistics and Supply Chain Management 102 102 * Smart Metering ... ... @@ -108,49 +108,43 @@ 108 108 109 109 110 110 111 -== 1.5 Pin Definitions & Switch==99 +== 1.5 Pin Definitions == 112 112 113 - 114 114 N95S31B use the mother board from NBSN95 which as below. 115 115 116 - 117 117 [[image:image-20220709144723-1.png]] 118 118 119 119 120 120 === 1.5.1 Jumper JP2 === 121 121 122 - 123 123 Power on Device when put this jumper. 124 124 125 125 111 + 126 126 === 1.5.2 BOOT MODE / SW1 === 127 127 114 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 128 128 129 -((( 130 -**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. 131 -))) 116 +2) Flash: work mode, device starts to work and send out console output for further debug 132 132 133 -((( 134 -**2) Flash:** work mode, device starts to work and send out console output for further debug 135 -))) 136 136 137 137 138 138 === 1.5.3 Reset Button === 139 139 140 - 141 141 Press to reboot the device. 142 142 143 143 125 + 144 144 === 1.5.4 LED === 145 145 146 - 147 147 It will flash: 148 148 149 -1. When boot the device in flash mode 130 +1. When boot the device in flash mode 131 +1. Send an uplink packet 150 150 151 -2. Send an uplink packet 152 152 153 153 135 + 154 154 = 2. Use N95S31B to communicate with IoT Server = 155 155 156 156 == 2.1 How it works == ... ... @@ -169,7 +169,7 @@ 169 169 170 170 ))) 171 171 172 -[[image:16575 20100595-569.png]]154 +[[image:1657350248151-650.png]] 173 173 174 174 ((( 175 175 ... ... @@ -178,6 +178,7 @@ 178 178 179 179 == 2.2 Configure the N95S31B == 180 180 163 + 181 181 === 2.2.1 Power On N95S31B === 182 182 183 183 ... ... @@ -184,48 +184,27 @@ 184 184 [[image:image-20220709150546-2.png]] 185 185 186 186 187 -=== 2.2. 2Test Requirement ===170 +=== 2.2.1 Test Requirement === 188 188 189 189 190 -((( 191 191 To use N95S31B in your city, make sure meet below requirements: 192 -))) 193 193 194 -* ((( 195 -Your local operator has already distributed a NB-IoT Network there. 196 -))) 197 -* ((( 198 -The local NB-IoT network used the band that N95S31B supports. 199 -))) 200 -* ((( 201 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 202 -))) 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. 203 203 204 - (((179 + 205 205 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 206 -))) 207 207 208 -((( 209 209 N95S31B supports different communication protocol such as : 210 -))) 211 211 212 212 ((( 213 -* ((( 214 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 215 -))) 216 -* ((( 217 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 218 -))) 219 -* ((( 220 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 221 -))) 222 -* ((( 223 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 224 -))) 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(%%)) 225 225 226 -((( 227 227 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. 228 -))) 229 229 230 230 231 231 ))) ... ... @@ -233,9 +233,9 @@ 233 233 [[image:1657350625843-586.png]] 234 234 235 235 198 + 236 236 === 2.2.3 Insert SIM card === 237 237 238 - 239 239 ((( 240 240 Insert the NB-IoT Card get from your provider. 241 241 ))) ... ... @@ -248,29 +248,26 @@ 248 248 [[image:1657351240556-536.png]] 249 249 250 250 213 + 251 251 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 252 252 253 - 254 254 ((( 255 255 ((( 256 256 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. 257 - 258 - 259 259 ))) 260 260 ))) 261 261 262 262 [[image:1657351312545-300.png]] 263 263 224 +**Connection:** 264 264 265 -(% style="color: blue" %)**Connection:**226 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 266 266 267 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**228 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 268 268 269 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**230 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 270 270 271 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 272 272 273 - 274 274 In the PC, use below serial tool settings: 275 275 276 276 * Baud: (% style="color:green" %)**9600** ... ... @@ -285,18 +285,17 @@ 285 285 286 286 [[image:1657329814315-101.png]] 287 287 288 - 289 289 ((( 290 -(% 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/]] 291 291 ))) 292 292 293 293 252 + 294 294 === 2.2.5 Use CoAP protocol to uplink data === 295 295 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/]] 296 296 297 -(% 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/]]** 298 298 299 - 300 300 ((( 301 301 **Use below commands:** 302 302 ))) ... ... @@ -305,10 +305,10 @@ 305 305 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 306 306 ))) 307 307 * ((( 308 -(% 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 309 309 ))) 310 310 * ((( 311 -(% 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 312 312 ))) 313 313 314 314 ((( ... ... @@ -327,6 +327,7 @@ 327 327 [[image:1657352185396-303.png]] 328 328 329 329 288 + 330 330 === 2.2.6 Use UDP protocol to uplink data(Default protocol) === 331 331 332 332 ... ... @@ -334,57 +334,50 @@ 334 334 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 335 335 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 336 336 337 -[[image:16573 52391268-297.png]]296 +[[image:1657330501006-241.png]] 338 338 339 339 340 -[[image:16573 52403317-397.png]]299 +[[image:1657330533775-472.png]] 341 341 342 342 343 -=== 2.2.7 Use MQTT protocol to uplink data === 344 344 303 +=== 2.2.6 Use MQTT protocol to uplink data === 345 345 346 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 347 347 348 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 349 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 350 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 351 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 352 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 353 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527354 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)306 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 307 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 308 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 309 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 310 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 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 355 355 356 -[[image:1657 352634421-276.png]]314 +[[image:1657249978444-674.png]] 357 357 358 358 359 -[[image:16573 52645687-385.png]]317 +[[image:1657330723006-866.png]] 360 360 361 361 362 362 ((( 363 -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. 364 364 ))) 365 365 366 366 367 -((( 368 -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. 369 -))) 370 370 326 +=== 2.2.7 Use TCP protocol to uplink data === 371 371 372 -=== 2.2.8 Use TCP protocol to uplink data === 373 373 374 - 375 -This feature is supported since firmware version v110 376 - 377 377 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 378 378 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 379 379 380 -[[image: 1657352898400-901.png]]332 +[[image:image-20220709093918-1.png]] 381 381 382 382 383 -[[image: 1657352914475-252.png]]335 +[[image:image-20220709093918-2.png]] 384 384 385 385 386 -=== 2.2.9 Change Update Interval === 387 387 339 +=== 2.2.8 Change Update Interval === 388 388 389 389 User can use below command to change the (% style="color:green" %)**uplink interval**. 390 390 ... ... @@ -391,244 +391,164 @@ 391 391 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 392 392 393 393 ((( 394 - 346 +(% style="color:red" %)**NOTE:** 395 395 ))) 396 396 397 397 ((( 398 -(% 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. 399 399 ))) 400 400 401 -((( 402 -(% 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).** 403 -))) 404 404 405 405 406 406 == 2.3 Uplink Payload == 407 407 357 +In this mode, uplink payload includes in total 14 bytes 408 408 409 -((( 410 -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. 411 -))) 412 412 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"]] 413 413 414 414 ((( 415 - 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. 416 416 ))) 417 417 418 -((( 419 - (% 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. 420 -))) 421 421 371 +[[image:1657331036973-987.png]] 422 422 423 423 ((( 424 -The uplink payloadsare composedinASCIIString.Forxample:374 +The payload is ASCII string, representative same HEX: 425 425 ))) 426 426 427 427 ((( 428 -0 a cd00ed0acc0ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:378 +0x72403155615900640c6c19029200 where: 429 429 ))) 430 430 431 -((( 432 - 0x 0acd 00ed0acc0000ef 02d21d Total12 bytes381 +* ((( 382 +Device ID: 0x724031556159 = 724031556159 433 433 ))) 434 - 435 - 436 -((( 437 -(% style="color:red" %)**NOTE:** 384 +* ((( 385 +Version: 0x0064=100=1.0.0 438 438 ))) 439 439 440 -(% style="color:red" %) 441 -1. ((( 442 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 388 +* ((( 389 +BAT: 0x0c6c = 3180 mV = 3.180V 443 443 ))) 444 -1. ((( 445 -**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 446 446 447 447 401 + 448 448 449 449 ))) 450 450 451 -== =2.3.1PayloadAnalyze ===405 +== 2.4 Payload Explanation and Sensor Interface == 452 452 453 -==== 2.3.1.1 Before Firmware v1.2 ==== 454 454 408 +=== 2.4.1 Device ID === 455 455 456 -N95S31B uplink payload includes in total 21 bytes 457 - 458 - 459 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 460 -|=(% style="width: 50px;" %)**Size(bytes)**|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 65px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**2** 461 -|(% 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" %)((( 462 462 ((( 463 - Reserve/Same asNBSN95CFGMOD=1411 +By default, the Device ID equal to the last 6 bytes of IMEI. 464 464 ))) 465 465 466 466 ((( 467 - Nofunctionhere.415 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 468 468 ))) 469 -)))|(% style="width:102px" %)((( 470 -((( 471 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 472 -))) 473 473 474 474 ((( 475 - By SHT31419 +**Example:** 476 476 ))) 477 -)))|(% style="width:81px" %)((( 478 -((( 479 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 480 -))) 481 481 482 482 ((( 483 - By SHT31423 +AT+DEUI=A84041F15612 484 484 ))) 485 -))) 486 486 487 487 ((( 488 - 489 - 490 -((( 491 -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. 492 492 ))) 493 -))) 494 494 495 495 496 -[[image:1657354294009-643.png]] 497 497 432 +=== 2.4.2 Version Info === 498 498 499 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 434 +((( 435 +Specify the software version: 0x64=100, means firmware version 1.00. 436 +))) 500 500 501 -**where:** 438 +((( 439 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 440 +))) 502 502 503 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 504 504 505 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 506 506 507 - *(%style="color:#037691"%)**BAT:**(%%) 0x0ccd=3277 mV=3.277V444 +=== 2.4.3 Battery Info === 508 508 509 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 510 - 511 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 512 - 513 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 514 - 515 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 516 - 517 -* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 518 - 519 519 ((( 520 - 447 +Ex1: 0x0B45 = 2885mV 448 +))) 521 521 522 - 523 - 450 +((( 451 +Ex2: 0x0B49 = 2889mV 524 524 ))) 525 525 526 -==== 2.3.1.2 Since Firmware v1.2 ==== 527 527 528 528 529 - Inthismode, uplink payloadincludes 91 bytes inotalby default.456 +=== 2.4.4 Signal Strength === 530 530 531 -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. 532 - 533 - 534 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 535 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:30px" %)**1**|(% style="width:20px" %)**1**|(% style="width:55px" %)**2**|(% style="width:35px" %)**1**|(% style="width:20px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:30px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:35px" %)**4** 536 -|=(% 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 ..... 537 - 538 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 539 - 540 - 541 -[[image:image-20220908154949-1.png]] 542 - 543 - 544 -The payload is ASCII string, representative same HEX: 545 - 546 -**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__ ** 547 - 548 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 549 - 550 -**where:** 551 - 552 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 553 - 554 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 555 - 556 -* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 557 - 558 -* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 559 - 560 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 561 - 562 -* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 563 - 564 -* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 565 - 566 -* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 567 - 568 -* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 569 - 570 -* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 571 - 572 -* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 573 - 574 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 575 - 576 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 577 - 578 - 579 -=== 2.3.2 Device ID === 580 - 581 - 582 582 ((( 583 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.459 +NB-IoT Network signal Strength. 584 584 ))) 585 585 586 586 ((( 587 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 463 +**Ex1: 0x1d = 29** 464 +))) 588 588 589 - 466 +((( 467 +(% style="color:blue" %)**0**(%%) -113dBm or less 590 590 ))) 591 591 592 592 ((( 593 -(% style="color:blue" %)** Example:**471 +(% style="color:blue" %)**1**(%%) -111dBm 594 594 ))) 595 595 596 596 ((( 597 - AT+DEUI=A84041F15612475 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 598 598 ))) 599 599 600 600 ((( 601 -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 +))) 602 602 603 - 482 +((( 483 +(% style="color:blue" %)**99** (%%) Not known or not detectable 604 604 ))) 605 605 606 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 607 607 608 608 609 - Bydefault,theDeviceID equal to the last 15 bits of IMEI.488 +=== 2.4.5 Distance === 610 610 611 - Usercan use**(%style="color:blue"%)AT+DEUI(%%)**tosetDeviceID490 +Get the distance. Flat object range 280mm - 7500mm. 612 612 613 - 614 -(% style="color:blue" %)**Example:** 615 - 616 -AT+DEUI=868411056754138 617 - 618 - 619 -=== 2.3.3 Version Info === 620 - 621 - 622 622 ((( 623 - 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 624 624 ))) 625 625 626 626 ((( 627 -Higher byte: Specify hardware version: always 0x00 for N95S31B 497 +((( 498 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 628 628 ))) 500 +))) 629 629 630 630 ((( 631 - Lowerbyte: Specify the software version: 0x6E=110, means firmware version 110503 + 632 632 ))) 633 633 634 634 ((( ... ... @@ -635,81 +635,65 @@ 635 635 636 636 ))) 637 637 510 +=== 2.4.6 Digital Interrupt === 511 + 638 638 ((( 639 - 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. 640 640 ))) 641 641 642 642 ((( 643 - 517 +The command is: 644 644 ))) 645 645 646 -=== 2.3.4 Battery Info === 647 - 648 - 649 649 ((( 650 - 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]])**.** 651 651 ))) 652 652 524 + 653 653 ((( 654 - 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. 655 655 ))) 656 656 657 657 658 -=== 2.3.5 Signal Strength === 659 - 660 - 661 661 ((( 662 - NB-IoT Network signalStrength.531 +Example: 663 663 ))) 664 664 665 665 ((( 666 - **Ex1:0x1d=29**535 +0x(00): Normal uplink packet. 667 667 ))) 668 668 669 669 ((( 670 -( %style="color:blue"%)**0**(%%) -113dBm orless539 +0x(01): Interrupt Uplink Packet. 671 671 ))) 672 672 542 + 543 + 544 +=== 2.4.7 +5V Output === 545 + 673 673 ((( 674 - (%style="color:blue"%)**1**(%%)-111dBm547 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 675 675 ))) 676 676 550 + 677 677 ((( 678 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm552 +The 5V output time can be controlled by AT Command. 679 679 ))) 680 680 681 681 ((( 682 -(% style="color:blue" %)** 31**(%%) -51dBm or greater556 +(% style="color:blue" %)**AT+5VT=1000** 683 683 ))) 684 684 685 685 ((( 686 - (%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. 687 687 ))) 688 688 689 689 690 -=== 2.3.6 Temperature & Humidity === 691 691 565 +== 2.5 Downlink Payload == 692 692 693 - Thedevice will beabletoget theSHT31temperature and humiditydatanowandupload toIoT Server.567 +By default, NDDS75 prints the downlink payload to console port. 694 694 695 -[[image:image-20220709161741-3.png]] 696 - 697 - 698 -Convert the read byte to decimal and divide it by ten. 699 - 700 - 701 -**Example:** 702 - 703 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 704 - 705 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 706 - 707 - 708 -== 2.4 Downlink Payload == 709 - 710 - 711 -By default, N95S31B prints the downlink payload to console port. 712 - 713 713 [[image:image-20220709100028-1.png]] 714 714 715 715 ... ... @@ -746,7 +746,7 @@ 746 746 ))) 747 747 748 748 ((( 749 -If payload = 0x04FF, it will reset the 95S31B605 +If payload = 0x04FF, it will reset the NDDS75 750 750 ))) 751 751 752 752 ... ... @@ -757,99 +757,144 @@ 757 757 ))) 758 758 759 759 760 -== 2.5 Humidity and Temperature alarm function == 761 761 617 +== 2.6 LED Indicator == 762 762 763 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 764 764 620 +The NDDS75 has an internal LED which is to show the status of different state. 765 765 766 -(% style="color:#037691" %)**AT+ SHHUM=min,max** 767 767 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. 768 768 769 -² When min=0, and max≠0, Alarm higher than max 628 +((( 629 + 630 +))) 770 770 771 -² When min≠0, and max=0, Alarm lower than min 772 772 773 -² When min≠0 and max≠0, Alarm higher than max or lower than min 774 774 634 +== 2.7 Firmware Change Log == 775 775 776 - (% style="color:blue" %)**Example:** 777 777 778 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 637 +((( 638 +Download URL & Firmware Change log 639 +))) 779 779 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 +))) 780 780 781 -(% style="color:#037691" %)**AT+ SHTEMP=min,max** 782 782 783 -² When min=0, and max≠0, Alarm higher than max 646 +((( 647 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 648 +))) 784 784 785 -² When min≠0, and max=0, Alarm lower than min 786 786 787 -² When min≠0 and max≠0, Alarm higher than max or lower than min 788 788 652 +== 2.8 Battery Analysis == 789 789 790 - **~(%style="color:blue"%)Example:(%%)**654 +=== 2.8.1 Battery Type === 791 791 792 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 793 793 657 +((( 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. 659 +))) 794 794 795 -== 2.6 Set the number of data to be uploaded and the recording time == 661 +((( 662 +The battery is designed to last for several years depends on the actually use environment and update interval. 663 +))) 796 796 665 +((( 666 +The battery related documents as below: 667 +))) 797 797 798 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 669 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 670 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 671 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 799 799 800 -* (% 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) 801 -* (% 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. 673 +((( 674 +[[image:image-20220709101450-2.png]] 675 +))) 802 802 803 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 804 804 805 -[[image:image-20221009001045-1.png||height="726" width="1009"]] 806 806 679 +=== 2.8.2 Power consumption Analyze === 807 807 808 -== 2.7 Read or Clear cached data == 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 +))) 809 809 810 810 811 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 686 +((( 687 +Instruction to use as below: 688 +))) 812 812 813 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 814 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 690 +((( 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/]] 692 +))) 815 815 816 -[[image:image-20220908163102-2.png]] 817 817 695 +((( 696 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 697 +))) 818 818 819 -= 2.8 Battery & Power Consumption = 699 +* ((( 700 +Product Model 701 +))) 702 +* ((( 703 +Uplink Interval 704 +))) 705 +* ((( 706 +Working Mode 707 +))) 820 820 709 +((( 710 +And the Life expectation in difference case will be shown on the right. 711 +))) 821 821 822 - N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about thebatteryinfoand how to replace.713 +[[image:image-20220709110451-3.png]] 823 823 824 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 825 825 826 826 827 - 717 +=== 2.8.3 Battery Note === 828 828 829 -= 3. Access NB-IoT Module = 719 +((( 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. 721 +))) 830 830 831 831 724 + 725 +=== 2.8.4 Replace the battery === 726 + 832 832 ((( 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). 729 +))) 730 + 731 + 732 + 733 += 3. Access NB-IoT Module = 734 + 735 +((( 833 833 Users can directly access the AT command set of the NB-IoT module. 834 834 ))) 835 835 836 836 ((( 837 837 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/]] 838 - 839 - 840 840 ))) 841 841 842 842 [[image:1657333200519-600.png]] 843 843 844 844 746 + 845 845 = 4. Using the AT Commands = 846 846 847 847 == 4.1 Access AT Commands == 848 848 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/]] 849 849 850 -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]] 851 851 852 - 853 853 AT+<CMD>? : Help on <CMD> 854 854 855 855 AT+<CMD> : Run <CMD> ... ... @@ -889,24 +889,7 @@ 889 889 890 890 AT+SERVADDR : Server Address 891 891 892 -AT+TR : Get or Set record time 893 893 894 -AT+APN : Get or set the APN 895 - 896 -AT+FBAND : Get or Set whether to automatically modify the frequency band 897 - 898 -AT+DNSCFG : Get or Set DNS Server 899 - 900 -AT+GETSENSORVALUE : Returns the current sensor measurement 901 - 902 -AT+NOUD : Get or Set the number of data to be uploaded 903 - 904 -AT+CDP : Read or Clear cached data 905 - 906 -AT+SHTEMP: Get or Set alarm of temp 907 - 908 -AT+SHHUM: Get or Set alarm of moisture 909 - 910 910 (% style="color:#037691" %)**COAP Management** 911 911 912 912 AT+URI : Resource parameters ... ... @@ -937,6 +937,7 @@ 937 937 AT+PWORD : Serial Access Password 938 938 939 939 824 + 940 940 = 5. FAQ = 941 941 942 942 == 5.1 How to Upgrade Firmware == ... ... @@ -951,14 +951,11 @@ 951 951 ))) 952 952 953 953 ((( 954 - 955 - 956 -((( 957 -(% 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. 958 958 ))) 959 -))) 960 960 961 961 843 + 962 962 = 6. Trouble Shooting = 963 963 964 964 == 6.1 Connection problem when uploading firmware == ... ... @@ -973,9 +973,9 @@ 973 973 974 974 ))) 975 975 858 + 976 976 == 6.2 AT Command input doesn't work == 977 977 978 - 979 979 ((( 980 980 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. 981 981 ... ... @@ -982,12 +982,18 @@ 982 982 983 983 ))) 984 984 867 + 985 985 = 7. Order Info = 986 986 987 987 988 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**871 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 989 989 990 990 874 +(% class="wikigeneratedid" %) 875 +((( 876 + 877 +))) 878 + 991 991 = 8. Packing Info = 992 992 993 993 ((( ... ... @@ -995,7 +995,7 @@ 995 995 996 996 (% style="color:#037691" %)**Package Includes**: 997 997 998 -* N 95S31BNB-IoTTemperatureandHumiditySensor886 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 999 999 * External antenna x 1 1000 1000 ))) 1001 1001 ... ... @@ -1004,24 +1004,21 @@ 1004 1004 1005 1005 (% style="color:#037691" %)**Dimension and weight**: 1006 1006 895 + 1007 1007 * Device Size: 13.0 x 5 x 4.5 cm 1008 1008 * Device Weight: 150g 1009 -* Package Size / pcs : 1 4.0x8x 5 cm1010 -* Weight / pcs : 180g898 +* Package Size / pcs : 15 x 12x 5.5 cm 899 +* Weight / pcs : 220g 1011 1011 ))) 1012 1012 1013 1013 ((( 1014 1014 1015 1015 905 + 1016 1016 1017 1017 ))) 1018 1018 1019 1019 = 9. Support = 1020 1020 1021 - 1022 1022 * 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. 1023 1023 * 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]] 1024 - 1025 - 1026 - 1027 -
- 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