-
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
fw_pos_ctrl: subtract trim pitch setpoint before TECS everywhere #14907
base: main
Are you sure you want to change the base?
Conversation
There was a question of interpretation of the various pitch limits in the fixedwing position controller (relative to the pitch setpoint offset or not). Let's settle this and make sure handled uniformly. |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
still relevant @sfuhrer |
Is there a reason this wasn't just merged? |
I've lost context here, but I recall there was confusion about the pitch (and various parameters) being an inconsistent mix of relative to the vehicle body frame and other cases that are relative to the pitch offset. I propose we all take a few minutes to review and schedule a short call to settle this. @CarlOlsson @sfuhrer @RomanBapst
We also need to make sure it's a clean/safe upgrade for existing users.
|
After brief discussion on slack the current consensus is to push the pitch offset into TECS itself so that the rest of the FW position controller can be kept simple and oblivious to the offset. All limits and configurable pitch settings are in the vehicle body frame. Does anyone have a different opinion? |
Probably just some clear documentation but will test it once I’m clear on the effects the changes will have. Having a pitch down on takeoff rollout is annoying so that will be good to get rid of. |
@dagar Also makes sense to me and shouldn't have effect on offboard, since it uses the same setpoint types |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
@sfuhrer @RomanBapst As discussed on Slack I don't understand why we would not subtract the trim pitch setpoint everywhere before pushing it into TECS. I noticed that the plane behaved differently when flying in position control mode compared to mission. I also added the change to places which I could not test, e.g. fw takeoff, so please review that more carefully.
Describe problem solved by this pull request
The limitation of the pitch setpoint was different in mission and position control
Describe your solution
Subract the trim pitch sp for position control mode in the same way as it is done for mission
Describe possible alternatives
A massive cleanup of the fw pos controller
Test data / coverage
I only tested position control so far