Changes for page LPS8v2 -- LoRaWAN Indoor Gateway User Manual

Last modified by Kilight Cao on 2024/12/31 16:31

From version < 308.1 >

edited by Xiaoye
on 2024/05/07 14:10

To version < 187.1 >

edited by Xiaoye
on 2023/04/25 15:56

Change comment: Uploaded new attachment "image-20230425155612-7.png", version {1}

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 59 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--LPS8v2 -- LoRaWAN Indoor Gateway User Manual
++LPS8v2 LoRaWAN Indoor Gateway User Manual

Content

@@ -8,7 +8,7 @@
  )))
--**Table of Contents:**
++**Table of Contents：**
  {{toc/}}
@@ -23,15 +23,15 @@
  (((
  (((
--The LPS8v2 is an (% style="color:blue" %)**open-source LoRaWAN Gateway**(%%). It lets you bridge LoRa wireless network to an IP network via (% style="color:blue" %)**WiFi , Ethernet or Cellular Network**(%%) (via Optional 4G module). The LoRa wireless allows users to send data and reach extremely long ranges at low data rates.
++The LPS8v2 is an (% style="color:green" %)**open-source LoRaWAN Gateway**(%%). It lets you bridge LoRa wireless network to an IP network via (% style="color:green" %)**WiFi , Ethernet or Cellular Network**(%%) (via Optional 4G module). The LoRa wireless allows users to send data and reach extremely long ranges at low data rates.
  )))
  (((
--The LPS8v2 is fully compatible with LoRaWAN protocol. It supports different kinds of LoRaWAN Network Connections such as: (% style="color:blue" %)**Semtech UDP Packet Forwarder, LoRaWAN Basic Station, ChirpStack MQTT Bridge**(%%), and so on. This makes LPS8V2 work with most LoRaWAN platforms in the market.
++The LPS8v2 is fully compatible with LoRaWAN protocol. It supports different kinds of LoRaWAN Network Connections such as: (% style="color:green" %)**Semtech UDP Packet Forwarder, LoRaWAN Basic Station, ChirpStack MQTT Bridge**(%%), and so on. This makes LPS8V2 work with most LoRaWAN platforms in the market.
  )))
  (((
--LPS8v2 also includes a (% style="color:blue" %)**built-in LoRaWAN Server and IoT server**(%%), which provide the possibility for the system integrator to deploy the IoT service without cloud service or 3rd servers.
++LPS8v2 also includes a (% style="color:green" %)**built-in LoRaWAN Server and IoT server**(%%), which provide the possibility for the system integrator to deploy the IoT service without cloud service or 3rd servers.
  )))
  (((
@@ -39,7 +39,7 @@
  )))
  (((
--LPS8v2 supports (% style="color:blue" %)**remote management**(%%). System Integrator can easy to remote monitor the gateway and maintain it.
++LPS8v2 supports (% style="color:green" %)**remote management**(%%). System Integrator can easy to remote monitor the gateway and maintain it.
  )))
@@ -66,6 +66,8 @@
  * Storage Temperature: -20 ~~ 70°C
  * Power Input: 5V, 2A, DC
++
++
  == 1.3 Features ==
@@ -81,58 +81,52 @@
  ** Semtech UDP Packet Forwarder
  ** LoRaWAN Basic Station
  ** ChirpStack-Gateway-Bridge (MQTT)
--* Built-in (% style="color:#037691" %)**ChirpStack**(%%) local LoRaWAN server
--* Built-in  (% style="color:#037691" %)**Node-Red** (%%)local Application server
++* Built-in (% style="color:#037691" %)//**The Things Network**//(%%) local LoRaWAN server
++* Built-in  (% style="color:#037691" %)//**Node-Red**// (%%)local Application server
--== 1.4 LED Indicators ==
--LPS8-V2 has totally four LEDs, They are:
++== 1.4 Block Diagram ==
--(% style="color:blue" %)**➢ Power LED**(%%): This RED LED will be solid if the device is properly powered
--(% style="color:blue" %)**➢ ETH LED**(%%):   This RGB LED will blink GREEN when the ETH port is connecting
++== 1.5 LED Indicators ==
--(% style="color:blue" %)**➢ SYS LED**(%%):   This RGB LED will show different colors in different states:
--                     ✓    **SOLID GREEN:** The device is alive with a LoRaWAN server connection.
++LPS8-V2 has totally four LEDs, They are:
--                     ✓    **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
--                     ✓**    SOLID RED:** Device doesn't have an Internet connection.
++(% style="color:blue" %)//**➢ Power LED**//(%%)//: This RED LED will be solid if the device is properly powered//
--(% style="color:blue" %)**➢ WIFI LED**(%%): This LED shows the WIFI interface connection status.
++(% style="color:blue" %)//**➢ ETH LED**//(%%)//:   This RGB LED will blink GREEN when the ETH port is connecting//
++(% style="color:blue" %)//**➢ SYS LED**//(%%)//:   This RGB LED will show different colors in different states~://
--== 1.5 Button Intruction ==
++//                     ✓ **SOLID GREEN:** The device is alive with a LoRaWAN server connection.//
++//                     ✓ **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//
--LPS8-V2 has a black toggle button, which is:
++//                     ✓** SOLID RED:** Device doesn't have an Internet connection.//
++(% style="color:blue" %)//**➢ WIFI LED**//(%%)//: This LED shows the WIFI interface connection status.//
--(% style="color:blue" %)**//➢ //Long press 4-5s                   : **(%%)the gateway will reload the Network and Initialize wifi configuration
--                            //                         // **LED status: ** ETH LED will BLINKIND BULE Until the reload is finished.
++== 1.6 Button Intruction ==
--(% style="color:blue" %)**➢ Long press more than 10s:**(%%)**    **the gateway will restore the factory settings.
++LPS8-V2 has a black toggle button, which is:
--                                                     **LED status: ** ETH LED will SOLID BULE Until the restore is finished.
++(% style="color:blue" %)**//➢ //Long press 4-5s                   : **(%%)the gateway will reload the Network and Initialize wifi configuration
--(% style="color:red" %)**Note: Restoring factory Settings does not erase data from the LPS8-V2 built-in server**
++                            //                          **LED status: ** ETH LED will BLINKIND BULE Until the reload is finished.//
--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]]**
++(% style="color:blue" %)//**➢ **//**Long press more than 10s:**(%%)**    **//the gateway will restore the factory settings.//
--When the gateway restores the factory settings is complete,
++                                                     //**LED status: ** ETH LED will SOLID BULE Until the restore is finished.//
--The WiFi configuration will enable WiFi Access Point by default.
--The other configuration will be restored to the default configuration.
--
--
  = 2. Quick Start =
@@ -141,28 +141,14 @@
  In most cases, the first thing you need to do is make the lps8-v2 accessible to the network.
--== 2.1 Access and Configure LPS8-V2 ==
++== 2.1 Connects to the network and accesses the gateway Web UI ==
--=== 2.1.1 Find IP address of LPS8-V2 ===
++=== 2.1.1 connect the network ===
--==== (% style="color:blue" %)**Method 1**(%%):  Connect via LPS8-V2 WiFi ====
++==== (% style="color:blue" %)**Method 1**(%%):  Connect via Ethernet with DHCP IP from the router ====
--Since software version **230524**,At the first boot of LPS8-V2, it will auto generate a WiFi network called (% style="color:green" %)**//dragino-xxxxxx //**(%%)with password:
--
--(% style="background-color:yellow" %)**dragino+dragino**
--
--User can use a PC to connect to this WiFi network. The PC will get an IP address 10.130.1.xxx and the LPS8-V2 has the default IP (% style="color:green" %)**10.130.1.1**
--
--[[image:image-20230527084515-1.png]]
--
--[[image:image-20230527085250-2.png||height="495" width="284"]]
--
--
--==== (% style="color:blue" %)**Method 2**(%%):  Connect via Ethernet with DHCP IP from the router ====
--
--
  (((
  Connect the LPS8-V2 Ethernet port to your router and LPS8-V2 can obtain an IP address from your router. In the router's management portal, you should be able to find what IP address the router has assigned to the LPS8-V2.
  )))
@@ -174,9 +174,10 @@
  [[image:image-20220622100129-1.png||height="332" width="1263"]]
--==== (% style="color:blue" %)**Method 3**(%%):  Connect via LPS8-V2 Fallback IP ====
++==== (% style="color:blue" %)**Method 2**(%%):  Connect via LPS8-V2 Fallback IP ====
++
  [[image:image-20230107084650-2.png||height="310" width="839"]]
@@ -187,7 +187,7 @@
 . Configure PC's Ethernet port has IP: 172.31.255.253 and Netmask: 255.255.255.252
--**Settings ~-~-> Network & Internet ~-~-> Ethernet ~-~-> Change advanced sharing options ~-~-> Double-click"Ethernet" ~-~-> Internet Protocol Version 4 (TCP/IPv4)**
++Settings ~-~-> Network & Internet ~-~-> Ethernet ~-~-> Change advanced sharing options ~-~-> Double-click"Ethernet" ~-~-> Internet Protocol Version 4 (TCP/IPv4)
  As in the below photo:
@@ -197,7 +197,7 @@
  Configure computer Ethernet port steps video: **[[attach:fallback ip.mp4||target="_blank"]]**
--If you still can't access the LPS8-V2 fallback ip, follow this connection to debug : **[[Trouble Shooting>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/#H9.3A0FallbackIPdoesnotwork2Chowcanuserscheck]]**
++If you still can't access the LPS8-V2 fallback ip, follow this connection to debug :**[[Trouble Shooting>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/#H9.2A0FallbackIPdoesnotwork2Chowcanuserscheck]]**
 . In the PC, use IP address 172.31.255.254 to access the LPS8-V2 via Web or Console.
@@ -205,8 +205,9 @@
  [[image:image-20230111094247-2.png||height="619" width="1250"]]
--==== (% style="color:blue" %)**Method 4**(%%):  Connect via WiFi with DHCP IP from the router ====
++==== (% style="color:blue" %)**Method 3**(%%):  Connect via WiFi with DHCP IP from the router ====
++
  [[image:image-20220622100542-2.png||height="369" width="1256"]]
@@ -240,11 +240,11 @@
  The account details for Web Login are:
--(% style="color:blue" %)**User Name: root**
++(% style="color:#4f81bd" %)**User Name: root**
--(% style="color:blue" %)**Password:   dragino**
++(% style="color:#4f81bd" %)**Password:   dragino**
--[[image:image-20240318160845-1.png]]
++[[image:image-20230106153501-1.png||height="367" width="894"]]
  == 2.2  Typical Network Setup ==
@@ -255,9 +255,7 @@
  LPS8-V2 supports flexible network set up for different environment. This section describes the typical network topology can be set in LPS8-V2. The typical network set up includes:
  * **WAN Port Internet Mode**
--
  * **WiFi Client Mode**
--
  * **Cellular Mode**
  === 2.2.2  Use WAN port to access Internet ===
@@ -307,12 +307,8 @@
  [[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"]]
--**Note: In most cases, the user simply types in the APN and checks the enable checkbox, without typing Pincode, Username, or Password settings.**
--
--
  === 2.2.5  Check Internet connection ===
--
  In the **home** page, we can check the Internet connection.
  * GREEN Tick  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/LPS8N%20-%20LoRaWAN%20Gateway%20User%20Manual/WebHome/1652436675869-206.png?width=15&height=14&rev=1.1||alt="1652436675869-206.png"]]  : This interface has Internet connection.
@@ -381,7 +381,7 @@
  == 3.1 Home ==
--Shows the system running status:
++//Shows the system running status~://
  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/WebHome/image-20220622102901-8.png?rev=1.1||alt="image-20220622102901-8.png" height="476" width="939"]]
@@ -391,15 +391,15 @@
  === 3.2.1 LoRa ~-~-> LoRa ===
--This page shows the LoRa Radio Settings. There is a set of default frequency bands according to LoRaWAN protocol, and users can customize the band* as well.
++//This page shows the LoRa Radio Settings. There is a set of default frequency bands according to LoRaWAN protocol, and users can customize the band* as well.//
--Different LPS8v2 hardware versions can support different frequency ranges:
++//Different LPS8v2 hardware versions can support different frequency ranges~://
--* (% style="color:#0000ff" %)**868**(% style="color:black" %): valid frequency: 863Mhz ~~ 870Mhz. for bands EU868, RU864, IN865, or KZ865.
--* (% style="color:#0000ff" %)**915**(% style="color:black" %): valid frequency: 902Mhz ~~ 928Mhz. for bands US915, AU915, AS923 or KR920
++* (% style="color:#0000ff" %)//**868**//(% style="color:black" %)//: valid frequency: 863Mhz ~~ 870Mhz. for bands EU868, RU864, IN865, or KZ865.//
++* (% style="color:#0000ff" %)//**915**//(% style="color:black" %)//: valid frequency: 902Mhz ~~ 928Mhz. for bands US915, AU915, AS923 or KR920//
  (% class="wikigeneratedid" %)
--After the user choose the frequency plan,  the user can see the actual frequency is used by checking the page (% style="color:#037691" %)**LogRead ~-~-> LoRa Log**
++//After the user choose the frequency plan,  the user can see the actual frequency is used by checking the page (% style="color:#037691" %)**LogRead ~-~-> LoRa Log**//
  (% class="wikigeneratedid" %)
@@ -416,7 +416,7 @@
  === 3.3.1 LoRaWAN ~-~-> LoRaWAN Semtech UDP ===
--This page is for the connection set up to a general LoRaWAN Network server such as [[TTN>>url:http://www.thethingsnetwork.org/]], [[ChirpStack>>url:https://www.chirpstack.io/]], etc.
++//This page is for the connection set up to a general LoRaWAN Network server such as [[TTN>>url:http://www.thethingsnetwork.org/]], [[ChirpStack>>url:https://www.chirpstack.io/]], etc.//
  [[image:image-20220616111932-2.png||height="516" width="672"]]
@@ -425,7 +425,7 @@
  === 3.3.2 LoRaWAN ~-~-> LoRaWAN Basic Station ===
--This page is for the connection set up to the TTN Basic Station, AWS-IoT, etc.
++//This page is for the connection set up to the TTN Basic Station, AWS-IoT, etc.//
  [[image:image-20220616113246-3.png||height="396" width="672"]]
@@ -440,9 +440,8 @@
  === 3.4.1 Network ~-~-> WiFi ===
--Users can configure the wifi WAN and enable Wifi Access Point on this interface
--[[image:image-20230619095946-1.png||height="332" width="827"]]
++[[image:image-20220616114756-4.png||height="251" width="669"]]
  === 3.4.2 Network ~-~-> System Status ===
@@ -454,7 +454,7 @@
  === 3.4.3 Network ~-~-> Network ===
--In the **Network ~-~-> Network** interface, Users can set the Ethernet WAN static ip address.
++In the Network ~-~-> Network interface, Users can set the Ethernet WAN static ip address.
  [[image:image-20230214093657-2.png||height="333" width="858"]]
@@ -462,7 +462,7 @@
  === 3.4.4 Network ~-~-> Cellular ===
--In the **Network ~-~-> Cellular** interface, Users can Enable Cellular WAN and configure Celluar.
++In the Network ~-~-> Cellular interface, Users can Enable Cellular WAN and configure Celluar.
  (% style="color:red" %)**Note: APN cannot be empty.**
@@ -469,16 +469,11 @@
  [[image:image-20230228115126-1.png]]
--After the configuration is complete, return to the Home interface and put the mouse on the Cell icon to check the Cellular state.
++After the configuration is complete, return to the Home interface and put the mouse on the Cell icon to check the Cellualr state.
  [[image:image-20230228115535-2.png||height="478" width="888"]]
--Note: Known bugs: 4g consumes a lot of data which has been fixed by the package: dragino-ui-230716
--
--[[Reduce data method>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/#H8.3Howtoreducethe4gdataconsumed]]
--
--
  == 3.5 System ==
  === 3.5.1 System ~-~-> System Overview ===
@@ -486,13 +486,13 @@
  Shows the system info:
--[[image:image-20231031162854-1.png]]
++[[image:image-20220917144512-5.png||height="618" width="853"]]
  === 3.5.2 System ~-~-> System General ===
--In the **System-> System General** interface, Users can customize the configuration System Password and set Timezone.
++In the System-> System General interface, Users can customize the configuration System Password and set Timezone.
  In addition, Users can customize the FallBack IP address.
@@ -502,150 +502,120 @@
  === 3.5.3 System ~-~-> Backup/Restore ===
--[[image:image-20231031162927-2.png]]
++[[image:image-20220917144725-6.png||height="208" width="869"]]
--=== 3.5.4 System ~-~-> Reboot / Reset ===
--In the **System-> Reboot / Reset** interface, users can can restart or reset the gateway.
++=== 3.5.4 System ~-~-> Remoteit ===
--ETH LED will SOLID BULE Until the restore is finished.
--When the gateway restores the factory settings is complete,
++In the System-> Remoteit interface, users can configure the gateway to be accessed remotely via Remote.it.
--The WiFi configuration will enable WiFi Access Point by default.
--The other configuration will be restored to the default configuration.
--
--[[image:image-20240203172853-1.png||height="365" width="901"]]
--
--
--=== 3.5.5 System ~-~-> Remoteit ===
--
--
--In the **System-> Remoteit** interface, users can configure the gateway to be accessed remotely via Remote.it.
--
--
  the users can refer to this link to configure them: **[[Monitor & Remote Access Gateway>>http://wiki.dragino.com/xwiki/bin/view/Main/Monitor%20%26%20Remote%20Access%20Gateway/?Remote%20Access#H2.1A0RemoteAccessviaRemote.it.]]**
  [[image:image-20221230092303-2.png]]
--=== 3.5.6 System ~-~-> Package Management ===
++=== 3.5.5 System ~-~-> Package Management ===
--In the **System ~-~-> Package Management** interface, Users can check the current version of Core Packages.
++In the System ~-~-> Package Management interface, Users can check the current version of Core Packages.
  [[image:image-20230214094316-4.png]]
--== 3.5 Logread ==
++= 4. Build-in Server =
--=== 3.5.1 LoRa Log ===
++The default factory version of LPS8-V2 is installed with the built-in Applicant server: (% style="color:blue" %)**Node-Red, and**(%%) LoRaWAN Server: (% style="color:blue" %)**The Things Network - Stack (Open Source 3.19 Version).**
--In the **Lograde ~-~-> LoRa Log page**, The users can view information about the gateway lora channel and the status of the IoT connection
--[[image:image-20240416112509-1.png]]
++[[image:image-20230214095318-5.png||height="347" width="980"]]
--=== 3.5.2 Gateway Traffic ===
++(% style="color:red" %)**Note:**
--In the **Lograde ~-~-> Gateway Traffic page**, The users can view sensor packages about Recent LoRa uplink/downlink/Join requests
++         **Path**: System ~-~-> Built-in Server
--[[image:image-20240416112618-2.png||height="705" width="1122"]]
++**Troubleshooting:**
--=== 3.5.3 System Log ===
--In the **Lograde ~-~-> System Log page**, The users can view information about the gateway system
++**~         1. URL does not jump properly**
--[[image:image-20240416112649-3.png||height="820" width="1122"]]
++                For the ttn-stack, you can click the update the URL which will update the configuration where change the hostname to the current local IP address as the URL.
++                For the Node-Red, you can use the local IP address and the port is 1880 to access it.
--=== 3.5.4 Record Log ===
--In the **Lograde ~-~-> Recod Log page**, The users can record the gateway curren running log.
++== 4.1 LoRaWAN Network  Server ~-~- The Things Network - Stack (TTN-V3) ==
--[[image:image-20240416112712-4.png||height="319" width="1128"]]
++You can access the gateway's built-in LNS server of (% style="color:blue" %)**The Things Network - Stack **(%%)via the URL( (% style="background-color:yellow" %)__**//http:~/~/<hostname>:8080 or http:~/~/<local-IPV4-address> //**__(%%)) in your browser.
++Such as  (% style="background-color:yellow" %)__**//http:~/~/dragino-54ff12:8080  or http:~/~/<Local-IPV4-Address>//**__
--= 4. Build-in Server =
--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**(%%).
++Login account:
++**User ID: **            ** (% style="background-color:yellow" %)admin(%%)**
--== 1). LoRaWAN Network Server: (% style="color:blue" %)**ChirpStack-V4**(%%) ==
++**Password: **        ** (% style="background-color:yellow" %)dragino(%%)**
--[[image:image-20231106180816-4.png||height="416" width="896"]]
--[[image:image-20231201165904-1.png||height="466" width="899"]]
++[[image:image-20220725171719-1.png||height="570" width="769"]]
--(% style="color:red" %)**Note:  The user can access the**(%%)** (% style="color:blue" %)ChirpStack-V4 (% style="color:red" %)via click the 'Launch' button, and the login account: admin/admin(%%)**
--For more information on server operations see [[Register LPSV2 to the built-in Chirpstack>>||anchor="H2.3TheLPS8-V2isregisteredandconnectedtoTheThingsNetwork"]]
++=== 4.1.1 The LPS8-V2 is registered and connected to Built-in The Things Network ===
++Users need to set the Service Provider to (% style="color:blue" %)**Local Host/Build-in Server **(%%) and click "Save&Apply"
--== 2). Application Network Server: (% style="color:blue" %)**Node-Red**(%%) ==
++The registration steps are basically similar to [[LPS8-V2 is registered and connected to The Things Network>>||anchor="H2.3TheLPS8-V2isregisteredandconnectedtoTheThingsNetwork"]]
++[[image:image-20230321092456-1.png]]
--[[image:image-20230616175558-7.png||height="362" width="894"]]
--[[image:image-20231201170355-2.png||height="536" width="899"]]
++== 4.2 Application Server ~-~- Node-Red ==
--(% style="color:red" %)**Note:  The user can access the**(%%)** (% style="color:blue" %)Node-RED (% style="color:red" %)via click the 'Launch' button(%%)**
++You can access the gateway's built-in AS server of (% style="color:blue" %)**Node-Red **(%%)via the URL((% style="background-color:yellow" %)__**//http:~/~/<hostname>:1880 or http:~/~/<local-IPV4-address>//**__(%%)) in your browser.
--== **3). Troubleshooting:** ==
++Such as (% style="background-color:yellow" %)__**//http:~/~/dragino-54ff12:1880  or http:~/~/<Local-IPV4-Address>//**__
--* (((
--=== ** If the URL does not jump properly.** ===
--)))
++[[image:image-20220725172124-3.png||height="610" width="843"]]
--                For the ChirpStack, you can use the local IP address and the port is **8080** to access it.
--                For the Node-Red, you can use the local IP address and the port is **1880** to access it.
++=== **Using Node-Red, InfluxDB and Grafana** ===
--* (((
--=== ** How to install InfluxDB, Garfana.** ===
--)))
++The LPS8-V2 supports this combination, the default, Node-red is pre-installed but the InfluxDB and Grafana is not pre-installed.
--                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]]
++the users can refer to this link to install them.
--* (((
--=== ** How to upgrade the gateway node.js to the latest version.** ===
--)))
++[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.6HowtoinstallGrafanaandinfluxdb>>http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.6HowtoinstallGrafanaandinfluxdb]]
--                The user can upgrade nodejs, see [[Upgrade Nodejs>>http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.5Howtoupgradethenodejsversiontothelatest.]]
++=== **Upgrade the node.js** ===
--* (((
--=== ** How to batch register device on the built-in Chirpstack network server** ===
--)))
++By default, the LPS8-V2 node.js uses the pre-install version v12 which is due to Debian the ultra-stable via ultra-old.
--                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]]
++the users can refer to this link to upgrade them.
--* (((
--=== ** Why my gateway is not Chirpstack?** ===
--)))
++[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.5Howtoupgradethenodejsversiontothelatest.>>http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.5Howtoupgradethenodejsversiontothelatest.]]
--                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]]**
++== 4.3 How to disable the built-in server ==
--* (((
--=== ** How to disable the built-in server** ===
--)))
++Use the following commands to start and stop the TTNv3 service:
++
  (% class="box infomessage" %)
  (((
--Use the following commands to start and stop the TTNv3 service:**     **
--
  **# start**
  systemctl start ttnstack
@@ -659,10 +659,10 @@
  systemctl disable ttnstack
  )))
--(% class="box infomessage" %)
--(((
  Use the following commands to start and stop the Node-Red service:
++(% class="box infomessage" %)
++(((
  **# start**
  systemctl start nodered
@@ -677,45 +677,26 @@
  )))
--* (((
--=== ** How to choose the Chirpstack server frequency SubBand** ===
--)))
++== 4.4 How to use ChirpStack on LPS8-V2 ==
--**~               ** The user has to choose a SubBand if using CN470, US915, AU915, or AS923.
--                 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.
++By default, the built-in LoRaWAN network server used on LPS8v2 is TTNv3, so users need to disable TTNv3 services and follow this link to install chirpstack:
--[[image:image-20230602140406-3.png||height="480" width="918"]]
++[[ChirpStack open-source LoRaWAN® Network Server documentation>>https://www.chirpstack.io/docs/getting-started/docker.html]]
++[[image:image-20230222094908-1.png||height="133" width="798"]]
--When the configuration is complete, click** "Save&Apply"**.
++= 5. How the LPS8-V2 connects to Chirpstack via gateway-bridge =
--(% 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.
--[[image:image-20230602143122-4.png||height="511" width="983"]]
--
--= 5. Watch Dog =
--
--
--LPS8-V2 supports the Watch Dog but is not enabled by the previous releases(2023-11-24 )
--
--The uses can be via the below method to enable Watch Dog:
--
--(% class="box infomessage" %)
--(((
--wget -P /tmp/ http:~/~/repo.dragino.com/release/tool/watchdog/enable_watchdog.sh && chmod +x /tmp/enable_watchdog.sh && /tmp/enable_watchdog.sh
--)))
--
--[[image:image-20231124113209-1.png||height="470" width="1157"]]
--
--
  = 6. How users can access LPS8-V2 using serial USB =
  (% style="color:blue" %)**USB TTL to LPS8-V2  Connection:**
++
  Port 1 of the UART on the LPS8-V2 is GND
  (% class="box infomessage" %)
@@ -727,8 +727,10 @@
  **GND <~-~--> GND (Black line)**
  )))
++
  **LPS8v2 UART connection photo**
++
  [[image:image-20230421094319-2.png||height="351" width="392"]]
  In the PC,you can use the serial port tool(such as [[putty>>url:http://www.chiark.greenend.org.uk/~~sgtatham/putty/download.html]] in Windows), you need to set the serial baud rate to (% style="color:blue" %)**115200**(%%) to access the serial console for LPS8v2. LPS8v2 will output system info once power on as below:
@@ -740,268 +740,114 @@
  [[image:image-20220804164747-2.png||height="622" width="594"]]
--= 7. OTA System Update =
++= 7. Use the helium gateway-rs as the Data-only Hotspot =
--LPS8v2 supports system auto-update via OTA, please see **[[this URL>>url:http://wiki.dragino.com/xwiki/bin/view/OTA%20Update/]]** for the detail of this feature.
++== **Step 1: Configure Frequency Band** ==
--== 7.1 Auto-update method ==
++//Each country has a requirement for frequency region. Choose the right one for your area.//
++[[image:image-20220905164308-1.png]]
--The default, each gateway will enable the auto-update function.
--this function will be triggered every boot and every midnight.
++== **Step 2: Configure the forward address** ==
--Users can enable/disable it via Web Page
--[[image:image-20230607094447-2.png]]
++**Select one of the servers to configure.**
++**For example:**
--== 7.2 Manual upgrade method ==
++[[image:image-20220905164847-2.png]]
--1). Using the Linux command to upgrade the system
--(% class="box infomessage" %)
--(((
--**apt update && apt install *dragino***
--)))
++== **Step 3: Download and Install the Helium-gateway-rs** ==
--2). Upgrade the system via the Web page button of "Manual Update"
++**Access the gateway CLI via SSH.**
--(% style="color:red" %)**Note: this method needs about 10 mins, so you will get the log after 10 mins.  **
++[[image:image-20220905165222-3.png]]
--[[image:image-20230607093849-1.png]]
++**Download gateway-rs.**
--= 8. FAQ =
++[[image:image-20220905165715-5.png]]
--== 8.1 How to change Hostname ==
--
--
--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:
--
  (% class="box infomessage" %)
  (((
--hostnamectl set-hostname dragino-123456
++**Command: wget [[http:~~/~~/repo.dragino.com/release/tool/gateway-rs/helium-gateway-v1.0.0-alpha.31-raspi234.deb>>http://repo.dragino.com/release/tool/gateway-rs/helium-gateway-v1.0.0-alpha.31-raspi234.deb]]**
  )))
--[[image:image-20230517102429-1.png]]
--After the configuration is complete, run "reboot" to restart the gateway.
++**Install gateway-rs.**
++[[image:image-20220905165917-7.png]]
--== 8.2 Build-in The Things Network migrate to ChirpStack ==
--
--
--Migrate guide:
--
--To stabilize the completion of the migration, The users can migrate in one of the following ways
--
--**Method 1. Using the Linux shell, **
--
--**Method 2. Flash a new image with the Chirpstack**
--
--
--=== Method 1: Using the Linux shell ===
--
  (% class="box infomessage" %)
  (((
--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
++**Command: dpkg -i helium-gateway-v1.0.0-alpha.31-raspi234.deb **
  )))
--=== Method 2: Flash a new image ===
++**Modify configuration.**
--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]]
++[[image:image-20220905173847-12.png]]
--== 8.3 How to reduce the 4g data consumed ==
--
--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.
--
--[[image:image-20230719100239-1.png||height="724" width="994"]]
--
--
--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
--
--[[image:image-20230719100332-2.png]]
--
--
--3. Disable the auto-update:
--
--[[image:image-20230719100419-3.png||height="458" width="995"]]
--
--
--== 8.4 How to connect the helium blockchain as a Data-only hotspot ==
--
--
  (% class="box infomessage" %)
  (((
--apt update && apt install helium-gateway
++**region=<Enter regional parameters> \
++&& sed -i '/region/d' /etc/helium_gateway/settings.toml && sed -i "1 i\region = \"$region\"" /etc/helium_gateway/settings.toml \
++&& sed -i '/region/d' /etc/helium_gateway/default.toml && sed -i "22 i\region = \"$region\"" /etc/helium_gateway/default.toml**
  )))
--== 8.5 How to change built-in LoRaWAN Server from ChirpStack v4 to TTN Stack v3. ==
++**Restart the helium_gateway**
++[[image:image-20220905170920-9.png]]
--By default, the LPS8v2's built-in server is ChirpStack v4,
--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:
--
--[[https:~~/~~/www.dropbox.com/scl/fi/qwtaw4i4dqonzramr93e4/dragino-LPS8V2-TTN-231124.rar?rlkey=nrftlkd1h8en6j07vzbhpj9ui&dl=0>>https://www.dropbox.com/scl/fi/qwtaw4i4dqonzramr93e4/dragino-LPS8V2-TTN-231124.rar?rlkey=nrftlkd1h8en6j07vzbhpj9ui&dl=0]]
--
--
--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]]
--
--
--== 8.6 How do I view gateway logs ==
--
--=== 8.6.1 LoRaWAN Log: ===
--
--
--==== Semtech UDP Log : ====
--
--When the gateway starts LoRaWAN Semtech UDP, users can check the logs of the Semtech UDP in the **LogRead ~-~-> System Log** interface
--
--[[image:image-20231017112115-2.png||height="611" width="821"]]
--
--
--==== Station Log: ====
--
--When the gateway starts Basic Station, users can check the logs of the station in the **LogRead ~-~-> System Log** interface
--
--[[image:image-20231017111606-1.png||height="622" width="821"]]
--
--
--=== 8.6.2  4G Log ===
--
--
--User needs to access the Linux console of the gateway and enter the following command:
--
  (% class="box infomessage" %)
  (((
--cat /var/log/qmilog.txt
++**systemctl restart helium_gateway**
  )))
--[[image:image-20231017114417-3.png||height="543" width="679"]]
++**Check the helium_gateway Log：**
--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]].
++[[image:image-20220905173952-13.png]]
--Below are some commands as reference:
-->Usage:  /usr/bin/quectel-CM [options]
-->     -s [apn [user password auth]]          Set apn/user/password/auth get from your network provider. auth: 1~~pap, 2~~chap
-->     -p pincode                             Verify sim card pin if sim card is locked
-->     -p [quectel-][qmi|mbim]-proxy          Request to use proxy
-->     -f logfilename                         Save log message of this program to file
-->     -u usbmonlog filename                  Save usbmon log to file
-->     -i interface                           Specify which network interface to setup data call when multi-modems exits
-->     -4                                     Setup IPv4 data call (default)
-->     -6                                     Setup IPv6 data call
-->     -k pdn                                 Specify which pdn to hangup data call (by send SIGINT to 'quectel-CM -n pdn')
-->     -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
-->     -b                                     Enable network interface bridge function (default 0)
-->     -v                                     Verbose log mode, for debug purpose.[Examples]
-->Example 1: /usr/bin/quectel-CM
-->Example 2: /usr/bin/quectel-CM -s 3gnet
-->Example 3: /usr/bin/quectel-CM -s 3gnet -v
--
--
--
--
--
--=== 8.6.3 Dmesg Log ===
--
--
--Users can check the logs of the Dmesg in the **LogRead ~-~-> System Log** interface:
--
--[[image:image-20231017115330-5.png||height="565" width="740"]]
--
--
--=== 8.6.4 Record Log ===
--
--
--Users can record DMESG logs and LoRaWAN logs on the **LogRead ~-~->Record Log** interface
--
--[[image:image-20231017115124-4.png||height="215" width="880"]]
--
--
--=== 8.6.5 View gateway logs via Linux Command ===
--
--
--**Semtech UDP Log :**
--
  (% class="box infomessage" %)
  (((
--**journalctl -u draginofwd -f**
++**journalctl -u helium_gateway -f**
  )))
--[[image:image-20231207144627-1.png||height="371" width="1017"]]
++(% style="color:red" %)**Note: if your device is not finished the onboarding, which is unable to connect to the Helium console.**
--**Station Log:**
++where the helium gateway log is shown:
--(% class="box infomessage" %)
--(((
--**tail -f /var/log/station.log **
--)))
++[[image:image-20220905174534-14.png]]
--[[image:image-20231207144758-2.png||height="132" width="1022"]]
++So you have to finish the onboarding, ~-~--Please refer to [[Step 2.7>>doc:Main.Notes for Helium.WebHome||anchor="H2.7A0Step6:OnboardingData-OnlyHotspot"]] to onboarding your LPS8-V2.
--**Dmesg Log:**
--(% class="box infomessage" %)
--(((
--**dmesg**
--)))
++= 8. OTA System Update =
--[[image:image-20231207145210-3.png||height="310" width="1021"]]
++LPS8v2 supports system auto update via OTA, please see **[[this URL>>url:http://wiki.dragino.com/xwiki/bin/view/OTA%20Update/]]** for the detail of this feature.
--== 8.7 DIN Mount Reference: ==
--
--[[image:image-20240318095605-1.jpeg||height="472" width="472"]]
--
--[[image:image-20240318095617-2.png]]
--
--
--== 8.8 NTP Service/Time Synchronization ==
--
--The gateway time sync service is provided by chrony service
--
--
--=== 1). Modify the NTP server address: ===
--
--(% class="box infomessage" %)
--(((
--Configuration file path:   /etc/chrony/chrony.conf
--)))
--
--
--=== 2). Start/Stop/Enable/Disable NTP service: ===
--
--(% class="box infomessage" %)
--(((
--systemctl start chrony
--\\systemctl stop chrony
--\\systemctl disable chrony
--\\systemctl enable chrony
--)))
--
--
--
  = 9. Trouble Shooting =
  == 9.1  I can't log in to the built-in Server TTN Stack which shows '**Login failed**'. ==
++
  [[image:image-20220920135918-1.png]]
@@ -1017,21 +1017,13 @@
  [[image:image-20220920141936-2.png]]
--== 9.2  The built-in TTN status is "Not Running" and the URI is "dragino-123456". How users fix this problem ==
++== 9.2  Fallback IP does not work, how can users check ==
--When this problem occurs, click "**Update To DEFAULT**" ,this problem will be fixed.
--
--[[image:image-20230508171607-1.png]]
--
--
--== 9.3  Fallback IP does not work, how can users check ==
--
--
  When the computer has completed the above fallback IP configuration,the LPS8v2 Web UI is still not accessible via fallback IP.
--**~1. Check whether the configuration is correct**
++**1.Check whether the configuration is correct**
  Run the CMD command to ipconfig and ping 172.31.255.254.
@@ -1047,54 +1047,15 @@
  If the firewall is not down, this will affect access to the gateway.
--== 9.4  Click "Manual_Update", why there is no response? ==
--
--
--When you click "Manual_Update", the gateway will finish updating within 10 minutes and display the update log.
--
--
--[[image:image-20230527090555-3.png||height="660" width="832"]]
--
--
--== 9.5  Why the LPS8V2's Access Point does not do not appear & Fallback IP unable to access ==
--
--
--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.
--
--(% class="box infomessage" %)
--(((
--apt update && apt install *dragino*
--
--wget -P /tmp/ [[http:~~/~~/repo.dragino.com/release/hp0c-packages/linux-image-current-draginohp0z_22.05.2_armhf.deb>>http://repo.dragino.com/release/hp0c-packages/linux-image-current-draginohp0z_22.05.2_armhf.deb]] && dpkg -i /tmp/[[linux-image-current-draginohp0z_22.05.2_armhf.deb>>http://repo.dragino.com/release/hp0c-packages/linux-image-current-draginohp0z_22.05.2_armhf.deb]]
--)))
--
--
--== 9.6  How to reset the built-in server ==
--
--
--**1) Build-in The Things Network**
--
--Refer to this link to delete the Built-in server's device.
--
--[[Delete devices from Build-in The Things Network>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Delete%20devices%20from%20Build-in%20The%20Things%20Network/]]
--
--
--**2) Build-in Chirpstack**
--
--Users need to click "Reset" on the Server~-~->NetServer interface, ChirpStack will be reset.
--
--[[image:image-20231106180846-5.png||height="310" width="668"]]
--
--
  = (% style="color:inherit; font-family:inherit; font-size:29px" %)10. Supports(%%) =
  (((
--If you are experiencing issues and can't solve them, you can send mail to [[support@dragino.com>>mailto:support@dragino.com]].
++**//If you are experiencing issues and can't solve them, you can send mail to [[support@dragino.com>>mailto:support@dragino.com]].//**
  )))
  (((
--With your question as detailed as possible. We will reply and help you in the shortest.
++**//With your question as detailed as possible. We will reply and help you in the shortest.//**
  = 11. Reference =
@@ -1114,27 +1114,19 @@
  (% style="color:#0000ff" %)**XXX**(% style="color:black" %): Frequency Band
  * (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
--
  * (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
--
  * (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
--
  * (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
--
  * (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
--
  * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
  (% style="color:#0000ff" %)**YYY**(% style="color:black" %): 4G Cellular Option
--* (% style="color:red" %)**EC25-E**(% style="color:black" %):      EMEA, Korea, Thailand, India
++* (% style="color:red" %)**E**(%%):    EMEA, Korea, Thailand, India.
++* (% style="color:red" %)**A**(%%):   North America/ Rogers/AT&T/T-Mobile.
++* (% style="color:red" %)**AU**(%%): Latin America, New Zeland, Taiwan
++* (% style="color:red" %)**J**(%%):    Japan, DOCOMO/SoftBank/ KDDI
--* (% style="color:red" %)**EC25-AFX**(% style="color:black" %): America:Verizon, AT&T(FirstNet), U.S.Cellular; Canada:Telus
--
--* (% style="color:red" %)**EC25-AUX**(% style="color:black" %): Latin America, New Zeland, Taiwan
--
--* (% style="color:red" %)**EC25-J**(% style="color:black" %):      Japan, DOCOMO, SoftBank, KDDI
--
  More info about valid bands, please see [[EC25-E product page>>url:https://www.quectel.com/product/ec25.htm]].

Delete Device.docx

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoye

Size

...	...	@@ -1,1 +1,0 @@
1		-336.4 KB

Content

image-20230425155659-8.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoye

Size

...	...	@@ -1,1 +1,0 @@
1		-34.8 KB

Content

image-20230508171607-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-37.5 KB

Content

image-20230517102429-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-25.5 KB

Content

image-20230524183659-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-55.9 KB

Content

image-20230526103829-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-55.7 KB

Content

image-20230526104156-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-33.0 KB

Content

image-20230526104501-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-125.6 KB

Content

image-20230526113915-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-55.8 KB

Content

image-20230526115650-5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-124.0 KB

Content

image-20230527084515-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-56.0 KB

Content

image-20230527085250-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-144.5 KB

Content

image-20230527090555-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-52.9 KB

Content

image-20230602135658-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-86.5 KB

Content

image-20230602135825-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-37.4 KB

Content

image-20230602140406-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-53.0 KB

Content

image-20230602143122-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-82.6 KB

Content

image-20230607093849-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoye

Size

...	...	@@ -1,1 +1,0 @@
1		-63.9 KB

Content

image-20230607094447-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoye

Size

...	...	@@ -1,1 +1,0 @@
1		-52.5 KB

Content

image-20230616162454-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-31.0 KB

Content

image-20230616162742-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-22.7 KB

Content

image-20230616162934-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-24.0 KB

Content

image-20230616174526-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-55.6 KB

Content

image-20230616174608-5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-44.4 KB

Content

image-20230616175332-6.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-20.6 KB

Content

image-20230616175558-7.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-38.9 KB

Content

image-20230616175617-8.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-38.2 KB

Content

image-20230616180004-9.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-38.1 KB

Content

image-20230619095946-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-38.0 KB

Content

image-20230719100239-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoye

Size

...	...	@@ -1,1 +1,0 @@
1		-66.4 KB

Content

image-20230719100332-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoye

Size

...	...	@@ -1,1 +1,0 @@
1		-47.0 KB

Content

image-20230719100419-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoye

Size

...	...	@@ -1,1 +1,0 @@
1		-47.3 KB

Content

image-20231017111606-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-117.6 KB

Content

image-20231017112115-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-114.3 KB

Content

image-20231017114417-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-130.4 KB

Content

image-20231017115124-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-28.6 KB

Content

image-20231017115330-5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-110.1 KB

Content

image-20231031162854-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-64.9 KB

Content

image-20231031162927-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-35.0 KB

Content

image-20231106175329-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-63.7 KB

Content

image-20231106175457-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-63.7 KB

Content

image-20231106175523-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-64.8 KB

Content

image-20231106180816-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-41.6 KB

Content

image-20231106180846-5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Kilight

Size

...	...	@@ -1,1 +1,0 @@
1		-41.9 KB

Content

image-20231124113209-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoye

Size

...	...	@@ -1,1 +1,0 @@
1		-198.7 KB

Content

image-20231201165904-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoye

Size

...	...	@@ -1,1 +1,0 @@
1		-29.5 KB

Content

image-20231201170355-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoye

Size

...	...	@@ -1,1 +1,0 @@
1		-70.2 KB

Content

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

Changes for page LPS8v2 -- LoRaWAN Indoor Gateway User Manual

Summary

Details

Applications

Navigation