I used the V2.0b12 in conjunction with MacsFanControl for a period of time already. This combination works well. I need MacsFanControl because I want to build my own fan profile to keep the PSU and PCIe compartment cool.
However, what I don't like is MacsFanControl's relatively high CPU demand (even though the overall CPU demand still low, but it's about 300-500% higher than this fan control software). Also, I don't like that MacsFanControl alter the target fan speed in conjunction with the Fan Force bit to force a fan run at a possible too low RPM regardless if the hardware is overheating. This is the most powerful area of MacsFanControl, I don't know any other software control the fan in this way. But it's also the most dangerous way to control the fan. There is no fail safe protection. If user set a wrong fan speed / profile, the hardware can overheat straight away.
Therefore, I add the PSU and PCIe fan control to this software, make it now able to control all fans. So that I can get rid of MacsFanControl completely.
Since I only want to set fan profiles, and I personally use iStat for monitoring. Therefore, I leave the chart as is, and remove all the reading from the control panel. Make it only for setting fan profile only.
There is no change on the CPU fan stuff (Regardless only CPU A has setting in the control panel. BOTH CPU will be monitored base on the same setting. And fans will spin up when either of the CPU reach the lower threshold. However, since CPU A always warmer, which means CPU A is always the master), but just add PSU and PCIe fan control.
PSU fan will react to the PSU component temperature (SMC key Tp1C)
PCIe fan will react to the PCIe compartment ambient temperature (SMC key Te1P)
e.g. In the above example.
When PCIe ambient reach 36C, the PCIe fan will spin up 100RPM / degree C
When PSU component reach 36C, the PSU fan will spin up 100RPM / degree C
This fan control software is aim to provide better cooling, and allow the user to keep the fan noise as low as possible, but not override system protection. Therefore, it will not and CANNOT override the infamous SMC bug (high PCIe and PSU fan after cold boot until GPU stressed). If you want to address that issue, please use MacsFanControl.
1st time install may cause the fan run at full speed. Not sure what's wrong, but some user report a 2nd installation fix it.
Some parameter in the control panel may be missing (or shows zero) after the 1st installation, please check all parameter in control panel after 1st install and set a valid number if required. If fan run at high speed. Try a 2nd install after all parameter set. (Set sensitivity to 30 will allow the fan to stabilise much quicker. But in general use, sensitivity 1-10 usually a better choice, which allow the fan spin up / down at a reasonable rate and avoid the sudden noticeable change of fan noise)
I believe Sierra require disable SIP to install this software. I am not sure. I always disable SIP on my Mac.
In general, MacsFanControl can do the job well (and most likely much better than this little beta software). However, there is one main function that this software can do but MacsFanControl cannot. Which is
Set a higher idle RPM + Auto fan spin up
MacsFanControl can only do one, but not both at the same time. But this software will allow the user to set a higher idle RPM (e.g. PSU fan idle at 1000RPM), and still provide auto spin up at lower threshold.
N.B.
This is a beta software, may be plenty of bugs.
Please study this thread to make sure you know how to uninstall this software and perform a SMC reset before you try it.
I tested this version on my Mac, it works well. However,
USE AT YOUR OWN RISK!
The apps will make all fans run at max speed few seconds after installation. DO NOT panic! This is normal. Just open the fan control panel in system preferences, and set all required parameters. The fan should spin down and then work as expected. (recommend set sensitivity to 30, let the fan spin down much quicker, than set it back to 1 or whatever you want)
https://forums.macrumors.com/thread...ol-now-version-2.1340705/page-7#post-24603371
Update 9th May 2017:
Bug fixed, and version updated to (V2.0b14). Details refer to post #152.