Jump to content

NDs and MCDUs freeze


swetters

Recommended Posts

A319 CFM both NDs and both MCDUs froze on approach. I had already selected runway for approach on F-PLN and I changed it to another runway and approach on F-PLN . After this change both MCDUs and NDs stopped working. None of MCDU buttons didn't work anymore in VC or in 2D panels and ND range swithch or WX-radar swithches didn't affect to NDs anymore. Everything else was working fine and I was able to land without ND and MCDU. After landing I tried to switch engines, APU, batteries and all IRS switches off. Everything else turned off, except those NDs and MCDUs. Tried to power up aircraft again and those NDs and MCDUs still not working.

 

Is there some error log somewhere in Airbus or P3D folders to figure out what happened? Or have anyone else had the same problem?

Link to comment
Share on other sites

  • Deputy Sheriffs

You can turn on logging in the config tool. The logs will be stored in the install folder:

Aerosoft A318-A319 Professional\Data

Link to comment
Share on other sites

  • Deputy Sheriffs

Can not reproduce at the moment.

Please provide more details if it happens again. F-PLAN, when did you change, screenshots etc.

 

Link to comment
Share on other sites

Tried to copy that flight and got following results.

 

NDs and MCDUs did not stop to work at this time. Instead of that, all previous waypoints before final approach was lost.

 

EFHK RWY15 and LUSE1M selected

Please login to display this image.

 

Changed to RWY04L/LUSE1B

Please login to display this image.

 

This is what there was left after change

Please login to display this image.

Please login to display this image.

 

FMGS.log. I noticed those errors from it I have marked with orange. Maybe those had something to do with the previous error too..?

 

[16/07/2018 19:23:41:603]: FP change: WPT1 added: 12, [PODOM] via [ILS04L].
[16/07/2018 19:23:41:603]: FP change: WPT1 added: 12, [EMPEV] via [ILS04L].
[16/07/2018 19:23:41:603]: FP change: WPT1 added: 12, [HTV06] via [ILS04L].
[16/07/2018 19:23:41:603]: FP change: WPT1 added: 12, [HTV20] via [ILS04L].
[16/07/2018 19:23:41:604]: FP change: WPT1 added: 10, [580] via [].
[16/07/2018 19:23:41:604]: FP change: WPT1 added: 10, [MANUAL] via [].
[16/07/2018 19:23:41:604]: FP change: STAR added: [I04L] @ [04L/ILS04L]; 10. 102.

 

Many [16/07/2018 19:23:42:635]: PSDs (DI:1)  20.2 - DEC... entries between. I thought those have nothing to do with this, so I erased them to keep this more readable.


[16/07/2018 19:23:53:004]: FP change: WPT1 added: 2, [LUSEP] via [LUSE1B].
[16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [NAPUN] via [LUSE1B].
[16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [HK890] via [LUSE1B].
[16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [HK897] via [LUSE1B].
[16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [NEMVI] via [LUSE1B].
[16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [HK802] via [LUSE1B].
[16/07/2018 19:23:53:006]: FP change: WPT1 added: 2, [HK801] via [LUSE1B].
[16/07/2018 19:23:53:006]: FP change: WPT1 added: 2, [PODOM] via [LUSE1B].
[16/07/2018 19:23:53:006]: FP change: WPT ersd: 12, [PODOM], at pos:12.
[16/07/2018 19:23:53:006]: FP change: STAR added: [LUSE1B] @ [04L/]; 2. 79.
[16/07/2018 19:23:53:006]: Prev WPT error.
[16/07/2018 19:23:53:006]: Prev WPT error.
[16/07/2018 19:23:53:053]: Prev WPT error.
[16/07/2018 19:23:53:904]: PredDes: 15,175 (total dist: 28.87).
[16/07/2018 19:23:53:904]: DECEL dist:  8.30. TotalDist:  28.87, Phase=4.     ALT=27396, ApprAltThr=7363. Managed=1.
[16/07/2018 19:23:53:904]: FlightParams: [27389, 197, 269] [-21.1, 0, 0, 0]. FM=-0.38,-2.27. TotalDist:29. DI=1.
[16/07/2018 19:23:54:111]: FP change, TMPY INSERTED A.
[16/07/2018 19:23:54:111]: MCDUAppType: 1.
[16/07/2018 19:23:54:111]: Arrival EFHK ILS04L,  3.0.
[16/07/2018 19:23:54:122]: RAD NAV: ARR ILS autotuned to: 111.90 (CRS 39).
[16/07/2018 19:23:54:133]: PredsPrAppr2: 0,12.
[16/07/2018 19:23:54:189]: FDComBankReq 1: -2.22, MGD:0. AB_AP_HDGmode_setDisp: 1; AB_AP_HDGmode: 0.00. Phase:4, modes:[1:3].
[16/07/2018 19:23:54:189]: PredDes: 3,12 (total dist: 0.00).
[16/07/2018 19:23:54:189]: FlightParams: [27384, 197, 269] [-22.1, 0, 0, 0]. FM=-0.36, 0.42. TotalDist:0. DI=1.

 

Many [16/07/2018 19:23:54:243]: FDComBankReq 1:  0.42, MGD:1. AB_AP_HDGmode_setDisp: 1... (like three rows above) entries


Error in putPt(): LUSEP(9692), CAS=-1008.963606.
Error in putPt(): NAPUN(9693), CAS=-1198.485772.
Error in putPt(): HK890(9694), CAS=-1350.894954.
Error in putPt(): HK897(9695), CAS=-1462.536892.
Error in putPt(): NEMVI(9696), CAS=-1534.641634.
Error in putPt(): HK802(9697), CAS=-1534.641634.
Error in putPt(): HK801(9698), CAS=-1509.173042.
Error in putPt(): EMPEV(9686), UTC=-803.842156.
Error in putPt(): HTV06(9687), UTC=-787.619156.
Error in putPt(): HTV20(9688), UTC=-706.914146.
Error in putPt(): EFHK(5), UTC=-650.474065.
[16/07/2018 19:23:55:014]: FDComBankReq 1:  0.53, MGD:1. AB_AP_HDGmode_setDisp: 1; AB_AP_HDGmode: 0.00. Phase:4, modes:[3:3].
[16/07/2018 19:23:55:014]: Prev WPT error.

 

More [16/07/2018 19:23:55:069]: FDComBankReq 1: -2.24... entries

[16/07/2018 19:23:57:067]: Prev WPT error.
[16/07/2018 19:23:57:133]: FDComBankReq 1:  0.71, MGD:1. AB_AP_HDGmode_setDisp: 1; AB_AP_HDGmode: 0.00. Phase:4, modes:[3:3].
[16/07/2018 19:23:57:133]: [fly_lnav] Empty WPT LUSEP skipped.

Link to comment
Share on other sites

This is happening with NavDataPro which came with the Airbus. I have Navigraph subscription but my Navigraph FMS Data Manager is not yet recognizing the new Airbus. However there should be come new AIRAC cycle on 19 Jul so maybe I'm able to change the data after that and test also what happens with Navigraph.

 

Thanks for checking this!

Link to comment
Share on other sites

For what it's worth, I encountered a similar issue last night on my initial test flight of the A318.  I added the Avianca repaint to the sim, and flew from SKSM to SKBO.  Things were mostly fine until I got on the approach to SKBO.  I was flying in on the ISVA2E approach to land on runway 13R.  One of the features of this approach is that you can be cleared direct to the final fix at AMVES, bypassing NOR03, NOR04, NOR05, PULDI, etc.  I had gone into the MCDU and attempted to delete some of those intermediate fixes, and both the MCDU and ND locked up as a result.  The plane was still flying, and fortunately, I was able to manually land it on 13R at SKBO by hand.  All of the other systems were responsive.

 

I believe I had FSUIPC's autosave feature turned on at 10 minute intervals, so it is possible I might have a save file from before this happened, if it would be helpful.

Link to comment
Share on other sites

  • Deputy Sheriffs
On 7/16/2018 at 7:32 PM, swetters said:

Tried to copy that flight and got following results.

 

NDs and MCDUs did not stop to work at this time. Instead of that, all previous waypoints before final approach was lost.

 

EFHK RWY15 and LUSE1M selected

Please login to display this image.

 

Changed to RWY04L/LUSE1B

Please login to display this image.

 

This is what there was left after change

Please login to display this image.

Please login to display this image.

 

FMGS.log. I noticed those errors from it I have marked with orange. Maybe those had something to do with the previous error too..?

 

[16/07/2018 19:23:41:603]: FP change: WPT1 added: 12, [PODOM] via [ILS04L].
[16/07/2018 19:23:41:603]: FP change: WPT1 added: 12, [EMPEV] via [ILS04L].
[16/07/2018 19:23:41:603]: FP change: WPT1 added: 12, [HTV06] via [ILS04L].
[16/07/2018 19:23:41:603]: FP change: WPT1 added: 12, [HTV20] via [ILS04L].
[16/07/2018 19:23:41:604]: FP change: WPT1 added: 10, [580] via [].
[16/07/2018 19:23:41:604]: FP change: WPT1 added: 10, [MANUAL] via [].
[16/07/2018 19:23:41:604]: FP change: STAR added: [I04L] @ [04L/ILS04L]; 10. 102.

 

Many [16/07/2018 19:23:42:635]: PSDs (DI:1)  20.2 - DEC... entries between. I thought those have nothing to do with this, so I erased them to keep this more readable.


[16/07/2018 19:23:53:004]: FP change: WPT1 added: 2, [LUSEP] via [LUSE1B].
[16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [NAPUN] via [LUSE1B].
[16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [HK890] via [LUSE1B].
[16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [HK897] via [LUSE1B].
[16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [NEMVI] via [LUSE1B].
[16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [HK802] via [LUSE1B].
[16/07/2018 19:23:53:006]: FP change: WPT1 added: 2, [HK801] via [LUSE1B].
[16/07/2018 19:23:53:006]: FP change: WPT1 added: 2, [PODOM] via [LUSE1B].
[16/07/2018 19:23:53:006]: FP change: WPT ersd: 12, [PODOM], at pos:12.
[16/07/2018 19:23:53:006]: FP change: STAR added: [LUSE1B] @ [04L/]; 2. 79.
[16/07/2018 19:23:53:006]: Prev WPT error.
[16/07/2018 19:23:53:006]: Prev WPT error.
[16/07/2018 19:23:53:053]: Prev WPT error.
[16/07/2018 19:23:53:904]: PredDes: 15,175 (total dist: 28.87).
[16/07/2018 19:23:53:904]: DECEL dist:  8.30. TotalDist:  28.87, Phase=4.     ALT=27396, ApprAltThr=7363. Managed=1.
[16/07/2018 19:23:53:904]: FlightParams: [27389, 197, 269] [-21.1, 0, 0, 0]. FM=-0.38,-2.27. TotalDist:29. DI=1.
[16/07/2018 19:23:54:111]: FP change, TMPY INSERTED A.
[16/07/2018 19:23:54:111]: MCDUAppType: 1.
[16/07/2018 19:23:54:111]: Arrival EFHK ILS04L,  3.0.
[16/07/2018 19:23:54:122]: RAD NAV: ARR ILS autotuned to: 111.90 (CRS 39).
[16/07/2018 19:23:54:133]: PredsPrAppr2: 0,12.
[16/07/2018 19:23:54:189]: FDComBankReq 1: -2.22, MGD:0. AB_AP_HDGmode_setDisp: 1; AB_AP_HDGmode: 0.00. Phase:4, modes:[1:3].
[16/07/2018 19:23:54:189]: PredDes: 3,12 (total dist: 0.00).
[16/07/2018 19:23:54:189]: FlightParams: [27384, 197, 269] [-22.1, 0, 0, 0]. FM=-0.36, 0.42. TotalDist:0. DI=1.

 

Many [16/07/2018 19:23:54:243]: FDComBankReq 1:  0.42, MGD:1. AB_AP_HDGmode_setDisp: 1... (like three rows above) entries


Error in putPt(): LUSEP(9692), CAS=-1008.963606.
Error in putPt(): NAPUN(9693), CAS=-1198.485772.
Error in putPt(): HK890(9694), CAS=-1350.894954.
Error in putPt(): HK897(9695), CAS=-1462.536892.
Error in putPt(): NEMVI(9696), CAS=-1534.641634.
Error in putPt(): HK802(9697), CAS=-1534.641634.
Error in putPt(): HK801(9698), CAS=-1509.173042.
Error in putPt(): EMPEV(9686), UTC=-803.842156.
Error in putPt(): HTV06(9687), UTC=-787.619156.
Error in putPt(): HTV20(9688), UTC=-706.914146.
Error in putPt(): EFHK(5), UTC=-650.474065.
[16/07/2018 19:23:55:014]: FDComBankReq 1:  0.53, MGD:1. AB_AP_HDGmode_setDisp: 1; AB_AP_HDGmode: 0.00. Phase:4, modes:[3:3].
[16/07/2018 19:23:55:014]: Prev WPT error.

 

More [16/07/2018 19:23:55:069]: FDComBankReq 1: -2.24... entries

[16/07/2018 19:23:57:067]: Prev WPT error.
[16/07/2018 19:23:57:133]: FDComBankReq 1:  0.71, MGD:1. AB_AP_HDGmode_setDisp: 1; AB_AP_HDGmode: 0.00. Phase:4, modes:[3:3].
[16/07/2018 19:23:57:133]: [fly_lnav] Empty WPT LUSEP skipped.

Hi, when changing from LUSE1M to 1B you already where on LUSE1M. Have you done that in HDG or NAV mode? Of course it should be possible.

 

Please login to display this image.

Link to comment
Share on other sites

  • Deputy Sheriffs
9 hours ago, cparrott73 said:

For what it's worth, I encountered a similar issue last night on my initial test flight of the A318.  I added the Avianca repaint to the sim, and flew from SKSM to SKBO.  Things were mostly fine until I got on the approach to SKBO.  I was flying in on the ISVA2E approach to land on runway 13R.  One of the features of this approach is that you can be cleared direct to the final fix at AMVES, bypassing NOR03, NOR04, NOR05, PULDI, etc.  I had gone into the MCDU and attempted to delete some of those intermediate fixes, and both the MCDU and ND locked up as a result.  The plane was still flying, and fortunately, I was able to manually land it on 13R at SKBO by hand.  All of the other systems were responsive.

 

I believe I had FSUIPC's autosave feature turned on at 10 minute intervals, so it is possible I might have a save file from before this happened, if it would be helpful.

Why did you start deleting? Just choose a direct to via DIR TO

Link to comment
Share on other sites

9 hours ago, masterhawk said:

Hi, when changing from LUSE1M to 1B you already where on LUSE1M. Have you done that in HDG or NAV mode? Of course it should be possible.

 

Please login to display this image.

 

I'm not sure how it's working in real aircraft, but in sim, especially if using default ATC, it's very useful feature you can change the approach without problems when you already are flying the first approach programmed. Normally you get the runway from default ATC so late, that the last enroute waypoint is already far away behind you. :)

 

In my both cases, NAV mode was on when I just changed the runway and STAR from MCDU. After change of course HDG mode, because there wasn't anymore route to fly with NAV mode. I supposed that aircraft just starts flying the new selected one... This is how it worked with previous version of Airbus in FSX without any problems.

Link to comment
Share on other sites

13 hours ago, masterhawk said:

Why did you start deleting? Just choose a direct to via DIR TO

 

A valid question - and indeed, I have used DIR TO many times.  I have attached the chart below to help explain it better.

 

In this case, I was between ISVAT and FLOTE, and did not want to go direct to AMVES until I reached NOR02.  So at that point, I was trying to delete NOR03, NOR04, NOR05, and PULDI from the flight plan in the MCDU, and just go direct from NOR02 to AMVES in the flight plan.

 

Hope this helps - if there is a better way of accomplishing what I tried to do, I'm willing to learn!

Please login to display this image.

Link to comment
Share on other sites

  • Deputy Sheriffs
9 minutes ago, cparrott73 said:

 

A valid question - and indeed, I have used DIR TO many times.  I have attached the chart below to help explain it better.

 

In this case, I was between ISVAT and FLOTE, and did not want to go direct to AMVES until I reached NOR02.  So at that point, I was trying to delete NOR03, NOR04, NOR05, and PULDI from the flight plan in the MCDU, and just go direct from NOR02 to AMVES in the flight plan.

 

Hope this helps - if there is a better way of accomplishing what I tried to do, I'm willing to learn!

Please login to display this image.

Ok, then try this method:

Please login to display this image.

Link to comment
Share on other sites

4 hours ago, masterhawk said:

Ok, then try this method:

Please login to display this image.

 

Thanks so much for the tip.  I'll give that a try once the latest update to the A318/A319 becomes available.

 

Link to comment
Share on other sites

Navigraph FMS data now supports A318-319 so I tried this with it too.

 

Results:

 

Changed runway and STAR after flying over LUSEP and NAPUN total 5 times from rwy15 to rwy04L and back again. Everything works perfectly and no errors in FMGS.log.

 

So in my case I think changing navdata from NavDataPro to Navigraph solved this issue.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use