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, 4 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 ... ... @@ -19,34 +19,29 @@ 19 19 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 22 - 23 23 ((( 22 + 23 + 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*. 25 -))) 26 26 27 -((( 28 28 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. 29 -))) 30 30 31 -((( 32 32 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 33 -))) 34 34 35 -((( 36 36 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). 37 -))) 38 38 39 - (((32 + 40 40 ~* make sure you have NB-IoT coverage locally. 34 + 35 + 41 41 ))) 42 42 43 - 44 44 [[image:1657348284168-431.png]] 45 45 46 46 41 + 47 47 == 1.2 Features == 48 48 49 - 50 50 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 51 51 * Monitor Temperature & Humidity via SHT31 52 52 * AT Commands to change parameters ... ... @@ -60,6 +60,7 @@ 60 60 61 61 62 62 57 + 63 63 == 1.3 Specification == 64 64 65 65 ... ... @@ -70,15 +70,16 @@ 70 70 71 71 (% style="color:#037691" %)**NB-IoT Spec:** 72 72 73 -* B1 @H-FDD: 2100MHz 74 -* B3 @H-FDD: 1800MHz 75 -* B8 @H-FDD: 900MHz 76 -* B5 @H-FDD: 850MHz 77 -* B20 @H-FDD: 800MHz 78 -* B28 @H-FDD: 700MHz 68 +* - B1 @H-FDD: 2100MHz 69 +* - B3 @H-FDD: 1800MHz 70 +* - B8 @H-FDD: 900MHz 71 +* - B5 @H-FDD: 850MHz 72 +* - B20 @H-FDD: 800MHz 73 +* - B28 @H-FDD: 700MHz 79 79 80 80 (% style="color:#037691" %)**Battery:** 81 81 77 + 82 82 * Li/SOCI2 un-chargeable battery 83 83 * Capacity: 8500mAh 84 84 * Self Discharge: <1% / Year @ 25°C ... ... @@ -87,9 +87,9 @@ 87 87 88 88 89 89 86 + 90 90 == 1.4 Applications == 91 91 92 - 93 93 * Smart Buildings & Home Automation 94 94 * Logistics and Supply Chain Management 95 95 * Smart Metering ... ... @@ -101,49 +101,41 @@ 101 101 102 102 103 103 104 -== 1.5 Pin Definitions & Switch==100 +== 1.5 Pin Definitions == 105 105 106 - 107 107 N95S31B use the mother board from NBSN95 which as below. 108 108 109 - 110 110 [[image:image-20220709144723-1.png]] 111 111 112 112 113 113 === 1.5.1 Jumper JP2 === 114 114 115 - 116 116 Power on Device when put this jumper. 117 117 118 118 112 + 119 119 === 1.5.2 BOOT MODE / SW1 === 120 120 115 +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. 121 121 122 -((( 123 -**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. 124 -))) 117 +2) Flash: work mode, device starts to work and send out console output for further debug 125 125 126 -((( 127 -**2) Flash:** work mode, device starts to work and send out console output for further debug 128 -))) 129 129 130 130 131 131 === 1.5.3 Reset Button === 132 132 133 - 134 134 Press to reboot the device. 135 135 136 136 126 + 137 137 === 1.5.4 LED === 138 138 139 - 140 140 It will flash: 141 141 142 -1. When boot the device in flash mode 131 +1. When boot the device in flash mode 132 +1. Send an uplink packet 143 143 144 -2. Send an uplink packet 145 145 146 - 147 147 = 2. Use N95S31B to communicate with IoT Server = 148 148 149 149 == 2.1 How it works == ... ... @@ -162,14 +162,16 @@ 162 162 163 163 ))) 164 164 165 -[[image:16575 20100595-569.png]]153 +[[image:1657350248151-650.png]] 166 166 167 167 ((( 168 168 169 169 ))) 170 170 159 + 171 171 == 2.2 Configure the N95S31B == 172 172 162 + 173 173 === 2.2.1 Power On N95S31B === 174 174 175 175 ... ... @@ -176,48 +176,26 @@ 176 176 [[image:image-20220709150546-2.png]] 177 177 178 178 179 -=== 2.2. 2Test Requirement ===169 +=== 2.2.1 Test Requirement === 180 180 181 181 182 -((( 183 183 To use N95S31B in your city, make sure meet below requirements: 184 -))) 185 185 186 -* ((( 187 -Your local operator has already distributed a NB-IoT Network there. 188 -))) 189 -* ((( 190 -The local NB-IoT network used the band that N95S31B supports. 191 -))) 192 -* ((( 193 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 194 -))) 174 +* Your local operator has already distributed a NB-IoT Network there. 175 +* The local NB-IoT network used the band that N95S31B supports. 176 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 195 195 196 -((( 197 197 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 198 -))) 199 199 200 -((( 201 201 N95S31B supports different communication protocol such as : 202 -))) 203 203 204 204 ((( 205 -* ((( 206 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 207 -))) 208 -* ((( 209 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 210 -))) 211 -* ((( 212 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 213 -))) 214 -* ((( 215 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 216 -))) 183 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 184 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 185 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 186 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 217 217 218 -((( 219 219 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. 220 -))) 221 221 222 222 223 223 ))) ... ... @@ -225,9 +225,9 @@ 225 225 [[image:1657350625843-586.png]] 226 226 227 227 196 + 228 228 === 2.2.3 Insert SIM card === 229 229 230 - 231 231 ((( 232 232 Insert the NB-IoT Card get from your provider. 233 233 ))) ... ... @@ -240,29 +240,26 @@ 240 240 [[image:1657351240556-536.png]] 241 241 242 242 211 + 243 243 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 244 244 245 - 246 246 ((( 247 247 ((( 248 248 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. 249 - 250 - 251 251 ))) 252 252 ))) 253 253 254 254 [[image:1657351312545-300.png]] 255 255 222 +**Connection:** 256 256 257 -(% style="color: blue" %)**Connection:**224 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 258 258 259 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**226 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 260 260 261 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**228 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 262 262 263 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 264 264 265 - 266 266 In the PC, use below serial tool settings: 267 267 268 268 * Baud: (% style="color:green" %)**9600** ... ... @@ -277,18 +277,17 @@ 277 277 278 278 [[image:1657329814315-101.png]] 279 279 280 - 281 281 ((( 282 -(% 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]]**246 +(% 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/]] 283 283 ))) 284 284 285 285 250 + 286 286 === 2.2.5 Use CoAP protocol to uplink data === 287 287 253 +(% 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/]] 288 288 289 -(% 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/]]** 290 290 291 - 292 292 ((( 293 293 **Use below commands:** 294 294 ))) ... ... @@ -297,10 +297,10 @@ 297 297 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 298 298 ))) 299 299 * ((( 300 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** 264 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 301 301 ))) 302 302 * ((( 303 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ 267 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 304 304 ))) 305 305 306 306 ((( ... ... @@ -319,6 +319,7 @@ 319 319 [[image:1657352185396-303.png]] 320 320 321 321 286 + 322 322 === 2.2.6 Use UDP protocol to uplink data(Default protocol) === 323 323 324 324 ... ... @@ -332,18 +332,18 @@ 332 332 [[image:1657352403317-397.png]] 333 333 334 334 300 + 335 335 === 2.2.7 Use MQTT protocol to uplink data === 336 336 337 - 338 338 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 339 339 340 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 341 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 342 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 343 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 344 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 345 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ 346 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ 305 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 306 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 307 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 308 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 309 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 310 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 311 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 347 347 348 348 [[image:1657352634421-276.png]] 349 349 ... ... @@ -350,19 +350,19 @@ 350 350 351 351 [[image:1657352645687-385.png]] 352 352 353 - 354 354 ((( 355 355 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. 356 356 ))) 357 357 322 + 358 358 ((( 359 359 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. 360 360 ))) 361 361 362 362 328 + 363 363 === 2.2.8 Use TCP protocol to uplink data === 364 364 365 - 366 366 This feature is supported since firmware version v110 367 367 368 368 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -374,9 +374,9 @@ 374 374 [[image:1657352914475-252.png]] 375 375 376 376 342 + 377 377 === 2.2.9 Change Update Interval === 378 378 379 - 380 380 User can use below command to change the (% style="color:green" %)**uplink interval**. 381 381 382 382 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -385,98 +385,58 @@ 385 385 386 386 ))) 387 387 388 -((( 389 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 390 -))) 391 391 392 -((( 393 -(% 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).** 394 -))) 395 395 396 - 397 397 == 2.3 Uplink Payload == 398 398 399 399 400 -((( 401 -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. 402 -))) 358 +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. 403 403 404 404 405 -((( 406 406 For example: 407 -))) 408 408 409 -((( 410 - (% 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. 411 -))) 363 + (% 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. 412 412 413 413 414 -((( 415 415 The uplink payloads are composed in ASCII String. For example: 416 -))) 417 417 418 -((( 419 419 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 420 -))) 421 421 422 -((( 423 423 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 424 -))) 425 425 426 426 427 -((( 428 428 (% style="color:red" %)**NOTE:** 429 -))) 430 430 431 431 (% style="color:red" %) 432 -1. ((( 433 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 434 -))) 435 -1. ((( 436 -**By default, the device will send an uplink message every 1 hour.** 376 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 377 +1. By default, the device will send an uplink message every 1 hour. 437 437 438 438 439 - 440 -))) 441 441 442 442 === 2.3.1 Payload Analyze === 443 443 444 - ==== 2.3.1.1BeforeFirmwarev1.2====383 +N95S31B uplink payload includes in total 21 bytes 445 445 446 446 447 -N95S31B uplink payload includes in total 21 bytes. 448 - 449 -(% border="1" style="background-color:#f2f2f2; width:520px" %) 450 -|=(% style="width: 50px;background-color:#D9E2F3" %)**Size(bytes)**|=(% style="width: 45px;background-color:#D9E2F3" %)**6**|=(% style="width: 25px;background-color:#D9E2F3" %)2|=(% style="width: 25px;background-color:#D9E2F3" %)**2**|=(% style="width: 65px;background-color:#D9E2F3" %)**1**|=(% style="width: 50px;background-color:#D9E2F3" %)1|=(% style="width: 120px;background-color:#D9E2F3" %)5|=(% style="width: 70px;background-color:#D9E2F3" %)**2**|=(% style="width: 70px;background-color:#D9E2F3" %)**2** 451 -|(% 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" %)((( 452 -((( 386 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 387 +|=(% style="width: 60px;" %)((( 388 +**Size(bytes)** 389 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1** 390 +|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)((( 453 453 Reserve/ Same as NBSN95 CFGMOD=1 454 -))) 455 455 456 -((( 457 457 No function here. 458 -))) 459 -)))|(% style="width:102px" %)((( 460 -((( 461 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 462 -))) 394 +)))|(% style="width:77px" %)((( 395 +[[Temperature >>||anchor="H2.4.5A0Distance"]] 463 463 464 -((( 465 465 By SHT31 466 -))) 467 -)))|(% style="width:81px" %)((( 468 -((( 469 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 470 -))) 398 +)))|(% style="width:80px" %)((( 399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 471 471 472 -((( 473 473 By SHT31 474 474 ))) 475 -))) 476 476 477 477 ((( 478 - 479 - 480 480 ((( 481 481 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 482 482 ))) ... ... @@ -486,89 +486,29 @@ 486 486 [[image:1657354294009-643.png]] 487 487 488 488 489 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457**414 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 490 490 491 -**where:** 416 +* Device ID: 0x724031607457 = 724031607457 417 +* Version: 0x006e=110=1.1.0 492 492 493 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 419 +* BAT: 0x0ccd = 3277 mV = 3.277V 420 +* Signal: 0x1b = 27 421 +* Model: 0x01 = 1 422 +* 0x00dc000ccc= reserve, ignore in N95S31B 423 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 424 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 494 494 495 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 496 - 497 -* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 498 - 499 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 500 - 501 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 502 - 503 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 504 - 505 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 506 - 507 -* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 508 - 509 509 ((( 510 510 428 +))) 511 511 430 +((( 512 512 513 513 ))) 514 514 515 -==== 2.3.1.2 Since Firmware v1.2 ==== 516 516 517 - 518 -In this mode, uplink payload includes 91 bytes in total by default. 519 - 520 -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. 521 - 522 - 523 -(% border="1" style="background-color:#f2f2f2; width:520px" %) 524 -|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:55px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:35px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:35px" %)**4** 525 -|=(% 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 ..... 526 - 527 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 528 - 529 - 530 -[[image:image-20220908154949-1.png]] 531 - 532 - 533 -The payload is ASCII string, representative same HEX: 534 - 535 -**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__ ** 536 - 537 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 538 - 539 -**where:** 540 - 541 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 542 - 543 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 544 - 545 -* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 546 - 547 -* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 548 - 549 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 550 - 551 -* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 552 - 553 -* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 554 - 555 -* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 556 - 557 -* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 558 - 559 -* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 560 - 561 -* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 562 - 563 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 564 - 565 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 566 - 567 - 568 - 569 569 === 2.3.2 Device ID === 570 570 571 - 572 572 ((( 573 573 By default, the Device ID equal to the last 6 bytes of IMEI. 574 574 ))) ... ... @@ -575,12 +575,10 @@ 575 575 576 576 ((( 577 577 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 578 - 579 - 580 580 ))) 581 581 582 582 ((( 583 - (% style="color:blue" %)**Example:**446 +**Example:** 584 584 ))) 585 585 586 586 ((( ... ... @@ -588,54 +588,30 @@ 588 588 ))) 589 589 590 590 ((( 591 -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. 592 - 593 - 454 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 594 594 ))) 595 595 596 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 597 597 598 598 599 -By default, the Device ID equal to the last 15 bits of IMEI. 600 - 601 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 602 - 603 - 604 -(% style="color:blue" %)**Example:** 605 - 606 -AT+DEUI=868411056754138 607 - 608 - 609 609 === 2.3.3 Version Info === 610 610 611 611 612 -((( 613 613 These bytes include the hardware and software version. 614 -))) 615 615 616 -((( 617 -**Higher byte:** Specify hardware version: always 0x00 for N95S31B 618 -))) 464 +Higher byte: Specify hardware version: always 0x00 for N95S31B 619 619 620 -((( 621 -**Lower byte:** Specify the software version: 0x6E=110, means firmware version 110 622 -))) 466 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 623 623 624 -((( 625 - 626 -))) 627 627 628 -((( 629 629 For example: 0x00 6E: this device is N95S31B with firmware version 110. 630 -))) 631 631 632 632 ((( 633 633 634 634 ))) 635 635 475 + 636 636 === 2.3.4 Battery Info === 637 637 638 - 639 639 ((( 640 640 Ex1: 0x0B45 = 2885mV 641 641 ))) ... ... @@ -645,9 +645,9 @@ 645 645 ))) 646 646 647 647 487 + 648 648 === 2.3.5 Signal Strength === 649 649 650 - 651 651 ((( 652 652 NB-IoT Network signal Strength. 653 653 ))) ... ... @@ -677,9 +677,9 @@ 677 677 ))) 678 678 679 679 519 + 680 680 === 2.3.6 Temperature & Humidity === 681 681 682 - 683 683 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 684 684 685 685 [[image:image-20220709161741-3.png]] ... ... @@ -695,16 +695,12 @@ 695 695 Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 696 696 697 697 698 -== 2.4 Downlink Payload == 699 699 538 +== 2.5 Downlink Payload == 700 700 701 -By default, 95S31Bprints the downlink payload to console port.540 +By default, NDDS75 prints the downlink payload to console port. 702 702 703 -(% border="1" style="background-color:#f2f2f2; width:520px" %) 704 -|(% style="background-color:#d9e2f3; color:#0070c0; width:200px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:170px" %)**Downlink payload size(bytes)** 705 -|(% style="width:204px" %)TDC(Transmit Time Interval)|(% style="width:80px" %)Any|(% style="width:94px" %)01|(% style="width:150px" %)4 706 -|(% style="width:204px" %)RESET|(% style="width:80px" %)Any|(% style="width:94px" %)04|(% style="width:150px" %)2 707 -|(% style="width:204px" %)INTMOD|(% style="width:80px" %)Any|(% style="width:94px" %)06|(% style="width:150px" %)4 542 +[[image:image-20220709100028-1.png]] 708 708 709 709 710 710 ((( ... ... @@ -740,7 +740,7 @@ 740 740 ))) 741 741 742 742 ((( 743 -If payload = 0x04FF, it will reset the 95S31B578 +If payload = 0x04FF, it will reset the NDDS75 744 744 ))) 745 745 746 746 ... ... @@ -751,76 +751,90 @@ 751 751 ))) 752 752 753 753 754 -== 2.5 Humidity and Temperature alarm function == 755 755 590 +== 2.8 Battery Analysis == 756 756 757 - **~(%style="color:blue"%)➢ ATCommand:(%%)**592 +=== 2.8.1 Battery Type === 758 758 759 759 760 -(% style="color:#037691" %)**AT+ SHHUM=min,max** 595 +((( 596 +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. 597 +))) 761 761 599 +((( 600 +The battery is designed to last for several years depends on the actually use environment and update interval. 601 +))) 762 762 763 -² When min=0, and max≠0, Alarm higher than max 603 +((( 604 +The battery related documents as below: 605 +))) 764 764 765 -² When min≠0, and max=0, Alarm lower than min 607 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 608 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 609 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 766 766 767 -² When min≠0 and max≠0, Alarm higher than max or lower than min 611 +((( 612 +[[image:image-20220709101450-2.png]] 613 +))) 768 768 769 769 770 - (% style="color:blue" %)**Example:** 771 771 772 - AT+ SHHUM=50,80~/~/ Alarmwhenhumiditylowerthan 50.617 +=== 2.8.2 Power consumption Analyze === 773 773 619 +((( 620 +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. 621 +))) 774 774 775 -(% style="color:#037691" %)**AT+ SHTEMP=min,max** 776 776 777 -² When min=0, and max≠0, Alarm higher than max 624 +((( 625 +Instruction to use as below: 626 +))) 778 778 779 -² When min≠0, and max=0, Alarm lower than min 628 +((( 629 +(% 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/]] 630 +))) 780 780 781 -² When min≠0 and max≠0, Alarm higher than max or lower than min 782 782 633 +((( 634 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 635 +))) 783 783 784 -**~ (% style="color:blue" %)Example:(%%)** 637 +* ((( 638 +Product Model 639 +))) 640 +* ((( 641 +Uplink Interval 642 +))) 643 +* ((( 644 +Working Mode 645 +))) 785 785 786 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 647 +((( 648 +And the Life expectation in difference case will be shown on the right. 649 +))) 787 787 651 +[[image:image-20220709110451-3.png]] 788 788 789 -== 2.6 Set the number of data to be uploaded and the recording time == 790 790 791 791 792 - **~(%style="color:blue"%)➢ AT Command:(%%)**655 +=== 2.8.3 Battery Note === 793 793 794 -* (% 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) 795 -* (% 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. 657 +((( 658 +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. 659 +))) 796 796 797 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 798 798 799 -[[image:image-20221009001045-1.png||height="726" width="1009"]] 800 800 663 +=== 2.8.4 Replace the battery === 801 801 802 -== 2.7 Read or Clear cached data == 665 +((( 666 +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). 667 +))) 803 803 804 804 805 -**~ (% style="color:blue" %)➢ AT Command:(%%)** 806 806 807 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 808 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 809 - 810 -[[image:image-20220908163102-2.png]] 811 - 812 - 813 -== 2.8 Battery & Power Consumption == 814 - 815 - 816 -N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 817 - 818 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 819 - 820 - 821 821 = 3. Access NB-IoT Module = 822 822 823 - 824 824 ((( 825 825 Users can directly access the AT command set of the NB-IoT module. 826 826 ))) ... ... @@ -827,21 +827,19 @@ 827 827 828 828 ((( 829 829 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/]] 830 - 831 - 832 832 ))) 833 833 834 834 [[image:1657333200519-600.png]] 835 835 836 836 684 + 837 837 = 4. Using the AT Commands = 838 838 839 839 == 4.1 Access AT Commands == 840 840 689 +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/]] 841 841 842 -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]] 843 843 844 - 845 845 AT+<CMD>? : Help on <CMD> 846 846 847 847 AT+<CMD> : Run <CMD> ... ... @@ -881,24 +881,7 @@ 881 881 882 882 AT+SERVADDR : Server Address 883 883 884 -AT+TR : Get or Set record time 885 885 886 -AT+APN : Get or set the APN 887 - 888 -AT+FBAND : Get or Set whether to automatically modify the frequency band 889 - 890 -AT+DNSCFG : Get or Set DNS Server 891 - 892 -AT+GETSENSORVALUE : Returns the current sensor measurement 893 - 894 -AT+NOUD : Get or Set the number of data to be uploaded 895 - 896 -AT+CDP : Read or Clear cached data 897 - 898 -AT+SHTEMP: Get or Set alarm of temp 899 - 900 -AT+SHHUM: Get or Set alarm of moisture 901 - 902 902 (% style="color:#037691" %)**COAP Management** 903 903 904 904 AT+URI : Resource parameters ... ... @@ -929,6 +929,7 @@ 929 929 AT+PWORD : Serial Access Password 930 930 931 931 762 + 932 932 = 5. FAQ = 933 933 934 934 == 5.1 How to Upgrade Firmware == ... ... @@ -943,12 +943,11 @@ 943 943 ))) 944 944 945 945 ((( 946 -Firmware Download:[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]] 947 - 948 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 777 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 949 949 ))) 950 950 951 951 781 + 952 952 = 6. Trouble Shooting = 953 953 954 954 == 6.1 Connection problem when uploading firmware == ... ... @@ -958,10 +958,14 @@ 958 958 **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]] 959 959 ))) 960 960 791 +(% class="wikigeneratedid" %) 792 +((( 793 + 794 +))) 961 961 796 + 962 962 == 6.2 AT Command input doesn't work == 963 963 964 - 965 965 ((( 966 966 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. 967 967 ... ... @@ -968,18 +968,18 @@ 968 968 969 969 ))) 970 970 971 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 972 972 973 - 974 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 975 - 976 - 977 977 = 7. Order Info = 978 978 979 979 980 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**809 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 981 981 982 982 812 +(% class="wikigeneratedid" %) 813 +((( 814 + 815 +))) 816 + 983 983 = 8. Packing Info = 984 984 985 985 ((( ... ... @@ -987,7 +987,7 @@ 987 987 988 988 (% style="color:#037691" %)**Package Includes**: 989 989 990 -* N 95S31BNB-IoTTemperatureandHumiditySensor824 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 991 991 * External antenna x 1 992 992 ))) 993 993 ... ... @@ -996,19 +996,21 @@ 996 996 997 997 (% style="color:#037691" %)**Dimension and weight**: 998 998 833 + 999 999 * Device Size: 13.0 x 5 x 4.5 cm 1000 1000 * Device Weight: 150g 1001 -* Package Size / pcs : 1 4.0x8x 5 cm1002 -* Weight / pcs : 180g836 +* Package Size / pcs : 15 x 12x 5.5 cm 837 +* Weight / pcs : 220g 1003 1003 ))) 1004 1004 840 +((( 841 + 1005 1005 1006 1006 844 + 845 +))) 846 + 1007 1007 = 9. Support = 1008 1008 1009 - 1010 1010 * 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. 1011 - 1012 1012 * 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]] 1013 - 1014 -
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 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