> 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/pf/si/weather.md). # Weather The **Weather** feature supports traditional meteorological sensors that provide simple **pulse** or **analog** signals. A YuDash data logger can directly measure: * **Wind Speed** from a pulse-generating anemometer * **Wind Direction** from a potentiometer-based wind vane * **Rainfall** from a tipping-bucket rain gauge These measurements are handled differently inside the data logger. **Wind speed** is calculated over a configurable measurement window. Pulses are counted during the selected sample duration and converted into a wind-speed value using the configured calibration factor. **Rainfall**, on the other hand, is accumulated continuously in the background. Each tipping-bucket pulse represents a known amount of rainfall and is added to the relevant rainfall counters. Wind direction is typically acquired as an analog voltage from the wind-vane potentiometer and converted to **0–359°** using analog measurement and data scaling. {% hint style="info" %} **Sensor calibration is application-specific.** The user must configure the appropriate conversion factors, pulse resolution, debounce and related measurement settings according to the connected sensor manufacturer's specifications. Incorrect settings can result in inaccurate measurements. {% endhint %} Compact weather stations with internal electronics may provide wind and rainfall parameters directly over **Modbus, SDI-12 or serial/ASCII interfaces**. Those sensors are handled through the corresponding digital sensor interface rather than through the direct Weather measurements described here. ## Wind Speed and Direction **Wind speed** is measured from pulses generated as the cups rotate. The YuDash data logger counts these pulses over a configured sample window and converts the measured pulse rate into wind speed using the configured sensor factor. The resulting value can then be represented in the required engineering units, such as **m/s, km/h, mph or knots**, depending on the application. **Wind direction** is usually measured using a potentiometer connected to the wind vane. The changing potentiometer position produces an analog voltage, which is measured by the YuDash data logger and scaled into the required angular representation. A typical application may use **degrees (0–359°)**, while other angular units such as **radians** may also be used where required. ```mermaid flowchart LR A["Wind Speed Sensor
Pulse Output"] --> B["YuDash Data Logger
Pulse Counting"] B --> C["Wind Speed"] D["Wind Direction Sensor
Potentiometer Output"] --> E["YuDash Data Logger
Analog Input"] E --> F["Data Scaling
0–359°"] F --> G["Wind Direction"] ``` {% hint style="info" %} **Wind measurement accuracy depends on the sensor configuration.** The correct speed factor, sample window, debounce and direction scaling must be set according to the connected anemometer specifications and the required output units. {% endhint %} ### Configure Wind Speed & Direction The following example explains the Weather configuration using the **Davis 6410 anemometer**, which provides both wind-speed pulse output and potentiometer-based wind direction. The same **configuration workflow** can be used with other traditional anemometers. Sensor-specific wiring, pulse factors, debounce values and direction scaling must be set according to the connected sensor. Detailed sensor wiring is covered separately under **Sensor Integrations**. > If the installation uses a **wind-speed-only sensor**, the Wind Direction configuration can be skipped. For this example: * **Wind Speed** is measured through the Weather pulse input. * **Wind Direction** is measured through an analog input and converted to the required angular units using Data Scaling. The following steps show the complete configuration. Our primary worked example is the **Davis anemometer**, which is widely used in weather and hydrometeorological installations. {% stepper %} {% step %} #### Connect the Davis 6410 to FELYX For this example: * **DI1** is used for wind-speed pulse counting. * **C5** is used for the 0–5 V wind-direction signal. * **V5B** provides the potentiometer excitation supply. * **GND** is common to the sensor. > Wind speed and wind direction are independent measurements even though both are carried through the same Davis RJ11 cable.

{% endstep %} {% step %} #### Enable Weather Measurement From **Device Settings**, enable the **Weather** feature. Also keep **Analog Inputs** and **Data Scaling** enabled, since wind direction is handled through the analog channel and then converted to degrees.

After applying the device configuration, open: **Sensor Settings → Weather**

{% endstep %} {% step %} #### Configure Wind Speed The Davis 6410 wind-speed output is connected to **DI2**. FELYX counts the incoming pulses and converts them into a wind-speed value inside the **Weather** block. Open **Weather → Wind Speed** and enable **Wind Speed**.

For this example:

Setting	Value	Purpose
Cloud Variable Name	`wind_speed`	Variable generated by FELYX
Speed Factor	`0.1667`	Calibration factor used to convert the measured pulse count/frequency into wind speed
Debounce	`5 ms`	Rejects very closely spaced transitions or electrical noise
Sample Window	`10000 ms`	Measurement window over which the wind-speed pulses are evaluated

> The **Speed Factor** depends on the pulse-to-speed relationship of the connected anemometer. The value shown above is the factor used for this Davis 6410 integration. > {% endstep %} {% step %} #### Configure Wind Direction Input Wind direction from the Davis 6410 is obtained from the **potentiometer wiper** on the green conductor. With the potentiometer powered from the FELYX 5 V supply, the direction signal is measured as a **0–5 V analog input**. Open: **Sensor Settings → Analog** Enable **Channel 5 / C5** and configure it as:

| Setting | Value | | -------------- | --------------- | | **Topology** | `C5: 0–5000 mV` | | **Input Min** | `0` | | **Input Max** | `5000` | | **Output Min** | `0` | | **Output Max** | `5000` | | **Multiplier** | `1` | | **Variable** | `w_direction` | At this stage, FELYX is measuring the raw wind-direction signal in millivolts. The Davis 6410 uses a **wind vane and potentiometer** for direction sensing; the green wire is the potentiometer wiper and the yellow wire is its supply {% endstep %} {% step %} #### Convert Wind Direction to Degrees Open: **Data Scale & AXON → Data Scaling** Add the variable `w_direction` and configure: | Setting | Value | | ----------------- | ------------- | | **Variable Name** | `w_direction` | | **Min In** | `0` | | **Max In** | `5000` | | **Min Out** | `0` | | **Max Out** | `359` | {% endstep %} {% step %} #### Step 6 — Verify Wind Data After saving the configuration, open the **YuDash Local Dashboard** and verify the generated wind variables

In this test, approximately **2.3 V** was applied to the wind-direction input **C5**. The dashboard shows: * `analog_5` = **2307.07 mV** — raw analog input * `w_direction` = **165.648°** — scaled wind-direction value * `wind_speed` — wind-speed value generated from the pulse input With the configured scaling of **0–5000 mV → 0–359°.** ``` 2307 mV / 5000 mV × 359 ≈ 165.6° ``` The dashboard therefore confirms that the analog wind-direction signal is being acquired and converted correctly. > During commissioning, rotate the wind vane and anemometer to confirm that both `w_direction` and `wind_speed` respond correctly across their operating range. > {% endstep %} > {% endstepper %} ## Rain Gauge A **tipping-bucket rain gauge** converts rainfall into a sequence of electrical pulses. Rainwater is collected through the funnel and directed into a small two-sided tipping bucket. As one side fills to a calibrated volume, the bucket tips and empties. A magnet attached to the tipping mechanism passes a **reed switch**, creating one electrical pulse for each tip. Each pulse therefore represents a known amount of rainfall, defined by the sensor calibration or **mm per tip** value. #### How FELYX Measures Rainfall The rain-gauge output is connected to the YuDash data logger as a simple pulse input. For the example shown here: * one reed-switch wire is connected to **DI1** * the second wire is connected to **GND** * every valid bucket tip produces one pulse * the data logger continuously counts these pulses in the background * the pulse count is converted into rainfall using the configured **mm per tip** value

Unlike wind speed, rainfall is not calculated only during a short sample window. The rain counter remains active continuously so that individual bucket tips are not missed. A **debounce** setting is used to prevent contact bounce or electrical noise from causing a single physical tip to be counted more than once. > **Rainfall accuracy depends on correct sensor settings.** The configured `mm per tip`, debounce and pulse-input wiring must match the rain-gauge manufacturer's specification. ### Configure Rain Gauge 1\) The wiring shown below is a **representative example** of connecting the Davis 6464 tipping-bucket rain gauge to a YuDash data logger using the sensor's RJ11 cable. In standard terminal-input configurations, the rain pulse and ground conductors are connected to the appropriate **DI** and **GND** terminals. YuDash also offers product variants with **direct RJ11 sensor connectors** for simplified Davis installations.

2\) Open **Sensor Settings → Weather → Rain Gauge** and enable **Rain Gauge**.

#### 3) Rain Gauge Settings


Setting	Example	Description
Gauge Mode	`0 — ISR (no deep sleep)`	Standard rain-pulse counting mode. Keep this at `0` for normal installations. Other modes are intended for experimental/special use.
mm Per Tip	`0.2`	Rainfall represented by one valid bucket tip. This value must match the rain-gauge calibration.
Debounce	`50 ms`	Rejects additional contact transitions occurring immediately after a valid tip.
Start of Day	`0`	Defines when the daily rainfall counter rolls over, in minutes after local `00:00`.
Rain Data Directory	`/rain_dir`	Internal SD-card directory used by the rain-processing system.

> **Do not modify or delete files inside `/rain_dir`.** These files are maintained internally by the YuDash data logger for rainfall calculations and counter continuity. #### 4) Rainfall Variables The Weather feature maintains four rainfall variables. These values are refreshed on approximately a **one-minute basis**.

Variable	Meaning
`rain_today`	Total rainfall accumulated during the current configured rainfall day
`rain_yesterday`	Total rainfall accumulated during the previous rainfall day
`rain_curr_hr`	Rainfall accumulated during the current clock hour
`rain_prev_hr`	Total rainfall accumulated during the immediately preceding clock hour

The variable names can be changed to suit the destination application. Current Hour and Previous Hour `rain_curr_hr` accumulates rainfall during the current local clock hour. At the hour rollover, the completed value is transferred to `rain_prev_hr`, while `rain_curr_hr` starts again from zero. #### 5) Start of Day Rainfall calculations use the **device local time**. By default, the rainfall day changes at **00:00 local time**. The **Start of Day** setting allows this rollover time to be shifted to match the reporting convention required by the applicable meteorological department or project specification. The value is entered as the number of minutes after midnight. For example: ``` 00:00 → 0 04:00 → 240 06:00 → 360 ``` This setting affects **rainfall calculations only**. It does not change the device clock or the timestamp used by other measurements. #### How Rainfall Variables Update The example below illustrates how `rain_today`, `rain_yesterday`, `rain_curr_hr`, and `rain_prev_hr` change over time during rainfall. It also shows how the configured **Start of Day** and hourly rollover affect the accumulated values.