AP2000i glitching like an SOB!

[MarkWebber]

Glad to see it's working for you now, Mark. Looks like a very thorough mod there.



You might be able to sue the new TT drive for the T-REX 600 with some mods???

Guess I'll have to have a peak at Greg's 600 next time I see him. I seem to have gotten past my belt difficulties but I dislike problem designs.

[catfight]

MLaBoyteaux,

You didn't happen to forget that you have to have the main batt connected to see the HV85 with the interface did you ? I have been guilty of that before!

[nikivan]

Mark, thanks for sharing this info. In addition to that, I've also read that bad bearings could cause glitches. I am having some issues and I've replaced all bearings on my X-400 Pro. I was surprised to find out that more than a half of them where bad. The heli is 1 year old. Today, after reading your post, I grounded the tail boom to the CF frame and I did a test flight. So far so good, hopefully the problem is fixed.

Nick

[MLaBoyteaux]

It seems to be solid now. I did several flights on Sunday afternoon without a single glitch.

This is just my opinion, but the AP-2000 seems to be more sensitive to interference than the PCM receiver. In retrospect, I don't think the static was discharging into the system, but the RF noise being generated by the arcing was interfering with the AP-2000.

I had just rebuilt the heli and installed new bearings along with the new all metal tail rotor from QuickUK. I think the metal tail rotor gear and housing exacerbated the buildup of static charges on the main shaft and tail rotor housing.

I knew it wasn't the bearings, I could disconnect the drive belt and the problem went away.

On my HV85 ESC, I've tried every sequence possible to get the Castlelink software to recognize it, with no luck. I suspect the static has killed the optical interface. It worked when I received it last month, but no more. As far as I can tell, there's no way to modify the governor gain without using the Castlelink.

[GGoodrum]

I think you might be right about the glitching/arcing taking out the CastleLink interface. I had one do this in a Raptor that had a few PCM lockouts.

You'll have to send it back to CC but they will instantly replace it.

-- Gary

[AZ ChopperCam]

for the record... my CC85HV will no longer see the castle link either and this is the same ESC that I was getting the glitching with the AP2000i.

I'll be sending it in soon to CC

[Load Factor]

Mark....

I replaced the ESC on the Joker and during that time had noticed that the ground from the tail had broken....probably while installing the new mount for the IR sensor. I repaired the ground and no more pitch glitch. Now I need to calibrate the AP 2000i for a left drift.

[rerazor]

After installing my Ap2000i on my eR50 I'm getting the "collective glitch" on spool up.

My HV85 is not found on my Castle link but all my other CC esc's work fine.

I will be adding the titian boom/belt this week and replacing the mainshaft bearings.

I have a metal boom mounted Tail servo mount.

My plan is to ground the tail boom/mount to the motor screw. Do I also need to ground to the negative side of the Esc lead or can I tap into the negative side of the UBEC?

[GGoodrum]

The negative side of the UBEC should be fine.

-- Gary

[rerazor]

I'll do it the same as Mark L. did in his pic to the ubec negative at the common point.

More wires :shock:

[rerazor]

Removed the tail belt and no glitch was seen.

I added a ground wire from the metal tail servo boom mount (scratched the anodizing/paint off the boom/mount) to a common bolt and then added a wire from common bolt to the negative wire of ubec. The collective glitch is gone and no other glitch is seen. The Api does register on avg. 1 glitch every minute of bench running.

I have the stock TT plastic tail case and pulley.

[Angelos]

rerazor,
what receiver are you using? PPM/PCM?

-Angelos

[rerazor]

JR R7703 PCM rx