And then along comes someone like myself that has over 50 various makers 2.4 receivers (many of them the "dreaded" AR6100's.) and to date, I had "1" failure of an AR6100 and it was DOA and never made it into a plane.
I even have one that burned up in an ESC fire that still works. I simply use it for a test receiver and haven’t reinstalled it into another plane. Should I ever run out of receivers and need to use it, I would in a second.
With all the different planes I have in my hanger, I’ve yet to have a brown out with any of them.
As for range, I’ve flown mine out to the limits of my eye sight (about 1800ft on a 28 in wing span F22 jet) and still had control. I simply could no longer determine which way it was going and being I was getting near a highway, chopped the power and elevator’ed it to the ground. I had control all the way down as well.
So, don’t trash 2.4 just because you have had such bad luck with it. As you can see from above, not everyone does.
And we now return you to the topic at hand;
You say you bench tested it to recreate the flight, did you move around the wires while moving the controls? I'm with CC that it sounds more like a loose connection rather than a brown out.
You thought you first had a brown out (motor died) and recovered.
What were doing at the time? Straight and level, 3D, a loop?
Any extreme maneuver could still point out a bad connection more that a brown out and I myself would assume that before thinking I had a receiver problem.
Lastly, you were going to land anyway after the first event to see if the receiver was blinking, Did you think to do so after the crash? As long as you didn't throw the batt away from the plane at impact, you would still be able to see if it was flashing or not.
|