View Full Version : 149DP glitching
MarkWebber
03-23-2007, 09:52 PM
On my R50 I've got an AP2000i which includes a glitch counter. It's pegging out. The heli is twitching around in the air. Doesn't duplicate on the ground. Mostly shows in the collective and throttle. The throttle will occasionally cut. Of course, control is fully regained then. It does not go into failsafe when this is happening.
Bad crystal? RX problem? Any thoughts?
DavidH
03-23-2007, 10:19 PM
Servo wire chaffed, take the AP2000i out of the RX. See if that is causing the twitching. If it is not going into failsafe, I would think it is not RF causing the twitching or glitching. If you can see it glitching continously, it would go into failsafe if it was RF interference.
David
MarkWebber
03-23-2007, 10:26 PM
The AP2000i has no interaction with the throttle which is where the glitching is most obvious in flight. I will check for wire chaffing, also.
I don't believe it is going into failsafe, either. The controls do not go to the failsafe position. I believe the occurances of the throttle going to off were just a more sever glitch.
SteveL
03-23-2007, 10:31 PM
Like David said.. In design PCM will not glitch. If the radio picks up interfearence, it will lock out. You can however have RFI or EMI get to a servo that is not coming from the receiver (Very common in large scale planes. I am thinking it might be a bad receiver ir AP2000i. You can have a sever feed interfearence back into the reciever also.
DavidH
03-23-2007, 10:33 PM
If the throttle is cutting. It is doing one of two things. It is going into failsafe from RF interference. Metal to metal will cause this. Usually when it goes into failsafe it takes at least 1-2 seconds for it to come back to normal after it sees a clear frame.
The other thing that could be happening, is there is bad connection in the battery or the plugs to the receiver from the switch. Also could be bad switch. Throttle cut is a sign of battery failsafe happening.
David
MarkWebber
03-24-2007, 09:29 AM
Post flight observations following crystal change. 5 min low hover...glitch count=2. Prior to crystal change glitch count=99(limit, I think) in short order.
I think I'll still send it in.