Triggering reconfig.ĭEBUG: (00:01:36.500) OpenHardwareMonitor: Sensor configuration mismatch found.
Triggering reconfig.ĭEBUG: (00:01:33.500) OpenHardwareMonitor: Sensor configuration mismatch found. Triggering reconfig.ĭEBUG: (00:01:30.500) OpenHardwareMonitor: Sensor configuration mismatch found.
Triggering reconfig.ĭEBUG: (00:01:27.500) OpenHardwareMonitor: Sensor configuration mismatch found. Triggering reconfig.ĭEBUG: (00:01:24.500) OpenHardwareMonitor: Sensor configuration mismatch found. Triggering reconfig.ĭEBUG: (00:01:21.500) OpenHardwareMonitor: Sensor configuration mismatch found. Triggering reconfig.ĭEBUG: (00:01:18.500) OpenHardwareMonitor: Sensor configuration mismatch found. Triggering reconfig.ĭEBUG: (00:01:15.500) OpenHardwareMonitor: Sensor configuration mismatch found. Triggering reconfig.ĭEBUG: (00:01:12.500) OpenHardwareMonitor: Sensor configuration mismatch found. Triggering reconfig.ĭEBUG: (00:01:09.500) OpenHardwareMonitor: Sensor configuration mismatch found. Triggering reconfig.ĭEBUG: (00:01:06.500) OpenHardwareMonitor: Sensor configuration mismatch found. Triggering reconfig.ĭEBUG: (00:01:03.500) OpenHardwareMonitor: Sensor configuration mismatch found. Triggering reconfig.ĭEBUG: (00:01:00.500) OpenHardwareMonitor: Sensor configuration mismatch found. Triggering reconfig.ĭEBUG: (00:00:57.500) OpenHardwareMonitor: Sensor configuration mismatch found. Triggering reconfig.ĭEBUG: (00:00:54.500) OpenHardwareMonitor: Sensor configuration mismatch found. Then it should start reporting values.Ĭode: Select all DEBUG: (00:00:51.469) OpenHardwareMonitor: Sensor configuration mismatch found. You may need to just let it initialize for a few (<5) seconds. The code you commented out is required as otherwise it will fail if you start changing sensors (turn on/off HDD monitoring) in an already running OHM process. This is to make sure that OHM has time to read all of the hardware which takes a finite amount of time (otherwise the available sensor list is constantly changing). The plugin reads the sensor list 3 times before reporting any values. That debug output is the correct behavior on startup.
The plugin strips trailing 's' from the sensor type so you can use the WMI reported string or the GUI reported string. Which is correct?Įither string for sensor type is fine.
However, WMI says "Temerature", "Voltage", "Fan". GUI says "Temperatures", "Voltages", "Fans". Shows 0.īTW, sensor type is different between OHM GUI and WMI. Spx wrote:First, this plugin doesn't work in my system. On the other hand, WMI test application (wbemtest.exe) shows correct value.Ĭommented out SensorMgr.cpp line 368-385, works fine. Triggering reconfig.ĭEBUG: (00:00:06.234) OpenHardwareMonitor: END: update sensor valuesĭEBUG: (00:00:06.234) OpenHardwareMonitor: BEGIN: Read measure 1ĭEBUG: (00:00:06.234) OpenHardwareMonitor: END: Read measure 1 Code: Select all DEBUG: (00:00:00.531) OpenHardwareMonitor: BEGIN: Adding measure 1ĭEBUG: (00:00:00.531) OpenHardwareMonitor: BEGIN: connectĭEBUG: (00:00:00.578) OpenHardwareMonitor: END: connectĭEBUG: (00:00:00.578) OpenHardwareMonitor: END: Adding measure 1ĭEBUG: (00:00:02.156) OpenHardwareMonitor: BEGIN: update sensor valuesĭEBUG: (00:00:02.156) OpenHardwareMonitor: BEGIN: connectĭEBUG: (00:00:02.187) OpenHardwareMonitor: END: connectĭEBUG: (00:00:02.187) OpenHardwareMonitor: END: update sensor valuesĭEBUG: (00:00:02.187) OpenHardwareMonitor: BEGIN: Read measure 1ĭEBUG: (00:00:02.187) OpenHardwareMonitor: END: Read measure 1ĭEBUG: (00:00:06.187) OpenHardwareMonitor: BEGIN: update sensor valuesĭEBUG: (00:00:06.187) OpenHardwareMonitor: BEGIN: connectĭEBUG: (00:00:06.219) OpenHardwareMonitor: END: connectĭEBUG: (00:00:06.234) OpenHardwareMonitor: Sensor configuration mismatch found.