Home › Forums › Everything about everything else › Naze32 servo frame rate (Cleanflight)
- This topic has 8 replies, 5 voices, and was last updated 6 years, 7 months ago by rcpilot_hun.
-
AuthorPosts
-
3 March, 2015 at 08:51 #11371TerjeModerator
In Davids video on the KK2 board he states the frame rate for digital servos should be high (400).
When sifting through the Cleanflight documentation I realized that the default frame rate for the servo is 50 – but can be changed in CLI by the “servo_pwm_rate” command. Has anyone fiddled around with these settings? Maybe that would fix some of the tailwag issues?
Default rate setting: 50
My suggested frame rate setting: 400P.S.: Another tweak to consider is the “mag_declination” on Naze32 funfly/Flip32+ boards? The correct setting can be found here: http://www.magnetic-declination.com/.
3 March, 2015 at 09:53 #11374Robert CParticipantIntresting find Terje, that could very well make a difference.
In the Baseflight documentation it is the same:
“Output frequency (in Hz) servo pins. Default is 50Hz. When using tricopters or gimbal with digital servo, this rate can be increased. Max of 498Hz (for 500Hz pwm period), and min of 50Hz. Most digital servos will support for example 330Hz.”
Will definitely give it a try, thanks 🙂
3 March, 2015 at 18:49 #11404TerjeModeratorSo I set the servo pwm rate to 400 running the “set servo_pwm_rate = 400” + “save” in the CLI. No problems on the micros Turnigy TSS-10HM Digital Micro Servo. It hovers pretty much like before, no big difference. Then I did the same on the minis TGY-210DMH Metal gear Coreless Digital Servo. The thing just spun around on the floor. I disarmed it and went to investigate. Then the mini armed it self and spun the motors up and flew right in my face! I had to slam it hard to the ground and hold it down till I could disconnect the battery. Pretty scary stuff! Once the CA has taken care of the broken legs and battery tray I will investigate into the matter (with the props removed).
In the meantime I suggest everybody else be very cautious when attempting to alter the servo pwm rate…
3 March, 2015 at 20:53 #11412TerjeModeratorOk, seems that the framerate of 400 fried the expensive TGY-210MH servo, which will keep me grounded for quite a while 🙁
– Unless I can find a loophole…
3 March, 2015 at 21:19 #11420Robert CParticipantI hope you didn’t get to badly injured 😮
I guess I will wait before trying it myself…
3 March, 2015 at 23:34 #11424TerjeModeratorLuckily still running the 7×3.5″ slowfly props (was about to install the 6×3″ gemfan carbon props) so the props just broke on contact with my arm. Minor cuts, not a lot af blood 🙂
I guess David will release the ultimate settings for the Naze32 board when the integrated boards arrive in 6 weeks time (“another 6 weeks of winter”). Looking forward to that 🙂
4 March, 2015 at 18:20 #11464rueParticipantWow – scary! Terje, thanks for the warning! I had the pwm rate on the list of parameters to tweak and will definitively stay away from this until we understand better what happened. Glad that you’ve been quick enough to ground the copter before it started to really eat on your arms…
16 April, 2015 at 00:30 #13308SputnikParticipantHi i have the TGY-210DMH and have set servo_pwm_rate = 400 and even 498 in Cleanflight.
No face/arm eating problem or fried servo.But I have still tailwag issues to solve 🙁
19 February, 2018 at 16:01 #41035rcpilot_hunParticipantHi, Guys!
Today I received an Afroflight Rev5 NAZE flight controller.
I could find inside DUMP list: (Cleanflight/NAZE 1.11.0 Nov 28 2015 / 15:30:06 (0c82a7b))
set motor_pwm_rate = 400
set servo_pwm_rate = 50I read from this topic, that digital servo’s PWM rate is near 400.
Do I think well, that I can test the digital servos (Turnigy™ MG90S DS/MG Serv) with PWM tester of brushless motors?
Thx: rcph
-
AuthorPosts
- The forum ‘Everything about everything else’ is closed to new topics and replies.