Fans Are Detected But Cannot Be Controlled

[Halliphax]

Per the title, the fans can be detected by the plugin but they can't be interacted with (i.e can't change the speed). Using the latest version of FanControl (175 NET 4.8)

[arlo-infinity]

@Halliphax I assisted in the testing of this plug-in when it was first created for Evan as he didn't actually have the hardware available.
@EvanMulawski I'm not sure if that has changed but probably not.

Unfortunately, I will be away from my computer that has my Razer PWM Fan Controller in it for several weeks so I can't confirm that the plugin is or is not working with FanControl 175. I can however confirm that it was working for me on FanControl 172. I don't know if I upgraded to 173, released Oct 27, before I left for my extended trip on November 1 but I may have done.

A couple of suggestions (Assuming that this is the first time you have tried to run this plugin):

1. Try uninstalling and rolling back to 172. Can be found here https://github.com/Rem0o/FanControl.Releases/releases
   If it does work with 172 try updating until it breaks.

2. If it still doesn't work, be sure that there are no other programs that are accessing the fan controller at the same time, as most programs don't play nice because, as far as I understand, assume they have full control of the device. This includes Razer Synapse, which can be set to autostart in the background on boot, so go search for anything Razer in your process list on Task Manager. Any other program which can detect the Razer PWM is also a potential culprit. I can however confirm that there are some programs, like SynapseRGB, detect the Razer PWM as a PID device, but don't interfere.

3. If it still doesn't work, try running Razer Synapse and see if it detects the Razer PWM Fan Controller and functions correctly, and check which version of the Firmware you have. If I remember correctly from beta testing I may have had to update to v1.01 of the Firmware from v1.00 or maybe v1.001 at some point.

[EvanMulawski]

Hi @Halliphax, try removing this plugin - the Libre Hardware Monitor library Fan Control uses now has a built-in implementation derived from my code.

[arlo-infinity]

Hi @Halliphax, try removing this plugin - the Libre Hardware Monitor library Fan Control uses now has a built-in implementation derived from my code.

That's helpful to know. Did this just change or has it been in there for awhile?

[EvanMulawski]

Possibly since V160 - Rem0o compiles his own version, so not 100% sure unless I decompile the library. I didn't realize it until a few weeks ago and I haven't had time to update the README.

[arlo-infinity]

Possibly since V160 - Rem0o compiles his own version, so not 100% sure unless I decompile the library. I didn't realize it until a few weeks ago and I haven't had time to update the README.

@EvanMulawski He said he updated LibreHardwareMonitorLib in V174, so maybe that was it (if it is indeed broken). As mentioned above I was updating upon the releases and I am 99% I had no issues at V172.

[Halliphax]

Thank you both for the prompt response

@arlo-infinity I’ll give this I go, I only have SignalRGB and FanControl installed so nothing else should be interfering. Do you happen to know how to update the firmware on the box? I initially used Razer synapse to make sure it was all working but couldn’t see any way to update the firmware (and Google is thin on info for this product).

@EvanMulawski I did notice that the fans were detected by FanControl but sadly they couldn’t be interacted with, similar to your plugin. Might be a firmware or version issue as the other user pointed out.

[arlo-infinity]

@Halliphax There is a seperate firmware updater that will flash it for you. You can download it here:

Razer PWM PC Fan Controller Firmware Updater

[Halliphax]

@arlo-infinity managed to find that last night and forgot to update this post, sorry!

So the firmware update worked but it then only managed to sync one group of fans. Installed Razer Synapse afterwards to try and figure out what was going on and it could only recognise one port (although four were occupied and I remember they were recognised pre-firmware update). Going back to good old motherboard headers for now.

Anyway, the plugin works it seems with 172 so there’s that, just appears to be my PWM box that’s dodgy!