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

Hold Pos in the first GPS Rescue stage as in the LAND stage #13545

Open
wshadw opened this issue Apr 18, 2024 · 1 comment
Open

Hold Pos in the first GPS Rescue stage as in the LAND stage #13545

wshadw opened this issue Apr 18, 2024 · 1 comment
Labels
Template: Feature Request Set by auto_close_issue.

Comments

@wshadw
Copy link

wshadw commented Apr 18, 2024

Is your feature request related to a problem? Please describe

The problem is that during the first stage (ASCEND), the drone continues to drift forward and may crash.
I have encountered this problem several times while flying in the mountains close to the surface.

Describe the solution you'd like

I think it's worth adding a position hold in the first stage (ASCEND) of the rescue, the same as in the landing stage (LAND).

Describe alternatives you've considered

For now I have solved the problem by setting Angle and Throttle to 1900 for the first stage of connection loss. This allows you to change the vector of forward motion to upward motion, preventing a possible collision with an obstacle ahead. But with such settings it is dangerous to fly in the forest or fly under obstacles, since the drone will slam into it at full speed.

Other information

No response

@wshadw wshadw added the Template: Feature Request Set by auto_close_issue. label Apr 18, 2024
@wshadw wshadw changed the title Hold Pos in the first GPS Rescue stage as in the ASCEND stage Hold Pos in the first GPS Rescue stage as in the LAND stage Apr 18, 2024
@jsk2084
Copy link

jsk2084 commented May 6, 2024

Prior to 4.5 (and 4.4), ascend mode worked a bit differently. Instead of leveling “flat” and climbing, it would attempt to fly straight up with little to no velocity. During the development of the newer versions of Rescue, I did extensive testing and found that the IMU would drift at a steady rate away from correct heading. To address this vulnerability, the ascent mode was changed to what we have now.

However, many changes to the IMU code have been made since then - It’s much more robust and less prone to these heading errors. I would be interested in seeing how the older ascent phase code would do now in prolonged climbs, after those imu improvements.

Aside from that heading drift vulnerability, the previous ascent mode was more refined than the current “level flat” method, and GPS Rescue might benefit if we brought it back. I’d love to help test this and find out. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Template: Feature Request Set by auto_close_issue.
Projects
None yet
Development

No branches or pull requests

2 participants