I am quite a Newbie to P3V5 and all the add-ons, so please be gentle 😉

I managed to get everything up&running with the latest versions of all that add-ons and "modules" with only some glitches left.

But: In wondered why there is no working VOR/ILS within Prepar3D. First I thought the data within the scenery is outdated and "injected" actual data via Navdatapro. Even with the right values, for example EDDL 23L ILS IDSW 109.9 no Info from the ILS, no glidescope etc etc. 

By chance the VRinsight FCU (Airbus) was disconnected and, big surprise, the data was there, reconnected, data gone again.

Perhaps there is an issue with the A320 module, Linda and FUSIPC? I can only "believe" that wihtin the mixture of the add-ons the frequencies get somewhat "messed-up". For example when progged the correct ILS, the ND shows a different Navaid, sometimes some khz down the correct value?

Any hints?

Edited December 8, 20205 yr by ScotFlieger

Apologises for the delay but I needed to re-configure my system to look at this issue. The main issue is that the Aerosoft NavData Pro installer does not recognise the FSLabs A3XX under P3Dv5. This means that the A3XX is limited to the default navdata provided by FSLabs instead of the latest.

Within the Aerosoft NavData Pro installer 1.0.7.1 I was able to change the installation address to c:/users/{name}/documents/prepar3d v5 add-ons/ and install the latest data set 2013R1. I recommend that after installing the data set you check the folder for older data. I then reloaded the FSLabs A320 and checked the MCDU for the correct data set. I was able to tune to EDDL 23L IDSW on 109.9MHz and fly an ILS approach.

I hope this helps.

 

Dear Andrew,

thanks for your help. Yes, the actual installer has some "problems" with V5 and A3xx, but I already managed to "inject" the data; I think I did it somehow tike you. 

But: The ILS IDSW with 109.9 is "there" and listed, also seen by the MCDU and I can fly an ILS approach with disconnected VRinsight. I admit, its strange.

 

But I will crosscheck again, perhaps the problem is only in my head....

 

 

When I did my test I was using the VRInsight Combo 2 Airbus (MCP2a) throughout. I used it to select ILS on the PFD and to engage LOC and APR modes. The frequency for ILS 23L was obtained via the MCDU as my Destination runway/approach. I did not check that NAV1 was set to 109.90 but its absence could be a FSLabs design issue. I will check when I get the opportunity.

I did a further test. I was able to use the MCP radio to tune NAV1 to a different frequency (overriding the MCDU destination runway) and carry out an automatic ILS approach.

Thanks again for your looking into it and sorry for my late reply.

Yes, I also assume that it is perhaps an fslabs issue. I fly EDDK-EDDL sometimes 10x a day and know all the frequencies by heart. Reinstalled Airbus and the data base, ILS frequs are always displayed right  in the MCDU (109.90 for 24l, 110.9 for 14L at EDDK). ILS approach still works only "sometimes". When not working, I see for example a freq of 109.89 instead of 109.90. Its just a wild guess but perhaps there is a "lost in translation" somewhere in between. 

 

Thanks again for your support,  I will try to find a "rule" between working and not working....

 

It´s me again. No able to find any "logic" behind the missing data.

I set up a flight from EDDL-EDDK with "fully progged" Airbus via MCDU right after the book and saved that scenario. When I load that scenario first time, everything is fine. After landing in Cologne I reset/restart the same scenario and fly again, this time without data from IKES 110.90. 

Perhaps it is a glitch within Prepar3D, for the time beeing I can live with that, thank god there is VASI/PAPI 🙂

Thank you very much for your time. 

 

 

 

This is not something LINDA can fix. All airport data comes from the Flt Sim, NavData and any add-ons.