w8ye

I totally agree.

What I found was that the tool, TXSERVO showed latency between the two servos. I switched them (the TXSERVO has "two channels") well, as it started out, servo 1 was in channel 1 and servo 2 was in channel 2 and tested them (tested the movement). Servo 2 seemed slower than servo 1. Then I put servo 1 in channel 2 and servo 2 in channel 1, and found that servo 2 was again slower than servo 1 (eyeball observation, nothing scientific here). The difference was perhaps one second. I guess I could time it electronically if I really wanted to, but my point is to inform new people (and some of our journeymen) of the fact that not all servos are alike.

For most of our applications, this probably won't matter. But, for some that may be comtemplating Pattern or 3D, well, the servos should match.

I've included a 'screen shot' of the TXSERVO software to show what the tool is capable of doing. The graph is a tool that you can click on and move the servo to that position. Note the values in the green background square. Centering the servo occurs at 1550,1550. The last position is slightly off, but it will center at 1550, 1550.

I guess what I am trying to point out here is that there are tools available to help you both center the servos, and test the difference in the "speed" (latency) of one servo against another. This helps select servos for use... ailerons (dual servo apps) or elevators (again, dual servo apps) or landing gear, or whatever.

Another point here is a tool that helps center servos. They all must be centered somehow, either with the TX or a tool like TXSERVO.
CGr