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

FW auto land with intermittent terrain data #6456

Closed
dagar opened this issue Jan 28, 2017 · 3 comments
Closed

FW auto land with intermittent terrain data #6456

dagar opened this issue Jan 28, 2017 · 3 comments

Comments

@dagar
Copy link
Member

dagar commented Jan 28, 2017

Fixed wing crash reported by @Flying_Forfun on px4 discuss during auto land with a lidar light. Unfortunately no sdlog is available, which is another bug.

During fixed wing auto land the terrain data becomes intermittant and due to the confusion the vehicle starts climbing, initiates flare at > 60m and stalls during the portion where the pitch setpoint is forced (https://github.com/PX4/Firmware/blob/master/src/modules/fw_pos_control_l1/fw_pos_control_l1_main.cpp#L1668)

@AndreasAntener @Tumbili what do you think?

http://discuss.px4.io/t/cant-switch-out-of-mission-mode-during-a-mission/2294

land_crash

@LorenzMeier
Copy link
Member

That whole feature is highly experimental and not application-hardened. It will need some love and whoever picks it up needs a bit of time. We do have a lidar in Gazebo (mounted to the optical flow iris), so the best would be to start with a pull request for sitl_gazebo which adds it to the plane model and starting testing there.

@dagar
Copy link
Member Author

dagar commented Feb 9, 2017

From a proper log for reference.

bad_flare3

When the altitude setpoint (green) drops to ~190m the vehicle is landing, but again flares early.

The FW position controller should be aborting landing if the the terrain data is reported invalid (not logged), but only if the last update is > 1s. These dropouts are much shorter.

@dagar
Copy link
Member Author

dagar commented Feb 9, 2017

@LorenzMeier do you think an appropriate fix here would be EKF2 tuning (EKF2_RNG_NOISE, EKF2_RNG_GATE), better handling of terrain data in fw_pos_ctrl (much shorter timeout), or both?

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

2 participants