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

MC - Loops maneuvers when MPC_XY_CRUISE > MPC_XY_VEL_MAX #11420

Closed
BazookaJoe1900 opened this issue Feb 9, 2019 · 9 comments
Closed

MC - Loops maneuvers when MPC_XY_CRUISE > MPC_XY_VEL_MAX #11420

BazookaJoe1900 opened this issue Feb 9, 2019 · 9 comments

Comments

@BazookaJoe1900
Copy link
Member

BazookaJoe1900 commented Feb 9, 2019

Reducing the MPC_XY_VEL_MAX to lower value then MPC_XY_CRUISE make the drone to fly in very strange way, it makes "loops" and fly backwards every few seconds.

This was tested on simulator only.
https://logs.px4.io/plot_app?log=14e8cf1c-2fca-4cf8-ba0d-26ea8c5dd5d1
To reproduce:
• Run simulator, with default parameters
• takeoff and fly-to remote location
• everything normal
• set MPC_XY_VEL_MAX 2
• you will see that every ~10 second the drone fly back, do some strange loop
• set MPC_XY_ CRUISE 2
• the drone fly slow, but ok
image

@dagar
Copy link
Member

dagar commented Feb 11, 2019

@bresch @Stifael any input here?

@bresch
Copy link
Member

bresch commented Feb 11, 2019

Ouch, we should force cruise < max

@dagar dagar added the bug label Feb 11, 2019
@BazookaJoe1900
Copy link
Member Author

@bresch how can you 'force' that? is it ok by you to change the parameter flash value if it doesn't apply the rule? or just whereever it being get() do the constrain?

@bresch
Copy link
Member

bresch commented Mar 7, 2019

Usually we constrain the parameter when we read using .get() and change the parameter using a .set(val).

Like here:
https://github.com/PX4/Firmware/blob/684e2974ac042e6ba2168f06bf91be4fbb7b6050/src/modules/mc_pos_control/mc_pos_control_main.cpp#L404

@BazookaJoe1900
Copy link
Member Author

@bresch for MPC_XY_CRUISE, there is no single point where we read the parameter and can modify it, it uses the new px4_params defined that I am not sure where I can rightlly fix that.

@stale
Copy link

stale bot commented Jun 24, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@bresch
Copy link
Member

bresch commented Jun 25, 2019

Don't close that

@stale stale bot removed the Admin: Wont fix label Jun 25, 2019
@BazookaJoe1900
Copy link
Member Author

I am not sure what fixed this behavior but it doesn't happens on current master enymore.
@bresch you can check this too and close

@bresch
Copy link
Member

bresch commented Jul 6, 2019

Fixed by #12404

@bresch bresch closed this as completed Jul 6, 2019
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

3 participants