All of lore.kernel.org
 help / color / mirror / Atom feed
From: paul@lshift.net (Paul Crowley)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] A better fan control program
Date: Wed, 28 Jun 2006 12:13:40 +0000	[thread overview]
Message-ID: <44A27274.4020909@lshift.net> (raw)
In-Reply-To: <44A2556C.7070205@lshift.net>

Mark M. Hoffman wrote:
> I skimmed through the blog entry and the earlier one which it references.
> In your first attempt you reinvented the 'P' part of a PID control loop.
> Don't give up! ;)  There's a *ton* of info about PID controllers on the
> web.  If you're still interested, you could start here:
> 
> http://en.wikipedia.org/wiki/PID_controller

Very interesting stuff, thanks!

My quick reading of this stuff indicates a possible problem.  On my 
system at least, I can only read the temperature in whole degrees; 
lm-sensors returns a number in thousandths of a degree, but sadly the 
last three digits are always zero.  This means that our differentiation 
of the temperature will be very crude, which could make it difficult to 
build a functioning PID controller.

How can I find out the maximum safe operating temperature of my current 
CPU?  Since my first priority is something that works on my current 
system, the only reason for me to pick this up again and explore in more 
detail is if I can afford to slow the fan even when the system is flat 
out, which means I need to know how fast I can run it.

Thanks again!
-- 
   [][][] Paul Crowley
     [][] LShift Ltd
   []  [] www.lshift.net


  parent reply	other threads:[~2006-06-28 12:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 10:09 [lm-sensors] A better fan control program Paul Crowley
2006-06-28 10:49 ` Mark M. Hoffman
2006-06-28 12:13 ` Paul Crowley [this message]
2006-06-30 11:19 ` Mark M. Hoffman
2006-06-30 11:32 ` Jean Delvare

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44A27274.4020909@lshift.net \
    --to=paul@lshift.net \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.