Jump to content

[1.0.7] LNAV not following SID route


crisk73
 Share

Recommended Posts

The flightplan is: LIPX LUMA5S LUMAV UZ982 ANC UL612 TRL UJ65 BAVES LGIR

LNAV is engaged but it doesn't even perform the first right turn as per SID, the plane goes straight ahead indefinitely.

Can anybody replicate it please? I tried several times but without success. Using Aerosoft NavdataPro cycle 1607.

Thanks.

Cris

GizmoLog.txt

IXEG_FMS_debug.txt

Link to comment
Share on other sites

i tried ro recreate your flight and had the same weird behavior. The aircraft does not try to join and follow the magenta to the right when engaging LNAV.

Because you did not select any arrival star neither runway (which was a problem on the past), i tried recreating the flight again but selecting BAVES1 arrival and runway 27. i selected the arrival procedure with no issue, as soon as i selected runway 27 and i had a gizmo soft crash!

 

I cleared everything and managed to complete the fmc programing including the arrival and runway.

 

Departed again and had the same weird LNAV behavior, i manually pressed LSk3 and then LSK1 skipping the initial LSK1 conditional and LSK2 (int) orders from the legs page and now LNAV was able to turn right and join the magenta properly.

A bit later i realized VNAV was unable to engage, i had to remove the miss approach procedure from the legs page leaving RW27 as the last step on the plan for the fmc to allow me engaging vnav and resume the flight.

 

conclusion:

there is a big mess here trying to recreate this flight, full of problems. I wonder whether this is related to navigraph database (running 1607rev2 here) or part of the fmc fine tuning still in progress.

 

the developers should try to recreate this flight and shed some light here.

 

Edited by mmerelles
misspelling
  • Upvote 1
Link to comment
Share on other sites

Thank you@mmerelles for your try. I don't think it's navdata fault as I have Aerosoft navdata and as I see the issue is the same.

Removing the first two conditional waypoints (750) and (intc) and manually selecting the first non conditional one makes the magenta line be joined but I remember I did this same route with 1.0.5 without problems. Thanks again!

Cris

Link to comment
Share on other sites

  • 2 months later...
  • 4 weeks later...

I just fixed a bug from another report that I believe is related to this.  Whenever you have an acute turn at a waypoint...and the next waypoint after the acute turn is too close to make (bypass)....then the plane would depart the LNAV path after teh waypoint BEFORE the acute turn.  This bug is due to our "look ahead" code that tries to anticiapte turns in order to give better LNAV tracking

I just enterd the route and see the waypoint combo I expected to see (OTBED > MONTY > WAL24)....and the route draws well now (it was kink'd before).  So I think this is fixed for the next update.

-tkyler

  • Upvote 1
Link to comment
Share on other sites

Thanks @tkyler. I found another problem regarding LNAV but in this case the waypoints aren't that close together. Departing LJLJ runway 12 and following either BERTA 2D or GIMIX 2D which both require a right turn after MG to intercept QDR 177. However, after passing MG the plane initiates a right turn but it never levels off on a 177 track. Instead it maintains right bank, doing 360s. I assume these two problems are not related but of course I might be wrong.

  • Upvote 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...