97
edits
Autopilot configuration reference: Difference between revisions
Jump to navigation
Jump to search
Added <initialize-to> documentation
No edit summary |
(Added <initialize-to> documentation) |
||
| Line 163: | Line 163: | ||
<feedback-if-disabled>true</feedback-if-disabled> | <feedback-if-disabled>true</feedback-if-disabled> | ||
</syntaxhighlight> | </syntaxhighlight> | ||
=== Initial value <code><initialize-to></code> (only available for <code><filter></code> elements) === | |||
By default, on the first iteration of the autopilot / property-rule the value the filter is working with is zero. The actual input value is fetched only afterwards, and this can lead to unexpected results - for example in a rate limiting / noise-spike filter with a small maximum rate of change of say 0.5, if the input is say 25, it will take 50 seconds for the output to actually arrive at that value. If that is a problem, the <code><initialize-to></code> element can be very handy. | |||
Recognized values are: | |||
* <code>input</code>: controller will be initialized to value of the <code><input></code> element | |||
* <code>output</code>: controller will be initialized to the value of the <code><output></code> element | |||
* <code>none</code>: controller will be initialized to zero | |||
Default is <code>none</code>. | |||
=== Printing debug output <debug> === | === Printing debug output <debug> === | ||