Originally Posted by
David Gladwin
After looking again at my servo travels again, all is excellent. SO wonder if your problem could have been the refresh interval set on your servo programming page.
The factory setting is 18ms, I have never changed that for JR servos and all has been well. Maybe, just maybe ??
David.
I don't think so David, as I played with different refresh rates and was never able to smooth out the choppiness. Do you use your 12x in Spcm with Wea?
Wea, themselves do not recommend using JR in spcm because of the choppiness of the servo movement. Not sure if you've noticed or not but, the servos will also overshoot their programmed endpoints when used in spcm. You have to move the sticks around fast to see this.They come back to where they should be but, a quick movement causes them to overshoot and then return to the proper end point. It results in what "appears" to be a very "sloppy" servo movement. It does not matter whether the endpoints are adjusted in the Tx or in Giga, they overshoot regardless.
Operating the JR 12x in PPM mode, the servos are smooth and perfectly accurate (as they should be), they do not overshoot pre-set endpoints but, the Tx has the dreadful limitation of 8 channels.
Believe me, I went through a lot to get this system working the way I wanted. In order to get more control channels, I bought a new Futaba 12FG ,I then sent it over to Germany (at a fair expense... almost $200 to ship it) for them to sort out the Weatronic Fasst adapter. They made firmware adjustments to the adapter and got it to work fine but, in terms of smoothness and speed, it's performance still did not compare to the native Futaba module/ receiver combo.
I don't know why they have had so many challenges with the adapters, the cheapo Chinese companies knock off Orange/ Lemon and "whatever" colour modules and receivers that seem to work. A quality company like Wea should be able to decode Futaba and JR and have the equipment work just as well as the native modules.
Anyway, all these module/adapter/ channel limitation issues should be solved with the BAT 60 so they will eventually be moot points. I would have waited for the BAT but, there were other things that the BAT wouldn't solve for me.
I was having issues with the Gyro's picking up acoustic turbine noise and thus glitching. I'm now running Cortex gyros and never a twitch. I was not fond of the need for the MUX box as a hub for sensors. I also expect development of compatibility with various turbine ECU's to be a long way off, if ever and this ability was very interesting to me.
Mike