Changes for page LPS8v2 -- LoRaWAN Indoor Gateway User Manual
Last modified by Kilight Cao on 2024/12/31 16:31
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 17 added, 0 removed)
- image-20231207144627-1.png
- image-20231207144758-2.png
- image-20231207145210-3.png
- image-20240203172853-1.png
- image-20240318095605-1.jpeg
- image-20240318095617-2.png
- image-20240318160845-1.png
- image-20240416112509-1.png
- image-20240416112618-2.png
- image-20240416112649-3.png
- image-20240416112712-4.png
- image-20240416112948-5.png
- image-20240518145859-1.png
- image-20240518145929-2.png
- image-20240518152100-3.png
- image-20240518152148-4.png
- image-20240518154223-5.png
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. Xiaoye1 +XWiki.Kilight - 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 ... ... @@ -18,7 +18,7 @@ 18 18 19 19 = 1. Introduction = 20 20 21 -== 1.1 What is LPS8v2 == 21 +== (% data-sider-select-id="66d5195f-ab1f-47c7-83cb-b027d0903e53" %)1.1 What is LPS8v2(%%) == 22 22 23 23 24 24 ((( ... ... @@ -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,6 +126,13 @@ 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 + 129 129 = 2. Quick Start = 130 130 131 131 ... ... @@ -153,7 +153,6 @@ 153 153 [[image:image-20230527085250-2.png||height="495" width="284"]] 154 154 155 155 156 - 157 157 ==== (% style="color:blue" %)**Method 2**(%%): Connect via Ethernet with DHCP IP from the router ==== 158 158 159 159 ... ... @@ -168,7 +168,6 @@ 168 168 [[image:image-20220622100129-1.png||height="332" width="1263"]] 169 169 170 170 171 - 172 172 ==== (% style="color:blue" %)**Method 3**(%%): Connect via LPS8-V2 Fallback IP ==== 173 173 174 174 ... ... @@ -200,7 +200,6 @@ 200 200 [[image:image-20230111094247-2.png||height="619" width="1250"]] 201 201 202 202 203 - 204 204 ==== (% style="color:blue" %)**Method 4**(%%): Connect via WiFi with DHCP IP from the router ==== 205 205 206 206 [[image:image-20220622100542-2.png||height="369" width="1256"]] ... ... @@ -240,7 +240,7 @@ 240 240 241 241 (% style="color:blue" %)**Password: dragino** 242 242 243 -[[image:image-202 30106153501-1.png||height="367" width="894"]]247 +[[image:image-20240318160845-1.png]] 244 244 245 245 246 246 == 2.2 Typical Network Setup == ... ... @@ -303,6 +303,9 @@ 303 303 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/LPS8N%20-%20LoRaWAN%20Gateway%20User%20Manual/WebHome/1657090932270-444.png?rev=1.1||alt="1657090932270-444.png"]] 304 304 305 305 310 +**Note: In most cases, the user simply types in the APN and checks the enable checkbox, without typing Pincode, Username, or Password settings.** 311 + 312 + 306 306 === 2.2.5 Check Internet connection === 307 307 308 308 ... ... @@ -497,10 +497,24 @@ 497 497 498 498 [[image:image-20231031162927-2.png]] 499 499 507 +=== 3.5.4 System ~-~-> Reboot / Reset === 500 500 501 - ===3.5.4System~-~-> Remoteit===509 +In the **System-> Reboot / Reset** interface, users can can restart or reset the gateway. 502 502 511 +ETH LED will SOLID BULE Until the restore is finished. 503 503 513 +When the gateway restores the factory settings is complete, 514 + 515 +The WiFi configuration will enable WiFi Access Point by default. 516 + 517 +The other configuration will be restored to the default configuration. 518 + 519 +[[image:image-20240203172853-1.png||height="365" width="901"]] 520 + 521 + 522 +=== 3.5.5 System ~-~-> Remoteit === 523 + 524 + 504 504 In the **System-> Remoteit** interface, users can configure the gateway to be accessed remotely via Remote.it. 505 505 506 506 ... ... @@ -509,7 +509,7 @@ 509 509 [[image:image-20221230092303-2.png]] 510 510 511 511 512 -=== 3.5. 5System ~-~-> Package Management ===533 +=== 3.5.6 System ~-~-> Package Management === 513 513 514 514 515 515 In the **System ~-~-> Package Management** interface, Users can check the current version of Core Packages. ... ... @@ -517,6 +517,38 @@ 517 517 [[image:image-20230214094316-4.png]] 518 518 519 519 541 +== 3.5 Logread == 542 + 543 +=== 3.5.1 LoRa Log === 544 + 545 + 546 +In the **Lograde ~-~-> LoRa Log page**, The users can view information about the gateway lora channel and the status of the IoT connection 547 + 548 +[[image:image-20240416112509-1.png]] 549 + 550 + 551 +=== 3.5.2 Gateway Traffic === 552 + 553 +In the **Lograde ~-~-> Gateway Traffic page**, The users can view sensor packages about Recent LoRa uplink/downlink/Join requests 554 + 555 +[[image:image-20240416112618-2.png||height="705" width="1122"]] 556 + 557 + 558 +=== 3.5.3 System Log === 559 + 560 +In the **Lograde ~-~-> System Log page**, The users can view information about the gateway system 561 + 562 +[[image:image-20240416112649-3.png||height="820" width="1122"]] 563 + 564 + 565 +=== 3.5.4 Record Log === 566 + 567 +In the **Lograde ~-~-> Recod Log page**, The users can record the gateway curren running log. 568 + 569 +[[image:image-20240416112712-4.png||height="319" width="1128"]] 570 + 571 + 572 + 520 520 = 4. Build-in Server = 521 521 522 522 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**(%%). ... ... @@ -545,31 +545,54 @@ 545 545 546 546 547 547 548 -**Troubleshooting:** 601 +== **3). Troubleshooting:** == 549 549 550 -**~ 1. If the URL does not jump properly.** 551 551 604 +* ((( 605 +=== ** If the URL does not jump properly.** === 606 +))) 607 + 552 552 For the ChirpStack, you can use the local IP address and the port is **8080** to access it. 553 553 554 554 For the Node-Red, you can use the local IP address and the port is **1880** to access it. 555 555 556 - **2. How to install InfluxDB, Garfana.** 557 557 558 - The LPS8V2 is not pre-installed InfluxDB and Garfana, the users can install them, see [[InfluxDB>>http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.6HowtoinstallGrafanaandinfluxdb]] 613 +* ((( 614 +=== ** How to install InfluxDB, Garfana.** === 615 +))) 559 559 560 - **3.Howtoupgade thegatewaynode.js tothe latest**617 + The LPS8V2 is not pre-installed with InfluxDB and Garfana, the users can install them, see [[InfluxDB>>http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.6HowtoinstallGrafanaandinfluxdb]] 561 561 562 - The user can upgrade nodejs, see [[Upgarde Nodejs>>http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.5Howtoupgradethenodejsversiontothelatest.]] 563 563 620 +* ((( 621 +=== ** How to upgrade the gateway node.js to the latest version.** === 622 +))) 564 564 624 + The user can upgrade nodejs, see [[Upgrade Nodejs>>http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.5Howtoupgradethenodejsversiontothelatest.]] 565 565 566 -== 4.3 How to disable the built-in server == 567 567 627 +* ((( 628 +=== ** How to batch register device on the built-in Chirpstack network server** === 629 +))) 568 568 569 - Use thefollowingcommandstostart andstopTTNv3service:631 + The user can register devices in batch on the gateway Web UI, see [[Batch Register>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H11.A0HowtouseChirpstackAPItobatchregisterSensorNode2FGatewayinChistapstackServer]] 570 570 633 + 634 +* ((( 635 +=== ** Why my gateway is not Chirpstack?** === 636 +))) 637 + 638 + After June '23, the default factory LPS8V2 pre-installed Chirpstack-V4 instead of The Things Stack, the users can migrate to Chistack-V4, see **[[Change TTN Stack v3 to ChirpStack>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/#H9.2Build-inTheThingsNetworkmigratetoChirpStack]]** 639 + 640 + 641 +* ((( 642 +=== ** How to disable the built-in server** === 643 +))) 644 + 571 571 (% class="box infomessage" %) 572 572 ((( 647 +Use the following commands to start and stop the TTNv3 service:** ** 648 + 573 573 **# start** 574 574 systemctl start ttnstack 575 575 ... ... @@ -583,10 +583,10 @@ 583 583 systemctl disable ttnstack 584 584 ))) 585 585 586 -Use the following commands to start and stop the Node-Red service: 587 - 588 588 (% class="box infomessage" %) 589 589 ((( 664 +Use the following commands to start and stop the Node-Red service: 665 + 590 590 **# start** 591 591 systemctl start nodered 592 592 ... ... @@ -601,21 +601,14 @@ 601 601 ))) 602 602 603 603 604 -== 4.4 Why my gateway is not Chirpstack? == 680 +* ((( 681 +=== ** How to choose the Chirpstack server frequency SubBand** === 682 +))) 605 605 684 +**~ ** The user has to choose a SubBand if using CN470, US915, AU915, or AS923. 606 606 607 - The newlyshipoutLPS8v2alreadyhave ChirpStackbuilt-inbydefault.Olderunitsmighthavebuilt-inTTNStackv3server,inthiscase,usercanchangefrom TTN Stack v3 toChirpStackby below instruction.686 + Note: Since the subbands of the Chirpstack are counted from 0, us915_1 of the Chirpstack is equal to US915 FSB2, so if your LoRa Rdio is using the US915 FSB2 you have to choose the us915_1 as the Chirpstack FSB. 608 608 609 -**[[Change TTN Stack v3 to ChirpStack>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/#H9.2Build-inTheThingsNetworkmigratetoChirpStack]]** 610 - 611 - 612 -=== 4.4.1 How do users choose the chirpstack server frequency SubBand === 613 - 614 - 615 -On the **Server ~-~-> Network Server** interface, choose the frequency Plan first. 616 - 617 -If the frequency Plan used is CN470, US915, AU915, or AS923, the user needs to choose a frequency sub-band, because the frequency Sub Band of ChirpStack starts from 0, so for example, us915_1 corresponds to the actual frequency US915_2. 618 - 619 619 [[image:image-20230602140406-3.png||height="480" width="918"]] 620 620 621 621 ... ... @@ -622,7 +622,7 @@ 622 622 When the configuration is complete, click** "Save&Apply"**. 623 623 624 624 625 -(% style="color:red" %)**Note:**(%%) When adding device profile, the selected Region configuration is also calculated from 0, so setting it to us915_1 corresponds to US915 Sub Band 2. 694 +(% style="color:red" %)**Note:**(%%) When adding the device profile, the selected Region configuration is also calculated from 0, so setting it to us915_1 corresponds to US915 Sub Band 2. 626 626 627 627 [[image:image-20230602143122-4.png||height="511" width="983"]] 628 628 ... ... @@ -634,7 +634,6 @@ 634 634 635 635 The uses can be via the below method to enable Watch Dog: 636 636 637 - 638 638 (% class="box infomessage" %) 639 639 ((( 640 640 wget -P /tmp/ http:~/~/repo.dragino.com/release/tool/watchdog/enable_watchdog.sh && chmod +x /tmp/enable_watchdog.sh && /tmp/enable_watchdog.sh ... ... @@ -643,7 +643,6 @@ 643 643 [[image:image-20231124113209-1.png||height="470" width="1157"]] 644 644 645 645 646 - 647 647 = 6. How users can access LPS8-V2 using serial USB = 648 648 649 649 ... ... @@ -697,7 +697,6 @@ 697 697 698 698 1). Using the Linux command to upgrade the system 699 699 700 - 701 701 (% class="box infomessage" %) 702 702 ((( 703 703 **apt update && apt install *dragino*** ... ... @@ -706,92 +706,250 @@ 706 706 707 707 2). Upgrade the system via the Web page button of "Manual Update" 708 708 775 +(% style="color:red" %)**Note: this method needs about 10 mins, so you will get the log after 10 mins. ** 709 709 710 -**Note: this method needs about 10 mins, so you will get the log after 10 mins. ** 711 - 712 712 [[image:image-20230607093849-1.png]] 713 713 714 714 780 +(% data-sider-select-id="65e92cfb-62df-4513-8469-b74edd72dea5" %) 781 += 8. More Services = 715 715 716 -= 8. FAQ=783 +== (% data-sider-select-id="6b164b64-51ae-4144-8ffd-5cd725b3bb5f" %)8.1 NTP Service/Time Synchronization(%%) == 717 717 718 - ==8.1 How to changeHostname==785 +The gateway time sync service is provided by chrony service 719 719 720 720 721 - Bydefault,Hostname isdragino-xxxxxx,If theuserneedsto changethe hostname, the userneeds to access the linux console of LPS8v2 andenterthe following command:788 +=== 1). Modify the NTP server address: === 722 722 723 723 (% class="box infomessage" %) 724 724 ((( 725 - hostnamectlset-hostname dragino-123456792 +Configuration file path: /etc/chrony/chrony.conf 726 726 ))) 727 727 728 -[[image:image-20230517102429-1.png]] 729 729 730 - Afterhe configuration iscomplete,run"reboot" torestartthe gateway.796 +=== 2). Start/Stop/Enable/Disable NTP service: === 731 731 798 +(% class="box infomessage" %) 799 +((( 800 +systemctl start chrony 801 +\\systemctl stop chrony 802 +\\systemctl disable chrony 803 +\\systemctl enable chrony 804 +))) 732 732 733 -== 8.2 Build-in The Things Network migrate to ChirpStack == 734 734 807 +== (% data-sider-select-id="de90793f-d833-4885-8b59-d0880f7256e6" %)8.2 How to connect the helium blockchain as a Data-only hotspot(%%) == 735 735 736 -Migrate guide: 737 737 738 -**1. Ensure that the gateway is in good network condition, Recommended use of ETH.** 810 +(% class="box infomessage" %) 811 +((( 812 +(% data-sider-select-id="3359233b-fcc9-4415-9bee-4151919fbb2e" %) 813 +apt update && apt install helium-gateway 814 +))) 739 739 740 -**2. On the Server ~-~-> Network Server interface, click "Management"** 741 741 742 -[[image:image-20230616162454-1.png]] 817 +(% data-sider-select-id="61881d06-3f91-437c-8b64-7032dea3c970" %) 818 += 9. More features = 743 743 820 +(% data-sider-select-id="692f00f1-a7cc-4954-ac62-0a5dddb0a0c6" %) 821 +== 9.1 How does the gateway connect to Chirpstack via MQTT Forwarder == 744 744 745 -**3. Click "Migrate-Chirpstack"** 746 746 747 - [[image:image-20230616162742-2.png]]824 +ChirpStack MQTT Forwarder is a MQTT packet forwarder for LoRa gateways. By default it forwards packets in Protobuf binary format, optionally it can be configured to use JSON encoding for debugging. In contrast to the ChirpStack Gateway Bridge, this component must always be installed on the gateway. 748 748 749 749 750 -**4. Strat Install ** 827 +(% data-sider-select-id="d2b54844-aad8-4198-9f17-841cd68db9b3" %) 828 +=== 9.1.1 Configure Packet Forwarder === 751 751 752 - Click startInstallandwait untilthemigrationsucceeds830 +In the Dragino web-interface, you must configure the Packet Forwarder such that it forwards to localhost on port 1700. 753 753 754 -[[image:image-20230616162934-3.png]] 832 +(% data-sider-select-id="48576a4e-42ef-4ac9-83b4-122fc10c6629" %) 833 +By default, the web-interface can be accessed by entering the following URL in your browser: (% data-sider-select-id="c2683c51-0bf8-4ac5-87be-c50edacc8f4b" %)**http:~/~/GATEWAY-IP-ADDRESS**(%%) (replace GATEWAY-IP-ADDRESS by the actual IP address of your gateway). The default credentials are root / dragino. 755 755 835 +* In the **LoRaWAN** menu, click **LoRaWAN ~-~- Semtech UDP** 836 +* Configure the following settings: 837 +** **Service Provider:** //Custom / Private LoRaWAN// 838 +** **Server Address:** localhost 839 +** **Uplink Port:** 1700 840 +** **Downlink Port:** 1700 841 +* Click **Save & Apply** 756 756 757 - **5.Migration completecheck result**843 +[[image:image-20240518145929-2.png||height="652" width="727"]] 758 758 759 -[[image:image-20230616174526-4.png||height="706" width="983"]] 760 760 846 +(% data-sider-select-id="716df9b1-d844-4797-bce9-9b1adf49b072" %) 847 +=== 9.1.2 Install ChirpStack MQTT Forwarder === 761 761 762 - [[image:image-20230616180004-9.png]]849 +==== ==== 763 763 851 +(% data-sider-select-id="2a752131-c23e-4da4-b142-5880dd688c39" %) 852 +(% data-sider-select-id="833bbe42-c175-4e13-ab7a-c8abc30378d0" %)**SSH login** 764 764 765 - ==8.3Howtoreducethe4gdataconsumed==854 +First you must login into the gateway using SSH: 766 766 856 +(% class="box infomessage" data-sider-select-id="608a94b0-8dee-453d-9433-5fe12c6559e5" %) 857 +((( 858 +ssh root@GATEWAY-IP-ADDRESS 859 +))) 767 767 768 -1). The gateway will check the network via ping 1.1.1.1/8.8.8.8 which will consume a lot of data, you can set the interval time to reduce data consume. 861 +(% data-sider-select-id="63adc977-8227-4585-ab1d-eea44a01c34c" %) 862 +The default password is: (% data-sider-select-id="5fad2844-9bd3-49e2-979b-ffd184b923cf" %)**dragino**(%%). 769 769 770 -[[image:image-20230719100239-1.png||height="724" width="994"]] 771 771 865 +(% data-sider-select-id="216fb9b4-6cee-4cb6-8b71-0a9cda3bd96a" %) 866 +(% data-sider-select-id="914750d6-03c5-48fe-ad27-49e99d95d877" %)**Download **(% data-sider-select-id="94e274ee-d341-40dc-8ca8-dc3c3b4c4981" %)**package** 772 772 773 -2. Change the LoRa status package interval time: It does not affect the connection between the gateway and the server, just the status packet interval 868 +(% data-sider-select-id="f95485e3-b535-4ea2-b0aa-0c46b5254782" %) 869 +Use the following commands to download the latest version of the ChirpStack MQTT Forwarder package: 774 774 775 -[[image:image-20230719100332-2.png]] 871 +(% class="box infomessage" data-sider-select-id="ab1338ab-a215-4185-8552-1efd6e067858" %) 872 +((( 873 +cd /tmp 874 +wget https:~/~/artifacts.chirpstack.io/downloads/chirpstack-mqtt-forwarder/chirpstack-mqtt-forwarder_4.3.0_linux_armhf.deb 875 +))) 776 776 777 777 778 -3. Disable the auto-update: 878 +(% data-sider-select-id="e59f1bad-427f-47b8-bc97-a818490576c4" %) 879 +(% data-sider-select-id="1b512eaf-c564-4835-afac-548b9a6a7045" %)**Install ** 779 779 780 - [[image:image-20230719100419-3.png||height="458"width="995"]]881 +Use the dpkg package-manager to install the downloaded package. Example: 781 781 883 +(% class="box infomessage" data-sider-select-id="7e7ff0cf-c367-4ff0-9387-f4eb82f3c89e" %) 884 +((( 885 +dpkg -i chirpstack-mqtt-forwarder_4.3.0_linux_armhf.deb 886 +))) 782 782 783 - == 8.4 How to connect the heliumblockchainas a Data-only hotspot ==888 +[[image:image-20240518152148-4.png]] 784 784 785 785 891 +(% data-sider-select-id="69e4a485-6ea8-46e7-97a3-8666bc9423a7" %) 892 +**Configuration** 893 + 894 +To connect the ChirpStack MQTT Forwarder to your MQTT broker, you must update the ChirpStack MQTT Forwarder configuration file. 895 + 896 +(% data-sider-select-id="e98443ef-dcc1-4be1-ad3e-ec31b0a580b4" %) 897 +This file is located at: (% data-sider-select-id="60301edc-5082-44e9-a91a-688327092116" %)**/etc/chirpstack-mqtt-forwarder/chirpstack-mqtt-forwarder.toml** 898 + 899 + 900 +**ChirpStack MQTT Forwarder Setting:** 901 + 902 +(% class="box" data-sider-select-id="1d70062d-64ab-410b-bd8e-476c73d5dd70" %) 903 +((( 904 +topic_prefix ~-~-> This corresponds to the frequency of the ChirpStack server 905 + 906 +server ~-~-> Fill in the ChirpStack server address, Example: tcp:~/~/10.130.2.15:1883 907 +))) 908 + 909 +username,password,ca_cert,tls_cert,tls_key parameters should be set as required. 910 + 911 + 912 +Use commands to modify configuration files: 913 + 914 +(% class="box infomessage" data-sider-select-id="d552b27f-cfd2-4f5a-9b7f-b627f5dd3387" %) 915 +((( 916 +vim /etc/chirpstack-mqtt-forwarder/chirpstack-mqtt-forwarder.toml 917 +))) 918 + 919 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/LPS8N%20-%20LoRaWAN%20Gateway%20User%20Manual/WebHome/image-20240518141059-6.png?rev=1.1||alt="image-20240518141059-6.png"]] 920 + 921 + 922 +**(Re)start and stop commands** 923 + 924 +Use the following commands to (re)start and stop the ChirpStack MQTT Forwarder service: 925 + 926 +(% class="box infomessage" data-sider-select-id="61c3c343-2cb9-4b07-8741-5d5da2d88ec3" %) 927 +((( 928 +# start 929 + 930 +(% data-sider-select-id="5482a31e-3aa0-403c-aec5-117839958068" %) 931 +systemctl start chirpstack-mqtt-forwarder 932 + 933 +# stop 934 + 935 +systemctl stop chirpstack-mqtt-forwarder 936 + 937 +# restart 938 + 939 +systemctl restart chirpstack-mqtt-forwarder 940 +))) 941 + 942 +(% data-sider-select-id="1cea423f-9653-47e6-8022-aadcb684f191" %) 943 +(% data-sider-select-id="f385e712-68bc-48fd-8b94-67a0c7e7cb70" %)**Note: If the LPS8v2 built-in server is running, it will cause a port conflict** 944 + 945 + 946 +**Check result** 947 + 948 +(% data-sider-select-id="43d1d40a-2620-4547-b00d-f78dd5427215" %) 949 +Use "** journalctl -u chirpstack-mqtt-forwarder -f(% data-sider-select-id="ab74df8a-b859-4afa-9c26-d0807e860e6c" %) (%%)**" to check the operation of ChirpStack MQTT Forwarder. 950 + 951 +[[image:image-20240518154223-5.png]] 952 + 953 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/LPS8N%20-%20LoRaWAN%20Gateway%20User%20Manual/WebHome/image-20240518143050-8.png?width=1170&height=702&rev=1.1||alt="image-20240518143050-8.png"]] 954 + 955 + 956 += (% data-sider-select-id="20d4ea6b-7328-46c6-bc97-f0050cfe382e" %)10. FAQ(%%) = 957 + 958 +== (% data-sider-select-id="9fbcac50-3c87-43d9-8611-8d311fcb7820" %)10.1 How to change Hostname(%%) == 959 + 960 + 961 +By default, Hostname is dragino-xxxxxx,If the user needs to change the hostname, the user needs to access the linux console of LPS8v2 and enter the following command: 962 + 786 786 (% class="box infomessage" %) 787 787 ((( 788 - aptupdate&& aptinstallhelium-gateway965 +hostnamectl set-hostname dragino-123456 789 789 ))) 790 790 968 +[[image:image-20230517102429-1.png]] 791 791 792 - ==8.5 Howtochange built-inLoRaWANServerfromChirpStackv4toTTN Stack v3.==970 +After the configuration is complete, run "reboot" to restart the gateway. 793 793 794 794 973 +== (% data-sider-select-id="20d4ea6b-7328-46c6-bc97-f0050cfe382e" %)10(% data-sider-select-id="62cdc3f4-fb6f-4e4d-92a5-60449c8b462f" %).2 Build-in The Things Network migrate to ChirpStack(%%) == 974 + 975 + 976 +Migrate guide: 977 + 978 +To stabilize the completion of the migration, The users can migrate in one of the following ways 979 + 980 +**Method 1. Using the Linux shell, ** 981 + 982 +**Method 2. Flash a new image with the Chirpstack** 983 + 984 + 985 +=== Method 1: Using the Linux shell === 986 + 987 +(% class="box infomessage" %) 988 +((( 989 +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 990 +))) 991 + 992 + 993 +=== Method 2: Flash a new image === 994 + 995 +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]] 996 + 997 + 998 +== (% data-sider-select-id="20d4ea6b-7328-46c6-bc97-f0050cfe382e" %)10(% data-sider-select-id="b2a44672-8abb-425d-a823-f2faa334cdb7" %).3 How to reduce the 4g data consumed(%%) == 999 + 1000 + 1001 +1). The gateway will check the network via ping 1.1.1.1/8.8.8.8 which will consume a lot of data, you can set the interval time to reduce data consume. 1002 + 1003 +[[image:image-20230719100239-1.png||height="724" width="994"]] 1004 + 1005 + 1006 +2. Change the LoRa status package interval time: It does not affect the connection between the gateway and the server, just the status packet interval 1007 + 1008 +[[image:image-20230719100332-2.png]] 1009 + 1010 + 1011 +3. Disable the auto-update: 1012 + 1013 +[[image:image-20230719100419-3.png||height="458" width="995"]] 1014 + 1015 + 1016 +== (% data-sider-select-id="20d4ea6b-7328-46c6-bc97-f0050cfe382e" %)10(% data-sider-select-id="457c03ce-1aaa-44c6-bf8e-0298ca8045e4" %).4 How to change built-in LoRaWAN Server from ChirpStack v4 to TTN Stack v3.(%%) == 1017 + 1018 + 795 795 By default, the LPS8v2's built-in server is ChirpStack v4, 796 796 797 797 If the user needs to change the built-in server from ChirpStack v4 to TTN Stack v3, the User needs to download the image and flash it to the LPS8v2 gateway: ... ... @@ -802,10 +802,11 @@ 802 802 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]] 803 803 804 804 805 -== 8.6 How do I view gateway logs == 1029 +== (% data-sider-select-id="20d4ea6b-7328-46c6-bc97-f0050cfe382e" %)10(% data-sider-select-id="f31494a0-5f58-4b5c-820e-9cb1be76d96f" %).6 How do I view gateway logs(%%) == 806 806 807 -=== 8.6.1 LoRaWAN Log: === 1031 +=== (% data-sider-select-id="20d4ea6b-7328-46c6-bc97-f0050cfe382e" %)10(% data-sider-select-id="2c782a3d-7138-45c4-bbdf-09c0e27ef896" %).6.1 LoRaWAN Log:(%%) === 808 808 1033 + 809 809 ==== Semtech UDP Log : ==== 810 810 811 811 When the gateway starts LoRaWAN Semtech UDP, users can check the logs of the Semtech UDP in the **LogRead ~-~-> System Log** interface ... ... @@ -820,10 +820,11 @@ 820 820 [[image:image-20231017111606-1.png||height="622" width="821"]] 821 821 822 822 823 -=== 8.6.2 4G Log === 1048 +=== (% data-sider-select-id="de76f982-b2e5-4327-aab4-8890814f5f53" %)9.6.2 4G Log(%%) === 824 824 825 -The user needs to access the Linux console of the gateway and enter the following command: 826 826 1051 +User needs to access the Linux console of the gateway and enter the following command: 1052 + 827 827 (% class="box infomessage" %) 828 828 ((( 829 829 cat /var/log/qmilog.txt ... ... @@ -831,25 +831,93 @@ 831 831 832 832 [[image:image-20231017114417-3.png||height="543" width="679"]] 833 833 834 -=== 8.6.3 Dmesg Log === 835 835 1061 +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]]. 1062 + 1063 +Below are some commands as reference: 1064 + 1065 +>Usage: /usr/bin/quectel-CM [options] 1066 +> -s [apn [user password auth]] Set apn/user/password/auth get from your network provider. auth: 1~~pap, 2~~chap 1067 +> -p pincode Verify sim card pin if sim card is locked 1068 +> -p [quectel-][qmi|mbim]-proxy Request to use proxy 1069 +> -f logfilename Save log message of this program to file 1070 +> -u usbmonlog filename Save usbmon log to file 1071 +> -i interface Specify which network interface to setup data call when multi-modems exits 1072 +> -4 Setup IPv4 data call (default) 1073 +> -6 Setup IPv6 data call 1074 +> -k pdn Specify which pdn to hangup data call (by send SIGINT to 'quectel-CM -n pdn') 1075 +> -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 1076 +> -b Enable network interface bridge function (default 0) 1077 +> -v Verbose log mode, for debug purpose.[Examples] 1078 +>Example 1: /usr/bin/quectel-CM 1079 +>Example 2: /usr/bin/quectel-CM -s 3gnet 1080 +>Example 3: /usr/bin/quectel-CM -s 3gnet -v 1081 + 1082 + 1083 + 1084 +=== (% data-sider-select-id="ec43d85c-19ec-48b0-a4fc-0ecd76f17fc4" %)9.6.3 Dmesg Log(%%) === 1085 + 1086 + 836 836 Users can check the logs of the Dmesg in the **LogRead ~-~-> System Log** interface: 837 837 838 838 [[image:image-20231017115330-5.png||height="565" width="740"]] 839 839 840 840 841 -=== 8.6.4 Record Log === 1092 +=== (% data-sider-select-id="3a977a3e-9417-40fa-bdfb-2544a88744a9" %)9.6.4 Record Log(%%) === 842 842 1094 + 843 843 Users can record DMESG logs and LoRaWAN logs on the **LogRead ~-~->Record Log** interface 844 844 845 845 [[image:image-20231017115124-4.png||height="215" width="880"]] 846 846 847 847 848 -= 9.TroubleShooting=1100 +=== (% data-sider-select-id="b988f832-4b37-4a61-b951-ff2138ad9cba" %)9.6.5 View gateway logs via Linux Command(%%) === 849 849 850 -== 9.1 I can't log in to the built-in Server TTN Stack which shows '**Login failed**'. == 851 851 1103 +**Semtech UDP Log :** 852 852 1105 +(% class="box infomessage" %) 1106 +((( 1107 +**journalctl -u draginofwd -f** 1108 +))) 1109 + 1110 +[[image:image-20231207144627-1.png||height="371" width="1017"]] 1111 + 1112 + 1113 +**Station Log:** 1114 + 1115 +(% class="box infomessage" %) 1116 +((( 1117 +**tail -f /var/log/station.log ** 1118 +))) 1119 + 1120 +[[image:image-20231207144758-2.png||height="132" width="1022"]] 1121 + 1122 + 1123 +**Dmesg Log:** 1124 + 1125 +(% class="box infomessage" %) 1126 +((( 1127 +**dmesg** 1128 +))) 1129 + 1130 +[[image:image-20231207145210-3.png||height="310" width="1021"]] 1131 + 1132 + 1133 +== (% data-sider-select-id="82550df9-987d-4f58-9877-86a0c5e621a4" %)9.5 DIN Mount Reference:(%%) == 1134 + 1135 + 1136 +[[image:image-20240318095605-1.jpeg||height="472" width="472"]] 1137 + 1138 +[[image:image-20240318095617-2.png]] 1139 + 1140 + 1141 + 1142 + 1143 += (% data-sider-select-id="9b024263-b754-45b6-ac15-22f86a4e1436" %)10. Trouble Shooting(%%) = 1144 + 1145 +== (% data-sider-select-id="cb7a0b2f-4144-4f58-86d0-64a15944840e" %)10.1 I can't log in to the built-in Server TTN Stack which shows '**Login failed**'.(%%) == 1146 + 853 853 [[image:image-20220920135918-1.png]] 854 854 855 855 ... ... @@ -865,7 +865,7 @@ 865 865 [[image:image-20220920141936-2.png]] 866 866 867 867 868 -== 9.2 The built-in TTN status is "Not Running" and the URI is "dragino-123456". How users fix this problem == 1162 +== (% data-sider-select-id="cb7a0b2f-4144-4f58-86d0-64a15944840e" %)10(% data-sider-select-id="f34b4950-25aa-4a6d-a2b4-4af0ec0010a7" %).2 The built-in TTN status is "Not Running" and the URI is "dragino-123456". How users fix this problem(%%) == 869 869 870 870 871 871 When this problem occurs, click "**Update To DEFAULT**" ,this problem will be fixed. ... ... @@ -873,13 +873,13 @@ 873 873 [[image:image-20230508171607-1.png]] 874 874 875 875 876 -== 9.3 Fallback IP does not work, how can users check == 1170 +== (% data-sider-select-id="cb7a0b2f-4144-4f58-86d0-64a15944840e" %)10(% data-sider-select-id="a7b8cd40-2ec5-4b4b-8220-d32ce0a303a0" %).3 Fallback IP does not work, how can users check(%%) == 877 877 878 878 879 879 When the computer has completed the above fallback IP configuration,the LPS8v2 Web UI is still not accessible via fallback IP. 880 880 881 881 882 -**1.Check whether the configuration is correct** 1176 +**~1. Check whether the configuration is correct** 883 883 884 884 Run the CMD command to ipconfig and ping 172.31.255.254. 885 885 ... ... @@ -895,7 +895,7 @@ 895 895 If the firewall is not down, this will affect access to the gateway. 896 896 897 897 898 -== 9.4 Click "Manual_Update", why there is no response? == 1192 +== (% data-sider-select-id="cb7a0b2f-4144-4f58-86d0-64a15944840e" %)10(% data-sider-select-id="b7eec45b-ad8c-4621-a815-f457810d25f4" %).4 Click "Manual_Update", why there is no response?(%%) == 899 899 900 900 901 901 When you click "Manual_Update", the gateway will finish updating within 10 minutes and display the update log. ... ... @@ -904,12 +904,11 @@ 904 904 [[image:image-20230527090555-3.png||height="660" width="832"]] 905 905 906 906 907 -== 9.5 Why the LPS8V2's Access Point does not do not appear & Fallback IP unable to access == 1201 +== (% data-sider-select-id="cb7a0b2f-4144-4f58-86d0-64a15944840e" %)10(% data-sider-select-id="ac1f33b3-1f28-477d-880c-534ac36adcbe" %).5 Why the LPS8V2's Access Point does not do not appear & Fallback IP unable to access(%%) == 908 908 909 909 910 910 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. 911 911 912 - 913 913 (% class="box infomessage" %) 914 914 ((( 915 915 apt update && apt install *dragino* ... ... @@ -918,7 +918,7 @@ 918 918 ))) 919 919 920 920 921 -== 9.6 How to reset the built-in server == 1214 +== (% data-sider-select-id="cb7a0b2f-4144-4f58-86d0-64a15944840e" %)10(% data-sider-select-id="0621ef51-7fc1-47ca-86ee-cc1f28f6754b" %).6 How to reset the built-in server(%%) == 922 922 923 923 924 924 **1) Build-in The Things Network** ... ... @@ -934,9 +934,10 @@ 934 934 935 935 [[image:image-20231106180846-5.png||height="310" width="668"]] 936 936 937 -= (% style="color:inherit; font-family:inherit; font-size:29px" %)10. Supports(%%) = 938 938 1231 += (% data-sider-select-id="7e5e9cb1-c1dc-4ea9-a9f7-9da676c581a5" style="color:inherit; font-family:inherit; font-size:29px" %)10. Supports(%%) = 939 939 1233 + 940 940 ((( 941 941 If you are experiencing issues and can't solve them, you can send mail to [[support@dragino.com>>mailto:support@dragino.com]]. 942 942 )))
- image-20231207144627-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +182.9 KB - Content
- image-20231207144758-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +51.0 KB - Content
- image-20231207145210-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +104.4 KB - Content
- image-20240203172853-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +24.5 KB - Content
- image-20240318095605-1.jpeg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +37.3 KB - Content
- image-20240318095617-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.9 KB - Content
- image-20240318160845-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +36.5 KB - Content
- image-20240416112509-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoye - Size
-
... ... @@ -1,0 +1,1 @@ 1 +82.7 KB - Content
- image-20240416112618-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoye - Size
-
... ... @@ -1,0 +1,1 @@ 1 +128.5 KB - Content
- image-20240416112649-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoye - Size
-
... ... @@ -1,0 +1,1 @@ 1 +119.8 KB - Content
- image-20240416112712-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoye - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.6 KB - Content
- image-20240416112948-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoye - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.6 KB - Content
- image-20240518145859-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +59.7 KB - Content
- image-20240518145929-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +59.5 KB - Content
- image-20240518152100-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +39.5 KB - Content
- image-20240518152148-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.0 KB - Content
- image-20240518154223-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +71.7 KB - Content