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

Copter: high altitude Non-GPS navigation using downward facing camera #23471

Open
rmackay9 opened this issue Apr 13, 2023 · 2 comments
Open

Copter: high altitude Non-GPS navigation using downward facing camera #23471

rmackay9 opened this issue Apr 13, 2023 · 2 comments

Comments

@rmackay9
Copy link
Contributor

rmackay9 commented Apr 13, 2023

This idea has appeared a few times over the years so here is an issue to consolidate the conversation about it.

The idea is to use a downward camera (probably mounted on a gimbal) to capture pictures of the terrain below at regular intervals and then compare these to set of images taken from known locations, find the best match and then extrapolate the vehicle's current position. This could then be used instead of the GPS to allow the vehicle to get safely home.

Some ideas:

  • A "mutual information" algorithm has been suggested as a good way to compare the live images from the stored images.
  • The zoom and heading of the two sets of images would be different so it might be necessary to crop and rotate the live images to better match the stored images.
  • The onboard terrain database could be useful in figuring out how much to zoom/crop the live image
  • The EKF normally requires position updates at 4hz (or higher) in order to maintain a good position and velocity estimate. If the images can't be captured at this rate it might be necessary to augment the position estimate with an optical flow based velocity estimate. It is possible that optical flow values could be calculated from the live video and the onboard terrain database.
  • The position and velocity estimates could be fed into the EKF using the VISION_POSITION_ESTIMATE and VISION_SPEED_ESTIMATE messages and then GPS/Non-GPS transitions could be used to handle the switch over between GPS and pictures.
@Ryanf55
Copy link
Collaborator

Ryanf55 commented Apr 17, 2023

Why is this tagged only to Copter? Couldn't it be used in Plane too?

@rmackay9
Copy link
Contributor Author

rmackay9 commented Apr 17, 2023

@Ryanf55,

Yes, it could/should work for Plane as well. The initial focus is on copters because they need the feature more than planes. Planes with an airspeed sensor can already dead reckoning fairly accurately for a couple of minutes at least. For copters it's only 30 seconds or less.

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