Mike-G

Thanks, @c-attack. Just the information I was looking for.

I would like to use the same fan curves for my 6 fans across all my profiles. I was thinking to create a baseline profile with the desired fan curves and then duplicate that as a starting point each time I add an application-specific profile. The problem with this, is that if I decide to change the fan curves after adding application-specific profiles created this way, I have to edit each of the profiles with the new fan curves. Is there a way to define the fan curves in such a way that a single definition of the curves will be shared by all my profiles (unless specifically overridden)? The fans are connected to a CommanderPro and I'm using iCUE 3.24.52 (latest at the time of this post).

That's just what I wanted to know. Thank you.

I'm doing a new build with 2 Commander Pros. I have a Bitspower thermal sensor as part of my cooling loop that I'd like to use with both CPros. [This forum thread indicates the sensor is compatible with the CPro], so I'm not concerned about one of the CPro's being able to see the sensor's reading. I would like to define fan profiles in each of the CPro's that are based on that single sensor. I've read there are sometimes conflicts when multiple applications/devices try to read the values from a single sensor at the same time (I'm thinking back to articles about HWInfo and iCUE). So the first question would be would a similar problem exist between 2 CPro's? If there are no conflicts, then is it possible to connect the sensor to CPro-A and make that value available to CPro-B as well? If the CPro's can't share sensor readings with each other, then if I connect the sensor to a thermal header on the motherboard, would both CPro's be able to use it for fan profiles and avoid the conflict I mentioned, above? As a last resort, I can modify my plan for the plumbing and include two sensors, but I'd like to avoid that, if possible. Any thoughts/suggestions?