motor PWM
DietmarM opened this issue · comments
Using GUI 0.57 and baseflight from 01.05.2015 I had this issue:
motor_pwm_rate = 0 - could not set to a good value - gui said 1000..2000 valid only ?!?
(Strange vibrations with this value - because much to slow)
went back to older Version and copter works fine.
Current release is 0.63, 0.57 is quite old.
OK - but this is the latest you can download on github.com
OK - now with the new gui and a new flashed Firmware it works - but Motor PWM rate seems to be nailed to 400 - cant Change it to 480 any more
Entering CLI Mode, type 'exit' to return, or 'help'
set motor_pwm_rate
motor_pwm_rate = 400
set motor_pwm_rate=480
motor_pwm_rate set to 480
save
Saving...
Rebooting...
Entering CLI Mode, type 'exit' to return, or 'help'
set motor_pwm_rate
motor_pwm_rate = 480
version
Afro32 CLI version 2.3 Mar 27 2015 / 10:52:12
OK - now I was able to reproduce it: there is a selection you can make at Configuration tab: brushed motors. This was empty first - able to Change PWM - now I changed it to off - 400 fixed.
...A bit strange: reboot and I was able to Change it and brushed got empty again - can't find the logic so far.
no above 500 is not possible by physics - but more than 400. It does not take values above 400 sometimes - but I can't tell how it happens.
I have to leave now - will try later again why and when it is strange.
It would be nice to see the PWM frequency in the gui when it is below 500 - or to be able to Change it there. Putting to off sets 400.
if (pwm_params.motorPwmRate > 500)
pwm_params.idlePulse = 0; // brushed motors
btw, tehres no reason to hve it above 400 anyway.
On Sun, May 3, 2015 at 5:03 PM, DietmarM notifications@github.com wrote:
no above 500 is not possible by physics - but more than 400. It does not
take values above 400 - but I can't tell how it happens.—
Reply to this email directly or view it on GitHub
#271 (comment).
Faster controle Loop is always a reason - the kiss takes it up to the physical limmit as far I know.
But I was staying below 500 always (< not <=).
@DietmarM there is also (sync_pwm==oneshot) and fast_pwm(125µs pulses) as feature options available.
now I changed the pitch trim in configuration - and its dangerous: Motor pwm got changed back to 0 again - it takes 1 sec to Switch off a crazys quad.
Bug in 0.63 gui with Firmware Mar 27 2015
There is also a report about the bug in a german forum:
http://www.kopterforum.de/topic/30718-info-baseflight-gui-l%C3%B6scht-motor-pwm-rate/
When the PWM rate is <> 400 and save is pressed in configuration tab - pwm rate gets set to 0
Afterwards this is dificult to get Bach to a 400 or other value.
Looks like a bug in the gui....
I think you need to open a bug @ configurator and stop spamming here - I
don't think this is baseflight related at all
On Sun, May 3, 2015 at 11:16 PM, DietmarM notifications@github.com wrote:
There is also a report about the bug in a german forum:
http://www.kopterforum.de/topic/30718-info-baseflight-gui-l%C3%B6scht-motor-pwm-rate/
When the PWM rate is <> 400 and save is pressed in configuration tab - pwm
rate gets set to 0Afterwards this is dificult to get Bach to a 400 or other value.
—
Reply to this email directly or view it on GitHub
#271 (comment).