I believe what you're asking for is called Aquaero

Citation de "Teasuti"

Citation de "Remayz"

I believe what you're asking for is called Aquaero

Can Aquaero do this without Aquasuite? On it's own, in the hardware. Not a sarcastic question, I don't have one, so I can't tell. I ask this genuinely.
[attach]11261[/attach]
[attach]11262[/attach]

Yes it can. i don't own one but i believe it can have up to 4 virtual sensors managed onboard

Quoted from "Remayz"

Yes it can. i don't own one but i believe it can have up to 4 virtual sensors managed onboard

I don’t own one either, but I think Remayz is right. Section 11.2 in the manual explains how the 4 virtual temp sensors can be assigned 3 temp data sources, and have 3 “modes” or functions - calculate the highest/lowest temp, the avg temp, or the temp difference between 2 data sources. I think you select the mode for each virtual temp sensor in Aquasuite or via the touch panel. This is separate from software temp sensors for which the data is brought into the Aquaero via USB.

Quoted from "Teasuti"

That's a good call. I haven't read it past section 7.1 which didn't mention other functions than just min/max/avg.

I'm
just going out on a limb here, but I'd be curious how clever is that
part of the firmware. Could a Virtual Sensor take the output from
another Virtual Sensor as an input? Currently in Aquasuite I have 3
thermistor readings on the GPU/CPU inlets and outlet to measure the heat
each component adds to the water, and having the Octo to do PID control
and adjust the pump speed to keep to a target temperature (difference)
of 1C of either the GPU or CPU block, whichever is higher.
This would
look like a stack of Virtual Sensors, where there're two Virtual
Sensors calculating the difference on the GPU and CPU inlet/outlet
separately, then a third Virtual Sensor would take these two and feed
the higher of the two into the output. It could be done with 3 Virtual
Sensors IF the firmware can reuse their output as input between them.
This is just an elaborated pump control I have in Windows Aquasuite.

Then I could still have the 4th one to calculate a differential between room temp and the water for the fan control.

For most single loop systems (CPU > GPU > Radiator), your hottest coolant will be at the 'in' side of the radiator.
Generally, ramping the pump up and down has little effect on the cooling plate. The increased coolant flow across the plate is offset by less time in the radiator.
120 to 220 lph is normally acceptable (find quietest pump setting in that range).
Then take the delta of ambient and the 'out' port of the radiator for the fan control, and leave the pumps alone.

Quoted from "InfoSeeker"

Generally, ramping the pump up and down has little effect on the cooling plate. The increased coolant flow across the plate is offset by less time in the radiator.
120 to 220 lph is normally acceptable (find quietest pump setting in that range).
Then take the delta of ambient and the 'out' port of the radiator for the fan control, and leave the pumps alone.

The effect that pump speed and flow rate has on cooling loop heat transfer efficiency has long been debated. The general consensus is that outside of extremes, it has little effect. I have confirmed this through my own testing. I set my D5 Next pump to 100% and let the temperatures stabilize. I then reduced the pump speed in 5% increments. I did not see any change in temps until the pump speed was below ~20%. I don’t think constantly changing the pump speed by having it chase a delta-T will significantly improve the loop heat transfer efficiency, and it may put undue strain on the pump.

Quoted from "Teasuti"

Could a Virtual Sensor take the output from another Virtual Sensor as an input? ...This is just an elaborated pump control I have in Windows Aquasuite.

When you set this up in Aquasuite, did you perform testing to determine what, if any, improvement it provides? You may want to reconsider what you use the calculation output data for. Unlike pump speed, radiator fan speeds do have a significant effect on coolant temp, which in turn has an effect on CPU and GPU coldplate temps. This is why many people use Aquasuite to subtract ambient temp from coolant temp and assign the delta-T data to a fan speed curve or PID controller.

Whether virtual sensor outputs can be temperature inputs to another virtual sensor is an interesting question, but unfortunately, I do not know the answer. Manual Section 11.2 says, “Mode and up to three data sources (temperature sensors) can be selected for each of the four virtual temperature sensors.” I think this means each of the 4 virtual sensors can have different temp sensors assigned to them, but it does not say whether one or more of these temp sensors can be the output of one of the other virtual sensors. Maybe someone who owns an Aquaero or an Aquacomputer rep will chime in here.

Quoted from "Teasuti"

Oh, I just got an idea.
Perhaps I should make a separate board with sensor inputs and outputs, that would do the mixing itself and just feed the output to the Octo.
This would be a nice Sunday afternoon Arduino project for baked-in fix functionalities.
From then on the customizability and adjustability would all depend on how far the maker is willing to take the project on the coding side of things.
(Aquacomputer this is your chance to take notes for your next product before I patent it.)

This is a cool idea! You could set up a microcontroller and a few temp sensors as a stand-alone device and write code that will perform the mathematical functions you want on the temp sensors’ data. I would use Arduino-IDE, ESP-IDF, or STM CUBE-IDE, since all of these compile source code into native machine code and flash it as firmware stored in non-volatile memory on the microcontroller. This part is relatively easy. The tricky part is getting the final delta-T value into the Octo and not via USB. The Octo temperature sensor inputs are designed for a 10KΩ NTC thermistor. Internally, I think the Octo provides a known excitation voltage (probably 3.3 V) and includes a fixed precision resistor that forms a voltage divider with the external thermistor. The voltage at the divider junction is measured by an ADC input on the Octo’s microcontroller. From this measured voltage, the known excitation voltage, and internal resistor value, the firmware calculates the effective resistance of the connected thermistor. The calculated resistance is then converted into a temperature value in degrees Celsius using an assumed thermistor model, likely implemented as a Beta-based approximation, commonly B3950Kor an equivalent lookup table derived from a 10 KΩ NTC thermistor characteristic curve. I doubt that the Octo is using Steinhart & Hartcoefficients to calculate the temperature as these are used for levels of precision that are higher than what the Octo targets.

Your microcontroller would have to output the delta-T data in a format that emulates the resistance of a 10KΩ NTC thermistor when it is measuring a temperature. I think the way to do this is add a Digi-Pot that the microcontroller talks to over I2C or SPI. The microcontroller would tell the Digi-Pot what DC resistance to output on its analog pins that are connected to an Octo temp sensor input. For this application, I would go with I2C and a Digi-Pot like the Analog Devices AD5241. It may require a series fixed resistor depending on the range of the Digi-Pot. If you have an idea for an easier way to get the temperature value from your microcontroller into the Octo, please share. Maybe I am overcomplicating this.