Closed GoogleCodeExporter closed 9 years ago
haha atached the wrong file, I'm sorry ;) here is the report
Original comment by darkj...@gmail.com
on 30 Jun 2010 at 4:03
Attachments:
I have taken a look at the Mainboard manual, and from what I see there it seems
that only 4 fans have the connection to be monitored. In the BIOS hardware
monitoring screenshot there are only 4 fans, and PCH_FAN (Chipset Fan Header)
seems not to have a "Sense" pin, or it is not connected (NC).
There are also only 2 temperatures in the BIOS screenshot, but I am not really
sure which 2 of the 3 are the correct ones. Why do you think there should be 3?
Could you make a screenshot of the "Gigabyte EasyTune 6" tool (when on its
hardware monitoring tab), and as good as possible at the same time save another
OpenHardwareMonitor.Report.txt. With that I should be able to add a good
mainboard specific configuration into the Open Hardware Monitor for your board.
Original comment by moel.mich
on 30 Jun 2010 at 8:56
You where right, I connected a fan and it does not show up. It was the ITE site
and the everest sensor dumps that made me think there where five:
http://www.ite.com.tw/EN/products_more.aspx?CategoryID=3&ID=5,69
you are right about the two temperatures too, but OHM does not seem to
display/find the one used for cpu-temp, only the mobo and some temp stuck at
25c.
I've made the screen and dump as you requested, also including everest sensor
page and dumps. I've also included an old it8718F specsheet, it's not for the
20, but maybe you can find out more about the it87xx in general from it.
One funny thing is that everest is reporting 12v as reg $25 * 0,016v * 4.0
192*0,016=3,072
3,072*4=12,288
that's an other way of going about it, but I like yours with the actual divider
network and reference v better...
Somehow easytune comes up with a slightly lower value, but looking at the
evererst dumps it reads from a different place? everests dumps show a separate
easytune section with the same 12v reading... also a gigabyte tmag and a des
section seem to be detected. I'm not enough in to this to get the fine details,
but maybe you can read it, so I included the dumps ...
Original comment by darkj...@gmail.com
on 30 Jun 2010 at 10:59
Attachments:
Thank you very much.
The automatically guessed configuration for mainboards was a bit bad in version
0.1.35, thats why it didn't show the third temperature sensor, also it was read
already.
I have created a new version which should now have a specific configuration for
your mainboard.
http://openhardwaremonitor.org/openhardwaremonitor-v0.1.36-alpha.zip
Please extract to a new folder or delete your old OpenHardwareMonitor.config
file first. Let me know if everything works the way it should.
Original comment by moel.mich
on 1 Jul 2010 at 8:32
Yes this looks alright. seemed the mobo was using temp 1 and 3 ;) and 2 is
unused...
looking at the source of 0.1.35 I guessed you needed to add something like this:
case Model.GA_P55_UD4:
v.Add(new Voltage("CPU VCore", 0));
v.Add(new Voltage("DRAM", 1, true));
v.Add(new Voltage("+3.3V", 2, true));
v.Add(new Voltage("+5V", 3, 6.8f, 10, 0, true));
v.Add(new Voltage("+12V", 5, 27, 9.1f, 0, true));
v.Add(new Voltage("VBat", 8));
t.Add(new Temperature("System", 0));
t.Add(new Temperature("CPU", 2));
f.Add(new Fan("CPU Fan", 0));
f.Add(new Fan("System Fan #2", 1));
f.Add(new Fan("Power Fan", 2));
f.Add(new Fan("System Fan #1", 3));
break;
have not yet looked at what you did with the new one ...
anyhow it's working, so that's great!
some thoughts:
Are you not worried that with the per mobo approach the list will soon become
an endless job to keep up with?
sure it's less confusing that the sensors unused by the board are now
permanently hidden(even with show hidden), but I kind of liked the generic
approach also... OHM just showing all the chips V and RPM's even the unused
ones... I'm perfectly capable evaluating and hiding the non used ones myself
;). maybe you could mix the generic and per mobo approach, summing up all the
sensors from the chip and then hiding the unused ones, but so that you could
still see them in 'show hidden' mode?
as for the dividers, maybe you could include some preset formula's like 0 to
+4,096V (0,1,0), +5V , -5V , +12V and -12V so you can quickly test if a value
makes sense.
oh and a feature request also came to mind:
- a reset min/max option
Regards,
Darkje
Original comment by darkj...@gmail.com
on 1 Jul 2010 at 9:23
Of course I am worried about the mainboard list approach to become an endless
job. But I don't really see any alternative.
With the version 0.1.36 and later, if the mainboard is not known it will fall
back to just showing all sensors with generic labels (and hiding most voltages
by default). This way the software will be useful even if the mainboard list is
not updated.
For a mainboard where the configuration is known I don't see any use in
displaying unconnected channels (excpet for debugging or correcting a
configuration). Maybe a command line option to force it into the generic
profile would be good for this.
Adding preset formulas is a bit a problem, because useful presets are also
mainboard specific or at least manufacturer specific. And its not so easy to
implement (because the parameters are implemented generically). Maybe its
something to add later if the whole mainboard specific configuration approach
proves useful.
Feature requests are always welcome, but please create a new issue for each
request.
Original comment by moel.mich
on 1 Jul 2010 at 10:03
Ok thank you very much. I like to play with the sensors so a debug mode would
be great.
I see about the formula's there are a few often used ones, but to many other
ones.
this issue is case closed and fixed, as far as I'm concerned. I'll post a new
one for the reset min/max option.
thanks again for answering so quick and honest!
Darkje
Original comment by darkj...@gmail.com
on 1 Jul 2010 at 10:23
Original issue reported on code.google.com by
darkj...@gmail.com
on 30 Jun 2010 at 4:01Attachments: