#fanspeed — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #fanspeed, aggregated by home.social.
-
@tedyapo Yeah, so Google Gemini. The code it gave me was almost right. I used it as an outline to understand how (extended) Kalman filters work and how to apply them to this problem, and steered me in pretty much the right direction. Best experience I've had with an LLM. It probably would have taken me longer without it, even though I did spend two whole days on it.
But there are glitches, and I don't know how to tune it to be smoother.
🧵 17/N
-
@poleguy @attie @rrmutt @tedyapo The Jupyter notebook is on Github here. It's not quality code, it's hacked together.
https://github.com/kbob/ESP32_Fan_Analysis/blob/main/analyze/kalman.ipynb
🧵 16/N
-
@tedyapo nicely sent me a Google Gemini outline of a Kalman filter to measure fan speed. I used it as an excuse to learn about Kalman filters. I carefully transcribed it into Python, and now I've got a not-quite-working implementation. Here are the graphs, same data as upthread in 🧵4 and 🧵5.
Graphs 1-3 here, 4-5 in the next post.
🧵 14/N
-
@tedyapo @poleguy @attie @rrmutt (This project is on my travel laptop, so I'm only working on it sporadically. D'oh.)
I did the CIC thing. I created samples where pulse present = 1 and absent = 0. Integrated, decimated, combed. The problem is that that's a DC signal. Integrators overflow on DC. I want to measure the DC bias (pulse density), so I can't just decay the integrators.
Suggestions welcome. (cont'd)
🧵 12/N
-
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.
-
Asus ROG Ally overheating can kill your microSD card reader (and cards), so Asus plans to crank up the fan speeds a bit, which could make the handheld noisier, but safter to use. Affected users can request repairs. https://www.tomshardware.com/news/asus-admits-rog-ally-microsd-card-reader-may-malfunction
-
Asus ROG Ally overheating can kill your microSD card reader (and cards), so Asus plans to crank up the fan speeds a bit, which could make the handheld noisier, but safter to use. Affected users can request repairs. https://www.tomshardware.com/news/asus-admits-rog-ally-microsd-card-reader-may-malfunction
-
Asus ROG Ally overheating can kill your microSD card reader (and cards), so Asus plans to crank up the fan speeds a bit, which could make the handheld noisier, but safter to use. Affected users can request repairs. https://www.tomshardware.com/news/asus-admits-rog-ally-microsd-card-reader-may-malfunction
-
Asus ROG Ally overheating can kill your microSD card reader (and cards), so Asus plans to crank up the fan speeds a bit, which could make the handheld noisier, but safter to use. Affected users can request repairs. https://www.tomshardware.com/news/asus-admits-rog-ally-microsd-card-reader-may-malfunction
-
Asus ROG Ally overheating can kill your microSD card reader (and cards), so Asus plans to crank up the fan speeds a bit, which could make the handheld noisier, but safter to use. Affected users can request repairs. https://www.tomshardware.com/news/asus-admits-rog-ally-microsd-card-reader-may-malfunction
-
Unser Control Center bietet verschiedene Lüftergeschwindigkeiten und -profile. Hier sieht man die Geschwindigkeitsunterschiede und die Temperaturschwelle, ab welcher der Lüfter komplett stoppt!
Mehr zum TUXEDO Control Center:
https://www.tuxedocomputers.com/de/Infos/News/Alles-unter-Kontrolle-mit-dem-TUXEDO-Control-Center_1.tuxedo
#Laptop #FanSpeed #Tuning -
Our Control Center offers various fan speed & profiles. See the differences in speed and the temperature treshold for the fan to stop running at all!
More on the TUXEDO Control Center:
https://www.tuxedocomputers.com/en/Infos/News/Everything-under-control-with-the-TUXEDO-Control-Center.tuxedo
#Laptop #FanSpeed #Tuning