<
From version < 129.3 >
edited by Xiaoling
on 2022/10/15 10:08
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
... ... @@ -99,7 +99,6 @@
99 99  
100 100  == ​1.4  Applications ==
101 101  
102 -
103 103  * Smart Buildings & Home Automation
104 104  * Logistics and Supply Chain Management
105 105  * Smart Metering
... ... @@ -111,20 +111,15 @@
111 111  ​
112 112  
113 113  
114 -
115 115  == 1.5  Pin Definitions & Switch ==
116 116  
117 -
118 118  N95S31B use the mother board from NBSN95 which as below.
119 119  
120 -
121 121  [[image:image-20220709144723-1.png]]
122 122  
123 123  
124 -
125 125  === 1.5.1 Jumper JP2 ===
126 126  
127 -
128 128  Power on Device when put this jumper.
129 129  
130 130  
... ... @@ -131,13 +131,12 @@
131 131  
132 132  === 1.5.2 BOOT MODE / SW1 ===
133 133  
134 -
135 135  (((
136 -**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.
137 137  )))
138 138  
139 139  (((
140 -**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
141 141  )))
142 142  
143 143  
... ... @@ -144,7 +144,6 @@
144 144  
145 145  === 1.5.3 Reset Button ===
146 146  
147 -
148 148  Press to reboot the device.
149 149  
150 150  
... ... @@ -151,18 +151,15 @@
151 151  
152 152  === 1.5.4 LED ===
153 153  
154 -
155 155  It will flash:
156 156  
157 -1.  When boot the device in flash mode
146 +1. When boot the device in flash mode
147 +1. Send an uplink packet
158 158  
159 -2.  Send an uplink packet
160 160  
161 161  
162 -
163 163  = 2.  Use N95S31B to communicate with IoT Server =
164 164  
165 -
166 166  == 2.1  How it works ==
167 167  
168 168  
... ... @@ -195,7 +195,6 @@
195 195  [[image:image-20220709150546-2.png]]
196 196  
197 197  
198 -
199 199  === 2.2.1 Test Requirement ===
200 200  
201 201  
... ... @@ -248,7 +248,6 @@
248 248  
249 249  === 2.2.3  Insert SIM card ===
250 250  
251 -
252 252  (((
253 253  Insert the NB-IoT Card get from your provider.
254 254  )))
... ... @@ -264,18 +264,14 @@
264 264  
265 265  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
266 266  
267 -
268 268  (((
269 269  (((
270 270  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.
271 -
272 -
273 273  )))
274 274  )))
275 275  
276 276  [[image:1657351312545-300.png]]
277 277  
278 -
279 279  **Connection:**
280 280  
281 281   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -299,9 +299,8 @@
299 299  
300 300  [[image:1657329814315-101.png]]
301 301  
302 -
303 303  (((
304 -(% 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/]]
305 305  )))
306 306  
307 307  
... ... @@ -308,10 +308,9 @@
308 308  
309 309  === 2.2.5  Use CoAP protocol to uplink data ===
310 310  
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/]]
311 311  
312 -(% 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/]]**
313 313  
314 -
315 315  (((
316 316  **Use below commands:**
317 317  )))
... ... @@ -320,10 +320,10 @@
320 320  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
321 321  )))
322 322  * (((
323 -(% 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
324 324  )))
325 325  * (((
326 -(% 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
327 327  )))
328 328  
329 329  (((
... ... @@ -359,16 +359,15 @@
359 359  
360 360  === 2.2.7  Use MQTT protocol to uplink data ===
361 361  
362 -
363 363  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
364 364  
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
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
372 372  
373 373  [[image:1657352634421-276.png]]
374 374  
... ... @@ -375,7 +375,6 @@
375 375  
376 376  [[image:1657352645687-385.png]]
377 377  
378 -
379 379  (((
380 380  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.
381 381  )))
... ... @@ -389,7 +389,6 @@
389 389  
390 390  === 2.2.8  Use TCP protocol to uplink data ===
391 391  
392 -
393 393  This feature is supported since firmware version v110
394 394  
395 395  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -404,7 +404,6 @@
404 404  
405 405  === 2.2.9  Change Update Interval ===
406 406  
407 -
408 408  User can use below command to change the (% style="color:green" %)**uplink interval**.
409 409  
410 410  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -413,21 +413,13 @@
413 413  
414 414  )))
415 415  
416 -(((
417 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
418 -)))
419 419  
420 -(((
421 -(% 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).**
422 -)))
423 423  
424 -
425 -
426 426  == 2.3  Uplink Payload ==
427 427  
428 428  
429 429  (((
430 -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.
431 431  )))
432 432  
433 433  
... ... @@ -459,10 +459,10 @@
459 459  
460 460  (% style="color:red" %)
461 461  1. (((
462 -**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"]].
463 463  )))
464 464  1. (((
465 -**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.
466 466  
467 467  
468 468  
... ... @@ -471,18 +471,14 @@
471 471  
472 472  === 2.3.1  Payload Analyze ===
473 473  
474 -
475 -==== 2.3.1.1  Before Firmware v1.2 ====
476 -
477 -
478 478  N95S31B uplink payload includes in total 21 bytes
479 479  
480 480  
481 -(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:745px" %)
444 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
482 482  |=(% style="width: 60px;" %)(((
483 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: 162px;" %)5|=(% style="width: 102px;" %)**2**|=(% style="width: 81px;" %)**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: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" %)(((
486 486  (((
487 487  Reserve/ Same as NBSN95 CFGMOD=1
488 488  )))
... ... @@ -490,7 +490,7 @@
490 490  (((
491 491  No function here.
492 492  )))
493 -)))|(% style="width:102px" %)(((
456 +)))|(% style="width:77px" %)(((
494 494  (((
495 495  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
496 496  )))
... ... @@ -498,7 +498,7 @@
498 498  (((
499 499  By SHT31
500 500  )))
501 -)))|(% style="width:81px" %)(((
464 +)))|(% style="width:80px" %)(((
502 502  (((
503 503  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
504 504  )))
... ... @@ -509,8 +509,6 @@
509 509  )))
510 510  
511 511  (((
512 -
513 -
514 514  (((
515 515  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
516 516  )))
... ... @@ -520,90 +520,29 @@
520 520  [[image:1657354294009-643.png]]
521 521  
522 522  
523 -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:
524 524  
525 -**where:**
486 +* Device ID: 0x724031607457 = 724031607457
487 +* Version: 0x006e=110=1.1.0
526 526  
527 -* (% 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
528 528  
529 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
530 -
531 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
532 -
533 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
534 -
535 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
536 -
537 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
538 -
539 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
540 -
541 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
542 -
543 543  (((
544 544  
498 +)))
545 545  
546 -
500 +(((
547 547  
548 548  )))
549 549  
550 -==== 2.3.1.2 Since Firmware v1.2 ====
551 551  
552 -
553 -In this mode, uplink payload includes 91 bytes in total by default.
554 -
555 -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.
556 -
557 -
558 -(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
559 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:47px" %)**2**|(% style="width:124px" %)**1**|(% style="width:56px" %)**1**|(% style="width:109px" %)**2**|(% style="width:80px" %)**1**|(% style="width:51px" %)**2**|(% style="width:79px" %)**2**|(% style="width:84px" %)**2**|(% style="width:100px" %)**4**|(% style="width:76px" %)**2**|(% style="width:81px" %)**2**|(% style="width:121px" %)**4**
560 -|(% 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 .....
561 -
562 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
563 -
564 -
565 -[[image:image-20220908154949-1.png]]
566 -
567 -
568 -The payload is ASCII string, representative same HEX:
569 -
570 -**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__ **
571 -
572 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
573 -
574 -**where:**
575 -
576 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
577 -
578 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
579 -
580 -* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
581 -
582 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
583 -
584 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
585 -
586 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
587 -
588 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
589 -
590 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
591 -
592 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
593 -
594 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
595 -
596 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
597 -
598 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
599 -
600 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
601 -
602 -
603 -
604 604  === 2.3.2  Device ID ===
605 605  
606 -
607 607  (((
608 608  By default, the Device ID equal to the last 6 bytes of IMEI.
609 609  )))
... ... @@ -610,12 +610,10 @@
610 610  
611 611  (((
612 612  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
613 -
614 -
615 615  )))
616 616  
617 617  (((
618 -(% style="color:blue" %)**Example:**
516 +**Example:**
619 619  )))
620 620  
621 621  (((
... ... @@ -623,28 +623,13 @@
623 623  )))
624 624  
625 625  (((
626 -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.
627 -
628 -
524 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
629 629  )))
630 630  
631 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
632 632  
633 633  
634 -By default, the Device ID equal to the last 15 bits of IMEI.
635 -
636 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
637 -
638 -
639 -(% style="color:blue" %)**Example:**
640 -
641 -AT+DEUI=868411056754138
642 -
643 -
644 -
645 645  === 2.3.3  Version Info ===
646 646  
647 -
648 648  (((
649 649  These bytes include the hardware and software version.
650 650  )))
... ... @@ -672,7 +672,6 @@
672 672  
673 673  === 2.3.4  Battery Info ===
674 674  
675 -
676 676  (((
677 677  Ex1: 0x0B45 = 2885mV
678 678  )))
... ... @@ -685,7 +685,6 @@
685 685  
686 686  === 2.3.5  Signal Strength ===
687 687  
688 -
689 689  (((
690 690  NB-IoT Network signal Strength.
691 691  )))
... ... @@ -718,7 +718,6 @@
718 718  
719 719  === 2.3.6  Temperature & Humidity ===
720 720  
721 -
722 722  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
723 723  
724 724  [[image:image-20220709161741-3.png]]
... ... @@ -737,7 +737,6 @@
737 737  
738 738  == 2.4  Downlink Payload ==
739 739  
740 -
741 741  By default, N95S31B prints the downlink payload to console port.
742 742  
743 743  [[image:image-20220709100028-1.png]]
... ... @@ -788,74 +788,11 @@
788 788  
789 789  
790 790  
791 -== 2.5  Humidity and Temperature alarm function ==
670 +== 2.5  ​Battery Analysis ==
792 792  
672 +=== 2.5.1  ​Battery Type ===
793 793  
794 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
795 795  
796 -
797 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
798 -
799 -
800 -² When min=0, and max≠0, Alarm higher than max
801 -
802 -² When min≠0, and max=0, Alarm lower than min
803 -
804 -² When min≠0 and max≠0, Alarm higher than max or lower than min
805 -
806 -
807 - (% style="color:blue" %)**Example:**
808 -
809 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
810 -
811 -
812 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
813 -
814 -² When min=0, and max≠0, Alarm higher than max
815 -
816 -² When min≠0, and max=0, Alarm lower than min
817 -
818 -² When min≠0 and max≠0, Alarm higher than max or lower than min
819 -
820 -
821 -**~ (% style="color:blue" %)Example:(%%)**
822 -
823 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
824 -
825 -
826 -
827 -== 2.6 Set the number of data to be uploaded and the recording time ==
828 -
829 -
830 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
831 -
832 -* (% 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)
833 -* (% 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.
834 -
835 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
836 -
837 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
838 -
839 -
840 -
841 -== 2.7 Read or Clear cached data ==
842 -
843 -
844 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
845 -
846 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
847 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
848 -
849 -[[image:image-20220908163102-2.png]]
850 -
851 -
852 -
853 -== 2.8  ​Battery Analysis ==
854 -
855 -
856 -=== 2.8.1  ​Battery Type ===
857 -
858 -
859 859  (((
860 860  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.
861 861  )))
... ... @@ -878,11 +878,10 @@
878 878  
879 879  
880 880  
881 -=== 2.8.2  Power consumption Analyze ===
697 +=== 2.5.2  Power consumption Analyze ===
882 882  
883 -
884 884  (((
885 -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.
886 886  )))
887 887  
888 888  (((
... ... @@ -890,9 +890,8 @@
890 890  )))
891 891  
892 892  
893 -=== 2.8.3  ​Battery Note ===
708 +=== 2.5.3  ​Battery Note ===
894 894  
895 -
896 896  (((
897 897  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.
898 898  )))
... ... @@ -899,7 +899,7 @@
899 899  
900 900  
901 901  
902 -=== 2.8.4  Replace the battery ===
716 +=== 2.5.4  Replace the battery ===
903 903  
904 904  
905 905  (((
... ... @@ -915,7 +915,6 @@
915 915  
916 916  = 3. ​ Access NB-IoT Module =
917 917  
918 -
919 919  (((
920 920  Users can directly access the AT command set of the NB-IoT module.
921 921  )))
... ... @@ -922,8 +922,6 @@
922 922  
923 923  (((
924 924  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/]] 
925 -
926 -
927 927  )))
928 928  
929 929  [[image:1657333200519-600.png]]
... ... @@ -932,13 +932,11 @@
932 932  
933 933  = 4.  Using the AT Commands =
934 934  
935 -
936 936  == 4.1  Access AT Commands ==
937 937  
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/]]
938 938  
939 -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]]
940 940  
941 -
942 942  AT+<CMD>?  : Help on <CMD>
943 943  
944 944  AT+<CMD>         : Run <CMD>
... ... @@ -978,24 +978,7 @@
978 978  
979 979  AT+SERVADDR  : Server Address
980 980  
981 -AT+TR      : Get or Set record time
982 982  
983 -AT+APN     : Get or set the APN
984 -
985 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
986 -
987 -AT+DNSCFG  : Get or Set DNS Server
988 -
989 -AT+GETSENSORVALUE   : Returns the current sensor measurement
990 -
991 -AT+NOUD      : Get or Set the number of data to be uploaded
992 -
993 -AT+CDP     : Read or Clear cached data
994 -
995 -AT+SHTEMP: Get or Set alarm of temp
996 -
997 -AT+SHHUM: Get or Set alarm of moisture
998 -
999 999  (% style="color:#037691" %)**COAP Management**      
1000 1000  
1001 1001  AT+URI            : Resource parameters
... ... @@ -1029,7 +1029,6 @@
1029 1029  
1030 1030  = ​5.  FAQ =
1031 1031  
1032 -
1033 1033  == 5.1 ​ How to Upgrade Firmware ==
1034 1034  
1035 1035  
... ... @@ -1045,7 +1045,7 @@
1045 1045  
1046 1046  
1047 1047  (((
1048 -(% 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.
1049 1049  )))
1050 1050  )))
1051 1051  
... ... @@ -1053,7 +1053,6 @@
1053 1053  
1054 1054  = 6.  Trouble Shooting =
1055 1055  
1056 -
1057 1057  == 6.1  ​Connection problem when uploading firmware ==
1058 1058  
1059 1059  
... ... @@ -1069,7 +1069,6 @@
1069 1069  
1070 1070  == 6.2  AT Command input doesn't work ==
1071 1071  
1072 -
1073 1073  (((
1074 1074  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.
1075 1075  
... ... @@ -1119,6 +1119,5 @@
1119 1119  
1120 1120  = 9.  Support =
1121 1121  
1122 -
1123 1123  * 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.
1124 1124  * 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
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0