#yourbiggestfan — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #yourbiggestfan, aggregated by home.social.
-
I pushed my firmware and my analysis notebook to Github.
The repository is here.
https://github.com/kbob/ESP32_Fan_AnalysisThe Jupyter notebook that created the upthread graphs is here.
https://github.com/kbob/ESP32_Fan_Analysis/blob/bb9b301058848362991cbcb2453ec73eb7901afd/src/fan%20analysis.ipynb -
Let's find those bands and see what's up. I analyzed both the half speed and full speed runs, as they both show the banding clearly.
The space between bands is 813-824 clocks, or 97-98 KHz. I can only guess why they're different.
If I understand Nyquist correctly, I can down sample my traces to 200 KHz and not lose any resolution.
-
My next hypothesis is that the tach signal is not a direct measurement of some analog signal but is generated by the fan controller and is quantized by the controller's clock.
So let's switch from looking at RPM to looking at intervals. This graph shows the same data, but the Y axis is the interval between edges, measured in ESP32 APB clocks (80 MHz). There are two pulses per fan revolution, so I've colored the two pulses differently.
-
I re-plotted the half speed run, calculating speed using the intervals between rising edges and the intervals between falling edges. These plots show both, all in one color. (Maybe I should have colorized them again.)
The small bands gaps are gone. There are still bands, but they're evenly spaced.
-
So what's going on with that banding? I calculated the time difference between every two tach edges and plotted them all together.
Hypothesis: There are four edges per rotation. Maybe the edges are not spaced exactly 90° apart.
Here, I've colored the bands for the constant speed runs. You can see that the rising edges are in one set of bands and the falling edges are in the others. So that's solved.