Thanks again for the detailed info...when I get back home in a couple weeks, I'll check mine out...Once you know what to look for the problem is easy to spot.
The opening screen in Channel Settings should look like this;
View attachment 7261
If it looks like either of these, you are in big trouble:
View attachment 7262 View attachment 7263
I called Yuneec to alert them to a flawed firmware update. They said it was impossible and that I pressed B1 which shut down the motors. They refused to look at the telemetry which clearly showed the problem. The failure occurred on final descent with yaw to the right at the same time. It dropped 180'.
So tonight I took the same controller and connected it to the flight simulator and did a quick test flight using the same control method. It did exactly the same thing every time I tried it.
Sooooo.........Yuneec........B1 was not pressed. Nope. I'm giving you a fail on CS for this one. And, oh, by the way, exactly the same thing just happened to another experience H pilot. And I confirmed it in his flight logs.
Thank you for this thread!!!I called Yuneec to alert them to a flawed firmware update. They said it was impossible and that I pressed B1 which shut down the motors. They refused to look at the telemetry which clearly showed the problem. The failure occurred on final descent with yaw to the right at the same time. It dropped 180'.
So tonight I took the same controller and connected it to the flight simulator and did a quick test flight using the same control method. It did exactly the same thing every time I tried it.
Sooooo.........Yuneec........B1 was not pressed. Nope. I'm giving you a fail on CS for this one. And, oh, by the way, exactly the same thing just happened to another experience H pilot. And I confirmed it in his flight logs.
Hey Jeff. Take another look at post #5 in this thread. I included a history before and after the update for the throttle channel. Prior to the update the minimum value of Ch0 is 662 and then drops to zero when B1 is pressed. After the update the value drops below 662 on every flight. The last flight on 6/22 was a much longer descent which is why the motors shut down as the value kept declining.noticed J3 and J4 were assigned to throttle
Hey Jeff. Take another look at post #5 in this thread. I included a history before and after the update for the throttle channel. Prior to the update the minimum value of Ch0 is 662 and then drops to zero when B1 is pressed. After the update the value drops below 662 on every flight. The last flight on 6/22 was a much longer descent which is why the motors shut down as the value kept declining.
I don't mess with Channel Settings and did not make this change. I have cautioned many times about changing them. Many months ago I did reduce the yaw rate but I did it properly. In this case it was added as a slave to J1. The second picture of the settings page was from another pilot. He did not change the setting either. His changed after the firmware update. He has been flying the H for over a year.
I have not used the wifi update method. I download the file and use it for each machine. I also don't think it's hardware related. The install jumped a cog and created a new vampire version.that begs the question of what is the root cause,
I feel badly about those as well. With many of them I simply looked at the telemetry data and could not see any problem. It doesn't show in telemetry. You have to go through the remote log to find the anomaly. Information about the remote logs is scarce so it took many hours to finally get things pinned down.Wow, I just read this Steve. Awesome job. I'm checking mine tonight. And to think of all those times we just brushed off another drop from the sky as a battery issue. I'm sure some of them were but how many more were this issue?
We use essential cookies to make this site work, and optional cookies to enhance your experience.