investigating INS 9 - 1 deletes added waypoints

[Prof_Plumpy]

Doing a VHHX to RJTT flight. 

Diligently populating the INS with the next way points after 9.  They all happily show up on the minimap in the centre console. Entered in all new way points 1-6. 6 being the last point needed to get to the ILS.  

When the INS flicked from 9-1 it deleted all the waypoints and reset them to 0000N 0000E.  Had to quickly re-enter the deleted 6 way points.  What did I do wrong? Not using GPS or any other function.  

So now we are following the INS but for the life of me it would not hold an altitude.  3000 set, 2500-3200 given.  She was all over the place.  Its hard to believe that the first plane that could do a Cat-3C autoland has so many issues holding a set altitude.  Or following an ILS. Or over flying a VOR without trying to do a 180 turn.  With each new 'update' there is a plethora of items that break.  

 

[richboy2307]

HI

10 hours ago, Prof_Plumpy said:

Diligently populating the INS with the next way points after 9.  They all happily show up on the minimap in the centre console. Entered in all new way points 1-6. 6 being the last point needed to get to the ILS.  

When the INS flicked from 9-1 it deleted all the waypoints and reset them to 0000N 0000E.  Had to quickly re-enter the deleted 6 way points.  What did I do wrong? Not using GPS or any other function.  

Did you import the waypoints from your OFP/Simbrief at any point? Or were they all always only manually entered?

If auto-import was used, there is logic that wipes the INS in order to import the next batch of waypoints, but this shouldn't trigger from fully manual entry normally.

10 hours ago, Prof_Plumpy said:

So now we are following the INS but for the life of me it would not hold an altitude.  3000 set, 2500-3200 given.  She was all over the place.  Its hard to believe that the first plane that could do a Cat-3C autoland has so many issues holding a set altitude. 

Could you please provide some screenshots showing your active modes + AFCS + configuration (flaps/gear) at the time? The team is working to fine-tune autopilot ALT HOLD behaviour particularly during configuration changes (Flaps or Gear) but if you can provide specific examples we can ensure those are specifically checked too.

Quote

 

Or following an ILS. Or over flying a VOR without trying to do a 180 turn.  With each new 'update' there is a plethora of items that break.  

 

Again, it would be more helpful if you can provide specific examples of scenarios where it didn't work as you expected? This would include steps taken before intercept, and particularly data such as heading, speeds, altitude, weights etc. Specifically with regards to ILS, you should not intercept at angles greater than 45 degree, preferably try less than 30 degrees to avoid massive overshoots or it failing to follow at all. 

 

Thanks!

[Prof_Plumpy]

Quote

If auto-import was used, there is logic that wipes the INS in order to import the next batch of waypoints, but this shouldn't trigger from fully manual entry normally.

 

INS auto import, then added manually. Was not aware it put in more waypoints, just figured it would load 9 then go back to waypoint 1. Maybe I should RTFM.  Tested in 1.0.4 and it did import the next 10. 

 

Runway 13 departure out of VHHX.  There is a VOR inline with the runway (TH VOR 115.5 heading 136). The plane will fly towards it, then wiggle/rock flies better after 1.0.4 (slight twitch) over top before settling back to 136. Nearing Max ToW of 226,000kg

 

Quote

Could you please provide some screenshots showing your active modes + AFCS + configuration (flaps/gear) at the time

No, all my screen shots are sunrise/sunset related.  Will try and capture more useful data.  Out of VHHX, past TH VOR, alt hold 7000 until WHISKY.  Clean configuration, 250knots. Past WHISKY you turn 90 degrees to intercept CH VOR 112.3, 104 degrees. 1.0.4 held the altitude much better.  When dialing FL290 into the AP the ALT jumped from 7000 to CAP 7200 and stayed there until I hit VNAV. 

Now the fun part, after hitting VNAV the engines went to idle, then up past max EPR in the TM box, then settled at CLIMB TM EPR.  Then it went to +5000FPM, lost speed and triggered AoA mode and TM turned off.  Intervened with 500fpm, then VNAV/TM with more speed and now nearing Japan at FL290. 

Step climp to LF310 from 290, the ALT box reads ALT CAP 29300 and the plane slowly climbs before hitting any alt change buttons (VNAV/VS).