Well, she hit hard today on the first flight of the day from 120 ft. The plane is a skywalker 1900 and it completely went unresponsive while in FBW-A. Im using 2.72 firmware. Can anyone help asses the logs to maybe pin point the problem? I noticed a drop in voltage twice on the log, but I cant seem to tie it in with a command. I have attached the tlog. Any help would be extremely appreciated.
I don't think a brown out was your major cause of problems. As far as I can see the major issues were:
This sort of problem with MTK GPS modules is one of the reasons I released 2.73, with a check on the satellite count to stop using GPS velocity for attitude correction.
So what I think happened is this. The MTK GPS lost lock, but kept claiming lock. The AHRS DCM code kept using the (incorrect) GPS velocity numbers to correct the accelerometers. That led the DCM attitude solution to be way off. The APM thought it was level, when it fact it was rolled at 25 degrees. You had a quite low roll limit in FBWA, giving not much authority to correct the incorrect attitude.
Additional factors that made things work:
PS: As I mentioned in a private msg to you, we can go over the log in more detail together if you would like