Wiki source code of LPS8N -- LoRaWAN Gateway User Manual
Version 221.1 by Edwin Chen on 2025/02/26 09:42
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | (% style="text-align:center" %) | ||
| 2 | [[image:1656917428377-954.png||height="475" width="475"]] | ||
| 3 | |||
| 4 | |||
| 5 | |||
| 6 | |||
| 7 | **Table of Contents:** | ||
| 8 | |||
| 9 | {{toc/}} | ||
| 10 | |||
| 11 | |||
| 12 | |||
| 13 | |||
| 14 | |||
| 15 | |||
| 16 | = 1. Introduction = | ||
| 17 | |||
| 18 | == (% data-sider-select-id="a36bf9cd-fdd9-49e1-813f-6d602534bdf0" %)1.1 What is the LPS8N(%%) == | ||
| 19 | |||
| 20 | |||
| 21 | ((( | ||
| 22 | The LPS8N is an (% style="color:blue" %)**open source LoRaWAN Indoor Gateway**(%%). It lets you bridge LoRa wireless network to an IP network via WiFi, Ethernet, 3G or 4G cellular network. The LoRa wireless allows users to send data and reach extremely long ranges at low data-rates. | ||
| 23 | ))) | ||
| 24 | |||
| 25 | ((( | ||
| 26 | The LPS8N uses (% style="color:blue" %)**Semtech packet forwarder**(%%) & (% style="color:blue" %)**LoRaWAN Station connection**(%%) and fully compatible with LoRaWAN protocol. It includes a (% style="color:blue" %)**SX1302 LoRaWAN concentrator**(%%), which provides 10 programmable parallel demodulation paths. | ||
| 27 | ))) | ||
| 28 | |||
| 29 | ((( | ||
| 30 | LPS8N has (% style="color:blue" %)**pre-configured standard LoRaWAN frequency bands**(%%) to use for different countries. User can also (% style="color:blue" %)**customized the frequency bands** (%%)to use in their own LoRa network. | ||
| 31 | ))) | ||
| 32 | |||
| 33 | ((( | ||
| 34 | LPS8N can communicate with ABP LoRaWAN end node without LoRaWAN server. System integrator can use it to integrate with their existing IoT Service without set up own LoRaWAN server or use 3rd party LoRaWAN service. | ||
| 35 | ))) | ||
| 36 | |||
| 37 | |||
| 38 | [[image:image-20220826090251-1.png]] | ||
| 39 | |||
| 40 | |||
| 41 | == 1.2 Specifications == | ||
| 42 | |||
| 43 | |||
| 44 | (% style="color:#037691" %)**Hardware System:** | ||
| 45 | |||
| 46 | ((( | ||
| 47 | Linux Part: | ||
| 48 | ))) | ||
| 49 | |||
| 50 | * 400Mhz ar9331 processor | ||
| 51 | * 64MB RAM | ||
| 52 | * 16MB Flash | ||
| 53 | |||
| 54 | (% style="color:#037691" %)**Interface:** | ||
| 55 | |||
| 56 | * 10M/100M RJ45 Ports x 1 | ||
| 57 | * WiFi : 802.11 b/g/n | ||
| 58 | * LoRaWAN Wireless | ||
| 59 | * Power Input: 5V DC, 2A, Type C | ||
| 60 | * USB 2.0 host connector x 1 | ||
| 61 | * Mini-PCI E connector x 1 | ||
| 62 | * SX1302 + 2 x SX1250 | ||
| 63 | |||
| 64 | (% style="color:#037691" %)**WiFi Spec:** | ||
| 65 | |||
| 66 | * IEEE 802.11 b/g/n | ||
| 67 | * Frequency Band: 2.4 ~~ 2.462GHz | ||
| 68 | * Tx power: | ||
| 69 | ** 11n tx power : mcs7/15: 11db mcs0 : 17db | ||
| 70 | ** 11b tx power: 18db | ||
| 71 | ** 11g 54M tx power: 12db | ||
| 72 | ** 11g 6M tx power: 18db | ||
| 73 | * Wifi Sensitivity | ||
| 74 | ** 11g 54M : -71dbm | ||
| 75 | ** 11n 20M : -67dbm | ||
| 76 | |||
| 77 | (% style="color:#037691" %)**LoRa Spec:** | ||
| 78 | |||
| 79 | * Up to -140 dBm sensitivity | ||
| 80 | * 70 dB CW interferer rejection at 1 MHz offset | ||
| 81 | * Able to operate with negative SNR, CCR up to 9dB | ||
| 82 | * 8 x 8 channels LoRa packet detectors,8 x SF5-SF12 LoRa demodulators,8 x SF5-SF10 LoRa demodulators,125/250/500 kHz LoRa demodulator and 1 x (G)FSK demodulator | ||
| 83 | * Dual digital TX & RX radio front-end interfaces | ||
| 84 | * 10 programmable parallel demodulation paths | ||
| 85 | * Dynamic data-rate (DDR) adaptation | ||
| 86 | * True antenna diversity or simultaneous dual-band operation | ||
| 87 | |||
| 88 | (% style="color:#037691" %)**Cellular 4G LTE (optional):** | ||
| 89 | |||
| 90 | * Quectel [[**EC25 LTE module**>>url:https://www.quectel.com/product/ec25minipcie.htm]] | ||
| 91 | * Micro SIM Slot | ||
| 92 | * External 4G Sticker Antenna. | ||
| 93 | * Up to 150Mbps downlink and 50Mbps uplink data rates | ||
| 94 | * Worldwide LTE,UMTS/HSPA+ and GSM/GPRS/EDGE coverage | ||
| 95 | * MIMO technology meets demands for data rate and link reliability in modem wireless communication systems | ||
| 96 | |||
| 97 | == 1.3 Features == | ||
| 98 | |||
| 99 | |||
| 100 | * Open Source OpenWrt system | ||
| 101 | * Managed by Web GUI, SSH via WAN or WiFi | ||
| 102 | * Remote access with Reverse-SSH or remote.it | ||
| 103 | * Emulates 49x LoRa demodulators | ||
| 104 | * LoRaWAN Gateway | ||
| 105 | * 10 programmable parallel demodulation paths | ||
| 106 | * Pre-configure to support different LoRaWAN regional settings. | ||
| 107 | * Allow to customize LoRaWAN regional parameters. | ||
| 108 | * Support Local decode ABP end node info and transfer to MQTT server | ||
| 109 | * Support different level log in. | ||
| 110 | * Support Semtech Packet Forwarder | ||
| 111 | * Support LoRaWAN basic station. | ||
| 112 | * Optional 3G/4G cellular connection | ||
| 113 | |||
| 114 | == 1.4 Hardware System Structure == | ||
| 115 | |||
| 116 | |||
| 117 | [[image:image-20220830153228-1.png]] | ||
| 118 | |||
| 119 | |||
| 120 | == 1.5 LPS8N Applications == | ||
| 121 | |||
| 122 | |||
| 123 | [[image:1657079055940-721.png]] | ||
| 124 | |||
| 125 | |||
| 126 | == 1.6 LED Indicators == | ||
| 127 | |||
| 128 | |||
| 129 | LPS8N has totally four LEDs, They are: | ||
| 130 | |||
| 131 | * **Power LED **[[image:image-20220706115518-1.png||height="15" width="16"]] : This (% style="color:red" %)**RED LED**(%%) will be **solid on** if the device is properly powered. | ||
| 132 | * **Wireless LED** [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/LG308N%20-%20LoRaWAN%20Gateway%20User%20Manual/WebHome/image-20220705165446-6.png?width=15&height=15&rev=1.1||alt="image-20220705165446-6.png" height="15" width="15"]]: This (% style="color:green" %)**GREEN LED**(%%) will be **solid on** if the device enablel WiFi AP. | ||
| 133 | * **SYS LED ** [[image:image-20220706115518-3.png||height="16" width="16"]] : This **RGB LED** will shows different colors on different state: | ||
| 134 | ** (% style="color:blue" %)**SOLID BLUE**(%%): Device is alive with LoRaWAN server connection. | ||
| 135 | ** (% style="color:blue" %)**BLINKING BLUE**(%%): a) Device has internet connection but no LoRaWAN Connection. or b) Device is in booting stage, in this stage, it will (% style="color:blue" %)**BLINKING BLUE**(%%) for several seconds and then with (% style="color:red" %)**SOLID RED**(%%) and (% style="color:blue" %)**BLINKING BLUE**(%%) together | ||
| 136 | ** (% style="color:red" %)**SOLID RED**(%%): Device doesn't have Internet connection. | ||
| 137 | |||
| 138 | * **ETH LED **[[image:image-20220706115518-4.png||height="15" width="17"]] : This LED shows the ETH interface connection status. | ||
| 139 | |||
| 140 | == 1.7 Button Instruction == | ||
| 141 | |||
| 142 | |||
| 143 | LPS8N has a black toggle button, which is: | ||
| 144 | |||
| 145 | |||
| 146 | (% style="color:blue" %)**//➢ //Long press 4-5s: **(%%)the gateway will reload the Network and Initialize wifi configuration | ||
| 147 | |||
| 148 | **LED status: ** SYS LED will BLINKING BLUE Until the reload is finished. | ||
| 149 | |||
| 150 | |||
| 151 | (% style="color:blue" %)**➢ Long press more than 30s: **(%%)the gateway will restart and restore factory settings. | ||
| 152 | |||
| 153 | **LED status: ** When the user releases the button, the LED will TURN OFF. | ||
| 154 | |||
| 155 | |||
| 156 | = 2. Access and Configure LPS8N = | ||
| 157 | |||
| 158 | |||
| 159 | ((( | ||
| 160 | The LPS8N is configured as a WiFi Access Point by factory default. You can access and configure the LPS8N after connecting to its WiFi network, or via its WAN Ethernet port. | ||
| 161 | ))) | ||
| 162 | |||
| 163 | |||
| 164 | == 2.1 Find IP address of LPS8N == | ||
| 165 | |||
| 166 | === 2.1.1 Connect via WiFi === | ||
| 167 | |||
| 168 | |||
| 169 | [[image:1657085974260-168.png]] | ||
| 170 | |||
| 171 | |||
| 172 | At the first boot of LPS8N, it will auto generate a WiFi network called (% style="color:green" %)**//dragino-xxxxxx //**(% style="color:black" %)with password: (% style="background-color:yellow" %)dragino+dragino | ||
| 173 | |||
| 174 | |||
| 175 | [[image:1652413127647-377.png]] | ||
| 176 | |||
| 177 | |||
| 178 | ((( | ||
| 179 | User can use a PC to connect to this WiFi network. The PC will get an IP address 10.130.1.xxx and the LPS8N has the default IP (% style="color:green" %)10.130.1.1 | ||
| 180 | |||
| 181 | |||
| 182 | ))) | ||
| 183 | |||
| 184 | === 2.1.2 Connect via Ethernet with DHCP IP from router === | ||
| 185 | |||
| 186 | |||
| 187 | [[image:1657086105922-299.png]] | ||
| 188 | |||
| 189 | |||
| 190 | ((( | ||
| 191 | Alternatively, connect the LPS8N Ethernet port to your router and LPS8N will 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 LPS8N. You can also use this IP to connect. | ||
| 192 | |||
| 193 | |||
| 194 | ))) | ||
| 195 | |||
| 196 | === 2.1.3 Connect via WiFi with DHCP IP from router === | ||
| 197 | |||
| 198 | |||
| 199 | [[image:1657086192720-649.png]] | ||
| 200 | |||
| 201 | |||
| 202 | If the LPS8N already connect to the router via WiFi, use can use the WiFi IP to connect to LPS8N. | ||
| 203 | |||
| 204 | |||
| 205 | === 2.1.4 Connect via Ethernet with fall back ip === | ||
| 206 | |||
| 207 | |||
| 208 | The WAN port also has a [[fall back ip address>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/LPS8N%20-%20LoRaWAN%20Gateway%20User%20Manual/#H11.3A0IconfiguredLPS8NforWiFiaccessandlostitsIP.Whattodonow3F]] for access if user doesn't connect to uplink router. Click [[here>>||anchor="H11.3A0IconfiguredLPS8NforWiFiaccessandlostitsIP.Whattodonow3F"]] to see how to configure. | ||
| 209 | |||
| 210 | |||
| 211 | == 2.2 Access Configure Web UI == | ||
| 212 | |||
| 213 | |||
| 214 | **Web Interface** | ||
| 215 | |||
| 216 | Open a browser on the PC and type the LPS8N ip address (depends on your connect method) | ||
| 217 | |||
| 218 | [[http:~~/~~/10.130.1.1/>>url:http://10.130.1.1/]] (Access via WiFi AP network) | ||
| 219 | |||
| 220 | or | ||
| 221 | |||
| 222 | http:~/~/IP_ADDRESS or [[http:~~/~~/ IP_ADDRESS:8000>>url:http://192.168.1.xx:8000]] | ||
| 223 | |||
| 224 | |||
| 225 | You will see the login interface of LPS8N as shown below. | ||
| 226 | |||
| 227 | The account details for Web Login are: | ||
| 228 | |||
| 229 | (% style="color:blue" %)**User Name: root** | ||
| 230 | |||
| 231 | (% style="color:blue" %)**Password: dragino** | ||
| 232 | |||
| 233 | [[image:1652414287022-223.png]] | ||
| 234 | |||
| 235 | |||
| 236 | = 3. Typical Network Setup = | ||
| 237 | |||
| 238 | == 3.1 Overview == | ||
| 239 | |||
| 240 | |||
| 241 | The LPS8N supports flexible network set up for different environments. This section describes the typical network topology. The network set up includes: | ||
| 242 | |||
| 243 | * **WAN Port Internet Mode** | ||
| 244 | * **WiFi Client Mode** | ||
| 245 | * **WiFi AP Mode** | ||
| 246 | |||
| 247 | == 3.2 Use WAN port to access Internet == | ||
| 248 | |||
| 249 | |||
| 250 | By default, the LPS8N is set to use the WAN port to connect to an upstream network. When you connect the LPS8N's WAN port to an upstream router, LPS8N will get an IP address from the router and have Internet access via the upstream router. The network status can be checked in the (% style="color:#4f81bd" %)**home page**: | ||
| 251 | |||
| 252 | |||
| 253 | [[image:1657088560833-398.png]] | ||
| 254 | |||
| 255 | |||
| 256 | == 3.3 Access the Internet as a WiFi Client == | ||
| 257 | |||
| 258 | |||
| 259 | In the WiFi Client Mode, LPS8N acts as a WiFi client and gets DHCP from an upstream router via WiFi. | ||
| 260 | |||
| 261 | ((( | ||
| 262 | The settings for WiFi Client is under page (% style="color:#4f81bd" %)**System~-~-> WiFi ~-~-> WiFi WAN Client Settings** | ||
| 263 | |||
| 264 | |||
| 265 | [[image:1657088818095-182.png]] | ||
| 266 | ))) | ||
| 267 | |||
| 268 | |||
| 269 | ((( | ||
| 270 | In the WiFi Survey Choose the WiFi AP, and input the Passphrase then click Save & Apply to connect. | ||
| 271 | |||
| 272 | |||
| 273 | ))) | ||
| 274 | |||
| 275 | == 3.4 Use built-in 4G modem for internet access == | ||
| 276 | |||
| 277 | |||
| 278 | ((( | ||
| 279 | ((( | ||
| 280 | If the LPS8N has 3G/4G Cellular modem, user can use it as main internet connection or back up. | ||
| 281 | ))) | ||
| 282 | |||
| 283 | |||
| 284 | ((( | ||
| 285 | First, install the Micro SIM card as below direction | ||
| 286 | ))) | ||
| 287 | |||
| 288 | ((( | ||
| 289 | Second, Power off/ ON LPS8N to let it detect the SIM card. | ||
| 290 | ))) | ||
| 291 | ))) | ||
| 292 | |||
| 293 | |||
| 294 | [[image:image-20241231155446-1.jpeg||height="263" width="888"]] | ||
| 295 | |||
| 296 | ((( | ||
| 297 | |||
| 298 | ))) | ||
| 299 | |||
| 300 | ((( | ||
| 301 | The set up page is (% style="color:#4f81bd" %)**System ~-~-> Cellular** | ||
| 302 | ))) | ||
| 303 | |||
| 304 | ((( | ||
| 305 | While use the cellular as Backup WAN, device will use Cellular for internet connection while WAN port or WiFi is not valid and switch back to WAN port or WiFi after they recover. | ||
| 306 | |||
| 307 | |||
| 308 | ))) | ||
| 309 | |||
| 310 | ((( | ||
| 311 | [[image:1657090932270-444.png]] | ||
| 312 | ))) | ||
| 313 | |||
| 314 | |||
| 315 | |||
| 316 | When cellular fails to connect or has problems, users can refer to this link to Trouble Shooting:**[[How to Trouble Shooting if Cellular connection fails>>https://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20cellular%20network%20connection/#H2.1ForLPS8N2FDLOS8N2FLG308N]]** | ||
| 317 | |||
| 318 | == 3.5 Check Internet connection == | ||
| 319 | |||
| 320 | |||
| 321 | In the (% style="color:#4f81bd" %)**home**(%%) page, we can check the Internet connection. | ||
| 322 | |||
| 323 | * GREEN Tick [[image:1652436675869-206.png||height="14" width="15"]] : This interface has Internet connection. | ||
| 324 | * Yellow Tick [[image:1652436705761-420.png||height="15" width="15"]] : This interface has IP address but don't use it for internet connection. | ||
| 325 | * RED Cross [[image:1652436787176-950.png||height="14" width="15"]] : This interface doesn't connected. | ||
| 326 | |||
| 327 | [[image:1657091099235-452.png]] | ||
| 328 | |||
| 329 | |||
| 330 | = 4. Example: Configure as a LoRaWAN gateway = | ||
| 331 | |||
| 332 | |||
| 333 | LPS8N is fully compatible with LoRaWAN protocol. It uses the legacy Semtech Packet forwarder to forward the LoRaWAN packets to server. The structure is as below. | ||
| 334 | |||
| 335 | |||
| 336 | ((( | ||
| 337 | [[image:image-20220826090251-1.png]] | ||
| 338 | ))) | ||
| 339 | |||
| 340 | ((( | ||
| 341 | This chapter describes how to use the LPS8N to work with (TTN v3)[[ LoRaWAN Server>>url:https://www.thethingsnetwork.org/]] ([[www.thethingsnetwork.org>>url:http://www.thethingsnetwork.org/]]) | ||
| 342 | ))) | ||
| 343 | |||
| 344 | |||
| 345 | == 4.1 Create a gateway in TTN V3 Server == | ||
| 346 | |||
| 347 | |||
| 348 | (% style="color:blue" %)**Step 1: Get a Unique gateway ID.** | ||
| 349 | |||
| 350 | |||
| 351 | ((( | ||
| 352 | Every LPS8N has a unique gateway id. The ID can be found at LoRaWAN page: | ||
| 353 | |||
| 354 | |||
| 355 | ))) | ||
| 356 | |||
| 357 | ((( | ||
| 358 | [[image:1657091583941-544.png]] | ||
| 359 | |||
| 360 | |||
| 361 | ))) | ||
| 362 | |||
| 363 | The example gateway id is: (% style="color:green" %)**a840411e96744154** | ||
| 364 | |||
| 365 | |||
| 366 | |||
| 367 | (% style="color:blue" %)**Step 2: Sign up a user account in TTN server** | ||
| 368 | |||
| 369 | |||
| 370 | [[**https:~~/~~/account.thethingsnetwork.org/register**>>url:https://account.thethingsnetwork.org/register]] | ||
| 371 | |||
| 372 | |||
| 373 | [[image:1657091739530-531.png]] | ||
| 374 | |||
| 375 | |||
| 376 | |||
| 377 | (% style="color:blue" %)**Step 3: Choose the TTNv3 Cluster Picker** | ||
| 378 | |||
| 379 | |||
| 380 | ((( | ||
| 381 | [[image:1657091719947-297.png]] | ||
| 382 | |||
| 383 | |||
| 384 | ))) | ||
| 385 | |||
| 386 | (% style="color:red" %)**Note: Choose the cluster corresponds to a specific Gateway server address** | ||
| 387 | |||
| 388 | |||
| 389 | * Europe 1** (% style="color:red" %)corresponding Gateway server address:(%%)**(% style="color:red" %) (% style="color:black" %)eu1.cloud.thethings.network | ||
| 390 | * North America 1 (% style="color:red" %)**corresponding Gateway server address: **(% style="color:black" %)nam1.cloud.thethings.network | ||
| 391 | * Australia 1 (% style="color:red" %)**corresponding Gateway server address: **(% style="color:black" %)au1.cloud.thethings.network | ||
| 392 | * Legacy V2 Console : (% style="color:red" %)**TTN v2 shuts down in December 2021** | ||
| 393 | |||
| 394 | (% style="color:blue" %)**Step 4: Create a Gateway** | ||
| 395 | |||
| 396 | |||
| 397 | [[image:1657091941182-367.png]] | ||
| 398 | |||
| 399 | Click the Gateway icon and then click Add gateway. | ||
| 400 | |||
| 401 | |||
| 402 | Open the following page: | ||
| 403 | |||
| 404 | |||
| 405 | [[image:image-20220706155323-5.png||height="579" width="1060"]] | ||
| 406 | |||
| 407 | |||
| 408 | [[image:image-20220706155323-6.png||height="582" width="1066"]] | ||
| 409 | |||
| 410 | |||
| 411 | ((( | ||
| 412 | (% style="color:red" %)**Notice: Gateway Server address must match the gateway configuration, otherwise you will have problem for End Node to join the network.** | ||
| 413 | |||
| 414 | |||
| 415 | ))) | ||
| 416 | |||
| 417 | After creating the gateway, you can see the gateway info, as below. | ||
| 418 | |||
| 419 | [[image:1657094130908-567.png]](% style="display:none" %) | ||
| 420 | |||
| 421 | |||
| 422 | == 4.2 Configure LPS8N to connect to TTN v3 == | ||
| 423 | |||
| 424 | |||
| 425 | ((( | ||
| 426 | You can now configure the LPS8N to let it connect to TTN network V3. | ||
| 427 | ))) | ||
| 428 | |||
| 429 | ((( | ||
| 430 | Make sure your LPS8N has a working Internet Connection first. | ||
| 431 | ))) | ||
| 432 | |||
| 433 | ((( | ||
| 434 | Choose the right server provider and click (% style="color:#4f81bd" %)**Save&Apply.** | ||
| 435 | |||
| 436 | |||
| 437 | ))) | ||
| 438 | |||
| 439 | [[image:1657094183213-301.png]] | ||
| 440 | |||
| 441 | |||
| 442 | (% style="color:red" %)**Note: The server address must match the Gateway server address you choose in TTN V3.** | ||
| 443 | |||
| 444 | |||
| 445 | In the home page, we can see the LoRaWAN connection is ready now. | ||
| 446 | |||
| 447 | |||
| 448 | [[image:1657094202420-798.png]] | ||
| 449 | |||
| 450 | |||
| 451 | |||
| 452 | In TTN v3 portal, we can also see the gateway is connected. | ||
| 453 | |||
| 454 | [[image:1657094221515-510.png]] | ||
| 455 | |||
| 456 | |||
| 457 | == 4.3 Configure frequency == | ||
| 458 | |||
| 459 | |||
| 460 | We also need to set the frequency plan in LPS8N to match the end node we use, so to receive the LoRaWAN packets from the LoRaWAN sensor. | ||
| 461 | |||
| 462 | |||
| 463 | [[image:1657094249818-468.png]] | ||
| 464 | |||
| 465 | |||
| 466 | |||
| 467 | In logread page, user can check the frequency actually used. | ||
| 468 | |||
| 469 | [[image:1657094333704-207.png]] | ||
| 470 | |||
| 471 | |||
| 472 | == 4.4 Add a LoRaWAN End Device == | ||
| 473 | |||
| 474 | |||
| 475 | ((( | ||
| 476 | This section shows how to add a LoRaWAN End device to a LoRaWAN network and see the data from TTN web site. | ||
| 477 | ))) | ||
| 478 | |||
| 479 | ((( | ||
| 480 | We use [[LT-22222-L>>url:http://www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html]] IO Controller as a reference device - the setup for other LoRaWAN devices will be similar. | ||
| 481 | ))) | ||
| 482 | |||
| 483 | [[image:1652422794767-871.png]] | ||
| 484 | |||
| 485 | |||
| 486 | ((( | ||
| 487 | (% style="color:blue" %)**Step 1**: (%%)Create a Device definition in TTN v3 with the OTAA keys from the example LT-22222-L IO Controller device. | ||
| 488 | |||
| 489 | |||
| 490 | ))) | ||
| 491 | |||
| 492 | ((( | ||
| 493 | Three codes are required to define the device in TTN v3: | ||
| 494 | ))) | ||
| 495 | |||
| 496 | * DEV EUI - Unique ID code for a particular device. | ||
| 497 | * APP EUI - ID code for an Application defined in TTN v3. | ||
| 498 | * APP Key - Unique key to secure communications with a particular device. | ||
| 499 | |||
| 500 | ((( | ||
| 501 | A set of these codes are stored in each device by the manufacturer as the default codes for that particular device. Each device is shipped with a sticker with the default Device EUI as shown below. | ||
| 502 | |||
| 503 | |||
| 504 | ))) | ||
| 505 | |||
| 506 | [[image:1657094382177-591.png]] | ||
| 507 | |||
| 508 | |||
| 509 | ((( | ||
| 510 | (% style="color:red" %)**Note: You may be able to change these codes in a device by using a configuration facility on the device e.g. the LT-22222 uses a serial port access and a series of AT commands. Changing the codes may be necessary in the case where you have to use codes assigned by a LoRa WAN server.** | ||
| 511 | |||
| 512 | |||
| 513 | ))) | ||
| 514 | |||
| 515 | ((( | ||
| 516 | For the TTN v3 server, you can use the codes set in the device as in the following example. | ||
| 517 | ))) | ||
| 518 | |||
| 519 | ((( | ||
| 520 | Select **Add Application** to open the screen below. | ||
| 521 | |||
| 522 | |||
| 523 | ))) | ||
| 524 | |||
| 525 | [[image:1657094417175-831.png]] | ||
| 526 | |||
| 527 | Open the **Application **select** Add end device** | ||
| 528 | |||
| 529 | |||
| 530 | Start Register the end device | ||
| 531 | |||
| 532 | [[image:1657094444802-101.png]] | ||
| 533 | |||
| 534 | ((( | ||
| 535 | Select OTAA activation mode | ||
| 536 | |||
| 537 | |||
| 538 | ))) | ||
| 539 | |||
| 540 | ((( | ||
| 541 | The LoRaWAN version for your device should be provided by the manufacturer in a datasheet as LoRaWAN version or LoRaWAN specification. The most commonly used LoRaWAN versions are v1.0.2 and v1.0.3. | ||
| 542 | ))) | ||
| 543 | |||
| 544 | [[image:1657094475730-208.png]] | ||
| 545 | |||
| 546 | First, input the End device ID, AppEUI and DevEUI. | ||
| 547 | |||
| 548 | |||
| 549 | [[image:1657094646429-966.png]] | ||
| 550 | |||
| 551 | Secondly, choose the corresponding frequency and LoRaWAN class capabilities. | ||
| 552 | |||
| 553 | |||
| 554 | [[image:1657094674045-755.png]] | ||
| 555 | |||
| 556 | ((( | ||
| 557 | Finally, Application layer settings input the corresponding AppKey. Before saving the configuration, check that the data matches the device. | ||
| 558 | |||
| 559 | |||
| 560 | ))) | ||
| 561 | |||
| 562 | ((( | ||
| 563 | (% style="color:blue" %)**Step 2**: (%%)Power on LT-22222-L device and it will automatically join the TTN network. After joining successfully, it will start to upload messages to the TTN v3. Select the Live data tab and you will see the data appearing in the panel. | ||
| 564 | |||
| 565 | |||
| 566 | ))) | ||
| 567 | |||
| 568 | ((( | ||
| 569 | (% style="color:red" %)**Note that it may take some time for the device data to appear in the TTN v3 display.** | ||
| 570 | |||
| 571 | |||
| 572 | ))) | ||
| 573 | |||
| 574 | [[image:1657094791060-639.png]] | ||
| 575 | |||
| 576 | |||
| 577 | = 5. Web Configure Pages = | ||
| 578 | |||
| 579 | == 5.1 Home == | ||
| 580 | |||
| 581 | |||
| 582 | Shows the system running status. | ||
| 583 | |||
| 584 | |||
| 585 | [[image:1657094893942-726.png]] | ||
| 586 | |||
| 587 | |||
| 588 | == 5.2 LoRa Settings == | ||
| 589 | |||
| 590 | === 5.2.1 LoRa ~-~-> LoRa === | ||
| 591 | |||
| 592 | |||
| 593 | ((( | ||
| 594 | This page shows the LoRa Radio Settings. There are a set of default frequency band according to LoRaWAN protocol, and user can customized the band* as well. | ||
| 595 | ))) | ||
| 596 | |||
| 597 | ((( | ||
| 598 | Different LPS8N hardware version can support different frequency range: | ||
| 599 | ))) | ||
| 600 | |||
| 601 | * (% style="color:blue" %)**868**(%%): valid frequency: 863Mhz ~~ 870Mhz. for bands EU868, RU864, IN865 or KZ865. | ||
| 602 | * (% style="color:blue" %)**915**(%%): valid frequency: 902Mhz ~~ 928Mhz. for bands US915, AU915, AS923 or KR920 | ||
| 603 | |||
| 604 | ((( | ||
| 605 | |||
| 606 | |||
| 607 | ((( | ||
| 608 | After user choose the frequency plan, he can see the actually frequency in used by checking the page (% style="color:green" %)**LogRead ~-~-> LoRa Log** | ||
| 609 | |||
| 610 | |||
| 611 | ))) | ||
| 612 | ))) | ||
| 613 | |||
| 614 | [[image:1657094930903-357.png]] | ||
| 615 | |||
| 616 | (% style="color:red" %)**Note *:** **[[See this instruction for how to customize frequency band>>doc:Main.How to customized LoRaWAN frequency band.WebHome]]** | ||
| 617 | |||
| 618 | |||
| 619 | === 5.2.2 LoRa ~-~-> ABP Decryption === | ||
| 620 | |||
| 621 | |||
| 622 | The LPS8N can communicate with LoRaWAN ABP End Node without the need of LoRaWAN server. It can be used in some cases such as: | ||
| 623 | |||
| 624 | * No internet connection. | ||
| 625 | * User wants to get data forward in gateway and forward to their server based on MQTT/HTTP, etc. (Combine ABP communication method and [[MQTT forward together>>doc:Main.MQTT Forward Instruction.WebHome]]). | ||
| 626 | |||
| 627 | ((( | ||
| 628 | Detail of this feature: **[[Communication with ABP End Node>>doc:Main.Communicate with ABP End Node without LoRaWAN Network Server --- LG308.WebHome]]** | ||
| 629 | |||
| 630 | |||
| 631 | ))) | ||
| 632 | |||
| 633 | [[image:1657095412271-942.png]] | ||
| 634 | |||
| 635 | |||
| 636 | == (% data-sider-select-id="9385f434-0cee-4e27-b68d-01cc94864f95" %)5.3 LoRaWAN Settings(%%) == | ||
| 637 | |||
| 638 | === 5.3.1 LoRaWAN ~-~-> LoRaWAN === | ||
| 639 | |||
| 640 | |||
| 641 | 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. | ||
| 642 | |||
| 643 | |||
| 644 | [[image:image-20240419150452-9.png||height="761" width="1098"]] | ||
| 645 | |||
| 646 | |||
| 647 | (% style="color:red" %)**Note:** | ||
| 648 | |||
| 649 | ~*: User can ignore the latitude and longitude settings here, LPS8N will use the actually value from GPS module. | ||
| 650 | |||
| 651 | ~**: Packet filter is to drop the unwanted LoRaWAN packet, instruction see here: | ||
| 652 | |||
| 653 | **See:** **[[Filter unwanted LoRaWAN packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]** | ||
| 654 | |||
| 655 | |||
| 656 | === 5.3.2 LoRaWAN ~-~-> LoRaWAN ~-~- Basic Station === | ||
| 657 | |||
| 658 | |||
| 659 | [[image:image-20230406172421-1.png||height="563" width="1089"]] | ||
| 660 | |||
| 661 | |||
| 662 | ((( | ||
| 663 | Please see this instruction to know more detail and a demo of how to connect to **[[AWS-IoT LoRaWAN Core>>doc:Main.AWS IoT Core for LoRaWAN.WebHome]].** | ||
| 664 | |||
| 665 | |||
| 666 | The basic station mode support **TTN/AWS/Chirpstack/ThingPark/Senet** Platform. | ||
| 667 | |||
| 668 | Instruction: | ||
| 669 | |||
| 670 | [[The Thing Network>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20TTN/#H3.A0GatewayRegistrationforBasicsStation]] | ||
| 671 | |||
| 672 | [[AWS-IoT LoRaWAN Core>>http://wiki.dragino.com/xwiki/bin/view/Main/AWS%20IoT%20Core%20for%20LoRaWAN/]] | ||
| 673 | |||
| 674 | [[Chirpstack>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H3.A0GatewayRegistrationforBasicsStation]] | ||
| 675 | |||
| 676 | ThingPark | ||
| 677 | |||
| 678 | [[Senet>>http://wiki.dragino.com/xwiki/bin/view/Main/Connection%20to%20Senet/#H3.A0SemtechBasicStation]] | ||
| 679 | |||
| 680 | |||
| 681 | |||
| 682 | ))) | ||
| 683 | |||
| 684 | === 5.3.3 LoRaWAN ~-~-> LORIOT === | ||
| 685 | |||
| 686 | |||
| 687 | ((( | ||
| 688 | Settings to communicate to LORIOT LoRaWAN Network Server: [[https:~~/~~/www.loriot.io/>>url:https://www.loriot.io/]] | ||
| 689 | ))) | ||
| 690 | |||
| 691 | ((( | ||
| 692 | Instruction: **[[Notes for LORIOT>>doc:Main.Notes for LORIOT.WebHome]]** | ||
| 693 | |||
| 694 | |||
| 695 | ))) | ||
| 696 | |||
| 697 | [[image:1652428648903-878.png||height="266" width="731"]] | ||
| 698 | |||
| 699 | |||
| 700 | == (% data-sider-select-id="901b4be6-9ff2-4d69-bbb1-a2ce5a602f9b" %)5.4 MQTT Settings(%%) == | ||
| 701 | |||
| 702 | |||
| 703 | ((( | ||
| 704 | If end nodes works in ABP mode, user can configure LPS8N to transfer the data to MQTT broker, | ||
| 705 | ))) | ||
| 706 | |||
| 707 | ((( | ||
| 708 | Instruction: **[[MQTT Forward Instruction>>doc:Main.MQTT Forward Instruction.WebHome]]** | ||
| 709 | ))) | ||
| 710 | |||
| 711 | |||
| 712 | [[image:1652428705046-212.png||height="417" width="733"]] | ||
| 713 | |||
| 714 | |||
| 715 | == (% data-sider-select-id="901b4be6-9ff2-4d69-bbb1-a2ce5a602f9b" %)5.5 Network(%%) == | ||
| 716 | |||
| 717 | === (% data-sider-select-id="5eaf7530-1272-4643-b349-9de78d98959c" %)5.5.1 (% data-sider-select-id="901b4be6-9ff2-4d69-bbb1-a2ce5a602f9b" %)Network(% data-sider-select-id="5eaf7530-1272-4643-b349-9de78d98959c" %) ~-~-> Network Status(%%) === | ||
| 718 | |||
| 719 | |||
| 720 | [[image:image-20240419143226-2.png||height="742" width="950"]] | ||
| 721 | |||
| 722 | |||
| 723 | === (% data-sider-select-id="5eaf7530-1272-4643-b349-9de78d98959c" %)5.5.2 (% data-sider-select-id="901b4be6-9ff2-4d69-bbb1-a2ce5a602f9b" %)Network(% data-sider-select-id="5eaf7530-1272-4643-b349-9de78d98959c" %) ~-~-> Network(%%) === | ||
| 724 | |||
| 725 | |||
| 726 | ((( | ||
| 727 | (% data-sider-select-id="040776ba-bc4f-4586-9d1c-eb5b5c7f1e7d" style="color:#037691" %)**__LAN Settings: __**(%%)When the LPS8N has the AP enable, LAN settings specify the network info for LPS8N's own network. | ||
| 728 | ))) | ||
| 729 | |||
| 730 | ((( | ||
| 731 | (% style="color:#037691" %)__**WAN Settings: **__(%%)Setting for LPS8N WAN port | ||
| 732 | ))) | ||
| 733 | |||
| 734 | ((( | ||
| 735 | (% style="color:#037691" %)__**WiFi Settings: **__** **(%%)Setting for LPS8N WiFi IP when use it as WiFi Client | ||
| 736 | ))) | ||
| 737 | |||
| 738 | [[image:image-20240419143347-3.png]] | ||
| 739 | |||
| 740 | |||
| 741 | === (% data-sider-select-id="5eaf7530-1272-4643-b349-9de78d98959c" %)5.5.3 (% data-sider-select-id="901b4be6-9ff2-4d69-bbb1-a2ce5a602f9b" %)Network(% data-sider-select-id="5eaf7530-1272-4643-b349-9de78d98959c" %) ~-~-> WiFi(%%) === | ||
| 742 | |||
| 743 | |||
| 744 | (% data-sider-select-id="e57f4efb-f39f-4e11-bde3-f13f9b08254d" %) | ||
| 745 | LPS8N WiFi Settings. | ||
| 746 | |||
| 747 | |||
| 748 | [[image:image-20240419143504-4.png||height="500" width="946"]] | ||
| 749 | |||
| 750 | |||
| 751 | === (% data-sider-select-id="be4c9623-8f61-4499-8859-fd388d34b2ab" %)5.5.4 Network ~-~-> Cellular(%%) === | ||
| 752 | |||
| 753 | |||
| 754 | While use the cellular as Backup WAN, device will use Cellular for internet connection while WAN port or WiFi is not valid and switch back to WAN port or WiFi after they recover. | ||
| 755 | |||
| 756 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/LPS8N%20-%20LoRaWAN%20Gateway%20User%20Manual/WebHome/1657155507672-204.png?rev=1.1||alt="1657155507672-204.png"]] | ||
| 757 | |||
| 758 | (% style="color:red" %)**Note *: For LPS8N which doesn't have the cellular module, this page will shows Cellular not detected.** | ||
| 759 | |||
| 760 | When cellular fails to connect or has problems, users can refer to this link to Trouble Shooting:**[[How to Trouble Shooting if Cellular connection fails>>https://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20cellular%20network%20connection/#H2.1ForLPS8N2FDLOS8N2FLG308N]]** | ||
| 761 | |||
| 762 | == (% data-sider-select-id="9da31818-a029-4f0a-b9ff-645e219e4f4e" %)5.6 System(%%) == | ||
| 763 | |||
| 764 | === (% data-sider-select-id="5eaf7530-1272-4643-b349-9de78d98959c" %)5.6.1 System ~-~-> System Overview(%%) === | ||
| 765 | |||
| 766 | |||
| 767 | Shows the system info: | ||
| 768 | |||
| 769 | |||
| 770 | [[image:image-20220826091810-6.png]] | ||
| 771 | |||
| 772 | |||
| 773 | === (% data-sider-select-id="63bebde2-7978-4bee-90b2-58884b714aea" %)5.6.2 System ~-~-> General ( login settings)(%%) === | ||
| 774 | |||
| 775 | |||
| 776 | [[image:image-20240419144019-5.png]] | ||
| 777 | |||
| 778 | ((( | ||
| 779 | |||
| 780 | |||
| 781 | (% data-sider-select-id="00e0325f-1698-4166-b578-eba5340e7e8e" style="color:#037691" %)**__System Password:__** | ||
| 782 | ))) | ||
| 783 | |||
| 784 | ((( | ||
| 785 | There are two login for LPS8N: (% style="color:blue" %)**root /dragino** (%%)or (% style="color:blue" %)**admin /dragino**. (%%)Both root and admin has the same right for WEB access. But root user has also the right to access via SSH to Linux system. admin only able to access WEB interface. | ||
| 786 | ))) | ||
| 787 | |||
| 788 | ((( | ||
| 789 | This page can be used to set the password for them. | ||
| 790 | ))) | ||
| 791 | |||
| 792 | ((( | ||
| 793 | (% style="color:#037691" %)**__Timezone: __**(%%)Set device timezone. | ||
| 794 | ))) | ||
| 795 | |||
| 796 | ((( | ||
| 797 | (% data-sider-select-id="be6bdce7-110b-4367-bcd5-d176d288153e" %) | ||
| 798 | (% data-sider-select-id="31384c06-f8bc-420e-ba58-0a2d5916e600" style="color:#037691" %)**__Port forwarding: __**(%%)Enable/Disable the HTTP and SSH access via WAN interface. | ||
| 799 | |||
| 800 | (% data-sider-select-id="0e3c0e0e-5796-4a1a-b3da-cdfc059c383d" %) | ||
| 801 | (% data-sider-select-id="31384c06-f8bc-420e-ba58-0a2d5916e600" style="color:#037691" %)**__Fallback Settings: __**(%%)Enable/Disable the Fallback interface. | ||
| 802 | |||
| 803 | (% data-sider-select-id="31384c06-f8bc-420e-ba58-0a2d5916e600" style="color:#037691" %)**__Keepalive_Script: __**(%%)Set the keepalive_scrpt interval. | ||
| 804 | |||
| 805 | (% data-sider-select-id="31384c06-f8bc-420e-ba58-0a2d5916e600" style="color:#037691" %)**__Logread Level: __**(%%)Change the logread level. | ||
| 806 | |||
| 807 | (% data-sider-select-id="2140bc4a-c71f-4387-845a-510c0b050940" %) | ||
| 808 | (% data-sider-select-id="31384c06-f8bc-420e-ba58-0a2d5916e600" style="color:#037691" %)**__Eable Internet Detect and Recover: __**(%%)Enable/Disable the Internet Detect interface,Internet Detect is enabled by default. When there is no gateway network, it will reboot after 15 minutes. | ||
| 809 | |||
| 810 | |||
| 811 | === (% data-sider-select-id="7b902d7f-391d-4277-92fc-77ddd2546b9a" %)5.6.3 System ~-~-> (%%)Backup/Restore Config === | ||
| 812 | |||
| 813 | |||
| 814 | [[image:image-20240419145717-7.png||height="240" width="890"]] | ||
| 815 | |||
| 816 | |||
| 817 | (% data-sider-select-id="f13ff9e2-da2d-4df6-a9e9-427b7c0e69e5" %) | ||
| 818 | === (% data-sider-select-id="7b902d7f-391d-4277-92fc-77ddd2546b9a" %)5.6.4 System ~-~-> (%%)Remote.it === | ||
| 819 | |||
| 820 | In the **System-> Remoteit** interface, users can configure the gateway to be accessed remotely via Remote.it. | ||
| 821 | |||
| 822 | the users can refer to this link to configure them: **[[Monitor & Remote Access Gateway>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Monitor%20%26%20Remote%20Access%20Gateway/?Remote%20Access#H2.1A0RemoteAccessviaRemote.it.]]** | ||
| 823 | |||
| 824 | [[image:image-20240419150201-8.png||height="535" width="882"]] | ||
| 825 | |||
| 826 | |||
| 827 | |||
| 828 | ))) | ||
| 829 | |||
| 830 | === (% data-sider-select-id="7b902d7f-391d-4277-92fc-77ddd2546b9a" %)5.6.5 System ~-~-> Remote Mgnt & Auto Provision(%%) === | ||
| 831 | |||
| 832 | |||
| 833 | Auto Provision is the feature for batch configure and remote management. It can be used in below two cases: | ||
| 834 | |||
| 835 | |||
| 836 | [[image:image-20220707112053-4.png||height="451" width="995"]] | ||
| 837 | |||
| 838 | [[image:image-20220707112053-5.png||height="453" width="1004"]] | ||
| 839 | |||
| 840 | (% style="display:none" %) | ||
| 841 | |||
| 842 | (% style="display:none" %) [[image:1657157402578-508.png||height="450" width="992"]] | ||
| 843 | |||
| 844 | (% id="cke_bm_589629S" style="display:none" %) [[image:image-20220707092040-2.png||height="452" width="1002"]] | ||
| 845 | |||
| 846 | [[image:image-20220826091725-5.png||height="479" width="1004"]] | ||
| 847 | |||
| 848 | |||
| 849 | ((( | ||
| 850 | Please see this document for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8N/Firmware/Application_Note/&file=Auto-update-feature.pdf>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Application_Note/&file=Auto-update-feature.pdf]] | ||
| 851 | ))) | ||
| 852 | |||
| 853 | (% style="display:none" %) (%%) | ||
| 854 | |||
| 855 | ((( | ||
| 856 | R-SSH is for remote access device and management, introduction for how to use: **[[Remote Access Gateway>>https://wiki.dragino.com/xwiki/bin/view/Main/Monitor%20%26%20Remote%20Access%20Gateway/#H3.A0RSSHIntroduction]]** | ||
| 857 | |||
| 858 | |||
| 859 | ))) | ||
| 860 | |||
| 861 | [[image:1652429624400-864.png||height="432" width="716"]] | ||
| 862 | |||
| 863 | |||
| 864 | === (% data-sider-select-id="48301489-7b19-464f-b442-96a6168a5e70" %)5.6.6 System ~-~-> Firmware Upgrade(%%) === | ||
| 865 | |||
| 866 | |||
| 867 | We keep improving the LPS8N Linux side firmware for new features and bug fixes. Below are the links for reference. | ||
| 868 | |||
| 869 | * **Latest firmware**: [[LoRa Gateway Firmware>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LG02-OLG02/Firmware/]], | ||
| 870 | |||
| 871 | ( [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8N/Firmware>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware]]) | ||
| 872 | |||
| 873 | * **Change Log**: [[Firmware Change Log>>url:http://www.dragino.com/downloads/downloads/LoRa_Gateway/LG02-OLG02/Firmware/ChangeLog]]. | ||
| 874 | |||
| 875 | ( [[http:~~/~~/www.dragino.com/downloads/downloads/LoRa_Gateway/LPS8N/Firmware/ChangeLog>>url:http://www.dragino.com/downloads/downloads/LoRa_Gateway/LIG16/Firmware/ChangeLog]] ) | ||
| 876 | |||
| 877 | |||
| 878 | ((( | ||
| 879 | The file named as (% style="color:green" %)**xxxxx–xxxxx-squashfs-sysupgrade.bin **(% style="color:black" %)is the upgrade Image. There are different methods to upgrade, as below. | ||
| 880 | ))) | ||
| 881 | |||
| 882 | ((( | ||
| 883 | (% style="color:green" %)**Web~-~-> System~-~-> Firmware Upgrade** | ||
| 884 | |||
| 885 | |||
| 886 | ))) | ||
| 887 | |||
| 888 | [[image:1657156052651-770.png]] | ||
| 889 | |||
| 890 | |||
| 891 | ((( | ||
| 892 | Select the required image and click (% style="color:blue" %)**Flash Image.**(%%) The image will be uploaded to the device, and then click (% style="color:blue" %)**Process Update**(%%) to upgrade. | ||
| 893 | ))) | ||
| 894 | |||
| 895 | |||
| 896 | ((( | ||
| 897 | (% style="color:red" %)**NOTE**: (%%)You normally need to (% style="color:blue" %)**//uncheck//**(%%) the (% style="color:blue" %)**Preserve Settings**(%%) checkbox when doing an upgrade to ensure that there is no conflict between the old settings and the new firmware. The new firmware will start up with its default settings. | ||
| 898 | |||
| 899 | |||
| 900 | ))) | ||
| 901 | |||
| 902 | ((( | ||
| 903 | The system will automatically boot into the new firmware after upgrade. | ||
| 904 | |||
| 905 | |||
| 906 | ))) | ||
| 907 | |||
| 908 | [[image:1657156094153-520.png]] | ||
| 909 | |||
| 910 | |||
| 911 | (% style="color:red" %)**NOTE***(%%): User can also upgrade firmware via Linux console | ||
| 912 | |||
| 913 | SCP the firmware to the system(% style="color:green" %)**/var**(%%)** **directory and then run | ||
| 914 | |||
| 915 | (% style="color:#4f81bd" %)**//root@OpenWrt:~~# /sbin/sysupgrade –n /var/Your_Image//** | ||
| 916 | |||
| 917 | |||
| 918 | (% style="color:red" %)**NOTE**(%%) : it is important to transfer the image in the /var directory, otherwise it may exceed the available flash size. | ||
| 919 | |||
| 920 | |||
| 921 | === (% data-sider-select-id="373b3cff-3336-4ea9-b2e3-80b269a25dbb" %)5.6.7 System ~-~-> Reboot/Reset(%%) === | ||
| 922 | |||
| 923 | |||
| 924 | [[image:1652430197132-330.png||height="256" width="724"]] | ||
| 925 | |||
| 926 | ((( | ||
| 927 | |||
| 928 | ))) | ||
| 929 | |||
| 930 | === (% data-sider-select-id="cc442f8d-4584-40ca-9073-38550c568e23" %)5.6.8 System ~-~-> Package Maintain(%%) === | ||
| 931 | |||
| 932 | |||
| 933 | [[image:1657156199070-491.png]] | ||
| 934 | |||
| 935 | |||
| 936 | Place to show what package has installed and possible to upgrade packages. | ||
| 937 | |||
| 938 | |||
| 939 | == (% data-sider-select-id="393c2ac7-980d-4a0c-b0da-cab40221782d" %)5.7 LogRead(%%) == | ||
| 940 | |||
| 941 | === (% data-sider-select-id="a1857d6d-7292-49a4-9c2b-821fdcd8435a" %)5.7.1 LogRead ~-~-> LoRa Log(%%) === | ||
| 942 | |||
| 943 | |||
| 944 | Show the frequency for LoRa Radio and traffics. | ||
| 945 | |||
| 946 | |||
| 947 | [[image:1657156300781-933.png]] | ||
| 948 | |||
| 949 | |||
| 950 | === (% data-sider-select-id="6e7c0405-1a69-41f7-a2d7-7c06ef64ecfe" %)5.7.2 LogRead ~-~-> Gateway Traffic(%%) === | ||
| 951 | |||
| 952 | Show the gateway traffic: | ||
| 953 | |||
| 954 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/DLOS8N/WebHome/image-20240416112159-1.png?width=872&height=610&rev=1.1||alt="image-20240416112159-1.png"]] | ||
| 955 | |||
| 956 | |||
| 957 | === (% data-sider-select-id="ce561240-23b4-4b3e-acc8-4a82ddba40f1" %)5.7.3 LogRead ~-~-> System Log(%%) === | ||
| 958 | |||
| 959 | |||
| 960 | Show the system log | ||
| 961 | |||
| 962 | |||
| 963 | [[image:1657156341198-226.png]] | ||
| 964 | |||
| 965 | |||
| 966 | === (% data-sider-select-id="c3f34a69-1c74-453c-a2b9-01ff619a05d2" %)5.7.4 LogRead ~-~-> Record Log(%%) === | ||
| 967 | |||
| 968 | This interface can record gateway logs: | ||
| 969 | |||
| 970 | For issue debug. User can **Start Log ~-~-> Wait for 10 minutes ~-~-> Stop Log** . Make sure this period include where issue happen. And then send the log to Dragino to debug. | ||
| 971 | |||
| 972 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/DLOS8N/WebHome/image-20240416112510-2.png?width=870&height=296&rev=1.1||alt="image-20240416112510-2.png"]] | ||
| 973 | |||
| 974 | = 6. More features = | ||
| 975 | |||
| 976 | |||
| 977 | == (% data-sider-select-id="2ef025e3-4214-4b1c-bb01-ee03e1db2bc2" %)6.1 NTP Service/Time Synchronization(%%) == | ||
| 978 | |||
| 979 | The gateway time sync service is provided by ntpd | ||
| 980 | |||
| 981 | === 1). Modify the NTP server address: === | ||
| 982 | |||
| 983 | (% class="box" %) | ||
| 984 | ((( | ||
| 985 | ~#~##Linux command | ||
| 986 | |||
| 987 | uci set system.ntp.server='0.openwrt.pool.ntp.org' #Required | ||
| 988 | |||
| 989 | uci add_list system.ntp.server='1.openwrt.pool.ntp.org' #Optional | ||
| 990 | |||
| 991 | uci add_list system.ntp.server='2.openwrt.pool.ntp.org' #Optional | ||
| 992 | |||
| 993 | uci add_list system.ntp.server='3.openwrt.pool.ntp.org' #Optional | ||
| 994 | |||
| 995 | uci commit system #Required | ||
| 996 | ))) | ||
| 997 | |||
| 998 | **Note: If the NTP server is a Windows host, it may cause the time synchronization to fail, ** | ||
| 999 | |||
| 1000 | |||
| 1001 | == (% data-sider-select-id="9ae226bc-051a-4d47-8a2f-13187e54c382" %)6.2 Packet Filtering(%%) == | ||
| 1002 | |||
| 1003 | |||
| 1004 | ((( | ||
| 1005 | Drop unwanted packets. | ||
| 1006 | ))) | ||
| 1007 | |||
| 1008 | ((( | ||
| 1009 | See: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Filter%20unwanted%20LoRaWAN%20packets/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Filter%20unwanted%20LoRaWAN%20packets/]] | ||
| 1010 | ))) | ||
| 1011 | |||
| 1012 | |||
| 1013 | == (% data-sider-select-id="b5a1b47f-bee3-4d68-961d-5c81b48ab3e4" %)6.3 Remote Access(%%) == | ||
| 1014 | |||
| 1015 | |||
| 1016 | ((( | ||
| 1017 | Remote Access Devices for management. | ||
| 1018 | ))) | ||
| 1019 | |||
| 1020 | ((( | ||
| 1021 | Instruction: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Monitor%20%26%20Remote%20Access%20Gateway/?Remote%20Access>>http://wiki.dragino.com/xwiki/bin/view/Main/Monitor%20%26%20Remote%20Access%20Gateway/?Remote%20Access]] | ||
| 1022 | ))) | ||
| 1023 | |||
| 1024 | |||
| 1025 | == (% data-sider-select-id="42a860ac-f871-40fc-8711-dd435b46239b" %)6.4 How to decode ABP LoRaWAN node(%%) == | ||
| 1026 | |||
| 1027 | |||
| 1028 | ((( | ||
| 1029 | Decode ABP: | ||
| 1030 | ))) | ||
| 1031 | |||
| 1032 | ((( | ||
| 1033 | [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Communicate%20with%20ABP%20End%20Node%20without%20LoRaWAN%20Network%20Server%20~~-~~--%20LG308/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Communicate%20with%20ABP%20End%20Node%20without%20LoRaWAN%20Network%20Server%20---%20LG308/]] | ||
| 1034 | ))) | ||
| 1035 | |||
| 1036 | |||
| 1037 | == (% data-sider-select-id="1e2d672a-9400-44cc-82db-3946bd1cc49e" %)6.5 How to set data to MQTT broker(%%) == | ||
| 1038 | |||
| 1039 | |||
| 1040 | ((( | ||
| 1041 | Only support ABP LoRaWAN End Node | ||
| 1042 | ))) | ||
| 1043 | |||
| 1044 | ((( | ||
| 1045 | Instruction: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/MQTT%20Forward%20Instruction/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/MQTT%20Forward%20Instruction/]] | ||
| 1046 | |||
| 1047 | |||
| 1048 | == (% data-sider-select-id="e5ea7147-f618-4c9a-b8f9-e108ee76b9da" %)6.6 How the gateway connects to Chirpstack v3/v4 via gateway-bridge(%%) == | ||
| 1049 | |||
| 1050 | |||
| 1051 | If the Chirpstack v3 Gateway-bridge is used, the corresponding gateway firmware must be used : | ||
| 1052 | |||
| 1053 | [[Chirpstack-gateway-bridge/Chirpstack-Bridge-V3.14.6-Bridge~~-~~-build-v5.4.1679487778-20230322-2024/>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/Chirpstack-Bridge-V3.14.6-Bridge--build-v5.4.1679487778-20230322-2024/]] | ||
| 1054 | |||
| 1055 | Chirpstack v3 via gateway-bridge Instruction: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H4.A0A0HowthegatewayconnectstoChirpstackv3viagateway-bridge>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H4.A0A0HowthegatewayconnectstoChirpstackv3viagateway-bridge]] | ||
| 1056 | |||
| 1057 | |||
| 1058 | If the Chirpstack v4 Gateway-bridge is used, the corresponding gateway firmware must be used : | ||
| 1059 | |||
| 1060 | [[Chirpstack-gateway-bridge/Chirpstack-Bridge-V4~~-~~-build-v5.4.1670655072-20221210-1452/>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/Chirpstack-Bridge-V4--build-v5.4.1670655072-20221210-1452/]] | ||
| 1061 | |||
| 1062 | Chirpstack v4 via gateway-bridge Instruction: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H4.A0HowthegatewayconnectstoChirpstackv4viagateway-bridge>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H4.A0HowthegatewayconnectstoChirpstackv4viagateway-bridge]] | ||
| 1063 | |||
| 1064 | |||
| 1065 | ))) | ||
| 1066 | |||
| 1067 | (% style="color:red" %)**Note**(%%): Different chirpstack versions use different gateway-bridge configurations. | ||
| 1068 | |||
| 1069 | After updating the Chirpstack gateway-bridge firmware, there is no need to re-download and install the Chirpstack gateway-bridge package | ||
| 1070 | |||
| 1071 | |||
| 1072 | (% data-sider-select-id="eb4b3bf2-9e33-4650-b4d6-1bc049896baa" %) | ||
| 1073 | == (% data-sider-select-id="e5ea7147-f618-4c9a-b8f9-e108ee76b9da" %)6.7 (% data-sider-select-id="1ae6690c-7910-44d5-999b-cd3b05be575f" %)How does the gateway connect to (% data-sider-select-id="e5ea7147-f618-4c9a-b8f9-e108ee76b9da" %)Chirpstack(% data-sider-select-id="1ae6690c-7910-44d5-999b-cd3b05be575f" %) via MQTT Forwarder(%%) == | ||
| 1074 | |||
| 1075 | |||
| 1076 | (% data-sider-select-id="33f2a7a8-cb1a-4c53-bd5b-716d3cc3d74f" %) | ||
| 1077 | 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. | ||
| 1078 | |||
| 1079 | |||
| 1080 | (% data-sider-select-id="73a14e4a-5128-4f13-8207-7837c412ff54" %) | ||
| 1081 | === 6.7.1 Configure Packet Forwarder === | ||
| 1082 | |||
| 1083 | |||
| 1084 | In the Dragino web-interface, you must configure the Packet Forwarder such that it forwards to localhost on port 1700. | ||
| 1085 | |||
| 1086 | (% data-sider-select-id="2972d256-3078-403f-9e33-3740a5869405" %) | ||
| 1087 | By default, the web-interface can be accessed by entering the following URL in your browser: (% data-sider-select-id="a9e64ab2-7a80-4174-b834-dba4904e3c85" %)**https:~/~/GATEWAY-IP-ADDRESS:8000**(%%) (replace GATEWAY-IP-ADDRESS by the actual IP address of your gateway). The default credentials are (% data-sider-select-id="16f9bbed-ffd7-4881-9cd1-33332f063857" %)**root / dragino**(%%). | ||
| 1088 | |||
| 1089 | * In the **LoRaWAN** menu, click **LoRaWAN ~-~- Semtech UDP** | ||
| 1090 | * Configure the following settings: | ||
| 1091 | ** **Service Provider:** //Custom / Private LoRaWAN// | ||
| 1092 | ** **Server Address:** //localhost// | ||
| 1093 | ** **Uplink Port:** //1700// | ||
| 1094 | ** **Downlink Port:** //1700// | ||
| 1095 | * Click **Save&Apply** | ||
| 1096 | |||
| 1097 | [[image:image-20240518114149-2.png||height="683" width="876"]] | ||
| 1098 | |||
| 1099 | |||
| 1100 | (% data-sider-select-id="7ada6cd9-b472-473e-b709-31db23947a9c" %) | ||
| 1101 | === 6.7.2 Install ChirpStack MQTT Forwarder === | ||
| 1102 | |||
| 1103 | |||
| 1104 | (% data-sider-select-id="cd761ad9-41f8-4cc3-8dc8-cf25ebe79e69" %) | ||
| 1105 | (% data-sider-select-id="74577a45-a26e-4ab8-b56c-2ba79220e6c6" %)**SSH login** | ||
| 1106 | |||
| 1107 | (% data-sider-select-id="f4b22a8a-3b87-4cc7-b4ed-451fdd8aa9a7" %) | ||
| 1108 | First user must login into the gateway using SSH,user can refer to the link to access the Linux console via SSH to the gateway: **[[SSH Access for Linux console>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/LPS8N%20-%20LoRaWAN%20Gateway%20User%20Manual/#H7.A0LinuxSystem||data-sider-select-id="27b6862a-68e4-4f69-a5b2-b33d8a06a09c"]]** | ||
| 1109 | |||
| 1110 | |||
| 1111 | (% data-sider-select-id="e9c9429f-f7c4-4eb3-b3f4-99553fe741b0" %) | ||
| 1112 | (% data-sider-select-id="83ee7071-3524-45ba-99b2-9f3472815cd8" %)**Download IPK** | ||
| 1113 | |||
| 1114 | Use the following commands to download the latest version of the chirpstack-mqtt-forwarder package: | ||
| 1115 | |||
| 1116 | (% class="box infomessage" data-sider-select-id="b970d0e5-64ca-47c8-8c9c-6261200a719f" %) | ||
| 1117 | ((( | ||
| 1118 | cd /tmp | ||
| 1119 | wget https:~/~/artifacts.chirpstack.io/downloads/chirpstack-mqtt-forwarder/vendor/dragino/mips_24kc/chirpstack-mqtt-forwarder_4.3.0-r1_mips_24kc.ipk | ||
| 1120 | ))) | ||
| 1121 | |||
| 1122 | |||
| 1123 | (% data-sider-select-id="27190188-ef2a-4d53-8b94-c4653b69b266" %) | ||
| 1124 | (% data-sider-select-id="3fe3ef50-33b9-4c6b-b228-7364e01382f3" %)**Install IPK** | ||
| 1125 | |||
| 1126 | Use the opkg package-manager to install the downloaded package. Example: | ||
| 1127 | |||
| 1128 | (% class="box infomessage" data-sider-select-id="86f1197c-5aaf-4a1b-a21f-09266a2805e7" %) | ||
| 1129 | ((( | ||
| 1130 | opkg install chirpstack-mqtt-forwarder_4.3.0-r1_mips_24kc.ipk | ||
| 1131 | ))) | ||
| 1132 | |||
| 1133 | [[image:image-20240518134824-5.png]] | ||
| 1134 | |||
| 1135 | |||
| 1136 | (% data-sider-select-id="e8065348-1a8e-45a9-bb73-171b9322d2b2" %) | ||
| 1137 | (% data-sider-select-id="e9401e38-e30d-4c39-94fa-927c9a40e151" %)**Configuration** | ||
| 1138 | |||
| 1139 | (% data-sider-select-id="2a70737e-070b-4a83-a474-2fef1076a006" %) | ||
| 1140 | To connect the ChirpStack MQTT Forwarder to your MQTT broker, you must update the ChirpStack MQTT Forwarder configuration file. | ||
| 1141 | |||
| 1142 | (% data-sider-select-id="be45c14f-1537-457e-9c9b-3fec22c024ac" %) | ||
| 1143 | This file is located at: (% data-sider-select-id="b010c8b8-6367-49bf-9c2e-3ee0b8a6ef0e" %)**/etc/chirpstack-mqtt-forwarder/chirpstack-mqtt-forwarder.toml** | ||
| 1144 | |||
| 1145 | |||
| 1146 | (% data-sider-select-id="be45c14f-1537-457e-9c9b-3fec22c024ac" %) | ||
| 1147 | (% data-sider-select-id="fab61fd5-2c9f-4b72-9b65-457dca26cbd0" %)**ChirpStack MQTT Forwarder Setting:** | ||
| 1148 | |||
| 1149 | (% class="box" data-sider-select-id="be45c14f-1537-457e-9c9b-3fec22c024ac" %) | ||
| 1150 | ((( | ||
| 1151 | topic_prefix ~-~-> This corresponds to the frequency of the ChirpStack server | ||
| 1152 | |||
| 1153 | server ~-~-> Fill in the ChirpStack server address, Example: tcp:~/~/10.130.2.15:1883 | ||
| 1154 | ))) | ||
| 1155 | |||
| 1156 | (% data-sider-select-id="be45c14f-1537-457e-9c9b-3fec22c024ac" %) | ||
| 1157 | username,password,ca_cert,tls_cert,tls_key parameters should be set as required. | ||
| 1158 | |||
| 1159 | |||
| 1160 | Use commands to modify configuration files: | ||
| 1161 | |||
| 1162 | (% class="box infomessage" data-sider-select-id="b84cf72d-69e4-441c-a8fb-bd21a500d223" %) | ||
| 1163 | ((( | ||
| 1164 | vim /etc/chirpstack-mqtt-forwarder/chirpstack-mqtt-forwarder.toml | ||
| 1165 | ))) | ||
| 1166 | |||
| 1167 | [[image:image-20240518141059-6.png]] | ||
| 1168 | |||
| 1169 | |||
| 1170 | (% data-sider-select-id="3312b6d5-334c-43ae-8cd9-2f73989940e2" %) | ||
| 1171 | (% data-sider-select-id="2b334f7c-35d3-4771-8b17-5760685430ac" %)**(Re)start and stop commands** | ||
| 1172 | |||
| 1173 | (% data-sider-select-id="b8175b05-70b1-4251-97a1-8c0b2644e4d4" %) | ||
| 1174 | Use the following commands to (re)start and stop the ChirpStack MQTT Forwarder service: | ||
| 1175 | |||
| 1176 | (% class="box infomessage" data-sider-select-id="fc0e9684-3620-4f52-8045-9f6b7dd083e3" %) | ||
| 1177 | ((( | ||
| 1178 | # start | ||
| 1179 | |||
| 1180 | (% data-sider-select-id="5a644c5c-1ca5-4680-877e-c6aecd21f9de" %) | ||
| 1181 | /etc/init.d/chirpstack-mqtt-forwarder start | ||
| 1182 | |||
| 1183 | # stop | ||
| 1184 | |||
| 1185 | /etc/init.d/chirpstack-mqtt-forwarder stop | ||
| 1186 | |||
| 1187 | # restart | ||
| 1188 | |||
| 1189 | /etc/init.d/chirpstack-mqtt-forwarder restart | ||
| 1190 | ))) | ||
| 1191 | |||
| 1192 | (% data-sider-select-id="bd72b54d-7316-46eb-8f1e-008a17aa6e9e" %) | ||
| 1193 | (% data-sider-select-id="fcef88f4-ef44-4459-9154-6cd154c5b298" %)**Check result** | ||
| 1194 | |||
| 1195 | (% data-sider-select-id="bd72b54d-7316-46eb-8f1e-008a17aa6e9e" %) | ||
| 1196 | Use "(% data-sider-select-id="494c67e8-3e62-45ee-8464-e2bb33057003" %)** **(%%)(% data-sider-select-id="494c67e8-3e62-45ee-8464-e2bb33057003" style="background-color:yellow" %)**logread -f **(%%)" to check the operation of ChirpStack MQTT Forwarder. | ||
| 1197 | |||
| 1198 | [[image:image-20240518142300-7.png]] | ||
| 1199 | |||
| 1200 | (% data-sider-select-id="a4ab5ddc-dbfe-4c41-ac6e-6159b517d02f" %) | ||
| 1201 | Go back to the Chirpstack server to check whether the gateway is (% data-sider-select-id="0689bd86-c7a8-4831-b064-d1c4ed6241e5" %)**"online"**(%%) and whether the packets are displayed normally. | ||
| 1202 | |||
| 1203 | [[image:image-20240518143050-8.png||height="702" width="1170"]] | ||
| 1204 | |||
| 1205 | |||
| 1206 | == (% data-sider-select-id="7800ac49-e340-4225-b076-fa02aeef43b6" %)6.8 How to extend the gateway size of memory with USB device (SD/TF card, USB flash drive).(%%) == | ||
| 1207 | |||
| 1208 | |||
| 1209 | USB card reader plugged into the USB port of the gateway | ||
| 1210 | |||
| 1211 | |||
| 1212 | Access the gateway Linux Command Line | ||
| 1213 | |||
| 1214 | |||
| 1215 | Check the USB device | ||
| 1216 | |||
| 1217 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/DLOS8N/WebHome/image-20230425165308-2.png?rev=1.1||alt="image-20230425165308-2.png" height="274" width="718"]] | ||
| 1218 | |||
| 1219 | |||
| 1220 | **Mount the USB device** | ||
| 1221 | |||
| 1222 | (% class="box infomessage" %) | ||
| 1223 | ((( | ||
| 1224 | **mount /dev/sda1 /mnt/** | ||
| 1225 | ))) | ||
| 1226 | |||
| 1227 | (% class="wikigeneratedid" %) | ||
| 1228 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/DLOS8N/WebHome/image-20230425174131-4.png?rev=1.1||alt="image-20230425174131-4.png"]] | ||
| 1229 | |||
| 1230 | |||
| 1231 | (% class="wikigeneratedid" %) | ||
| 1232 | **Set up the automatic mount on boot** | ||
| 1233 | |||
| 1234 | (% class="box infomessage" %) | ||
| 1235 | ((( | ||
| 1236 | **sed -i '3cmount \/dev\/sda1 \/mnt\/' /etc/rc.local ** | ||
| 1237 | ))) | ||
| 1238 | |||
| 1239 | (% class="wikigeneratedid" %) | ||
| 1240 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/DLOS8N/WebHome/image-20230425173831-3.png?width=833&height=105&rev=1.1||alt="image-20230425173831-3.png"]] | ||
| 1241 | |||
| 1242 | |||
| 1243 | == (% data-sider-select-id="549c1118-9953-4d63-b060-f29990a0efff" %)6.9 More instructions(%%) == | ||
| 1244 | |||
| 1245 | |||
| 1246 | [[LoRaWAN Gateway Instruction>>doc:Main.WebHome]](LoRaWAN Gateway) | ||
| 1247 | |||
| 1248 | |||
| 1249 | == (% data-sider-select-id="259fae0e-46c2-4483-8d6a-2025695cbb8e" %)6.10 Auto-Provision(%%) == | ||
| 1250 | |||
| 1251 | |||
| 1252 | Auto Provision is the feature for batch configure and remote management. It can be used in below two cases: | ||
| 1253 | |||
| 1254 | [[image:image-20220707092040-1.png||height="451" width="995"]] | ||
| 1255 | |||
| 1256 | [[image:image-20220707092040-2.png||height="452" width="1002"]] | ||
| 1257 | |||
| 1258 | [[image:image-20220826091546-4.png]](% style="display:none" %) | ||
| 1259 | |||
| 1260 | |||
| 1261 | ((( | ||
| 1262 | Please see this document for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8N/Firmware/Application_Note/&file=Auto-update-feature.pdf>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Application_Note/&file=Auto-update-feature.pdf]] | ||
| 1263 | ))) | ||
| 1264 | |||
| 1265 | (% style="display:none" %) (%%) | ||
| 1266 | |||
| 1267 | = 7. (% style="display:none" %) (%%)Linux System = | ||
| 1268 | |||
| 1269 | |||
| 1270 | The LPS8N is based on the OpenWrt Linux system. It is open source, and users are free to configure and modify the Linux settings. | ||
| 1271 | |||
| 1272 | (% style="display:none" %) (%%) | ||
| 1273 | |||
| 1274 | == (% data-sider-select-id="ea0a026a-c7f9-42a6-8a0c-4c805370b1dc" %)7.1 SSH Access for Linux console(%%) == | ||
| 1275 | |||
| 1276 | |||
| 1277 | User can access the Linux console via the SSH protocol. Make sure your PC and the LPS8N are connected to the same network, then use a SSH tool (such as [[putty>>url:http://www.chiark.greenend.org.uk/~~sgtatham/putty/download.html]] in Windows) to access it. | ||
| 1278 | |||
| 1279 | IP address: IP address of LPS8N | ||
| 1280 | |||
| 1281 | Port: 22 (via WiFi AP mode) or 2222 (via WAN Interface) | ||
| 1282 | |||
| 1283 | User Name: (% style="color:green" %)**root** | ||
| 1284 | |||
| 1285 | Password: (% style="color:green" %)**dragino** (% style="color:black" %)(default) | ||
| 1286 | |||
| 1287 | After logging in, you will be in the Linux console and can enter commands as shown below. | ||
| 1288 | |||
| 1289 | |||
| 1290 | [[image:1657158198733-338.png]] | ||
| 1291 | |||
| 1292 | |||
| 1293 | (% data-sider-select-id="d80817f0-5014-49db-a781-63e9c9f0527f" %) | ||
| 1294 | The “** (% style="background-color:yellow" %)logread -f(%%)**(% style="background-color:yellow" %)” (%%)command can be used to debug how system runs. | ||
| 1295 | |||
| 1296 | |||
| 1297 | [[image:1657158190234-805.png]] | ||
| 1298 | |||
| 1299 | |||
| 1300 | == 7.2 Edit and Transfer files == | ||
| 1301 | |||
| 1302 | |||
| 1303 | ((( | ||
| 1304 | The LPS8N supports the (% style="color:green" %)**SCP protocol** (% style="color:black" %)and has a built-in (% style="color:green" %)**SFTP server**. (% style="color:black" %)There are many ways to edit and transfer files using these protocols. | ||
| 1305 | ))) | ||
| 1306 | |||
| 1307 | ((( | ||
| 1308 | In Windows, one of the easiest methods is using the [[WinSCP>>url:https://winscp.net/eng/index.php]] utility. | ||
| 1309 | ))) | ||
| 1310 | |||
| 1311 | ((( | ||
| 1312 | After establishing access via WinSCP to the device, you can use an FTP style window to drag / drop files to the LPS8N, or edit the files directly in the windows. | ||
| 1313 | ))) | ||
| 1314 | |||
| 1315 | ((( | ||
| 1316 | Screenshot is as below: | ||
| 1317 | ))) | ||
| 1318 | |||
| 1319 | [[image:1652431650755-450.png]] | ||
| 1320 | |||
| 1321 | |||
| 1322 | == 7.3 File System == | ||
| 1323 | |||
| 1324 | |||
| 1325 | ((( | ||
| 1326 | The LPS8N has a 16MB flash and a 64MB RAM. The /var and /tmp directories are in the RAM, so contents stored in /tmp and /var will be erased after rebooting the device. Other directories are in the flash and will remain after reboot. | ||
| 1327 | ))) | ||
| 1328 | |||
| 1329 | ((( | ||
| 1330 | The Linux system uses around 8MB ~~10MB flash size which means there is not much room for user to store data in the LPS8N flash. | ||
| 1331 | ))) | ||
| 1332 | |||
| 1333 | ((( | ||
| 1334 | You can use an external USB flash memory device to extend the size of flash memory for storage. | ||
| 1335 | ))) | ||
| 1336 | |||
| 1337 | |||
| 1338 | == 7.4 Package maintenance system == | ||
| 1339 | |||
| 1340 | |||
| 1341 | LPS8N uses the OpenWrt [[**OPKG package maintenance system**>>https://oldwiki.archive.openwrt.org/doc/techref/opkg]]. There are more than 3000+ packages available in our package server for users to install for their applications. For example, if you want to add the **//iperf //** tool, you can install the related packages and configure LPS8N to use **//iperf //**. | ||
| 1342 | |||
| 1343 | ((( | ||
| 1344 | Below are some example **//opkg //** commands. For more information please refer to the [[OPKG package maintain system>>https://oldwiki.archive.openwrt.org/doc/techref/opkg]]** **([[https:~~/~~/oldwiki.archive.openwrt.org/doc/techref/opkg>>https://oldwiki.archive.openwrt.org/doc/techref/opkg]]) | ||
| 1345 | ))) | ||
| 1346 | |||
| 1347 | ((( | ||
| 1348 | **In Linux Console run:** | ||
| 1349 | ))) | ||
| 1350 | |||
| 1351 | ((( | ||
| 1352 | (% style="color:green" %)**root@dragino-169d30:~~# opkg update** (% style="color:black" %)~/~/ to get the latest packages list | ||
| 1353 | ))) | ||
| 1354 | |||
| 1355 | ((( | ||
| 1356 | (% style="color:green" %)**root@dragino-169d30:~~# opkg list** (% style="color:black" %) ~/~/shows the available packages | ||
| 1357 | ))) | ||
| 1358 | |||
| 1359 | ((( | ||
| 1360 | (% style="color:green" %)**root@dragino-169d30:~~# opkg install iperf ** (% style="color:black" %)~/~/ install iperf | ||
| 1361 | ))) | ||
| 1362 | |||
| 1363 | The system will automatically install the required packages as shown below. | ||
| 1364 | |||
| 1365 | |||
| 1366 | ((( | ||
| 1367 | (% style="background-color:#dcdcdc" %)//root@dragino-169d30:/etc/opkg# opkg install iperf// | ||
| 1368 | ))) | ||
| 1369 | |||
| 1370 | ((( | ||
| 1371 | (% style="background-color:#dcdcdc" %)//Installing iperf (2.0.12-1) to root…// | ||
| 1372 | ))) | ||
| 1373 | |||
| 1374 | ((( | ||
| 1375 | (% style="background-color:#dcdcdc" %)//Downloading //[[(% style="background-color: rgb(220, 220, 220); background-color: rgb(220, 220, 220)" %)//http:~~/~~/downloads.openwrt.org/snapshots/packages/mips_24kc/base/iperf_2.0.12-1_mips_24kc.ipk//>>url:http://downloads.openwrt.org/snapshots/packages/mips_24kc/base/iperf_2.0.12-1_mips_24kc.ipk]] | ||
| 1376 | ))) | ||
| 1377 | |||
| 1378 | ((( | ||
| 1379 | (% style="background-color:#dcdcdc" %)//Installing uclibcxx (0.2.4-3) to root…// | ||
| 1380 | ))) | ||
| 1381 | |||
| 1382 | ((( | ||
| 1383 | (% style="background-color:#dcdcdc" %)//Downloading //[[(% style="background-color: rgb(220, 220, 220); background-color: rgb(220, 220, 220)" %)//http:~~/~~/downloads.openwrt.org/snapshots/packages/mips_24kc/base/uclibcxx_0.2.4-3_mips_24kc.ipk//>>url:http://downloads.openwrt.org/snapshots/packages/mips_24kc/base/uclibcxx_0.2.4-3_mips_24kc.ipk]] | ||
| 1384 | ))) | ||
| 1385 | |||
| 1386 | ((( | ||
| 1387 | (% style="background-color:#dcdcdc" %)//Configuring uclibcxx.// | ||
| 1388 | ))) | ||
| 1389 | |||
| 1390 | ((( | ||
| 1391 | (% style="background-color:#dcdcdc" %)//Configuring iperf.// | ||
| 1392 | |||
| 1393 | |||
| 1394 | ))) | ||
| 1395 | |||
| 1396 | = 8. Upgrade Linux Firmware = | ||
| 1397 | |||
| 1398 | |||
| 1399 | We keep improving the LPS8N Linux side firmware for new features and bug fixes. Below are the links for reference. | ||
| 1400 | |||
| 1401 | * **Latest firmware**: [[LoRa Gateway Firmware>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LG02-OLG02/Firmware/]], | ||
| 1402 | |||
| 1403 | ( [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8N/Firmware>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware]]) | ||
| 1404 | |||
| 1405 | * **Change Log**: [[Firmware Change Log>>url:http://www.dragino.com/downloads/downloads/LoRa_Gateway/LG02-OLG02/Firmware/ChangeLog]]. | ||
| 1406 | |||
| 1407 | ( [[http:~~/~~/www.dragino.com/downloads/downloads/LoRa_Gateway/LPS8N/Firmware/ChangeLog>>url:http://www.dragino.com/downloads/downloads/LoRa_Gateway/LIG16/Firmware/ChangeLog]] ) | ||
| 1408 | |||
| 1409 | |||
| 1410 | ((( | ||
| 1411 | The file named as (% style="color:green" %)** xxxxx–xxxxx-squashfs-sysupgrade.bin **(%%)is the upgrade Image. There are different methods to upgrade, as below. | ||
| 1412 | ))) | ||
| 1413 | |||
| 1414 | |||
| 1415 | == 8.1 Upgrade via Web UI == | ||
| 1416 | |||
| 1417 | |||
| 1418 | ((( | ||
| 1419 | Go to the page: (% style="color:green" %)**Web ~-~-> System ~-~-> Firmware Upgrade** | ||
| 1420 | ))) | ||
| 1421 | |||
| 1422 | ((( | ||
| 1423 | Select the required image and click (% style="color:red" %)**Flash Image.**(%%) The image will be uploaded to the device, and then click (% style="color:red" %)**Process Update**(%%) to upgrade. | ||
| 1424 | ))) | ||
| 1425 | |||
| 1426 | |||
| 1427 | ((( | ||
| 1428 | (% style="color:red" %)**NOTE**(%%): You normally need to (% style="color:blue" %)**//uncheck//**(%%) the (% style="color:blue" %)//**Preserve Settings**//(%%) checkbox when doing an upgrade to ensure that there is no conflict between the old settings and the new firmware. The new firmware will start up with its default settings. | ||
| 1429 | ))) | ||
| 1430 | |||
| 1431 | |||
| 1432 | ((( | ||
| 1433 | The system will automatically boot into the new firmware after upgrade. | ||
| 1434 | |||
| 1435 | |||
| 1436 | ))) | ||
| 1437 | |||
| 1438 | [[image:1657158986600-386.png]] | ||
| 1439 | |||
| 1440 | |||
| 1441 | == 8.2 Upgrade via Linux console == | ||
| 1442 | |||
| 1443 | |||
| 1444 | ((( | ||
| 1445 | SCP the firmware to the system** (% style="color:green" %)/var(%%)** directory and then run | ||
| 1446 | ))) | ||
| 1447 | |||
| 1448 | ((( | ||
| 1449 | (% style="color:#4472c4" %)** //root@OpenWrt:~~# /sbin/sysupgrade –n /var/Your_Image//** | ||
| 1450 | ))) | ||
| 1451 | |||
| 1452 | |||
| 1453 | ((( | ||
| 1454 | (% style="color:red" %)**NOTE**(%%): it is important to transfer the image in the /var directory, otherwise it may exceed the available flash size. | ||
| 1455 | ))) | ||
| 1456 | |||
| 1457 | |||
| 1458 | = 9. OTA System Update = | ||
| 1459 | |||
| 1460 | |||
| 1461 | LPS8N 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. | ||
| 1462 | |||
| 1463 | |||
| 1464 | = 10. FAQ = | ||
| 1465 | |||
| 1466 | == 10.1 How can I configure for a customized frequency band? == | ||
| 1467 | |||
| 1468 | |||
| 1469 | ((( | ||
| 1470 | See below link for how to customize frequency band: [[How to customized LoRaWAN frequency band>>doc:Main.How to customized LoRaWAN frequency band.WebHome]] | ||
| 1471 | ))) | ||
| 1472 | |||
| 1473 | ((( | ||
| 1474 | |||
| 1475 | ))) | ||
| 1476 | |||
| 1477 | == 10.2 Can I make my own firmware for the gateway, where can I find the source code? == | ||
| 1478 | |||
| 1479 | |||
| 1480 | ((( | ||
| 1481 | Yes, You can make your own firmware for the LPS8N for branding purposes or to add customized applications. | ||
| 1482 | ))) | ||
| 1483 | |||
| 1484 | ((( | ||
| 1485 | The source code and compile instructions can be found at: [[https:~~/~~/github.com/dragino/openwrt_lede-18.06>>url:https://github.com/dragino/openwrt_lede-18.06]] | ||
| 1486 | ))) | ||
| 1487 | |||
| 1488 | ((( | ||
| 1489 | |||
| 1490 | ))) | ||
| 1491 | |||
| 1492 | == 10.3 Can I use 868Mhz version for 915Mhz bands? == | ||
| 1493 | |||
| 1494 | |||
| 1495 | It is possible but the distance will be very short, you can select US915 frequency band in 868Mhz version hardware. It will work but you will see the performance is greatly decreased because the 868Mhz version has an RF filter for band 863~~870Mhz, all other frequencies will have high attenuation. | ||
| 1496 | |||
| 1497 | |||
| 1498 | == (% data-sider-select-id="59a03633-54e9-489e-a7d2-d0a332359cee" %)10.4 DIN Rail Mounting Reference.(%%) == | ||
| 1499 | |||
| 1500 | |||
| 1501 | [[image:image-20240318095136-1.jpeg||height="785" width="785"]] | ||
| 1502 | |||
| 1503 | [[image:image-20240318095410-2.png||height="179" width="402"]] | ||
| 1504 | |||
| 1505 | |||
| 1506 | |||
| 1507 | = 11. Trouble Shooting = | ||
| 1508 | |||
| 1509 | == 11.1 I get kernel error when install new package, how to fix? == | ||
| 1510 | |||
| 1511 | |||
| 1512 | In some cases, when installing a package with **//opkg//**, it will generate a kernel error such as below due to a mismatch I the kernel ID: | ||
| 1513 | |||
| 1514 | (% style="background-color:yellow" %)root@dragino-16c538:~~# opkg install kmod-dragino2-si3217x_3.10.49+0.2-1_ar71xx.ipk | ||
| 1515 | |||
| 1516 | (% style="background-color:yellow" %)Installing kmod-dragino2-si3217x (3.10.49+0.2-1) to root… | ||
| 1517 | |||
| 1518 | (% style="background-color:yellow" %)Collected errors: | ||
| 1519 | |||
| 1520 | (% style="background-color:yellow" %)* satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-dragino2-si3217x: | ||
| 1521 | |||
| 1522 | (% style="background-color:yellow" %)* kernel (= 3.10.49-1-4917516478a753314254643facdf360a) * | ||
| 1523 | |||
| 1524 | (% style="background-color:yellow" %)* opkg_install_cmd: Cannot install package kmod-dragino2-si3217x. | ||
| 1525 | |||
| 1526 | ((( | ||
| 1527 | In this case, you can use the –force-depends option to install such package as long as the actual kernel version is the same. | ||
| 1528 | ))) | ||
| 1529 | |||
| 1530 | (% style="background-color:yellow" %)Opkg install kmod-dragino2-si3217x_3.10.49+0.2-1_ar71xx.ipk –force-depends | ||
| 1531 | |||
| 1532 | |||
| 1533 | == 11.2 How to recover the LPS8N if the firmware crashes == | ||
| 1534 | |||
| 1535 | |||
| 1536 | ((( | ||
| 1537 | Please follow this instruction to recover your gateway: [[Recover Gateway>>doc:Main.How to Recover Gateway if can't access it.WebHome]] | ||
| 1538 | ))) | ||
| 1539 | |||
| 1540 | ((( | ||
| 1541 | |||
| 1542 | ))) | ||
| 1543 | |||
| 1544 | == 11.3 I configured LPS8N for WiFi access and lost its IP. What to do now? == | ||
| 1545 | |||
| 1546 | |||
| 1547 | [[image:image-20231116112906-1.png]] | ||
| 1548 | |||
| 1549 | |||
| 1550 | ((( | ||
| 1551 | The LPS8N has a fall-back IP address on its WAN port. This IP is always enabled so you can use the fall-back IP to access LPS8N no matter what the WiFi IP is. The fall back IP is useful for connecting and debug the unit. | ||
| 1552 | ))) | ||
| 1553 | |||
| 1554 | (% style="color:red" %)**Note: fallback IP can be disabled in the WAN and DHCP page.** | ||
| 1555 | |||
| 1556 | |||
| 1557 | **Steps to connect via fall back IP:** | ||
| 1558 | |||
| 1559 | ~1. Connect PC's Ethernet port to LPS8N's WAN port | ||
| 1560 | |||
| 1561 | 2. Configure PC's Ethernet port has | ||
| 1562 | IP: 172.31.255.253 and | ||
| 1563 | Netmask: 255.255.255.252 | ||
| 1564 | |||
| 1565 | |||
| 1566 | As below photo: | ||
| 1567 | |||
| 1568 | [[image:1652435256286-879.png]] | ||
| 1569 | |||
| 1570 | |||
| 1571 | 3. In the PC, use IP address 172.31.255.254 to access the LPS8N via Web or Console. | ||
| 1572 | |||
| 1573 | Please note the latest firmware uses port 8000 for http and 2222 for ssh access. | ||
| 1574 | |||
| 1575 | |||
| 1576 | == 11.4 I connect to the LPS8N's SSID but LPS8N didn't assign DHCP IP to my laptop? == | ||
| 1577 | |||
| 1578 | |||
| 1579 | ((( | ||
| 1580 | This is a known bug for the firmware version before 2019-09-23 for LPS, the issue was fixed since version: LG02_LG08~-~-build-v5.2.1569218466-20190923-1402. | ||
| 1581 | ))) | ||
| 1582 | |||
| 1583 | ((( | ||
| 1584 | In the old version, user can use the [[fall back ip method >>||anchor="H10.3A0IconfiguredLPS8NforWiFiaccessandlostitsIP.Whattodonow3F"]]to access and configure the device. | ||
| 1585 | |||
| 1586 | |||
| 1587 | == 11.5 When i power on LPS8N , i can only see PWR LED is on. other LEDs are not blinking. == | ||
| 1588 | |||
| 1589 | If there is no LED blink except the PWR led. There might be: | ||
| 1590 | |||
| 1591 | 1) Power adapter issue. In this case, please try another power adapter. | ||
| 1592 | |||
| 1593 | 2) Mother Board broken. | ||
| 1594 | ))) | ||
| 1595 | |||
| 1596 | |||
| 1597 | (% data-sider-select-id="496725ea-6ec4-436c-82d7-547b7e14d448" %) | ||
| 1598 | == (% data-sider-select-id="59a03633-54e9-489e-a7d2-d0a332359cee" %)11.6 (%%)Why does the gateway reboot every 15 minutes without Internet? == | ||
| 1599 | |||
| 1600 | |||
| 1601 | (% data-sider-select-id="4b74d469-5382-4aed-969a-48abd1fe271b" %) | ||
| 1602 | Check whether Internet Detect is enabled on the System~-~->General interface. | ||
| 1603 | |||
| 1604 | (% data-sider-select-id="2140bc4a-c71f-4387-845a-510c0b050940" %) | ||
| 1605 | Internet Detect is enabled by default. When there is no gateway network, it will reboot after 15 minutes. | ||
| 1606 | |||
| 1607 | [[image:image-20240419145139-6.png||height="639" width="856"]] | ||
| 1608 | |||
| 1609 | |||
| 1610 | = 12. Order Info = | ||
| 1611 | |||
| 1612 | |||
| 1613 | **PART: (% style="color:blue" %)LPS8N-XXX-YYY: (%%)** | ||
| 1614 | |||
| 1615 | (% style="color:blue" %) **XXX:**(%%)** Frequency Band** | ||
| 1616 | |||
| 1617 | * (% style="color:red" %)** 868**(% style="color:black" %) : valid frequency: 863Mhz ~~ 870Mhz. for bands EU868, RU864, IN865 or KZ865. | ||
| 1618 | * (% style="color:red" %)** 915**(% style="color:black" %): valid frequency: 902Mhz ~~ 928Mhz. for bands US915, AU915, AS923 or KR920 | ||
| 1619 | |||
| 1620 | (% style="color:blue" %) **YYY:**(%%)** 4G Cellular Option** | ||
| 1621 | |||
| 1622 | * (% style="color:red" %)**EC25-E**(% style="color:black" %): EMEA, Korea, Thailand, India. | ||
| 1623 | * (% style="color:red" %)**EC25-AFX**(% style="color:black" %): America:Verizon, AT&T(FirstNet), U.S.Cellular; Canada:Telus | ||
| 1624 | * (% style="color:red" %)**EC25-AUX**(% style="color:black" %): Latin America, New Zeland, Taiwan | ||
| 1625 | * (% style="color:red" %)**EC25-J**(% style="color:black" %): Japan, DOCOMO, SoftBank, KDDI | ||
| 1626 | |||
| 1627 | More info about valid bands, please see [[EC25-E product page>>url:https://www.quectel.com/product/ec25.htm]]. | ||
| 1628 | |||
| 1629 | |||
| 1630 | = 13. Packing Info = | ||
| 1631 | |||
| 1632 | |||
| 1633 | ((( | ||
| 1634 | **Package Includes**: | ||
| 1635 | ))) | ||
| 1636 | |||
| 1637 | * LPS8N LoRaWAN Gateway x 1 | ||
| 1638 | * Stick Antenna for LoRa RF part. Frequency is one of 470 or 868 or 915Mhz depends the model ordered | ||
| 1639 | * Packaging with environmental protection paper box | ||
| 1640 | |||
| 1641 | ((( | ||
| 1642 | **Dimension and weight**: | ||
| 1643 | ))) | ||
| 1644 | |||
| 1645 | * Device Size: 12 x 12 x 3 cm | ||
| 1646 | * Weight: 187g | ||
| 1647 | * Package Size: 14.5 x 13.5 x 6 cm | ||
| 1648 | * Weight: 300g | ||
| 1649 | |||
| 1650 | = 14. Support = | ||
| 1651 | |||
| 1652 | |||
| 1653 | * Try to see if your questions already answered in the [[wiki>>doc:Main.WebHome]]. | ||
| 1654 | * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. | ||
| 1655 | Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before mentioned schedule. | ||
| 1656 | * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to:[[support@dragino.com>>url:file:///C:/Users/11315/Documents/D:/Projects/LoRa%20Product%20Line/LG308%20Picocell%20Gateway/LG308/LG308%20%25E8%25AF%25B4%25E6%2598%258E%25E4%25B9%25A6/support@dragino.com]] | ||
| 1657 | |||
| 1658 |