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

Tag tracking speed integration #2931

Merged

Conversation

gautierhattenberger
Copy link
Member

  • add a guided mode instruction in flight plan
  • a speed control to the tag tracking module
  • change guidance API to a more generic name (not related to GUIDED mode)
  • add a demo flight plan

replace #2913

It allows (for rotorcraft) to use all the possibilities of the guided
mode from a single instruction in the flight plan, but without leaving
the NAV mode as it was done before. Thus all capabilities of the FP are
still accessible.
[imu] connect aligner with 1efilter for imu
Guidance set functions are not limited to guidance mode. Use them when
possible to set masks correctly.
Copy link
Member

@noether noether left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is okei.

I am now reviewing the guidance for the rotorcraft since we would like, finally, to integrate the GVF.

@gautierhattenberger gautierhattenberger merged commit fafbde8 into paparazzi:master Oct 19, 2022
@gautierhattenberger gautierhattenberger deleted the tag_tracking_speed-integration branch October 19, 2022 07:27
@gautierhattenberger
Copy link
Member Author

@noether I also want to reorganize the guidance/nav for rotorcraft, so if you have your work in a public branch, let me know, at least to avoid double work and faster convergence (I have not started yet).

@noether
Copy link
Member

noether commented Oct 19, 2022

Ah cool! We did not start it yet (we started first with the guidance of the rover). Once we start, I will let you know it.

What I had in mind for the GVF is the following. GVF generates the desired 3D velocity or 3D acceleration, then sends such information to low-level controllers like INDI for the accelerations (this should work very well, we have done something similar with Ewoud when we did the collaborative transportation with rotorcraft). For the 3D velocity, it can always be split into vertical and horizontal, but the result maybe will not be the best.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants