Spektrum TX module requires fixed PPM frame length

[GoogleCodeExporter]

It would appear that the Spektrum TX module requires a fixed PPM frame length 
(instead of the floating length frames that works for 'everyone' else) in order 
to function properly. A frame length of 22.5ms seems to be in order.

Oh ... and this is not new to the ER9X team. They already have code to handle 
this situation. Well, that's good news.

This will need to be addressed for the upcoming stable release, since here's at 
least one (new to g9x) local fellow using Spektrum gear who will need it.

Original issue reported on code.google.com by gru...@gmail.com on 4 Oct 2011 at 10:46

[GoogleCodeExporter]

Hmmm. May not be a fixed frame length that's required, so much as a maximum 
length. I have confirmed that ER9X has a setting for this though and that 
indeed, 22.5ms does work with the Spektrum module in question.

Original comment by gru...@gmail.com on 4 Oct 2011 at 11:01

[GoogleCodeExporter]

DOH! G'9X already has this coded exactly the same as ER9X -- but tests today 
prove G9X is not working working with the Spektrum module, yet is working on 
exact same model set-up with a Fly-Sky module. Specifically, the Spektrum 
module has significant jitter (ch.3 esp. for some reason) and very noticeable 
lag/latency, making servo moving anything but smooth. The Fly-Sky module is 
smooth as silk. The Spektrum module works perfectly fine under ER9X though!

Perhaps it's not the frame length then. Need to put the thing back on the scope 
and have another (better) look.

Original comment by gru...@gmail.com on 4 Oct 2011 at 11:27

[GoogleCodeExporter]

This turned out to be a red herring. Long story. No time to explain. We're 
moving on.

Original comment by gru...@gmail.com on 8 Oct 2011 at 9:50

• Changed state: Invalid