Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
moving_average_on_avrs [2016/03/21 02:01] – [Moving Average on AVRs] Traumflug | moving_average_on_avrs [2018/05/27 16:10] (current) – external edit (unknown user) | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Moving Average on AVRs ====== | ====== Moving Average on AVRs ====== | ||
- | One problem with the controlling strategy on the [[ISTAtrol]] is thermistor readings jittering by about 1%, which is quite a lot if we want to keep the reading ( = target temperature) in a similarly tight range. As a result of this, the radiator valve is often opened or closed a bit, just because such a jittered value comes in, just to be moved back on the next reading. Not good, mechanics is subject to wear and we want to preserve our mechanics. | + | One problem with the controlling strategy on the [[ISTAtrol]] is thermistor readings jittering by about 1%, which is quite a lot if we want to keep the reading ( = target temperature) in a similarly tight range. As a result of this, the radiator valve is often opened or closed a bit because such a jittered value comes in, just to be moved back on the next reading. Not good, mechanics is subject to wear and we want to preserve our mechanics. |
There are solutions. Building better hardware is neither trivial nor free of cost, so the typical approach is to implement a **moving average algorithm**. | There are solutions. Building better hardware is neither trivial nor free of cost, so the typical approach is to implement a **moving average algorithm**. | ||
Line 62: | Line 62: | ||
</ | </ | ||
- | Code size on the ISTAtrol/ | + | Code size on the ISTAtrol/ |
moving_average_on_avrs.1458522070.txt.gz · Last modified: 2018/05/27 16:10 (external edit)