Closed brentward closed 10 months ago
From your LHM screenshot, you got 2 NCT6796D-R on that board? That's a first.
"Identifier": "/lpc/nct6796dr/control
Problem would then lie here, we got identifier conflicts.
Yeah, that seems like the issue. Is this an issue with LHM or does FanControl create the identifiers?
FanControl uses the identifiers provided as is, so I guess I'll have to add another layer on top verifying for dups.
Created a PR in LHM for this bug: https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/pull/1183
Update: I must have used the wrong version of FanControl because I tried using the build artifacts from your LHM PR again with a fresh copy of the net_7_0 version of FanControl and it started up and the issue seems to be resolved. I will use it for a bit and report back.
~Is it possible to use the build artifacts from your LHM PR to test if it fixes FanControl? I tried just dropping the LibreHardwareMonitorLib.* files from the net70 artifact into the FanControl directory but that didn't work.~
I've been using it with the artifacts from your LHM PR for a few days and everything seems to be working.
Does the latest FanControl release, V173, include your LHM fix? I installed it expecting to have to replace the LHM files again but it continued to work without doing that.
I compile my own branch of LHM for FanControl, with urgent fixes in it, until they get merged.
When I upgraded to V174 a bunch of sensors for the fans were reset. Is this caused by a difference between your custom version of LHM and the way it was merged? I'm redetecting the fans now and they are all still work but I'm wondering; will I have to do this again on future upgrades?
Yes kind of, the implementation changed a bit. Now all identifiers with an index of 0 get their index removed so that everybody with only a single LPC chip doesn't get all their identifiers changed.
for eg: If you got only a single NCT6796D: /lpc/nct6796d/control/1
if you got three: NCT6796D /lpc/nct6796d/control/1 /lpc/nct6796d/1/control/1 /lpc/nct6796d/2/control/1 [...]
People with single chip => no identifier change People with two chip (like you) => both chip get a unique identifier.
You should be good now.
Describe the bug My system shows duplicate identifiers for fans and sensors which is causing conflicts and preventing sensor pairing and any configuration information from saving. Is there a log.txt file next to FanControl.exe with recent date entries? No log.txt
Relevant hardware specs and setup ASRock z690 PG Velocita
In LibreHardwareMonitor there are two different entries for Nuvoton NCT6796D-R that each list 7 fans and controls, so it seems that FanControl is not distinguishing between the fans and controls with the same index on the different controllers.
The default configuration shows duplicate identifies for Controls and FanSensors.