Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:hw:01-axon:lte [2019/11/21 07:23] – tomhora | en:hw:01-axon:lte [2025/05/16 09:55] (current) – [Autoswitch feature] typo ofojt | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | {{page> | ||
| ====== Axon LTE ====== | ====== Axon LTE ====== | ||
| - | <WRAP center round tip 60%> | + | |
| - | Looking for a guide how to get started with LTE on Mervis? Please see [[en: | + | < |
| + | {{ : | ||
| + | <WRAP half column 13%> | ||
| + | {{ : | ||
| + | </ | ||
| + | <WRAP half column 83%> | ||
| + | Looking for a guide how to get started with LTE on **Mervis | ||
| + | </ | ||
| </ | </ | ||
| ===== Quick-start guide ===== | ===== Quick-start guide ===== | ||
| - | <WRAP center round info 80%> | + | < |
| - | Axon series | + | {{ : |
| + | <WRAP half column 13%> | ||
| + | {{ : | ||
| + | </ | ||
| + | <WRAP half column 83%> | ||
| + | Axon series | ||
| * [[https:// | * [[https:// | ||
| * [[https:// | * [[https:// | ||
| + | </ | ||
| </ | </ | ||
| Line 15: | Line 29: | ||
| - Insert a micro-sim supporting LTE data into the slot. | - Insert a micro-sim supporting LTE data into the slot. | ||
| - | - Log-in to the controller | + | - Log-in to the unit via SSH. |
| - Install unipi-lte package:< | - Install unipi-lte package:< | ||
| sudo su | sudo su | ||
| Line 23: | Line 37: | ||
| - Edit file / | - Edit file / | ||
| - In the same way, set the PIN parameter if SIM is PIN-protected. | - In the same way, set the PIN parameter if SIM is PIN-protected. | ||
| - | - Restart your controller. Be patient, registration to the mobile network can take tens of seconds. When registered, NET LED lights up. | + | - Restart your unit. Be patient, registration to the mobile network can take tens of seconds. When registered, NET LED lights up. |
| - During normal operation, " | - During normal operation, " | ||
| - In case of any problem, check the Syslog for more info (you can use grep command to filter messages from the unipi-lte service). | - In case of any problem, check the Syslog for more info (you can use grep command to filter messages from the unipi-lte service). | ||
| Line 30: | Line 44: | ||
| By default, the unipi-lte Linux service provides automatic handling with the default network gateway according to the WAN availability on both main and backup network interfaces. The main network adapter is usually wired ethernet (eth0) while the backup is realized by the LTE modem. In the Linux routing table, the default GW routes for both of these interfaces should be always present. When a " | By default, the unipi-lte Linux service provides automatic handling with the default network gateway according to the WAN availability on both main and backup network interfaces. The main network adapter is usually wired ethernet (eth0) while the backup is realized by the LTE modem. In the Linux routing table, the default GW routes for both of these interfaces should be always present. When a " | ||
| - | Therefore, it is necessary to continually keep the metrics as positive non-zero values. This is ensured by a DHCP client when DHCP is active on the main network interface, but **it must be assured manually if static IP is configured on the main interface** (as static routes have zero metrics as default). As an example, you can put a constant to the interface’s configuration file at ///etw/ | + | Therefore, it is necessary to continually keep the metrics as positive non-zero values. This is ensured by a DHCP client when DHCP is active on the main network interface but **it must be assured manually if static IP is configured on the main interface** (as static routes have zero metrics as default). As an example, you can put a constant to the interface’s configuration file at ///etc/ |
| - | Then, the ///etw/ | + | Then, the ///etc/ |
| < | < | ||
| # Example static IP configuration for unit belonging to LAN | # Example static IP configuration for unit belonging to LAN | ||
| Line 47: | Line 61: | ||
| The auto-switch feature can be disabled in the daemon’s config file. | The auto-switch feature can be disabled in the daemon’s config file. | ||
| - | An additional feature **auto_keepon** should help if the lte network interface is turned off accidentally (e.g. caused by //ifdown// command). In such a case, the re-enable (UP) operation is performed on that interface and also routing table records are refreshed. The feature is enabled by default and can be disabled in the configuration file. | + | An additional feature **auto_keepon** should help if the LTE network interface is turned off accidentally (e.g. caused by //ifdown// command). In such a case, the re-enable (UP) operation is performed on that interface and also routing table records are refreshed. The feature is enabled by default and can be disabled in the configuration file. |
| ===== LED Indicators ===== | ===== LED Indicators ===== | ||
| Line 59: | Line 73: | ||
| ===== Useful hints ===== | ===== Useful hints ===== | ||
| - | * It' | + | * for optimal signal strength |
| * Operate both Wi-Fi and LTE simultaneously is not recommended. | * Operate both Wi-Fi and LTE simultaneously is not recommended. | ||
| * The Ethernet interface is set as primary while the LTE acts as a backup by default. | * The Ethernet interface is set as primary while the LTE acts as a backup by default. | ||