freddiel 0 Posted March 23, 2020 Share Posted March 23, 2020 The other day, I began having a problem with the FMS and displays of the A320 family aircraft. Yesterday, I had the problem twice with the A321SL CFM and today I had the problem with the A319SL CFM. Yesterday, when the aircraft loaded to the turnaround state I have set default, all the display units were blank. I went to the pop-up menu and checked to see which state the aircraft was in, and it said turnaround. I clicked turnaround again and everything loaded fine. However, shortly into entering the route into the MCDU, it stopped recognizing any airways or waypoints. I rebooted the computer and tried to start the same flight again, but the exact same thing happened, even at the exact same airway/waypoint entry. (For what it's worth, the sequence where it stopped working was trying to enter Q93/SHRKS from MALET). I had been able to enter the first few as planned, but after that entry went wrong no other waypoints or airways were recognized by the aircraft. Today, the A319 loaded fine and all the screens loaded like they should, except the FGMC option at the top left of the "SELECT DESIRED SYSTEM" page on the MCDU simply didn't display. I clicked where it should have been and it loaded like normal. However, shortly into entering the route, the aircraft stopped recognizing any other waypoints or airways. I'm not sure if any other problems exist as I did not try to go any further in the flight planning process. Its AIRAC is current at cycle 2003 and there are no regular or experimental updates available in the ASUpdater. What can I do? Please login to display this image. Link to comment Share on other sites More sharing options...
Deputy Sheriffs Secondator 643 Posted March 23, 2020 Deputy Sheriffs Share Posted March 23, 2020 Hello freddiel, What version of the Airbus are you using? About the turnaround state issue where screens are blank, we are aware of this issue where the EXT PWR is not always connected when loading in turnaround state. We tried to have a look into this but unfortunately so far we have been unable to point where the issue lies. You can get around this by loading the turnaround state again and the displays should work again. About the navdata not working. What Navdata provider are you using? Do you have the correct provider selected through the configurator? What does the FMGS Data page say for the primary nav cycle? Link to comment Share on other sites More sharing options...
freddiel 0 Posted March 23, 2020 Author Share Posted March 23, 2020 Thanks for the quick response. I'm using 1.3.0.3 for both the A318/19 and A320/21. I use Navigraph to update the AIRAC cycle. I have attached an image of the FMGS page. The interesting part for me is that I had done plenty of flights in the Airbus before I encountered this problem, although only one flight since updating to 1.3.0.3. It could just be a coincidence that the flight plan I used for the last flight was compatible with cycle 1809 so I wouldn't have noticed an issue. Please login to display this image. Link to comment Share on other sites More sharing options...
Deputy Sheriffs Secondator 643 Posted March 23, 2020 Deputy Sheriffs Share Posted March 23, 2020 Yeah. The aircraft is definitely using the default NavDataPro 1809 cycle that it gets shipped with. Please change the cycle through the A3xx configurator to Navigraph and then the latest flight plans generated on simbrief or PFPX with 2003 cycle should work. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.