Differences

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

--- en:hw:01-axon:lte [2023/07/11 14:58] – avsetula
+++ en:hw:01-axon:lte [2025/05/16 09:55] (current) – [Autoswitch feature] typo ofojt
@@ Line 1: / Line 1: @@
 {{page>en:hw:01-axon:replacement-of-axon-hidden}}
 ====== Axon LTE ======
-<WRAP group 100%>
-<WRAP half column 81%>
+<WRAP group center round box 95%>
-<WRAP center round tip 60%>
+{{ :files:img_warning-line_b.png?nolink |}}
+<WRAP half column 13%>
+{{ :en:hw:08_safety-instructions_pseudo-ISO-7010-info.png?nolink |(i)}}
+</WRAP>
+<WRAP half column 83%>
 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>
-</WRAP>
-<WRAP half column 15%>
-;;#
-<html><span class="dev-tag dev-axon">Axon</span></html>
-;;#
 </WRAP>
 </WRAP>
@@ Line 16: / Line 14: @@
 ===== Quick-start guide =====
-<WRAP center round info 80%>
+<WRAP group center round box 95%>
+{{ :files:img_warning-line_b.png?nolink |}}
+<WRAP half column 13%>
+{{ :en:hw:09_safety-instructions_pseudo-ISO-7010-attention.png?nolink |(!)}}
+</WRAP>
+<WRAP half column 83%>
 Axon series units 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]]
+</WRAP>
 </WRAP>
@@ Line 40: / 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 "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//.
+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/network/interfaces.d//.
-Then, the ///etw/network/interfaces.d/**eth0**// file for static IP configuration may look like:
+Then, the ///etc/network/interfaces.d/**eth0**// file for static IP configuration may look like:
 <code>
 # Example static IP configuration for unit belonging to LAN