> For the complete documentation index, see [llms.txt](https://docs.yudash.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yudash.com/felyx/gs/how.md).
# How FELYX Works
## Understanding FELYX: Configuration & Data Flow
FELYX is designed around a modular configuration architecture. The device is configured through its built-in **Web UI over LAN or Wi-Fi**, while JSON-based configuration is used extensively across device functions and for configuration backup and restore.
A typical FELYX application can be understood as a simple data flow:
The configuration pages and Wizards define how data moves through each stage.
#### Network Configuration – How FELYX Connects
In addition to defining **what data to read, how to process it, and where to send it**, FELYX must also be configured for **how it connects to the network or Internet**.
This is handled separately under **Network Settings**, where the required connection mode is selected: **4G/LTE, Ethernet, Wi-Fi, or Offline**.
Network settings are stored separately from the main device configuration. This allows the same FELYX configuration to be retained even when the network connection method changes.
### Wizard-Based Configuration
Most FELYX features are configured through dedicated **Wizards**. Each Wizard groups the settings required for a particular function and provides a structured interface for configuring that feature.
For example, Analog Inputs are configured through the **Analog Wizard**, SDI-12 sensors through the **SDI-12 Wizard**, Data Scaling through the **DataScale Wizard**, and AXON functions through the **AXON Wizard**.
The detailed settings are saved through the respective Wizard and remain available as part of the device configuration.
### Configure and Enable
In FELYX, **configuration and feature activation are separate**.
A feature can be fully configured and its settings saved through the corresponding Wizard. However, the feature is processed by the device only when it is also **enabled under Device Settings → Feature Settings**.
For example, Analog Input channels may be configured and saved in the Analog Wizard, but analog inputs will be processed only when the **Analog Inputs** checkbox is enabled under Feature Settings.
This separation provides flexibility. A feature can be temporarily disabled without deleting or changing its saved configuration.
### Sensor Settings – What to Read
The **Sensor Settings** section defines the sensors and instruments from which FELYX acquires data.
Depending on the FELYX model and application, sensor data may be acquired through interfaces such as **RS485 Modbus RTU, SDI-12, Analog Inputs, Rain Gauge inputs, Wind Speed & Direction inputs and other supported interfaces**.
Each sensor configuration maps the acquired measurements to variables within FELYX. These variables can then be used by other device functions for processing, monitoring, logging and telemetry.
### Data Processing – What to Do with the Data
After data has been acquired, FELYX can process the values locally before they are displayed, logged or transmitted.
#### Data Scaling
**Data Scaling** provides functions for scaling and clipping sensor values. It can be used to convert acquired values into the required engineering or application values.
#### YuDash AXON
**YuDash AXON Edge Intelligence** provides additional on-device processing capabilities. AXON supports functions including formula-based derived parameters, ASCII/custom protocol parsing, rule-based edge actions and an embedded SQL database and dashboard.
This allows FELYX to perform calculations and application logic directly at the edge rather than only forwarding raw sensor data.
**Sensor Settings acquire the data. Data Scaling and AXON process the data.**
### Live Monitoring and Display
FELYX provides local methods for viewing device and sensor information without requiring cloud connectivity.
#### Live Dashboard
The on-device **Live Dashboard** provides real-time monitoring of the present sensor and parameter values through the FELYX Web UI. It is useful during installation, commissioning, testing and diagnostics.
FELYX also provides on-device data monitoring and access to the SD Card through its local interface.
#### OLED Display
The built-in **OLED Display** provides local device status and diagnostic information directly on the FELYX hardware.
Together, the Web UI and OLED provide immediate local visibility of device operation.
### Data Logger – Store the Data
The **Data Logger** provides local storage of sensor and calculated data.
FELYX supports configurable CSV format and timestamping, along with user-defined file names and logging intervals.
The Data Logger therefore provides historical data storage independently of cloud or network connectivity.
**Data Logger defines what FELYX stores locally.**
### Cloud Settings – Where to Send the Data
The **Cloud Settings** section controls IoT Telemetry from FELYX to external servers and cloud platforms.
FELYX supports **MQTT, REST API, HTTP and FTP**, TLS/SSL encryption, configurable JSON/TXT payloads, and multi-server telemetry with automatic backfill after network recovery.
The Cloud Settings determine how the required variables are packaged and transmitted to the configured destination.
### Overall FELYX Data Flow
