Difference between revisions of "Servos react somehow "notchy" at high frame rate. Is MICROBEAST damaging my servos?"
Jump to navigation
Jump to search
Shornstein (talk | contribs) (Created page with "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 co...") |
Shornstein (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | 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 | + | 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. |
| − | From firmware version V2 | + | From MICROBEAST firmware version V2.0.0 onwards a special software filter was installed which slightly mitigates these rough servo movements. |
Latest revision as of 20:04, 9 December 2013
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.
From MICROBEAST firmware version V2.0.0 onwards a special software filter was installed which slightly mitigates these rough servo movements.