Today was a thrilling, frustrating and sad day to fly.....
I did several mission flights using EZ-GUI. The frustrating part was that RTH wouldn't engage until it reached the proper altitude. This happened a couple of days ago. So today I set
Code: Select all
//Wait to reach RTH alt before start moving to home (0-no, 1-yes)
#define WAIT_FOR_RTH_ALT 0 //(**)
and uploaded it to the controller.
Unfortunately that didn't solve the problem, which surprised me.
Then after going through EZ-GUI I stumbled on the the menu "Nav Settings" and saw the "Wait to reach RTH alt." was active even so it was set to "0" in the firmware. I think there is a code error in EZ-GUI because the firmware settings should have highest priority.
After I unchecked it in EZ-GUI RTH worked without waiting for alt to be reached. Eizo, you might want to check all the options in Nav Settings and compare them to hard coded firmware settings.
One other thing that is very annoying is when setting up missions in the mission planner every step I take I get "Protocol, Navigation is not supported by your flight controller". Please get rid of that message as I do all missions without the QC connected. I then upload each mission when I'm on the field.
Also, you spelled supported wrong, it's missing a "u"
Well, the sad part is I won't be doing any more testing until I get new parts for my QC. Yes, I knew I had very little battery power left and I knew it was very cold (3°C) but when a lady comes by you want to impress...
It didn't take 20 seconds and my QC fell from 15 meters to the ground
Only me to blame!!