-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
T_SEN1 input missing #6
Comments
Hello, Do you have the ability to run a Windows 1O and test with Hardware monitor if the sensor is detected and display the good value? |
No, unfortunately not. This PC is linux only. However, I just found this here, which could be helpful: So it seems hwinfo can show it, but LibreHardwareMonitor can't (yet). |
@Fred78290 @berniyh |
@Fred78290 : no Luck with CPUID HW Monitor - shall i try something else? |
@FocalDE |
The screenshot says "NUC126". For that I found docs here: There is also info about a temperature sensor in section 8.4.2. Don't quite understand though why they would hook up that sensor to another controller, especially one that seems to fulfill a different purpose normally. |
There is a workaround for using this sensor.
PS: I attachted the probe directly on the radiator to monitor the exhaust temperature: |
Hi,
thanks for the driver, it works very well on my MSI B550 Gaming Carbon board.
However, I noticed that one temperature is missing and that is the temperature for the T_SEN1 input, which can be used to monitor e.g. the case temperature or the water temperature in case of water cooling.
I have installed a thermister to the correct pin and in the BIOS I get a proper reading for the sensor (about 30°C).
I already tried increasing the number of temperatures being read in the driver to 8 (which is the maximum as far as I understood), but that gives me a 0°C reading, just like the M2 one.
Do you have an idea how to fix this or how to find out whether the thermister is connected to this controller?
I didn't see any other controller on the mainboard it could be connected to but it is of course possible that I missed something.
The text was updated successfully, but these errors were encountered: