Page 13 of 14

Re: Frsky problem.

PostPosted: Sun Sep 05, 2010 10:41 am
by pkt
AFAIK these are the fixes for jitter (servo jerkiness when moving). As I mentioned below, the update date column in the table seem to be incorrect; the files you actually get when you download are version 100825, which I believe means they were created on 25th August 2010.

But I'm guessing here, I could be wrong of course! Can anyone from FrSky please comment?

Re: Frsky problem.

PostPosted: Sun Sep 05, 2010 10:46 am
by takilara
those files have been on the site for several months

Re: Frsky problem.

PostPosted: Sun Sep 05, 2010 10:50 am
by pkt
takilara wrote:those files have been on the site for several months


Yeah? That's disappointing then, 'cos I just used them to upgrade my Tx. Maybe I've downgraded it instead!

I guess I don't understand FrSky's version numbering system at all then, if it's not date based.

Re: Frsky problem.

PostPosted: Sun Sep 05, 2010 10:57 am
by mr.sneezy
You guys are right, those are not the 'jerky fix' files. Looks like the new files have not gone public yet.
I'm not sure where I stand right now on this topic with FrSky, but rest assured they seem to have fixed the problem in the beta I was sent to try. I'll let you know more when I check a few details with Eva.

Re: Frsky problem.

PostPosted: Tue Sep 07, 2010 7:27 am
by Cheralex
Guys, looks like new ROM released.
http://www.frsky-rc.com/ShowNews.asp?id=40

Re: Frsky problem. Servo Chatter cause identified

PostPosted: Tue Sep 07, 2010 4:12 pm
by pkt
Hi all,
The good news is - I've found what's causing my servos to chatter continuously while stationary. Unfortunately the bad news is that I haven't found how to cure it.

Here's a video showing my testing and results: http://www.youtube.com/watch?v=nTKaGRf7g5k

Here's the analysis:

I started by examining the PPM signals at the input pin to the Tx module and at the servo outputs on the Rx, looking for any instability in the servo control pulses. Both proved to be rock solid, with <1us jitter on the encoder output and none at all I could measure with a 1Gsample/s scope on the FrSky Rx outputs. A single click on the trim would cause a very obvious 4-5us shift in the pulse length. This rules out any encoder problems (such as noise coupling through the power supply from the Tx module that some others have noted in this thread) or receiver instability as the cause of the servo chatter.

In the process of fiddling around however, I stumbled on the cause - RFI (Radio Frequency Intererence) from the Rx telemetry transmissions directly affecting the digital servo amp. I found that as I handled the Rx the chattering would come and go, and I worked out that it would stop completely if I held the active antenna.

In the video I show the chattering reliably stopping when I hold the antenna, or cup the RF end of the Rx in my hand. I tested with both digital and analogue servos - JR DS811 digital servos, an old JR NES507 analogue servo and a cheapo no-name mini-servo out of a park flyer. The analogue servos are completely unaffected, only the digital servo shows the problem (I have 4 DS811's - they all do the same thing).

I then did some testing to try and work out if the RFI was coming in on the servo lead or being picked up directly from the RF field. I added ferrites on the servo lead (the video doesn't show it, but I tried ferrites at both ends of the lead), and then tested with extension leads to space the servo away from the Rx. The results suggest there is a bit of both going on, but that direct RF coupling is the dominant problem.

So I reckon the RFI is either:
a) Affecting the operation of the pot a/d, causing the pot position to be misread.
b) Pushing the quartz oscillator frequency around, so the PPM counter miscounts.
c) Doing both.

I opened up a servo and had a bit of a probe around to see if I could find a fix, so far without success. Some 10nF/100nF bypass caps in the right places or better groundplaning on the servo amp might help, but for now the only solution I have is not to use the DS811 servos with the telemetry system. That's not really a great solution though, so I'll keep looking.

I'll post a follow-up video soon with some additional testing I did - and showing the antenna diversity and RSSI working. A cool and totally unexpected by-product!

Re: Frsky problem.

PostPosted: Tue Sep 07, 2010 5:33 pm
by takilara
Was this with the "non chatter" firmware released today?

I want to try this new firmware, but i am a little skeptical as flashing the Rx is a little scary. (this is my last Two-Way Rx)

Re: Frsky problem.

PostPosted: Tue Sep 07, 2010 6:29 pm
by Allan Warner
Pkt, be interested to know if the cheap 'parkfly' servo is still crunchy (coggy) on a different RF link, ie 35mHz FM. The response looks remarkably similar to the 'coggy' response (at moderate stick movement speeds) I had with some servos using the FrSky telemetry units on my Futaba Tx.

Re: Frsky problem.

PostPosted: Tue Sep 07, 2010 6:39 pm
by takilara
Since FrSky has acknowledged that this is a problem, and has submitted a new ROM that deals with this problem, i am curious if anyone have had the time to upgrade yet...

Re: Frsky problem.

PostPosted: Tue Sep 07, 2010 8:26 pm
by takilara
Does anyone know what this means from the FrSky webpage regarding upgrading the Rx?
"RX must have a RS232 converter installed between the RX module data pins and the PC comm. Port."

Is it enough to make a connector that converts the connector from the FrSky usb cable to a 3-pin connector to use with the Rx?
Or do we need some sort of level converter?