Problems!! 14MZ 2.4 R6014FS

[lazun]

Hello all.

I'm helping out a friend and coaching them for competition. He is using all Futaba equipment and 2 Duralite Batteries, 14MZ, 2.4, R6014FS RX DA150 aerobat simple easy setup.

He has about 30 flights on the system FLAWLESS!!

Then an issue:

While starting the engine a second or two later after engine start the plane locks out. Moving the sticks does nothing. We look at the rx and it is solid red, tx solid green as if it lost the bind. But it didn't. We shut the engine off and cycle the rx switch and it goes green. So we start it again and it was fine. So after a little testing we decided to fly. A 17 minute flight FLAWLESS.

Then it happened again 3 times the same way during engine start. Now we know there is defiantly a problem. We didn't know if it was the rx or tx. We ruled out the tx at the time because when we lost it we cycled the tx switch and the rx stayed solid red. The tx was always solid green before and after. Cycling the rx switch would only make it come back to steady green on the rx.

What is this? It gets better.

We come out the next day with a different airplane with about 3 flights on it. Different plane and rx. It does the same thing!!!! WHAT?!!
Five times we lost the signal. This time without even running the engine. The plane was just sitting there on the ground no engine testing the control surfaces and boom lost it. Cycle the rx switches and get it back then a few seconds later loose it again!!!? Happened 5 times no engine this time. Unless you cycle the rx switches you will not get the rx back.

This is serious! Any help?

The airplane was indeed going into hold and going to the pre-set failsafe settings. No power box. Simple setup. Two Duralite packs. If it is going into failsafe why is it that you cannot get it back without cycling the switches.

Today we went out with the plane with a different rx r6014 in it and tx 14mz. We did everything and it would not go red. We started the engine 11 times. Ran the engine for 15 minutes touched the antennas to the ignition, ignition wires, spinner, batt, tapped the module did jumping jacks with the tx and NOTHING. Left it on for half hour and NOTHING.

Without question it is the rx or tx or both. We are leaning towards the rx.

Any ideas or others with issues like this?

We cannot take a chance. These airplanes are custom and have 300+ hours a piece on them.

There is no question that it is the rx and/or tx. Question for the techs is why doesn't it come back? Why is it that until you cycle the switch it will go green?


Some said vibration:
I would agree with this statement 100%. However, if the other aircraft this was happening too was with a new RX and with the engine off.

My point is that regardless of setup, defective switches, wires, batteries, powerboxes, ignition or even outside interference ect, that make the RX go into this mode, it should come back. But it doesn't until you cycle the power. This makes me question only the RX.

Have there been programming or hardware issues with the RX's regarding this?

[Exfokkerflyer]

I had an issue with the 6014FS. Had it in a SebArt Sukhoi 30e. Previously flown on XPS with no issues for about a dozen flights. Wanting to switch everything over to FAAST I tried out the new 2.4 set up. Lost the plane on the sixth flight with an apparent hold straight into the ground. I say apparent as upon impact, the radio equip was spread over several feet, all disconnected. I had a pretty good installation, I honestly don't feel that was the problem, but I am "open" to the possibility... though my gut says no.

Could not duplicate the problem, all equipment tested fine. Sent it back and they could not find the problem. For other reasons I actually have another receiver now, but I think I am going to wait and see how things shake up before I start putting this in my big stuff.

Not your problem, but just wanted to answer the question if anybody else was having issues with the Rx or system in general. My answer is yes, and I don't know why.

Good luck, hope you can figure out your problem.

[Judge]

If the light on the RX is going red that is telling you that it has lost contact with the TX. Cycling the power resets the RX, and if it "sees" its TX, then the light turns green.

For some reason it appears that these RXs are losing contact with the TX. Since it is highly unlikely that two separate RXs with the same issue arrived in the hands of the same person, I suspect the TX.

So again, I'd check that the TX module is fully seated and that the pins look OK. If all that looks good I'd send the TX, module, and RXs in to be looked at.

I would check that the TX module is fully seated. I would also look to make sure there are no bent pins, etc. It sounds very much to me like an issue with the module, or how it is installed.

[Exfokkerflyer]

Judge, are you referring to my post? The XPS was not installed in the 14MZ, it was and still is on a 9Z. The only reason I mentioned the XPS in my post was to say that the system (motor,esc, installation arrangement) was solid.

I don't mean to hijack the original post either. But now that I think about it, I had some issues binding the original receiver. It wasn't bound when I first received it, and had to do it myself. No biggie, worked for a while, a while later it didn't. Eventually I got it to "take" and didn't have any issues... until the crash that is, but like I said I don't know if it locked out, lost bind, or what....

I should also add that I sent the radio, module, and rx back for service after the crash. All were found to be working properly according to the tech.

[Judge]

Got mixed up. Changed it. Thanks.

But it still sounds to me like the OP is having a module issue and not a RX issue. Odds of 2 bad RXs with the same guy pretty slim. But the TX module is a common item for both planes he had trouble with.

[freya1]

The exact same thing happenned to my friend with the 12FG (2.4 Dedicated system) and the original 614RX that came with the system, he was flying a QQ Python and as soon as he landed, he had nothing, lucky the throtle was at idle and the plane was just rolling, he recycled the switches and everything worked again, we held the airplane while he worked the controls and about 3 minutes later it did it again, we tried it about three times and it lost signal. He sent the TX and RX to futaba about a week ago, haven't heard anything yet.
I have been flying my planes with a 14 MZ and 2.4 conversion and also a helicopter, no issues yet but I am waiting to see what the tell him, still holding on to my 72mghz RX's. I hope we hear something soon.

[Judge]

Very odd. It will be interesting to hear what they find. Keep us posted.

[Fastaljr]

I am keeping an eye here on this post, i just recieved my 14 2.4 module, I didnt buy the 14 reciever as i dont have a plane that requires it yet. Are these incidents all with the 14 channel 2.4 reciever just????

[BR289]

I have plenty of flights on my 12Z with the 2.4 Module without any problems. I havent tried it in the 14MZ yet ( its in service getting stiffer springs ) but plan on doing it when I get it back.
I am also very interested in the findings of this problem and I too suspect either the module or the radio...not the receivers.
Please keep us posted....
Blair

[Mithrandir]

I am suspicious of the electrical power system.

Put a power meter in the system and watch the voltage.

[lazun]

Well All!!!
We have found the issue!!!!
You all are not going to believe this but it is seriously going to impact how you install your 6014FS!!
It has nothing to do with TX, 2.4 modules (we tried that too by the way) or your setup.
IT IS ALL ABOUT HEAT!!!!!
Whatever you do, do not let this RX get up to 164 degrees!! It will go red on you!!

My friend is in AZ. The flying we have done is mostly in the evening and AZ has been fairly cool. But the other day when this was happening it was the middle of the day and hot sun. We took a flight and it was fine. But then problems!! We didn't realize it at the time.

At home we were setting up for the XFC. Had the plane in the driveway with 2 RX 6014FS in it for redundancy. We had them on no problem for 15 minutes. Then 15 minutes later one RX goes red and the other one went red as well a few seconds later!! We tried everything to get them back and they would only come back momentarily until they went red again. What the hell!!

What can it be?!!! We said maybe heat? The sun was hot!! With a temp gun we shot it showing 167 degrees F. We wheeled the plane in the garage again and let it sit for a while. We turned everything on. For 24 minutes we could not get it to go red. We wheeled it out into the sun again and had the temp gun on it. At 164 degrees F they went red. Both RX at 164F went red. Even though they cooled down bringing it back inside, they would not come back online if you did not cycle the switches. We tested this 3 times and as long as the RX was less than 164 degrees F we could not make it go RED!!!! But the second our temp gun got to 164 degrees F "BANG RED". You tell us?!

By the way the techs obviously said the RX's where fine no problems. We had sent it to them. They could not get them to fail. We found this heat problem out yesterday and were too late to call them. We will let them know Monday morning.

It's getting hot out there in the USA!! AZ is 115F. Not to mention folks running canisters in there fuselages.

We are convinced that this is the issue. It makes sense, is consistent and we were able to fail it consistently every time!!

By the way this was tested on 4 diffrent RX!!!

I'm not sure if we are off here. However, we will keep you posted on what Futaba techs will say.

[Judge]

I've sent this post to Bill Baxter and Krysta Hunt so they are made aware of it.

Honestly 164 degrees is pretty hot. Heat sensitivity is nothing new either. Why else do we see plane covers, etc.

But it shows that it is important to do what you can to keep the interior of the plane cool, which is good practice in any case.

I'll let you know if I get any more info next week from Bill or Krysta.