[BUG] CoreTemp - no individual clockspeeds, multis and Vids

[jsmorley]

The author of CoreTemp has responded, and although he has added what I think you need to the "shared memory" of CoreTemp, he is not certain he has the time to work on the plugin. Stand by... I'm laying some guilt on him.

[The Coolest]

Hi everyone,

Indeed the plugin has not been updated in about 6 years now. I guess other than this little niggle it was probably working well
As jsmorley has noted, Core Temp does support multiple frequencies in its shared memory block, it didn't when the plugin was written, though.
So I'll add the code to the plugin in the upcoming few days to implement support for per-core frequencies.

[protator]

That sounds great, thx a lot.
But if possible please also implement a way to get the readings for the virtual core's speeds, not just physical cores.
That'd be the coolest .

[The Coolest]

Core Temp currently only shares multipliers for physical cores, so that's not possible right now.

[Bekarfel]

I just checked your code and it works the same as mine. I have found that very rarely do the cores have different speeds.

Yes, I had to manually refresh CoreTemp with a very low refresh rate to be able to capture the cores' clock discrepancies after I identified it existed. I took a look through the code on github, but I'm not a programmer and I couldn't figure out how it polled for the CPU core loads.

A very big thanks to TheCoolest for looking into this long after the original release!

[protator]

Core Temp currently only shares multipliers for physical cores, so that's not possible right now.

How can that be? My CoreTemp install clearly shows two individual threads per core with their respective clockspeeds.

I don't want to sound ungrateful, but it's right in front of me .... or am I missing something crucial here?

[The Coolest]

The interface Core Temp exposes to the outside world doesn't support it.
Regardless, what you're basically seeing is the same physical core polled at different times, that is why the multiplier is different. The actual, physical core can only run at a specific frequency at one time.
If you're interested, there's an SDK for Core Temp you can look at to see how Rainmeter accesses the available information.
http://www.alcpu.com/CoreTemp/developers.html

[jsmorley]

Ok, The_Coolest has made some additions to the plugin.

There are 4 new CoreTempType values:

CoreSpeed
Requires a 0-based CoreTempIndex to the desired core
This is a calculation based on the FSB speed for the system, times the CoreBusMultiplier for the indexed core.

CoreBusMultiplier
Requires a 0-based CoreTempIndex to the desired core

Tdp
Supports, but does not require, a 0-based CoreTempIndex to the CPU on multi-CPU systems.

Power
Supports, but does not require, a 0-based CoreTempIndex to the CPU on multi-CPU systems.
Not all CPU's support a "Power" reading

Here is a pre-release "beta" of Rainmeter 4.1, which has the changes to the plugin. Could you guys please test this with your systems and ensure it works as expected?

https://builds.rainmeter.net/Rainmeter-4.1-r2770-beta.exe

Requires that the latest CoreTemp 1.6 application be running on your system.
http://www.alcpu.com/CoreTemp/

[CyberTheWorm]

Capture.PNG

4.1.0 beta r2770 64-bit (Mar 6 2017)
Windows 10 Pro 64-bit (build 14393)
Path: C:\Program Files\Rainmeter\
IniFile: C:\Users\Graham\AppData\Roaming\Rainmeter\Rainmeter.ini
SkinPath: C:\Users\Graham\Documents\Rainmeter\Skins\

Using these Measures, hope I got them correct:

Code: Select all

[MeasureCore0Temp]
Measure=Plugin
Plugin=CoreTemp
CoreTempType=Temperature
CoreTempIndex=0

[MeasureCore0Speed]
Measure=Plugin
Plugin=CoreTemp
CoreTempType=CpuSpeed
CoreTempIndex=0

[MeasureCoreSpeed]
Measure=Plugin
Plugin=CoreTemp
CoreTempType=CoreSpeed
CoreTempIndex=0

[MeasureBusSpeed]
Measure=Plugin
Plugin=CoreTemp
CoreTempType=CoreBusMultiplier
CoreTempIndex=0

[MeasureCore0Voltage]
Measure=Plugin
Plugin=CoreTemp
CoreTempType=Vid
CoreTempIndex=0

[MeasureCore0Load]
Measure=Plugin
Plugin=CoreTemp
CoreTempType=Load
CoreTempIndex=0

[MeasureCPUName]
Measure=Plugin
Plugin=CoreTemp
CoreTempType=CpuName

[MeasureTDP]
Measure=Plugin
Plugin=CoreTemp
CoreTempType=Tdp
CoreTempIndex=0

[MeasurePower]
Measure=Plugin
Plugin=CoreTemp
CoreTempType=Power
CoreTempIndex=0

[jsmorley]

Using these Measures, hope I got them correct:

Looks ok. Are those the value you expected from your system?