.... just a bit insulting that you ignore what I’m trying to convey and infer I don’t remember reading a 5 motor fault on my remote, have a sluggish then unpredictable response to input, have my craft fly away on its own, crash into my fence and then refuse to accept input to shut down...
First of all: I'm sorry you decided to take my reply personal and get offended; but data logs are data logs, and personal experience is always subjective.
Also the Telemetry data request is not to call you out on your recollection of events, it's because telemetry data records a lot of information that is invisible on the remote, like GPS accuracy, RSSI, yaw/pitch/roll values, remote input, etc..
Second, I meant that we could help give you more insight
other than Yuneec's:
It is a known fact for some users that Yuneec techs usually go for the "text book solution". For example you could search around for the Aircrafts shutting down in mid air issues;
@Steve Carr actually figured out what was happening to some users when, under certain specific conditions, a controller 'bug' caused the shutdown sequence to initiate and their aircrafts motors stopped mid-flight: He reached out to Yuneec, with the evidence of the fatal 'bug' which could even be replicated on their simulator, but their techs ignored all that and said
(paraphrasing) "No, people are just pressing the shutdown button while flying"
Lastly, there are a few accounts around here that are apparently made only to claim false misshaps on the Typhoon H
(some of us suspect a constant smearing campaing) and even though most members are always willing to help sometimes these accounts go silent after requesting the Telemetry data
(or are reluctant to share), either because the logs simply don't exist or because the user knows what they did wrong and don't want others to see.
I'm not saying this is your case, I'm just letting you know this happens.
Greetings