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, 8 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,6 +9,7 @@ 9 9 10 10 **Table of Contents:** 11 11 12 +{{toc/}} 12 12 13 13 14 14 ... ... @@ -16,21 +16,35 @@ 16 16 17 17 = 1. Introduction = 18 18 20 + 19 19 == 1.1 What is N95S31B NB-IoT Sensor Node == 20 20 21 21 ((( 22 22 23 23 26 +((( 24 24 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 +))) 25 25 30 +((( 26 26 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 +))) 27 27 34 +((( 28 28 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 +))) 29 29 38 +((( 30 30 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 +))) 31 31 42 +((( 43 + 44 +))) 32 32 46 +((( 33 33 ~* make sure you have NB-IoT coverage locally. 48 +))) 34 34 35 35 36 36 ))) ... ... @@ -54,7 +54,6 @@ 54 54 * 8500mAh Battery for long term use 55 55 56 56 57 - 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -74,7 +74,6 @@ 74 74 75 75 (% style="color:#037691" %)**Battery:** 76 76 77 - 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -82,9 +82,9 @@ 82 82 * Max boost current: 2A, 1 second 83 83 84 84 85 - 86 86 == 1.4 Applications == 87 87 100 + 88 88 * Smart Buildings & Home Automation 89 89 * Logistics and Supply Chain Management 90 90 * Smart Metering ... ... @@ -96,15 +96,20 @@ 96 96 97 97 98 98 99 -== 1.5 Pin Definitions == 100 100 113 +== 1.5 Pin Definitions & Switch == 114 + 115 + 101 101 N95S31B use the mother board from NBSN95 which as below. 102 102 118 + 103 103 [[image:image-20220709144723-1.png]] 104 104 105 105 122 + 106 106 === 1.5.1 Jumper JP2 === 107 107 125 + 108 108 Power on Device when put this jumper. 109 109 110 110 ... ... @@ -111,14 +111,20 @@ 111 111 112 112 === 1.5.2 BOOT MODE / SW1 === 113 113 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. 115 115 116 -2) Flash: work mode, device starts to work and send out console output for further debug 133 +((( 134 +**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. 135 +))) 117 117 137 +((( 138 +**2) Flash:** work mode, device starts to work and send out console output for further debug 139 +))) 118 118 119 119 142 + 120 120 === 1.5.3 Reset Button === 121 121 145 + 122 122 Press to reboot the device. 123 123 124 124 ... ... @@ -125,16 +125,18 @@ 125 125 126 126 === 1.5.4 LED === 127 127 152 + 128 128 It will flash: 129 129 130 -1. When boot the device in flash mode 131 -1. Send an uplink packet 155 +1. When boot the device in flash mode 132 132 157 +2. Send an uplink packet 133 133 134 134 135 135 136 136 = 2. Use N95S31B to communicate with IoT Server = 137 137 163 + 138 138 == 2.1 How it works == 139 139 140 140 ... ... @@ -151,7 +151,7 @@ 151 151 152 152 ))) 153 153 154 -[[image:1657 350248151-650.png]]180 +[[image:1657520100595-569.png]] 155 155 156 156 ((( 157 157 ... ... @@ -167,27 +167,49 @@ 167 167 [[image:image-20220709150546-2.png]] 168 168 169 169 196 + 170 170 === 2.2.1 Test Requirement === 171 171 172 172 200 +((( 173 173 To use N95S31B in your city, make sure meet below requirements: 202 +))) 174 174 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. 204 +* ((( 205 +Your local operator has already distributed a NB-IoT Network there. 206 +))) 207 +* ((( 208 +The local NB-IoT network used the band that N95S31B supports. 209 +))) 210 +* ((( 211 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 212 +))) 178 178 179 - 214 +((( 180 180 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 216 +))) 181 181 218 +((( 182 182 N95S31B supports different communication protocol such as : 220 +))) 183 183 184 184 ((( 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(%%)) 223 +* ((( 224 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 225 +))) 226 +* ((( 227 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 228 +))) 229 +* ((( 230 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 231 +))) 232 +* ((( 233 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 234 +))) 189 189 236 +((( 190 190 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. 238 +))) 191 191 192 192 193 193 ))) ... ... @@ -198,6 +198,7 @@ 198 198 199 199 === 2.2.3 Insert SIM card === 200 200 249 + 201 201 ((( 202 202 Insert the NB-IoT Card get from your provider. 203 203 ))) ... ... @@ -213,23 +213,27 @@ 213 213 214 214 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 215 215 265 + 216 216 ((( 217 217 ((( 218 218 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. 269 + 270 + 219 219 ))) 220 220 ))) 221 221 222 222 [[image:1657351312545-300.png]] 223 223 224 -**Connection:** 225 225 226 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND277 +**(% style="color:blue" %)Connection:** 227 227 228 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD279 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 229 229 230 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD281 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 231 231 283 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 232 232 285 + 233 233 In the PC, use below serial tool settings: 234 234 235 235 * Baud: (% style="color:green" %)**9600** ... ... @@ -244,8 +244,9 @@ 244 244 245 245 [[image:1657329814315-101.png]] 246 246 300 + 247 247 ((( 248 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]302 +(% 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]]** 249 249 ))) 250 250 251 251 ... ... @@ -252,9 +252,10 @@ 252 252 253 253 === 2.2.5 Use CoAP protocol to uplink data === 254 254 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/]] 256 256 310 +(% 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/]]** 257 257 312 + 258 258 ((( 259 259 **Use below commands:** 260 260 ))) ... ... @@ -263,10 +263,10 @@ 263 263 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 264 264 ))) 265 265 * ((( 266 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 321 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 267 267 ))) 268 268 * ((( 269 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 324 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 270 270 ))) 271 271 272 272 ((( ... ... @@ -302,21 +302,23 @@ 302 302 303 303 === 2.2.7 Use MQTT protocol to uplink data === 304 304 305 -N95S31B supports only plain MQTT now it doesn’t support TLS and other related encryption. 306 306 307 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 308 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 309 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 310 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 311 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 312 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 313 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 361 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 314 314 363 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 364 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 365 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 366 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 367 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 368 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ Set the sending topic of MQTT 369 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ Set the subscription topic of MQTT 370 + 315 315 [[image:1657352634421-276.png]] 316 316 317 317 318 318 [[image:1657352645687-385.png]] 319 319 376 + 320 320 ((( 321 321 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. 322 322 ))) ... ... @@ -328,79 +328,82 @@ 328 328 329 329 330 330 331 -=== 2.2. 7388 +=== 2.2.8 Use TCP protocol to uplink data === 332 332 333 333 391 +This feature is supported since firmware version v110 392 + 334 334 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 335 335 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 336 336 337 -[[image: image-20220709093918-1.png]]396 +[[image:1657352898400-901.png]] 338 338 339 339 340 -[[image: image-20220709093918-2.png]]399 +[[image:1657352914475-252.png]] 341 341 342 342 343 343 344 -=== 2.2. 8403 +=== 2.2.9 Change Update Interval === 345 345 405 + 346 346 User can use below command to change the (% style="color:green" %)**uplink interval**. 347 347 348 348 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 349 349 350 350 ((( 351 - (%style="color:red" %)**NOTE:**411 + 352 352 ))) 353 353 354 354 ((( 355 -(% style="color:red" %) 1.By default, thedevicewillsend an uplinkmessageevery1hour.415 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 356 356 ))) 357 357 418 +((( 419 +(% 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).** 420 +))) 358 358 359 359 423 + 360 360 == 2.3 Uplink Payload == 361 361 362 -In this mode, uplink payload includes in total 14 bytes 363 363 427 +((( 428 +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. 429 +))) 364 364 365 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 366 -|=(% style="width: 60px;" %)((( 367 -**Size(bytes)** 368 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 369 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]] 370 370 371 371 ((( 372 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.433 +For example: 373 373 ))) 374 374 436 +((( 437 + (% 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. 438 +))) 375 375 376 -[[image:1657331036973-987.png]] 377 377 378 378 ((( 379 -The payload is ASCIIstring,representative sameHEX:442 +The uplink payloads are composed in ASCII String. For example: 380 380 ))) 381 381 382 382 ((( 383 -0 x72403155615900640c6c19029200where:446 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 384 384 ))) 385 385 386 - *(((387 - DeviceID:0x724031556159=724031556159449 +((( 450 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 388 388 ))) 389 -* ((( 390 -Version: 0x0064=100=1.0.0 452 + 453 + 454 +((( 455 +(% style="color:red" %)**NOTE:** 391 391 ))) 392 392 393 -* ((( 394 -BAT: 0x0c6c = 3180 mV = 3.180V 458 +(% style="color:red" %) 459 +1. ((( 460 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 395 395 ))) 396 -* ((( 397 -Signal: 0x19 = 25 398 -))) 399 -* ((( 400 -Distance: 0x0292= 658 mm 401 -))) 402 -* ((( 403 -Interrupt: 0x00 = 0 462 +1. ((( 463 +**By default, the device will send an uplink message every 1 hour.** 404 404 405 405 406 406 ... ... @@ -407,105 +407,191 @@ 407 407 408 408 ))) 409 409 410 -== 2. 4PayloadExplanation and SensorInterface==470 +=== 2.3.1 Payload Analyze === 411 411 412 412 413 -=== 2. 4.1DeviceID===473 +==== 2.3.1.1 Before Firmware v1.2 ==== 414 414 475 + 476 +N95S31B uplink payload includes in total 21 bytes 477 + 478 + 479 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 480 +|=(% style="width: 50px;" %)((( 481 +**Size(bytes)** 482 +)))|=(% style="width: 40px;" %)**6**|=(% style="width: 20px;" %)2|=(% style="width: 20px;" %)**2**|=(% style="width: 60px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 100px;" %)5|=(% style="width: 102px;" %)**2**|=(% style="width: 81px;" %)**2** 483 +|(% 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" %)((( 415 415 ((( 416 - By default, theDeviceID equal to thelast6bytes of IMEI.485 +Reserve/ Same as NBSN95 CFGMOD=1 417 417 ))) 418 418 419 419 ((( 420 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID489 +No function here. 421 421 ))) 491 +)))|(% style="width:102px" %)((( 492 +((( 493 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 494 +))) 422 422 423 423 ((( 424 - **Example:**497 +By SHT31 425 425 ))) 499 +)))|(% style="width:81px" %)((( 500 +((( 501 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 502 +))) 426 426 427 427 ((( 428 - AT+DEUI=A84041F15612505 +By SHT31 429 429 ))) 507 +))) 430 430 431 431 ((( 432 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 510 + 511 + 512 +((( 513 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 433 433 ))) 515 +))) 434 434 435 435 518 +[[image:1657354294009-643.png]] 436 436 437 -=== 2.4.2 Version Info === 438 438 439 -((( 440 -Specify the software version: 0x64=100, means firmware version 1.00. 441 -))) 521 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 442 442 443 -((( 444 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 445 -))) 523 +**where:** 446 446 525 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 447 447 527 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 448 448 449 - ===2.4.3BatteryInfo===529 +* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 450 450 451 -((( 452 -Ex1: 0x0B45 = 2885mV 453 -))) 531 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 454 454 455 -((( 456 -Ex2: 0x0B49 = 2889mV 457 -))) 533 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 458 458 535 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 459 459 537 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 460 460 461 - ===2.4.4SignalStrength===539 +* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 462 462 463 463 ((( 464 -NB-IoT Network signal Strength. 465 -))) 542 + 466 466 467 - (((468 - **Ex1:0x1d = 29**544 + 545 + 469 469 ))) 470 470 548 +==== 2.3.1.2 Since Firmware v1.2 ==== 549 + 550 + 551 +In this mode, uplink payload includes 91 bytes in total by default. 552 + 553 +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. 554 + 555 + 556 +(% border="2" style="background-color:#ffffcc; color:green; width:520px" %) 557 +|(% style="width:50px" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**2**|(% style="width:50px" %)**1**|(% style="width:30px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:50px" %)**4** 558 +|(% 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 ..... 559 + 560 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 561 + 562 + 563 +[[image:image-20220908154949-1.png]] 564 + 565 + 566 +The payload is ASCII string, representative same HEX: 567 + 568 +**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__ ** 569 + 570 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 571 + 572 +**where:** 573 + 574 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 575 + 576 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 577 + 578 +* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 579 + 580 +* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 581 + 582 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 583 + 584 +* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 585 + 586 +* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 587 + 588 +* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 589 + 590 +* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 591 + 592 +* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 593 + 594 +* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 595 + 596 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 597 + 598 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 599 + 600 + 601 +=== 2.3.2 Device ID === 602 + 603 + 471 471 ((( 472 - (% style="color:blue"%)**0**(%%)-113dBmorless605 +By default, the Device ID equal to the last 6 bytes of IMEI. 473 473 ))) 474 474 475 475 ((( 476 -(% style="color:blue" %)**1**(%%) -111dBm 609 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 610 + 611 + 477 477 ))) 478 478 479 479 ((( 480 -(% style="color:blue" %)** 2...30**(%%) -109dBm... -53dBm615 +(% style="color:blue" %)**Example:** 481 481 ))) 482 482 483 483 ((( 484 - (% style="color:blue" %)**31** (%%) -51dBm or greater619 +AT+DEUI=A84041F15612 485 485 ))) 486 486 487 487 ((( 488 -(% style="color:blue" %)**99** (%%) Not known or not detectable 623 +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. 624 + 625 + 489 489 ))) 490 490 628 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 491 491 492 492 493 - ===2.4.5Distance===631 +By default, the Device ID equal to the last 15 bits of IMEI. 494 494 495 - Getthedistance.Flatbjectrange280mm - 7500mm.633 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 496 496 635 + 636 +(% style="color:blue" %)**Example:** 637 + 638 +AT+DEUI=868411056754138 639 + 640 + 641 + 642 +=== 2.3.3 Version Info === 643 + 644 + 497 497 ((( 498 - Forexample,if the datayou getfrom theregisteris **__0x0B 0x05__**, the distancebetweenthesensorand the measuredobject is646 +These bytes include the hardware and software version. 499 499 ))) 500 500 501 501 ((( 502 -((( 503 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 650 +Higher byte: Specify hardware version: always 0x00 for N95S31B 504 504 ))) 505 -))) 506 506 507 507 ((( 508 - 654 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 509 509 ))) 510 510 511 511 ((( ... ... @@ -512,65 +512,85 @@ 512 512 513 513 ))) 514 514 515 -=== 2.4.6 Digital Interrupt === 516 - 517 517 ((( 518 - Digital Interruptrefers topin (% style="color:blue"%)**GPIO_EXTI**(%%),andtherearedifferent triggermethods. When thereisa trigger, theNDDS75 will send a packetto theserver.662 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 519 519 ))) 520 520 521 521 ((( 522 - Thecommand is:666 + 523 523 ))) 524 524 669 + 670 +=== 2.3.4 Battery Info === 671 + 672 + 525 525 ((( 526 - (% 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]])**.**674 +Ex1: 0x0B45 = 2885mV 527 527 ))) 528 528 529 - 530 530 ((( 531 - Thelowerfourbits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.678 +Ex2: 0x0B49 = 2889mV 532 532 ))) 533 533 534 534 682 + 683 +=== 2.3.5 Signal Strength === 684 + 685 + 535 535 ((( 536 - Example:687 +NB-IoT Network signal Strength. 537 537 ))) 538 538 539 539 ((( 540 - 0x(00):Normaluplinkpacket.691 +**Ex1: 0x1d = 29** 541 541 ))) 542 542 543 543 ((( 544 - 0x(01):InterruptUplinkPacket.695 +(% style="color:blue" %)**0**(%%) -113dBm or less 545 545 ))) 546 546 547 - 548 - 549 -=== 2.4.7 +5V Output === 550 - 551 551 ((( 552 - NDDS75willenable +5Voutputbeforeallsamplinganddisablethe+5vafterall sampling.699 +(% style="color:blue" %)**1**(%%) -111dBm 553 553 ))) 554 554 555 - 556 556 ((( 557 - The5V output timean be controlledbyAT Command.703 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 558 558 ))) 559 559 560 560 ((( 561 -(% style="color:blue" %)** AT+5VT=1000**707 +(% style="color:blue" %)**31** (%%) -51dBm or greater 562 562 ))) 563 563 564 564 ((( 565 - Meansset5V valid timetohave 1000ms. Sothereal5V outputwillactuallyhave1000ms+samplingtime for othersensors.711 +(% style="color:blue" %)**99** (%%) Not known or not detectable 566 566 ))) 567 567 568 568 569 569 570 -== 2. 5Downlink Payload ==716 +=== 2.3.6 Temperature & Humidity === 571 571 572 -By default, NDDS75 prints the downlink payload to console port. 573 573 719 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 720 + 721 +[[image:image-20220709161741-3.png]] 722 + 723 + 724 +Convert the read byte to decimal and divide it by ten. 725 + 726 + 727 +**Example:** 728 + 729 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 730 + 731 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 732 + 733 + 734 + 735 +== 2.4 Downlink Payload == 736 + 737 + 738 +By default, N95S31B prints the downlink payload to console port. 739 + 574 574 [[image:image-20220709100028-1.png]] 575 575 576 576 ... ... @@ -607,7 +607,7 @@ 607 607 ))) 608 608 609 609 ((( 610 -If payload = 0x04FF, it will reset the DDS75776 +If payload = 0x04FF, it will reset the N95S31B 611 611 ))) 612 612 613 613 ... ... @@ -619,48 +619,76 @@ 619 619 620 620 621 621 622 -== 2. 6LEDIndicator ==788 +== 2.5 Humidity and Temperature alarm function == 623 623 624 624 625 - TheNDDS75hasan internalLED which is toshow thestatusofdifferent state.791 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 626 626 627 627 628 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 629 -* Then the LED will be on for 1 second means device is boot normally. 630 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 631 -* For each uplink probe, LED will be on for 500ms. 794 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 632 632 633 -((( 634 - 635 -))) 636 636 797 +² When min=0, and max≠0, Alarm higher than max 637 637 799 +² When min≠0, and max=0, Alarm lower than min 638 638 639 - ==2.7FirmwareChangeLog==801 +² When min≠0 and max≠0, Alarm higher than max or lower than min 640 640 641 641 642 -((( 643 -Download URL & Firmware Change log 644 -))) 804 + (% style="color:blue" %)**Example:** 645 645 646 -((( 647 -[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]] 648 -))) 806 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 649 649 650 650 651 -((( 652 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 653 -))) 809 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 654 654 811 +² When min=0, and max≠0, Alarm higher than max 655 655 813 +² When min≠0, and max=0, Alarm lower than min 656 656 815 +² When min≠0 and max≠0, Alarm higher than max or lower than min 816 + 817 + 818 +**~ (% style="color:blue" %)Example:(%%)** 819 + 820 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 821 + 822 + 823 + 824 +== 2.6 Set the number of data to be uploaded and the recording time == 825 + 826 + 827 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 828 + 829 +* (% 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) 830 +* (% 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. 831 + 832 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 833 + 834 +[[image:image-20221009001045-1.png||height="726" width="1009"]] 835 + 836 + 837 + 838 +== 2.7 Read or Clear cached data == 839 + 840 + 841 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 842 + 843 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 844 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 845 + 846 +[[image:image-20220908163102-2.png]] 847 + 848 + 849 + 657 657 == 2.8 Battery Analysis == 658 658 852 + 659 659 === 2.8.1 Battery Type === 660 660 661 661 662 662 ((( 663 -The N DDS75 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.857 +The N95S31B 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. 664 664 ))) 665 665 666 666 ((( ... ... @@ -683,54 +683,35 @@ 683 683 684 684 === 2.8.2 Power consumption Analyze === 685 685 686 -((( 687 -Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 688 -))) 689 689 690 - 691 691 ((( 692 -Instruction to use as below:882 +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 to analyze the power consumption in different case. User can use it for design guideline for their project. 693 693 ))) 694 694 695 695 ((( 696 - (%style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]886 + 697 697 ))) 698 698 699 699 700 -((( 701 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 702 -))) 890 +=== 2.8.3 Battery Note === 703 703 704 -* ((( 705 -Product Model 706 -))) 707 -* ((( 708 -Uplink Interval 709 -))) 710 -* ((( 711 -Working Mode 712 -))) 713 713 714 714 ((( 715 - And the Life expectation in difference casewillbe shownon theright.894 +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 uplink data, then the battery life may be decreased. 716 716 ))) 717 717 718 -[[image:image-20220709110451-3.png]] 719 719 720 720 899 +=== 2.8.4 Replace the battery === 721 721 722 -=== 2.8.3 Battery Note === 723 723 724 724 ((( 725 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.903 +You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board. 726 726 ))) 727 727 728 728 729 - 730 -=== 2.8.4 Replace the battery === 731 - 732 732 ((( 733 -The default battery pack of N DDS75 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).908 +The default battery pack of N95S31B 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). 734 734 ))) 735 735 736 736 ... ... @@ -737,6 +737,7 @@ 737 737 738 738 = 3. Access NB-IoT Module = 739 739 915 + 740 740 ((( 741 741 Users can directly access the AT command set of the NB-IoT module. 742 742 ))) ... ... @@ -743,6 +743,8 @@ 743 743 744 744 ((( 745 745 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/]] 922 + 923 + 746 746 ))) 747 747 748 748 [[image:1657333200519-600.png]] ... ... @@ -751,11 +751,13 @@ 751 751 752 752 = 4. Using the AT Commands = 753 753 932 + 754 754 == 4.1 Access AT Commands == 755 755 756 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 757 757 936 +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]] 758 758 938 + 759 759 AT+<CMD>? : Help on <CMD> 760 760 761 761 AT+<CMD> : Run <CMD> ... ... @@ -795,7 +795,24 @@ 795 795 796 796 AT+SERVADDR : Server Address 797 797 978 +AT+TR : Get or Set record time 798 798 980 +AT+APN : Get or set the APN 981 + 982 +AT+FBAND : Get or Set whether to automatically modify the frequency band 983 + 984 +AT+DNSCFG : Get or Set DNS Server 985 + 986 +AT+GETSENSORVALUE : Returns the current sensor measurement 987 + 988 +AT+NOUD : Get or Set the number of data to be uploaded 989 + 990 +AT+CDP : Read or Clear cached data 991 + 992 +AT+SHTEMP: Get or Set alarm of temp 993 + 994 +AT+SHHUM: Get or Set alarm of moisture 995 + 799 799 (% style="color:#037691" %)**COAP Management** 800 800 801 801 AT+URI : Resource parameters ... ... @@ -829,6 +829,7 @@ 829 829 830 830 = 5. FAQ = 831 831 1029 + 832 832 == 5.1 How to Upgrade Firmware == 833 833 834 834 ... ... @@ -841,13 +841,18 @@ 841 841 ))) 842 842 843 843 ((( 844 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 1042 + 1043 + 1044 +((( 1045 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 845 845 ))) 1047 +))) 846 846 847 847 848 848 849 849 = 6. Trouble Shooting = 850 850 1053 + 851 851 == 6.1 Connection problem when uploading firmware == 852 852 853 853 ... ... @@ -863,6 +863,7 @@ 863 863 864 864 == 6.2 AT Command input doesn't work == 865 865 1069 + 866 866 ((( 867 867 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. 868 868 ... ... @@ -873,7 +873,7 @@ 873 873 = 7. Order Info = 874 874 875 875 876 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**1080 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 877 877 878 878 879 879 (% class="wikigeneratedid" %) ... ... @@ -888,7 +888,7 @@ 888 888 889 889 (% style="color:#037691" %)**Package Includes**: 890 890 891 -* NS E01DistanceDetectSensorNode x 11095 +* N95S31B NB-IoT Temperature and Humidity Sensor 892 892 * External antenna x 1 893 893 ))) 894 894 ... ... @@ -897,11 +897,10 @@ 897 897 898 898 (% style="color:#037691" %)**Dimension and weight**: 899 899 900 - 901 901 * Device Size: 13.0 x 5 x 4.5 cm 902 902 * Device Weight: 150g 903 -* Package Size / pcs : 1 5x12x 5.5cm904 -* Weight / pcs : 220g1106 +* Package Size / pcs : 14.0 x 8x 5 cm 1107 +* Weight / pcs : 180g 905 905 ))) 906 906 907 907 ((( ... ... @@ -913,5 +913,6 @@ 913 913 914 914 = 9. Support = 915 915 1119 + 916 916 * 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. 917 917 * 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]]
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 KB - Content
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.2 KB - Content
- image-20220908154949-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +58.5 KB - Content
- image-20220908163102-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.7 KB - Content
- image-20221009001045-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content