-
Notifications
You must be signed in to change notification settings - Fork 17.4k
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
Rover: 4.1.0 issues list #17116
Comments
I connected uCenter today and used Tools->Receiver Configuration->GNSS->File to save these four configuration files. They are labeled accordingly with the GPS_AUTO_CONFIG parameter value in the filenames. A diff of the moving base (MB) files and Rover files reveals no obvious answers - they are identical. However, as I was downloading them with the flight controller active and telemetry connected, I had no 'Unhealthy GPS Signal' warnings when GPS_AUTO_CONFIG was enabled. When I rebooted with it disabled, the 'Unhealthy GPS Signal' warnings were present even after full EKF3 alignment and a good GPS yaw solution. Without rebooting, I enabled GPS_AUTO_CONFIG, and the message instantaneously disappeared. UBX_F9P_Auto=1_MB.txt |
@rmackay9 has anyone validated whether "Speed controller I-term build-up when motors are saturated" is a legit bug? |
the DSHOT reverse range is inverted issue is only on 4.2, it works on 4.1 |
This is a list of known issues especially blockers for the 4.1.0 rover release. The equivalent Copter issue is #16478
Issues requiring investigation:
Existing 4.0 issues
Resolved issues:
The text was updated successfully, but these errors were encountered: