Jump to content

HWSensors3

Slice

By Slice,
in Hardware Sensors

 Share
2,189 posts in this topic

Recommended Posts

Andres ZeroCross
Andres ZeroCross
Posted
Posted (edited)
18 minutes ago, vector sigma said:

Hi, I forgot 3/4 translations.. see the new incoming app

I hope that I have fix it, but after seeing this an idea was coming.. let see a new functionality :D of the new app.

P.S. beta 7 is no more, all is rewritten from scratch.

Please a ioreg can't say mutch without it.

 

Attached..

 

And this is screenshot of the HWMonitorSMC2 Alpha 9

image.thumb.png.c11398a6142f630417ed3413593106a7.png

Andres’s iMac.ioreg.zip

Edited by Andres ZeroCross
  • Thanks 2
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted (edited)

New app promoted to Beta:

  1. Added new translations in Russian by Andrey1970, Italian and English by me.
  2. Added check for Intel Power Gadget: cpu must be Intel (Lol), family 6, model > 42, i.e >= 2nd generation of "Core" models. Xeon models 42, 46 and 47 are supported as I see that they can work (anyway SMC keys if present will be entirely read).
  3. Moved CPU Package IGPU inside the GPU group. If the IOAccelerator's monitoring is turned on that key will be added inside the Intel sub group.
  4. Tried to fix pulsations of the text in the top bar. Need a confirmation.
  5. New: instead of display sensors in the top bar, you can now display a gadget that you can place where you like. This gadget is always on top of other windows... so that you can now compare, run programs or make a test stress cosily observing the value you need. see the pictures:

 

1.png.a4bf19c452f3b4604b6fcd806ddbf79f.png2.png.9d3feecaa0104cd77d38b01ae8c6649f.png3.png.c22f075a324284990d36092fd83bbf76.png4.png.78f138f3da72004d197c1ab2fbb87ea3.png

 

5.png.7bb91f16cb8c097228aa9d2c0d5e4f19.png

 

Let me know.

 

One problem. DRAM is still under the CPU group due to the fact that is really inefficent to move it under the memory group. To do that a second call to the IntelPowerGadget.framework and its driver is needed and basically is a second call of all of its functionality. Really heavy, wont do that sorry.

 

HWMonitorSMC2.app_SMC_swift4.2_Beta1.zip

 

Edited by vector sigma
added missing Russian translations
  • Like 2
  • Thanks 1
Link to comment
Share on other sites
Andrey1970
Andrey1970
Posted
Posted 
// Fans
"Fans or Pumps" = "Вентиляторы и помпы";
"Fan/Pump speed" = "Вентилятор обороты";
"Fan %d" = "Вентилятор %d";
"speed" = "обороты"; // rpm, all in lower case letters
"min speed" = "мин. обороты"; // rpm, all in lower case letters
"max speed" = "макс. обороты"; // rpm, all in lower case letters

Temporarily so.

I thinking that the translation will need to be corrected after I will see application.

I do not see some parameters, you possibly forgot still.

Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted
Just now, Andrey1970 said: 

// Fans
"Fans or Pumps" = "Вентиляторы и помпы";
"Fan/Pump speed" = "Вентилятор обороты";
"Fan %d" = "Вентилятор %d";
"speed" = "обороты"; // rpm, all in lower case letters
"min speed" = "мин. обороты"; // rpm, all in lower case letters
"max speed" = "макс. обороты"; // rpm, all in lower case letters

 

Thanks. Please I need also "Max Frequency" = "Max Frequency";

2 minutes ago, Andrey1970 said:

I do not see some parameters, you possibly forgot still.

Sorry which one? I didn't understand..

  • Like 1
Link to comment
Share on other sites
Andres ZeroCross
Andres ZeroCross
Posted
Posted
6 minutes ago, vector sigma said:

New app promoted to Beta:

  1. Added new translations in Russian by Andrey1970, Italian and English by me.
  2. Added check for Intel Power Gadget: cpu must be Intel (Lol), family 6, model > 42, i.e >= 2nd generation of "Core" models. Xeon models 42, 46 and 47 are supported as I see that they can work (anyway SMC keys if present will be entirely read).
  3. Moved CPU Package IGPU inside the GPU group. If the IOAccelerator's monitoring is turned on that key will be added inside the Intel sub group.
  4. Tried to fix pulsations of the text in the top bar. Need a confirmation.
  5. New: instead of display sensors in the top bar, you can now display a gadget that you can place where you like. This gadget is always on top of other windows... so that you can now compare, run programs or make a test stress cosily observing the value you need. see the pictures:

 

1.png.a4bf19c452f3b4604b6fcd806ddbf79f.png2.png.9d3feecaa0104cd77d38b01ae8c6649f.png3.png.c22f075a324284990d36092fd83bbf76.png4.png.78f138f3da72004d197c1ab2fbb87ea3.png

 

5.png.7bb91f16cb8c097228aa9d2c0d5e4f19.png

 

Let me know.

 

One problem. DRAM is still under the CPU group due to the fact that is really inefficent to move it under the memory group. To do that a second call to the IntelPowerGadget.framework and its driver is needed and basically is a second call of all of its functionality. Really heavy, wont do that sorry.

 

HWMonitorSMC2.app_SMC_swift4.2_Beta1.zip

 

Working good,, but my SSD (Fujitsu F200) still not get health status

image.thumb.png.d00f9b8bfceba22c19340cdecf2aa6d4.png

  • Like 1
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted
25 minutes ago, Andres ZeroCross said:

 

Attached..

 

And this is screenshot of the HWMonitorSMC2 Alpha 9

 

Andres’s iMac.ioreg.zip

Thanks I'll take a look tomorrow

1 minute ago, Andres ZeroCross said:

Working good,, but my SSD (Fujitsu F200) still not get health status

Sorry I really did not found any specification for that. Can you show me a dump from Windows where I can take a look on the attributed used for the values you are looking for?

  • Like 1
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted
Just now, Andres ZeroCross said:

May i know "what attribute value" did you use to detect life for reguler ssd in your code?

If I knew it, I would not have asked you :wink_anim:. Usually they are under "vendor specific data" that for ATA/SATA any Vendors can place where they like since the standard allow that (allow even to omit them). 

Anyway, most of the programs that dump smart attributes usually publish the attribute for temperature, life etc.. just find one.

Link to comment
Share on other sites
Andres ZeroCross
Andres ZeroCross
Posted
Posted (edited)
11 minutes ago, vector sigma said:

If I knew it, I would not have asked you :wink_anim:. Usually they are under "vendor specific data" that for ATA/SATA any Vendors can place where they like since the standard allow that (allow even to omit them). 

Anyway, most of the programs that dump smart attributes usually publish the attribute for temperature, life etc.. just find one.

 

Just for your information, this screenshot from HWMonitor from FakeSMC

 

A. This is for ESA3SMD2ISJB120GB (Life percentage is detected with HWMonitorSMC2 too)
307880579_ScreenShot2018-10-31at04_35_37.png.5e18319c867512dcac2b79b8ea82d2bc.png


 

A. This is for Fujitsu F200 (Life percentage is not detected with HWMonitorSMC2)

1954774842_ScreenShot2018-10-31at04_37_51.png.8d9f2ce8d867fe96e37a3593a7474899.png

 

I think id 173 from F200 (Wear leveling count) is as reference for life percentage,, many SSD use id 177 as Wear Leveling Count. Sorry, just my opinion

Edited by Andres ZeroCross
Link to comment
Share on other sites
Andrey1970
Andrey1970
Posted
Posted
38 minutes ago, Andres ZeroCross said:

Moved CPU Package IGPU inside the GPU group. If the IOAccelerator's monitoring is turned on that key will be added inside the Intel sub group.

 IGPU Packages does not change the indication. 

It is not necessary to remove IGPU Packages when IOAccelerator's monitoring is turned off.

Most likely a bug because of it.

Link to comment
Share on other sites
Extreme™
Extreme™
Posted
Posted (edited)
1 hour ago, vector sigma said:

Nuova app promosso a Beta:

  1. Aggiunte nuove traduzioni in russo da Andrey1970, italiano e inglese da me.
  2. Aggiunto il controllo per Intel Potenza Gadget: CPU deve essere Intel (Lol), famiglia 6, il modello> 42, vale a dire> = 2 ° generazione di modelli di "Core". modelli Xeon 42, 46 e 47 sono supportati come vedo che possono lavorare (tasti comunque SMC se presente sarà interamente lettura).
  3. Spostato iGPU CPU pacchetto all'interno del gruppo GPU. Se il monitoraggio del IOAccelerator è acceso quel tasto verrà aggiunto all'interno del gruppo sub Intel.
  4. Ha cercato di risolvere pulsazioni del testo nella barra in alto. Hai bisogno di una conferma.
  5. Nuovo: invece di sensori di visualizzazione nella barra in alto, è ora possibile visualizzare un gadget che è possibile inserire in cui ti piace. Questo gadget è sempre in cima ad altre finestre ... in modo che ora è possibile confrontare, eseguire programmi o fare uno stress test di cosily osservando il valore desiderato. vedere le immagini:

 

1.png.a4bf19c452f3b4604b6fcd806ddbf79f.png2.png.9d3feecaa0104cd77d38b01ae8c6649f.png3.png.c22f075a324284990d36092fd83bbf76.png4.png.78f138f3da72004d197c1ab2fbb87ea3.png

 

5.png.7bb91f16cb8c097228aa9d2c0d5e4f19.png

 

Fammi sapere.

 

Un problema. DRAM è ancora sotto il gruppo di CPU a causa del fatto che in realtà è inefficent per spostarlo sotto il gruppo di memoria. Per fare questo è necessaria una seconda chiamata al IntelPowerGadget.framework e il suo driver e fondamentalmente è una seconda chiamata di tutte le sue funzionalità. Davvero pesante, non farà che mi dispiace.

 

HWMonitorSMC2.app_SMC_swift4.2_Beta1.zip

 

 

Thank you for reply and new beta Vector Sigma.

 

Tried  but pulsation effect persists:

 

https://streamable.com/8v6yx

Edited by Extreme™
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted (edited)
19 hours ago, Andres ZeroCross said:

 

Just for your information, this screenshot from HWMonitor from FakeSMC

Sorry  but, this surely is not from FakeSMC: S.M.A.R.T in macOS is a library embedded with the OS itself and the only way is to query the dedicated driver, no need to reinvent the wheel ;).

Anyway It is a losed war. If you know where they are you can read it, otherwise there are tens and tens of ssds who no one knows where to look because these values aren't mostly never published. The attribute 173 (not 177 which is already taken into account) is really uncommon from the rest of the world and in fact I have my doubts that HWSensor can read S.M.A.R.T from every ssd in commerce, and as far as I know he cannot read S.M.A.R.T from NVME while HWMonitorSMC2 can :wink_anim:.

 

Try that: HWMonitorSMC2.app_SMC_swift4.2_Beta2.zip (may be the need of more attempts if some bytewise is needed)

18 hours ago, Andrey1970 said:

Maybe it was not necessary to move IGPU Packages? 

In group CPU it worked without bug.

I forgot to add the reading when the Timer call the function that update the sensor:hysterical:

Edited by vector sigma
monitor of new values added in beta3
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted
8 minutes ago, Extreme™ said:

 

Thank you for reply and new beta Vector Sigma.

 

Tried  but pulsation effect persists:

 

https://streamable.com/8v6yx

I have a vaguely Idea on why that doesn't happen to me: I don't have the dropbox icon or any other at left. Anyway this is not simple to solve (don't tell me the old app was able because is dead and because it just use different system, in fact you now have a lot of timers instead of only one, that's the cause). I'll look into this at the week end.

  • Like 1
Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted (edited)
23 hours ago, Andrey1970 said:

Bug.

When the option "IOaccelerator" is switched off, indications the frequency igpu and a utilization igpu do not change.

I think this one is really good: HWMonitorSMC2.app_SMC_swift4.2_Beta4.zip

EDIT

 

looks at the preferences, now Intel Power Gadget must be activated.

Edited by vector sigma
Link to comment
Share on other sites
Andrey1970
Andrey1970
Posted
Posted
35 minutes ago, vector sigma said:

I think this one is really good: HWMonitorSMC2.app_SMC_swift4.2_Beta4.zip

EDIT

 

looks at the preferences, now Intel Power Gadget must be activated.

 

IGPU utilization does not work, indications only 0-1% in case of high loading IGPU. Does not work and with on, and with off option IOaccelerator.
I would like that the option an IOaccelerator was used only for the discrete GPU. IGPU let shows from IPG and sensors.

Link to comment
Share on other sites
vector sigma
vector sigma
Posted
Posted (edited)
1 hour ago, Andrey1970 said:

IGPU let shows from IPG and sensors

This is already happening. When IPG is loaded 'IGPU utilization' comes from it, or from IOAccelerator if IPG isn't loaded. but:

1 hour ago, Andrey1970 said:

I would like that the option an IOaccelerator was used only for the discrete GPU

To show nothing from who doesn't have a discrete card like my laptop? Consider that I'm not shipping the IntelPowerGadget.framework and not all the peoples may want this.

1 hour ago, Andrey1970 said:

indications only 0-1% in case of high loading IGPU

That means that this is the truth.

 

 

Please compile this program:PowerGadgetAPIExample.zip and run it. Tell me what it says.

 

Edited by vector sigma
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...