Effects of grill patterns on fan performance/noise (2011)
pugetsystems.com
pugetsystems.com
> Always look at the date when you read a hardware article. Some of the content in this article is most likely out of date, as it was written on September 19, 2011.
Not only do they have a date on the article (and many posts in recent years simply don't), but they draw your attention to it because it's long ago.
It's such a small but important detail. Instantly increases my trust for the company.
Does the change and differentiation in fan blade design have implications for grill interference noise with regards to this data? Do fans that are optimized for flow versus those for pressure behave the same? Do 80mm, 120mm, and 140mm all have the same grill noise characteristics?
I'd gladly pay $10 more for a PC case with a less noisy grill, but I can't find any that has this, not even ones that are advertised as "silent".
Reminds me of the time some Rust advocates insisted 2016 was an era before programmers were aware of the concepts of abstraction and separation of concerns:
Responses defend it on the grounds that it was a long time ago, i.e. 2016.
Where's the straw man?
>I don't see anyone insisting on that, either.
Okay, I'm really lost -- if they weren't disputing that my expectations were too high, then their comments ("it was way back in 2016, man!") were not responsive at all. Is that really the pillar you want to lean on?
In any case, let's review:
Steve Klabnik dismissing my criticism because the library is abandoned (as if that's a defense of a 2016 library not having abstraction):
https://news.ycombinator.com/item?id=18943056
User cetra dismissing my points because the library "had not been updated" in a number of years (as if you can't expect a 2016 library to have to proper abstraction until it gets updates):
https://news.ycombinator.com/item?id=18943056
fpgaminer dismissing my points because "Static, perfect code is rare" (as if failure to abstract irrelevant details is okay because no one gets the code perfect with no need to ever change):
https://news.ycombinator.com/item?id=19109529
kaoD insisting it was a dark age of rust, justifying the poor abstraction:
https://news.ycombinator.com/item?id=19110116
Are we looking at the same links?
The closest might be kaoD, who says:
> I'm sure they were more concerned with making the code work, making it secure, etc.
i.e. proper abstraction was not their priority at that time.
I think you are reading into these comments and finding meaning that doesn't exist.
Edit: So, yes, I agree that Rust devs knew about a abstraction. When the replies tell me that, they’re not disagreeing with anything I’ve said. My point is that it therefore follows that it was a reasonable expectation to have of the code, that it obeys abstraction. They were giving excuses for why it might not have kept up with eg newly discovered bugs, but not why it would fail to get such basic stuff right … besides, of course, it being the dark ages of 2016.
> Rust 1.0 was just released and the ecosystem was mostly maturing at that point. You're talking about version 0.2.36 of a library that had been in development for less than two years during a quite tempestuous time in Rust.
It's not something they would only figure out after fixing the thousandth bug.
On topic: This article was written by an SI (system integrator). 2011 is ancient history as far as PC hardware goes. Eg today's fans are a lot more efficient at the same price point and most enthusiasts need a lot more static pressure for radiators.
But it is for most of the other articles this site publishes about consumer computer hardware, like the two that were published surrounding this one ([1], [2]). This article just happens to be an exception.
[1]: https://www.pugetsystems.com/labs/articles/Product-Qualifica...
[2]: https://www.pugetsystems.com/labs/articles/Product-Qualifica...
Blame Google. It favors the newest content, regardless of quality.
Lots of valuable information on the web is just not searchable on Google, even with exact phrasing.
Shakespeare is next.
On that point, I feel everyone's collective pain on the situation with open offices. I don't have the power to avoid them, so the best I can do is advocate for getting the signal-to-noise problem solved right.
One evening, I was sitting alone in the eating area of a very high end office, and noticed a whooshing sound coming from the top edge of the room. I thought it was maybe some air vent, but there was no wind outside. I stuck my phone camera up behind the front lip of a shelf and saw a set of speakers. They were playing something close to brown noise!
And, I learned about sound masking [1]. So, apparently there's two ends to be avoided, in the signal-to-noise problem!
1. Partitions around workspaces create a modest barrier effect, not so much realizable for your nearest neighbors but those more distant. No one installs partitions up to 48" or 52" but you have to at least break line of sight to the noisemaker to realize any improvement. This reduces signal.
2. Acoustically absorptive ceilings avoid the overhead reflection that would be the next cue to an occupant. The partition comes first, but this is second. Another signal reducer.
3. Background noise, whether a consistent HVAC system or sound masking system raises the noise floor of the environment. We have a pretty good sense of what level is acceptable to most people, but there will always be those with sensitivities. The noise is usually pink noise with some EQ to sound like HVAC air distribution. Unfortunately there has to be some treble in the noise signal to reduce the consonants of speech, which can be more annoying.
You won't make nearby co-workers inaudible, but the hope is that those 20 ft or so further will be less problematic. For inaudibility you have to get S/N to around -10 dB, that's a noise floor of 10 dB higher than the source, which is only realizable with walls at least to the ceiling.
I remember building this room with walls lined with 1 foot thick Helmholtz resonators tuned to a range of frequencies. The same with portions of the ceiling. And, of course, there were broken-up and angled surfaces to help diffuse sound, avoid creating standing waves and stimulation of room modes. Back then I even wrote a bunch of software to run acoustics analysis and evaluate room characteristics based on a range of parameters, including construction materials, etc.
Here are a couple of screen shots:
https://i.imgur.com/sXQmc8d.png
https://i.imgur.com/q0kHVbQ.png
Since then I have always been very aware of acoustics in every environment. Restaurants are particularly horrendous. Nearly all of them seem to be reverberation chambers designed to destroy sound. Most would benefit greatly by deploying a few very simple tools to control sound and allow patrons to have conversations in a reasonable environment.
Most people don't put their ear next to a case fan to see if it's annoying or not. You experience its sound from several feet away, and the measurement should reflect that.
Practically speaking no you wouldn't want to factor the turbulence generated at the microphone because the user of the computer wouldn't be hearing that.
There is a lot of information about airflow around cylinders. Eg [1]. The top left diagram should be the one that applies with small diameters and the kind of airflow rates in a PC fan.
I would guess that all the other shapes have micro-scale sharp edges that leave vortexes which both slow the flow down and make noise.
Like, even on cut or stamped grills, how much could performance be improved by e.g. sandblasting the finished piece from one or both sides and taking down the edges a bit?
That tells me if you were to get a 1000x really powerful fan, then the grille would start giving turbulent flow, and might no longer perform the best.
Page with lots of details: http://labman.phys.utk.edu/phys221core/modules/m8/turbulence....
I even remember, when in mac clones used ultra-high-speed coolers, which now used only in rack devices.
And yes, ultra-high-speed coolers, has much higher speed and make turbulence.
That said, my current PC has plastic "angled slats" at the back (outlet) and a honeycomb and mesh (filter) at the front, so it could be quieter. I'll keep it in mind if I ever buy a new one. I believe the wire one was the most common on older PCs (90's / 2000's).
"They took a high-performance business jet, added extra drag, and ran the engines in reverse to simulate a flying manhole cover."
Wind tunnels use honeycomb flow straighteners to take care of this.
A full blown analysis might use computational aeroacoustics software that can calculate the noise generated from solid geometry in a given flow. This field has advanced considerably since when the article was published due to newer methods like LBM. It'd be beyond the scope of journalism like this, but it is no doubt done by companies with resources like Apple.
I also had to strap a full CRT PC to a table that rotated through various axies to measure the EMI/RFI coming from the complete setup while it was running and every now and then the straps would slip and the whole thing would crash down and make a big bang and a mess. Good times.
Why was the "test finger" so expensive? What was it made of?
Why not just use a $3 wooden dowel rod from Home Depot?
Test fingers and the like are very expensive because of the serious precision they have to be machined to, and are made of expensive materials to minimize dimensional changes the result from environmental variations and use.
But also keep in mind that test fingers are used for more than just seeing if it can poke through a screen.
Way way way back when I worked in the auto supplier industry, we needed to test to make sure the auto-up windows and auto-closing minivan doors would actually not cut your finger/hand/leg off. We always used pencils as a first try. They break a lot easier than a dowel rod of the same diameter. If we were happy with the results, we'd get out the test finger. If it looked a little iffy, we'd suggest that the engineers should use their own fingers if they were really confident in their work.
[0] https://knowledge.bsigroup.com/products/standard-test-finger...
[1] https://www.amazon.co.uk/GOWE-IEC61032-IEC60529-Probe-Finger...
Technically it's a 2530% increase, but that's silly because it doesn't correspond to how people experience sound.
If the unguarded fan is at 35.5 dBa, and the turbine guard is at 50.2 dBa, the delta is 14.7 dB. This is the same increase in perceived noise as an unguarded 60 dBa fan and a guard that raised the noise level to 74.7 dBa, not a relative difference of 41% and 24.5%.
Matthias has an interesting video that is tangentially related talking about the distance of a fan to a window and air flow. While watching I was wondering how this interacts with PC case fans and if they are losing a lot of performance by being directly against the case.
PC fans are surprisingly dangerous.
So much so, that Dell and HP are forced to put a little triangle "warning!! fan!" sticker next to the fan in a laptop.
Okay, maybe not. In the case of the blower fans, you are more of a danger to the fan than it is to you. Touching the thin blades while operating is often enough to snap some or all of them off the hub.
On normal axial fans, DIY PC market fans are often underpowered, at 0.1-0.2A at 12 volts. This isn't a lot of power, and the rotation speed is low and as you have found, not very dangerous.
However, outside of the DIY PC market, even in any PSU, fans are often rated at 0.3 A, and the average graphics card fan is rated 0.6 A. Once you get into the several watts territory, the fan is capable of operating at 3000+ RPM. On OEM PCs, 80-90mm CPU fans are rated at like 0.9-2.5A. In servers, fans up to 4A are common. These operate at 10,000 RPM or more.
The reason you do not hear about this is because most systems oversize the fan and run it at a low speed to reduce noise, but keep that machine that is choking in dust running at full speed so the factory floor doesn't halt or something. I have seen Dells in these kinds of situations where nobody will clean the PC in 20 years, but it has to, and does, keep trucking. These kinds of fans produce robot vacuum cleaner territory of static pressure, up to many inches of water column at 250 CFM.
These kinds of fans are extremely dangerous. China/AliExpress calls them "high speed violence fans" for a reason. The motor hubs are usually made of steel in higher powered ones, and the stall torque is high. The blades have a swept, sharpened tip made of glass fiber reinforced plastic, and the blade assembly carries several hundred grams to kilograms of inertial force. These fans will mangle fingers. When I was very young and inexperienced, [warning graphic], I caught my finger on the sharp tip of a 90mm fan from a Dell while it was spinning down. In a separate incident, I also managed to touch a Intel stock cooler on full speed, and the blade got caught under my fingernail.
Always use a suitable fan guard or safety equipment when testing cooling fans or working around them. The more powerful fans will take off chunks of your fingers, and even a tame seeming fan can quickly speed up to dangerous power levels without notice when the system controller senses a case open, fan failure, or high ambient situation.
I might be misreading this. Are you saying you can stop a running box fan, powered on, force being applied to the impeller by the electric motor, with your pinky?
I calculated that a 20" box, 1000rpm fan blade moves at around 50 mph. Those large ones might hit pretty hard but will not cause serious injury.
I think he's talking about a small 8 inch desktop model, going maybe 500rpm - that's only 7mph.
[0]: https://youtube.com/watch?v=tMLIzedVvH8&t=1031 (timestamp included)
https://www.ingentaconnect.com/content/ince/ncej/2013/000000...
https://www.sciencedirect.com/science/article/abs/pii/S00224...
https://www.sciencedirect.com/science/article/abs/pii/S00224...
They place specially shaped "obstructors" in fan ducts which create destructive interference with some of the prominent noise tones.
One way that such synchronization can occur is by the blades passing the holes, and I suppose that the high noise of the 'turbine' grill is caused or exacerbated by the blades alternately aligning with the holes and the ribs. I recently learned that tire treads are made with a pseudo-randomized block size, as with a same size all around the sounds each makes as it contacts the road would be periodic, producing a siren-like sound with a definite pitch.
The swirl pattern presumably mitigates this effect by having little variation in the overall blade/rib alignment through one revolution. There are also tire treads like this.
The difficulties of using interference in reducing fan noise are that it becomes less effective the whiter the noise is, and that destructive interference somewhere usually creates constructive interference elsewhere else.
This PC case fan (https://noctua.at/en/noctua_anc_project) is designed for ANC. It generates the inverted signal inside the fan.
I’d predict the most open to Have the least resistance, which would give the least noise.
The author did not compare the grills at specific airflows, but the information is still useful.
Measuring something as that nobody even thinks about or realizes is there, and finding an actual big difference in performance is always a delightful discovery to me.
20 years ago where known, that place instead of grille deflector tube (like lens hood), will make cooler significantly quieter, just because tube absorb some sound and vibrations. I don't know, why this variant does not shown in this research.
Debris are usually covered by a foam filter in front of the fans (if at all). I’ll usually take that off though and just clean it every once in a while.
My young nephew shoves his hand it in all the time for fun with zero harm.
It's very size/shape/rpm dependent.
https://en.wikipedia.org/wiki/Coand%C4%83_effect
Edit: I see the tester used an anemometer, which measures just the air moving THROUGH the anemometer.
If the exhaust is smaller than the intake, then air will move at a higher speed through the exhaust. Thus the anemometer will show a higher reading.
Maybe the swirl will also have an effect, depending on whether the fan blades and anemometer blades rotate in the same or opposite directions.
Here, as with the anemometer, you are not measuring the total mass flow; what's being measured is the velocity of part of that flow, and you are intercepting more of that flow on the outflow side. If you were to measure and integrate the velocity over two hemispheres centered on the fan and divided by the plane of the blades, with a barrier in that plane to prevent recirculation, and calculate the mass flow from that (you can assume constant density as the pressure change is tiny), you will find that the total outflow downstream equals the total inflow upstream.†
† To actually do this experiment, you will need a sensitive anemometer which measures over a small area and does not unduly interfere with the flow, such as a hot-wire probe type. There may be additional difficulties in averaging turbulence.