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

GPS Fix estimation (dead reconing, RTH without GPS fix) for fixed wing #8347

Merged
merged 83 commits into from
Dec 8, 2023

Conversation

RomanLut
Copy link
Contributor

@RomanLut RomanLut commented Aug 21, 2022

GPS Fix estimation (dead reconing, RTH without GPS fix) for fixed wing

Video demonstration

IMAGE ALT TEXT HERE

There is possibility to allow plane to estimate it's position when GPS fix is lost.
The main purpose is RTH without GPS.
It works on fixed wing only.

Up-to-date description:
https://github.com/RomanLut/inav/blob/submit-gps-fix-estimation/docs/GPS_fix_estimation.md

Requires configurator change:
iNavFlight/inav-configurator#1669

@RomanLut
Copy link
Contributor Author

Tested in simulator only :(

@JulioCesarMatias
Copy link
Collaborator

JulioCesarMatias commented Aug 21, 2022

I think some problems occurred during your push... Because you have several files modified, with the HIL mode included... You have 2 options:

1 - Close this PR and open a new one with only the modifications of this new recurse.

2 - Sync the branch of this PR with the Master, and delete the files from the HIL mode.

As there were many files changed, I myself couldn't read the algorithm and understand what you changed to add the feature (maybe it's even laziness on my part)

@JulioCesarMatias
Copy link
Collaborator

yeah... this PR is hard to analyze now, I'll leave it for the future

@JulioCesarMatias
Copy link
Collaborator

JulioCesarMatias commented Aug 21, 2022

the "dead-reckoning" part of the coordinates, wind and fuselage velocity also exists in a new AHRS that I'm working on bringing to iNav... Glad we had the same idea ^^

@JulioCesarMatias
Copy link
Collaborator

the "BOXGPSOFF" option should only be kept during testing before that one day it is approved to merge... It will be good help for Dev's testing... When this feature has a final version, I recommend removing the option to force the GPS failure (I don't think you want users bothering you and saying that your algorithm crashes their planes)

@DzikuVx
Copy link
Member

DzikuVx commented Aug 22, 2022

@RomanLut please update docs and resolve conflicts please

@RomanLut RomanLut changed the title GPS Fix estimation (dead reconing, RTH without GPS) for fixed wing GPS Fix estimation (dead reconing, RTH without GPS fix) for fixed wing Aug 22, 2022
@RomanLut
Copy link
Contributor Author

@RomanLut please update docs and resolve conflicts please

done.

@breadoven
Copy link
Collaborator

Does the wind estimator only seem to work if you fly in circles ? This is typically how wind estimators work with software for paragliders/hang gliders etc, either rely on flying in circles (thermaling) or flying in zig zags was another option.

@RomanLut
Copy link
Contributor Author

Zigzag should work too.

Wind estimator does estimation when attititude changes by ~10 degrees. Then estimated wind vector is updated with 5% of computed value. ~36 estimations in circle is enough to get good estimation.

https://drive.google.com/file/d/0ByvTkVQo3tqXVzBYQUZicUNvbEE/view?resourcekey=0-s-7v3PgOUrZt7fI6JNlu-Q

@shota3527
Copy link
Contributor

shota3527 commented Sep 26, 2022

@RomanLut

Cruise airspeed is specified in m/s.

To convert km/h to m/s, multiply by 27.77.

Example: 100 km/h = 100 * 27.77 = 2777 m/s

is this cm/s or m/s ?

@RomanLut
Copy link
Contributor Author

is this cm/s or m/s ?

You are right, it should be cm/s, updated documentation. Thanks.

@b14ckyy
Copy link
Collaborator

b14ckyy commented Dec 9, 2022

Hi @RomanLut
I want to real flight test this feature in the next days. But it has conflicts. Can you solve them so I can put it in a test build?

…-gps-fix-estimation

removed GPS Off box
implemented Disable GPS sensor fix logic condition
@RomanLut
Copy link
Contributor Author

RomanLut commented Aug 9, 2023

@RomanLut I'm moving this to INAV 7. But I'd like to merge whenever you say it's safe to merge. So, is it safe to merge?

Feature is ready to merge now

@konstkarapan
Copy link

Sounds very interesting. Could this be implemented for multirotors as well?

@DangerD1024
Copy link

Any workaround with spoofing?

@DzikuVx
Copy link
Member

DzikuVx commented Oct 27, 2023

@RomanLut thi somehow got below my radar :( Can you resolve conflicts and then we will schedule for 7.1?

@DzikuVx DzikuVx modified the milestones: 7.0, 7.1 Oct 27, 2023
@RomanLut
Copy link
Contributor Author

@RomanLut thi somehow got below my radar :( Can you resolve conflicts and then we will schedule for 7.1?

Resolved

@DzikuVx
Copy link
Member

DzikuVx commented Nov 3, 2023

@RomanLut damn, we have more conflicts now....

@RomanLut
Copy link
Contributor Author

RomanLut commented Nov 3, 2023

@RomanLut damn, we have more conflicts now....

@DzikuVx Resolved

@DzikuVx DzikuVx modified the milestones: 7.1, 8.0 Dec 8, 2023
@DzikuVx DzikuVx merged commit cb1964b into iNavFlight:master Dec 8, 2023
15 checks passed
@bakwc
Copy link

bakwc commented Dec 8, 2023

Cool!

@RomanLut
Copy link
Contributor Author

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

Successfully merging this pull request may close these issues.