vector sigma Posted November 6, 2018 Share Posted November 6, 2018 5 hours ago, Andrey1970 said: Earlier I wrote that keys power, show the underestimated indications, but you to me did not check and referred to the different moments of reading. I've installed VirtualSMC so I see something wrong. Probably I was stated that you can never see the same exact thing in IntelPowerGadget.app and HWMonitorSMC due to the different start polling time interval (as I explained to someone pages back HWMonitorSMC start from 100 milliseconds instead of 50 in IPG.app), but without a try I wasn't able to see that. 5 hours ago, Andrey1970 said: I think there is which character it is not visible. I entered a new line "Purgeable" = "Очищаемая"; again and having deleted an old line "Purgeable" = "Очищаемая"; and the translation appeared. Don't know why, but this already happened multiple times, probably some hidden characters. 5 hours ago, Andrey1970 said: Now everything is correct. Good, the new app engine is a total refactoring made in swift instead of objective-c and c, and that has causing a new debugging also due to my lack of hardwares to test with, but you guys helped a lot . 1 Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2645882 Share on other sites More sharing options...
vector sigma Posted November 6, 2018 Share Posted November 6, 2018 17 hours ago, jinbingmao said: “VBAT”=？"cpu VID"=? "pch"=? VBAT is the cmos battery voltage? Really I don't know how to read it but IMHO who cares? a spare CR2032 will solve all problems, however it will work for years.. cpu VID: Is determined by Intel, but you should see the "voltage" currently in use if you have the correct kext plugin for FakeSMC or VirtualSMC. For the pch I need your SMC dump and see if you have these keys ready. Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2645885 Share on other sites More sharing options...
Andrey1970 Posted November 6, 2018 Share Posted November 6, 2018 @vector sigma It is necessary to separate a gap value and dimensionality. For example: now 1200MHz, but 1200 MHz are necessary. Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2645890 Share on other sites More sharing options...
vector sigma Posted November 6, 2018 Share Posted November 6, 2018 (edited) 5 minutes ago, Andrey1970 said: @vector sigma It is necessary to separate a gap value and dimensionality. For example: now 1200MHz, but 1200 MHz are necessary. Already tried in past and looks bad, at least not for everything. Edited November 6, 2018 by vector sigma Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2645891 Share on other sites More sharing options...
Andrey1970 Posted November 6, 2018 Share Posted November 6, 2018 (edited) 26 minutes ago, vector sigma said: Already tried in past and looks bad, at least not for everything. Bad looks or not bad looks, so it is impossible to argue. Believe me, I am an engineer and I know as correctly. The gap is not necessary only for °C and %. Edited November 6, 2018 by Andrey1970 Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2645893 Share on other sites More sharing options...
vector sigma Posted November 6, 2018 Share Posted November 6, 2018 (edited) 50 minutes ago, Andrey1970 said: I am an engineer and I know as correctly. Me as well, but what you proposed cause the top bar to contain less sensors due to additional spaces and a bad look. More for doing that we should introduce more useless calculations to ensure that 2400MHz will become 2400 MHz but 1% will remain 1% and not 1 % depending on what will be shown in the top bar or in the popover. More some existing functions that autocalculate MB and GB from bytes using Apple API already shown the correct unit.... but without spaces and I don't know how to fix as the source code is closed. If you want that for Russian why you didn't insert a space in the Localizable.strings that you give me that is enough? (but if will not work in any places due to Apple API please don't claim at me). Last night (or the day before) I'll notice that you use translated unit of measurement, but if my name is "Alessandro Volta" for us non Russian guys is a bit strange since to see our names to not be our name any more (never saw in any book here).... but we leave in peace with every one else ways of doing things. So, do you want a space also before %? EDIT ok no space for % and °C. Edited November 6, 2018 by vector sigma Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2645897 Share on other sites More sharing options...
Andrey1970 Posted November 6, 2018 Share Posted November 6, 2018 54 minutes ago, vector sigma said: Me as well, but what you proposed cause the top bar to contain less sensors due to additional spaces and a bad look. More for doing that we should introduce more useless calculations to ensure that 2400MHz will become 2400 MHz but 1% will remain 1% and not 1 % depending on what will be shown in the top bar or in the popover. More some existing functions that autocalculate MB and GB from bytes using Apple API already shown the correct unit.... but without spaces and I don't know how to fix as the source code is closed. If you want that for Russian why you didn't insert a space in the Localizable.strings that you give me that is enough? (but if will not work in any places due to Apple API please don't claim at me). Last night (or the day before) I'll notice that you use translated unit of measurement, but if my name is "Alessandro Volta" for us non Russian guys is a bit strange since to see our names to not be our name any more (never saw in any book here).... but we leave in peace with every one else ways of doing things. So, do you want a space also before %? Now I understood that the reason in a top bar. Then let remains as is. "Алессандро Вольта" - it not the translation into Russian, it is so written with the Russian alphabet, we speak in Russian "Alessandro Volta". Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2645915 Share on other sites More sharing options...
vector sigma Posted November 6, 2018 Share Posted November 6, 2018 2 minutes ago, Andrey1970 said: "Алессандро Вольта" - it not the translation into Russian, it is so written with the Russian alphabet, we speak in Russian "Alessandro Volta". For me is fine, wanted to say that in Europe the units will remain as is no matter the nationality, and was just curious how "Volta" that has medieval origins can be translated literally when the true meaning is really something else . So 'л' is 'l' 'c' is 's'. Easy now I can talk Russian 8 minutes ago, Andrey1970 said: Now I understood that the reason in a top bar. Then let remains as is. I've already done that: "+12V Bus Voltage" = "Напряжение +12 В"; "+5V Bus Voltage" = "Напряжение +5 В"; "-12V Bus Voltage" = "Напряжение -12 В"; "-5V Bus Voltage" = "Напряжение -5 В"; "3.3 VCC Voltage" = "Напряжение 3.3 В VCC"; "3.3 VSB Voltage" = "Напряжение 3.3 В VSB"; "3.3 AVCC Voltage" = "Напряжение 3.3 В AVCC"; // Units of measurement "GHz" = " GHz"; // Giga Hertz "MHz" = " МГц"; // Mega Hertz "MB" = " МБ"; // Mega byte "GB" = " GB"; // Giga byte "°C" = "°C"; // Celsius "W" = " Вт"; // Watt "mWh" = " mWh"; // milli Watt per hour "J" = " J"; // Joule "V" = " В"; // Volt "mV" = " мВ"; // milli Volt "mA" = " мА"; // milli Ampere "rpm" = " об/мин"; // revolutions per minute should I leave it as is or not? Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2645918 Share on other sites More sharing options...
Andrey1970 Posted November 6, 2018 Share Posted November 6, 2018 (edited) 33 minutes ago, vector sigma said: should I leave it as is or not? No, I looked at the top bar, it looks bad. Correct please "GHz" = "ГГц" "GB" = "ГБ" "mWh" = "мВт⋅ч" "J" = "Дж" Edited November 6, 2018 by Andrey1970 Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2645925 Share on other sites More sharing options...
vector sigma Posted November 6, 2018 Share Posted November 6, 2018 Done. Tomorrow I'll commit all the changes, but now I want a beer with friends. See you. 1 Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2645929 Share on other sites More sharing options...
jinbingmao Posted November 6, 2018 Share Posted November 6, 2018 (edited) 6 hours ago, vector sigma said: VBAT is the cmos battery voltage? Really I don't know how to read it but IMHO who cares? a spare CR2032 will solve all problems, however it will work for years.. cpu VID: Is determined by Intel, but you should see the "voltage" currently in use if you have the correct kext plugin for FakeSMC or VirtualSMC. For the pch I need your SMC dump and see if you have these keys ready. SMC DUMP: key: #KEY, size: 04, type: ui32, attr: 00, value: <0000005d> key: $Num, size: 01, type: ui8 , attr: 00, value: <01> key: ACID, size: 08, type: ch8*, attr: 00, value: <babe3c45 c0031043> key: ALI0, size: 04, type: {ali, attr: 00, value: <06010200> key: ALRV, size: 02, type: ui16, attr: 00, value: <0001> key: ALV0, size: 10, type: {alv, attr: 00, value: <010103b7 00a30015 6af4> key: CLKH, size: 08, type: {clh, attr: 00, value: <00007080 00011940> key: CLKT, size: 04, type: ui32, attr: 00, value: <00005a60> key: EPCI, size: 04, type: flag, attr: 00, value: <07b0f000> key: FNum, size: 01, type: ui8 , attr: 00, value: <02> key: LSOF, size: 01, type: flag, attr: 00, value: <01> key: LSSB, size: 02, type: {lso, attr: 00, value: <0101> key: LsNM, size: 01, type: ui8 , attr: 00, value: <01> key: LsbV, size: 05, type: {rev, attr: 00, value: <01040a00 06> key: MOST, size: 02, type: ui16, attr: 00, value: <8003> key: MSDW, size: 01, type: ui8 , attr: 00, value: <01> key: MSPS, size: 01, type: {msp, attr: 00, value: <00> key: MSSD, size: 01, type: si8 , attr: 00, value: <03> key: NATJ, size: 01, type: ui8 , attr: 00, value: <02> key: NTOK, size: 01, type: ui8 , attr: 00, value: <01> key: NVPR, size: 01, type: ui8 , attr: 00, value: <00> key: OSK0, size: 32, type: ch8*, attr: 00, value: <6f757268 61726477 6f726b62 79746865 7365776f 72647367 75617264 6564706c> key: OSK1, size: 32, type: ch8*, attr: 00, value: <65617365 646f6e74 73746561 6c286329 4170706c 65436f6d 70757465 72496e63> key: REV , size: 06, type: {rev, attr: 00, value: <02300f00 0002> key: RMde, size: 01, type: char, attr: 00, value: <41> key: RPlt, size: 08, type: ch8*, attr: 00, value: <74390000 00000000> key: RBr , size: 08, type: ch8*, attr: 00, value: <7439006a 31370000> key: BEMB, size: 01, type: flag, attr: 00, value: <01> key: NATi, size: 02, type: ui16, attr: 00, value: <001e> key: TC0D, size: 02, type: sp78, attr: 00, value: <2000> key: FRC0, size: 02, type: freq, attr: 00, value: <06a4> key: VC0C, size: 02, type: fp2e, attr: 00, value: <3687> key: TC1D, size: 02, type: sp78, attr: 00, value: <1600> key: FRC1, size: 02, type: freq, attr: 00, value: <06a4> key: TC2D, size: 02, type: sp78, attr: 00, value: <1700> key: FRC2, size: 02, type: freq, attr: 00, value: <06a4> key: TC3D, size: 02, type: sp78, attr: 00, value: <1a00> key: FRC3, size: 02, type: freq, attr: 00, value: <06a4> key: MPkC, size: 02, type: ui16, attr: 00, value: <aa00> key: TN0P, size: 02, type: sp78, attr: 00, value: <1600> key: Th0H, size: 02, type: sp78, attr: 00, value: <1b00> key: TA0P, size: 02, type: sp78, attr: 00, value: <1300> key: Vp3C, size: 02, type: fp2e, attr: 00, value: <d883> key: VP0R, size: 02, type: sp4b, attr: 00, value: <61eb> key: Vp1C, size: 02, type: sp4b, attr: 00, value: <290a> key: VS0C, size: 02, type: fp2e, attr: 00, value: <7333> key: VM0R, size: 02, type: fp2e, attr: 00, value: <5f3b> key: Vp4C, size: 02, type: fp2e, attr: 00, value: <d70a> key: VBAT, size: 02, type: fp2e, attr: 00, value: <c937> key: F0Ac, size: 02, type: fpe2, attr: 00, value: <0fbc> key: F0ID, size: 16, type: {fds, attr: 00, value: <00010000 43505520 e9a38ee6 89870000> key: F0Tg, size: 01, type: ui8 , attr: 00, value: <82> key: F0St, size: 01, type: ui8 , attr: 00, value: <14> key: F0Ss, size: 01, type: ui8 , attr: 00, value: <00> key: F0Ft, size: 01, type: ui8 , attr: 00, value: <41> key: F0Pt, size: 01, type: ui8 , attr: 00, value: <46> key: F0Fo, size: 01, type: ui8 , attr: 00, value: <03> key: F0Ct, size: 01, type: ui8 , attr: 00, value: <1c> key: F1Tg, size: 01, type: ui8 , attr: 00, value: <80> key: F1St, size: 01, type: ui8 , attr: 00, value: <14> key: F1Ss, size: 01, type: ui8 , attr: 00, value: <00> key: F1Ft, size: 01, type: ui8 , attr: 00, value: <32> key: F1Pt, size: 01, type: ui8 , attr: 00, value: <46> key: F1Fo, size: 01, type: ui8 , attr: 00, value: <03> key: F1Ct, size: 01, type: ui8 , attr: 00, value: <1c> key: F1Ac, size: 02, type: fpe2, attr: 00, value: <0554> key: F1ID, size: 16, type: {fds, attr: 00, value: <00010035 e590b8e6 b094e9a3 8ee68987> key: F2Tg, size: 01, type: ui8 , attr: 00, value: <80> key: F2St, size: 01, type: ui8 , attr: 00, value: <14> key: F2Ss, size: 01, type: ui8 , attr: 00, value: <00> key: F2Ft, size: 01, type: ui8 , attr: 00, value: <32> key: F2Pt, size: 01, type: ui8 , attr: 00, value: <46> key: F2Fo, size: 01, type: ui8 , attr: 00, value: <03> key: F2Ct, size: 01, type: ui8 , attr: 00, value: <1c> key: F3Tg, size: 01, type: ui8 , attr: 00, value: <02> key: F3St, size: 01, type: ui8 , attr: 00, value: <00> key: F3Ss, size: 01, type: ui8 , attr: 00, value: <ff> key: F3Ft, size: 01, type: ui8 , attr: 00, value: <00> key: F3Pt, size: 01, type: ui8 , attr: 00, value: <00> key: F3Fo, size: 01, type: ui8 , attr: 00, value: <00> key: F3Ct, size: 01, type: ui8 , attr: 00, value: <ff> key: F4Tg, size: 01, type: ui8 , attr: 00, value: <30> key: F4St, size: 01, type: ui8 , attr: 00, value: <97> key: F4Ss, size: 01, type: ui8 , attr: 00, value: <40> key: F4Ft, size: 01, type: ui8 , attr: 00, value: <00> key: F4Pt, size: 01, type: ui8 , attr: 00, value: <00> key: F4Fo, size: 01, type: ui8 , attr: 00, value: <eb> key: F4Ct, size: 01, type: ui8 , attr: 00, value: <40> key: FMCL, size: 01, type: ui8 , attr: 00, value: <77> key: FMCR, size: 01, type: ui8 , attr: 00, value: <c7> key: TG0D, size: 02, type: sp78, attr: 00, value: <1d00> key: QENA, size: 01, type: ui8 , attr: 00, value: <01> key: HE0N, size: 01, type: ui8 , attr: 00, value: <10> "Pxh" is there, I'm sorry!！ Edited November 7, 2018 by jinbingmao Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2645941 Share on other sites More sharing options...
vector sigma Posted November 7, 2018 Share Posted November 7, 2018 (edited) 20 hours ago, jinbingmao said: SMC DUMP: key: #KEY, size: 04, type: ui32, attr: 00, value: <0000005d> key: $Num, size: 01, type: ui8 , attr: 00, value: <01> key: ACID, size: 08, type: ch8*, attr: 00, value: <babe3c45 c0031043> key: ALI0, size: 04, type: {ali, attr: 00, value: <06010200> key: ALRV, size: 02, type: ui16, attr: 00, value: <0001> key: ALV0, size: 10, type: {alv, attr: 00, value: <010103b7 00a30015 6af4> key: CLKH, size: 08, type: {clh, attr: 00, value: <00007080 00011940> key: CLKT, size: 04, type: ui32, attr: 00, value: <00005a60> key: EPCI, size: 04, type: flag, attr: 00, value: <07b0f000> key: FNum, size: 01, type: ui8 , attr: 00, value: <02> key: LSOF, size: 01, type: flag, attr: 00, value: <01> key: LSSB, size: 02, type: {lso, attr: 00, value: <0101> key: LsNM, size: 01, type: ui8 , attr: 00, value: <01> key: LsbV, size: 05, type: {rev, attr: 00, value: <01040a00 06> key: MOST, size: 02, type: ui16, attr: 00, value: <8003> key: MSDW, size: 01, type: ui8 , attr: 00, value: <01> key: MSPS, size: 01, type: {msp, attr: 00, value: <00> key: MSSD, size: 01, type: si8 , attr: 00, value: <03> key: NATJ, size: 01, type: ui8 , attr: 00, value: <02> key: NTOK, size: 01, type: ui8 , attr: 00, value: <01> key: NVPR, size: 01, type: ui8 , attr: 00, value: <00> key: OSK0, size: 32, type: ch8*, attr: 00, value: <6f757268 61726477 6f726b62 79746865 7365776f 72647367 75617264 6564706c> key: OSK1, size: 32, type: ch8*, attr: 00, value: <65617365 646f6e74 73746561 6c286329 4170706c 65436f6d 70757465 72496e63> key: REV , size: 06, type: {rev, attr: 00, value: <02300f00 0002> key: RMde, size: 01, type: char, attr: 00, value: <41> key: RPlt, size: 08, type: ch8*, attr: 00, value: <74390000 00000000> key: RBr , size: 08, type: ch8*, attr: 00, value: <7439006a 31370000> key: BEMB, size: 01, type: flag, attr: 00, value: <01> key: NATi, size: 02, type: ui16, attr: 00, value: <001e> key: TC0D, size: 02, type: sp78, attr: 00, value: <2000> key: FRC0, size: 02, type: freq, attr: 00, value: <06a4> key: VC0C, size: 02, type: fp2e, attr: 00, value: <3687> key: TC1D, size: 02, type: sp78, attr: 00, value: <1600> key: FRC1, size: 02, type: freq, attr: 00, value: <06a4> key: TC2D, size: 02, type: sp78, attr: 00, value: <1700> key: FRC2, size: 02, type: freq, attr: 00, value: <06a4> key: TC3D, size: 02, type: sp78, attr: 00, value: <1a00> key: FRC3, size: 02, type: freq, attr: 00, value: <06a4> key: MPkC, size: 02, type: ui16, attr: 00, value: <aa00> key: TN0P, size: 02, type: sp78, attr: 00, value: <1600> key: Th0H, size: 02, type: sp78, attr: 00, value: <1b00> key: TA0P, size: 02, type: sp78, attr: 00, value: <1300> key: Vp3C, size: 02, type: fp2e, attr: 00, value: <d883> key: VP0R, size: 02, type: sp4b, attr: 00, value: <61eb> key: Vp1C, size: 02, type: sp4b, attr: 00, value: <290a> key: VS0C, size: 02, type: fp2e, attr: 00, value: <7333> key: VM0R, size: 02, type: fp2e, attr: 00, value: <5f3b> key: Vp4C, size: 02, type: fp2e, attr: 00, value: <d70a> key: VBAT, size: 02, type: fp2e, attr: 00, value: <c937> key: F0Ac, size: 02, type: fpe2, attr: 00, value: <0fbc> key: F0ID, size: 16, type: {fds, attr: 00, value: <00010000 43505520 e9a38ee6 89870000> key: F0Tg, size: 01, type: ui8 , attr: 00, value: <82> key: F0St, size: 01, type: ui8 , attr: 00, value: <14> key: F0Ss, size: 01, type: ui8 , attr: 00, value: <00> key: F0Ft, size: 01, type: ui8 , attr: 00, value: <41> key: F0Pt, size: 01, type: ui8 , attr: 00, value: <46> key: F0Fo, size: 01, type: ui8 , attr: 00, value: <03> key: F0Ct, size: 01, type: ui8 , attr: 00, value: <1c> key: F1Tg, size: 01, type: ui8 , attr: 00, value: <80> key: F1St, size: 01, type: ui8 , attr: 00, value: <14> key: F1Ss, size: 01, type: ui8 , attr: 00, value: <00> key: F1Ft, size: 01, type: ui8 , attr: 00, value: <32> key: F1Pt, size: 01, type: ui8 , attr: 00, value: <46> key: F1Fo, size: 01, type: ui8 , attr: 00, value: <03> key: F1Ct, size: 01, type: ui8 , attr: 00, value: <1c> key: F1Ac, size: 02, type: fpe2, attr: 00, value: <0554> key: F1ID, size: 16, type: {fds, attr: 00, value: <00010035 e590b8e6 b094e9a3 8ee68987> key: F2Tg, size: 01, type: ui8 , attr: 00, value: <80> key: F2St, size: 01, type: ui8 , attr: 00, value: <14> key: F2Ss, size: 01, type: ui8 , attr: 00, value: <00> key: F2Ft, size: 01, type: ui8 , attr: 00, value: <32> key: F2Pt, size: 01, type: ui8 , attr: 00, value: <46> key: F2Fo, size: 01, type: ui8 , attr: 00, value: <03> key: F2Ct, size: 01, type: ui8 , attr: 00, value: <1c> key: F3Tg, size: 01, type: ui8 , attr: 00, value: <02> key: F3St, size: 01, type: ui8 , attr: 00, value: <00> key: F3Ss, size: 01, type: ui8 , attr: 00, value: <ff> key: F3Ft, size: 01, type: ui8 , attr: 00, value: <00> key: F3Pt, size: 01, type: ui8 , attr: 00, value: <00> key: F3Fo, size: 01, type: ui8 , attr: 00, value: <00> key: F3Ct, size: 01, type: ui8 , attr: 00, value: <ff> key: F4Tg, size: 01, type: ui8 , attr: 00, value: <30> key: F4St, size: 01, type: ui8 , attr: 00, value: <97> key: F4Ss, size: 01, type: ui8 , attr: 00, value: <40> key: F4Ft, size: 01, type: ui8 , attr: 00, value: <00> key: F4Pt, size: 01, type: ui8 , attr: 00, value: <00> key: F4Fo, size: 01, type: ui8 , attr: 00, value: <eb> key: F4Ct, size: 01, type: ui8 , attr: 00, value: <40> key: FMCL, size: 01, type: ui8 , attr: 00, value: <77> key: FMCR, size: 01, type: ui8 , attr: 00, value: <c7> key: TG0D, size: 02, type: sp78, attr: 00, value: <1d00> key: QENA, size: 01, type: ui8 , attr: 00, value: <01> key: HE0N, size: 01, type: ui8 , attr: 00, value: <10> "Pxh" is there, I'm sorry!！ Hi, I did not yet investigate your SMC dump, but is the above picture coming from Aida in Windows as I suspect? If yes I'm very sorry that Hackintoshes produces tiny informations about your hardware, but the fact is that if we need something almost always we have to write a driver from scratch. Example for VBAT: PC = CMOS battery (value ready to be read) Mac = PRAM battery (published by SMC?? I don't think) Hackintosh = CMOS battery ?? pity, how to read? The same for GPU Power and voltages. in Windows is ready to be read, but in macOS need a driver to be written by someone. Geforce & ATI plugins should show something when the hardware is known, but that should be a job for Slice as I haven't knowledge in this area. You enlight the "-5 volts bus voltage", what is wrong? The "wording" looks more correct than in Aida to me since is a differential voltage that should let you understand if there is a short to ground or else. Basically on a hackintosh everithing must be written. Later or tomorrow I'll study your dump to see if there is something usefull to be added to the app. Edited November 7, 2018 by vector sigma typos Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646085 Share on other sites More sharing options...
jinbingmao Posted November 7, 2018 Share Posted November 7, 2018 2 hours ago, vector sigma said: Hi, I did not yet investigate your SMC dump, but is the above picture coming from Aida in Windows as I suspect? If yes I'm very sorry that Hackintoshes produces tiny informations about your hardware,but the fact is that if we need something almost always we have to write a driver from scratch. Example for VBAT: PC = CMOS battery (value ready to be read) Mac = PRAM battery (published by SMC?? I don't think) Hackintosh = CMOS battery ?? pity, how to read? The same for GPU Power and voltages. in Windows is ready to be read, but in macOS need a driver to be written by someone. Geforce & ATI plugins should show something when the hardware is known, but that should be a job for Slice as I haven't knowledge in this area. You enlight the "-5 volts bus voltage", what is wrong? The "wording" looks more correct than in Aida to me since is a differential voltage that should let you understand if there is a short to ground or else. Basically on a hackintosh everithing must be written. Later or tomorrow I'll study your dump to see if there is something usefull to be added to the app. You said all right! I see. Thanks for your help! 1 Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646150 Share on other sites More sharing options...
losinka Posted November 7, 2018 Share Posted November 7, 2018 The second graphic card (Thunderbolt-3 Vega FE) shows the wrong information - same as on the main graphic card (Vega RX 64). 0rpm on the RX Vega 64 - correct. Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646163 Share on other sites More sharing options...
vector sigma Posted November 7, 2018 Share Posted November 7, 2018 1 hour ago, losinka said: The second graphic card (Thunderbolt-3 Vega FE) shows the wrong information - same as on the main graphic card (Vega RX 64). 0rpm on the RX Vega 64 - correct. Please, post a ioreg Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646182 Share on other sites More sharing options...
losinka Posted November 8, 2018 Share Posted November 8, 2018 20 hours ago, vector sigma said: Please, post a ioreg attached. Thank you! 2xGPU.ioreg.zip Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646417 Share on other sites More sharing options...
vector sigma Posted November 9, 2018 Share Posted November 9, 2018 22 hours ago, losinka said: attached. Thank you! 2xGPU.ioreg.zip Thanks, tomorrow I'll give you a test application to dump some info and let me understand better what to do. See you tomorrow. Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646668 Share on other sites More sharing options...
vector sigma Posted November 10, 2018 Share Posted November 10, 2018 On 11/8/2018 at 8:08 PM, losinka said: attached. Thank you! 2xGPU.ioreg.zip Hi. Please create a directory in to your Desktop called HWGraphics, this will enable the dump of graphics cards info using the IO. Use the attached app, the dump will occour once at the application start up. Post here the entire directory. @jinbingmao (and anyone intrested), I've added back some sensors reading, please tell me if you notice them (cpu proximity/Heatsink/North Bridge temperature, VBAT voltage (i.e. Battery under "Motherboards"), GPUs proximity temperature, GPU memory frequency. ... (require these keys to be existing). Corrected some typos. HWMonitorSMC2.app_debug_IO_1.zip Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646871 Share on other sites More sharing options...
jinbingmao Posted November 10, 2018 Share Posted November 10, 2018 1 hour ago, vector sigma said: 你好。请在桌面中创建名为HWGraphics的目录，这将使用IO启用图形卡信息的转储。使用附加的应用程序，转储将在应用程序启动时出现一次。在这里发布整个目录。 @jinbingmao （以及任何有兴趣的人），我添加了一些传感器读数，请告诉我你是否注意到它们（cpu proximity / Heatsink / North Bridge温度，VBAT电压（即“主板”下的电池），GPU接近温度，GPU记忆频率......（要求这些密钥存在）。纠正了一些拼写错误。 HWMonitorSMC2.app_debug_IO_1.zip 1 Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646886 Share on other sites More sharing options...
vector sigma Posted November 10, 2018 Share Posted November 10, 2018 @jinbingmao, can I have a translation for: "North Bridge" = "North Bridge"; "Total Power" = "Total Power"; "Total Power" is referred to the Watts consumed by the GPU. And, is Battery correct? "Battery" = "电池"; // singular Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646889 Share on other sites More sharing options...
jinbingmao Posted November 10, 2018 Share Posted November 10, 2018 Just now, vector sigma said: @jinbingmao, can I have a translation for: "North Bridge" = "North Bridge"; "Total Power" = "Total Power"; "Total Power" is referred to the Watts consumed by the GPU. And, is Battery correct? "Battery" = "电池"; // singular "Total Power"="显卡总功率" "North Bridge"="北桥" "Battery"="coms电池" 5 minutes ago, vector sigma said: @jinbingmao, can I have a translation for: "North Bridge" = "North Bridge"; "Total Power" = "Total Power"; "Total Power" is referred to the Watts consumed by the GPU. And, is Battery correct? "Battery" = "电池"; // singular Revise Localizable.strings.zip 1 Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646890 Share on other sites More sharing options...
jinbingmao Posted November 10, 2018 Share Posted November 10, 2018 "Intel(R) Power Gadget" can not show Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646892 Share on other sites More sharing options...
vector sigma Posted November 10, 2018 Share Posted November 10, 2018 (edited) test it: HWMonitorSMC2.app_debug_2.zip 7 minutes ago, jinbingmao said: "Intel(R) Power Gadget" can not show Sorry but what do you mean? Is a empty group? Edited November 10, 2018 by vector sigma Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646894 Share on other sites More sharing options...
jinbingmao Posted November 10, 2018 Share Posted November 10, 2018 (edited) 20分钟前，矢量西格玛说： 测试它： HWMonitorSMC2.app_debug_2.zip 对不起，你是什么意思？是空团吗？ Edited November 10, 2018 by jinbingmao latter version is not Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646897 Share on other sites More sharing options...
vector sigma Posted November 10, 2018 Share Posted November 10, 2018 Please write in your language what do you think is a problem. I will use the translator... Link to comment https://www.insanelymac.com/forum/topic/299861-hwsensors3/page/53/#findComment-2646898 Share on other sites More sharing options...
Recommended Posts