Hey there!
After playing a little bit around with Rattitude and Acro mode (I really have to get a little race quad ?) I set the third flight mode (lowest position on ST16 - switched the rth to the Aux button) back to "my normal" Mission Mode, went out to the field and wanted to do some flying in Position Mode. But directly after booting, the Thunderbird armed the motors, raised the thrust and simply flipped into the ground. No reaction to disarm, so I had to pull the battery. So I took the props away and gave it another try - normal behavior, arming after command, raising thrust on command and disarming just as it should. So I risked another try with props mounted, and again no unusual behavior, it took off, but in about 1m height I had no more response on any control input! The Thunderbird made a little move forward, turned by 90° to the right, stopped, turned again by 90° and then raised the landing gear and finally touched the ground with legs raised. At least it reacted to the disarm command.
So I returned to home, checked all values in the parameters and settings, but there's nothing - at least to me - strange to find. I reloaded the original parameter file to get back to the proven settings and went out again. Outcome's still pretty unsatisfying as it now won't arm. When hitting the flight mode switch from Position to Stabilize it instantly looses GPS and won't retrieve a position after switching back (waited for ~10 minutes).
Any ideas? Lost a little bit trust as yesterday everything was really great, I just changed the modes and suddenly everything's going south ?.
Hmm.. that's really weird stuff going on there. Sorry to hear you are having issues with it, but I am sure that we will find a way to fix them!
First of all, it should really not throttle up by itself.
No response to control input and the drone making controlled 90 degree turns looks like it is running a some kind of mission. But how did that mission end up there as they do not remain on the drone when it is restarted. Did you upload something there using QGroundcontrol? The landing gear is actuated automatically only in mission and RTH mode.
If the drone won't arm, there is something wrong with it, as there are some self-tests that the PX4 does when the drone is started. What alarms or warnings the QGroundcontrol gives when you try to arm it
without propellers and USB connected?
Position to Stabilize should not cause the GPS loss either. There is something really weird going on now - thanks for reporting these. I'll get back to developing it very soon now when autumn and winter comes (no more outdoor sports etc ;-))
After sending us the logs, to fix the drone: what would be a good idea to do, is to erase the STM32 completely and flash the first Thunderbird firmware image in the quite beginning of this thread - without mission support and see how it behaves with that?
Could you help me a little to debug this? Would it be possible for you to write a brief step-by-step instructions for me, what you did to the drone before this issue? Which settings (if you can remember) you modified, how many times, what kind of missions you flew and so on?
For now, I am going to hide this Crazy Destroyer experimental firmware for a while from here. The original non-mission-capable, well-tested and proven to be reliable Thunderbird will still of course be available. The source codes in the Git are also for it. The Crazy Destroyer will come back after a while, when I have upgraded it to the latest PX4 and figured out what's going on with it.
Edit: The RTH (or any other flight mode) on the AUX button is something I have never tried in a combination with a switch. I wonder if that has caused some confusion and weird flight mode behavior. I'll test it myself this week. ;-)
Just to make sure there is no file corruption, could you send the parameter file you are using for me, I could check that it is OK.
Br,
TR
