Originally Posted by
billdelong
If a manufacturer posted their frame rates, then I simply transposed them, of the radios that I personally owned, and if the frame rate was not published, then I hooked up my PPM to get readings to put in the chart. I feel confident that my method of calculating the frame rates was very accurate.
Using your method to show servo frame rate the Futaba 4PK has 3.30ms if you want to add to your list. But in all my test the GT3B have 16.0ms but it might be because there are several versions of the RX. The Radiolink RX I have tested is R4EH-H and it have a loop time of 18ms and 18.2ms listed in your sheet might be the same because when i look at a recording of the signal some have 18.1ms and 18.2ms but the majority is 18.0ms. No RX I have tested is 100% consistent with their times some send 5 signals correct then 1 with .2ms extra. But you should really change the description to servo frame rate. Because as you can see reading these values and the actual transmit delays they are both values around 5-20ms and people get confused easy. And a radio with lower frame rate can have faster latency than one with higher frame rate as my test shows.
The problem is that some on your list have 1ms and 1.5ms. This is impossible because the maximum signal of 2ms that the servo need for maximum output in one direction can't be sent in 1ms time. It looks like Sanwa might have some proprietary protocol for communicating with Sanwa branded servos that might have a different communication but unless the speed on those are verified the values are just impossible.
The Ko propo have on their website listed neutral pulse 1.5ms and this might be the value you have found and put in your list, this is not the update rate this is just stating the obvious that a servo have a 1.5ms pulse as it's center position. If it is the time between pulses the real value should be 1.5ms + 2ms for the pulse it self. I have found no information of Ko propo having some other sservo communication protocol making a frame rate time of 1.5ms impossible.
EDIT: It might also be important to actually show that the radio can handle another protocol for the servo signals, but the protocols don't really have the standard set or named. ESC for quads have started using other protocols such as oneshot because they need to update the esc faster than the original 2ms pulse allows. But they have taken the road with an open standard and it is very clear what they do. RC radio manufactures have taken the bad road down the closed street trying to sell servos that only works with their stuff so it will be a sad and confusing future for us it they continue with this approach. But hopefully the big brand servo manufactures will set a standard that they just have to accept.
EDIT2: Futaba frame rates from sellers infopages, all systems have a fast and slow mode for analog servo compatibility:
Servo Frame Rates:
• T-FHSS: 3.3/15ms
• S-FHSS: 6.8/13.6ms