-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
create mc_rate_control (split out of mc_att_control) #12650
Conversation
49f678b
to
5056af4
Compare
a2fc430
to
396712e
Compare
As a single diff this is probably rather hard to review, however the majority of it was simply duplicating mc_att_control and gutting code on each side. Besides that the only real change is slightly different logic in the now standalone mc_rate_control for when to not run. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything I saw while scanning the code is in my opinion a huge leap in the right direction. I don't see a thing that breaks but I also couldn't study every single detail. It doesn't solve all problems but it doesn't have to but it makes it a lot easier and hence attractive for further improvements.
We should do some testing especially also of the acro, stabilized, rattitude modes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I started looking into details but it's too much to look through right now.
Tested on PixRacer V4: Position Mode: Good. - Procedure Notes: Log: MASTER COMPARISON: Tested on CUAV V5+: Position Mode: Good. - Procedure Notes: Log: MASTER COMPARISON: |
Tested on NXP FMUK66 v3: Modes Tested Procedure Notes: Log: Tested on Pixhawk Pro v4Pro: Modes Tested Procedure Notes: Log: Tested on Pixhawk 4 mini v5: Modes Tested Procedure Notes: Log: |
Tested on Pixhawk 2 Cube v3Loaded el PR12650 and vehicle did not arm, and popup message said "Preflight Fail: Compass #2 uncalibrated. The vehicle has failed a pre-arm check. In order to arm the vehicle, resolve the failure." Loaded Stable firmware and vehicle calibrated and armed without issues. **Log ** |
a1a57f9
to
0570bbd
Compare
@jorge789 this is an unrelated problem caused by the buggy icm20948 driver (previously reported itself erroneously as another mpu9250). You should be seeing the same issue in master until you recalibrate. |
3c1f811
to
b69f734
Compare
de792e6
to
21f68bb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, apart from latency considerations.
Not ready to merge until all VTOL types have been carefully tested. |
21f68bb
to
01670db
Compare
01670db
to
be25215
Compare
d49c1ad
to
bf9c967
Compare
Tested on Pixhawk 4 mini v5 |
bf9c967
to
2b2d61b
Compare
What is the status of this? Was it tested on all VTOL types? Is anything else blocking? |
These changes check out in SITL and have been tested to some extent on real hardware by the test team. I'm not absolutely confident all VTOL subtleties have been preserved, but to be honest that's a pretty good indicator we have a larger problem. It's early in the v1.11 release cycle. Let's get this in, keep an eye out for possible regressions, and continue working towards a fundamentally better architecture that's maintainable. Thanks for the help everyone! |
Testing