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, 4 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -55,6 +55,7 @@ 55 55 56 56 == 1.2 Features == 57 57 58 + 58 58 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 59 59 * Monitor Temperature & Humidity via SHT31 60 60 * AT Commands to change parameters ... ... @@ -68,7 +68,6 @@ 68 68 69 69 70 70 71 - 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -77,7 +77,6 @@ 77 77 * Supply Voltage: 2.1v ~~ 3.6v 78 78 * Operating Temperature: -40 ~~ 85°C 79 79 80 - 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 83 * - B1 @H-FDD: 2100MHz ... ... @@ -87,7 +87,6 @@ 87 87 * - B20 @H-FDD: 800MHz 88 88 * - B28 @H-FDD: 700MHz 89 89 90 - 91 91 (% style="color:#037691" %)**Battery:** 92 92 93 93 * Li/SOCI2 un-chargeable battery ... ... @@ -98,9 +98,9 @@ 98 98 99 99 100 100 101 - 102 102 == 1.4 Applications == 103 103 101 + 104 104 * Smart Buildings & Home Automation 105 105 * Logistics and Supply Chain Management 106 106 * Smart Metering ... ... @@ -112,44 +112,49 @@ 112 112 113 113 114 114 115 -== 1.5 Pin Definitions == 113 +== 1.5 Pin Definitions & Switch == 116 116 115 + 117 117 N95S31B use the mother board from NBSN95 which as below. 118 118 118 + 119 119 [[image:image-20220709144723-1.png]] 120 120 121 121 122 122 === 1.5.1 Jumper JP2 === 123 123 124 + 124 124 Power on Device when put this jumper. 125 125 126 126 127 - 128 128 === 1.5.2 BOOT MODE / SW1 === 129 129 130 + 130 130 ((( 131 -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. 132 +**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. 132 132 ))) 133 133 134 134 ((( 135 -2) Flash: work mode, device starts to work and send out console output for further debug 136 +**2) Flash:** work mode, device starts to work and send out console output for further debug 136 136 ))) 137 137 138 138 139 - 140 140 === 1.5.3 Reset Button === 141 141 142 + 142 142 Press to reboot the device. 143 143 144 144 145 - 146 146 === 1.5.4 LED === 147 147 148 + 148 148 It will flash: 149 149 150 -1. When boot the device in flash mode 151 -1. Send an uplink packet 151 +1. When boot the device in flash mode 152 152 153 +2. Send an uplink packet 154 + 155 + 153 153 = 2. Use N95S31B to communicate with IoT Server = 154 154 155 155 == 2.1 How it works == ... ... @@ -168,7 +168,7 @@ 168 168 169 169 ))) 170 170 171 -[[image:1657 350248151-650.png]]174 +[[image:1657520100595-569.png]] 172 172 173 173 ((( 174 174 ... ... @@ -177,7 +177,6 @@ 177 177 178 178 == 2.2 Configure the N95S31B == 179 179 180 - 181 181 === 2.2.1 Power On N95S31B === 182 182 183 183 ... ... @@ -184,26 +184,48 @@ 184 184 [[image:image-20220709150546-2.png]] 185 185 186 186 187 -=== 2.2. 1Test Requirement ===189 +=== 2.2.2 Test Requirement === 188 188 189 189 192 +((( 190 190 To use N95S31B in your city, make sure meet below requirements: 194 +))) 191 191 192 -* Your local operator has already distributed a NB-IoT Network there. 193 -* The local NB-IoT network used the band that N95S31B supports. 194 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 196 +* ((( 197 +Your local operator has already distributed a NB-IoT Network there. 198 +))) 199 +* ((( 200 +The local NB-IoT network used the band that N95S31B supports. 201 +))) 202 +* ((( 203 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 204 +))) 195 195 206 +((( 196 196 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 208 +))) 197 197 210 +((( 198 198 N95S31B supports different communication protocol such as : 212 +))) 199 199 200 200 ((( 201 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 202 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 203 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 204 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 215 +* ((( 216 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 217 +))) 218 +* ((( 219 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 220 +))) 221 +* ((( 222 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 223 +))) 224 +* ((( 225 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 226 +))) 205 205 228 +((( 206 206 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. 230 +))) 207 207 208 208 209 209 ))) ... ... @@ -211,9 +211,9 @@ 211 211 [[image:1657350625843-586.png]] 212 212 213 213 214 - 215 215 === 2.2.3 Insert SIM card === 216 216 240 + 217 217 ((( 218 218 Insert the NB-IoT Card get from your provider. 219 219 ))) ... ... @@ -226,26 +226,29 @@ 226 226 [[image:1657351240556-536.png]] 227 227 228 228 229 - 230 230 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 231 231 255 + 232 232 ((( 233 233 ((( 234 234 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. 259 + 260 + 235 235 ))) 236 236 ))) 237 237 238 238 [[image:1657351312545-300.png]] 239 239 240 -**Connection:** 241 241 242 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND267 +(% style="color:blue" %)**Connection:** 243 243 244 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD269 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 245 245 246 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD271 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 247 247 273 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 248 248 275 + 249 249 In the PC, use below serial tool settings: 250 250 251 251 * Baud: (% style="color:green" %)**9600** ... ... @@ -260,17 +260,18 @@ 260 260 261 261 [[image:1657329814315-101.png]] 262 262 290 + 263 263 ((( 264 -(% 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/]]292 +(% 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]]** 265 265 ))) 266 266 267 267 268 - 269 269 === 2.2.5 Use CoAP protocol to uplink data === 270 270 271 -(% 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/]] 272 272 299 +(% 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/]]** 273 273 301 + 274 274 ((( 275 275 **Use below commands:** 276 276 ))) ... ... @@ -279,10 +279,10 @@ 279 279 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 280 280 ))) 281 281 * ((( 282 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 310 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 283 283 ))) 284 284 * ((( 285 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 313 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 286 286 ))) 287 287 288 288 ((( ... ... @@ -301,7 +301,6 @@ 301 301 [[image:1657352185396-303.png]] 302 302 303 303 304 - 305 305 === 2.2.6 Use UDP protocol to uplink data(Default protocol) === 306 306 307 307 ... ... @@ -315,18 +315,18 @@ 315 315 [[image:1657352403317-397.png]] 316 316 317 317 318 - 319 319 === 2.2.7 Use MQTT protocol to uplink data === 320 320 347 + 321 321 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 322 322 323 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 324 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 325 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 326 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 327 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 328 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 329 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 350 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 351 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 352 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 353 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 354 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 355 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ Set the sending topic of MQTT 356 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ Set the subscription topic of MQTT 330 330 331 331 [[image:1657352634421-276.png]] 332 332 ... ... @@ -333,6 +333,7 @@ 333 333 334 334 [[image:1657352645687-385.png]] 335 335 363 + 336 336 ((( 337 337 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. 338 338 ))) ... ... @@ -343,9 +343,9 @@ 343 343 ))) 344 344 345 345 346 - 347 347 === 2.2.8 Use TCP protocol to uplink data === 348 348 376 + 349 349 This feature is supported since firmware version v110 350 350 351 351 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -357,9 +357,9 @@ 357 357 [[image:1657352914475-252.png]] 358 358 359 359 360 - 361 361 === 2.2.9 Change Update Interval === 362 362 390 + 363 363 User can use below command to change the (% style="color:green" %)**uplink interval**. 364 364 365 365 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -368,43 +368,71 @@ 368 368 369 369 ))) 370 370 399 +((( 400 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 401 +))) 371 371 403 +((( 404 +(% 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).** 405 +))) 372 372 407 + 373 373 == 2.3 Uplink Payload == 374 374 375 375 376 -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. 411 +((( 412 +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. 413 +))) 377 377 378 378 416 +((( 379 379 For example: 418 +))) 380 380 381 - (% 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. 420 +((( 421 + (% 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. 422 +))) 382 382 383 383 425 +((( 384 384 The uplink payloads are composed in ASCII String. For example: 427 +))) 385 385 429 +((( 386 386 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 431 +))) 387 387 433 +((( 388 388 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 435 +))) 389 389 390 390 438 +((( 391 391 (% style="color:red" %)**NOTE:** 440 +))) 392 392 393 393 (% style="color:red" %) 394 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 395 -1. By default, the device will send an uplink message every 1 hour. 443 +1. ((( 444 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 445 +))) 446 +1. ((( 447 +**By default, the device will send an uplink message every 1 hour.** 396 396 397 397 450 + 451 +))) 452 + 398 398 === 2.3.1 Payload Analyze === 399 399 455 +==== 2.3.1.1 Before Firmware v1.2 ==== 456 + 457 + 400 400 N95S31B uplink payload includes in total 21 bytes 401 401 402 402 403 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 404 -|=(% style="width: 60px;" %)((( 405 -**Size(bytes)** 406 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 407 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 461 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 462 +|=(% 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** 463 +|(% 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" %)((( 408 408 ((( 409 409 Reserve/ Same as NBSN95 CFGMOD=1 410 410 ))) ... ... @@ -412,7 +412,7 @@ 412 412 ((( 413 413 No function here. 414 414 ))) 415 -)))|(% style="width: 77px" %)(((471 +)))|(% style="width:102px" %)((( 416 416 ((( 417 417 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 418 418 ))) ... ... @@ -420,7 +420,7 @@ 420 420 ((( 421 421 By SHT31 422 422 ))) 423 -)))|(% style="width:8 0px" %)(((479 +)))|(% style="width:81px" %)((( 424 424 ((( 425 425 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 426 426 ))) ... ... @@ -431,6 +431,8 @@ 431 431 ))) 432 432 433 433 ((( 490 + 491 + 434 434 ((( 435 435 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 436 436 ))) ... ... @@ -440,29 +440,90 @@ 440 440 [[image:1657354294009-643.png]] 441 441 442 442 443 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:501 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 444 444 445 -* Device ID: 0x724031607457 = 724031607457 446 -* Version: 0x006e=110=1.1.0 503 +**where:** 447 447 448 -* BAT: 0x0ccd = 3277 mV = 3.277V 449 -* Signal: 0x1b = 27 450 -* Model: 0x01 = 1 451 -* 0x00dc000ccc= reserve, ignore in N95S31B 452 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 453 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 505 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 454 454 507 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 508 + 509 +* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 510 + 511 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 512 + 513 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 514 + 515 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 516 + 517 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 518 + 519 +* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 520 + 455 455 ((( 456 456 457 -))) 458 458 459 - (((524 + 460 460 461 461 ))) 462 462 528 +==== 2.3.1.2 Since Firmware v1.2 ==== 463 463 530 + 531 +In this mode, uplink payload includes 91 bytes in total by default. 532 + 533 +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. 534 + 535 + 536 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 537 +|=(% 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** 538 +|=(% 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 ..... 539 + 540 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 541 + 542 + 543 +[[image:image-20220908154949-1.png]] 544 + 545 + 546 +The payload is ASCII string, representative same HEX: 547 + 548 +**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__ ** 549 + 550 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 551 + 552 +**where:** 553 + 554 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 555 + 556 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 557 + 558 +* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 559 + 560 +* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 561 + 562 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 563 + 564 +* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 565 + 566 +* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 567 + 568 +* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 569 + 570 +* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 571 + 572 +* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 573 + 574 +* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 575 + 576 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 577 + 578 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 579 + 580 + 581 + 464 464 === 2.3.2 Device ID === 465 465 584 + 466 466 ((( 467 467 By default, the Device ID equal to the last 6 bytes of IMEI. 468 468 ))) ... ... @@ -469,10 +469,12 @@ 469 469 470 470 ((( 471 471 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 591 + 592 + 472 472 ))) 473 473 474 474 ((( 475 -**Example:** 596 +(% style="color:blue" %)**Example:** 476 476 ))) 477 477 478 478 ((( ... ... @@ -480,30 +480,54 @@ 480 480 ))) 481 481 482 482 ((( 483 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 604 +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. 605 + 606 + 484 484 ))) 485 485 609 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 486 486 487 487 612 +By default, the Device ID equal to the last 15 bits of IMEI. 613 + 614 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 615 + 616 + 617 +(% style="color:blue" %)**Example:** 618 + 619 +AT+DEUI=868411056754138 620 + 621 + 488 488 === 2.3.3 Version Info === 489 489 490 490 625 +((( 491 491 These bytes include the hardware and software version. 627 +))) 492 492 629 +((( 493 493 Higher byte: Specify hardware version: always 0x00 for N95S31B 631 +))) 494 494 633 +((( 495 495 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 635 +))) 496 496 637 +((( 638 + 639 +))) 497 497 641 +((( 498 498 For example: 0x00 6E: this device is N95S31B with firmware version 110. 643 +))) 499 499 500 500 ((( 501 501 502 502 ))) 503 503 504 - 505 505 === 2.3.4 Battery Info === 506 506 651 + 507 507 ((( 508 508 Ex1: 0x0B45 = 2885mV 509 509 ))) ... ... @@ -513,9 +513,9 @@ 513 513 ))) 514 514 515 515 516 - 517 517 === 2.3.5 Signal Strength === 518 518 663 + 519 519 ((( 520 520 NB-IoT Network signal Strength. 521 521 ))) ... ... @@ -545,9 +545,9 @@ 545 545 ))) 546 546 547 547 548 - 549 549 === 2.3.6 Temperature & Humidity === 550 550 695 + 551 551 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 552 552 553 553 [[image:image-20220709161741-3.png]] ... ... @@ -563,11 +563,11 @@ 563 563 Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 564 564 565 565 566 - 567 567 == 2.4 Downlink Payload == 568 568 569 -By default, NDDS75 prints the downlink payload to console port. 570 570 714 +By default, N95S31B prints the downlink payload to console port. 715 + 571 571 [[image:image-20220709100028-1.png]] 572 572 573 573 ... ... @@ -604,7 +604,7 @@ 604 604 ))) 605 605 606 606 ((( 607 -If payload = 0x04FF, it will reset the DDS75752 +If payload = 0x04FF, it will reset the N95S31B 608 608 ))) 609 609 610 610 ... ... @@ -615,12 +615,70 @@ 615 615 ))) 616 616 617 617 763 +== 2.5 Humidity and Temperature alarm function == 618 618 619 -== 2.5 Battery Analysis == 620 620 621 - ===2.5.1BatteryType===766 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 622 622 623 623 769 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 770 + 771 + 772 +² When min=0, and max≠0, Alarm higher than max 773 + 774 +² When min≠0, and max=0, Alarm lower than min 775 + 776 +² When min≠0 and max≠0, Alarm higher than max or lower than min 777 + 778 + 779 + (% style="color:blue" %)**Example:** 780 + 781 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 782 + 783 + 784 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 785 + 786 +² When min=0, and max≠0, Alarm higher than max 787 + 788 +² When min≠0, and max=0, Alarm lower than min 789 + 790 +² When min≠0 and max≠0, Alarm higher than max or lower than min 791 + 792 + 793 +**~ (% style="color:blue" %)Example:(%%)** 794 + 795 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 796 + 797 + 798 +== 2.6 Set the number of data to be uploaded and the recording time == 799 + 800 + 801 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 802 + 803 +* (% 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) 804 +* (% 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. 805 + 806 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 807 + 808 +[[image:image-20221009001045-1.png||height="726" width="1009"]] 809 + 810 + 811 +== 2.7 Read or Clear cached data == 812 + 813 + 814 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 815 + 816 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 817 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 818 + 819 +[[image:image-20220908163102-2.png]] 820 + 821 + 822 +== 2.8 Battery Analysis == 823 + 824 +=== 2.8.1 Battery Type === 825 + 826 + 624 624 ((( 625 625 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. 626 626 ))) ... ... @@ -642,11 +642,11 @@ 642 642 ))) 643 643 644 644 848 +=== 2.8.2 Power consumption Analyze === 645 645 646 -=== 2.5.2 Power consumption Analyze === 647 647 648 648 ((( 649 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]852 +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. 650 650 ))) 651 651 652 652 ((( ... ... @@ -653,8 +653,8 @@ 653 653 654 654 ))) 655 655 859 +=== 2.8.3 Battery Note === 656 656 657 -=== 2.5.3 Battery Note === 658 658 659 659 ((( 660 660 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. ... ... @@ -661,10 +661,9 @@ 661 661 ))) 662 662 663 663 867 +=== 2.8.4 Replace the battery === 664 664 665 -=== 2.5.4 Replace the battery === 666 666 667 - 668 668 ((( 669 669 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. 670 670 ))) ... ... @@ -675,9 +675,9 @@ 675 675 ))) 676 676 677 677 678 - 679 679 = 3. Access NB-IoT Module = 680 680 882 + 681 681 ((( 682 682 Users can directly access the AT command set of the NB-IoT module. 683 683 ))) ... ... @@ -684,19 +684,21 @@ 684 684 685 685 ((( 686 686 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/]] 889 + 890 + 687 687 ))) 688 688 689 689 [[image:1657333200519-600.png]] 690 690 691 691 692 - 693 693 = 4. Using the AT Commands = 694 694 695 695 == 4.1 Access AT Commands == 696 696 697 -See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]] 698 698 901 +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]] 699 699 903 + 700 700 AT+<CMD>? : Help on <CMD> 701 701 702 702 AT+<CMD> : Run <CMD> ... ... @@ -736,7 +736,24 @@ 736 736 737 737 AT+SERVADDR : Server Address 738 738 943 +AT+TR : Get or Set record time 739 739 945 +AT+APN : Get or set the APN 946 + 947 +AT+FBAND : Get or Set whether to automatically modify the frequency band 948 + 949 +AT+DNSCFG : Get or Set DNS Server 950 + 951 +AT+GETSENSORVALUE : Returns the current sensor measurement 952 + 953 +AT+NOUD : Get or Set the number of data to be uploaded 954 + 955 +AT+CDP : Read or Clear cached data 956 + 957 +AT+SHTEMP: Get or Set alarm of temp 958 + 959 +AT+SHHUM: Get or Set alarm of moisture 960 + 740 740 (% style="color:#037691" %)**COAP Management** 741 741 742 742 AT+URI : Resource parameters ... ... @@ -767,7 +767,6 @@ 767 767 AT+PWORD : Serial Access Password 768 768 769 769 770 - 771 771 = 5. FAQ = 772 772 773 773 == 5.1 How to Upgrade Firmware == ... ... @@ -784,11 +784,12 @@ 784 784 ((( 785 785 786 786 787 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 1007 +((( 1008 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 788 788 ))) 1010 +))) 789 789 790 790 791 - 792 792 = 6. Trouble Shooting = 793 793 794 794 == 6.1 Connection problem when uploading firmware == ... ... @@ -803,9 +803,9 @@ 803 803 804 804 ))) 805 805 806 - 807 807 == 6.2 AT Command input doesn't work == 808 808 1029 + 809 809 ((( 810 810 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. 811 811 ... ... @@ -812,7 +812,6 @@ 812 812 813 813 ))) 814 814 815 - 816 816 = 7. Order Info = 817 817 818 818 ... ... @@ -819,11 +819,6 @@ 819 819 Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 820 820 821 821 822 -(% class="wikigeneratedid" %) 823 -((( 824 - 825 -))) 826 - 827 827 = 8. Packing Info = 828 828 829 829 ((( ... ... @@ -849,11 +849,16 @@ 849 849 ((( 850 850 851 851 852 - 853 853 854 854 ))) 855 855 856 856 = 9. Support = 857 857 1072 + 858 858 * 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. 859 859 * 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]] 1075 + 1076 + 1077 + 1078 + 1079 +
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 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