Remove caching of dT value from pt1FilterApply4

[digitalentity]

Fixes #611

[stronnag]

deleted ... wrong issue

[DzikuVx]

@digitalentity is it possible that this caching of dT was also affecting D-term filtering in PID rate controller?

[digitalentity]

Yes, I believe it's likely.
Probably the dT for the first very first PID loop is very big since it's
probably measured since zero (power-up) and accounts for all boot up
sequence.

On Mon, Sep 19, 2016 at 4:46 PM, Paweł Spychalski notifications@github.com
wrote:

@digitalentity https://github.com/digitalentity is it possible that
this caching of dT was also affecting D-term filtering in PID rate
controller?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#614 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AKi_m8gotmY1xCH1zXfXNrA0SEEWTDUzks5qrpJHgaJpZM4J_8lY
.

[DzikuVx]

That would somehow explain very big D-Term oscillations I've observed on yesterday logs. Maybe like they are not really 30Hz oscillations but an effect of aliasing (low recording speed)