New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configuration - Unable to save Yaw Servo settings #991
Comments
thanks for the report. Please confirm that you also tried latest configurator with firmware < 1.9.0. Please note this issue should have been opened in the configurator issue tracker. |
I had the same issue, I went back to v1.8.1 and with the latest configurator I can change the servo settings Also I found I couldn't load my v1.8.1 backup file to the NAZE32 after upgrading to V1.9. I would get the line of script saying it was loading but it would just hang Configurator v0.65.0, AFRO NAZE32 |
Same for me, latest configurator works fine with 1.8.1, but will not save servo settings for 1.9.0. |
Yeah, same for me, previous versions of cleanflight (<1.9.0) with latest (0.65.0) configurator worked... |
Fixed in 9a8a316 for Cleanflight code. |
I also ran into this when I updated my cf from a "almost 1.9.0" / 4857050 to official 1.9.0 and restoring my backup file hung. It was of course equally reproducible by trying to modify the servo tab... |
Closing this. Configurator needs work for latest master code and existing servo configuration code will likely be replaced with new code due to new servo mixing rules and servo angle support. |
Aug 21st just downloaded the latest 1.9.0 and can confirm this is still not fixed. Can't save any servo settings. |
VCP improvements to remove need for delay in serial_cli for F4 targets.
Is it correct that this is still an issue? v2.0.2 is still showing the same behaviour. |
After upgrading to fw v1.9.0 on Naze32 via Configurator v0.65.0, the "Yaw Servo" setting page under "Servos" tab doesn't work. Changes made on this page can't be save to eeprom. Previous versions fw 1.8.1 worked fine.
The text was updated successfully, but these errors were encountered: