Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 129.4 >
edited by Xiaoling
on 2022/10/25 17:00
To version < 119.2 >
edited by Xiaoling
on 2022/08/22 14:47
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -69,6 +69,8 @@
69 69  * 8500mAh Battery for long term use
70 70  
71 71  
72 +
73 +
72 72  == 1.3  Specification ==
73 73  
74 74  
... ... @@ -77,6 +77,8 @@
77 77  * Supply Voltage: 2.1v ~~ 3.6v
78 78  * Operating Temperature: -40 ~~ 85°C
79 79  
82 +
83 +
80 80  (% style="color:#037691" %)**NB-IoT Spec:**
81 81  
82 82  * - B1 @H-FDD: 2100MHz
... ... @@ -86,6 +86,8 @@
86 86  * - B20 @H-FDD: 800MHz
87 87  * - B28 @H-FDD: 700MHz
88 88  
93 +
94 +
89 89  (% style="color:#037691" %)**Battery:**
90 90  
91 91  * Li/SOCI2 un-chargeable battery
... ... @@ -95,6 +95,8 @@
95 95  * Max boost current: 2A, 1 second
96 96  
97 97  
104 +
105 +
98 98  == ​1.4  Applications ==
99 99  
100 100  
... ... @@ -131,11 +131,11 @@
131 131  
132 132  
133 133  (((
134 -**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.
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.
135 135  )))
136 136  
137 137  (((
138 -**2) Flash:**  work mode, device starts to work and send out console output for further debug
146 +2) Flash: work mode, device starts to work and send out console output for further debug
139 139  )))
140 140  
141 141  
... ... @@ -152,9 +152,9 @@
152 152  
153 153  It will flash:
154 154  
155 -1.  When boot the device in flash mode
163 +1. When boot the device in flash mode
164 +1. Send an uplink packet
156 156  
157 -2.  Send an uplink packet
158 158  
159 159  
160 160  
... ... @@ -274,13 +274,13 @@
274 274  [[image:1657351312545-300.png]]
275 275  
276 276  
277 -**(% style="color:blue" %)Connection:**
285 +**Connection:**
278 278  
279 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
287 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
280 280  
281 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
289 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
282 282  
283 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
291 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
284 284  
285 285  
286 286  In the PC, use below serial tool settings:
... ... @@ -318,10 +318,10 @@
318 318  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
319 319  )))
320 320  * (((
321 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
329 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
322 322  )))
323 323  * (((
324 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
332 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
325 325  )))
326 326  
327 327  (((
... ... @@ -357,16 +357,15 @@
357 357  
358 358  === 2.2.7  Use MQTT protocol to uplink data ===
359 359  
360 -
361 361  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
362 362  
363 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
364 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
365 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
366 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
367 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
368 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
369 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
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
370 370  
371 371  [[image:1657352634421-276.png]]
372 372  
... ... @@ -373,7 +373,6 @@
373 373  
374 374  [[image:1657352645687-385.png]]
375 375  
376 -
377 377  (((
378 378  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.
379 379  )))
... ... @@ -387,7 +387,6 @@
387 387  
388 388  === 2.2.8  Use TCP protocol to uplink data ===
389 389  
390 -
391 391  This feature is supported since firmware version v110
392 392  
393 393  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -402,7 +402,6 @@
402 402  
403 403  === 2.2.9  Change Update Interval ===
404 404  
405 -
406 406  User can use below command to change the (% style="color:green" %)**uplink interval**.
407 407  
408 408  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -411,21 +411,13 @@
411 411  
412 412  )))
413 413  
414 -(((
415 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
416 -)))
417 417  
418 -(((
419 -(% 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).**
420 -)))
421 421  
422 -
423 -
424 424  == 2.3  Uplink Payload ==
425 425  
426 426  
427 427  (((
428 -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.
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.
429 429  )))
430 430  
431 431  
... ... @@ -457,10 +457,10 @@
457 457  
458 458  (% style="color:red" %)
459 459  1. (((
460 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
456 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
461 461  )))
462 462  1. (((
463 -**By default, the device will send an uplink message every 1 hour.**
459 +By default, the device will send an uplink message every 1 hour.
464 464  
465 465  
466 466  
... ... @@ -469,18 +469,14 @@
469 469  
470 470  === 2.3.1  Payload Analyze ===
471 471  
472 -
473 -==== 2.3.1.1  Before Firmware v1.2 ====
474 -
475 -
476 476  N95S31B uplink payload includes in total 21 bytes
477 477  
478 478  
479 -(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
480 -|=(% style="width: 50px;" %)(((
471 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
472 +|=(% style="width: 60px;" %)(((
481 481  **Size(bytes)**
482 -)))|=(% 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**
483 -|(% 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" %)(((
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" %)(((
484 484  (((
485 485  Reserve/ Same as NBSN95 CFGMOD=1
486 486  )))
... ... @@ -488,7 +488,7 @@
488 488  (((
489 489  No function here.
490 490  )))
491 -)))|(% style="width:102px" %)(((
483 +)))|(% style="width:77px" %)(((
492 492  (((
493 493  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
494 494  )))
... ... @@ -496,7 +496,7 @@
496 496  (((
497 497  By SHT31
498 498  )))
499 -)))|(% style="width:81px" %)(((
491 +)))|(% style="width:80px" %)(((
500 500  (((
501 501  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
502 502  )))
... ... @@ -507,8 +507,6 @@
507 507  )))
508 508  
509 509  (((
510 -
511 -
512 512  (((
513 513  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
514 514  )))
... ... @@ -518,89 +518,29 @@
518 518  [[image:1657354294009-643.png]]
519 519  
520 520  
521 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
511 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
522 522  
523 -**where:**
513 +* Device ID: 0x724031607457 = 724031607457
514 +* Version: 0x006e=110=1.1.0
524 524  
525 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
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
526 526  
527 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
528 -
529 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
530 -
531 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
532 -
533 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
534 -
535 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
536 -
537 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
538 -
539 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
540 -
541 541  (((
542 542  
525 +)))
543 543  
544 -
527 +(((
545 545  
546 546  )))
547 547  
548 -==== 2.3.1.2 Since Firmware v1.2 ====
549 549  
550 -
551 -In this mode, uplink payload includes 91 bytes in total by default.
552 -
553 -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.
554 -
555 -
556 -(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
557 -|(% 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**
558 -|(% 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 .....
559 -
560 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
561 -
562 -
563 -[[image:image-20220908154949-1.png]]
564 -
565 -
566 -The payload is ASCII string, representative same HEX:
567 -
568 -**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__ **
569 -
570 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
571 -
572 -**where:**
573 -
574 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
575 -
576 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
577 -
578 -* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
579 -
580 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
581 -
582 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
583 -
584 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
585 -
586 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
587 -
588 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
589 -
590 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
591 -
592 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
593 -
594 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
595 -
596 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
597 -
598 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
599 -
600 -
601 601  === 2.3.2  Device ID ===
602 602  
603 -
604 604  (((
605 605  By default, the Device ID equal to the last 6 bytes of IMEI.
606 606  )))
... ... @@ -607,12 +607,10 @@
607 607  
608 608  (((
609 609  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
610 -
611 -
612 612  )))
613 613  
614 614  (((
615 -(% style="color:blue" %)**Example:**
543 +**Example:**
616 616  )))
617 617  
618 618  (((
... ... @@ -620,28 +620,13 @@
620 620  )))
621 621  
622 622  (((
623 -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.
624 -
625 -
551 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
626 626  )))
627 627  
628 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
629 629  
630 630  
631 -By default, the Device ID equal to the last 15 bits of IMEI.
632 -
633 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
634 -
635 -
636 -(% style="color:blue" %)**Example:**
637 -
638 -AT+DEUI=868411056754138
639 -
640 -
641 -
642 642  === 2.3.3  Version Info ===
643 643  
644 -
645 645  (((
646 646  These bytes include the hardware and software version.
647 647  )))
... ... @@ -669,7 +669,6 @@
669 669  
670 670  === 2.3.4  Battery Info ===
671 671  
672 -
673 673  (((
674 674  Ex1: 0x0B45 = 2885mV
675 675  )))
... ... @@ -682,7 +682,6 @@
682 682  
683 683  === 2.3.5  Signal Strength ===
684 684  
685 -
686 686  (((
687 687  NB-IoT Network signal Strength.
688 688  )))
... ... @@ -715,7 +715,6 @@
715 715  
716 716  === 2.3.6  Temperature & Humidity ===
717 717  
718 -
719 719  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
720 720  
721 721  [[image:image-20220709161741-3.png]]
... ... @@ -734,7 +734,6 @@
734 734  
735 735  == 2.4  Downlink Payload ==
736 736  
737 -
738 738  By default, N95S31B prints the downlink payload to console port.
739 739  
740 740  [[image:image-20220709100028-1.png]]
... ... @@ -785,74 +785,11 @@
785 785  
786 786  
787 787  
788 -== 2.5  Humidity and Temperature alarm function ==
697 +== 2.5  ​Battery Analysis ==
789 789  
699 +=== 2.5.1  ​Battery Type ===
790 790  
791 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
792 792  
793 -
794 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
795 -
796 -
797 -² When min=0, and max≠0, Alarm higher than max
798 -
799 -² When min≠0, and max=0, Alarm lower than min
800 -
801 -² When min≠0 and max≠0, Alarm higher than max or lower than min
802 -
803 -
804 - (% style="color:blue" %)**Example:**
805 -
806 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
807 -
808 -
809 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
810 -
811 -² When min=0, and max≠0, Alarm higher than max
812 -
813 -² When min≠0, and max=0, Alarm lower than min
814 -
815 -² When min≠0 and max≠0, Alarm higher than max or lower than min
816 -
817 -
818 -**~ (% style="color:blue" %)Example:(%%)**
819 -
820 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
821 -
822 -
823 -
824 -== 2.6 Set the number of data to be uploaded and the recording time ==
825 -
826 -
827 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
828 -
829 -* (% 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)
830 -* (% 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.
831 -
832 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
833 -
834 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
835 -
836 -
837 -
838 -== 2.7 Read or Clear cached data ==
839 -
840 -
841 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
842 -
843 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
844 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
845 -
846 -[[image:image-20220908163102-2.png]]
847 -
848 -
849 -
850 -== 2.8  ​Battery Analysis ==
851 -
852 -
853 -=== 2.8.1  ​Battery Type ===
854 -
855 -
856 856  (((
857 857  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.
858 858  )))
... ... @@ -875,11 +875,10 @@
875 875  
876 876  
877 877  
878 -=== 2.8.2  Power consumption Analyze ===
724 +=== 2.5.2  Power consumption Analyze ===
879 879  
880 -
881 881  (((
882 -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.
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.
883 883  )))
884 884  
885 885  (((
... ... @@ -887,9 +887,8 @@
887 887  )))
888 888  
889 889  
890 -=== 2.8.3  ​Battery Note ===
735 +=== 2.5.3  ​Battery Note ===
891 891  
892 -
893 893  (((
894 894  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.
895 895  )))
... ... @@ -896,7 +896,7 @@
896 896  
897 897  
898 898  
899 -=== 2.8.4  Replace the battery ===
743 +=== 2.5.4  Replace the battery ===
900 900  
901 901  
902 902  (((
... ... @@ -912,7 +912,6 @@
912 912  
913 913  = 3. ​ Access NB-IoT Module =
914 914  
915 -
916 916  (((
917 917  Users can directly access the AT command set of the NB-IoT module.
918 918  )))
... ... @@ -919,8 +919,6 @@
919 919  
920 920  (((
921 921  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/]] 
922 -
923 -
924 924  )))
925 925  
926 926  [[image:1657333200519-600.png]]
... ... @@ -929,13 +929,11 @@
929 929  
930 930  = 4.  Using the AT Commands =
931 931  
932 -
933 933  == 4.1  Access AT Commands ==
934 934  
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/]]
935 935  
936 -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]]
937 937  
938 -
939 939  AT+<CMD>?  : Help on <CMD>
940 940  
941 941  AT+<CMD>         : Run <CMD>
... ... @@ -975,24 +975,7 @@
975 975  
976 976  AT+SERVADDR  : Server Address
977 977  
978 -AT+TR      : Get or Set record time
979 979  
980 -AT+APN     : Get or set the APN
981 -
982 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
983 -
984 -AT+DNSCFG  : Get or Set DNS Server
985 -
986 -AT+GETSENSORVALUE   : Returns the current sensor measurement
987 -
988 -AT+NOUD      : Get or Set the number of data to be uploaded
989 -
990 -AT+CDP     : Read or Clear cached data
991 -
992 -AT+SHTEMP: Get or Set alarm of temp
993 -
994 -AT+SHHUM: Get or Set alarm of moisture
995 -
996 996  (% style="color:#037691" %)**COAP Management**      
997 997  
998 998  AT+URI            : Resource parameters
... ... @@ -1026,7 +1026,6 @@
1026 1026  
1027 1027  = ​5.  FAQ =
1028 1028  
1029 -
1030 1030  == 5.1 ​ How to Upgrade Firmware ==
1031 1031  
1032 1032  
... ... @@ -1042,7 +1042,7 @@
1042 1042  
1043 1043  
1044 1044  (((
1045 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
866 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
1046 1046  )))
1047 1047  )))
1048 1048  
... ... @@ -1050,7 +1050,6 @@
1050 1050  
1051 1051  = 6.  Trouble Shooting =
1052 1052  
1053 -
1054 1054  == 6.1  ​Connection problem when uploading firmware ==
1055 1055  
1056 1056  
... ... @@ -1066,7 +1066,6 @@
1066 1066  
1067 1067  == 6.2  AT Command input doesn't work ==
1068 1068  
1069 -
1070 1070  (((
1071 1071  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.
1072 1072  
... ... @@ -1116,6 +1116,5 @@
1116 1116  
1117 1117  = 9.  Support =
1118 1118  
1119 -
1120 1120  * 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.
1121 1121  * 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