ORIGINAL: jetfixr
Thanks for all the advice. I have switched out the servo and will be trying that momentarily, but if that doesn't work, I will switch the pushrod out to a carbon fiber one. I just liked the simplicity of the cable. Bald Eagle, yes I did do a search on this subject first, but every post I found was about interferance on all servos, but I am having problems with only the throttle servo. I thought there just might be something I was missing. Why take the time to type something up if you aren't going to try and help?
---------------
Many carbon fiber compounds are also conductive, but it might be worth a try if you already have the carbon fiber material available.
In the old traditional encoding schemes, radios NOT on 2.4 GHz, the throttle or a seldom used auxiliary channel was usually assigned the last position in the pulse train. The thoughts were that the channels furthest away from the sync pulse were more likely to suffer degradation than those cloest. I don't know if there is a technical basis for this assumption or not - but that is how it was explained many, many years ago.
So, with the above stated, it is possible that those channel assignments furthest from the beginning of the fresh frame could suffer some degradation, while earlier channels may not suffer anything obvious to the operator. That was the old paradigm. I was never convinced that the theory held any water, but I felt obliged to repeat this R/C myth.
I would rectify the conductive throttle cable first. That isn't good no matter what other problems are present. Then, if the cable replacement fails, change out the servo to a different one. If the problem goes away, all the better. If not, then it is likely that something else is causing the problem. Sometimes, just reorienting the wiring in your model can cause or eliminate such a problem.
Good luck.
Ed Cregger