Skip to content

Flight path vector for FrSky S.Port telemetey #324

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

Closed
teckel12 opened this issue Jun 29, 2019 · 1 comment · Fixed by #336
Closed

Flight path vector for FrSky S.Port telemetey #324

teckel12 opened this issue Jun 29, 2019 · 1 comment · Fixed by #336

Comments

@teckel12
Copy link
Owner

Is your feature request related to a problem? Please describe

Flight path vector only works on Crossfire, make it work on FrSky S.Port

Describe the solution you'd like

Flight path vector added to S.Port

Describe alternatives you've considered

Don't offer support on S.Port telemetry

Additional context

For this to work, a YAW sensor will need to be added to INAV. Not a huge deal, as there's already a switch to replace the accelerometer values (which are never used anyway) with ROLL and PITCH. Just add YAW as well.

Flight path vector is established when comparing YAW (direction pointing) with Hdg (direction heading).

As a bonus with FrSky S.Port support, the flight path vector could use the vario data to also calculate the pitch of the flight path vector (not just the yaw). Actually, this could be done in a basic way on Crossfire too even without a vario sensor using historical altitude data. May work even better as altitude changes can be averaged out. Will look into...

@teckel12 teckel12 self-assigned this Jun 29, 2019
@teckel12
Copy link
Owner Author

Vertical speed now included with latest Crossfire Rx firmware and INAV, so introducing vertical speed into the calculation of the flight path vector is now possible.

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

Successfully merging a pull request may close this issue.

1 participant