Hello Fellow Yuneec Pilot!
Join our free Yuneec community and remove this annoying banner!
Sign up

The Last Straw....

If you search for 'flyaway' or 'loss of control' and any drone name, you'll find reports. It does happen - radio control devices are not 100% perfect. By your criteria, we wouldn't have a single flying drone in the sky right now.

Yep, Tuna, it is funny, ironic at least, that some here insist on promoting competitive products and bashing Yuneec.

If you take a quick trip to any of the DJI forums, you find most of the same problems from Phantom owners: TBE, dropping from sky, FW update problems, 3rd bad copter in a row, OA not working, bad new batteries, company refusal to help, and on and on. As you and others have pointed out, a large number of these problems turn out to have been self-generated by owners.
 
  • Like
Reactions: Tuna
A big difference between Karma and the Typhoon is where the corporate offices are located. If a Karma falls out of the sky and kills someone Go Pro gets sued big time. If a Typhoon did the same they could pack up the U.S. operation and go home. There's virtually zero chance of litigating them for product liability.


Sent from my iPhone using Tapatalk
 
  • Like
Reactions: Markinter
I much prefer to just grab it out of the air - I could never do that with my single rotor helis or race quads!
So you replied to a very long post with a quick statement that doesn't reference what you "would never do". Just a bit ambiguous. Are you saying you would never land the bird as normal and you always grab it out of the air?
 
I've had it with the Typhoon H. Today was the last straw. I'm done...

Yesterday I took it out to ensure the 3.01 upgrade didn't degrade anything and that my "recovery" process from the "H" bricking after the OTA update failed in the middle of updating. Too cold out to do more than a battery pack. But other than a slight drift, everything "seemed" to be okay.

Today, took it out, did all my usual pre-flight checks to include the weather and Kp Index. Ensured everything looked good before taking off. As I powered on my ST16 I heard a loud whining noise. Bad fans! I decided to go ahead and fly. Immediately after take-off, about 4 feet out and 6 feet up, the ST16 vibrated getting my attention, I look down and see something about GPS lost, put in angle mode, return home and perform a CC. I didn't catch all of the message as I looked up to make sure the H wasn't drifting in a bad direction. I could see the status light flashing orange. I landed the H and performed a CC.

Thing is I was in angle mode. Part of my Pre-flight checklist is to ensure all switches and nobs are in my desired starting position which includes being in angle mode.

Flew around. Checked out some of the 3.0 features and exercised different switches and buttons. Everything seemed fine with the exception of a slight drift at about 6' (not prop-wash). Battery got down to 14.6 volts so I started manual landing. I knew the 3.01 was supposed to make landing better, but mine seemed to be a bit super sensitive to stick inputs. As it touched down, with the left stick "full down", the motors started to slow but then suddenly the H tipped backwards and the motors started spinning up. I started to worry it was going to tip backwards, but the motors slowed, the front came down and it idled down. I thought it weird...

So I put the second battery in, did my usual check before doing anything and did several landings. Everything seemed fine. It still seemed sensitive to stick inputs but nothing weird. Flew it around and when the battery reached 14.6 volts I started to land it. As it touched down, it started to tilt forward. I thought WTF? so I gave it "throttle" to lift off and it did. I spun it around then attempted to land again. It touched down and leaned forward without the motors starting to idle down, it was going over. I pulled right stick back in attempt pivot it backwards and gave it throttle in attempt to lift off. No luck. It just went forward breaking the two front props and flipping over. It also put a small crack at a seam in the rear of the bird near the battery housing.

I'm just so done with this drone. You can search my posts and find the issues I've had with this one and the first one I owned which was bad from the beginning. I'm no noob to R/C or drones, I've got an Inspire and a P4 which has not given one serious problem. I've also had a Q500 which was problem free. I've spent more time doing check-out flights with this drone than actual photo opportunities. I can't ever tell how this drone will react to firmware upgrades, some upgrades are fine other degrade it. Its been back to Yuneec to have the GPS Module replaced. I just don't trust this thing.

Its on its way back to Yuneec yet again. I don't know if they'll find anything... Been on this forum for ages. Seems like us early adopters have the problematic drones. Captain Drone, Drone Clone, and myself, just to name a few.

I'm very disappointed in this drone. I really liked everything it has to offer. When it works its nice, I've got some great pictures with it. Yuneec CS is great. We talked and length and they'll take a look. I'm not hopeful though because this tipping issue was not consistent.

But with all that said, I'm done. I need something that I can rely on flight after flight, upgrade after upgrade. I get small issues, but not this.

When it comes back IF they've repaired it, I'm still done, I'm going to see if someone may be interested in purchasing it locally at a greatly reduced price with full disclosure. If its not repaired, I'm going to put in on a shelf as a hard lesson learned. I won't say I'm done with Yuneec. If they can get their quality control sorted and offer a drone that does what I want, I'll be back...

Oh and guess what came today? The RS module.... I don't know if I'll be able to return it. If not stay tuned, I'll be selling it for 250.00 shipped anywhere in the lower 48....
 
Don't ever think about trying to sell your H's. I have been trying to sell, priced LOW, zero interest. Only RC item in 15 years I can't sell.
If you're still selling, how much do you want for it? I have a couple but could use a back up to my back up.
 
So you replied to a very long post with a quick statement that doesn't reference what you "would never do". Just a bit ambiguous. Are you saying you would never land the bird as normal and you always grab it out of the air?

Yes, by stating that "I much prefer to just grab it out of the air", I meant that, if not precluded by uncontrollable circumstances, I'd always (all things being equal) grab, catch, or otherwise arrest my Typhoon H whilst still airborne, and not land the craft "normally", by lowering the craft to the deck, tarmac, ground, street, etc....

Sorry for the ambiguity.
 
I hear what your saying. The last couple of days my TH has been giving me issues. It starts flying in circle on it's own. I can fly for a few minute without issue and then suddenly it starts flying in a circle and continues to fly in a circle while I'm trying to land.

I was going to use it for a project, but the range just wasn't there. I bought a Maverick and so far it works great. I still have my TH and Q500. I'm just adding to my collection. I hope I can get the circling issue resolved. And yes I have done all calibrations.
 
Yeah so I had two landing accidents in the past week with one of my Typhoon H Pro's (haven't flown the other yet). I will say these weren't ideal locations but the same thing happened in two completely different scenarios. One was on the pool level (8th floor, 180 degree horizontal/vertical clearance, 11-14 satellites) of the high-rise I live in and the other was in my inside my condo (22nd floor/18 floors above me). Both cases the bird behaved in the same manner while landing.

I launched to a height of less than 10 feet, hovered for a few seconds, manually brought the bird down and was about to turn off the ST16. The motors all of a sudden throttled and the bird rose up a foot and flew to the right (side ways) several feet before it hit something and busting up a couple of props. Indoors it flew to the left, which adds to my confusion. I was in Angle mode and didn't mess with GPS. I exacerbated the situation by having the bird in the rabbit position...just a bad habit that I didn't pay attention to.

I need to check what version I'm running on everything but I can say the ST16 is running b27 (the latest is b30). I didn't have this issue before, which I think, tells me updating won't fix the problem. I'm hoping there is some logic I haven't thought of that will point in that direction because obviously that's an easy fix. The only other thing is the conditions in which I did this test launch weren't ideal but completely different. I'm in Midtown Atlanta, so other than a busy nearby park, I have to drive a good distance to get to a more ideal location...before taking a 60 minute round trip, I'd really like to have some confidence in my aircraft.

Thoughts anyone...Bueller?
 
Sudden changes in air pressure will confuse the Typhoon barometer, which can cause it to try and lift off again (it thinks it's dropping altitude). Flying indoors is susceptible to this (think of the change in air pressure when someone slams a door on your level), and flying in heavily built up areas can also cause problems (sudden gusts between buildings). When it lifts off, it will also try to maintain a constant GPS location, which can have drifted a small amount whilst it was landed - so you get the drone flying off to one side.

The answer is to hold throttle down and kill the motors as soon as you have landed. Keep the throttle held down until the motors have stopped.

Some firmware versions may be more susceptible to this than others, but the main cause is the physical situation that you're flying in. Once you have landed, don't leave the motors idling any longer than you have to, particularly when you're flying in difficult locations. This isn't a GPS problem.
 
Sudden changes in air pressure will confuse the Typhoon barometer, which can cause it to try and lift off again (it thinks it's dropping altitude). Flying indoors is susceptible to this (think of the change in air pressure when someone slams a door on your level), and flying in heavily built up areas can also cause problems (sudden gusts between buildings). When it lifts off, it will also try to maintain a constant GPS location, which can have drifted a small amount whilst it was landed - so you get the drone flying off to one side.

The answer is to hold throttle down and kill the motors as soon as you have landed. Keep the throttle held down until the motors have stopped.

Some firmware versions may be more susceptible to this than others, but the main cause is the physical situation that you're flying in. Once you have landed, don't leave the motors idling any longer than you have to, particularly when you're flying in difficult locations. This isn't a GPS problem.

You say: "Keep the throttle held down until the motors have stopped." Keeping the throttle stick down will reduce prop RPM from flight idle to ground idle. To stop the motors you have to press the red button (#1).
 
I've had it with the Typhoon H. Today was the last straw. I'm done...

Yesterday I took it out to ensure the 3.01 upgrade didn't degrade anything and that my "recovery" process from the "H" bricking after the OTA update failed in the middle of updating. Too cold out to do more than a battery pack. But other than a slight drift, everything "seemed" to be okay.

Today, took it out, did all my usual pre-flight checks to include the weather and Kp Index. Ensured everything looked good before taking off. As I powered on my ST16 I heard a loud whining noise. Bad fans! I decided to go ahead and fly. Immediately after take-off, about 4 feet out and 6 feet up, the ST16 vibrated getting my attention, I look down and see something about GPS lost, put in angle mode, return home and perform a CC. I didn't catch all of the message as I looked up to make sure the H wasn't drifting in a bad direction. I could see the status light flashing orange. I landed the H and performed a CC.

Thing is I was in angle mode. Part of my Pre-flight checklist is to ensure all switches and nobs are in my desired starting position which includes being in angle mode.

Flew around. Checked out some of the 3.0 features and exercised different switches and buttons. Everything seemed fine with the exception of a slight drift at about 6' (not prop-wash). Battery got down to 14.6 volts so I started manual landing. I knew the 3.01 was supposed to make landing better, but mine seemed to be a bit super sensitive to stick inputs. As it touched down, with the left stick "full down", the motors started to slow but then suddenly the H tipped backwards and the motors started spinning up. I started to worry it was going to tip backwards, but the motors slowed, the front came down and it idled down. I thought it weird...

So I put the second battery in, did my usual check before doing anything and did several landings. Everything seemed fine. It still seemed sensitive to stick inputs but nothing weird. Flew it around and when the battery reached 14.6 volts I started to land it. As it touched down, it started to tilt forward. I thought WTF? so I gave it "throttle" to lift off and it did. I spun it around then attempted to land again. It touched down and leaned forward without the motors starting to idle down, it was going over. I pulled right stick back in attempt pivot it backwards and gave it throttle in attempt to lift off. No luck. It just went forward breaking the two front props and flipping over. It also put a small crack at a seam in the rear of the bird near the battery housing.

I'm just so done with this drone. You can search my posts and find the issues I've had with this one and the first one I owned which was bad from the beginning. I'm no noob to R/C or drones, I've got an Inspire and a P4 which has not given one serious problem. I've also had a Q500 which was problem free. I've spent more time doing check-out flights with this drone than actual photo opportunities. I can't ever tell how this drone will react to firmware upgrades, some upgrades are fine other degrade it. Its been back to Yuneec to have the GPS Module replaced. I just don't trust this thing.

Its on its way back to Yuneec yet again. I don't know if they'll find anything... Been on this forum for ages. Seems like us early adopters have the problematic drones. Captain Drone, Drone Clone, and myself, just to name a few.

I'm very disappointed in this drone. I really liked everything it has to offer. When it works its nice, I've got some great pictures with it. Yuneec CS is great. We talked and length and they'll take a look. I'm not hopeful though because this tipping issue was not consistent.

But with all that said, I'm done. I need something that I can rely on flight after flight, upgrade after upgrade. I get small issues, but not this.

When it comes back IF they've repaired it, I'm still done, I'm going to see if someone may be interested in purchasing it locally at a greatly reduced price with full disclosure. If its not repaired, I'm going to put in on a shelf as a hard lesson learned. I won't say I'm done with Yuneec. If they can get their quality control sorted and offer a drone that does what I want, I'll be back...

Oh and guess what came today? The RS module.... I don't know if I'll be able to return it. If not stay tuned, I'll be selling it for 250.00 shipped anywhere in the lower 48....
 
I've had it with the Typhoon H. Today was the last straw. I'm done...

Yesterday I took it out to ensure the 3.01 upgrade didn't degrade anything and that my "recovery" process from the "H" bricking after the OTA update failed in the middle of updating. Too cold out to do more than a battery pack. But other than a slight drift, everything "seemed" to be okay.

Today, took it out, did all my usual pre-flight checks to include the weather and Kp Index. Ensured everything looked good before taking off. As I powered on my ST16 I heard a loud whining noise. Bad fans! I decided to go ahead and fly. Immediately after take-off, about 4 feet out and 6 feet up, the ST16 vibrated getting my attention, I look down and see something about GPS lost, put in angle mode, return home and perform a CC. I didn't catch all of the message as I looked up to make sure the H wasn't drifting in a bad direction. I could see the status light flashing orange. I landed the H and performed a CC.

Thing is I was in angle mode. Part of my Pre-flight checklist is to ensure all switches and nobs are in my desired starting position which includes being in angle mode.

Flew around. Checked out some of the 3.0 features and exercised different switches and buttons. Everything seemed fine with the exception of a slight drift at about 6' (not prop-wash). Battery got down to 14.6 volts so I started manual landing. I knew the 3.01 was supposed to make landing better, but mine seemed to be a bit super sensitive to stick inputs. As it touched down, with the left stick "full down", the motors started to slow but then suddenly the H tipped backwards and the motors started spinning up. I started to worry it was going to tip backwards, but the motors slowed, the front came down and it idled down. I thought it weird...

So I put the second battery in, did my usual check before doing anything and did several landings. Everything seemed fine. It still seemed sensitive to stick inputs but nothing weird. Flew it around and when the battery reached 14.6 volts I started to land it. As it touched down, it started to tilt forward. I thought WTF? so I gave it "throttle" to lift off and it did. I spun it around then attempted to land again. It touched down and leaned forward without the motors starting to idle down, it was going over. I pulled right stick back in attempt pivot it backwards and gave it throttle in attempt to lift off. No luck. It just went forward breaking the two front props and flipping over. It also put a small crack at a seam in the rear of the bird near the battery housing.

I'm just so done with this drone. You can search my posts and find the issues I've had with this one and the first one I owned which was bad from the beginning. I'm no noob to R/C or drones, I've got an Inspire and a P4 which has not given one serious problem. I've also had a Q500 which was problem free. I've spent more time doing check-out flights with this drone than actual photo opportunities. I can't ever tell how this drone will react to firmware upgrades, some upgrades are fine other degrade it. Its been back to Yuneec to have the GPS Module replaced. I just don't trust this thing.

Its on its way back to Yuneec yet again. I don't know if they'll find anything... Been on this forum for ages. Seems like us early adopters have the problematic drones. Captain Drone, Drone Clone, and myself, just to name a few.

I'm very disappointed in this drone. I really liked everything it has to offer. When it works its nice, I've got some great pictures with it. Yuneec CS is great. We talked and length and they'll take a look. I'm not hopeful though because this tipping issue was not consistent.

But with all that said, I'm done. I need something that I can rely on flight after flight, upgrade after upgrade. I get small issues, but not this.

When it comes back IF they've repaired it, I'm still done, I'm going to see if someone may be interested in purchasing it locally at a greatly reduced price with full disclosure. If its not repaired, I'm going to put in on a shelf as a hard lesson learned. I won't say I'm done with Yuneec. If they can get their quality control sorted and offer a drone that does what I want, I'll be back...

Oh and guess what came today? The RS module.... I don't know if I'll be able to return it. If not stay tuned, I'll be selling it for 250.00 shipped anywhere in the lower 48....
Are you serious about selling it?
 
You say: "Keep the throttle held down until the motors have stopped." Keeping the throttle stick down will reduce prop RPM from flight idle to ground idle. To stop the motors you have to press the red button (#1).
I don't think he meant to say that pulling down the throttle stick would stop the motors -- all he is saying is that you should hold the throttle there until after you have killed the motors using the red button, to avoid the TH trying to maintain its current altitude (which requires an increase in prop speed).
 
If the props have not gone to idle by the time you let go of the stick there is a chance the H will rise off the ground on its own. If you hold the throttle back you can push the red disarm button to fully stop the motors. The throttle stick will never by itself stop the motors. The flight is not over until the propellers are stopped.
 
I don't think he meant to say that pulling down the throttle stick would stop the motors -- all he is saying is that you should hold the throttle there until after you have killed the motors using the red button, to avoid the TH trying to maintain its current altitude (which requires an increase in prop speed).

^^^^ This. Yes, what I'm saying is that you shouldn't release the throttle from its down position until you have pressed the red button and stopped the motors.
 
So I will comment with, "I understand both sides" Mine was one of the very first H 's. Went through several updates no issues what so ever, around six months. Then got to a point with the GPS loss/drifting/not wanting to land. Called Yuneec and they had me send it in. They replaced the GPS board with the second gen board that has been discussed in other places here, got it back and have continued for months with no update or drifting problems. I did update yesterday. The OTA way, and am flying without problems. I understand you frustration!
 
Thanks all very helpful. I'll be flying for real tomorrow so I'll heed the advice and my guess is it will solve the issue.
I'm going to go ahead and update as well right now. Hopefully that's a good move.
Thanks again!
 

New Posts

Members online

Forum statistics

Threads
20,955
Messages
241,599
Members
27,284
Latest member
csandoval