Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 130.4 >
edited by Xiaoling
on 2023/04/28 13:48
To version < 125.2 >
edited by Xiaoling
on 2022/09/09 15:51
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,8 +17,11 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 +
20 20  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21 21  
23 +(((
24 +
22 22  
23 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*.
... ... @@ -37,13 +37,20 @@
37 37  )))
38 38  
39 39  (((
43 +
44 +)))
45 +
46 +(((
40 40  ~* make sure you have NB-IoT coverage locally.
41 41  )))
42 42  
50 +
51 +)))
43 43  
44 44  [[image:1657348284168-431.png]]
45 45  
46 46  
56 +
47 47  == 1.2 ​ Features ==
48 48  
49 49  
... ... @@ -59,6 +59,7 @@
59 59  * 8500mAh Battery for long term use
60 60  
61 61  
72 +
62 62  == 1.3  Specification ==
63 63  
64 64  
... ... @@ -69,12 +69,12 @@
69 69  
70 70  (% style="color:#037691" %)**NB-IoT Spec:**
71 71  
72 -* B1 @H-FDD: 2100MHz
73 -* B3 @H-FDD: 1800MHz
74 -* B8 @H-FDD: 900MHz
75 -* B5 @H-FDD: 850MHz
76 -* B20 @H-FDD: 800MHz
77 -* B28 @H-FDD: 700MHz
83 +* - B1 @H-FDD: 2100MHz
84 +* - B3 @H-FDD: 1800MHz
85 +* - B8 @H-FDD: 900MHz
86 +* - B5 @H-FDD: 850MHz
87 +* - B20 @H-FDD: 800MHz
88 +* - B28 @H-FDD: 700MHz
78 78  
79 79  (% style="color:#037691" %)**Battery:**
80 80  
... ... @@ -85,6 +85,7 @@
85 85  * Max boost current: 2A, 1 second
86 86  
87 87  
99 +
88 88  == ​1.4  Applications ==
89 89  
90 90  
... ... @@ -99,6 +99,8 @@
99 99  ​
100 100  
101 101  
114 +
115 +
102 102  == 1.5  Pin Definitions & Switch ==
103 103  
104 104  
... ... @@ -108,6 +108,7 @@
108 108  [[image:image-20220709144723-1.png]]
109 109  
110 110  
125 +
111 111  === 1.5.1 Jumper JP2 ===
112 112  
113 113  
... ... @@ -114,18 +114,20 @@
114 114  Power on Device when put this jumper.
115 115  
116 116  
132 +
117 117  === 1.5.2 BOOT MODE / SW1 ===
118 118  
119 119  
120 120  (((
121 -**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.
137 +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.
122 122  )))
123 123  
124 124  (((
125 -**2) Flash:**  work mode, device starts to work and send out console output for further debug
141 +2) Flash: work mode, device starts to work and send out console output for further debug
126 126  )))
127 127  
128 128  
145 +
129 129  === 1.5.3 Reset Button ===
130 130  
131 131  
... ... @@ -132,18 +132,20 @@
132 132  Press to reboot the device.
133 133  
134 134  
152 +
135 135  === 1.5.4 LED ===
136 136  
137 137  
138 138  It will flash:
139 139  
140 -1.  When boot the device in flash mode
158 +1. When boot the device in flash mode
159 +1. Send an uplink packet
141 141  
142 -2.  Send an uplink packet
143 143  
144 144  
145 145  = 2.  Use N95S31B to communicate with IoT Server =
146 146  
165 +
147 147  == 2.1  How it works ==
148 148  
149 149  
... ... @@ -166,8 +166,10 @@
166 166  
167 167  )))
168 168  
188 +
169 169  == 2.2 ​ Configure the N95S31B ==
170 170  
191 +
171 171  === 2.2.1  Power On N95S31B ===
172 172  
173 173  
... ... @@ -174,9 +174,10 @@
174 174  [[image:image-20220709150546-2.png]]
175 175  
176 176  
177 -=== 2.2.2 Test Requirement ===
178 178  
199 +=== 2.2.1 Test Requirement ===
179 179  
201 +
180 180  (((
181 181  To use N95S31B in your city, make sure meet below requirements:
182 182  )))
... ... @@ -223,6 +223,7 @@
223 223  [[image:1657350625843-586.png]]
224 224  
225 225  
248 +
226 226  === 2.2.3  Insert SIM card ===
227 227  
228 228  
... ... @@ -238,6 +238,7 @@
238 238  [[image:1657351240556-536.png]]
239 239  
240 240  
264 +
241 241  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
242 242  
243 243  
... ... @@ -252,13 +252,13 @@
252 252  [[image:1657351312545-300.png]]
253 253  
254 254  
255 -(% style="color:blue" %)**Connection:**
279 +**Connection:**
256 256  
257 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
281 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
258 258  
259 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
283 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
260 260  
261 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
285 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
262 262  
263 263  
264 264  In the PC, use below serial tool settings:
... ... @@ -281,6 +281,7 @@
281 281  )))
282 282  
283 283  
308 +
284 284  === 2.2.5  Use CoAP protocol to uplink data ===
285 285  
286 286  
... ... @@ -295,10 +295,10 @@
295 295  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
296 296  )))
297 297  * (((
298 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
323 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
299 299  )))
300 300  * (((
301 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
326 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
302 302  )))
303 303  
304 304  (((
... ... @@ -317,6 +317,7 @@
317 317  [[image:1657352185396-303.png]]
318 318  
319 319  
345 +
320 320  === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
321 321  
322 322  
... ... @@ -330,18 +330,19 @@
330 330  [[image:1657352403317-397.png]]
331 331  
332 332  
359 +
333 333  === 2.2.7  Use MQTT protocol to uplink data ===
334 334  
335 335  
336 336  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
337 337  
338 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
339 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
340 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
341 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
342 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
343 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
344 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
365 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
366 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
367 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
368 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
369 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
370 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
371 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
345 345  
346 346  [[image:1657352634421-276.png]]
347 347  
... ... @@ -353,11 +353,13 @@
353 353  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.
354 354  )))
355 355  
383 +
356 356  (((
357 357  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.
358 358  )))
359 359  
360 360  
389 +
361 361  === 2.2.8  Use TCP protocol to uplink data ===
362 362  
363 363  
... ... @@ -372,6 +372,7 @@
372 372  [[image:1657352914475-252.png]]
373 373  
374 374  
404 +
375 375  === 2.2.9  Change Update Interval ===
376 376  
377 377  
... ... @@ -392,6 +392,7 @@
392 392  )))
393 393  
394 394  
425 +
395 395  == 2.3  Uplink Payload ==
396 396  
397 397  
... ... @@ -405,7 +405,7 @@
405 405  )))
406 406  
407 407  (((
408 - (% 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.
439 + (% 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.
409 409  )))
410 410  
411 411  
... ... @@ -434,11 +434,13 @@
434 434  **By default, the device will send an uplink message every 1 hour.**
435 435  
436 436  
468 +
437 437  
438 438  )))
439 439  
440 440  === 2.3.1  Payload Analyze ===
441 441  
474 +
442 442  ==== 2.3.1.1  Before Firmware v1.2 ====
443 443  
444 444  
... ... @@ -445,9 +445,11 @@
445 445  N95S31B uplink payload includes in total 21 bytes
446 446  
447 447  
448 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
449 -|=(% 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**
450 -|(% 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" %)(((
481 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %)
482 +|=(% style="width: 60px;" %)(((
483 +**Size(bytes)**
484 +)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 174px;" %)5|=(% style="width: 106px;" %)**2**|=(% style="width: 85px;" %)**2**
485 +|(% 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:174px" %)(((
451 451  (((
452 452  Reserve/ Same as NBSN95 CFGMOD=1
453 453  )))
... ... @@ -455,7 +455,7 @@
455 455  (((
456 456  No function here.
457 457  )))
458 -)))|(% style="width:102px" %)(((
493 +)))|(% style="width:106px" %)(((
459 459  (((
460 460  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
461 461  )))
... ... @@ -463,7 +463,7 @@
463 463  (((
464 464  By SHT31
465 465  )))
466 -)))|(% style="width:81px" %)(((
501 +)))|(% style="width:85px" %)(((
467 467  (((
468 468  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
469 469  )))
... ... @@ -485,85 +485,62 @@
485 485  [[image:1657354294009-643.png]]
486 486  
487 487  
488 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
523 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
489 489  
490 -**where:**
525 +* Device ID:  0x724031607457 = 724031607457
491 491  
492 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
527 +* Version:  0x006e=110=1.1.0
493 493  
494 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
529 +* BAT:  0x0ccd = 3277 mV = 3.277V
495 495  
496 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
531 +* Signal:  0x1b = 27
497 497  
498 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
533 +* Model:  0x01 = 1
499 499  
500 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
535 +* 0x00dc000ccc= reserve, ignore in N95S31B
501 501  
502 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
537 +* Temperature by SHT31:  0x00e1 = 225 = 22.5 °C
503 503  
504 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
539 +* Humidity by SHT31:  0x0186 = 390 = 39.0 %rh
505 505  
506 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
507 -
508 508  (((
509 509  
510 510  
544 +
511 511  
512 512  )))
513 513  
514 514  ==== 2.3.1.2 Since Firmware v1.2 ====
515 515  
516 -
517 517  In this mode, uplink payload includes 91 bytes in total by default.
518 518  
519 519  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.
520 520  
554 +|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
555 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
521 521  
522 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
523 -|=(% 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**
524 -|=(% 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 .....
525 -
526 526  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
527 527  
528 -
529 529  [[image:image-20220908154949-1.png]]
530 530  
531 -
532 532  The payload is ASCII string, representative same HEX:
533 533  
534 -**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__ **
563 +0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
535 535  
536 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
565 +* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
566 +* (% style="color:blue" %) Version: 0x000c=120=1.2
567 +* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
568 +* (% style="color:red" %) Singal: 0x0c = 12
569 +* (% style="color:blue" %) Mod: 0x01 = 1
570 +* TemDS18B20: 0x0000= 0 = 0
571 +* (% style="color:green" %)Interrupt: 0x00= 0
572 +* (% style="color:green" %)adc: 0x0030= 48
573 +* SHTTEM: 0x0114= 276 = 27.6
574 +* SHTHUM:0x0231 =561=56.1%
575 +* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
576 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
577 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
537 537  
538 -**where:**
539 -
540 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
541 -
542 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
543 -
544 -* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
545 -
546 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
547 -
548 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
549 -
550 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
551 -
552 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
553 -
554 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
555 -
556 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
557 -
558 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
559 -
560 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
561 -
562 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
563 -
564 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
565 -
566 -
567 567  === 2.3.2  Device ID ===
568 568  
569 569  
... ... @@ -573,12 +573,10 @@
573 573  
574 574  (((
575 575  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
576 -
577 -
578 578  )))
579 579  
580 580  (((
581 -(% style="color:blue" %)**Example:**
591 +**Example:**
582 582  )))
583 583  
584 584  (((
... ... @@ -586,21 +586,20 @@
586 586  )))
587 587  
588 588  (((
589 -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.
599 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
590 590  
591 591  
592 592  )))
593 593  
594 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
604 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
595 595  
596 596  
597 597  By default, the Device ID equal to the last 15 bits of IMEI.
598 598  
599 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
609 +User can use **AT+DEUI** to set Device ID
600 600  
611 +**Example:**
601 601  
602 -(% style="color:blue" %)**Example:**
603 -
604 604  AT+DEUI=868411056754138
605 605  
606 606  
... ... @@ -612,11 +612,11 @@
612 612  )))
613 613  
614 614  (((
615 -**Higher byte:** Specify hardware version: always 0x00 for N95S31B
624 +Higher byte: Specify hardware version: always 0x00 for N95S31B
616 616  )))
617 617  
618 618  (((
619 -**Lower byte:** Specify the software version: 0x6E=110, means firmware version 110
628 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
620 620  )))
621 621  
622 622  (((
... ... @@ -631,6 +631,7 @@
631 631  
632 632  )))
633 633  
643 +
634 634  === 2.3.4  Battery Info ===
635 635  
636 636  
... ... @@ -643,6 +643,7 @@
643 643  )))
644 644  
645 645  
656 +
646 646  === 2.3.5  Signal Strength ===
647 647  
648 648  
... ... @@ -675,6 +675,7 @@
675 675  )))
676 676  
677 677  
689 +
678 678  === 2.3.6  Temperature & Humidity ===
679 679  
680 680  
... ... @@ -693,6 +693,7 @@
693 693  Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
694 694  
695 695  
708 +
696 696  == 2.4  Downlink Payload ==
697 697  
698 698  
... ... @@ -745,15 +745,12 @@
745 745  )))
746 746  
747 747  
748 -== 2.5  Humidity and Temperature alarm function ==
761 +== 2.5 Humidity and Temperature alarm function ==
749 749  
763 +➢ AT Command:
750 750  
751 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
765 +AT+ SHHUM=min,max
752 752  
753 -
754 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
755 -
756 -
757 757  ² When min=0, and max≠0, Alarm higher than max
758 758  
759 759  ² When min≠0, and max=0, Alarm lower than min
... ... @@ -760,13 +760,12 @@
760 760  
761 761  ² When min≠0 and max≠0, Alarm higher than max or lower than min
762 762  
773 +Example:
763 763  
764 - (% style="color:blue" %)**Example:**
765 -
766 766  AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
767 767  
768 768  
769 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
778 +AT+ SHTEMP=min,max
770 770  
771 771  ² When min=0, and max≠0, Alarm higher than max
772 772  
... ... @@ -774,44 +774,91 @@
774 774  
775 775  ² When min≠0 and max≠0, Alarm higher than max or lower than min
776 776  
786 +Example:
777 777  
778 -**~ (% style="color:blue" %)Example:(%%)**
779 -
780 780  AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
781 781  
782 -
783 783  == 2.6 Set the number of data to be uploaded and the recording time ==
784 784  
792 +➢ AT Command:
785 785  
786 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
794 +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)
787 787  
788 -* (% 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)
789 -* (% 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.
796 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
790 790  
791 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
798 +== 2.7 Read or Clear cached data ==
792 792  
793 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
800 +➢ AT Command:
794 794  
802 +AT+CDP ~/~/ Read cached data
795 795  
796 -== 2.7 Read or Clear cached data ==
804 +[[image:image-20220908163102-2.png]]
797 797  
806 +AT+CDP=0 ~/~/ Clear cached data
798 798  
799 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
808 +== 2.8  ​Battery Analysis ==
800 800  
801 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
802 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
803 803  
804 -[[image:image-20220908163102-2.png]]
811 +=== 2.8.1  ​Battery Type ===
805 805  
806 806  
807 -== 2.8 Battery & Power Consumption ==
814 +(((
815 +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.
816 +)))
808 808  
818 +(((
819 +The battery is designed to last for several years depends on the actually use environment and update interval. 
820 +)))
809 809  
810 -N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
822 +(((
823 +The battery related documents as below:
824 +)))
811 811  
812 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
826 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
827 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
828 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
813 813  
830 +(((
831 +[[image:image-20220709101450-2.png]]
832 +)))
814 814  
834 +
835 +
836 +=== 2.8.2  Power consumption Analyze ===
837 +
838 +
839 +(((
840 +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.
841 +)))
842 +
843 +(((
844 +
845 +)))
846 +
847 +
848 +=== 2.8.3  ​Battery Note ===
849 +
850 +
851 +(((
852 +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.
853 +)))
854 +
855 +
856 +
857 +=== 2.8.4  Replace the battery ===
858 +
859 +
860 +(((
861 +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.
862 +)))
863 +
864 +
865 +(((
866 +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).
867 +)))
868 +
869 +
870 +
815 815  = 3. ​ Access NB-IoT Module =
816 816  
817 817  
... ... @@ -828,8 +828,10 @@
828 828  [[image:1657333200519-600.png]]
829 829  
830 830  
887 +
831 831  = 4.  Using the AT Commands =
832 832  
890 +
833 833  == 4.1  Access AT Commands ==
834 834  
835 835  
... ... @@ -923,8 +923,10 @@
923 923  AT+PWORD  : Serial Access Password
924 924  
925 925  
984 +
926 926  = ​5.  FAQ =
927 927  
987 +
928 928  == 5.1 ​ How to Upgrade Firmware ==
929 929  
930 930  
... ... @@ -937,14 +937,18 @@
937 937  )))
938 938  
939 939  (((
940 -Firmware Download：[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]]
1000 +
941 941  
1002 +(((
942 942  (% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
943 943  )))
1005 +)))
944 944  
945 945  
1008 +
946 946  = 6.  Trouble Shooting =
947 947  
1011 +
948 948  == 6.1  ​Connection problem when uploading firmware ==
949 949  
950 950  
... ... @@ -952,7 +952,12 @@
952 952  **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]]
953 953  )))
954 954  
1019 +(% class="wikigeneratedid" %)
1020 +(((
1021 +
1022 +)))
955 955  
1024 +
956 956  == 6.2  AT Command input doesn't work ==
957 957  
958 958  
... ... @@ -962,12 +962,7 @@
962 962  
963 963  )))
964 964  
965 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
966 966  
967 -
968 -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]]//**.
969 -
970 -
971 971  = 7. ​ Order Info =
972 972  
973 973  
... ... @@ -974,6 +974,11 @@
974 974  Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
975 975  
976 976  
1041 +(% class="wikigeneratedid" %)
1042 +(((
1043 +
1044 +)))
1045 +
977 977  = 8.  Packing Info =
978 978  
979 979  (((
... ... @@ -996,13 +996,15 @@
996 996  * Weight / pcs : 180g
997 997  )))
998 998  
1068 +(((
1069 +
999 999  
1000 1000  
1072 +
1073 +)))
1074 +
1001 1001  = 9.  Support =
1002 1002  
1003 1003  
1004 1004  * 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.
1005 -
1006 1006  * 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]]
1007 -
1008 -
image-20221009001045-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0