Translations:Help:FAQ/38/en: Difference between revisions

From BEASTX Wiki
Jump to navigation Jump to search
FuzzyBot (talk | contribs)
Importing a new version from external source
 
FuzzyBot (talk | contribs)
Importing a new version from external source
 
Line 1: Line 1:
===Servos react somehow "notchy" at high frame rate. Is MICROBEAST damaging my servos?===
===Servos react somehow "notchy" at high frame rate. Is MICROBEAST damaging my servos?===
If the servos are approved by the manufacturer to this driving frequency, this is a normal effect. The servos get new positioning signals four times faster than if they are connected to a conventional remote control receiver. Especially servos with brushless motors run very hard and direct which causes slightly jerky movements in modes with high servo framerate. This is totally harmless to the servos and you will not notice in flight operation.
If the servos are approved by the manufacturer to this driving frequency, this is a normal effect. The servos get new positioning signals four times faster than if they are connected to a conventional remote control receiver. Especially servos with brushless motors run very hard and direct which causes slightly jerky movements in modes with high servo frame rate. This is totally harmless to the servos and you will not notice in flight operation.

Latest revision as of 11:38, 4 March 2016

Servos react somehow "notchy" at high frame rate. Is MICROBEAST damaging my servos?

If the servos are approved by the manufacturer to this driving frequency, this is a normal effect. The servos get new positioning signals four times faster than if they are connected to a conventional remote control receiver. Especially servos with brushless motors run very hard and direct which causes slightly jerky movements in modes with high servo frame rate. This is totally harmless to the servos and you will not notice in flight operation.