Wiki source code of LPS8v2 - Japenese Manual
Last modified by Edwin Chen on 2022/07/14 09:54
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | [[image:image-20220620202334-2.png||height="467" width="809"]] | ||
| 2 | |||
| 3 | |||
| 4 | ((( | ||
| 5 | **LPS8v2 User Manual** | ||
| 6 | |||
| 7 | |||
| 8 | ))) | ||
| 9 | |||
| 10 | **Table of Contents：** | ||
| 11 | |||
| 12 | {{toc/}} | ||
| 13 | |||
| 14 | = **1. Introduction** = | ||
| 15 | |||
| 16 | == **1.1 What is LPS8v2** == | ||
| 17 | |||
| 18 | ((( | ||
| 19 | 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. | ||
| 20 | |||
| 21 | 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. | ||
| 22 | |||
| 23 | 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. | ||
| 24 | |||
| 25 | Different countries use different LoRaWAN frequency bands. LPS8v2 has these bands pre-configured. Users can also customize the frequency bands to use in their own LoRa network. | ||
| 26 | |||
| 27 | LPS8v2 supports (% style="color:green" %)**remote management**(%%). System Integrator can easy to remote monitor the gateway and maintain it. | ||
| 28 | |||
| 29 | |||
| 30 | == **1.2 Specifications** == | ||
| 31 | |||
| 32 | **Hardware System:** | ||
| 33 | |||
| 34 | * CPU: Quad-core Cortex-A7 1.2Ghz | ||
| 35 | * RAM: 512MB | ||
| 36 | * eMMC: 4GB | ||
| 37 | |||
| 38 | **Interface:** | ||
| 39 | |||
| 40 | * 10M/100M RJ45 Ports x 1 | ||
| 41 | * Multi-Channel LoRaWAN Wireless | ||
| 42 | * WiFi 802.11 b/g/n | ||
| 43 | |||
| 44 | **Operating Condition:** | ||
| 45 | |||
| 46 | * Work Temperature: -20 ~~ 65°C | ||
| 47 | * Storage Temperature: -20 ~~ 65°C | ||
| 48 | * Power Input: 5V, 2A, DC | ||
| 49 | |||
| 50 | == **1.3 Features** == | ||
| 51 | |||
| 52 | * Open Source Debian system | ||
| 53 | * Managed by Web GUI, SSH via WAN or WiFi | ||
| 54 | * Remote Management | ||
| 55 | * Auto-provisioning for batch deployment and management | ||
| 56 | * LoRaWAN Gateway | ||
| 57 | * 10 programmable parallel demodulation paths | ||
| 58 | * Pre-configured to support different LoRaWAN regional settings. | ||
| 59 | * Allow customizing LoRaWAN regional parameters. | ||
| 60 | * Different kinds of LoRaWAN Connections such as | ||
| 61 | ** Semtech UDP Packet Forwarder | ||
| 62 | ** LoRaWAN Basic Station | ||
| 63 | ** ChirpStack-Gateway-Bridge (MQTT) | ||
| 64 | * Built-in //**The Things Network**// local LoRaWAN server | ||
| 65 | * Built-in //**Node-Red**// local Application server | ||
| 66 | |||
| 67 | == **1.4 Block Diagram** == | ||
| 68 | |||
| 69 | |||
| 70 | == **1.5 LED Indicators** == | ||
| 71 | |||
| 72 | LPS8-V2 has totally four LEDs, They are: | ||
| 73 | |||
| 74 | |||
| 75 | //**➢ Power LED**: This RED LED will be solid if the device is properly powered// | ||
| 76 | |||
| 77 | |||
| 78 | //**➢ LoRa LED**: This RGB LED will blink GREEN when the LoRaWAN module starts or transmit a packet// | ||
| 79 | |||
| 80 | |||
| 81 | //**➢ SYS LED**: This RGB LED will show different colors in different states~:// | ||
| 82 | |||
| 83 | // ✓ SOLID BLUE: The device is alive with a LoRaWAN server connection.// | ||
| 84 | |||
| 85 | // ✓ BLINKING BLUE: a) Device has internet connection but no LoRaWAN Connection. or b) Device is in booting stage, in this stage, it will BLINKING BLUE for several seconds and then with SOLID RED and BLINKING BLUE together// | ||
| 86 | |||
| 87 | // ✓ SOLID RED: Device doesn’t have an Internet connection.// | ||
| 88 | |||
| 89 | |||
| 90 | //**➢ ETH LED**: This LED shows the ETH interface connection status.// | ||
| 91 | |||
| 92 | |||
| 93 | = **2. Quick Start** = | ||
| 94 | |||
| 95 | The LPS8-V2 supports network access via Ethernet or Wi-Fi connection and runs without a network. | ||
| 96 | |||
| 97 | In most cases, the first thing you need to do is make the lps8-v2 accessible to the network. | ||
| 98 | |||
| 99 | |||
| 100 | == **2.1 Connects to the network and accesses the gateway Web UI** == | ||
| 101 | |||
| 102 | |||
| 103 | == **2.1.1 connect the network.** == | ||
| 104 | |||
| 105 | === === | ||
| 106 | |||
| 107 | === **Method 1**: Connect via Ethernet with DHCP IP from the router === | ||
| 108 | |||
| 109 | Connect the LPS8-V2 Ethernet port to your router and LPS8 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. | ||
| 110 | |||
| 111 | You can also use this IP to connect. | ||
| 112 | |||
| 113 | [[image:image-20220622100129-1.png||height="332" width="1263"]] | ||
| 114 | |||
| 115 | |||
| 116 | === **Method 2**: Connect via WiFi with DHCP IP from the router === | ||
| 117 | |||
| 118 | |||
| 119 | [[image:image-20220622100542-2.png||height="369" width="1256"]] | ||
| 120 | |||
| 121 | |||
| 122 | The LPS8-V2 has a fall-back IP address on its WAN port. you have to access the gateway Web-UI to configure the WiFi connection via the fallback IP address. | ||
| 123 | |||
| 124 | |||
| 125 | **Steps to connect via fallback IP:** | ||
| 126 | |||
| 127 | ~1. Connect PC’s Ethernet port to LPS8-V2's WAN port | ||
| 128 | |||
| 129 | 2. Configure PC's Ethernet port has IP: 172.31.255.253 and Netmask: 255.255.255.252 | ||
| 130 | |||
| 131 | [[image:image-20220622101433-4.png]] | ||
| 132 | |||
| 133 | |||
| 134 | and then On the PC, use the IP address **http:~/~/172.31.255.254** to access the LPS8-V2 via Web or Console. | ||
| 135 | |||
| 136 | |||
| 137 | [[image:image-20220622102210-5.png||height="569" width="1039"]] | ||
| 138 | |||
| 139 | |||
| 140 | Fill in the WiFi information by checking the box and clicking **Save&Apply** | ||
| 141 | |||
| 142 | |||
| 143 | [[image:image-20220622102702-6.png]] | ||
| 144 | |||
| 145 | |||
| 146 | **Wi-Fi configuration successful** | ||
| 147 | |||
| 148 | |||
| 149 | [[image:image-20220622102847-7.png]] | ||
| 150 | |||
| 151 | [[image:image-20220622102901-8.png||height="513" width="1011"]] | ||
| 152 | |||
| 153 | |||
| 154 | |||
| 155 | |||
| 156 | == **2.2 The LPS8-V2 is registered and connected to The Things Network** == | ||
| 157 | |||
| 158 | |||
| 159 | === **2.2.1 Select your area frequency** === | ||
| 160 | |||
| 161 | First, you need to set the frequency plan in LPS8-V2 to match the end node we use, so to receive the LoRaWAN packets from the LoRaWAN sensor. | ||
| 162 | |||
| 163 | [[image:image-20220622103332-9.png]] | ||
| 164 | |||
| 165 | |||
| 166 | === **2.2.2 Get the only gateway EUI** === | ||
| 167 | |||
| 168 | Every LPS8-V2 has a unique gateway id. The ID can be found on LoRaWAN Semtech page: | ||
| 169 | |||
| 170 | [[image:image-20220622103355-10.png]] | ||
| 171 | |||
| 172 | |||
| 173 | **Note: Choose the cluster that corresponds to a specific Gateway server address** | ||
| 174 | |||
| 175 | **➢ Europe 1:** corresponding Gateway server address: **eu1.cloud.thethings.network** | ||
| 176 | |||
| 177 | **➢ North America 1:** corresponding Gateway server address: **nam1.cloud.thethings.network** | ||
| 178 | |||
| 179 | **➢ Australia 1: ** corresponding Gateway server address: **au1.cloud.thethings.network** | ||
| 180 | |||
| 181 | **➢ Legacy V2 Console:** TTN v2 shuts down in December 2021 | ||
| 182 | |||
| 183 | |||
| 184 | [[image:image-20220622103956-12.png]] | ||
| 185 | |||
| 186 | |||
| 187 | |||
| 188 | == 2.2.3 Register the gateway to The Things Network == | ||
| 189 | |||
| 190 | **Login to The Things Network** | ||
| 191 | |||
| 192 | [[https:~~/~~/console.cloud.thethings.network/>>https://console.cloud.thethings.network/]] | ||
| 193 | |||
| 194 | **Add the gateway** | ||
| 195 | |||
| 196 | [[image:image-20220622104252-13.png||height="511" width="953"]] | ||
| 197 | |||
| 198 | |||
| 199 | **Get it online** | ||
| 200 | |||
| 201 | |||
| 202 | = **3. Web Configure Pages** = | ||
| 203 | |||
| 204 | |||
| 205 | == **3.1 Home** == | ||
| 206 | |||
| 207 | //Shows the system running status~:// | ||
| 208 | |||
| 209 | == **3.2 LoRa Settings** == | ||
| 210 | |||
| 211 | |||
| 212 | === **3.2.1 LoRa ~-~-> LoRa** === | ||
| 213 | |||
| 214 | |||
| 215 | //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.// | ||
| 216 | |||
| 217 | //Different LPS8v2 hardware versions can support different frequency ranges~:// | ||
| 218 | |||
| 219 | * (% style="color:#0000ff" %)//**868**//(% style="color:black" %)//: valid frequency: 863Mhz ~~ 870Mhz. for bands EU868, RU864, IN865 or KZ865.// | ||
| 220 | * (% style="color:#0000ff" %)//**915**//(% style="color:black" %)//: valid frequency: 902Mhz ~~ 928Mhz. for bands US915, AU915, AS923 or KR920// | ||
| 221 | |||
| 222 | (% class="wikigeneratedid" %) | ||
| 223 | //After the user choose the frequency plan, the user can see the actual frequency is used by checking the page **LogRead ~-~-> LoRa Log**// | ||
| 224 | |||
| 225 | (% class="wikigeneratedid" %) | ||
| 226 | [[image:image-20220616110739-1.png||height="372" width="682"]] | ||
| 227 | |||
| 228 | |||
| 229 | //**Note ***: See this instruction for how to customize the frequency band~:// | ||
| 230 | |||
| 231 | //__[[How to customized LoRaWAN frequency band - DRAGINO>>url:http://8.211.40.43/xwiki/bin/view/Main/How%20to%20customized%20LoRaWAN%20frequency%20band/]]__// | ||
| 232 | |||
| 233 | |||
| 234 | == **3.3 LoRaWAN Settings** == | ||
| 235 | |||
| 236 | |||
| 237 | === **3.3.1 LoRaWAN ~-~-> LoRaWAN Semtech UDP** === | ||
| 238 | |||
| 239 | |||
| 240 | //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.// | ||
| 241 | |||
| 242 | [[image:image-20220616111932-2.png||height="516" width="672"]] | ||
| 243 | |||
| 244 | |||
| 245 | === **3.3.2 LoRaWAN ~-~-> LoRaWAN Basic Station** === | ||
| 246 | |||
| 247 | |||
| 248 | //This page is for the connection set up to the TTN Basic Station, AWS-IoT, etc.// | ||
| 249 | |||
| 250 | [[image:image-20220616113246-3.png||height="396" width="672"]] | ||
| 251 | |||
| 252 | |||
| 253 | Please see this instruction to know more detail and a demo for how to use of LoRaWAN Basic Station: __[[Use of LoRaWAN Basic Station - DRAGINO>>url:http://8.211.40.43/xwiki/bin/view/Main/Use%20of%20LoRaWAN%20Basic%20Station/]]__ | ||
| 254 | |||
| 255 | |||
| 256 | == **3.4 Network Settings** == | ||
| 257 | |||
| 258 | |||
| 259 | === **3.4.1 Network ~-~-> WiFi** === | ||
| 260 | |||
| 261 | |||
| 262 | [[image:image-20220616114756-4.png||height="251" width="669"]] | ||
| 263 | |||
| 264 | |||
| 265 | === **3.4.2 Network ~-~-> System Status** === | ||
| 266 | |||
| 267 | |||
| 268 | [[image:image-20220616115229-5.png||height="548" width="665"]] | ||
| 269 | |||
| 270 | |||
| 271 | === **3.4.3 Network ~-~-> Firewall** === | ||
| 272 | |||
| 273 | |||
| 274 | [[image:image-20220616115351-6.png||height="244" width="661"]] | ||
| 275 | |||
| 276 | |||
| 277 | == **3.5 System** == | ||
| 278 | |||
| 279 | |||
| 280 | === **3.5.1 System ~-~-> System Overview** === | ||
| 281 | |||
| 282 | |||
| 283 | Shows the system info: | ||
| 284 | |||
| 285 | |||
| 286 | === **3.5.2 System ~-~-> Backup/Restore** === | ||
| 287 | |||
| 288 | |||
| 289 | [[image:image-20220616115808-7.png||height="194" width="649"]] | ||
| 290 | |||
| 291 | |||
| 292 | 3.5.3 | ||
| 293 | |||
| 294 | |||
| 295 | (% style="color:inherit; font-family:inherit; font-size:29px" %)**10. Supports** | ||
| 296 | |||
| 297 | ((( | ||
| 298 | **//If you are experiencing issues and can't solve them, you can send mail to [[support@dragino.com>>mailto:support@dragino.com]].//** | ||
| 299 | ))) | ||
| 300 | |||
| 301 | ((( | ||
| 302 | **//With your question as detailed as possible. We will reply and help you in the shortest.//** | ||
| 303 | |||
| 304 | |||
| 305 | ))) | ||
| 306 | |||
| 307 | = **10. Order Info** = | ||
| 308 | |||
| 309 | (% style="color:#0000ff" %)**LPS8v2-XXX-YYY** | ||
| 310 | |||
| 311 | (% style="color:#0000ff" %)**XXX**(% style="color:black" %): Frequency Band | ||
| 312 | |||
| 313 | * **AS923**: LoRaWAN AS923 band | ||
| 314 | * **AU915**: LoRaWAN AU915 band | ||
| 315 | * **EU868**: LoRaWAN EU868 band | ||
| 316 | * **KR920**: LoRaWAN KR920 band | ||
| 317 | * **US915**: LoRaWAN US915 band | ||
| 318 | * **IN865**: LoRaWAN IN865 band | ||
| 319 | |||
| 320 | (% style="color:#0000ff" %)**YYY**(% style="color:black" %): 4G Cellular Option | ||
| 321 | |||
| 322 | * ** E**: EMEA, Korea, Thailand, India. | ||
| 323 | * ** A**: North America/ Rogers/AT&T/T-Mobile. | ||
| 324 | * ** AU**: Latin America, New Zeland, Taiwan | ||
| 325 | * ** J**: Japan, DOCOMO/SoftBank/ KDDI | ||
| 326 | |||
| 327 | More info about valid bands, please see [[EC25-E product page>>url:https://www.quectel.com/product/ec25.htm]]. | ||
| 328 | |||
| 329 | |||
| 330 | = **11. Manufacturer Info** = | ||
| 331 | |||
| 332 | **Shenzhen Dragino Technology Development co. LTD** | ||
| 333 | |||
| 334 | Room 202, Block B, BCT Incubation Bases (BaoChengTai), No.8 CaiYunRoad | ||
| 335 | |||
| 336 | LongCheng Street, LongGang District ; Shenzhen 518116,China | ||
| 337 | |||
| 338 | |||
| 339 | = **12. FCC Warning** = | ||
| 340 | |||
| 341 | This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: | ||
| 342 | |||
| 343 | ~-~- Reorient or relocate the receiving antenna. | ||
| 344 | |||
| 345 | ~-~- Increase the separation between the equipment and receiver. | ||
| 346 | |||
| 347 | ~-~- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. | ||
| 348 | |||
| 349 | ~-~- Consult the dealer or an experienced radio/TV technician for help. | ||
| 350 | |||
| 351 | |||
| 352 | Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment. | ||
| 353 | |||
| 354 | |||
| 355 | The antenna(s) used for this transmitter must be installed to provide a separation distance of at least 20 cm from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter. | ||
| 356 | ))) |