I recently bought the mCubed bigNG fan/pump controller (http://www.overclockers.co.uk/showproduct.php?prodid=BB-005-MU). It is connected via USB and gets its power via a 4-pin molex connector. It has 2 digital temperature sensors and 4 analogue sensors. Finally it has 4 "fan" sensor lines for telling the MB/BOIS what the current fan speeds are.
You program the sensors using some frankly klunky and out-dated software (T-balancer Navigator 2.12) that allows the fan speeds to be altered according to the various temperature readings, or manually. You can choose to control the fan by
* "Response Curve" - a set of temperature v fan speed points, joined by straight lines
* Target Temperature (with various options for moving towards that temperature)
* Software Sensor (see below)
* Manual
Since each fan channel can support up to 20 W of output you can control a pump as well as a set of fans. My plan is to use this to control my pump and the fans on my radiator at the very least. Doubtless I will control the other fans as much as I can within the constraints of the available outputs. I like the fact that the bigNG is self-contained and will come into life immediately, allowing the fans and pump to start before the BIOS has finished its POST, never mind the OS.
It is possible to calibrate the temperature sensors, although I haven't tried this yet.
It is also possible to feed temperatures from the CPU/GPU and other MB ICs, but this will only happen when the software is running (and communicating with the bigNG). This is the "Software Sensor" mode mentioned above but my experience with it to date is a) it only works with a few tools that read the MB sensors and b) it seems to "forget" it settings when there is an issue communicating with the software actually providing the sensor readings.
Having said that these "software sensor" temperatures ought to be far more accurate than the ones provided via the bigNG's own sensors (which could be relatively far from the actual silicon, but the "software sensors" are only any use once someone has logged into the computer. This would be offset through the use of a service/daemon that started early in the boot and didn't need to wait for someone to login. I have my doubts that the current software offering will include such functionality. The good news, however, is that the API for controlling the bigNG (via its USB interface) is published, so it would be possible to write such as service. It is something I may do, but it's not top of my todo list!
At the moment my bigNG is only controlling my computer fans and it seems to do this well. However when I rebuilt my computer over Christmas it will be controlling my coolant pump and I will then be relying on it to never stop the pump. I will let you know how I get on with that build.
You program the sensors using some frankly klunky and out-dated software (T-balancer Navigator 2.12) that allows the fan speeds to be altered according to the various temperature readings, or manually. You can choose to control the fan by
* "Response Curve" - a set of temperature v fan speed points, joined by straight lines
* Target Temperature (with various options for moving towards that temperature)
* Software Sensor (see below)
* Manual
Since each fan channel can support up to 20 W of output you can control a pump as well as a set of fans. My plan is to use this to control my pump and the fans on my radiator at the very least. Doubtless I will control the other fans as much as I can within the constraints of the available outputs. I like the fact that the bigNG is self-contained and will come into life immediately, allowing the fans and pump to start before the BIOS has finished its POST, never mind the OS.
It is possible to calibrate the temperature sensors, although I haven't tried this yet.
It is also possible to feed temperatures from the CPU/GPU and other MB ICs, but this will only happen when the software is running (and communicating with the bigNG). This is the "Software Sensor" mode mentioned above but my experience with it to date is a) it only works with a few tools that read the MB sensors and b) it seems to "forget" it settings when there is an issue communicating with the software actually providing the sensor readings.
Having said that these "software sensor" temperatures ought to be far more accurate than the ones provided via the bigNG's own sensors (which could be relatively far from the actual silicon, but the "software sensors" are only any use once someone has logged into the computer. This would be offset through the use of a service/daemon that started early in the boot and didn't need to wait for someone to login. I have my doubts that the current software offering will include such functionality. The good news, however, is that the API for controlling the bigNG (via its USB interface) is published, so it would be possible to write such as service. It is something I may do, but it's not top of my todo list!
At the moment my bigNG is only controlling my computer fans and it seems to do this well. However when I rebuilt my computer over Christmas it will be controlling my coolant pump and I will then be relying on it to never stop the pump. I will let you know how I get on with that build.