-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is the multiplier with the anemometer correct #6
Comments
Hi, Sorry for the late reply. I agree with you, there has been a lot of wind here and the measurements are not consistent with the official stations. My method for the calculation: For 60 seconds, at 2.4Km/h, we have 60 pulses/minutes.
And according to the measurements made this weekend, it is more in connection. Have you made the change and do you confirm this result in practice? |
Yeah, I used 0.01111 in my setup. I have no other device as reference, but it feels more in check with reality/predictions. |
Now, after reading this thread, I'm not sure about 0.11111 and the calculation from my last post https://community.home-assistant.io/t/measuring-wind-speed/395693/3 I need to investigate more. |
One another very useful post : mkuoppa/esphomeweatherstation#2 (comment) @khenderick What is the diameter of your anemometer ? |
Perhaps it could help :
|
My diameter is ~18cm (hard to measure). This means a circumference of ~0.5m. Thus in theory, if the wind moves 0.5m/s, the anemometer rotates once per second. Ignoring any losses, this would mean 1.8km/h. The datasheet talks about 2.4km/h for one rotation per second, which is 0.69m/s. The "correction factor" would then be ~1.4. It's not easy to verify without a known-correct device. Currently, my devices is more or less in the ballpark with what these "live wind map" sides say (3.82m/s measured vs 4m/s on the map). |
I made measurements with a calibrated anemometer and I confirm that the speed measured with the coefficient 0.0055 is not good and is 2 times lower, the good value is close to 0.0111. However, I tried to calculate the multiplier with the formulas given in the links and I can't find 0.0111, whatever I do, I always find 0.0055, I will keep the reasoning applied in this comment as a formula, it is the only one in phase with the measurements. Problem with the current formula:
This result is 2 times lower than the measured wind with calibrated anemometer. If someone can explain to me what the problem is with this formula, I'd love to hear it. |
The wind speed calculation is just a rough estimate that calculates the rotations speed of the anemometer in m/s. Then applies a small factor to compensate for drag etc (calibration factor). To get a more accurate measurement I recommend calibrating against another anemometer or other wind speed measurement. But hey my goal was not to create a precise measurement but rather something that can be used in home automation (ex. Retract my awning when the wind speed is over some threshold). The position of my anemometer is not optimal either (from a metrology perspective). |
It's seems that your friction factor is approx 2. |
@mkuoppa @nliaudat Did you see a problem with my approach from this comment #6 (comment) ? |
You missed the friction factor or unknown correction factor : look at : https://www.mdpi.com/2411-9660/2/3/21 |
No need for the friction factor because the calculation is based on the manufacturer's calibration which indicates that at 2.4km/h, the switch closes 1 time per second. |
I made more precise measurements and after changing the measurement platform to For 60 seconds, at 2.4Km/h, we have 120 (not 60) pulses/minutes.
We end up with the same value calculated with the other method. 2 different calculation methods and a measurement made with an anemometer confirms the value of 0.005555 of the multiplier. I don't know why you need a multiplier of 0.011111 but here are some tips to make sure everything is ok:
I have some wind sensor related changes to commit to shortly but now I'll close this ticket. |
According to the datasheet one pulse per second corresponds with 2.4 km/h, which is 0.6666 m/s. For a update interval of 60s, I would think the multiplier would have to be 0.01111. The multiplier in weatherstation.yaml is set to 0.00555, which is about half that value, and I'm not sure I fully understand this difference.
The text was updated successfully, but these errors were encountered: