osPID

Great work by Brett Beauregard  <brett  ospid.com>

Scott's Series of articles on programming a PID algorithm

  1. Sample Time - The PID algorithm functions best if it is evaluated at a regular interval. If the algorithm is aware of this interval, we can also simplify some of the internal math.
  2. Derivative Kick - Not the biggest deal, but easy to get rid of, so we’re going to do just that.
  3. On-The-Fly Tuning Changes - A good PID algorithm is one where tuning parameters can be changed without jolting the internal workings.
  4. Reset Windup Mitigation -We’ll go into what Reset Windup is, and implement a solution with side benefits
  5. On/Off (Auto/Manual) - In most applications, there is a desire to sometimes turn off the PID controller and adjust the output by hand, without the controller interfering
  6. Initialization - When the controller first turns on, we want a “bumpless transfer.” That is, we don’t want the output to suddenly jerk to some new value
  7. Controller Direction - This last one isn’t a change in the name of robustness per se. it’s designed to ensure that the user enters tuning parameters with the correct sign.

 

RocketScream is where you can get an osPID kit

 

My Evaluation Notes

  • Getting started page 
  • What to use for powering up osPID? –  standard + center pin wall wart
  • When I tried to upload software griped "must be in a particular folder" …when I only the file called out it griped "Analog button does not exist".  I put all the files in the folder the software created and it was happy.
  •  

 

 

 

 

 

 

 

 

 

You can leave a response, or trackback from your own site.

Leave a Reply