You're right. I am misinformed. I thought 2.4 was supposed to work.
I've done plenty of reading. THAT'S why I made the switch. I don't really care HOW it works, I only have to know THAT it works, with confidence, and that I am operating it properly.
It seems like there are two schools of people here: Those who have seen problems with 2.4 and those who havent.
Those who have are at least offering suggestions on how to correct what I experienced. Those who haven't seem to be in denial that it could happen.
I make my living flight testing for the Gov't. If I had a nickel for every time an engineer told me "that can't happen, it wasn't DESIGNED that way", I wouldn't have to work for Uncle Sam.
I am sticking with 2.4 because I believe it IS the future and better in every way, but I can't deny that I have experienced something with this system that should be better understood and better addressed. I am contemplating what changes I will make to ensure it never happens again. Here WAS my set up when it failed:
Batt: Expert 2700mah nimh on a heavy-duty switch.
Tx/Rx: Spektrum DSM2 Airmod on a Futaba 9C/AR7000 remote Rx spaced on 12"extension mounted 90 degrees off the primary Rx
Servos: 5 Digital/High-torque
Battery condition after failure: Batt volts - 6.5 used 370 Mah
Plane was pointed at me, at ~300 ft, wings level, pitch level. I lost control for 3-5 secs. The plane went to fail safe. The throttle went to idle and the nose dropped until at about 200 ft, I was able to re-gain control and land.
Should I have not had a loss of signal? Absolutely. Did I have one for longer than it takes to click a stop watch? Absolutely.
If it wasn't a low voltage re-boot, then what was it? I'll gladly take any suggestions on my set up. I'd hate to spend a huge amount of $ on A123s and a battery redundant RX if I don't have to.
My apologies for sounding short or giving the impression that I have any clue what is going on with my set-up. I'm not and I don't. That's why I'm here.