Hello Jeff,
I found the same bug some days ago and I reported it here on the lists.
Your solution was also my first approach, but it did not work for the
Integrator-part. The value ep_n is wrong for the next cycle.
But after a looot of testing I found this solution:
//
I seem to recall Erik commited a change to the autopilot code in the
last week or so. Does that fix something? Did that introduce a new
problem? This is pretty subtle, complex code so people shouldn't be
messing with it too much unless they are really sure they know what's
going on with it.
I was practicing landing the unlandable today, and ran into a little
emergency. It is a bit amusing and I thought I'd share it with you guys.
http://www.students.yorku.ca/~ampere/fgfs-screen-001.jpg
http://www.students.yorku.ca/~ampere/fgfs-screen-003.jpg
As you can see, there is a problem
Ahh, yes. I see your point. Since the change in output is based on
change in error (not current error), if the amount of output shift is
altered but the last error (ep_n_1) is not the two will effectively
become out of sync. In fact, the same thing must have been happening
when delta_u_n was
On Wednesday 28 September 2005 04:48, Ampere K. Hardraade wrote:
In addition, each time I press F3, two screenshots are made: one ordinary
screenshot, and another with a dialog box which looks similar to this
(http://www.students.yorku.ca/~ampere/fgfs-screen-004.jpg).
well, I hacked the code
