How to use
This page describes how to use SuckControl.
SuckControl can only control what LibreHardwareMonitor is able to control. From my experience, all nvidia graphic cards work, but not AMD 5000 and 6000 series. All motherboards I tested work. But from the issues it is clear, that there are not (properly) working motherboards, too. Some NVMes seem to be reporting 0°C.
Not sure if fan controllers are supported. Plugging the fans directly into the motherboard works. Of course, fans plugged into the PSU, wont be possible to control.
- Make sure, to set the fan ports to DC or PWM in the BIOS according to the plugged in fans
- Disable automatic fan control in the BIOS for the fans which should be controled with SuckControl
- Same for the graphics card in MSI Afterburner and Geforce Experience (ALT+Z)
- Most of the PWM fans don't turn off at 0% speed (this can also depend on your motherboard)
- A workaround would be to set the PWM fans to DC in the BIOS, but thats not recommended
The interface is split into two parts. Rules and sensors.
On the first start, there wont be any rules. Every rule needs to be created. The header shows the temperature sensor and the first fan associated with this rule. Other fans aren't shown, but they are there.
Under the temperature sensor the temperatures are shown which were set. Same goes for the values under the fan, but the values are the speed of the fan. The speed of the fans between two temperature sensors is calculated, moves linear to the next one.
Rules can be deleted or turned off.
The sensors are split into three columns.
- Fan controller speed sensors (0-100%)
- Fan speed sensors (RPM)
- Temperature sensors (°C)
The fan controller sensors have a slider to manually set a speed. This is for testing only and therefor not saved! This slider is disabled, if the fan controller is associated with an enabled rule. Disabling a rule enables the sliders.
The button is also only active, if the fan is not used in an active rule. This button sets the fan to default, "frees" it. Allowing the motherboard to control the fan again. Or the VBIOS of the graphic card.
Shows the fan speed in RPM (revolutions per minute). The yellow cable of the fan transmits this info.
All the available temperature sensors of the system are shown here. Any of them can be freely used in a rule.
All sensors can be renamed. A click on the name opens a popup. Take time identifying all the sensors before renaming them. The same name can be used multiple times, like "CPU" for temperature, fan speed and fan controller. But that should be avoided if the Artemis feature is enabled.
Enable the Artemis feature to send the sensor values to Artemis. The json plugin of Cheerpipe is required to be installed in Artemis for this feature to work. Download it on the Actions tab. Refer to the Artemis docs to learn how to use these data.
Click the plus sign in the bottom right corner to open the page for adding a new rule.
- Only fan controllers which aren't in a rule are shown, the same fan can't be in more than one rule
- Multiple fans can be used in one rule
- All fans will be set to the same speed in this case (RPM will differ, depending on the fans)
- At least one temperature sensor and one fan need to be selected
- The next temperature and speed values need to be higher than the previous ones
- All the values are limited from 0 to 100
- At least the first values are required (this would set a static speed)
- Depending on the fan (DC, not PWM), the fan might start spinning at 40%-50% speed
- Either stay with the lowest speed above this point, or change directly from 0% to 40% (set temp to 40 and speed 0, second values to temp 41 and speed 40%)
- Generally there shouldn't be any need to set the speed to 80% or higher (but test the rules and set them accordingly)