Absolutely correct, but I would add that in point two it will hover until control is reestablished and if not reestablished it will land at a low battery level.
Having read all your posts, Keith, I have to concur with @PatR s observations. It seems that many of your issues are to some degree self inflicted. Flying behind trees and loosing control signal is a fundamental example that any competent drone pilot should strive to avoid. Messing around with the controller settings when they don't need to be messed around with is another example of causing yourself problems.
Interesting development for me yesterday. Remember my H has only refused to come down once so far, in just over 100 flights ? Well in yesterday's session, both flights exhibited this behaviour again ! First one got stuck at 40 ft, and wouldn't come down any lower than that until I dropped the landing gear, and even then it would only descend incredibly slowly (though descend it did with throttle held to minimum). Now, I am aware of that 'feature' but not that it would ever stop my craft at 40 ft ! Isn't that normally about 12 ft where that happens ?
Anyway, I moved to another location for the second flight so the H had a chance to rest and cool down before I sent it up again. That flight went OK too, in terms of control and flight behaviour, but I found another problem as I was 'walking the hex'; that is to say the H was in D-pad forward procession mode, and I was walking behind it, manually altering yaw as it travelled forward so that it ultimately went in a very large circle around the glade I was exploring. After a few yaw inputs it became clear that the camera wasn't facing forwards any more - it was remaining pointed slightly off to the right, and then this condition remained even when right stick was stirred, and D-pad mode cancelled, and indeed it stayed like that until power down. All the time S2 was in top position, heading mode. A minor problem, but duly noted !
But now we had the landing problem again ! Gear was down this time, but the craft wouldn't go below 20 ft ! And the drift was back with a vengeance ! I didn't panic - I'm getting good at this now, so I cycled the landing gear, popped her up to 100 ft, and came down again, this time she would let me go as low as I liked, as fast as I liked - we seemed to be missing the graded descent of a normal landing. But the drift was pretty incredible now , and slightly speedier than it has been before. I released the sticks and waited for hover, but unusually, hover took a long time coming ! This rang alarm bells for me and I resolved to check my hardware monitor on the St-16 as soon as I landed - surely this level of drift was going to be caused by ropey output from aileron or similar ? But no, all stick controls were behaving flawlessly, and I tested them for a whole 5 minutes, where that continued to be the case. So that drift was not caused by sticks not returning to center, so what was it caused by I wonder ? I still had 'GPS lock', and the normal solid purple light with white flashes. Anyway, after allowing it to drift about 20 ft to see how far it would go, it eventually returned to hover and then I hand caught it without further problems.
I am going to get the telemetry from those flights and see if I can get to the bottom of what happened and why. Talking of which, found and solved another problem trying to get that. ONLY use the cable that Yuneec provide - any old USB C cable won't do !
Update: Well, telemetry showed the reason for the drifting. 100% GPS loss - nothing more or less complicated than that. When I let it drift, and it stabilized, it simply got GPS back. What it didn't do, at any point, was send my controller a message that GPS was lost, and that light never stopped being solid purple, so some confusion remains !
Interesting.Interesting development for me yesterday. Remember my H has only refused to come down once so far, in just over 100 flights ? Well in yesterday's session, both flights exhibited this behaviour again ! First one got stuck at 40 ft, and wouldn't come down any lower than that until I dropped the landing gear, and even then it would only descend incredibly slowly (though descend it did with throttle held to minimum). Now, I am aware of that 'feature' but not that it would ever stop my craft at 40 ft ! Isn't that normally about 12 ft where that happens ?
Anyway, I moved to another location for the second flight so the H had a chance to rest and cool down before I sent it up again. That flight went OK too, in terms of control and flight behaviour, but I found another problem as I was 'walking the hex'; that is to say the H was in D-pad forward procession mode, and I was walking behind it, manually altering yaw as it travelled forward so that it ultimately went in a very large circle around the glade I was exploring. After a few yaw inputs it became clear that the camera wasn't facing forwards any more - it was remaining pointed slightly off to the right, and then this condition remained even when right stick was stirred, and D-pad mode cancelled, and indeed it stayed like that until power down. All the time S2 was in top position, heading mode. A minor problem, but duly noted !
But now we had the landing problem again ! Gear was down this time, but the craft wouldn't go below 20 ft ! And the drift was back with a vengeance ! I didn't panic - I'm getting good at this now, so I cycled the landing gear, popped her up to 100 ft, and came down again, this time she would let me go as low as I liked, as fast as I liked - we seemed to be missing the graded descent of a normal landing. But the drift was pretty incredible now , and slightly speedier than it has been before. I released the sticks and waited for hover, but unusually, hover took a long time coming ! This rang alarm bells for me and I resolved to check my hardware monitor on the St-16 as soon as I landed - surely this level of drift was going to be caused by ropey output from aileron or similar ? But no, all stick controls were behaving flawlessly, and I tested them for a whole 5 minutes, where that continued to be the case. So that drift was not caused by sticks not returning to center, so what was it caused by I wonder ? I still had 'GPS lock', and the normal solid purple light with white flashes. Anyway, after allowing it to drift about 20 ft to see how far it would go, it eventually returned to hover and then I hand caught it without further problems.
I am going to get the telemetry from those flights and see if I can get to the bottom of what happened and why. Talking of which, found and solved another problem trying to get that. ONLY use the cable that Yuneec provide - any old USB C cable won't do !
Update: Well, telemetry showed the reason for the drifting. 100% GPS loss - nothing more or less complicated than that. When I let it drift, and it stabilized, it simply got GPS back. What it didn't do, at any point, was send my controller a message that GPS was lost, and that light never stopped being solid purple, so some confusion remains !
I think I am making progress here - I have gone the whole hog, and made full flight video with dashware telemetry overlays, and that has revealed some 'interesting' readings !
Not all the readings - I haven't yet worked out how to get error-state and GPS mode stats in there yet, which would show us when GPS failed, but I'm working on it...
So here's the weirdness. Before I launch I see my altitude is 0 ft, but when I start motors, that suddenly, and to my mind inexplicably, drops to -18 ft, then continues to fall as I rise !! Then we get some corresponding values as I bring it back down to just above ground level, and it stays concurrent for the rest of the flight, always about 36 ft down from where it actually was ! I'm guessing that might go some way to explaining why it wouldn't let me down without a struggle at the end of this flight (if it thought it was much nearer the ground than it was).
Of course I will link this video as soon as it has uploaded, but it's an 11 minute flight so won't be up 'til later today... but then we can all watch and wonder together !
