Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 | (% style="text-align:center" %) | ||
| 4 | [[image:1652409757234-446.png||height="399" width="399"]] | ||
| 5 | |||
| 6 | |||
| 7 | |||
| 8 | **DLOS8N Outdoor LoRaWAN Gateway User Manual** | ||
| 9 | |||
| 10 | |||
| 11 | **Table of Contents：** | ||
| 12 | |||
| 13 | {{toc/}} | ||
| 14 | |||
| 15 | |||
| 16 | |||
| 17 | |||
| 18 | = 1. Introduction = | ||
| 19 | |||
| 20 | == 1.1 What is the DLOS8N == | ||
| 21 | |||
| 22 | ((( | ||
| 23 | The DLOS8N is an (% style="color:#4f81bd" %)open source outdoor LoRaWAN Gateway. (% style="color:black" %)It lets you bridge LoRa wireless network to an IP network via WiFi, Ethernet, 3G or 4G cellular. The LoRa wireless allows users to send data and reach extremely long ranges at low data-rates. | ||
| 24 | ))) | ||
| 25 | |||
| 26 | ((( | ||
| 27 | DLOS8N supports (% style="color:#4f81bd" %)Semtech packet forwarder (% style="color:black" %)and (% style="color:#4f81bd" %)LoRaWAN Station connection, (% style="color:black" %)it is fully compatible with LoRaWAN protocol. DLOS8N includes a (% style="color:#4f81bd" %)SX1302 LoRaWAN concentrator. | ||
| 28 | ))) | ||
| 29 | |||
| 30 | ((( | ||
| 31 | DLOS8N has (% style="color:#4f81bd" %)pre-configured standard LoRaWAN frequency bands (% style="color:black" %)to use for different countries.User can also customize the frequency bands to use in their own LoRaWAN network. | ||
| 32 | ))) | ||
| 33 | |||
| 34 | ((( | ||
| 35 | DLOS8N 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. | ||
| 36 | ))) | ||
| 37 | |||
| 38 | ((( | ||
| 39 | DLOS8N supports (% style="color:#4f81bd" %) auto-provision (% style="color:black" %) for mass deployment and long term maintain. System intergrator can easily change the settings. | ||
| 40 | ))) | ||
| 41 | |||
| 42 | [[image:1652411526195-923.png]] | ||
| 43 | |||
| 44 | |||
| 45 | == 1.2 Specifications == | ||
| 46 | |||
| 47 | **Hardware System:** | ||
| 48 | |||
| 49 | Linux Part: | ||
| 50 | |||
| 51 | * 400Mhz ar9331 processor | ||
| 52 | * 64MB RAM | ||
| 53 | * 16MB Flash | ||
| 54 | |||
| 55 | **Interface:** | ||
| 56 | |||
| 57 | * 10M/100M RJ45 Ports x 1 | ||
| 58 | * WiFi : 802.11 b/g/n | ||
| 59 | * LoRaWAN Wireless | ||
| 60 | * Power Input: 12 ~~ 24 V DC, 2 A | ||
| 61 | * IEEE 802.3 af compliant PoE port (DC 37 ~~ 57 v) | ||
| 62 | * USB 2.0 host connector x 1 | ||
| 63 | * Mini-PCI E connector x 1 | ||
| 64 | * SX1302 + 2 x SX1250 | ||
| 65 | |||
| 66 | **WiFi Spec:** | ||
| 67 | |||
| 68 | * IEEE 802.11 b/g/n | ||
| 69 | * Frequency Band: 2.4 ~~ 2.462GHz | ||
| 70 | * Tx power: | ||
| 71 | ** 11n tx power : mcs7/15: 11db mcs0 : 17db | ||
| 72 | ** 11b tx power: 18db | ||
| 73 | ** 11g 54M tx power: 12db | ||
| 74 | ** 11g 6M tx power: 18db | ||
| 75 | * Wifi Sensitivity | ||
| 76 | ** 11g 54M : -71dbm | ||
| 77 | ** 11n 20M : -67dbm | ||
| 78 | |||
| 79 | **LoRa Spec:** | ||
| 80 | |||
| 81 | * Up to -140 dBm sensitivity with SX1250 Tx/Rx front-end | ||
| 82 | * 70 dB CW interferer rejection at 1 MHz offset | ||
| 83 | * Able to operate with negative SNR, CCR up to 9dB | ||
| 84 | * Emulates 49 x LoRa demodulators and 1 x (G)FSK demodulator | ||
| 85 | * Dual digital TX & RX radio front-end interfaces | ||
| 86 | * 10 programmable parallel demodulation paths | ||
| 87 | * Dynamic data-rate (DDR) adaptation | ||
| 88 | * True antenna diversity or simultaneous dual-band operation | ||
| 89 | |||
| 90 | **Cellular 4G LTE (optional):** | ||
| 91 | |||
| 92 | * Quectel: [[**EC25 LTE module**>>url:https://www.quectel.com/product/ec25minipcie.htm]] | ||
| 93 | * Standard Size SIM Slot | ||
| 94 | * 2 x 4G Sticker Antenna. | ||
| 95 | * Up to 150Mbps downlink and 50Mbps uplink data rates | ||
| 96 | * Worldwide LTE,UMTS/HSPA+ and GSM/GPRS/EDGE coverage | ||
| 97 | * MIMO technology meets demands for data rate and link reliability in modem wireless communication systems | ||
| 98 | |||
| 99 | **Power over Ethernet:** | ||
| 100 | |||
| 101 | * IEEE 802.3af compliant. | ||
| 102 | * Support wide input voltage range 37Vdc to 57Vdc. | ||
| 103 | * Thermal cut off. | ||
| 104 | * Short circuit protection. | ||
| 105 | * Over current protection | ||
| 106 | * Isolation level 4 KVrms. | ||
| 107 | * Enhanced surge protection | ||
| 108 | |||
| 109 | == 1.3 Features == | ||
| 110 | |||
| 111 | * Open Source Embedded Linux system | ||
| 112 | * Managed by Web GUI, SSH via LAN or WiFi | ||
| 113 | * Support Semtech UDP packet forwarder | ||
| 114 | * Support LoRaWAN Station Connection | ||
| 115 | * Cellular Failover conntection(option) | ||
| 116 | * Direct Communication to LoRaWAN ABP Node | ||
| 117 | * LoRaWAN packet filtering | ||
| 118 | * Far seeing LED indicator | ||
| 119 | * Built-in GPS module for location & timing | ||
| 120 | * External fiber glass antenna | ||
| 121 | * Auto-Provision | ||
| 122 | * Remote Monitoring | ||
| 123 | * 802.3af PoE | ||
| 124 | * IP65 | ||
| 125 | * Lighting Protection | ||
| 126 | * Power Consumption:12v ,300-500mA | ||
| 127 | |||
| 128 | == 1.4 Hardware System Structure == | ||
| 129 | |||
| 130 | [[image:1652411641871-482.png||height="425" width="732"]] | ||
| 131 | |||
| 132 | |||
| 133 | == 1.5 DLOS8N Applications == | ||
| 134 | |||
| 135 | [[image:1652411671209-920.png||height="618" width="650"]] | ||
| 136 | |||
| 137 | |||
| 138 | == 1.6 LED Indicators == | ||
| 139 | |||
| 140 | [[image:1652411720670-489.png]] | ||
| 141 | |||
| 142 | |||
| 143 | There is a waterproof triple color LED on DLOS8N enclosure, the meaning of the LED is: | ||
| 144 | |||
| 145 | ((( | ||
| 146 | ((( | ||
| 147 | * ((( | ||
| 148 | (% style="color:green" %)**SOLID GREEN**: (% style="color:black" %)DLOS8N is alive with LoRaWAN server connection. | ||
| 149 | ))) | ||
| 150 | ))) | ||
| 151 | |||
| 152 | * ((( | ||
| 153 | (% style="color:green" %)**BLINKING GREEN**:(% style="color:black" %) a) Device has internet connection but no LoRaWAN Connection. or b) Device is in booting stage, in this stage, it will (% style="color:green" %)**BLINKING GREEN**(% style="color:black" %) for several seconds and then (% style="color:red" %)**RED** (% style="color:black" %)and (% style="color:#ffc000" %)**YELLOW** (% style="color:black" %)will blink together. | ||
| 154 | ))) | ||
| 155 | * ((( | ||
| 156 | (% style="color:red" %)**SOLID RED**: (% style="color:black" %)Device doesn’t have Internet connection. | ||
| 157 | ))) | ||
| 158 | ))) | ||
| 159 | |||
| 160 | |||
| 161 | == 1.7 WiFi Direction == | ||
| 162 | |||
| 163 | DLOS8N use directional WiFi Antenna. The best direction is as below: | ||
| 164 | |||
| 165 | [[image:1652412859663-161.png||height="341" width="333"]] | ||
| 166 | |||
| 167 | |||
| 168 | = 2. Access and Configure DLOS8N = | ||
| 169 | |||
| 170 | The DLOS8N is configured as a WiFi Access Point by default. User can access and configure the DLOS8N after connecting to its WiFi network, or via its Ethernet port. | ||
| 171 | |||
| 172 | == 2.1 Find IP address of DLOS8N == | ||
| 173 | |||
| 174 | === 2.1.1 Connect via WiFi === | ||
| 175 | |||
| 176 | [[image:1652412985720-934.png]] | ||
| 177 | |||
| 178 | |||
| 179 | At the first boot of DLOS8N, it will auto generate a WiFi network called (% style="color:green" %)**//dragino-xxxxxx //**(% style="color:black" %)with password: | ||
| 180 | |||
| 181 | [[image:1652413127647-377.png]] | ||
| 182 | |||
| 183 | (% style="background-color:#ffffcc" %)dragino+dragino | ||
| 184 | |||
| 185 | User can use a PC to connect to this WiFi network. The PC will get an IP address 10.130.1.xxx and the DLOS8N has the default IP (% style="color:green" %)10.130.1.1 | ||
| 186 | |||
| 187 | |||
| 188 | === 2.1.2 Connect via Ethernet with DHCP IP from router === | ||
| 189 | |||
| 190 | [[image:1652414114583-532.png]] | ||
| 191 | |||
| 192 | |||
| 193 | Alternatively, connect the DLOS8N Ethernet port to your router and DLOS8N 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 DLOS8N. You can also use this IP to connect. | ||
| 194 | |||
| 195 | |||
| 196 | === 2.1.3 Connect via WiFi with DHCP IP from router === | ||
| 197 | |||
| 198 | [[image:1652414137639-956.png]] | ||
| 199 | |||
| 200 | |||
| 201 | If the DLOS8N already connect to the router via WiFi, use can use the WiFi IP to connect to DLOS8N. | ||
| 202 | |||
| 203 | |||
| 204 | === 2.1.4 Connect via Ethernet with fall back ip === | ||
| 205 | |||
| 206 | The WAN port also has a [[fall back ip address>>path:#_I_configured_LPS8]] for access if user doesn’t connect to uplink router. Click [[here>>path:#_I_configured_LPS8]] to see how to configure. | ||
| 207 | |||
| 208 | |||
| 209 | == 2.2 Access Configure Web UI == | ||
| 210 | |||
| 211 | **Web Interface** | ||
| 212 | |||
| 213 | Open a browser on the PC and type the DLOS8N ip address (depends on your connect method) | ||
| 214 | |||
| 215 | [[http:~~/~~/10.130.1.1/>>url:http://10.130.1.1/]] (Access via WiFi AP network) | ||
| 216 | |||
| 217 | or | ||
| 218 | |||
| 219 | http:~/~/IP_ADDRESS or [[http:~~/~~/ IP_ADDRESS:8000>>url:http://192.168.1.xx:8000]] | ||
| 220 | |||
| 221 | |||
| 222 | You will see the login interface of DLOS8N as shown below. | ||
| 223 | |||
| 224 | The account details for Web Login are: | ||
| 225 | |||
| 226 | (% style="color:#4f81bd" %)**User Name: root** | ||
| 227 | |||
| 228 | (% style="color:#4f81bd" %)**Password: dragino** | ||
| 229 | |||
| 230 | [[image:1652414287022-223.png]] | ||
| 231 | |||
| 232 | |||
| 233 | |||
| 234 | |||
| 235 | = 3. Typical Network Setup = | ||
| 236 | |||
| 237 | == 3.1 Overview == | ||
| 238 | |||
| 239 | The DLOS8N supports flexible network set up for different environments. This section describes the typical network topology. The network set up includes: | ||
| 240 | |||
| 241 | * **WAN Port Internet Mode** | ||
| 242 | * **WiFi Client Mode** | ||
| 243 | * **WiFi AP Mode** | ||
| 244 | * **Cellular Mode** | ||
| 245 | |||
| 246 | == 3.2 Use WAN port to access Internet == | ||
| 247 | |||
| 248 | By default, the DLOS8N is set to use the WAN port to connect to an upstream network. When you connect the DLOS8N’s WAN port to an upstream router, DLOS8N 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**: | ||
| 249 | |||
| 250 | [[image:1652420169255-959.png]] | ||
| 251 | |||
| 252 | |||
| 253 | == 3.3 Access the Internet as a WiFi Client == | ||
| 254 | |||
| 255 | In the WiFi Client Mode, DLOS8N acts as a WiFi client and gets DHCP from an upstream router via WiFi. | ||
| 256 | |||
| 257 | The settings for WiFi Client is under page (% style="color:#4f81bd" %)**System~-~-> WiFi ~-~-> WiFi WAN Client Settings** | ||
| 258 | |||
| 259 | [[image:1652420327792-211.png]] | ||
| 260 | |||
| 261 | |||
| 262 | In the WiFi Survey Choose the WiFi AP, and input the Passphrase then click Save & Apply to connect. | ||
| 263 | |||
| 264 | |||
| 265 | == 3.4 Access the Internet via Cellular == | ||
| 266 | |||
| 267 | If the DLOS8N support 3G/4G Cellular modem option, When the label on the shell is displayed as Model : DLOS8N-EC25, it indicates that DLOS8 already has EC25 3G/4G modules,user can use it as main internet connection or back up. | ||
| 268 | |||
| 269 | |||
| 270 | First, release the four screws of DLOS8N, pull out PCB and install SIM card as below: | ||
| 271 | |||
| 272 | [[image:1652420606018-181.png]] | ||
| 273 | |||
| 274 | |||
| 275 | [[image:1652420718132-929.png||height="450" width="766"]] | ||
| 276 | |||
| 277 | |||
| 278 | The set up page is (% style="color:#4f81bd" %)**System ~-~-> Cellular** | ||
| 279 | |||
| 280 | |||
| 281 | 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. | ||
| 282 | |||
| 283 | [[image:1652421032117-341.png||height="329" width="752"]] | ||
| 284 | |||
| 285 | (% style="color:red" %)**Note** *: For DLOS8N which doesn’t have the cellular module, this page will shows Cellular not detected. | ||
| 286 | |||
| 287 | |||
| 288 | == 3.5 Check Internet connection == | ||
| 289 | |||
| 290 | In the (% style="color:#4f81bd" %)**home**(%%) page, we can check the Internet connection. | ||
| 291 | |||
| 292 | * GREEN Tick [[image:1652421151598-130.png||height="23" width="24"]] : This interface has Internet connection. | ||
| 293 | * Yellow Tick [[image:1652421168047-470.png||height="22" width="21"]] : This interface has IP address but don’t use it for internet connection. | ||
| 294 | * RED Cross [[image:1652421179500-890.png||height="24" width="27"]] : This interface doesn’t connected. | ||
| 295 | |||
| 296 | [[image:1652421351382-793.png||height="339" width="765"]] | ||
| 297 | |||
| 298 | |||
| 299 | = 4. Example: Configure as a LoRaWAN gateway = | ||
| 300 | |||
| 301 | DLOS8N 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. | ||
| 302 | |||
| 303 | [[image:image-20220513140429-1.png||height="565" width="824"]] | ||
| 304 | |||
| 305 | This chapter describes how to use the DLOS8Nto work with | ||
| 306 | |||
| 307 | [[T>>url:https://www.thethingsnetwork.org/]]heThingsNetwork v3(T[[TN>>url:https://www.thethingsnetwork.org/]] v3[[)>>url:http://)]][[ LoRaWAN Server>>url:https://www.thethingsnetwork.org/]] ([[www.thethingsnetwork.org>>url:http://www.thethingsnetwork.org/]]) | ||
| 308 | |||
| 309 | |||
| 310 | == 4.1 Create a gateway in TTN V3 Server == | ||
| 311 | |||
| 312 | (% style="color:#4f81bd" %)**Step 1: Get a Unique gateway ID.** | ||
| 313 | |||
| 314 | Every DLOS8N has a unique gateway id. The ID can be found at LoRaWAN page: | ||
| 315 | |||
| 316 | [[image:1652421929753-168.png||height="403" width="739"]] | ||
| 317 | |||
| 318 | The example gateway id is: a840411e96744154 | ||
| 319 | |||
| 320 | |||
| 321 | (% style="color:#4f81bd" %)**Step 2: Sign up a user account in TTN server** | ||
| 322 | |||
| 323 | [[**https:~~/~~/account.thethingsnetwork.org/register**>>url:https://account.thethingsnetwork.org/register]] | ||
| 324 | |||
| 325 | [[image:1652422127479-258.png||height="346" width="738"]] | ||
| 326 | |||
| 327 | |||
| 328 | (% style="color:#4f81bd" %)**Step 3: Choose the TTNv3 Cluster Picker** | ||
| 329 | |||
| 330 | [[image:1652422142236-792.png||height="356" width="737"]] | ||
| 331 | |||
| 332 | |||
| 333 | (% style="color:red" %)**Note: Choose the cluster corresponds to a specific Gateway server address** | ||
| 334 | |||
| 335 | * Europe 1 (% style="color:red" %)corresponding Gateway server address: (% style="color:black" %)eu1.cloud.thethings.network | ||
| 336 | * North America 1 (% style="color:red" %)corresponding Gateway server address:** **(% style="color:black" %)nam1.cloud.thethings.network | ||
| 337 | * Australia 1 (% style="color:red" %)corresponding Gateway server address:** **(% style="color:black" %)au1.cloud.thethings.network | ||
| 338 | * Legacy V2 Console : (% style="color:red" %)TTN v2 shuts down in December 2021 | ||
| 339 | |||
| 340 | (% style="color:#4f81bd" %)**Step 4: Create a Gateway** | ||
| 341 | |||
| 342 | [[image:1652422440891-514.png||height="360" width="747"]] | ||
| 343 | |||
| 344 | Click the Gateway icon and then click Add gateway. | ||
| 345 | |||
| 346 | Open the following page: | ||
| 347 | |||
| 348 | [[image:1652422470352-518.png||height="391" width="716"]] | ||
| 349 | |||
| 350 | [[image:1652422479876-297.png||height="398" width="729"]] | ||
| 351 | |||
| 352 | (% style="color:red" %)**Notice: **Gateway Server address must match the gateway configuration, otherwise you will have problem for End Node to join the network. | ||
| 353 | |||
| 354 | After creating the gateway, you can see the gateway info, as below. | ||
| 355 | |||
| 356 | [[image:1652422509034-682.png||height="299" width="739"]] | ||
| 357 | |||
| 358 | |||
| 359 | == 4.2 Configure DLOS8N to connect to TTN v3 == | ||
| 360 | |||
| 361 | You can now configure the DLOS8N to let it connect to TTN network V3. | ||
| 362 | |||
| 363 | Make sure your DLOS8N has a working Internet Connection first. | ||
| 364 | |||
| 365 | Choose the right server provider and click (% style="color:#4f81bd" %)**Save&Apply** | ||
| 366 | |||
| 367 | [[image:1652422624783-580.png||height="327" width="729"]] | ||
| 368 | |||
| 369 | (% style="color:red" %)**Note: **The server address must match the Gateway server address you choose in TTN V3. | ||
| 370 | |||
| 371 | In the home page, we can see the LoRaWAN connection is ready now. | ||
| 372 | |||
| 373 | [[image:1652422685063-596.png||height="327" width="729"]] | ||
| 374 | |||
| 375 | In TTN v3 portal, we can also see the gateway is connected. | ||
| 376 | |||
| 377 | [[image:1652422703020-955.png||height="343" width="730"]] | ||
| 378 | |||
| 379 | |||
| 380 | == 4.3 Configure frequency == | ||
| 381 | |||
| 382 | We also need to set the frequency plan in DLOS8N to match the end node we use, so to receive the LoRaWAN packets from the LoRaWAN sensor. | ||
| 383 | |||
| 384 | [[image:1652422737399-529.png||height="362" width="737"]] | ||
| 385 | |||
| 386 | |||
| 387 | In logread page, user can check the frequency actually used. | ||
| 388 | |||
| 389 | [[image:1652422763536-750.png||height="514" width="730"]] | ||
| 390 | |||
| 391 | |||
| 392 | 4.4 Add a LoRaWAN End Device | ||
| 393 | |||
| 394 | This section shows how to add a LoRaWAN End device to a LoRaWAN network and see the data from TTN web site. | ||
| 395 | |||
| 396 | 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. | ||
| 397 | |||
| 398 | [[image:1652422794767-871.png]] | ||
| 399 | |||
| 400 | (% style="color:#4f81bd" %)**Step 1**: (% style="color:black" %)Create a Device definition in TTN v3 with the OTAA keys from the example LT-22222-L IO Controller device. | ||
| 401 | |||
| 402 | Three codes are required to define the device in TTN v3: | ||
| 403 | |||
| 404 | * DEV EUI - Unique ID code for a particular device. | ||
| 405 | * APP EUI - ID code for an Application defined in TTN v3. | ||
| 406 | * APP Key - Unique key to secure communications with a particular device. | ||
| 407 | |||
| 408 | 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. | ||
| 409 | |||
| 410 | [[image:1652422840936-838.png]] | ||
| 411 | |||
| 412 | |||
| 413 | (% 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. | ||
| 414 | |||
| 415 | For the TTN v3 server, you can use the codes set in the device as in the following example. | ||
| 416 | |||
| 417 | Select **Add Application** to open the screen below. | ||
| 418 | |||
| 419 | [[image:1652422946999-255.png||height="356" width="744"]] | ||
| 420 | |||
| 421 | Open the **Application **select** Add end device** | ||
| 422 | |||
| 423 | Start Register the end device | ||
| 424 | |||
| 425 | [[image:1652422975885-591.png||height="359" width="726"]] | ||
| 426 | |||
| 427 | Select OTAA activation mode | ||
| 428 | |||
| 429 | |||
| 430 | 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. | ||
| 431 | |||
| 432 | [[image:1652422998005-968.png||height="352" width="744"]] | ||
| 433 | |||
| 434 | First, input the End device ID, AppEUI and DevEUI. | ||
| 435 | |||
| 436 | [[image:1652423022781-339.png||height="365" width="741"]] | ||
| 437 | |||
| 438 | Secondly, choose the corresponding frequency and LoRaWAN class capabilities. | ||
| 439 | |||
| 440 | [[image:1652423046741-467.png||height="355" width="736"]] | ||
| 441 | |||
| 442 | Finally, Application layer settings input the corresponding AppKey. Before saving the configuration, check that the data matches the device. | ||
| 443 | |||
| 444 | |||
| 445 | (% style="color:#4f81bd" %)**Step 2**: (% style="color:black" %)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. | ||
| 446 | |||
| 447 | (% style="color:red" %)Note that it may take some time for the device data to appear in the TTN v3 display. | ||
| 448 | |||
| 449 | [[image:1652423277549-324.png||height="273" width="745"]] | ||
| 450 | |||
| 451 | |||
| 452 | = 5. Web Configure Pages = | ||
| 453 | |||
| 454 | == 5.1 Home == | ||
| 455 | |||
| 456 | Shows the system running status. | ||
| 457 | |||
| 458 | [[image:1652423418568-752.png||height="329" width="724"]] | ||
| 459 | |||
| 460 | |||
| 461 | == 5.2 LoRa Settings == | ||
| 462 | |||
| 463 | === 5.2.1 LoRa ~-~-> LoRa === | ||
| 464 | |||
| 465 | 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. | ||
| 466 | |||
| 467 | Different DLOS8N hardware version can support different frequency range: | ||
| 468 | |||
| 469 | * **868**: valid frequency: 863Mhz ~~ 870Mhz. for bands EU868, RU864, IN865 or KZ865. | ||
| 470 | * **915**: valid frequency: 902Mhz ~~ 928Mhz. for bands US915, AU915, AS923 or KR920 | ||
| 471 | |||
| 472 | After user choose the frequency plan, he can see the actually frequency in used by checking the page **LogRead ~-~-> LoRa Log** | ||
| 473 | |||
| 474 | [[image:1652423554776-574.png||height="380" width="740"]] | ||
| 475 | |||
| 476 | Note *: See this instruction for how to customize frequency band: | ||
| 477 | |||
| 478 | [[http:~~/~~/wiki.dragino.com/index.php?title=Customized_Frequency_Band_for_Gateway>>url:http://wiki.dragino.com/index.php?title=Customized_Frequency_Band_for_Gateway]] | ||
| 479 | |||
| 480 | |||
| 481 | === 5.2.2 LoRa ~-~-> ABP Decryption === | ||
| 482 | |||
| 483 | The DLOS8N can communicate with LoRaWAN ABP End Node without the need of LoRaWAN server. It can be used in some cases such as: | ||
| 484 | |||
| 485 | * No internet connection. | ||
| 486 | * 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>>http://8.211.40.43:8080/xwiki/bin/view/Main/MQTT%20Forward%20Instruction/]]). | ||
| 487 | |||
| 488 | Detail of this feature: [[Communication with ABP End Node>>http://8.211.40.43:8080/xwiki/bin/view/Main/Communicate%20with%20ABP%20End%20Node%20without%20LoRaWAN%20Network%20Server%20---%20LG308/]] | ||
| 489 | |||
| 490 | [[image:1652423628833-467.png||height="357" width="755"]] | ||
| 491 | |||
| 492 | |||
| 493 | == 5.3 LoRaWAN Settings == | ||
| 494 | |||
| 495 | === 5.3.1 LoRaWAN ~-~-> LoRaWAN === | ||
| 496 | |||
| 497 | 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 | ||
| 498 | |||
| 499 | [[image:1652423628833-467.png||height="357" width="755"]] | ||
| 500 | |||
| 501 | (% style="color:red" %)**Note:** | ||
| 502 | |||
| 503 | ~*: User can ignore the latitude and longitude settings here, DLOS8N will use the actually value from GPS module. | ||
| 504 | |||
| 505 | ~**: Packet filter is to drop the unwanted LoRaWAN packet, instruction see here: | ||
| 506 | |||
| 507 | See :[[Filter unwanted LoRaWAN packets>>http://8.211.40.43:8080/xwiki/bin/view/Main/Filter%20unwanted%20LoRaWAN%20packets/]] | ||
| 508 | |||
| 509 | |||
| 510 | === 5.3.2 LoRaWAN ~-~-> Amazon AWS-IoT === | ||
| 511 | |||
| 512 | [[image:1652428499323-384.png||height="275" width="723"]] | ||
| 513 | |||
| 514 | Please see this instruction to know more detail and demo for how to connect to AWS-IoT LoRaWAN Core: [[http:~~/~~/wiki.dragino.com/index.php?title=Notes_for_AWS-IoT-Core>>url:http://wiki.dragino.com/index.php?title=Notes_for_AWS-IoT-Core]] | ||
| 515 | |||
| 516 | |||
| 517 | === 5.3.3 LoRaWAN ~-~-> LORIOT === | ||
| 518 | |||
| 519 | Settings to communicate to LORIOT LoRaWAN Network Server: [[https:~~/~~/www.loriot.io/>>url:https://www.loriot.io/]] | ||
| 520 | |||
| 521 | Instruction: [[http:~~/~~/wiki.dragino.com/index.php?title=Notes_for_LORIOT>>url:http://wiki.dragino.com/index.php?title=Notes_for_LORIOT]] | ||
| 522 | |||
| 523 | [[image:1652428648903-878.png||height="266" width="731"]] | ||
| 524 | |||
| 525 | |||
| 526 | == 5.4 MQTT Settings == | ||
| 527 | |||
| 528 | If end nodes works in ABP mode, user can configure DLOS8N to transfer the data to MQTT broker, | ||
| 529 | |||
| 530 | Instruction: | ||
| 531 | |||
| 532 | [[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#MQTT_Forward_Instruction>>url:http://wiki.dragino.com/index.php?title=Main_Page#MQTT_Forward_Instruction]] | ||
| 533 | |||
| 534 | [[image:1652428705046-212.png||height="417" width="733"]] | ||
| 535 | |||
| 536 | |||
| 537 | == 5.5 System == | ||
| 538 | |||
| 539 | === 5.5.1 System ~-~-> System Overview === | ||
| 540 | |||
| 541 | Shows the system info: | ||
| 542 | |||
| 543 | [[image:1652428773760-580.png||height="408" width="728"]] | ||
| 544 | |||
| 545 | |||
| 546 | === 5.5.2 System ~-~-> General ( login settings) === | ||
| 547 | |||
| 548 | [[image:1652428861256-300.png||height="354" width="724"]] | ||
| 549 | |||
| 550 | **__System Password:__** | ||
| 551 | |||
| 552 | There are two login for DLOS8N: (% style="color:#4f81bd" %)root /dragino (% style="color:black" %)or (% style="color:#4f81bd" %)admin /dragino. (% style="color:black" %)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. | ||
| 553 | |||
| 554 | This page can be used to set the password for them. | ||
| 555 | |||
| 556 | ((( | ||
| 557 | |||
| 558 | ))) | ||
| 559 | |||
| 560 | **__Timezone:__** | ||
| 561 | |||
| 562 | Set device timezone. | ||
| 563 | |||
| 564 | ((( | ||
| 565 | |||
| 566 | ))) | ||
| 567 | |||
| 568 | **__Port forwarding:__** | ||
| 569 | |||
| 570 | Enable/Disable the HTTP and SSH access via WAN interface. | ||
| 571 | |||
| 572 | |||
| 573 | === 5.5.3 System ~-~-> Network === | ||
| 574 | |||
| 575 | [[image:1652429149053-824.png||height="467" width="725"]] | ||
| 576 | |||
| 577 | **__LAN Settings:__** | ||
| 578 | |||
| 579 | When the DLOS8N has the AP enable, LAN settings specify the network info for DLOS8N’s own network. | ||
| 580 | |||
| 581 | ((( | ||
| 582 | |||
| 583 | ))) | ||
| 584 | |||
| 585 | __**WAN Settings:**__ | ||
| 586 | |||
| 587 | Setting for DLOS8N WAN port | ||
| 588 | |||
| 589 | ((( | ||
| 590 | |||
| 591 | ))) | ||
| 592 | |||
| 593 | __**WiFi Settings:**__ | ||
| 594 | |||
| 595 | Setting for DLOS8N WiFi IP when use it as WiFi Client | ||
| 596 | |||
| 597 | |||
| 598 | === 5.5.4 System ~-~-> WiFi === | ||
| 599 | |||
| 600 | DLOS8N WiFi Settings. | ||
| 601 | |||
| 602 | [[image:1652429430767-921.png||height="367" width="723"]] | ||
| 603 | |||
| 604 | |||
| 605 | === 5.5.5 System ~-~-> Cellular === | ||
| 606 | |||
| 607 | 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. | ||
| 608 | |||
| 609 | [[image:1652429309615-825.png||height="320" width="732"]] | ||
| 610 | |||
| 611 | (% style="color:red" %)Note *: For DLOS8N which doesn’t have the cellular module, this page will shows Cellular not detected. | ||
| 612 | |||
| 613 | |||
| 614 | === 5.5.6 System ~-~-> Network Status === | ||
| 615 | |||
| 616 | [[image:1652429486609-208.png||height="415" width="728"]] | ||
| 617 | |||
| 618 | |||
| 619 | === 5.5.7 System ~-~-> Remote Mgnt & Auto Provision === | ||
| 620 | |||
| 621 | Auto Provision is the feature for batch configure and remote management. It can be used in below two cases: | ||
| 622 | |||
| 623 | [[image:1652429518191-846.png||height="332" width="733"]] | ||
| 624 | |||
| 625 | [[image:1652429527544-247.png||height="327" width="724"]] | ||
| 626 | |||
| 627 | [[image:1652429537849-154.png||height="339" width="722"]] | ||
| 628 | |||
| 629 | Please see this document for detail: | ||
| 630 | |||
| 631 | [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/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]] | ||
| 632 | |||
| 633 | |||
| 634 | R-SSH is for remote access device and management, introduction for how to use: | ||
| 635 | |||
| 636 | [[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#Remote_Access_Gateway_via_Reverse_SSH>>url:http://wiki.dragino.com/index.php?title=Main_Page#Remote_Access_Gateway_via_Reverse_SSH]] | ||
| 637 | |||
| 638 | [[image:1652429624400-864.png||height="432" width="716"]] | ||
| 639 | |||
| 640 | |||
| 641 | === 5.5.8 System ~-~-> Firmware Upgrade === | ||
| 642 | |||
| 643 | We keep improving the DLOS8N Linux side firmware for new features and bug fixes. Below are the links for reference. | ||
| 644 | |||
| 645 | * **Latest firmware**: [[LoRa Gateway Firmware>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LG02-OLG02/Firmware/]], | ||
| 646 | |||
| 647 | ( [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LG02-OLG02/Firmware>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LG02-OLG02/Firmware/]] ) | ||
| 648 | |||
| 649 | * **Change Log**: [[Firmware Change Log>>url:http://www.dragino.com/downloads/downloads/LoRa_Gateway/LG02-OLG02/Firmware/ChangeLog]]. | ||
| 650 | |||
| 651 | ( [[http:~~/~~/www.dragino.com/downloads/downloads/LoRa_Gateway/LG02-OLG02/Firmware/ChangeLog>>url:http://www.dragino.com/downloads/downloads/LoRa_Gateway/LG02-OLG02/Firmware/ChangeLog]] ) | ||
| 652 | |||
| 653 | |||
| 654 | 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. | ||
| 655 | |||
| 656 | (% style="color:green" %)**Web~-~-> System~-~-> Firmware Upgrade** | ||
| 657 | |||
| 658 | [[image:1652429711145-862.png||height="270" width="737"]] | ||
| 659 | |||
| 660 | Select the required image and click **Flash Image.** The image will be uploaded to the device, and then click **Process Update** to upgrade. | ||
| 661 | |||
| 662 | (% style="color:red" %)**NOTE**: (% style="color:black" %)You normally need to **//uncheck//** the **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. | ||
| 663 | |||
| 664 | The system will automatically boot into the new firmware after upgrade. | ||
| 665 | |||
| 666 | [[image:1652429962190-224.png||height="358" width="729"]] | ||
| 667 | |||
| 668 | |||
| 669 | (% style="color:red" %)**NOTE***(%%): User can also upgrade firmware via Linux console | ||
| 670 | |||
| 671 | SCP the firmware to the system(% style="color:green" %)**/var**(%%)** **directory and then run | ||
| 672 | |||
| 673 | (% style="color:#4f81bd" %)**//root@OpenWrt:~~# /sbin/sysupgrade –n /var/Your_Image//** | ||
| 674 | |||
| 675 | (% style="color:red" %)**NOTE**(%%) : it is important to transfer the image in the /var directory, otherwise it may exceed the available flash size. | ||
| 676 | |||
| 677 | |||
| 678 | === 5.5.9 System ~-~-> Reboot/Reset === | ||
| 679 | |||
| 680 | [[image:1652430197132-330.png||height="256" width="724"]] | ||
| 681 | |||
| 682 | ((( | ||
| 683 | |||
| 684 | ))) | ||
| 685 | |||
| 686 | === 5.5.10 System ~-~-> Package Maintain === | ||
| 687 | |||
| 688 | [[image:1652430243826-126.png||height="289" width="723"]] | ||
| 689 | |||
| 690 | Place to show what package has installed and possible to upgrade packages. | ||
| 691 | |||
| 692 | ((( | ||
| 693 | |||
| 694 | ))) | ||
| 695 | |||
| 696 | == 5.6 LogRead == | ||
| 697 | |||
| 698 | === 5.6.1 LogRead ~-~-> LoRa Log === | ||
| 699 | |||
| 700 | [[image:1652430356784-567.png||height="325" width="730"]] | ||
| 701 | |||
| 702 | Show the frequency for LoRa Radio and traffics. | ||
| 703 | |||
| 704 | ((( | ||
| 705 | |||
| 706 | ))) | ||
| 707 | |||
| 708 | === 5.6.2 LogRead ~-~-> System Log === | ||
| 709 | |||
| 710 | Show the system log | ||
| 711 | |||
| 712 | [[image:1652430369760-511.png||height="373" width="730"]] | ||
| 713 | |||
| 714 | |||
| 715 | = 6. More features = | ||
| 716 | |||
| 717 | == 6.1 More instructions == | ||
| 718 | |||
| 719 | [[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRa.2FLoRaWAN_Gateway_Instruction>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRa.2FLoRaWAN_Gateway_Instruction]] | ||
| 720 | |||
| 721 | ((( | ||
| 722 | |||
| 723 | ))) | ||
| 724 | |||
| 725 | = 7. Linux System = | ||
| 726 | |||
| 727 | The DLOS8N is based on the OpenWrt Linux system. It is open source, and users are free to configure and modify the Linux settings. | ||
| 728 | |||
| 729 | == 7.1 SSH Access for Linux console == | ||
| 730 | |||
| 731 | User can access the Linux console via the SSH protocol. Make sure your PC and the DLOS8N 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. | ||
| 732 | |||
| 733 | IP address: IP address of DLOS8N | ||
| 734 | |||
| 735 | Port: 22 (via WiFi AP mode) or 2222 (via WAN Interface) | ||
| 736 | |||
| 737 | User Name: (% style="color:green" %)**root** | ||
| 738 | |||
| 739 | Password: (% style="color:green" %)**dragino** (% style="color:black" %)(default) | ||
| 740 | |||
| 741 | After logging in, you will be in the Linux console and can enter commands as shown below. | ||
| 742 | |||
| 743 | [[image:1652431588565-830.png]] | ||
| 744 | |||
| 745 | The “(% class="mark" %)**logread -f**(%%)” command can be used to debug how system runs. | ||
| 746 | |||
| 747 | [[image:1652431609193-637.png||height="214" width="732"]] | ||
| 748 | |||
| 749 | |||
| 750 | == 7.2 Edit and Transfer files == | ||
| 751 | |||
| 752 | The DLOS8N 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. | ||
| 753 | |||
| 754 | In Windows, one of the easiest methods is using the [[WinSCP>>url:https://winscp.net/eng/index.php]] utility. | ||
| 755 | |||
| 756 | After establishing access via WinSCP to the device, you can use an FTP style window to drag / drop files to the DLOS8N, or edit the files directly in the windows. | ||
| 757 | |||
| 758 | Screenshot is as below: | ||
| 759 | |||
| 760 | [[image:1652431650755-450.png]] | ||
| 761 | |||
| 762 | |||
| 763 | == 7.3 File System == | ||
| 764 | |||
| 765 | The DLOS8N 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. | ||
| 766 | |||
| 767 | The Linux system uses around 8MB ~~10MB flash size which means there is not much room for user to store data in the DLOS8N flash. | ||
| 768 | |||
| 769 | You can use an external USB flash memory device to extend the size of flash memory for storage. | ||
| 770 | |||
| 771 | |||
| 772 | == 7.4 Package maintenance system == | ||
| 773 | |||
| 774 | DLOS8N 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 DLOS8N to use **//iperf //**. | ||
| 775 | |||
| 776 | 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]]) | ||
| 777 | |||
| 778 | **In Linux Console run:** | ||
| 779 | |||
| 780 | ((( | ||
| 781 | (% style="color:green" %)**root@dragino-169d30:~~# opkg update** (% style="color:black" %)~/~/ to get the latest packages list | ||
| 782 | ))) | ||
| 783 | |||
| 784 | ((( | ||
| 785 | (% style="color:green" %)**root@dragino-169d30:~~# opkg list** (% style="color:black" %) ~/~/shows the available packages | ||
| 786 | ))) | ||
| 787 | |||
| 788 | ((( | ||
| 789 | (% style="color:green" %)**root@dragino-169d30:~~# opkg install iperf ** (% style="color:black" %)~/~/ install iperf | ||
| 790 | ))) | ||
| 791 | |||
| 792 | The system will automatically install the required packages as shown below. | ||
| 793 | |||
| 794 | |||
| 795 | ((( | ||
| 796 | (% style="background-color:#dcdcdc" %)//root@dragino-169d30:/etc/opkg# opkg install iperf// | ||
| 797 | ))) | ||
| 798 | |||
| 799 | ((( | ||
| 800 | (% style="background-color:#dcdcdc" %)//Installing iperf (2.0.12-1) to root…// | ||
| 801 | ))) | ||
| 802 | |||
| 803 | ((( | ||
| 804 | (% 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]] | ||
| 805 | ))) | ||
| 806 | |||
| 807 | ((( | ||
| 808 | (% style="background-color:#dcdcdc" %)//Installing uclibcxx (0.2.4-3) to root…// | ||
| 809 | ))) | ||
| 810 | |||
| 811 | ((( | ||
| 812 | (% 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]] | ||
| 813 | ))) | ||
| 814 | |||
| 815 | ((( | ||
| 816 | (% style="background-color:#dcdcdc" %)//Configuring uclibcxx.// | ||
| 817 | ))) | ||
| 818 | |||
| 819 | ((( | ||
| 820 | (% style="background-color:#dcdcdc" %)//Configuring iperf.// | ||
| 821 | ))) | ||
| 822 | |||
| 823 | = 8. Upgrade Linux Firmware = | ||
| 824 | |||
| 825 | |||
| 826 | = 9. FAQ = | ||
| 827 | |||
| 828 | == 9.1 How can I configure for a customized frequency band? == | ||
| 829 | |||
| 830 | See below link for how to customize frequency band: | ||
| 831 | |||
| 832 | [[http:~~/~~/wiki.dragino.com/index.php?title=Customized_Frequency_Band_for_Gateway>>url:http://wiki.dragino.com/index.php?title=Customized_Frequency_Band_for_Gateway]] | ||
| 833 | |||
| 834 | |||
| 835 | == 9.2 Can I connect DLOS8N to LORIOT? == | ||
| 836 | |||
| 837 | Yes, the set up instruction is here: [[http:~~/~~/wiki.dragino.com/index.php?title=Notes_for_LORIOT>>url:http://wiki.dragino.com/index.php?title=Notes_for_LORIOT]] | ||
| 838 | |||
| 839 | |||
| 840 | == 9.3 Can I make my own firmware for the gateway, where can I find the source code? == | ||
| 841 | |||
| 842 | Yes, You can make your own firmware for the DLOS8N for branding purposes or to add customized applications. | ||
| 843 | |||
| 844 | 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]] | ||
| 845 | |||
| 846 | |||
| 847 | == 9.4 Can I use 868Mhz version for 915Mhz bands? == | ||
| 848 | |||
| 849 | 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. | ||
| 850 | |||
| 851 | |||
| 852 | = 10. Trouble Shooting = | ||
| 853 | |||
| 854 | == 10.1 I get kernel error when install new package, how to fix? == | ||
| 855 | |||
| 856 | 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: | ||
| 857 | |||
| 858 | (% style="background-color:yellow" %)root@dragino-16c538:~~# opkg install kmod-dragino2-si3217x_3.10.49+0.2-1_ar71xx.ipk | ||
| 859 | |||
| 860 | (% style="background-color:yellow" %)Installing kmod-dragino2-si3217x (3.10.49+0.2-1) to root… | ||
| 861 | |||
| 862 | (% style="background-color:yellow" %)Collected errors: | ||
| 863 | |||
| 864 | (% style="background-color:yellow" %)* satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-dragino2-si3217x: | ||
| 865 | |||
| 866 | (% style="background-color:yellow" %)* kernel (= 3.10.49-1-4917516478a753314254643facdf360a) * | ||
| 867 | |||
| 868 | (% style="background-color:yellow" %)* opkg_install_cmd: Cannot install package kmod-dragino2-si3217x. | ||
| 869 | |||
| 870 | In this case, you can use the –force-depends option to install such package as long as the actual kernel version is the same. | ||
| 871 | |||
| 872 | (% style="background-color:yellow" %)Opkg install kmod-dragino2-si3217x_3.10.49+0.2-1_ar71xx.ipk –force-depends | ||
| 873 | |||
| 874 | |||
| 875 | == 10.2 How to recover the DLOS8N if the firmware crashes == | ||
| 876 | |||
| 877 | Please follow this instruction to recover your gateway: | ||
| 878 | |||
| 879 | [[http:~~/~~/wiki.dragino.com/index.php?title=Recover_Gateway>>url:http://wiki.dragino.com/index.php?title=Recover_Gateway]] | ||
| 880 | |||
| 881 | |||
| 882 | == 10.3 I configured DLOS8N for WiFi access and lost its IP. What to do now? == | ||
| 883 | |||
| 884 | [[image:1652435238615-272.png||height="247" width="727"]] | ||
| 885 | |||
| 886 | The DLOS8N 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 DLOS8N no matter what the WiFi IP is. The fall back IP is useful for connecting and debug the unit. | ||
| 887 | |||
| 888 | (% style="color:red" %)Note: fallback IP can be disabled in the WAN and DHCP page. | ||
| 889 | |||
| 890 | |||
| 891 | Steps to connect via fall back IP: | ||
| 892 | |||
| 893 | ~1. Connect PC’s Ethernet port to DLOS8N’s WAN port | ||
| 894 | |||
| 895 | 2. Configure PC’s Ethernet port has | ||
| 896 | IP: 172.31.255.253 and | ||
| 897 | Netmask: 255.255.255.252 | ||
| 898 | |||
| 899 | As below photo: | ||
| 900 | |||
| 901 | [[image:1652435256286-879.png]] | ||
| 902 | |||
| 903 | 3. In the PC, use IP address 172.31.255.254 to access the DLOS8N via Web or Console. | ||
| 904 | |||
| 905 | Please note the latest firmware uses port 8000 for http and 2222 for ssh access. | ||
| 906 | |||
| 907 | |||
| 908 | = 11. Order Info = | ||
| 909 | |||
| 910 | (% style="color:#4f81bd" %) **//PART: DLOS8N-XXX-YYY//: ** | ||
| 911 | |||
| 912 | (% style="color:#4f81bd" %) **//XXX: Frequency Band//** | ||
| 913 | |||
| 914 | * (% style="color:#4f81bd" %)** 868**(% style="color:black" %) : valid frequency: 863Mhz ~~ 870Mhz. for bands EU868, RU864, IN865 or KZ865. | ||
| 915 | * (% style="color:#4f81bd" %)** 915**(% style="color:black" %): valid frequency: 902Mhz ~~ 928Mhz. for bands US915, AU915, AS923 or KR920 | ||
| 916 | |||
| 917 | (% style="color:#4f81bd" %) **//YYY: 4G Cellular Option//** | ||
| 918 | |||
| 919 | * (% style="color:#4f81bd" %)** E**(% style="color:black" %): EMEA, Korea, Thailand, India. | ||
| 920 | * (% style="color:#4f81bd" %)** A**(% style="color:black" %): North America/ Rogers/AT&T/T-Mobile. | ||
| 921 | * (% style="color:#4f81bd" %)** AU**(% style="color:black" %): Latin America, New Zeland, Taiwan | ||
| 922 | * (% style="color:#4f81bd" %)** J**(% style="color:black" %): Japan, DOCOMO/SoftBank/ KDDI | ||
| 923 | |||
| 924 | More info about valid bands, please see [[EC25-E product page>>url:https://www.quectel.com/product/ec25.htm]]. | ||
| 925 | |||
| 926 | |||
| 927 | = 12. Packing Info = | ||
| 928 | |||
| 929 | **Package Includes**: | ||
| 930 | |||
| 931 | * DLOS8N LoRaWAN Gateway x 1 | ||
| 932 | * Stick Antenna for LoRa RF part. Frequency is one of 470 or 868 or 915Mhz depends the model ordered | ||
| 933 | * Packaging with environmental protection paper box | ||
| 934 | |||
| 935 | **Dimension and weight**: | ||
| 936 | |||
| 937 | * Device Size: 12 x 12 x 3 cm | ||
| 938 | * Weight: 187g | ||
| 939 | * Package Size: 14.5 x 13.5 x 6 cm | ||
| 940 | * Weight: 300g | ||
| 941 | * | ||
| 942 | |||
| 943 | = 13. Support = | ||
| 944 | |||
| 945 | * Try to see if your questions already answered in the [[wiki>>url:http://wiki.dragino.com/]]. | ||
| 946 | * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. | ||
| 947 | Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before mentioned schedule. | ||
| 948 | * 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]] |