Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 129.6 >
edited by Xiaoling
on 2022/10/25 17:04
To version < 119.1 >
edited by Xiaoling
on 2022/07/12 17:49
>
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  (((
... ... @@ -56,7 +56,6 @@
56 56  
57 57  == 1.2 ​ Features ==
58 58  
59 -
60 60  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
61 61  * Monitor Temperature & Humidity via SHT31
62 62  * AT Commands to change parameters
... ... @@ -68,6 +68,8 @@
68 68  * Micro SIM card slot for NB-IoT SIM
69 69  * 8500mAh Battery for long term use
70 70  
69 +
70 +
71 71  == 1.3  Specification ==
72 72  
73 73  
... ... @@ -93,9 +93,10 @@
93 93  * Max continuously current: 130mA
94 94  * Max boost current: 2A, 1 second
95 95  
96 -== ​1.4  Applications ==
97 97  
98 98  
98 +== ​1.4  Applications ==
99 +
99 99  * Smart Buildings & Home Automation
100 100  * Logistics and Supply Chain Management
101 101  * Smart Metering
... ... @@ -107,20 +107,15 @@
107 107  ​
108 108  
109 109  
110 -
111 111  == 1.5  Pin Definitions & Switch ==
112 112  
113 -
114 114  N95S31B use the mother board from NBSN95 which as below.
115 115  
116 -
117 117  [[image:image-20220709144723-1.png]]
118 118  
119 119  
120 -
121 121  === 1.5.1 Jumper JP2 ===
122 122  
123 -
124 124  Power on Device when put this jumper.
125 125  
126 126  
... ... @@ -127,13 +127,12 @@
127 127  
128 128  === 1.5.2 BOOT MODE / SW1 ===
129 129  
130 -
131 131  (((
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.
127 +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.
133 133  )))
134 134  
135 135  (((
136 -**2) Flash:**  work mode, device starts to work and send out console output for further debug
131 +2) Flash: work mode, device starts to work and send out console output for further debug
137 137  )))
138 138  
139 139  
... ... @@ -140,7 +140,6 @@
140 140  
141 141  === 1.5.3 Reset Button ===
142 142  
143 -
144 144  Press to reboot the device.
145 145  
146 146  
... ... @@ -147,18 +147,15 @@
147 147  
148 148  === 1.5.4 LED ===
149 149  
150 -
151 151  It will flash:
152 152  
153 -1.  When boot the device in flash mode
146 +1. When boot the device in flash mode
147 +1. Send an uplink packet
154 154  
155 -2.  Send an uplink packet
156 156  
157 157  
158 -
159 159  = 2.  Use N95S31B to communicate with IoT Server =
160 160  
161 -
162 162  == 2.1  How it works ==
163 163  
164 164  
... ... @@ -191,7 +191,6 @@
191 191  [[image:image-20220709150546-2.png]]
192 192  
193 193  
194 -
195 195  === 2.2.1 Test Requirement ===
196 196  
197 197  
... ... @@ -244,7 +244,6 @@
244 244  
245 245  === 2.2.3  Insert SIM card ===
246 246  
247 -
248 248  (((
249 249  Insert the NB-IoT Card get from your provider.
250 250  )))
... ... @@ -260,27 +260,23 @@
260 260  
261 261  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
262 262  
263 -
264 264  (((
265 265  (((
266 266  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.
267 -
268 -
269 269  )))
270 270  )))
271 271  
272 272  [[image:1657351312545-300.png]]
273 273  
260 +**Connection:**
274 274  
275 -(% style="color:blue" %)**Connection:**
262 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
276 276  
277 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
264 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
278 278  
279 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
266 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
280 280  
281 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
282 282  
283 -
284 284  In the PC, use below serial tool settings:
285 285  
286 286  * Baud:  (% style="color:green" %)**9600**
... ... @@ -295,9 +295,8 @@
295 295  
296 296  [[image:1657329814315-101.png]]
297 297  
298 -
299 299  (((
300 -(% 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]]**
284 +(% 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/]]
301 301  )))
302 302  
303 303  
... ... @@ -304,10 +304,9 @@
304 304  
305 305  === 2.2.5  Use CoAP protocol to uplink data ===
306 306  
291 +(% 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/]]
307 307  
308 -(% 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/]]**
309 309  
310 -
311 311  (((
312 312  **Use below commands:**
313 313  )))
... ... @@ -316,10 +316,10 @@
316 316  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
317 317  )))
318 318  * (((
319 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
302 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
320 320  )))
321 321  * (((
322 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
305 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
323 323  )))
324 324  
325 325  (((
... ... @@ -355,16 +355,15 @@
355 355  
356 356  === 2.2.7  Use MQTT protocol to uplink data ===
357 357  
358 -
359 359  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
360 360  
361 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
362 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
363 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
364 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
365 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
366 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
367 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
343 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
344 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
345 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
346 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
347 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
348 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
349 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
368 368  
369 369  [[image:1657352634421-276.png]]
370 370  
... ... @@ -371,7 +371,6 @@
371 371  
372 372  [[image:1657352645687-385.png]]
373 373  
374 -
375 375  (((
376 376  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.
377 377  )))
... ... @@ -385,7 +385,6 @@
385 385  
386 386  === 2.2.8  Use TCP protocol to uplink data ===
387 387  
388 -
389 389  This feature is supported since firmware version v110
390 390  
391 391  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -400,7 +400,6 @@
400 400  
401 401  === 2.2.9  Change Update Interval ===
402 402  
403 -
404 404  User can use below command to change the (% style="color:green" %)**uplink interval**.
405 405  
406 406  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -409,21 +409,13 @@
409 409  
410 410  )))
411 411  
412 -(((
413 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
414 -)))
415 415  
416 -(((
417 -(% 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).**
418 -)))
419 419  
420 -
421 -
422 422  == 2.3  Uplink Payload ==
423 423  
424 424  
425 425  (((
426 -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.
397 +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.
427 427  )))
428 428  
429 429  
... ... @@ -455,10 +455,10 @@
455 455  
456 456  (% style="color:red" %)
457 457  1. (((
458 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
429 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
459 459  )))
460 460  1. (((
461 -**By default, the device will send an uplink message every 1 hour.**
432 +By default, the device will send an uplink message every 1 hour.
462 462  
463 463  
464 464  
... ... @@ -467,18 +467,14 @@
467 467  
468 468  === 2.3.1  Payload Analyze ===
469 469  
470 -
471 -==== 2.3.1.1  Before Firmware v1.2 ====
472 -
473 -
474 474  N95S31B uplink payload includes in total 21 bytes
475 475  
476 476  
477 -(% border="1.5" cellspacing="0" style="background-color:#ffffcc; color:green; width:520px" %)
478 -|=(% scope="row" style="width: 50px;" %)(((
444 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
445 +|=(% style="width: 60px;" %)(((
479 479  **Size(bytes)**
480 -)))|=(% style="width: 40px;" %)**6**|=(% style="width: 20px;" %)2|=(% style="width: 20px;" %)**2**|=(% style="width: 60px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 100px;" %)5|=(% style="width: 102px;" %)**2**|=(% style="width: 81px;" %)**2**
481 -|=(% 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" %)(((
447 +)))|=(% 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**
448 +|(% 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" %)(((
482 482  (((
483 483  Reserve/ Same as NBSN95 CFGMOD=1
484 484  )))
... ... @@ -486,7 +486,7 @@
486 486  (((
487 487  No function here.
488 488  )))
489 -)))|(% style="width:102px" %)(((
456 +)))|(% style="width:77px" %)(((
490 490  (((
491 491  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
492 492  )))
... ... @@ -494,7 +494,7 @@
494 494  (((
495 495  By SHT31
496 496  )))
497 -)))|(% style="width:81px" %)(((
464 +)))|(% style="width:80px" %)(((
498 498  (((
499 499  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
500 500  )))
... ... @@ -505,8 +505,6 @@
505 505  )))
506 506  
507 507  (((
508 -
509 -
510 510  (((
511 511  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
512 512  )))
... ... @@ -516,88 +516,29 @@
516 516  [[image:1657354294009-643.png]]
517 517  
518 518  
519 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
484 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
520 520  
521 -**where:**
486 +* Device ID: 0x724031607457 = 724031607457
487 +* Version: 0x006e=110=1.1.0
522 522  
523 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
489 +* BAT: 0x0ccd = 3277 mV = 3.277V
490 +* Signal: 0x1b = 27
491 +* Model: 0x01 = 1
492 +* 0x00dc000ccc= reserve, ignore in N95S31B
493 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
494 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
524 524  
525 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
526 -
527 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
528 -
529 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
530 -
531 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
532 -
533 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
534 -
535 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
536 -
537 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
538 -
539 539  (((
540 540  
498 +)))
541 541  
542 -
500 +(((
543 543  
544 544  )))
545 545  
546 -==== 2.3.1.2 Since Firmware v1.2 ====
547 547  
548 -
549 -In this mode, uplink payload includes 91 bytes in total by default.
550 -
551 -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.
552 -
553 -
554 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
555 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**2**|(% style="width:50px" %)**1**|(% style="width:30px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:50px" %)**4**
556 -|=(% 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 .....
557 -
558 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
559 -
560 -
561 -[[image:image-20220908154949-1.png]]
562 -
563 -
564 -The payload is ASCII string, representative same HEX:
565 -
566 -**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__ **
567 -
568 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
569 -
570 -**where:**
571 -
572 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
573 -
574 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
575 -
576 -* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
577 -
578 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
579 -
580 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
581 -
582 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
583 -
584 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
585 -
586 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
587 -
588 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
589 -
590 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
591 -
592 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
593 -
594 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
595 -
596 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
597 -
598 598  === 2.3.2  Device ID ===
599 599  
600 -
601 601  (((
602 602  By default, the Device ID equal to the last 6 bytes of IMEI.
603 603  )))
... ... @@ -604,12 +604,10 @@
604 604  
605 605  (((
606 606  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
607 -
608 -
609 609  )))
610 610  
611 611  (((
612 -(% style="color:blue" %)**Example:**
516 +**Example:**
613 613  )))
614 614  
615 615  (((
... ... @@ -617,28 +617,13 @@
617 617  )))
618 618  
619 619  (((
620 -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.
621 -
622 -
524 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
623 623  )))
624 624  
625 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
626 626  
627 627  
628 -By default, the Device ID equal to the last 15 bits of IMEI.
629 -
630 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
631 -
632 -
633 -(% style="color:blue" %)**Example:**
634 -
635 -AT+DEUI=868411056754138
636 -
637 -
638 -
639 639  === 2.3.3  Version Info ===
640 640  
641 -
642 642  (((
643 643  These bytes include the hardware and software version.
644 644  )))
... ... @@ -666,7 +666,6 @@
666 666  
667 667  === 2.3.4  Battery Info ===
668 668  
669 -
670 670  (((
671 671  Ex1: 0x0B45 = 2885mV
672 672  )))
... ... @@ -679,7 +679,6 @@
679 679  
680 680  === 2.3.5  Signal Strength ===
681 681  
682 -
683 683  (((
684 684  NB-IoT Network signal Strength.
685 685  )))
... ... @@ -712,7 +712,6 @@
712 712  
713 713  === 2.3.6  Temperature & Humidity ===
714 714  
715 -
716 716  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
717 717  
718 718  [[image:image-20220709161741-3.png]]
... ... @@ -731,7 +731,6 @@
731 731  
732 732  == 2.4  Downlink Payload ==
733 733  
734 -
735 735  By default, N95S31B prints the downlink payload to console port.
736 736  
737 737  [[image:image-20220709100028-1.png]]
... ... @@ -782,74 +782,11 @@
782 782  
783 783  
784 784  
785 -== 2.5  Humidity and Temperature alarm function ==
670 +== 2.5  ​Battery Analysis ==
786 786  
672 +=== 2.5.1  ​Battery Type ===
787 787  
788 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
789 789  
790 -
791 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
792 -
793 -
794 -² When min=0, and max≠0, Alarm higher than max
795 -
796 -² When min≠0, and max=0, Alarm lower than min
797 -
798 -² When min≠0 and max≠0, Alarm higher than max or lower than min
799 -
800 -
801 - (% style="color:blue" %)**Example:**
802 -
803 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
804 -
805 -
806 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
807 -
808 -² When min=0, and max≠0, Alarm higher than max
809 -
810 -² When min≠0, and max=0, Alarm lower than min
811 -
812 -² When min≠0 and max≠0, Alarm higher than max or lower than min
813 -
814 -
815 -**~ (% style="color:blue" %)Example:(%%)**
816 -
817 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
818 -
819 -
820 -
821 -== 2.6 Set the number of data to be uploaded and the recording time ==
822 -
823 -
824 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
825 -
826 -* (% 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)
827 -* (% 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.
828 -
829 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
830 -
831 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
832 -
833 -
834 -
835 -== 2.7 Read or Clear cached data ==
836 -
837 -
838 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
839 -
840 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
841 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
842 -
843 -[[image:image-20220908163102-2.png]]
844 -
845 -
846 -
847 -== 2.8  ​Battery Analysis ==
848 -
849 -
850 -=== 2.8.1  ​Battery Type ===
851 -
852 -
853 853  (((
854 854  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.
855 855  )))
... ... @@ -872,11 +872,10 @@
872 872  
873 873  
874 874  
875 -=== 2.8.2  Power consumption Analyze ===
697 +=== 2.5.2  Power consumption Analyze ===
876 876  
877 -
878 878  (((
879 -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.
700 +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.
880 880  )))
881 881  
882 882  (((
... ... @@ -884,9 +884,8 @@
884 884  )))
885 885  
886 886  
887 -=== 2.8.3  ​Battery Note ===
708 +=== 2.5.3  ​Battery Note ===
888 888  
889 -
890 890  (((
891 891  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.
892 892  )))
... ... @@ -893,7 +893,7 @@
893 893  
894 894  
895 895  
896 -=== 2.8.4  Replace the battery ===
716 +=== 2.5.4  Replace the battery ===
897 897  
898 898  
899 899  (((
... ... @@ -909,7 +909,6 @@
909 909  
910 910  = 3. ​ Access NB-IoT Module =
911 911  
912 -
913 913  (((
914 914  Users can directly access the AT command set of the NB-IoT module.
915 915  )))
... ... @@ -916,8 +916,6 @@
916 916  
917 917  (((
918 918  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/]] 
919 -
920 -
921 921  )))
922 922  
923 923  [[image:1657333200519-600.png]]
... ... @@ -926,13 +926,11 @@
926 926  
927 927  = 4.  Using the AT Commands =
928 928  
929 -
930 930  == 4.1  Access AT Commands ==
931 931  
748 +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/]]
932 932  
933 -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]]
934 934  
935 -
936 936  AT+<CMD>?  : Help on <CMD>
937 937  
938 938  AT+<CMD>         : Run <CMD>
... ... @@ -972,24 +972,7 @@
972 972  
973 973  AT+SERVADDR  : Server Address
974 974  
975 -AT+TR      : Get or Set record time
976 976  
977 -AT+APN     : Get or set the APN
978 -
979 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
980 -
981 -AT+DNSCFG  : Get or Set DNS Server
982 -
983 -AT+GETSENSORVALUE   : Returns the current sensor measurement
984 -
985 -AT+NOUD      : Get or Set the number of data to be uploaded
986 -
987 -AT+CDP     : Read or Clear cached data
988 -
989 -AT+SHTEMP: Get or Set alarm of temp
990 -
991 -AT+SHHUM: Get or Set alarm of moisture
992 -
993 993  (% style="color:#037691" %)**COAP Management**      
994 994  
995 995  AT+URI            : Resource parameters
... ... @@ -1023,7 +1023,6 @@
1023 1023  
1024 1024  = ​5.  FAQ =
1025 1025  
1026 -
1027 1027  == 5.1 ​ How to Upgrade Firmware ==
1028 1028  
1029 1029  
... ... @@ -1039,7 +1039,7 @@
1039 1039  
1040 1040  
1041 1041  (((
1042 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
839 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
1043 1043  )))
1044 1044  )))
1045 1045  
... ... @@ -1047,7 +1047,6 @@
1047 1047  
1048 1048  = 6.  Trouble Shooting =
1049 1049  
1050 -
1051 1051  == 6.1  ​Connection problem when uploading firmware ==
1052 1052  
1053 1053  
... ... @@ -1063,7 +1063,6 @@
1063 1063  
1064 1064  == 6.2  AT Command input doesn't work ==
1065 1065  
1066 -
1067 1067  (((
1068 1068  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.
1069 1069  
... ... @@ -1113,6 +1113,5 @@
1113 1113  
1114 1114  = 9.  Support =
1115 1115  
1116 -
1117 1117  * 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.
1118 1118  * 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]]
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

Applications

Navigation

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