--- title: "Barani MeteoWind 2" description: "Monitor wind speed, gusts and wind direction via Modbus RTU through an RS-485-to-Ethernet gateway. TapHome integration template for Barani MeteoWind 2." url: "https://taphome.com/en/compatibility/barani-meteowind2/" language: en lastmod: 2026-10-08 generator: hugo ai: topics: ["modbus-tcp","modbus-rtu","sensor","rs485","wind-sensor","anemometer","gateway"] questions: ["How to integrate Barani MeteoWind 2 with TapHome?","What does the Barani MeteoWind 2 TapHome template measure?","How to connect Barani MeteoWind 2 via Modbus RTU to TapHome?","Which RS-485-to-Ethernet gateway works with the MeteoWind 2 TapHome template?","What are the correct RS-485 wire colors on the MeteoWind 2 bayonet cable?","How to calibrate the wind direction north offset on the MeteoWind 2?"] --- # Barani MeteoWind 2 Communication: Modbus TCP - [Barani Design Official Website](https://www.baranidesign.com/meteowind2-anemometer) > Network address > > TapHome reaches this device at the address entered on import. Give the device a fixed address — an IP reservation in the router, or its mDNS name if it supports one — otherwise the integration stops working when the router changes the address. > > [Network Preparation](https://taphome.com/en/docs/setup/network-preparation/) ## Integration guide The Barani MeteoWind 2 is a combined cup anemometer and wind vane built by BARANI DESIGN Technologies (Slovakia). It exceeds WMO and MEASNET Class 1 accuracy standards and samples wind speed and direction at 10 Hz. The same template also covers the **Heated MeteoWind 2**, which shares identical wiring and an identical Modbus register map. The sensor is natively a **Modbus RTU / RS-485** device — it has no Ethernet port. The TapHome template is declared as Modbus TCP, so the sensor is connected through an **RS-485-to-Ethernet gateway** (a Modbus-RTU-to-TCP converter). The template polls five input registers every 1 second and exposes wind speed in km/h and wind direction in degrees. ## Hardware connection The sensor ships with a 5 m pigtail cable with a weather-sealed bayonet connector on the sensor side and tinned leads on the other. All BARANI DESIGN RS-485 sensors share the same wire-color scheme, so MeteoWind 2, Heated MeteoWind 2 and other Barani Modbus sensors are electrically interchangeable on the same bus. ### Wiring ![Barani MeteoWind 2 bayonet cable wire colors — Brown VCC, White GND, Green RS-485 A, Yellow RS-485 B](https://taphome.com/images/compatibility/barani-meteowind2/wiring-rs485_hu_d9a00bdae2b3f95e.jpg) | Wire color | Function | Notes | |------------|----------|-------| | **Brown** | VCC (+5 to +24 V DC) | Power positive. Inrush and reverse-polarity protected. | | **White** | GND | Common ground for power and RS-485 reference. | | **Green** | RS-485 **A** | Non-inverting data line (D+). | | **Yellow** | RS-485 **B** | Inverting data line (D−). | > [!WARNING] > Some PLCs and gateways label their RS-485 terminals with reversed polarity. If the sensor does not respond after wiring, swap the Green and Yellow wires and retry — the Barani side of the cable follows the canonical A/B convention. ### Gateway and bus topology The TapHome template uses `ModbusTcpCCU`, so an **RS-485-to-Ethernet gateway** (Modbus-RTU-to-TCP converter) is required between the sensor and TapHome Core. Three options are commonly used: - **TapHome Modbus-to-LAN converter** — the native TapHome accessory, pre-configured for Modbus RTU bridging. - **Barani Easy MODBUS Starter Kit** — Barani's own RS-485 USB converter bundle for PC setup and debugging; a full TCP gateway (e.g. USR-TCP232 or similar) is still required for network use. - **Generic Modbus-RTU-to-TCP gateways** — any standard RS-485-to-Ethernet converter (USR-TCP232-style, Moxa, Waveshare) works, provided it passes Modbus RTU frames transparently. Follow standard RS-485 bus practice: - Use twisted-pair cable for the A/B lines (ideally shielded). - Terminate both ends of the bus with a 120 Ω resistor on cable runs longer than ~5 m. - Keep the White (GND) wire tied to the same ground reference as the gateway. - Up to 247 slaves and ~1200 m total bus length at 19 200 baud are supported by the RS-485 specification. Feed the Brown wire from an external 5–24 V DC rail. The sensor draws about 2.6 mA at 12 V (combined speed + direction, 10 Hz sampling, RS-485 on), so a small DIN-rail supply is sufficient. Do not back-feed power from the TapHome data bus. ## Configuration ### Default Modbus parameters The MeteoWind 2 ships with these factory defaults: | Parameter | Default | |-----------|---------| | Protocol | Modbus RTU | | Baud rate | 19 200 bps | | Data bits | 8 | | Parity | None | | Stop bits | 1 | | Slave ID | 1 | Protocol (RTU/ASCII), Slave ID, baud rate, parity and stop bits are all user-selectable via **Holding register 5** using the Barani Easy MODBUS Viewer software. Any change to Holding register 5 must be persisted by writing `0x0008` to **Holding register 11** (save command) — the device acknowledges by reading `0x0000` back. In most TapHome deployments the factory defaults are left unchanged. ### Import parameters When importing the template in TapHome, provide: - **IP Address** — the IP of the RS-485-to-Ethernet gateway on the local network. - **Slave ID** — Modbus slave address of the MeteoWind 2 (default `1`). Configure the gateway itself (port 502, RS-485 side at 19 200 / 8 / N / 1) according to the gateway manufacturer's instructions before importing the template. ### Wind direction north-offset calibration The MeteoWind 2 wind vane reports a raw direction in degrees relative to a mechanical reference mark on the housing. To make the readings align with true north, a one-time calibration is performed at install time by writing an offset to **Holding register 74** (`0x0049`): ```text Angle OFFSET (bits) = 1024 − ( measured_deg / 360 × 1024 ) ``` Procedure: 1. Measure the physical orientation error of the sensor against true north (e.g. with a compass app). 2. Write the computed offset to Holding register 74 (function code `06`). 3. Persist by writing `0x0008` to Holding register 11 — the device acknowledges by reading `0x0000`. This calibration is not exposed in the current TapHome template — use the Barani Easy MODBUS Viewer software or any Modbus master tool to perform it once, and the offset stays in the sensor's non-volatile memory afterwards. ## Device capabilities The template exposes five read-only sensor variables, all polled over Modbus TCP every 1 second. ### Wind speed monitoring - **Wind Speed** — instantaneous wind speed in km/h, sampled at 10 Hz internally. Read from Input register 6 (offset 5, Uint16, raw × 0.036 = km/h). - **Average Wind Speed** — wind speed averaged over the configured sampling period. Read from Input register 8 (offset 7, Uint16). Useful for smoothing noisy readings and for slow-reacting automations. - **Max Wind Speed** — peak (gust) wind speed observed within the configured sampling period. Read from Input register 9 (offset 8, Uint16). Ideal for gust-based automation rules such as automatically retracting awnings, shades or pergolas above a safety threshold. The averaging period used by the Average and Max variables is configured via **Holding register 10** (seconds, 1-second increments). It defaults to a short window suitable for live monitoring and can be increased for calmer, longer-term averaging. ### Wind direction monitoring - **Wind Direction** — current wind direction in degrees (0–360°), sampled at 10 Hz. Read from Input register 7 (offset 6, Uint16, raw ÷ 100 = degrees). North alignment depends on the one-time Holding register 74 calibration — see *Wind direction north-offset calibration* above. - **Average Wind Direction** — wind direction averaged over the same sampling period configured by Holding register 10. Read from Input register 10 (offset 9, Uint16). ### Additional capabilities The MeteoWind 2 also exposes a handful of configuration and maintenance registers over Modbus — the packed communication settings (Holding register 5), the sampling / averaging period (Holding register 10), the save-settings command (Holding register 11) and the wind-direction north-offset calibration (Holding register 74). The Heated MeteoWind 2 variant additionally provides an independent heater-control circuit (20 W @ 24 V or 5 W @ 12 V) that is wired separately and is not part of the Modbus register map. These configuration registers and the heater control can be exposed as service actions in a future template update. ## Troubleshooting ### No communication after import 1. Verify the gateway is powered and reachable on the local network — ping its IP address from a device on the same subnet. 2. Confirm the gateway's RS-485 side is configured for **19 200 / 8 / N / 1** to match the MeteoWind 2 factory defaults. 3. Check that the Slave ID in the TapHome import parameters matches the sensor's ID (factory default is `1`). 4. Ensure TapHome Core and the gateway share the same network / subnet, and that no firewall is blocking Modbus TCP (port 502) between them. ### Intermittent readings or CRC errors 1. Confirm the White (GND) wire is connected to the gateway ground — RS-485 requires a shared ground reference, not just the A/B differential pair. 2. Verify bus termination — add a 120 Ω resistor at both ends of the bus on runs longer than ~5 m. 3. Use twisted-pair (ideally shielded) cable for A/B and route it away from high-power or high-frequency cables. ### Wind direction is offset from true north The sensor's zero direction depends on its physical mounting orientation. Perform the one-time **wind-direction north-offset calibration** (see Configuration section) to align the readings with true north. Without calibration, the direction values are still consistent and usable for relative changes, but the absolute heading will be wrong. ### Heated MeteoWind 2 heater not working The heater circuit on the Heated MeteoWind 2 variant is wired independently of the RS-485 data bus and is not controlled through this TapHome template. Verify the heater wiring and heater power supply (20 W @ 24 V DC or 5 W @ 12 V DC) against the Heated MeteoWind 2 wiring notes in the Barani FAQ. ## Available devices 5 These devices appear in TapHome after import. MeteoWind 2 Module Wind Direction Variable Read-only Current wind direction in degrees (0–360°), sampled at 10 Hz — requires one-time north-offset calibration at install time Register: I:6 Uint16 Unit: ° Read ```taphome MODBUSR(A, 6, Uint16) / 100.0 ``` Wind Speed Variable Read-only Instantaneous wind speed in km/h, sampled at 10 Hz Register: I:5 Uint16 Unit: km/h Read ```taphome MODBUSR(A, 5, Uint16) * 0.036 ``` Average Wind Speed Variable Read-only Wind speed averaged over the configured sampling period (km/h) Register: I:7 Uint16 Unit: km/h Read ```taphome MODBUSR(A, 7, Uint16) * 0.036 ``` Max Wind Speed Variable Read-only Peak (gust) wind speed observed within the configured sampling period (km/h) — useful for gust-based automation rules Register: I:8 Uint16 Unit: km/h Read ```taphome MODBUSR(A, 8, Uint16) * 0.036 ``` Average Wind Direction Variable Read-only Wind direction averaged over the configured sampling period (degrees) Register: I:9 Uint16 Unit: ° Read ```taphome MODBUSR(A, 9, Uint16) / 100.0 ``` **Connection:** Modbus TCP • Slave ID: $\[SlaveId] Possible improvements (4) - H:4 Communication settings — Packed bitfield — protocol (RTU/ASCII), Slave ID (1–127), stop bits, parity, baud rate. Rarely needs runtime change; typically set once via Barani's configuration tool. - H:10 Sampling / averaging period — Uint16 seconds — averaging window for Input registers 8/9/10 (Average speed, Max speed, Average direction). Could be exposed as a service action. - H:11 Save settings / commit — Write 0x0008 to persist pending configuration changes; device ACKs by reading back 0x0000. Only needed when writing H:4 or H:74. - H:74 Wind direction north-offset calibration — 1024-bit circle offset for aligning wind vane with true north. Formula: offset = 1024 − (measured\_deg / 360 × 1024). Required once at install time; could be exposed as a service action in template. ## Import parameters Enter these values when you import the XML. | Asked in the app | Default | |------------------|---------------| | Slave ID | `1` | | IP address | `192.168.0.1` | ## Sources - MeteoWind 2 Datasheet [www.baranidesign.com](https://www.baranidesign.com/s/MeteoWind-2-DataSheet.pdf) 2026-04-16 [PDF](https://taphome.com/compatibility/devices/barani-meteowind2/manufacturer/datasheet.pdf) - Barani Easy MODBUS Quick Guide (MeteoWind register map) [www.baranidesign.com](https://www.baranidesign.com/s/Easy-MODBUS-Starter-Kit-Quick-Guide.pdf) 2026-04-16 [PDF](https://taphome.com/compatibility/devices/barani-meteowind2/manufacturer/modbus-quick-guide.pdf) - MeteoWind 2 product page [www.baranidesign.com](https://www.baranidesign.com/meteowind2-anemometer) 2026-04-16 - MeteoWind & MeteoTemp RS-485 Wire Colors and Electrical Connection (FAQ) [www.baranidesign.com](https://www.baranidesign.com/faq-articles/2020/3/23/meteotemp-meteowind-rs485-wire-colors-and-electrical-connection) 2026-04-16 Manufacturer documents are © their respective owners. They are provided as published by the manufacturer, for reference only. ## Related Documentation - [Modbus Integration](https://taphome.com/en/compatibility/modbus-guide/) - [Modbus](https://taphome.com/en/docs/integration/modbus/) - [Simple configuration using templates](https://taphome.com/en/docs/integration/modbus/templates/) - [Modbus scripts and prefetch](https://taphome.com/en/docs/script/modbus-scripts/) - [Modbus functions](https://taphome.com/en/docs/script/modbus/) - [Modbus data types](https://taphome.com/en/docs/script/modbus-data-types/)