TDR stall turn dive to the ground

[dxflyer]

Okay. Second flight of the day for the TDR testing different blades. Everything was normal until I did a stall turn. On the way down I tried to pull up - elevator did not response - cyclic did not response. I watched my TDR dive straight into the ground nose first, then smoke. Both TP 5000mah 65c toasted; soon it was smoking, luckily the battery smoking was away from the heli. Still the damage was severe to say the least. I checked the vbar log and it was saying in many instances RC input of channel 5 out of range.... What caused this loss of cyclic response...I am using a separate receiver hooked up to vbar; Channel 5 is pitch for me and I am not using bank switching..

Warning pictures are not for the weak..

More pictures here. https://www.helifreak.com/showthread.php?t=419980

[Egroeg]

Sad to see this.
Did you do a range test at all?

[Mercuriell]

Feel for you buddy - even 12000 miles away

I had two instances loss of elevator cyclic when first flew my TDR - turned out to be a bad sensor in the Henseleit edition of VBAR. Obviously make sure plug did not fall out of sensor, linkage break on elevator, stripped splines on elevator horn, radio shielding, brown out etc ....

[thefrog]

That's really terrible, not cool to see at all. Just a note - doubt this would have caused the crash - but one blade appears to be on the wrong way.

[Mehari]

Originally Posted by thefrog

one blade appears to be on the wrong way.

Not so. One blade grip has rotated 180 degrees. Looks like both swash-grip linkages were thrown.

[marcosp]

Really sad to see this. Did you have vibration warnings? Futaba or Spektrum? Are you using S-Bus or similar or every channel separately into the Vbar?If Sbus how do you feed power to the Rx and the Vbar exactly? Does your log register until the crash and afterwards?

Sounds like after you turned in the stall turn either: the power cable or Sbus cable disconnected from the Rx, same but from the Vbar, vibe numbed the Vbar (though it shouldn't last so long that you can not recover at all). As John mentions, failed sensors do generate freezes. Usually you see one channel out of range, when you see two it freezes.

If you give us additional info we can help you sort out what happened. Besides the bummer of the crash it's even worse not knowing why!

[CyprusFlyer]

Aw thats a real bummer mate, sorry to see and hope you get to the bottom of the cause, nothing worse than not finding the problem. I am thinking loss of PWM signal from receiver to VBAR that points to a cable, however, if you were sure that you had no cyclic response, say in roll too then its a Vbar freeze, but might be worth posting the log on the Vbar forum for an experiences interpretation.
If nothing found then difficult to have trust the system for a long time, worth sending Vbar in for a checkup?

Post edit: see you have posted in the Vbar thread already

[kimmik]

Given the nature of the failure i'd be very careful not to use the same rx/sats and vbar for an expensive heli again until proven reliable. If you rebuild, use a new fbl and maybe sats too. These will need to be sussed out. Could be as simple as poor connection, or as hard as intermittent hardware failure of either vbar or rx/sats.

I'm terribly sorry to see the crash.

[6cuda6]

I'm gonna have nightmares now.......not really but very sorry to see this happen.

[dswitkin]

Sorry to see this. FWIW I bought a used black VBar a while ago and discovered that the elevator gyro was not working, even though the aileron and rudder gyros were fine. That sensor must be using either three separate gyros or a two axis (a+r) plus a one axis (e). When I got it replaced I made sure to tip the helicopter and watch the swash to make sure it tilted in the opposite direction for both axes.

Good luck with the rebuild,
Daniel

[dxflyer]

Had 3 good flights on the TDR. TDR is back. Vbar has no errors.

[ourbail]

Welcome back..........

Sent by Swagged Out Evo 4G

[KidHeli]

looking good man, what tail blades are those?

[Stolla]

what you do to prevent the lockout in future, still on sats?, if so upgrade to latest vbar firmware and do a check, if you have an old sat cable, cut signal wire to sat and s if it flashes to simulate loss off signal. If not you'll have to check those often by removing one and check for bad wires etc. btw shoegoo those wires on sats, not to the sat but between wire and plug. Also If my memory serves me correctly when you look at sat writing in front facing you the top left aerial is the signal, so must see clear air. After my problems I went back to futaba. hopefully the latest release from vstabi have fixed this

[dxflyer]

Those are align blades; just temporary until I get the radix back on it. The only other tail blades I had were 115 and I did not want to use those.

I am thinking that the cause might be a loose wire somewhere. So this time around I hot glued pretty much all the connections to the vbar and receivers. This time around I am using the vbar governor and it rocks when doing 3d. Also updated 5.3 firmware on the vbar.

I have not gotten the courage back yet to do high stall turn to speed run, but eventually I will.

[KidHeli]

Thanks, I'm looking to switch my Edge 105 to 110's I liked the way those look.

Sent from my LG-V909 using Tapatalk 2

[Stolla]

Just watch out with the bigger tailblades, tdr doesn't like heavy tailblades, cause vibes

[donskills]

Originally Posted by dxflyer

Had 3 good flights on the TDR. TDR is back. Vbar has no errors.

Congrats!!