Tx or Rx fault..

[pgkevet]

Switched on 8FG, bleeped as it finished initialsing as usual.. switched on 700N....it just sat there. I fiddled with the radio and the 700N sprang to life.
That made me think tx fault. Switched heli off and on ..fine. Switched tx and heli off and on in order.. nada until i moved a stick. repeated that several times and most times both behaved normally..but every now and again the 700N wouldn't iitialise in a decent timescale but did initialise/respond when a stick was moved.
So i do back to the shed and play wth tx and 600N ... consistently both respond as expected. So i try both helis together.. before i realise I'm being a dipstick with on heli on 7 channel and one on 14 channel tx output...

So I put everthing away in frustration to go off and think about it..

As it goes i do have a spare tx but check copying all settings properly isn't a quick excercise. I also have a second heli with a 14 channel rx which is the next stage.. see if they both behave the same (tx) or whether it is just the 700N rx: that's a job for this evening cos I'm pigged off now.....

[milly0812]

Tx or Rx fault..

Bloody Futaba

[debrooker]

Bloody Futaba

just what i was thinking ... piece of c$@p


BTW I'm futaba

very odd behaviour really, my finger of blame would be the radio

[pgkevet]

The gameplan is to set-up both 14 channel rx helis at same time with the tx set for either one and see if they both respond/fail to respond at the same time...if so it's the tx. If it's just th 700 that is iffy then it's the 700rx.
That's my logic anyway.
If tx then I'll swap current updated numbers over to my 12FG that (for some reason) I haven't used for a year.
Whatever is iffy will go to ripmax to be checked out.
700N did have a heavy forced auto 2 weeks ago after a tail grip link failed
But it's obviously not safe to fly until the source of fault is proven.

Oh well, dog got an exra run behind the quad bike all round the farm and hill fields..and there's always grass to cut <sigh>

[pgkevet]

2 helis side by side with 14channel faast receivers of the same type onboard. Tx already selected for the 700N and switched on. Switch on Spectra and almost instantly the cyclics level. switch on the 700N and 10-15 secs before it does the same or may not do the same until a tx stick is moved. However the 700N rx does go from red to green led almost immediately.

Does that mean that it's picking up the carrier digits and recognising the tx but the having some internal checksum issue????

I dont see how this would be related to any power issues...it does have the align 2:1 powering this heli but no dodgy flickering switch and steady 3 greens since fully charged. All plugs solid in the rx.

I'm not sure if worth sedning to ripmax..it's the original type faast 14 channel..not even the second gen high speed one.

Suggestions????

[milly0812]

Tx or Rx fault..

Try a Rebind ???

[pgkevet]

Try a Rebind ???

I did consider that.. but it's not speccy and the green light shows it's bound. I don't think futaba has any other rx memory/reset, does it? It picks up tx data such as failsafe each time?

[cjcj1949]

If you have two rxs and two txs you should be able to swop the pairs and find the faulty unit. Unless you have one system that needs a certain input like an esc which needs an input pulse less than 1.0ms. Systems can be very complex when you don't have access to what is going on inside, too many variables.

[pgkevet]

If you have two rxs and two txs you should be able to swop the pairs and find the faulty unit. Unless you have one system that needs a certain input like an esc which needs an input pulse less than 1.0ms. Systems can be very complex when you don't have access to what is going on inside, too many variables.

I'm happy it's that rx. Remember that on futaba here's no model match so it's easy to have two or more rx's bound to the tx all working at once. It's only that one heli that misbehaves.