search

jmeier64 / open-hardware-monitor

Automatically exported from code.google.com/p/open-hardware-monitor
0 stars 0 forks source link

T-Balancer BigNG reading values from Open Hardware Monitor #181

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently the T-Balancer BigNG can read values from SpeedFan and Motherboard 
Monitor, both very outdated,inferior alternatives to Open Hardware Monitor.

Since OHM can already read values from the BigNG, could it be possible that it 
feeds sensor values to BigNG, so that OHM is an one stop solution for BigNG 
owners? Maybe OHM could suply its values in a MBM compatible format so that the 
T-Balancer tools have not to be rewritten (software developement of the BigNG 
is not very fast to say it in a polite way)

Original issue reported on code.google.com by bernat.s...@gmail.com on 4 Mar 2011 at 5:13

GoogleCodeExporter commented 9 years ago 
As far as I know the T-Balancer bigNG itself can not read any values from 
SpeedFan or Motherboard Monitor. The Navigator software reads the values from 
SpeedFan or Motherboard Monitor. But the Navigator does not forward the sensor 
values as sensor values to the bigNG, but calculates fan control values from in 
software and forwards the fan control values to the bigNG hardware. This is 
done using the same interface that is used for "manual" control in the 
Navigator as well. One possible solution would be to add code to the Open 
Hardware Monitor to make it appear to the Navigator as if it was SpeedFan. But 
I personally find this approach not very nice. For successful operation it 
would need the bigNG hardware and both the Navigator and the Open Hardware 
Monitor software running.

In my opinion one needs the curve based control modes only. I plan to implement 
a control curve based controller for fan control in a general way into the Open 
Hardware Monitor. One can select one or several sensors and one fan control 
channel and define a control curve with a few points. The Open Hardware Monitor 
then reads the sensors once per second, calculates the control output and 
writes that to the fan control channel.  Beside this also manual fan control 
will be supported in the Open Hardware Monitor (this is already implemented for 
ATI GPUs in the latest alpha versions).

So for this implementation two things are still missing: The control curve 
editing user interface and an implementation for writing to the fan control 
channels of the T-Balacner bigNG. Once these two things are implemented you 
shouldn't need to Navigator anymore, except for an initial configuration of the 
settings stored in the bigNG hardware.

Original comment by moel.mich on 4 Mar 2011 at 5:58

GoogleCodeExporter commented 9 years ago 
How the software sensors work in the bigNG / Navigator has been "documented" 
here:
http://www.mcubed-tech.com/forum/showthread.php?tid=559&pid=2488#pid2488

Urlo: "Hi, Sorry for late reply. Yes you are right, in a mode with software 
sensors the TBalancer is in manual mode. The software calculates the values and 
transmits only output commands."

Original comment by moel.mich on 4 Mar 2011 at 6:15