Skip to content
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

ArduPilot 4.6 issues list #28612

Open
3 of 16 tasks
rmackay9 opened this issue Nov 14, 2024 · 9 comments
Open
3 of 16 tasks

ArduPilot 4.6 issues list #28612

rmackay9 opened this issue Nov 14, 2024 · 9 comments

Comments

@rmackay9
Copy link
Contributor

rmackay9 commented Nov 14, 2024

This is a list of issues discovered during ArduPilot 4.6 testing. Issues for Copter/Rover-4.5 issues are here

Reports requiring investigation

  • Takeoff throttle behavior for planes without airspeed sensor changed (issue, PR)
  • Custom Build Server for CubeOrangePlus with OpenDroneID shows linker error (discussion1, discussion2)
  • when the user has configured ESC, FFT or RPM notch and has INS_HNTCx_REF=0 then they end up with a fixed notch. We should have an arming check to tell them they need to set the REF to 1.0 (any non-zero value will do actually) check that INS_HNTCn_REF is non-zero for ESC,RPM or FFT notches #28786
  • add a warning if the GCS system clock and UTC clock on the flight controller differs by over 20s and signing is active, as signing will fail with a 30s difference

Confirmed issues

Plane Specific Issues

Enhancements or Issues that may not be resolved before the stable release

  • Add LDRobot LD19 support (discussion, issue)
  • need to provide a clearer message to users when the power status flags change, indicating loss of a power source in flight. A statustext at message level CRITICAL I think is warranted, maybe "POWER STATUS CHANGE" ? (Tridge has details)

Wiki issues/enhancement requests (Wiki To-Do list)

  • None

Resolved issues

@rmackay9 rmackay9 pinned this issue Nov 14, 2024
@amilcarlucas
Copy link
Contributor

Why not copy the open issues from 4.5 into this page to make sure they are not forgotten?

@rmackay9
Copy link
Contributor Author

@amilcarlucas,

We could but I worry that the result will be that we have two really long lists of issues that we don't actually clear up. If we can get focus from the dev team on investigating the issues and resolving them then that could work. We should discuss at the next dev call I think

@tridge
Copy link
Contributor

tridge commented Nov 16, 2024

@rmackay9 @CraigElder I think we need to restructure the dev calls. By the time we get to the copter/plane issues section we are all exhausted (I know I am). I think we should start with the release issues, and look at PRs that address those issues. PRs for new features or cleanups should come after we've looked at critical issues

@Ryanf55
Copy link
Collaborator

Ryanf55 commented Nov 18, 2024

Here's a new one. I'm not sure whether you want me to add it to the list:
#28666

@rmackay9
Copy link
Contributor Author

@Ryanf55,
Thanks for that. Tridge has put an item on the list that involves the auto-enable parameter. Maybe it's the same? In any case, I've added this to the list as well under confirmed issues.

@menschel
Copy link
Contributor

@rmackay9
In case you want to list it separately for plane.
Issue Takeoff not completing under TKOFF_OPTIONS[0]=0 #28685
PR attempting to fix it Plane: Fix inability to climb the last few meters of takeoff

@rmackay9
Copy link
Contributor Author

@menschel thanks for that, added!

@menschel
Copy link
Contributor

I have created another issue.

Plane 4.6 beta - Takeoff throttle behavior for planes without airspeed sensor changed from 4.5.7

and the corresponding PR
Plane: Fix level-off and throttle without airspeed sensor

@rmackay9
Copy link
Contributor Author

Hi @menschel, thanks, added to the list!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants