Differences

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

--- app-hotes:wifi-switcher [2023/10/31 15:22] – [WAN in Link Manager] cakir
+++ app-hotes:wifi-switcher [2023/12/12 12:21] (current) – [Goal] cakir
@@ Line 1: / Line 1: @@
 ====== Wifi Switcher ======
-===== Goal =====
+===== Goal and benefit for the costumer =====
-In this guide we will describe how to setup the WiFi Switcher SDK script on a Netmodule router. This script will take care of automatically connecting to a WiFi Access Point when it is part of a list we defined. The list is in a seperate file and consists of SSIDs and associated Password.
+In this guide we will describe how to setup the WiFi Switcher SDK script on a Netmodule router. This script will take care of automatically connecting to a WiFi Access Point when it is part of a list we defined. The list is in a seperate file and consists of SSIDs and associated Password. The benefit is that only these known access points can be connected to.
 ===== Application example =====
 Background for this script is a customer who uses our routers in railway applications. The router in the train is supposed to connect to a WiFi network on each respective train station. Only WiFi access points that can be found in the list are used to connect to.
+<code c application-example>
+TRAIN        TRAIN        TRAIN          TRAIN
+STATION A    STATION B    STATION C      STATION X
++--------+   +--------+   +--------+     +--------+
+|WIFI AP1|   |WIFI AP2|   |WIFI AP3|     |WIFI APX|
+|        |   |        |   |        |     |        |
++--------+   +--------+   +--------+ ... +--------+
+     TRAIN WIFI CLIENT
+        +--------+
++---------------------------------------------->
+</code>
 ===== Setup =====
 Here we will describe step-by-step how to setup the router with the wifi switcher functionality.
@@ Line 16: / Line 31: @@
 ==== Setup Trigger ====
-Here we setup a trigger that will start our SDK script later on. Since the script is supposed to run at all times we will set our trigger to event-based -> sdk-startup. As soon as SDK is enabled our wifi switcher script will be running.
+Here we setup a trigger that will start our SDK script later on. Since the script is supposed to run at all times we will set our trigger to "event-based -> sdk-startup". As soon as SDK is enabled our wifi switcher script will be running.
 {{:app-notes:triggers.png}}
@@ Line 30: / Line 45: @@
 {{:app-notes:jobs.png}}
-==== Setup Wifi Networks List ====
+==== Setup WiFi Networks List ====
-Unlike the wifi-switcher script the list of allowed wifi networks does not need to be connected with a job or trigger. It just needts to be available on the device. The reason why we use the GUI to insert this list is update security and also having this file be part of the router config. This wold not be the case when we simply just copy it by hand.
+Unlike the wifi-switcher script the list of allowed wifi access points does not need to be connected with a job or trigger. It just needts to be available on the device. The reason why we use the GUI to insert this list is update security and also having this file be part of the router config. This would not be the case when we simply just copy it by hand.
-It is important to use the correct name "wifi-networks.cfg" for this file, otherwise the WiFi Switcher script will not be able to find it. So just get the list example (can be found at the end of this guide) and adjust SSIDs and passwords to your scenario. The list is not limited to 7 entrys, it is possible to put a arbitary number of SSIDs to the file.
+It is important to use the correct name "wifi-networks.cfg" for this file, otherwise the WiFi Switcher script will not be able to find it. So just get the list example (can be found at the end of this guide) and adjust SSIDs and passwords to your scenario. The list is not limited to 7 entrys, it is possible to insert an arbitary number of SSIDs to the file.
 {{:app-notes:networks.png}}
@@ Line 46: / Line 61: @@
 Here is a short description of the funtionality of the script.
-You have the option to set DEBUG=1, this will give you some output visible in tail-log.
+You have the option to set DEBUG=1, this will give you some debug output visible in tail-log.
-First the scirpt will read in the list of access points it is supposed to connect to.
-Then the scirpt will keep on looking up the state of the WiFi (WLAN1 setup as WANLINK2).
+First the scirpt will import the list of access points it is supposed to connect to. Then the scirpt will keep on looking up the state of the WiFi (WLAN1 which is setup as WANLINK2).
-In case of the state being "dialing" or "up" we do nothing and wait for 5 seconds before we check status again.
-In caste the state is "down" and the last scan is at least 30 seconds in the past we trigger a new scan of the currently available Wifi networkss.
+In case of the state being "dialing" or "up" we do nothing and wait for 5 seconds before we check this status again. In caste the state is "down" and the last scan is at least 30 seconds in the past we trigger a new scan of the currently available Wifi networkss.
-After the scan is finished we take the data and compare it to the list we created earlier. When a known access point is found and the last WiFi config update is at least 120 seconds in the past, we update the wifi config so we can connect to the now available WiFi etwork.
+After the scan is finished we take the data and compare it to the list we imported earlier. When a known access point is found and the last WiFi config update is at least 120 seconds in the past, we update the wifi config so we can connect to the now available WiFi AP.
 <code c wifi-switcher.are>

User Tools

Site Tools

Differences

Page Tools