Differences

This shows you the differences between two versions of the page.

--- en:hw:01-axon:lte [2019/09/25 07:27]
martyy [Quick-start guide]
+++ en:hw:01-axon:lte [2020/11/10 16:17]
avsetula
@@ Line 1: / Line 1: @@
+{{page>en:hw:01-axon:replacement-of-axon-hidden}}
 ====== Axon LTE ======
+<WRAP center round tip 60%>
+Looking for a guide how to get started with LTE on **Mervis IDE**? Please see [[en:sw:01-mervis:lte-configuration-hidden|this tutorial]], otherwise continue here.
+</WRAP>
 ===== Quick-start guide =====
 <WRAP center round info 80%>
-LTE functionality is available in the open-source image only. Axon series controllers are shipped with the Mervis image by default. **__To use LTE, you have to flash the open-source image manually.__**
+Axon series controllers are shipped with the Mervis image by default. Mervis can be disabled or you can flash the open-source image manually.
   * [[https://kb.unipi.technology/files:software:os-images:00-start#axon_opensource_os|open-source image]]
   * [[https://kb.unipi.technology/en:hw:01-axon:image|HOW-TO Flash the OS]]
-LTE support on the Axon Mervis OS image will be available soon.
 </WRAP>
@@ Line 23: / Line 27: @@
   - During normal operation, "Mobile network" LED indicators SIM, NET, INT should be ON while blinking SIG indicates signal strength.
   - In case of any problem, check the Syslog for more info (you can use grep command to filter messages from the unipi-lte service).
+==== Autoswitch feature ====
+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 "swap" of these interfaces is necessary, the unipi-lte daemon automatically increases/decreases their metrics.
+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/network/interfaces.d//.
+Then, the ///etw/network/interfaces.d/**eth0**// file for static IP configuration may look like:
+<code>
+# Example static IP configuration for unit belonging to LAN
+auto eth0
+iface eth0 inet static
+  address 192.168.221.188
+  gateway 192.168.221.1
+  netmask 255.255.255.0
+  dns-nameservers 192.168.221.1
+  metric 5 # A positive non-zero constant
+</code>
+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.
 ===== LED Indicators =====
@@ Line 34: / Line 60: @@
 ===== Useful hints =====
-  * It's **necessary to use a cable-connected antenna** located outside an enclosure (e.g. switchboard).
+  * for optimal signal strength **it is necessary to use an external antenna** installed in an open space (eg. outside any enclosures). External antenna is included in the package of each LTE controller - during the purchase, you can also choose between the default antenna with magnetic mount, or a larger one with on-wall mount. Both antennas can be also purchased [[https://www.unipi.technology/others-c42|separately]]
   * 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.