Last modified by Kilight Cao on 2024/12/31 16:31
<
From version < 306.1 >
edited by Edwin Chen
on 2024/05/03 20:49
To version < 284.1 >
edited by Xiaoye
on 2023/12/04 14:05
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -LPS8v2 -- LoRaWAN Indoor Gateway User Manual
1 +LPS8v2 LoRaWAN Indoor Gateway User Manual
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoye
Content
... ... @@ -8,7 +8,7 @@
8 8  
9 9  )))
10 10  
11 -**Table of Contents:**
11 +**Table of Contents：**
12 12  
13 13  {{toc/}}
14 14  
... ... @@ -96,11 +96,11 @@
96 96  
97 97  (% style="color:blue" %)**➢ SYS LED**(%%):  This RGB LED will show different colors in different states:
98 98  
99 - ✓  **SOLID GREEN:** The device is alive with a LoRaWAN server connection.
99 + ✓ **SOLID GREEN:** The device is alive with a LoRaWAN server connection.
100 100  
101 - ✓  **BLINKING GREEN:** a) Device has internet connection but no LoRaWAN Connection. or b) Device is in booting stage, in this stage, it will BLINKING GREEN for several seconds and then with BLINKING GREEN together
101 + ✓ **BLINKING GREEN:** a) Device has internet connection but no LoRaWAN Connection. or b) Device is in booting stage, in this stage, it will BLINKING GREEN for several seconds and then with BLINKING GREEN together
102 102  
103 - ✓**  SOLID RED:** Device doesn't have an Internet connection.
103 + ✓** SOLID RED:** Device doesn't have an Internet connection.
104 104  
105 105  (% style="color:blue" %)**➢ WIFI LED**(%%): This LED shows the WIFI interface connection status.
106 106  
... ... @@ -126,13 +126,6 @@
126 126  See this link for steps on how to clear data from the built-in server: **[[How to reset the built-in server>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/#H9.6A0Howtoresetthebuilt-inserver]]**
127 127  
128 128  
129 -When the gateway restores the factory settings is complete,
130 -
131 -The WiFi configuration will enable WiFi Access Point by default.
132 -
133 -The other configuration will be restored to the default configuration.
134 -
135 -
136 136  = 2. Quick Start =
137 137  
138 138  
... ... @@ -160,6 +160,7 @@
160 160  [[image:image-20230527085250-2.png||height="495" width="284"]]
161 161  
162 162  
156 +
163 163  ==== (% style="color:blue" %)**Method 2**(%%):  Connect via Ethernet with DHCP IP from the router ====
164 164  
165 165  
... ... @@ -174,6 +174,7 @@
174 174  [[image:image-20220622100129-1.png||height="332" width="1263"]]
175 175  
176 176  
171 +
177 177  ==== (% style="color:blue" %)**Method 3**(%%):  Connect via LPS8-V2 Fallback IP ====
178 178  
179 179  
... ... @@ -205,6 +205,7 @@
205 205  [[image:image-20230111094247-2.png||height="619" width="1250"]]
206 206  
207 207  
203 +
208 208  ==== (% style="color:blue" %)**Method 4**(%%):  Connect via WiFi with DHCP IP from the router ====
209 209  
210 210  [[image:image-20220622100542-2.png||height="369" width="1256"]]
... ... @@ -244,7 +244,7 @@
244 244  
245 245  (% style="color:blue" %)**Password:   dragino**
246 246  
247 -[[image:image-20240318160845-1.png]]
243 +[[image:image-20230106153501-1.png||height="367" width="894"]]
248 248  
249 249  
250 250  == 2.2  Typical Network Setup ==
... ... @@ -501,24 +501,10 @@
501 501  
502 502  [[image:image-20231031162927-2.png]]
503 503  
504 -=== 3.5.4 System ~-~-> Reboot / Reset ===
505 505  
506 -In the **System-> Reboot / Reset** interface, users can can restart or reset the gateway.
501 +=== 3.5.4 System ~-~-> Remoteit ===
507 507  
508 -ETH LED will SOLID BULE Until the restore is finished.
509 509  
510 -When the gateway restores the factory settings is complete,
511 -
512 -The WiFi configuration will enable WiFi Access Point by default.
513 -
514 -The other configuration will be restored to the default configuration.
515 -
516 -[[image:image-20240203172853-1.png||height="365" width="901"]]
517 -
518 -
519 -=== 3.5.5 System ~-~-> Remoteit ===
520 -
521 -
522 522  In the **System-> Remoteit** interface, users can configure the gateway to be accessed remotely via Remote.it.
523 523  
524 524  
... ... @@ -527,7 +527,7 @@
527 527  [[image:image-20221230092303-2.png]]
528 528  
529 529  
530 -=== 3.5.6 System ~-~-> Package Management ===
512 +=== 3.5.5 System ~-~-> Package Management ===
531 531  
532 532  
533 533  In the **System ~-~-> Package Management** interface, Users can check the current version of Core Packages.
... ... @@ -535,38 +535,6 @@
535 535  [[image:image-20230214094316-4.png]]
536 536  
537 537  
538 -== 3.5 Logread ==
539 -
540 -=== 3.5.1 LoRa Log ===
541 -
542 -
543 -In the **Lograde ~-~-> LoRa Log page**, The users can view information about the gateway lora channel and the status of the IoT connection
544 -
545 -[[image:image-20240416112509-1.png]]
546 -
547 -
548 -=== 3.5.2 Gateway Traffic ===
549 -
550 -In the **Lograde ~-~-> Gateway Traffic page**, The users can view sensor packages about Recent LoRa uplink/downlink/Join requests
551 -
552 -[[image:image-20240416112618-2.png||height="705" width="1122"]]
553 -
554 -
555 -=== 3.5.3 System Log ===
556 -
557 -In the **Lograde ~-~-> System Log page**, The users can view information about the gateway system
558 -
559 -[[image:image-20240416112649-3.png||height="820" width="1122"]]
560 -
561 -
562 -=== 3.5.4 Record Log ===
563 -
564 -In the **Lograde ~-~-> Recod Log page**, The users can record the gateway curren running log.
565 -
566 -[[image:image-20240416112712-4.png||height="319" width="1128"]]
567 -
568 -
569 -
570 570  = 4. Build-in Server =
571 571  
572 572  After the v1.7-230606 version, the LPS8-V2 default factory pre-installed the LoRaWAN Server: (% style="color:blue" %)**ChirpStack-V4**(%%), Application Server: (% style="color:blue" %)**Node-Red**(%%).
... ... @@ -700,6 +700,7 @@
700 700  
701 701  The uses can be via the below method to enable Watch Dog:
702 702  
653 +
703 703  (% class="box infomessage" %)
704 704  (((
705 705  wget -P /tmp/ http:~/~/repo.dragino.com/release/tool/watchdog/enable_watchdog.sh && chmod +x /tmp/enable_watchdog.sh && /tmp/enable_watchdog.sh
... ... @@ -708,6 +708,7 @@
708 708  [[image:image-20231124113209-1.png||height="470" width="1157"]]
709 709  
710 710  
662 +
711 711  = 6. How users can access LPS8-V2 using serial USB =
712 712  
713 713  
... ... @@ -761,6 +761,7 @@
761 761  
762 762  1). Using the Linux command to upgrade the system
763 763  
716 +
764 764  (% class="box infomessage" %)
765 765  (((
766 766  **apt update && apt install *dragino***
... ... @@ -769,11 +769,13 @@
769 769  
770 770  2). Upgrade the system via the Web page button of "Manual Update"
771 771  
772 -(% style="color:red" %)**Note: this method needs about 10 mins, so you will get the log after 10 mins.  **
773 773  
726 +**Note: this method needs about 10 mins, so you will get the log after 10 mins.  **
727 +
774 774  [[image:image-20230607093849-1.png]]
775 775  
776 776  
731 +
777 777  = 8. FAQ =
778 778  
779 779  == 8.1 How to change Hostname ==
... ... @@ -796,26 +796,33 @@
796 796  
797 797  Migrate guide:
798 798  
799 -To stabilize the completion of the migration, The users can migrate in one of the following ways
754 +**1. Ensure that the gateway is in good network condition, Recommended use of ETH.**
800 800  
801 -**Method 1. Using the Linux shell, **
756 +**2. On the Server ~-~-> Network Server interface, click "Management"**
802 802  
803 -**Method 2. Flash a new image with the Chirpstack**
758 +[[image:image-20230616162454-1.png]]
804 804  
805 805  
806 -=== Method 1: Using the Linux shell ===
761 +**3. Click "Migrate-Chirpstack"**
807 807  
808 -(% class="box infomessage" %)
809 -(((
810 -wget -P /tmp [[http:~~/~~/repo.dragino.com/release/tool/chirpstack/migrate_chirpstack>>http://repo.dragino.com/release/tool/chirpstack/migrate_chirpstack]] && chmod +x /tmp/migrate_chirpstack && /tmp/migrate_chirpstack
811 -)))
763 +[[image:image-20230616162742-2.png]]
812 812  
813 813  
814 -=== Method 2: Flash a new image ===
766 +**4. Strat Install **
815 815  
816 -Image flash steps: [[How to flash a new image(OS) to the gateway(LPS8V2)>>http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.3A0Howtoflashanewimage28OS29tothegateway28LPS8V229]]
768 +Click start Install and wait until the migration succeeds
817 817  
770 +[[image:image-20230616162934-3.png]]
818 818  
772 +
773 +**5.Migration complete check result**
774 +
775 +[[image:image-20230616174526-4.png||height="706" width="983"]]
776 +
777 +
778 +[[image:image-20230616180004-9.png]]
779 +
780 +
819 819  == 8.3 How to reduce the 4g data consumed ==
820 820  
821 821  
... ... @@ -860,7 +860,6 @@
860 860  
861 861  === 8.6.1 LoRaWAN Log: ===
862 862  
863 -
864 864  ==== Semtech UDP Log : ====
865 865  
866 866  When the gateway starts LoRaWAN Semtech UDP, users can check the logs of the Semtech UDP in the **LogRead ~-~-> System Log** interface
... ... @@ -877,9 +877,8 @@
877 877  
878 878  === 8.6.2  4G Log ===
879 879  
841 +The user needs to access the Linux console of the gateway and enter the following command:
880 880  
881 -User needs to access the Linux console of the gateway and enter the following command:
882 -
883 883  (% class="box infomessage" %)
884 884  (((
885 885  cat /var/log/qmilog.txt
... ... @@ -887,37 +887,8 @@
887 887  
888 888  [[image:image-20231017114417-3.png||height="543" width="679"]]
889 889  
890 -
891 -LPS8v2 use **quectel-CM** linux drive for dial up. The manual of this driver can be found here: [[**quectel-CM driver user manual**>>https://www.dropbox.com/scl/fi/73n2jl2c5r8h4i187to4n/Quectel_WCDMA_LTE_Linux_USB_Driver_User_Guide_V1.9-20190212.pdf?rlkey=j8834bw38d4neieisg54zngu9&st=kjsd4zx4&dl=0]].
892 -
893 -Below are some commands as reference:
894 -
895 -Usage:  /usr/bin/quectel-CM [options]
896 - -s [apn [user password auth]]  Set apn/user/password/auth get from your network provider. auth: 1~~pap, 2~~chap
897 - -p pincode Verify sim card pin if sim card is locked
898 - -p [quectel-][qmi|mbim]-proxy  Request to use proxy
899 - -f logfilename Save log message of this program to file
900 - -u usbmonlog filename  Save usbmon log to file
901 - -i interface Specify which network interface to setup data call when multi-modems exits
902 - -4 Setup IPv4 data call (default)
903 - -6 Setup IPv6 data call
904 - -k pdn Specify which pdn to hangup data call (by send SIGINT to 'quectel-CM -n pdn')
905 - -m iface-idx Bind QMI data call to wwan0_<iface idx> when QMAP used. E.g '-n 7 -m 1' bind pdn-7 data call to wwan0_1
906 - -b Enable network interface bridge function (default 0)
907 - -v Verbose log mode, for debug purpose.
908 -
909 -[Examples]
910 -Example 1: /usr/bin/quectel-CM
911 -Example 2: /usr/bin/quectel-CM -s 3gnet
912 -Example 3: /usr/bin/quectel-CM -s 3gnet -v
913 -
914 -
915 -
916 -
917 -
918 918  === 8.6.3 Dmesg Log ===
919 919  
920 -
921 921  Users can check the logs of the Dmesg in the **LogRead ~-~-> System Log** interface:
922 922  
923 923  [[image:image-20231017115330-5.png||height="565" width="740"]]
... ... @@ -925,82 +925,16 @@
925 925  
926 926  === 8.6.4 Record Log ===
927 927  
928 -
929 929  Users can record DMESG logs and LoRaWAN logs on the **LogRead ~-~->Record Log** interface
930 930  
931 931  [[image:image-20231017115124-4.png||height="215" width="880"]]
932 932  
933 933  
934 -=== 8.6.5 View gateway logs via Linux Command ===
935 -
936 -
937 -**Semtech UDP Log :**
938 -
939 -(% class="box infomessage" %)
940 -(((
941 -**journalctl -u draginofwd -f**
942 -)))
943 -
944 -[[image:image-20231207144627-1.png||height="371" width="1017"]]
945 -
946 -
947 -**Station Log:**
948 -
949 -(% class="box infomessage" %)
950 -(((
951 -**tail -f /var/log/station.log **
952 -)))
953 -
954 -[[image:image-20231207144758-2.png||height="132" width="1022"]]
955 -
956 -
957 -**Dmesg Log:**
958 -
959 -(% class="box infomessage" %)
960 -(((
961 -**dmesg**
962 -)))
963 -
964 -[[image:image-20231207145210-3.png||height="310" width="1021"]]
965 -
966 -
967 -== 8.7 DIN Mount Reference: ==
968 -
969 -
970 -[[image:image-20240318095605-1.jpeg||height="472" width="472"]]
971 -
972 -[[image:image-20240318095617-2.png]]
973 -
974 -
975 -== 8.8 NTP Service/Time Synchronization ==
976 -
977 -The gateway time sync service is provided by chrony service
978 -
979 -
980 -=== 1). Modify the NTP server address: ===
981 -
982 -(% class="box infomessage" %)
983 -(((
984 -Configuration file path:  /etc/chrony/chrony.conf
985 -)))
986 -
987 -
988 -=== 2). Start/Stop/Enable/Disable NTP service: ===
989 -
990 -(% class="box infomessage" %)
991 -(((
992 -systemctl start chrony
993 -\\systemctl stop chrony
994 -\\systemctl disable chrony
995 -\\systemctl enable chrony
996 -)))
997 -
998 -
999 -
1000 1000  = 9. Trouble Shooting =
1001 1001  
1002 1002  == 9.1  I can't log in to the built-in Server TTN Stack which shows '**Login failed**'. ==
1003 1003  
868 +
1004 1004  [[image:image-20220920135918-1.png]]
1005 1005  
1006 1006  
... ... @@ -1030,7 +1030,7 @@
1030 1030  When the computer has completed the above fallback IP configuration,the LPS8v2 Web UI is still not accessible via fallback IP.
1031 1031  
1032 1032  
1033 -**~1. Check whether the configuration is correct**
898 +**1.Check whether the configuration is correct**
1034 1034  
1035 1035  Run the CMD command to ipconfig and ping 172.31.255.254.
1036 1036  
... ... @@ -1060,6 +1060,7 @@
1060 1060  
1061 1061  Earlier versions of the LPS8V2 which missing the AP driver and not installed the fallback package, so the users have to do an extra update.
1062 1062  
928 +
1063 1063  (% class="box infomessage" %)
1064 1064  (((
1065 1065  apt update && apt install *dragino*
... ... @@ -1084,7 +1084,6 @@
1084 1084  
1085 1085  [[image:image-20231106180846-5.png||height="310" width="668"]]
1086 1086  
1087 -
1088 1088  = (% style="color:inherit; font-family:inherit; font-size:29px" %)10. Supports(%%) =
1089 1089  
1090 1090  
image-20231207144627-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -182.9 KB
Content
image-20231207144758-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -51.0 KB
Content
image-20231207145210-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -104.4 KB
Content
image-20240203172853-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -24.5 KB
Content
image-20240318095605-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -37.3 KB
Content
image-20240318095617-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -32.9 KB
Content
image-20240318160845-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.5 KB
Content
image-20240416112509-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -82.7 KB
Content
image-20240416112618-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -128.5 KB
Content
image-20240416112649-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -119.8 KB
Content
image-20240416112712-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -29.6 KB
Content
image-20240416112948-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -29.6 KB
Content

Applications

Navigation

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