Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 125.3 >
edited by Xiaoling
on 2022/09/09 15:56
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  
... ... @@ -110,7 +110,6 @@
110 110  
111 111  
112 112  
113 -
114 114  == 1.5  Pin Definitions & Switch ==
115 115  
116 116  
... ... @@ -157,6 +157,8 @@
157 157  1. Send an uplink packet
158 158  
159 159  
167 +
168 +
160 160  = 2.  Use N95S31B to communicate with IoT Server =
161 161  
162 162  
... ... @@ -356,7 +356,6 @@
356 356  
357 357  === 2.2.7  Use MQTT protocol to uplink data ===
358 358  
359 -
360 360  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
361 361  
362 362  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
... ... @@ -372,7 +372,6 @@
372 372  
373 373  [[image:1657352645687-385.png]]
374 374  
375 -
376 376  (((
377 377  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.
378 378  )))
... ... @@ -386,7 +386,6 @@
386 386  
387 387  === 2.2.8  Use TCP protocol to uplink data ===
388 388  
389 -
390 390  This feature is supported since firmware version v110
391 391  
392 392  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -401,7 +401,6 @@
401 401  
402 402  === 2.2.9  Change Update Interval ===
403 403  
404 -
405 405  User can use below command to change the (% style="color:green" %)**uplink interval**.
406 406  
407 407  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -410,21 +410,13 @@
410 410  
411 411  )))
412 412  
413 -(((
414 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
415 -)))
416 416  
417 -(((
418 -(% 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).**
419 -)))
420 420  
421 -
422 -
423 423  == 2.3  Uplink Payload ==
424 424  
425 425  
426 426  (((
427 -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.
428 428  )))
429 429  
430 430  
... ... @@ -456,10 +456,10 @@
456 456  
457 457  (% style="color:red" %)
458 458  1. (((
459 -**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"]].
460 460  )))
461 461  1. (((
462 -**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.
463 463  
464 464  
465 465  
... ... @@ -468,18 +468,14 @@
468 468  
469 469  === 2.3.1  Payload Analyze ===
470 470  
471 -
472 -==== 2.3.1.1  Before Firmware v1.2 ====
473 -
474 -
475 475  N95S31B uplink payload includes in total 21 bytes
476 476  
477 477  
478 -(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %)
471 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
479 479  |=(% style="width: 60px;" %)(((
480 480  **Size(bytes)**
481 -)))|=(% 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**
482 -|(% 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" %)(((
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" %)(((
483 483  (((
484 484  Reserve/ Same as NBSN95 CFGMOD=1
485 485  )))
... ... @@ -487,7 +487,7 @@
487 487  (((
488 488  No function here.
489 489  )))
490 -)))|(% style="width:106px" %)(((
483 +)))|(% style="width:77px" %)(((
491 491  (((
492 492  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
493 493  )))
... ... @@ -495,7 +495,7 @@
495 495  (((
496 496  By SHT31
497 497  )))
498 -)))|(% style="width:85px" %)(((
491 +)))|(% style="width:80px" %)(((
499 499  (((
500 500  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
501 501  )))
... ... @@ -506,8 +506,6 @@
506 506  )))
507 507  
508 508  (((
509 -
510 -
511 511  (((
512 512  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
513 513  )))
... ... @@ -519,83 +519,27 @@
519 519  
520 520  The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
521 521  
522 -* Device ID:  0x724031607457 = 724031607457
513 +* Device ID: 0x724031607457 = 724031607457
514 +* Version: 0x006e=110=1.1.0
523 523  
524 -* Version:  0x006e=110=1.1.0
525 -
526 -* BAT:  0x0ccd = 3277 mV = 3.277V
527 -
528 -* Signal:  0x1b = 27
529 -
530 -* Model:  0x01 = 1
531 -
516 +* BAT: 0x0ccd = 3277 mV = 3.277V
517 +* Signal: 0x1b = 27
518 +* Model: 0x01 = 1
532 532  * 0x00dc000ccc= reserve, ignore in N95S31B
520 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
521 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
533 533  
534 -* Temperature by SHT31:  0x00e1 = 225 = 22.5 °C
535 -
536 -* Humidity by SHT31:  0x0186 = 390 = 39.0 %rh
537 -
538 538  (((
539 539  
525 +)))
540 540  
541 -
527 +(((
542 542  
543 543  )))
544 544  
545 -==== 2.3.1.2 Since Firmware v1.2 ====
546 546  
547 -
548 -In this mode, uplink payload includes 91 bytes in total by default.
549 -
550 -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.
551 -
552 -
553 -(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
554 -|(% 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**
555 -|(% 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 .....
556 -
557 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
558 -
559 -
560 -[[image:image-20220908154949-1.png]]
561 -
562 -
563 -The payload is ASCII string, representative same HEX:
564 -
565 -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:
566 -
567 -* (% style="color:red" %)Device ID: f868411056758782 = f868411056758782
568 -
569 -* (% style="color:blue" %)Version: 0x000c=120=1.2
570 -
571 -* (% style="color:green" %)BAT: 0x0d0f = 3343 mV = 3.343V
572 -
573 -* (% style="color:red" %)Singal: 0x0c = 12
574 -
575 -* (% style="color:blue" %)Mod: 0x01 = 1
576 -
577 -* TemDS18B20: 0x0000= 0 = 0
578 -
579 -* (% style="color:green" %)Interrupt: 0x00= 0
580 -
581 -* (% style="color:green" %)adc: 0x0030= 48
582 -
583 -* SHTTEM: 0x0114= 276 = 27.6
584 -
585 -* SHTHUM:0x0231 =561=56.1%
586 -
587 -* (% style="color:red" %)Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
588 -
589 -* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
590 -
591 -* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
592 -
593 -
594 -
595 -
596 596  === 2.3.2  Device ID ===
597 597  
598 -
599 599  (((
600 600  By default, the Device ID equal to the last 6 bytes of IMEI.
601 601  )))
... ... @@ -614,25 +614,12 @@
614 614  
615 615  (((
616 616  The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
617 -
618 -
619 619  )))
620 620  
621 -(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
622 622  
623 623  
624 -By default, the Device ID equal to the last 15 bits of IMEI.
625 -
626 -User can use **AT+DEUI** to set Device ID
627 -
628 -**Example:**
629 -
630 -AT+DEUI=868411056754138
631 -
632 -
633 633  === 2.3.3  Version Info ===
634 634  
635 -
636 636  (((
637 637  These bytes include the hardware and software version.
638 638  )))
... ... @@ -660,7 +660,6 @@
660 660  
661 661  === 2.3.4  Battery Info ===
662 662  
663 -
664 664  (((
665 665  Ex1: 0x0B45 = 2885mV
666 666  )))
... ... @@ -673,7 +673,6 @@
673 673  
674 674  === 2.3.5  Signal Strength ===
675 675  
676 -
677 677  (((
678 678  NB-IoT Network signal Strength.
679 679  )))
... ... @@ -706,7 +706,6 @@
706 706  
707 707  === 2.3.6  Temperature & Humidity ===
708 708  
709 -
710 710  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
711 711  
712 712  [[image:image-20220709161741-3.png]]
... ... @@ -725,7 +725,6 @@
725 725  
726 726  == 2.4  Downlink Payload ==
727 727  
728 -
729 729  By default, N95S31B prints the downlink payload to console port.
730 730  
731 731  [[image:image-20220709100028-1.png]]
... ... @@ -775,59 +775,12 @@
775 775  )))
776 776  
777 777  
778 -== 2.5 Humidity and Temperature alarm function ==
779 779  
780 -➢ AT Command:
697 +== 2.5  ​Battery Analysis ==
781 781  
782 -AT+ SHHUM=min,max
699 +=== 2.5.1  ​Battery Type ===
783 783  
784 -² When min=0, and max≠0, Alarm higher than max
785 785  
786 -² When min≠0, and max=0, Alarm lower than min
787 -
788 -² When min≠0 and max≠0, Alarm higher than max or lower than min
789 -
790 -Example:
791 -
792 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
793 -
794 -
795 -AT+ SHTEMP=min,max
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 -Example:
804 -
805 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
806 -
807 -== 2.6 Set the number of data to be uploaded and the recording time ==
808 -
809 -➢ AT Command:
810 -
811 -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)
812 -
813 -AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
814 -
815 -== 2.7 Read or Clear cached data ==
816 -
817 -➢ AT Command:
818 -
819 -AT+CDP ~/~/ Read cached data
820 -
821 -[[image:image-20220908163102-2.png]]
822 -
823 -AT+CDP=0 ~/~/ Clear cached data
824 -
825 -== 2.8  ​Battery Analysis ==
826 -
827 -
828 -=== 2.8.1  ​Battery Type ===
829 -
830 -
831 831  (((
832 832  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.
833 833  )))
... ... @@ -850,11 +850,10 @@
850 850  
851 851  
852 852  
853 -=== 2.8.2  Power consumption Analyze ===
724 +=== 2.5.2  Power consumption Analyze ===
854 854  
855 -
856 856  (((
857 -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.
858 858  )))
859 859  
860 860  (((
... ... @@ -862,9 +862,8 @@
862 862  )))
863 863  
864 864  
865 -=== 2.8.3  ​Battery Note ===
735 +=== 2.5.3  ​Battery Note ===
866 866  
867 -
868 868  (((
869 869  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.
870 870  )))
... ... @@ -871,7 +871,7 @@
871 871  
872 872  
873 873  
874 -=== 2.8.4  Replace the battery ===
743 +=== 2.5.4  Replace the battery ===
875 875  
876 876  
877 877  (((
... ... @@ -887,7 +887,6 @@
887 887  
888 888  = 3. ​ Access NB-IoT Module =
889 889  
890 -
891 891  (((
892 892  Users can directly access the AT command set of the NB-IoT module.
893 893  )))
... ... @@ -894,8 +894,6 @@
894 894  
895 895  (((
896 896  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/]] 
897 -
898 -
899 899  )))
900 900  
901 901  [[image:1657333200519-600.png]]
... ... @@ -904,13 +904,11 @@
904 904  
905 905  = 4.  Using the AT Commands =
906 906  
907 -
908 908  == 4.1  Access AT Commands ==
909 909  
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/]]
910 910  
911 -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]]
912 912  
913 -
914 914  AT+<CMD>?  : Help on <CMD>
915 915  
916 916  AT+<CMD>         : Run <CMD>
... ... @@ -950,24 +950,7 @@
950 950  
951 951  AT+SERVADDR  : Server Address
952 952  
953 -AT+TR      : Get or Set record time
954 954  
955 -AT+APN     : Get or set the APN
956 -
957 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
958 -
959 -AT+DNSCFG  : Get or Set DNS Server
960 -
961 -AT+GETSENSORVALUE   : Returns the current sensor measurement
962 -
963 -AT+NOUD      : Get or Set the number of data to be uploaded
964 -
965 -AT+CDP     : Read or Clear cached data
966 -
967 -AT+SHTEMP: Get or Set alarm of temp
968 -
969 -AT+SHHUM: Get or Set alarm of moisture
970 -
971 971  (% style="color:#037691" %)**COAP Management**      
972 972  
973 973  AT+URI            : Resource parameters
... ... @@ -1001,7 +1001,6 @@
1001 1001  
1002 1002  = ​5.  FAQ =
1003 1003  
1004 -
1005 1005  == 5.1 ​ How to Upgrade Firmware ==
1006 1006  
1007 1007  
... ... @@ -1017,7 +1017,7 @@
1017 1017  
1018 1018  
1019 1019  (((
1020 -(% 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.
1021 1021  )))
1022 1022  )))
1023 1023  
... ... @@ -1025,7 +1025,6 @@
1025 1025  
1026 1026  = 6.  Trouble Shooting =
1027 1027  
1028 -
1029 1029  == 6.1  ​Connection problem when uploading firmware ==
1030 1030  
1031 1031  
... ... @@ -1041,7 +1041,6 @@
1041 1041  
1042 1042  == 6.2  AT Command input doesn't work ==
1043 1043  
1044 -
1045 1045  (((
1046 1046  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.
1047 1047  
... ... @@ -1091,6 +1091,5 @@
1091 1091  
1092 1092  = 9.  Support =
1093 1093  
1094 -
1095 1095  * 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.
1096 1096  * 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

Applications

Navigation

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