No ILS Capture

[Dazza]

Help i have flown this aircraft 3 times now and everytime without incident, but everytime i have ILS sw on LOC sw on but it does not capture the localiser or glide path, pls help

[jaybird]

I just completed a flight KLAS-KLAX, landed ILS25L, and it captured flawlessly, so you need to provide more data, this is not enough to help anyone debug your problem.

What airport, what runway, any other pertinent detail.

Inibuilds is inundated with stuff right now, just saying things like "no workie here" doesn't help. Yes, there are issues, we need to be a supportive community, and actually help them in order to help us 🙂 

Jack

[RTK1972]

same for me happens. if i select runway 25R (EDDF) in FMS, the ILS frequency shows up but if you approach the airport ILS is not "activating".

This happens with every airport i am approaching and try to do a ILS approach (EIDW, LPPT, LEBL and EDDM)

[richboy2307]

Hi @Dazza/ @RTK1972

Are you using 'SIM DEFAULT' navdata or 'NAVIGRAPH' on the OIS OPTIONS - THIRD PARTY page?

For the 'SIM DEFAULT' navdata, the ILS autotune feature is dependent on the scenery add-on used having properly defined the ILS frequencies for each runway. The ILS itself will exist and function, but as its not tied to the runway, it will simply not be autotuned.

 

Best Practice - Approach Preperation

As part of your descent preparation,

• MFD FMS NAVAIDS page
  Verify the correct ILS station identifier (IDENT) is shown.
  - Refer to charts to find the IDENT of your specific ILS.
  - If the field is not properly populated, manually input the desired IDENT. 
  - The FREQ and CRS fields will update automatically upon entering the IDENT.
  
  E.g. For FACT ILS Z RWY 19 approach, we'd enter the ILS IDENT of 'KSI'.
   
  
  
• EFIS Control Panel - LS push button
  Verify that the LS button is pressed in and lit up green when passing 10,000ft. This will help ensure that approach guidance is shown on the PFD.
  
  
  When you are in range, the the tuned ILS IDENT, FREQ, CRS and DME (where coupled to the same station) will be shown on the bottom left corner of your PFD. You will also see the LOC/GS guidance diamonds.
  

Thanks!

[RTK1972]

i swotched it to Navigraph, because with Software neither a SID nor a STAR showed up and wasn't seleectable. So with Navigraph at least i was able to select the right SID or STAR approach, even though i don'T have a navigraph subscription...

[richboy2307]

@RTK1972

That sounds like your installed scenery is having a conflict with the default Navdata. 

51 minutes ago, RTK1972 said:

So with Navigraph at least i was able to select the right SID or STAR approach, even though i don'T have a navigraph subscription...

The iniBuilds A350 Airliner comes bundled with an older Navigraph AIRAC data (2303) by default as part of your purchase. The subscription is required to update to the latest, however without one you can still use the older cycle.

Thanks!
 

[jaybird]

3 hours ago, RTK1972 said:

same for me happens. if i select runway 25R (EDDF) in FMS, the ILS frequency shows up but if you approach the airport ILS is not "activating".

This happens with every airport i am approaching and try to do a ILS approach (EIDW, LPPT, LEBL and EDDM)

How do you do an approach? Are you flying a STAR, normally that would dump you into an IAF for an ILS approach right? That entry fix will have an altitude as well, and you should have your descent set up so you arrive at that fix with everything you need set, the only thing one needs to do is press the APR button, and activate the other FMS (at least I always do, I've seen some say that isn't necessary).

Do you see the localizer activate? 

BTW, I've now done KLAX-KATL, a Delta flight, landing 27L, and this time on 2024. Still have some performance issues, but everything worked.

Looks to me that your problem isn't the plane, its procedural or data. I have always had a Navigraph subscription, I recommend it.

Cheers,

Jack

 

[RTK1972]

but having an issue at every airport i fly to isn't realistic, isn't it ? And with the Fenix, as an examle, i don't have any issue.....

[henkhugo]

9 hours ago, richboy2307 said:

Hi @Dazza/ @RTK1972

Are you using 'SIM DEFAULT' navdata or 'NAVIGRAPH' on the OIS OPTIONS - THIRD PARTY page?

For the 'SIM DEFAULT' navdata, the ILS autotune feature is dependent on the scenery add-on used having properly defined the ILS frequencies for each runway. The ILS itself will exist and function, but as its not tied to the runway, it will simply not be autotuned.

 

Best Practice - Approach Preperation

As part of your descent preparation,

• MFD FMS NAVAIDS page
  Verify the correct ILS station identifier (IDENT) is shown.
  - Refer to charts to find the IDENT of your specific ILS.
  - If the field is not properly populated, manually input the desired IDENT. 
  - The FREQ and CRS fields will update automatically upon entering the IDENT.
  
  E.g. For FACT ILS Z RWY 19 approach, we'd enter the ILS IDENT of 'KSI'.
   
  
  
• EFIS Control Panel - LS push button
  Verify that the LS button is pressed in and lit up green when passing 10,000ft. This will help ensure that approach guidance is shown on the PFD.
  
  
  When you are in range, the the tuned ILS IDENT, FREQ, CRS and DME (where coupled to the same station) will be shown on the bottom left corner of your PFD. You will also see the LOC/GS guidance diamonds.
  

Thanks!

Tried is with both Navigraph and default data at FACT with two different results. On the default data it wont even let me enter the IDENT. See images attached for the Navigraph data results. Still doesn't work. It must also be noted that the VOR is not giving DME data at all. 

[richboy2307]

Hi @henkhugo

I am not able to reproduce your issue. Just tried on both Navdata sets in both FS 2020 & 2024 (with Asobo FACT scenery). Able to receive proper indications on the PFD and arm APPR mode.

Please try with an empty community folder, in case your scenery is causing some conflicts.

 

Thanks!

[henkhugo]

I have just tried at default KJAX scenery with the same results. No VOR needles, no DME and no ILS yet they show on the NAVRAD. 

Let me move everything but the A350 from my Community folder and re test at FACT 

[henkhugo]

8 hours ago, richboy2307 said:

Hi @henkhugo

I am not able to reproduce your issue. Just tried on both Navdata sets in both FS 2020 & 2024 (with Asobo FACT scenery). Able to receive proper indications on the PFD and arm APPR mode.

Please try with an empty community folder, in case your scenery is causing some conflicts.

 

Thanks!

After clearing the community folder we have VOR needles and DME at FACT. We even have ILS LOC showing on the ground! Now to find the conflict. 

[henkhugo]

@richboy2307 I have found the issue.

Something in that scenery file is clashing with the DME/VOR/ILS in the A350

There we go. DME, VOR needles, ILS LOC

[RTK1972]

in all honesty: This is a joke. The A350 is the only plane i have issues with. Even the Fenix has zero problems and it is way complex...

[CR7]

22 hours ago, richboy2307 said:

Hi @Dazza/ @RTK1972

Are you using 'SIM DEFAULT' navdata or 'NAVIGRAPH' on the OIS OPTIONS - THIRD PARTY page?

For the 'SIM DEFAULT' navdata, the ILS autotune feature is dependent on the scenery add-on used having properly defined the ILS frequencies for each runway. The ILS itself will exist and function, but as its not tied to the runway, it will simply not be autotuned.

 

Best Practice - Approach Preperation

As part of your descent preparation,

• MFD FMS NAVAIDS page
  Verify the correct ILS station identifier (IDENT) is shown.
  - Refer to charts to find the IDENT of your specific ILS.
  - If the field is not properly populated, manually input the desired IDENT. 
  - The FREQ and CRS fields will update automatically upon entering the IDENT.
  
  E.g. For FACT ILS Z RWY 19 approach, we'd enter the ILS IDENT of 'KSI'.
   
  
  
• EFIS Control Panel - LS push button
  Verify that the LS button is pressed in and lit up green when passing 10,000ft. This will help ensure that approach guidance is shown on the PFD.
  
  
  When you are in range, the the tuned ILS IDENT, FREQ, CRS and DME (where coupled to the same station) will be shown on the bottom left corner of your PFD. You will also see the LOC/GS guidance diamonds.
  

Thanks!

Hi there. Do I need to update the data if I using NAVIGRAPH on the OIS?

[henkhugo]

You need to find which scenery in your collection is causing the conflict. Would be interesting to see if the various sceneries has the same objects 

[richboy2307]

3 hours ago, RTK1972 said:

in all honesty: This is a joke. The A350 is the only plane i have issues with. Even the Fenix has zero problems and it is way complex...

The Fenix works externally to the sim, with all data lookup and ILS signal calculations also running external to it.

We understand your frustration, however there are sometimes limitations to doing things internally within the sim environment in the interest of cross-platform compatibility. These issues of sceneries affecting availability of procedures/data is for the most part a sim issue and will affect any Aircraft who rely on the sim for this basic function.

3 hours ago, CR7 said:

Hi there. Do I need to update the data if I using NAVIGRAPH on the OIS?

The plane comes with a Cycle 2303 data bundled by default. If you have an active Navigraph Subscription, it is recommended to update to the latest navdata cycle via the OIS. Instructions here: 

 

4 hours ago, henkhugo said:

Something in that scenery file is clashing with the DME/VOR/ILS in the A350

Glad you found it. Yeah not sure why OPST scenery is affecting this but glad you found the culprit. Worth reporting to the maker of the scenery as well.

As the solution has been found I will lock this thread now.

Solution: For anyone else coming across this thread, please follow the best practices mentioned above to set ILS IDENT and in case of issues try with an empty community folder to rule out conflicts.

Thanks!