Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 119.2 >
edited by Xiaoling
on 2022/08/22 14:47
To version < 123.1 >
edited by David Huang
on 2022/09/08 16:37
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.David
Content
... ... @@ -68,9 +68,6 @@
68 68  * Micro SIM card slot for NB-IoT SIM
69 69  * 8500mAh Battery for long term use
70 70  
71 -
72 -
73 -
74 74  == 1.3  Specification ==
75 75  
76 76  
... ... @@ -79,8 +79,6 @@
79 79  * Supply Voltage: 2.1v ~~ 3.6v
80 80  * Operating Temperature: -40 ~~ 85°C
81 81  
82 -
83 -
84 84  (% style="color:#037691" %)**NB-IoT Spec:**
85 85  
86 86  * - B1 @H-FDD: 2100MHz
... ... @@ -90,8 +90,6 @@
90 90  * - B20 @H-FDD: 800MHz
91 91  * - B28 @H-FDD: 700MHz
92 92  
93 -
94 -
95 95  (% style="color:#037691" %)**Battery:**
96 96  
97 97  * Li/SOCI2 un-chargeable battery
... ... @@ -100,9 +100,6 @@
100 100  * Max continuously current: 130mA
101 101  * Max boost current: 2A, 1 second
102 102  
103 -
104 -
105 -
106 106  == ​1.4  Applications ==
107 107  
108 108  
... ... @@ -163,9 +163,6 @@
163 163  1. When boot the device in flash mode
164 164  1. Send an uplink packet
165 165  
166 -
167 -
168 -
169 169  = 2.  Use N95S31B to communicate with IoT Server =
170 170  
171 171  
... ... @@ -365,6 +365,7 @@
365 365  
366 366  === 2.2.7  Use MQTT protocol to uplink data ===
367 367  
355 +
368 368  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
369 369  
370 370  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
... ... @@ -380,6 +380,7 @@
380 380  
381 381  [[image:1657352645687-385.png]]
382 382  
371 +
383 383  (((
384 384  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.
385 385  )))
... ... @@ -393,6 +393,7 @@
393 393  
394 394  === 2.2.8  Use TCP protocol to uplink data ===
395 395  
385 +
396 396  This feature is supported since firmware version v110
397 397  
398 398  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -407,6 +407,7 @@
407 407  
408 408  === 2.2.9  Change Update Interval ===
409 409  
400 +
410 410  User can use below command to change the (% style="color:green" %)**uplink interval**.
411 411  
412 412  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -415,8 +415,11 @@
415 415  
416 416  )))
417 417  
409 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
418 418  
411 +**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 419  
413 +
420 420  == 2.3  Uplink Payload ==
421 421  
422 422  
... ... @@ -453,10 +453,10 @@
453 453  
454 454  (% style="color:red" %)
455 455  1. (((
456 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
450 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
457 457  )))
458 458  1. (((
459 -By default, the device will send an uplink message every 1 hour.
453 +**By default, the device will send an uplink message every 1 hour.**
460 460  
461 461  
462 462  
... ... @@ -465,6 +465,7 @@
465 465  
466 466  === 2.3.1  Payload Analyze ===
467 467  
462 +
468 468  N95S31B uplink payload includes in total 21 bytes
469 469  
470 470  
... ... @@ -499,6 +499,8 @@
499 499  )))
500 500  
501 501  (((
497 +
498 +
502 502  (((
503 503  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
504 504  )))
... ... @@ -525,12 +525,41 @@
525 525  )))
526 526  
527 527  (((
528 -
525 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
529 529  )))
530 530  
528 +In this mode, uplink payload includes 91 bytes in total by default.
531 531  
530 +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.
531 +
532 +|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
533 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
534 +
535 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
536 +
537 +[[image:image-20220908154949-1.png]]
538 +
539 +The payload is ASCII string, representative same HEX:
540 +
541 +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:
542 +
543 +* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
544 +* (% style="color:blue" %) Version: 0x000c=120=1.2
545 +* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
546 +* (% style="color:red" %) Singal: 0x0c = 12
547 +* (% style="color:blue" %) Mod: 0x01 = 1
548 +* TemDS18B20: 0x0000= 0 = 0
549 +* (% style="color:green" %)Interrupt: 0x00= 0
550 +* (% style="color:green" %)adc: 0x0030= 48
551 +* SHTTEM: 0x0114= 276 = 27.6
552 +* SHTHUM:0x0231 =561=56.1%
553 +* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
554 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
555 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
556 +
532 532  === 2.3.2  Device ID ===
533 533  
559 +
534 534  (((
535 535  By default, the Device ID equal to the last 6 bytes of IMEI.
536 536  )))
... ... @@ -549,12 +549,25 @@
549 549  
550 550  (((
551 551  The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
578 +
579 +
552 552  )))
553 553  
582 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
554 554  
555 555  
585 +By default, the Device ID equal to the last 15 bits of IMEI.
586 +
587 +User can use **AT+DEUI** to set Device ID
588 +
589 +**Example:**
590 +
591 +AT+DEUI=868411056754138
592 +
593 +
556 556  === 2.3.3  Version Info ===
557 557  
596 +
558 558  (((
559 559  These bytes include the hardware and software version.
560 560  )))
... ... @@ -582,6 +582,7 @@
582 582  
583 583  === 2.3.4  Battery Info ===
584 584  
624 +
585 585  (((
586 586  Ex1: 0x0B45 = 2885mV
587 587  )))
... ... @@ -594,6 +594,7 @@
594 594  
595 595  === 2.3.5  Signal Strength ===
596 596  
637 +
597 597  (((
598 598  NB-IoT Network signal Strength.
599 599  )))
... ... @@ -626,6 +626,7 @@
626 626  
627 627  === 2.3.6  Temperature & Humidity ===
628 628  
670 +
629 629  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
630 630  
631 631  [[image:image-20220709161741-3.png]]
... ... @@ -644,6 +644,7 @@
644 644  
645 645  == 2.4  Downlink Payload ==
646 646  
689 +
647 647  By default, N95S31B prints the downlink payload to console port.
648 648  
649 649  [[image:image-20220709100028-1.png]]
... ... @@ -693,12 +693,59 @@
693 693  )))
694 694  
695 695  
739 +== 2.5 Humidity and Temperature alarm function ==
696 696  
697 -== 2.5  ​Battery Analysis ==
741 +➢ AT Command:
698 698  
699 -=== 2.5.1  ​Battery Type ===
743 +AT+ SHHUM=min,max
700 700  
745 +² When min=0, and max≠0, Alarm higher than max
701 701  
747 +² When min≠0, and max=0, Alarm lower than min
748 +
749 +² When min≠0 and max≠0, Alarm higher than max or lower than min
750 +
751 +Example:
752 +
753 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
754 +
755 +
756 +AT+ SHTEMP=min,max
757 +
758 +² When min=0, and max≠0, Alarm higher than max
759 +
760 +² When min≠0, and max=0, Alarm lower than min
761 +
762 +² When min≠0 and max≠0, Alarm higher than max or lower than min
763 +
764 +Example:
765 +
766 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
767 +
768 +== 2.6 Set the number of data to be uploaded and the recording time ==
769 +
770 +➢ AT Command:
771 +
772 +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)
773 +
774 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
775 +
776 +== 2.7 Read or Clear cached data ==
777 +
778 +➢ AT Command:
779 +
780 +AT+CDP ~/~/ Read cached data
781 +
782 +[[image:image-20220908163102-2.png]]
783 +
784 +AT+CDP=0 ~/~/ Clear cached data
785 +
786 +== 2.8  ​Battery Analysis ==
787 +
788 +
789 +=== 2.8.1  ​Battery Type ===
790 +
791 +
702 702  (((
703 703  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.
704 704  )))
... ... @@ -721,10 +721,11 @@
721 721  
722 722  
723 723  
724 -=== 2.5.2  Power consumption Analyze ===
814 +=== 2.8.2  Power consumption Analyze ===
725 725  
816 +
726 726  (((
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.
818 +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.
728 728  )))
729 729  
730 730  (((
... ... @@ -732,8 +732,9 @@
732 732  )))
733 733  
734 734  
735 -=== 2.5.3  ​Battery Note ===
826 +=== 2.8.3  ​Battery Note ===
736 736  
828 +
737 737  (((
738 738  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.
739 739  )))
... ... @@ -740,7 +740,7 @@
740 740  
741 741  
742 742  
743 -=== 2.5.4  Replace the battery ===
835 +=== 2.8.4  Replace the battery ===
744 744  
745 745  
746 746  (((
... ... @@ -756,6 +756,7 @@
756 756  
757 757  = 3. ​ Access NB-IoT Module =
758 758  
851 +
759 759  (((
760 760  Users can directly access the AT command set of the NB-IoT module.
761 761  )))
... ... @@ -762,6 +762,8 @@
762 762  
763 763  (((
764 764  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/]] 
858 +
859 +
765 765  )))
766 766  
767 767  [[image:1657333200519-600.png]]
... ... @@ -770,11 +770,13 @@
770 770  
771 771  = 4.  Using the AT Commands =
772 772  
868 +
773 773  == 4.1  Access AT Commands ==
774 774  
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/]]
776 776  
872 +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]]
777 777  
874 +
778 778  AT+<CMD>?  : Help on <CMD>
779 779  
780 780  AT+<CMD>         : Run <CMD>
... ... @@ -814,7 +814,24 @@
814 814  
815 815  AT+SERVADDR  : Server Address
816 816  
914 +AT+TR      : Get or Set record time
817 817  
916 +AT+APN     : Get or set the APN
917 +
918 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
919 +
920 +AT+DNSCFG  : Get or Set DNS Server
921 +
922 +AT+GETSENSORVALUE   : Returns the current sensor measurement
923 +
924 +AT+NOUD      : Get or Set the number of data to be uploaded
925 +
926 +AT+CDP     : Read or Clear cached data
927 +
928 +AT+SHTEMP: Get or Set alarm of temp
929 +
930 +AT+SHHUM: Get or Set alarm of moisture
931 +
818 818  (% style="color:#037691" %)**COAP Management**      
819 819  
820 820  AT+URI            : Resource parameters
... ... @@ -848,6 +848,7 @@
848 848  
849 849  = ​5.  FAQ =
850 850  
965 +
851 851  == 5.1 ​ How to Upgrade Firmware ==
852 852  
853 853  
... ... @@ -863,7 +863,7 @@
863 863  
864 864  
865 865  (((
866 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
981 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
867 867  )))
868 868  )))
869 869  
... ... @@ -871,6 +871,7 @@
871 871  
872 872  = 6.  Trouble Shooting =
873 873  
989 +
874 874  == 6.1  ​Connection problem when uploading firmware ==
875 875  
876 876  
... ... @@ -886,6 +886,7 @@
886 886  
887 887  == 6.2  AT Command input doesn't work ==
888 888  
1005 +
889 889  (((
890 890  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.
891 891  
... ... @@ -935,5 +935,8 @@
935 935  
936 936  = 9.  Support =
937 937  
1055 +
938 938  * 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.
939 939  * 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]]
1058 +
1059 +
image-20220908154949-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +58.5 KB
Content
image-20220908163102-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +29.7 KB
Content

Applications

Navigation

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