inav
inav copied to clipboard
iNavFlight
Landing direction
This is second part of https://github.com/iNavFlight/inav/pull/4961 For airplane it defined direction to land with aproach. https://github.com/iNavFlight/inav/issues/1814 https://github.com/iNavFlight/inav/issues/3670 https://github.com/iNavFlight/inav/issues/4070 For multirotors it defined head direction when landing. When 0 (default) it is disabled and work as before.
Is this possible to add a parameter to set landing direction when you launch wing, that case land direction should be the same as launch direction ?
@mistyk The default value 0 have this behavior, but this is very inaccurate. A 10 degree deviation at 150 meters approach is 26 meters drift.
that case land direction should be the same as launch direction ?
Yes, if take off under the wind and wind direction not change, will land under the wind.
This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. This issue / pull request will be closed if no further activity occurs within two weeks.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. This issue / pull request will be closed if no further activity occurs within two weeks.
If the average GPS direction of the first 10 to 15 meters after the launch are computed the resulting vector and position + starting altitude can be used as the virtual landing strip, maybe virtualy desplacing it further 5 meters or so in order to avoid hitting a touchdown point in front of the runway on approach.
Using the GPS course instead of the aircraft longitudinal axis would automaticaly compensate the virtual runway for any crosswin that might exist on take off and landing , provided that the pilot took off maintaining the runway axis for those initial 10-15 meters.
The landing vector should be used as the extended runway centerline that should be followed during the approach maneouvre, which if followed closely will again compensate for any wind drifting.
This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. This issue / pull request will be closed if no further activity occurs within two weeks.
This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. This issue / pull request will be closed if no further activity occurs within two weeks.
This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. This issue / pull request will be closed if no further activity occurs within two weeks.
This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. This issue / pull request will be closed if no further activity occurs within two weeks.
This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. This issue / pull request will be closed if no further activity occurs within two weeks.
This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. This issue / pull request will be closed if no further activity occurs within two weeks.
This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help. This issue / pull request will be closed if no further activity occurs within two weeks.
