• 27.04.2024, 09:23
  • Registrieren
  • Anmelden
  • Sie sind nicht angemeldet.

 

Lieber Besucher, herzlich willkommen bei: Aqua Computer Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.

Aquasuite: Controlling your Pumps/Fans with virtual sensors and automatic condition based curve switching.

Dienstag, 16. Januar 2024, 07:57

This is a virtual sensor I came up with to allow me to run two or more curves on the same profile for a fan or pump header. Within the sensor I can configure triggers so that the fan/pump will switch curves when system conditions are met.



As im not as versed in posting to this forum here is a reddit post linked with the guide.
https://www.reddit.com/r/watercooling/co…s_with_virtual/

CPU/GPU load virtual sensors for more data driven load values.

CPU

GPU

https://pastebin.com/ASTEEz3S
Pump controller V4.1 Virtual Sensor XML code for importing into auquasuite

It's constantly evolving and it has changed already since typing this... mostly just playing with filters lol.
Enjoy ! Hopefully some of you can find a use or share with me what you would change/improve.

Dienstag, 16. Januar 2024, 14:30

WOW!

That looks like it was a lot of fun to do... but why? Rube Goldberg comes to mind.

There is little reason to vary pump speed/coolant velocity once a reasonable value is attained (2-4 l/m yielding the quietest performance).

Fans are your primary control, and they only impact coolant flowing through the radiator.
The main interest is the Δt between the outlet of the radiator and room ambient, throwing in a myriad other sensors only serves to confuse the result.

Applicable adages being "Just because you can, doesn't mean you should" and "KISS".

Remayz

Senior Member

Dienstag, 16. Januar 2024, 19:22

just to play around? ^^

the first thing that came to my mind when looking at it is that Aquasuite already has automatic profile switching based off whatever you want.

Dienstag, 16. Januar 2024, 21:09

This is interesting. It kind of reminds me of the Intercooler Thermal Regulator. That did turn out to have some significant issues, but those aside, it was another example of complex sensor data processing that can be done in Aquasuite.

Dienstag, 16. Januar 2024, 21:46

It was quite fun. And funny enough I did make a Rube Goldberg machine years ago.

The main reason besides experimentation was to develop a way of increasing the pump speed when it’s needed most and only then. Increasing flow rate will move more heat from components to the radiator. If the fans are maxed the only thing you can do is speed up the pump or lower ambient temp to gain additional cooling. In the case of fans it can be used to shut them off completely when delta T is a value you set for silent operation until load or temp increases. I currently don’t have a flow meter installed but am building a dual pump parallel x flow rad setup that will utilize two flow meter. Both before the manifold to ensure I can tune equal flowrates through the rads, should I decide to split the manifold through waterblocks of different resistance. Something like this allows me to take full advantage of the higher delta T of parallel rads while also minimizing restriction for all the QDC’s. It’s a custom case I’m building in solidworks for minimal footprint and ease of maintenance. It needed an overkill virtual sensor to go alongside. :D

Creating this sensor also seemed less daunting then setting up two or more profiles to switch back and forth on conditions. But I certainly could use this to drive outputs and switch profiles and achieve the same result. It is much easier to tune it all being integrated into a single virtual sensor, less confusing as well.

Remayz

Senior Member

Dienstag, 16. Januar 2024, 23:39

spoiler : increasing pump speed will do nothing for cooling.
it only helps if your flow is way too low and the water goes through the waterblock at a snail's pace.
but as soon as the waterblocks have enough flow to not "overheat", there's almost no effect with increasing pump speed. That minimum flow requirement changes from block to block, so there's no universal value.

just as an example, on my rig if i let the flow drop below 60l/h (~700 rpm), the GPU heats up drastically. but between 70 and the max i have of 240 L/h (2200 rpm, it's a DDC), the temperature drops by 1.5°C. basically nothing.
the only thing that influences heat disspation, unsurprisingly is the fans.
If shifting your pump speed gives you marge temperature gains, you have severe flow restrictions. Flowmeters will help you check that.

Mittwoch, 17. Januar 2024, 07:41

But there is a temperature change as a result of increased flow...

And that is the point of this. Not what you should or shouldn't do. Or that its so small it shouldn't matter. This is meant for those who want to squeeze every bit of cooling potential out of their loop, but only when they need it.
If that is your takeaway, you are missing the other configurations this sensor could be used for.
And if you just want a static pump and fan running off Delta T that's fine too.

Its not enough to say flowrate doesn't make a difference because even if that change is 1C or 5C its still there... If you have a target Delta, that 1C might mean something to someone.
Nor is it accurate to say their isn't a hot and cold side off the loop or that "water temps equalize" because my temps sensors all over the loop don't back that up. There most definitely is a hotter and a colder side, sure it might be under 1C most of the time, but if you have fans and a radiator the difference is there.

Too many people just repeat what they hear. Most people don't know that mixed metal loops are totally fine with todays coolants so long as you don't provide a direct metal to metal electrical connection of two metals with different electrical potential or bridge them with a conductor in addition to the coolant.
Its cheaper for manufacturers to say no aluminum than take the risk of someone screwing in a brass fitting to an aluminum rad or having copper touching a conductive surface with aluminum touching the same surface 20" away while both are immersed in a conductive coolant.
Brass fittings are installed in aluminum all the time, like a cars engine, however its typically a very small amount of the noble metal and a very large amount of the reactive metal so the electrical potential isn't great, and corrosion of the anode is very slow.

Rant over lol

This sensor was made for those who want maximin performance and are okay with the increased pump noise that comes with the curve switch.
They're not large values as we are far far from taking advantage of waters thermal properties with the temps we work with, but this is about performance optimization with a given system. Pushing what a homebuilt loop is capable of.


In the build I mentioned before, I am taking steps to optimize coolant paths, using larger tubing and fittings to minimize frictional losses before they split, which halves the flowrate, then flowrate is further divided by the number of coolant paths in the radiator. All tubing lengths for parallel runs will be equal.

If I have a flow of 220lph, that then splits and becomes (65lph split again lol) 110lph entering the rads, then 6.875lph passing through the rads before becoming 110lph again in the end-tank, and 220lph again when all combine in the manifold. (or stay at 110lph if I divide the manifold)
Flow meters and ball valves will allow me to equalize the parallel flow should I split the manifold. There will be water blocks on almost everything and about 8 QDC's, hence dual pumps and the virtual sensor to boost the pump when system conditions dictate its needed.

Its overkill AF and somehow I'm cramming it all in to the volume of a Mini ATX Case with movable maintenance features while keeping an airframe inspiration. Once the coolant is routed aluminum cover panels will be made to look like WW2 fighter aircraft skin complete with aircraft rivets.




2x 420mm rads and 1x 92mm rad, with option for external rad once done
Routing the coolant pipes and planning all the 3D printed cable guides to keep features is proving challenging lol... but I will make it work.
If machined or welded parts need to be made, that is no problem.

If that sounds crazy I asked chat GTP to write me a script to actuate USB relays to power solenoids valves, so I could have an aquasuite output trigger the process and divert coolant to an external rad only when needed lol. Obviously its kinda pointless when I could just switch profiles to turn on external radiator fans, but cool nonetheless.

Remayz

Senior Member

Mittwoch, 17. Januar 2024, 09:21

There is no temperature change at increased waterflow if you stay clear of that minimum limit. that was an extreme example running a pump at 60L/h to show at what threshold the waterblocks i use stop functionning well. if i drop it to 50L/h, the GPU temp under load rises by like 10°C.
I run the pump typically around 120L/h (~50%PWM) and between this and full speed there's basically no temperature difference.
As long as you are well clear of that minimum flow requirement from your blocks, the only thing influencing component temperature is the fans.
Oh and BTW i'm not repeating what i heard, that's what i tested for myself :p

Yes there is a hot and cold side on a loop obviously, but flow and delta T equalize each other on the formula for calculating dissipated energy. If you increase your pump flow, you decrease the delta T, and that results in a net gain of 0 in dissipated energy through your rads. the only thing giving you any gain is what is making the water to ambient delta T to drop, which is the fans.
That's why if you care about efficiency, there's basically only one virtual sensor that matters and it's just a substraction :p and for optimization, you can switch between several fan curves for various amounts of cooling depending on what you want.. less noise, more cooling.. etc.
Also, increasing pipe diameter doesn't reduce flowrate, it decreases coolant linear speed. lower speed with bigger diameter = same flow, with less friction losses as you said.

Donnerstag, 18. Januar 2024, 10:34

Nice work! Instead of walking the same road as everyone else it is far better to blaze your own way and leave a trail for others to follow. :thumbsup:

Remayz

Senior Member

Donnerstag, 18. Januar 2024, 11:30

Basically don't worry about the nitpicking yes ^^ do what you want. it's not called "CUSTOM" loop for nothing !

Donnerstag, 18. Januar 2024, 17:43

Sorry that was confusing wording. Flow rate isn't reduced. A flow of 220lph split through two tubes will still have a total flow off 220lph, but the flow through each of the two tubes after the split will be 110lph. And yes the velocity does decrease with larger less restrictive tubing compared to the same flow through smaller tubing.


But how does increasing flow rate not contribute to additional cooling?

Technically there is a Delta T for the waterblocks-coolant and a Delta T for the coolant-ambient air.


Q=mcDT
The rate at which heat is transferred is directly related to the mass flow rate, by increasing flow you increase heat transfer. Flow rate is directly related to the total amount of heat transfer occurring. Its non proportional, as Delta T is decreasing, doubling flow isn't gonna double Q.

At a constant CPU load there is a constant amount of heat energy being dumped in to the loop (Q)
So by increasing flow, Delta T does decrease in regards to the waterblock-coolant to maintain that constant (Q). Which is good! Cooler water in the block can absorb more heat energy and has a higher flow to move that additional absorbed heat.
Its confusing because that formula represents the mass flowrate, given that we have a cap to the total liquid volume of coolant in the system, higher flowrate = faster mass of water circulating.


In regards to the radiator.

Q=mcDT

We are decreasing delta T from the moment water enters to when it exits in order to cool it, so yes the higher this number, the more efficient our rad can be.
But with a constant flow, the fact Delta T is decreasing does not mean flow is increasing to maintain Q or that the specific heat of water is changing significantly enough to matter. In this case Q is changing as the amount energy is leaving the system is related to how fast the mass of coolant is moving and how fast delta T is decreasing. Which is where fans come in. (all of this is assuming a constant airflow)

So, by increasing the mass flow of water though the radiator, we are physically moving more heat through the rad, meaning more energy is removed compared to a lower flowrate.
It by no means cancels each other out. Even if delta T is .0001C, the more we increase flow, the more heat energy can be transferred up until our pump maxes out.


Among a myriad of other factors affecting water cooling that aren't accounted for.
  • Increased pump speed means more turbulence which leads to better absorption and shedding of heat as opposed to laminar flow which has a shield of water on the edges of the coolant path blocking most of the water from heat. This is a big factor in heat transfer and good blocks are designed to induce turbulence, but higher flow usually means more turbulence.
  • Increased pump speeds or bigger pumps will add more of their own heat energy to the loop (maybe 5-20W depending on size and speed)
  • Technically as the fluid heats up its viscosity decreases leading to better flow characteristics.
  • What speed your fans are running, and how much they vary with changes in Delta T.
  • Specific heat capacity of the waterblocks themselves
  • Restrictive components
Overall it isn't a lot in our systems, because the amount of heat energy and temp deltas aren't large numbers.
It is also completely dependent on the individual setup and ambient temperature, you might have .5C temp changes you write off as insignificant, but someone else might see 5C+ even with a good flowrate to begin with.




In my case, when the fans are running at 100% with a high system load, and the pump speed increases up to 100%, the rate at which Delta T is increasing is dramatically slowed as the pump speeds up. I know I currently need more radiator SA, but increasing flow is definitely increasing the amount of heat removed from the loop.


Actually typing this is making me wonder if I should be running my pump controller off the first Delta T, under stress test load that Delta goes almost immediately to 35C while the Radiator Delta T climbs about 2C over a slightly longer period as the water absorbs thermal energy. Typically is sits ~.5C-2C at idle compared to Radiator Delta T.
By bumping pump speed, the rate at which that 2C change occurs will increase. While that might mean lower fan speeds initially, they are much quieter so I prefer pump speeds increasing secondary to fans when noise is factored in. But it might be worth a test...




But anyway this is my understanding of how it works. Please let me know if that is incorrect and why.

ChatGPT has entered the chat

Freitag, 19. Januar 2024, 02:32

Q=mcDT
The rate at which heat is transferred is directly related to the mass flow rate, by increasing flow you increase heat transfer. Flow rate is directly related to the total amount of heat transfer occurring. Its non proportional, as Delta T is decreasing, doubling flow isn't gonna double Q.
I am by no means an expert on this, but I typed this formula into ChatGPT and got back the following.

The equation Q=mcΔT is the formula for calculating heat transfer, where:
Q represents the amount of heat transferred.
m is the mass of the substance undergoing the temperature change.
c is the specific heat capacity of the substance.
ΔT is the change in temperature.

The formula is based on the principle that the amount of heat transferred (Q) is equal to the product of the mass (m), the specific heat capacity (c), and the change in temperature (ΔT).
Q is typically measured in joules (J).
m is measured in kilograms (kg).
c is measured in joules per kilogram per degree Celsius (J/(kg·°C)).
ΔT is the change in temperature, measured in degrees Celsius (°C) or Kelvin (K).


It does not say anything about “mass flow rate”, it just says m is the mass. There is no mention of flow rate.. I followed up with the question, “Does flow rate affect the rate of heat transfer in a computer cooling loop?” The response was:

Yes, the flow rate can affect the rate of heat transfer in a computer cooling loop. In a computer cooling system, such as a liquid cooling setup, the flow rate of the coolant plays a role in how efficiently heat is transferred away from the components, such as the CPU or GPU. Here are some ways in which flow rate can impact heat transfer in a computer cooling loop:
  • Increased Heat Dissipation: A higher flow rate can lead to more efficient heat dissipation. It ensures that the coolant circulates quickly through the components, carrying away heat and preventing hotspots
  • Improved Convective Heat Transfer: Higher flow rates enhance convective heat transfer. This means that the coolant absorbs heat from the components more effectively as it flows over or around them.
  • Reduced Residence Time: While increased flow rates can improve convective heat transfer, it also reduces the residence time of the coolant in contact with the heat source. Striking the right balance is essential to ensure that there is sufficient time for effective heat exchange.
  • Coolant Velocity: Higher flow rates result in increased coolant velocity. This can contribute to better mixing and prevent the formation of boundary layers that might impede heat transfer.
  • Temperature Uniformity: Proper flow rate helps in maintaining temperature uniformity across the cooling loop. It prevents certain areas from becoming excessively hot and contributes to overall system stability. .
It's worth noting that there can be diminishing returns beyond a certain flow rate. Excessive flow rates may not significantly improve heat transfer and could lead to increased energy consumption due to the pump working harder.
In summary, flow rate is a critical parameter in the effectiveness of a computer cooling loop. Achieving an optimal flow rate requires consideration of the specific components, the cooling system design, and the characteristics of the coolant to ensure efficient heat transfer and overall system performance.

So it seems that flow rate can affect the rate of heat transfer, but indirectly due to secondary effects, and above a certain flow rate, increasing it further reaps diminishing returns. Like Remayz, I have compared temps at various flow rates and found that there is a low threshold below which temps start increasing, in my case around 60l/hr. Above that, temps level off. Further increasing flow rate until the pump is at 100% did not make any difference in temps.

PvF

Full Member

Freitag, 19. Januar 2024, 05:42

It does not say anything about “mass flow rate”,


What you need is the Formular for the "heat flow" = "Power".
This Formular is similar to Q=mcDT but with a dot above the "Q" and the "m" to indicate this is per "time" - e.g. per second (1J/s = 1W)
c for water is 4187J/(kg*K) - with 35% Glycol c is approximately 3800 J/(kg*K)
The good thing is that 1kg of water is equal to 1litre (SI-System rocks :thumbsup: )

for example with 80l/h and a difference of 2K (e.g. in/out Radiator):
Power = 0,022l/s * 4187J/(kg*K) * 2K = 184,23 J/s or W

This Formular is also used internal to calculate the Power within the high flow Next (this is not 100% correct, because "double protect ultra" ≠ 100% Water)
"c" for double protect ultra is for sure somewhat between 4187J/(kg*K) and 3800 J/(kg*K), but with very low flow rates, low delta T and temperature Sensors with a tolerance of ±0,5K this is only an approximate estimate anyway

Freitag, 19. Januar 2024, 08:27

What you need is the Formular for the "heat flow" = "Power".
This Formular is similar to Q=mcDT but with a dot above the "Q" and the "m" to indicate this is per "time" - e.g. per second (1J/s = 1W)
Sorry that was my error in typing.It’s been a while since I took a physics or chemistry class lol, It’s the formula for cooling capacity.
But yes it is supposed to be
heat = mass flow * specific heat capacity * temperature differencekW = (kg/s)x(kJ/kg/°C)x( °C)
As you said we can convert units as needed just so they are ones we are more familiar with for use with watercooled computer systems.

W=(lph) x (4.18KJ/Kg K@35C) x (DT) I use an aquasuite sensor that someone else created to calculate my cooling capacity with a virtual sensor.https://www.reddit.com/r/watercooling/s/Cp1UYwU24D
I am by no means an expert on this, but I typed this formula into ChatGPT and got back the following.
Interesting, I myself have used chat GPT to try to understand flow/pressure/volume and their relationships in coolant pathways
I believe the diminishing returns it is referring too, is due mostly to pump power, and oversizing your pump. Too powerful a pump will dump excess unwanted heat that takes more energy to cool. Ideally we don’t want the pump adding significantly to what it’s working to counter so I agree there is a balance. I don’t believe the pumps we are running are capable of tipping that balance however. Maybe some of the top line eheim pumps but even that might be a stretch.



I suppose aquasuite has a great logging feature
Time to do some tests and log.
  • Delta T waterblock-coolant
  • Delta T coolant-ambient
  • System Wattage
  • Pump speed
  • Flow rate
  • Fans set at a constant 100% so my radiator will be performing at its max given ambient temp


Since its so heavily dependent on your radiator surface area and fan's CFM(CMM).


What Delta T are you getting at your radiator?
edit* stupid question lol


What Delta T are you getting at system Idle? and under system Load?
Since the temp plays such a large factor for efficiency i'm curious what number you are seeing.

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »DeathToTheWind« (19. Januar 2024, 16:08)

Remayz

Senior Member

Freitag, 19. Januar 2024, 11:17

only the D5 is watercooled and still, it dumps such minute amounts of heat in the water that you can basically disregard it.
The temperature sensors are so imprecise anyway you'll probably have bigger measurement errors than pump heat "offsets".
If you use DDC pumps for space savings, they are air cooled so it won't trouble the measures during your tests.

What ChatGPT told you about flow rates influencing heat transfer is correct but in our case with computer watercooling, the energies involved are so low it makes virtually no difference as you saw.

Freitag, 19. Januar 2024, 16:28

only the D5 is watercooled and still, it dumps such minute amounts of heat in the water that you can basically disregard it.
The temperature sensors are so imprecise anyway you'll probably have bigger measurement errors than pump heat "offsets".
If you use DDC pumps for space savings, they are air cooled so it won't trouble the measures during your tests.

What ChatGPT told you about flow rates influencing heat transfer is correct but in our case with computer watercooling, the energies involved are so low it makes virtually no difference as you saw.


I use D5's so good to know.

I also use 4 temp sensors and will be upping that to 8. I'm less worried about reporting inaccuracies with that many.

I also found that the Koolance ones seem to be the most accurate as all of their probes, including the inline ones, have temp probes protruding into the coolant path, as opposed to just buried in the wall.

Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »DeathToTheWind« (19. Januar 2024, 16:35)

Freitag, 19. Januar 2024, 17:00

Just out of curiosity, I monitored my temperatures in desktop mode without any interaction on my part, and the result was as expected.
With a normal pump setting of 30% and ~100 l/h, the CPU temperature was 37.75 °C, of course with repeated increases because something in the background needed CPU power.

With a pump output of 100% and ~180 l/h the result was the same.

My water temperature under load is ~2.5 °C above room temperature.
The only significant changes I see with this type of load are when the room temperature changes. Then the water temperature fluctuates.

However, when I increase the 3 fans of the upper 420 radiator from 490 to 740 RPM, the CPU temperature drops from 37.75 °C to 37.38 °C.
Since I am a friend of quiet computers, I did not turn up the other 3 radiators :-)

I monitored the temperatures for 10 minutes with each change.
I can't provide a result under full load, this is just a waste of energy for me and there is no full load in my usage scenario, neither my browser, nor my slicer or Solid Edge are that power-hungry, even World of Warcraft is rather tame :-)

By the way, my CPU is the Ryzen 7 7700.

I think creating a completely exaggerated software sensor is completely justified if you enjoy it, but I find the claim that the pump control makes even a remotely significant difference in CPU temperature rather strange.
Es gibt keinen Ausweg, den ein Mensch nicht beschreitet, um die tatsächliche Arbeit des Denkens zu vermeiden.
Thomas Alva Edison (1847-1931), amerik. Erfinder

Remayz

Senior Member

Freitag, 19. Januar 2024, 18:30

I also use 4 temp sensors and will be upping that to 8. I'm less worried about reporting inaccuracies with that many.

I also found that the Koolance ones seem to be the most accurate as all of their probes, including the inline ones, have temp probes protruding into the coolant path, as opposed to just buried in the wall.
The problem is those 8 are probably not in the same places in the loop, so you never know which ones read correct :p
NTC thermistors are notoriously inacurrate, so you'll have to cheat a bit with offsets in Aquasuite, and even then, the response will not always match between sensors. for a same temperature change, some will be reading higher, some will be lower.

On my loop, electrical power reading from CPU + GPU match the calculated heat output under load, but it's like 50W off at idle because of inaccuracy of those sensors.
You can get good matches but you'll have to painstakingly characterize each sensor and pair them to have a somewhat useable before rads/after rads temps for example.

For my loop, i tested the NTC i have against my multimeter thermocouple and adjusted some offsets to be roughly in the ballpark.
Like the room ambient temperature sensor was a whole degree off. it's huge in terms of accuracy, but eh.. it only caused the water and the components) to be 1°C warmer

At least the AC controllers are very stable so you will have very precise and stable readings of our uncalibrated sensors :p

Freitag, 19. Januar 2024, 22:03

What you need is the Formula for the "heat flow" = "Power".
This Formula is similar to Q=mcDT but with a dot above the "Q" and the "m" to indicate this is per "time" - e.g. per second (1J/s = 1W)
Thank you for clarifying this.
[/size]W=(lph) x (4.18KJ/Kg K@35C) x (DT) I use an aquasuite sensor that someone else created to calculate my cooling capacity with a virtual sensor.https://www.reddit.com/r/watercooling/s/Cp1UYwU24D
Thanks for posting this link. I have encountered several Playground flows that calculate the amount of power in watts that a rad is dissipating but this was the cleanest one. Some of the others included smoothing filters.
only the D5 is watercooled and still, it dumps such minute amounts of heat in the water that you can basically disregard it.
I am not sure this is a valid assumption. I built a test loop on a table that initially consisted of a D5 Next, Ultitube D150, a spinner flow indicator, a High Flow Next, and a ball valve. Coolant volume was ~500ml of distilled water. No CPU or GPU block, and no radiator. With an ambient temp of ~25°C and the pump running at 50%, I was surprised to see the water temp rise to over 40°C after running for ~30 min. The only source of heat in this test loop was the D5 Next and possibly to a lesser degree, the High Flow Next. I suppose that once large heat sources are added to the loop (CPU and GPU blocks), the pump waste heat may be relatively insignificant, but I was surprised that just the pump waste heat could increase the temp of 500ml of distilled water by 15°C that quickly with no rad to dissipate the heat.
I also found that the Koolance ones seem to be the most accurate as all of their probes, including the inline ones, have temp probes protruding into the coolant path, as opposed to just buried in the wall.
Interesting. I looked on Koolance’s website. Some of their temp sensor are thermocouples. The inline or butt-plug thermistor models are:
  • SEN-TP010MFG - Coolant Temperature Sensor Inline, Male/Female Threads, 10K Ohm
  • SEN-TPL010K - Coolant Temperature Sensor Inline, Female/Female Threads, 10K Ohm
  • SEN-AP008B - Coolant Temperature Sensor, Brass, 10K Ohm
  • SEN-AP008G - Coolant Temperature Sensor Plug, 10K Ohm
Are these the models you are referring to? Koolance does have spec sheets for these thermistors that list max temp but they do not accuracy. The thermocouple specs list a temp range and an accuracy of +/-1.5°C which is not that great.
NTC thermistors are notoriously inacurrate, so you'll have to cheat a bit with offsets in Aquasuite, and even then, the response will not always match between sensors. for a same temperature change, some will be reading higher, some will be lower.
Agree. The accuracy of 10K thermistors is not high enough to use them for data calculations that involve temperature differences of 2 or 3°C. You can calibrate them at 0°C by immersing them in a glass of ice water but that does not guarantee that they will report the same values at higher temps. Even if you calibrated them in 5°C increments across the range encountered in a computer cooling loop, Aquasuite does not support offsets at different temps. Even with the limitations of the temp sensors and Aquasuite, I think it is possible to get rreasonably accurate values.

Samstag, 20. Januar 2024, 18:55

My water temperature under load is ~2.5 °C above room temperature.
The only significant changes I see with this type of load are when the room temperature changes. Then the water temperature fluctuates.
However, when I increase the 3 fans of the upper 420 radiator from 490 to 740 RPM, the CPU temperature drops from 37.75 °C to 37.38 °C.

Yes because the formula Q=mCpDT, air flow is treated like a fluid and has a mass flow rate like the coolant, the only difference is the specific heat capacity of air is like 1 and water is around 4x that. Water is also much denser, and non compressible.
Which, like flow rate for your pump, is why the faster you move air at a temp delta the more energy is passed on. A larger volume of air would have to move significantly faster than water to carry the same energy at the same delta T. Which makes sense, and is why Radiators have huge SA and waterblocks just have a fraction of the SA. The mass of each is relatively similar provided they are the same material like copper, just have different densities.
But that's also why I don't think there is a benefit to increasing pump speed without first having to increase your fan speed, and any testing I will do is with the fans at 100%. Its also how my controller is set up, the pump speed doesn't increase until the delta T is high enough that the fans are close to their max or at their max.
It's probably also why i'm seeing such different results. My radiator SA is much smaller it seems than most people, so i'm working with larger temp Deltas. That large delta, means that increasing flowrate is quite noticeable. For example i'm working with a Delta of 5C at idle and more than double that under any significant load. Time and future tests on the new system with like 3x the rad space will tell, and ill make the necessary config changes to the controller.

The problem is those 8 are probably not in the same places in the loop, so you never know which ones read correct :p
NTC thermistors are notoriously inacurrate, so you'll have to cheat a bit with offsets in Aquasuite, and even then, the response will not always match between sensors. for a same temperature change, some will be reading higher, some will be lower.

Normally yes, and in my case 4 will be random, but because the other 4 will be responsible for inlet and outlet temps on a unconventional parallel radiator setup, essentially they are symmetrical. The temps they see should be the same, or enough that an average of each inlet and outlet sensor should be close to actual temps unless both sensors run hotter or colder.
But that's good to know, i'll have to pick up a thermocouple for my multimeter so I can calibrate, label, and adjust sensor offsets in AS.

Are these the models you are referring to? Koolance does have spec sheets for these thermistors that list max temp but they do not accuracy. The thermocouple specs list a temp range and an accuracy of +/-1.5°C which is not that great.

Yes those are the ones I was referenceing, I dont have any on hand and can't remember if i ever viewed the spec sheet myself. At the time i was scrounging for CAD models so i wouldn't have to model everything myself. The rads and GPU block were fun enough lol. But when i opened the .step files and saw the probes inside the coolant path i was sold. If they aren't accurate, they will at least be more responsive, as the fitting plays less of a role.