<
From version < 119.2 >
edited by Xiaoling
on 2022/08/22 14:47
To version < 129.36 >
edited by Xiaoling
on 2023/04/03 17:01
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,7 +17,6 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 -
21 21  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
22 22  
23 23  (((
... ... @@ -70,7 +70,6 @@
70 70  
71 71  
72 72  
73 -
74 74  == 1.3  Specification ==
75 75  
76 76  
... ... @@ -79,19 +79,15 @@
79 79  * Supply Voltage: 2.1v ~~ 3.6v
80 80  * Operating Temperature: -40 ~~ 85°C
81 81  
82 -
83 -
84 84  (% style="color:#037691" %)**NB-IoT Spec:**
85 85  
86 -* - B1 @H-FDD: 2100MHz
87 -* - B3 @H-FDD: 1800MHz
88 -* - B8 @H-FDD: 900MHz
89 -* - B5 @H-FDD: 850MHz
90 -* - B20 @H-FDD: 800MHz
91 -* - B28 @H-FDD: 700MHz
82 +* B1 @H-FDD: 2100MHz
83 +* B3 @H-FDD: 1800MHz
84 +* B8 @H-FDD: 900MHz
85 +* B5 @H-FDD: 850MHz
86 +* B20 @H-FDD: 800MHz
87 +* B28 @H-FDD: 700MHz
92 92  
93 -
94 -
95 95  (% style="color:#037691" %)**Battery:**
96 96  
97 97  * Li/SOCI2 un-chargeable battery
... ... @@ -102,7 +102,6 @@
102 102  
103 103  
104 104  
105 -
106 106  == ​1.4  Applications ==
107 107  
108 108  
... ... @@ -117,7 +117,6 @@
117 117  ​
118 118  
119 119  
120 -
121 121  == 1.5  Pin Definitions & Switch ==
122 122  
123 123  
... ... @@ -127,7 +127,6 @@
127 127  [[image:image-20220709144723-1.png]]
128 128  
129 129  
130 -
131 131  === 1.5.1 Jumper JP2 ===
132 132  
133 133  
... ... @@ -134,20 +134,18 @@
134 134  Power on Device when put this jumper.
135 135  
136 136  
137 -
138 138  === 1.5.2 BOOT MODE / SW1 ===
139 139  
140 140  
141 141  (((
142 -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.
143 143  )))
144 144  
145 145  (((
146 -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
147 147  )))
148 148  
149 149  
150 -
151 151  === 1.5.3 Reset Button ===
152 152  
153 153  
... ... @@ -154,21 +154,18 @@
154 154  Press to reboot the device.
155 155  
156 156  
157 -
158 158  === 1.5.4 LED ===
159 159  
160 160  
161 161  It will flash:
162 162  
163 -1. When boot the device in flash mode
164 -1. Send an uplink packet
151 +1.  When boot the device in flash mode
165 165  
153 +2.  Send an uplink packet
166 166  
167 167  
168 -
169 169  = 2.  Use N95S31B to communicate with IoT Server =
170 170  
171 -
172 172  == 2.1  How it works ==
173 173  
174 174  
... ... @@ -194,7 +194,6 @@
194 194  
195 195  == 2.2 ​ Configure the N95S31B ==
196 196  
197 -
198 198  === 2.2.1  Power On N95S31B ===
199 199  
200 200  
... ... @@ -201,10 +201,9 @@
201 201  [[image:image-20220709150546-2.png]]
202 202  
203 203  
189 +=== 2.2.2 Test Requirement ===
204 204  
205 -=== 2.2.1 Test Requirement ===
206 206  
207 -
208 208  (((
209 209  To use N95S31B in your city, make sure meet below requirements:
210 210  )))
... ... @@ -251,7 +251,6 @@
251 251  [[image:1657350625843-586.png]]
252 252  
253 253  
254 -
255 255  === 2.2.3  Insert SIM card ===
256 256  
257 257  
... ... @@ -267,7 +267,6 @@
267 267  [[image:1657351240556-536.png]]
268 268  
269 269  
270 -
271 271  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
272 272  
273 273  
... ... @@ -282,13 +282,13 @@
282 282  [[image:1657351312545-300.png]]
283 283  
284 284  
285 -**Connection:**
267 +(% style="color:blue" %)**Connection:**
286 286  
287 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
269 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
288 288  
289 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
271 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
290 290  
291 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
273 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
292 292  
293 293  
294 294  In the PC, use below serial tool settings:
... ... @@ -311,7 +311,6 @@
311 311  )))
312 312  
313 313  
314 -
315 315  === 2.2.5  Use CoAP protocol to uplink data ===
316 316  
317 317  
... ... @@ -326,10 +326,10 @@
326 326  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
327 327  )))
328 328  * (((
329 -(% 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
330 330  )))
331 331  * (((
332 -(% 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
333 333  )))
334 334  
335 335  (((
... ... @@ -348,7 +348,6 @@
348 348  [[image:1657352185396-303.png]]
349 349  
350 350  
351 -
352 352  === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
353 353  
354 354  
... ... @@ -362,18 +362,18 @@
362 362  [[image:1657352403317-397.png]]
363 363  
364 364  
365 -
366 366  === 2.2.7  Use MQTT protocol to uplink data ===
367 367  
347 +
368 368  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
369 369  
370 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
371 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
372 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
373 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
374 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
375 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
376 -* (% 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
377 377  
378 378  [[image:1657352634421-276.png]]
379 379  
... ... @@ -380,6 +380,7 @@
380 380  
381 381  [[image:1657352645687-385.png]]
382 382  
363 +
383 383  (((
384 384  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.
385 385  )))
... ... @@ -390,9 +390,9 @@
390 390  )))
391 391  
392 392  
393 -
394 394  === 2.2.8  Use TCP protocol to uplink data ===
395 395  
376 +
396 396  This feature is supported since firmware version v110
397 397  
398 398  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -404,9 +404,9 @@
404 404  [[image:1657352914475-252.png]]
405 405  
406 406  
407 -
408 408  === 2.2.9  Change Update Interval ===
409 409  
390 +
410 410  User can use below command to change the (% style="color:green" %)**uplink interval**.
411 411  
412 412  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -415,13 +415,20 @@
415 415  
416 416  )))
417 417  
399 +(((
400 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
401 +)))
418 418  
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 +)))
419 419  
407 +
420 420  == 2.3  Uplink Payload ==
421 421  
422 422  
423 423  (((
424 -N95S31B 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.
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.
425 425  )))
426 426  
427 427  
... ... @@ -453,26 +453,26 @@
453 453  
454 454  (% style="color:red" %)
455 455  1. (((
456 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
444 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
457 457  )))
458 458  1. (((
459 -By default, the device will send an uplink message every 1 hour.
447 +**By default, the device will send an uplink message every 1 hour.**
460 460  
461 461  
462 -
463 463  
464 464  )))
465 465  
466 466  === 2.3.1  Payload Analyze ===
467 467  
455 +==== 2.3.1.1  Before Firmware v1.2 ====
456 +
457 +
468 468  N95S31B uplink payload includes in total 21 bytes
469 469  
470 470  
471 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
472 -|=(% style="width: 60px;" %)(((
473 -**Size(bytes)**
474 -)))|=(% 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**
475 -|(% 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" %)(((
476 476  (((
477 477  Reserve/ Same as NBSN95 CFGMOD=1
478 478  )))
... ... @@ -480,7 +480,7 @@
480 480  (((
481 481  No function here.
482 482  )))
483 -)))|(% style="width:77px" %)(((
471 +)))|(% style="width:102px" %)(((
484 484  (((
485 485  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
486 486  )))
... ... @@ -488,7 +488,7 @@
488 488  (((
489 489  By SHT31
490 490  )))
491 -)))|(% style="width:80px" %)(((
479 +)))|(% style="width:81px" %)(((
492 492  (((
493 493  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
494 494  )))
... ... @@ -499,6 +499,8 @@
499 499  )))
500 500  
501 501  (((
490 +
491 +
502 502  (((
503 503  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
504 504  )))
... ... @@ -508,29 +508,89 @@
508 508  [[image:1657354294009-643.png]]
509 509  
510 510  
511 -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**
512 512  
513 -* Device ID: 0x724031607457 = 724031607457
514 -* Version: 0x006e=110=1.1.0
503 +**where:**
515 515  
516 -* BAT: 0x0ccd = 3277 mV = 3.277V
517 -* Signal: 0x1b = 27
518 -* Model: 0x01 = 1
519 -* 0x00dc000ccc= reserve, ignore in N95S31B
520 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
521 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
505 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
522 522  
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 +
523 523  (((
524 524  
525 -)))
526 526  
527 -(((
528 528  
529 529  )))
530 530  
527 +==== 2.3.1.2 Since Firmware v1.2 ====
531 531  
529 +
530 +In this mode, uplink payload includes 91 bytes in total by default.
531 +
532 +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.
533 +
534 +
535 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
536 +|=(% 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**
537 +|=(% 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 .....
538 +
539 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
540 +
541 +
542 +[[image:image-20220908154949-1.png]]
543 +
544 +
545 +The payload is ASCII string, representative same HEX:
546 +
547 +**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__ **
548 +
549 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
550 +
551 +**where:**
552 +
553 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
554 +
555 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
556 +
557 +* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
558 +
559 +* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
560 +
561 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
562 +
563 +* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
564 +
565 +* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
566 +
567 +* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
568 +
569 +* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
570 +
571 +* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
572 +
573 +* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
574 +
575 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
576 +
577 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
578 +
579 +
580 +
532 532  === 2.3.2  Device ID ===
533 533  
583 +
534 534  (((
535 535  By default, the Device ID equal to the last 6 bytes of IMEI.
536 536  )))
... ... @@ -537,10 +537,12 @@
537 537  
538 538  (((
539 539  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
590 +
591 +
540 540  )))
541 541  
542 542  (((
543 -**Example:**
595 +(% style="color:blue" %)**Example:**
544 544  )))
545 545  
546 546  (((
... ... @@ -548,13 +548,27 @@
548 548  )))
549 549  
550 550  (((
551 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
603 +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.
604 +
605 +
552 552  )))
553 553  
608 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
554 554  
555 555  
611 +By default, the Device ID equal to the last 15 bits of IMEI.
612 +
613 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
614 +
615 +
616 +(% style="color:blue" %)**Example:**
617 +
618 +AT+DEUI=868411056754138
619 +
620 +
556 556  === 2.3.3  Version Info ===
557 557  
623 +
558 558  (((
559 559  These bytes include the hardware and software version.
560 560  )))
... ... @@ -579,9 +579,9 @@
579 579  
580 580  )))
581 581  
582 -
583 583  === 2.3.4  Battery Info ===
584 584  
650 +
585 585  (((
586 586  Ex1: 0x0B45 = 2885mV
587 587  )))
... ... @@ -591,9 +591,9 @@
591 591  )))
592 592  
593 593  
594 -
595 595  === 2.3.5  Signal Strength ===
596 596  
662 +
597 597  (((
598 598  NB-IoT Network signal Strength.
599 599  )))
... ... @@ -623,9 +623,9 @@
623 623  )))
624 624  
625 625  
626 -
627 627  === 2.3.6  Temperature & Humidity ===
628 628  
694 +
629 629  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
630 630  
631 631  [[image:image-20220709161741-3.png]]
... ... @@ -641,9 +641,9 @@
641 641  Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
642 642  
643 643  
644 -
645 645  == 2.4  Downlink Payload ==
646 646  
712 +
647 647  By default, N95S31B prints the downlink payload to console port.
648 648  
649 649  [[image:image-20220709100028-1.png]]
... ... @@ -693,69 +693,76 @@
693 693  )))
694 694  
695 695  
762 +== 2.5  Humidity and Temperature alarm function ==
696 696  
697 -== 2.5  ​Battery Analysis ==
698 698  
699 -=== 2.5.1  ​Battery Type ===
765 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
700 700  
701 701  
702 -(((
703 -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.
704 -)))
768 +(% style="color:#037691" %)**AT+ SHHUM=min,max**
705 705  
706 -(((
707 -The battery is designed to last for several years depends on the actually use environment and update interval. 
708 -)))
709 709  
710 -(((
711 -The battery related documents as below:
712 -)))
771 +² When min=0, and max≠0, Alarm higher than max
713 713  
714 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
715 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
716 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
773 +² When min≠0, and max=0, Alarm lower than min
717 717  
718 -(((
719 -[[image:image-20220709101450-2.png]]
720 -)))
775 +² When min≠0 and max≠0, Alarm higher than max or lower than min
721 721  
722 722  
778 + (% style="color:blue" %)**Example:**
723 723  
724 -=== 2.5.2  Power consumption Analyze ===
780 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
725 725  
726 -(((
727 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
728 -)))
729 729  
730 -(((
731 -
732 -)))
783 +(% style="color:#037691" %)**AT+ SHTEMP=min,max**
733 733  
785 +² When min=0, and max≠0, Alarm higher than max
734 734  
735 -=== 2.5.3  ​Battery Note ===
787 +² When min≠0, and max=0, Alarm lower than min
736 736  
737 -(((
738 -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.
739 -)))
789 +² When min≠0 and max≠0, Alarm higher than max or lower than min
740 740  
741 741  
792 +**~ (% style="color:blue" %)Example:(%%)**
742 742  
743 -=== 2.5.4  Replace the battery ===
794 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
744 744  
745 745  
746 -(((
747 -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.
748 -)))
797 +== 2.6 Set the number of data to be uploaded and the recording time ==
749 749  
750 750  
751 -(((
752 -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).
753 -)))
800 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
754 754  
802 +* (% 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)
803 +* (% 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.
755 755  
805 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
756 756  
807 +[[image:image-20221009001045-1.png||height="726" width="1009"]]
808 +
809 +
810 +== 2.7 Read or Clear cached data ==
811 +
812 +
813 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
814 +
815 +* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
816 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
817 +
818 +[[image:image-20220908163102-2.png]]
819 +
820 +
821 +== 2.8 Battery & Power Consumption ==
822 +
823 +
824 +N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
825 +
826 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
827 +
828 +
757 757  = 3. ​ Access NB-IoT Module =
758 758  
831 +
759 759  (((
760 760  Users can directly access the AT command set of the NB-IoT module.
761 761  )))
... ... @@ -762,19 +762,21 @@
762 762  
763 763  (((
764 764  The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
838 +
839 +
765 765  )))
766 766  
767 767  [[image:1657333200519-600.png]]
768 768  
769 769  
770 -
771 771  = 4.  Using the AT Commands =
772 772  
773 773  == 4.1  Access AT Commands ==
774 774  
775 -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/]]
776 776  
850 +See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
777 777  
852 +
778 778  AT+<CMD>?  : Help on <CMD>
779 779  
780 780  AT+<CMD>         : Run <CMD>
... ... @@ -814,7 +814,24 @@
814 814  
815 815  AT+SERVADDR  : Server Address
816 816  
892 +AT+TR      : Get or Set record time
817 817  
894 +AT+APN     : Get or set the APN
895 +
896 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
897 +
898 +AT+DNSCFG  : Get or Set DNS Server
899 +
900 +AT+GETSENSORVALUE   : Returns the current sensor measurement
901 +
902 +AT+NOUD      : Get or Set the number of data to be uploaded
903 +
904 +AT+CDP     : Read or Clear cached data
905 +
906 +AT+SHTEMP: Get or Set alarm of temp
907 +
908 +AT+SHHUM: Get or Set alarm of moisture
909 +
818 818  (% style="color:#037691" %)**COAP Management**      
819 819  
820 820  AT+URI            : Resource parameters
... ... @@ -845,7 +845,6 @@
845 845  AT+PWORD  : Serial Access Password
846 846  
847 847  
848 -
849 849  = ​5.  FAQ =
850 850  
851 851  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -863,12 +863,11 @@
863 863  
864 864  
865 865  (((
866 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
957 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
867 867  )))
868 868  )))
869 869  
870 870  
871 -
872 872  = 6.  Trouble Shooting =
873 873  
874 874  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -883,9 +883,9 @@
883 883  
884 884  )))
885 885  
886 -
887 887  == 6.2  AT Command input doesn't work ==
888 888  
978 +
889 889  (((
890 890  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.
891 891  
... ... @@ -892,7 +892,6 @@
892 892  
893 893  )))
894 894  
895 -
896 896  = 7. ​ Order Info =
897 897  
898 898  
... ... @@ -899,11 +899,6 @@
899 899  Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
900 900  
901 901  
902 -(% class="wikigeneratedid" %)
903 -(((
904 -
905 -)))
906 -
907 907  = 8.  Packing Info =
908 908  
909 909  (((
... ... @@ -929,11 +929,14 @@
929 929  (((
930 930  
931 931  
932 -
933 933  
934 934  )))
935 935  
936 936  = 9.  Support =
937 937  
1021 +
938 938  * 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.
939 939  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
1024 +
1025 +
1026 +
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
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0