• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSX ILS not working

PlayedByDemon

PlayedByDemon

Messages
198
Country
germany
Hi Fellows,

I am near to finish my V2.0 EDJA and I am encouting trouble with the ILS and NDB. Out of no reason the ILS and NDB Instruments ignore the existing ILS and NDB frequencies on my airport. This is what I have done so far:

1. frequencies for NDB and ILS are still correct -> checked
2. changed Name to CATIII and Range of ILS and NDB from 30Nm to 25Nm -> no effect allthough beeing reported that would help
3. deleted complete ILS and added new -> still not working
4. cleared and deleted NDB (all within ADEX) -> not working
5. checked the Raw Data Tool in ADEX -> no success, all seems to be good
6. I added an approach -> can this disturb NDB and ILS?

I was looking the past week to get it solved but with no luck. Maybe one of you pros can give me a hint how to solve that problem so I can use the NDB and ILS again. Many thanks in advance

Greets

Demon
 
Hi,

change the range of the ILS to 25-27nm and the NDB to 25nm and everything will be fine.

Maybe rework the pos. of the ILS Transmitters (LOC, GP, DME) and the Comms frequencies to the real and discard all the default NDBs/VORs, Routes and Waypoints which came from the default.

Regards
Hans
 
HansW said:
Hi,

change the range of the ILS to 25-27nm and the NDB to 25nm and everything will be fine.

Maybe rework the pos. of the ILS Transmitters (LOC, GP, DME) and the Comms frequencies to the real and discard all the default NDBs/VORs, Routes and Waypoints which came from the default.

Regards
Hans
Click to expand...

Hi Hans,

thanks for your reply. But as you can read in my first post, I already changed the frequencies to the original ones and shortened the range down to 25 Nm without any effect :o. How does the location of the ILS (LOC, DME, GP) influences them to work properly? :eek:

cheers,

Demon
 
Demon,

I took your posted ad2 file, opened it with ADE X v.1.47.16 and compiled to a bgl. Started FSX with this file active and, as you wrote, no ILS and no NDB!

Inside the ILS/NDB properties I found ranges = 10nm (ILS) and = 0 nm (!NDB). So I looked inside the German AIP and found that this transmitters have a range about 25nm. Changed this, compiled again, started FSX and with me everything is fine. Btw I used a native FSX SP2 for this check.

My 'small' letter advice has nothing to do with the working of the transmitters in FSX, it's only because the ADEX default positioning of ILS/DME/GP is not always correct. This is the case in Memmingen. Also the Comms freq. in your file are not that ones which are actually used in reality. Memmingen has a Ground, Tower and also ATIS freq. That's all I ment.

Hans
 
Hi Hans,

Sorry if I sounded ofensive. was not my intension. I am on ADEX 1.50 Pro. if I change the ranges and recompile nothing changes. I also dont see where I missed typing in the ranges. In either properties it seems everything is ok. I'll try again and report. Never the less thanks a lot for taking the time to share your knowladge with me.

Greets

Demon
 
Demon said:
Hi Hans,

Sorry if I sounded ofensive. was not my intension. I am on ADEX 1.50 Pro. if I change the ranges and recompile nothing changes. I also dont see where I missed typing in the ranges. In either properties it seems everything is ok. I'll try again and report. Never the less thanks a lot for taking the time to share your knowladge with me.

Greets

Demon
Click to expand...


Hi Demon

Like HansW said the Ranges are not set properly in your .ad2 file you attached





Also open the FSX Map Mode and make sure no ILS within 60 NM's is using the same freq.
 
Hi Jim,

I checked everything and I can't find the error. I also don't understand how it happend, that there was no range in the NDB. I have another ad2 file uploaded, maybe you could check that again?! the only instrument which is working is the DME on frq 117,2. The rest stays dead. I have no clue so far, why it is not working. There is no other ILS or NDB with the same frequence. Hope I get that solved somehow. Many thanks in advance.

cheers

Demon
 

Attachments

Demon

I set your ILS to 28NM
I set your VOR from a DME only to a VOR+DME transmitting 195 NM
I set your NDB to 75 NM

Your .ad2 file is attached
 
Last edited:
@Demon
your 2. ad2-file from post #10 contains unchanged ranges for the Navs at EDJA. So again, nothing to get there in FSX.

@Jim
your file works (with me), but these settings are far away from any reality.
ALD is a Terminal DME and ALG a Terminal Locator and the operational ranges are shown below.
 

Attachments

  • edja_navs.jpg
    edja_navs.jpg
    35.7 KB · Views: 521
HansW said:
@Demon
your 2. ad2-file from post #10 contains unchanged ranges for the Navs at EDJA. So again, nothing to get there in FSX.

@Jim
your file works (with me), but these settings are far away from any reality.
ALD is a Terminal DME and ALG a Terminal Locator and the operational ranges are shown below.
Click to expand...

Thanks Hans

Demon will have to reset they way he wants. I set the NAVAIDS so they would work but he can change them to their proper specs.
 
HansW said:
@Demon
your 2. ad2-file from post #10 contains unchanged ranges for the Navs at EDJA. So again, nothing to get there in FSX.
Click to expand...

First of all: Many Thanks, that you took the time to help me out!!! It's been appricitated a lot.

@HansW: I am wondering if my version of ADEX is working properly. I dont know why diferent ppl see diferent things in my ad2-file. You say my second file has no changes. But I did change things like the ranges. I also don't understand how Jim had the wrong ranges which I never typed in in the first file I've provided. That is all very strange to me. But how come FSX doesnt recognize the DME, NDB etc. the way I set it up? What can I do wrong with the NDB for example other than to add it, put in the correspnding frequence and the range?! Anything I need to take into account while creating Navaids?

@Jim: Many thanks again for taking the time. I am wondering if I change the settings, than it wont work again. You changed the DME to a VOR/DME which is originaly not correct. Memmingen has no VOR/DME. So I try to keep it right. But the DME wasnt the proble because that was the only thing working :) ILS and NDB din't work and still I dont know why. Changing ranges and frequencies had no effect at all. I am just trying the file you've provided and will see if it works now. If not than I am out of ideas what else could cause the malfunction.

Time passes............ok the ad2-file now works the way expected. I try to change it back to the original navaids step by step and see by trial and error where it goofs around.

I'll report shortly...

Thanks again to you guys for beeing such a great help! :)

Cheers

Demon
 
Problem Solved!

Hi all,

I think I've found the problem. I have my Units set to meters. When I now have to put in the range for the NDB a max of 100 meters is the limit. I have to go into the Raw tools to change the range into the correct value. 25 Nm are around 40233,6 Meters. I need to fill that value into the NDB range and it works. But in ADEX when I input 40233,6 meters it shrinks it down to 100. so it cant work that way. I will inform scruffyduck if that is normal or a bug...

Thanks guys for helping me!!!!!

Cheers

Demon
 
Hi Demon,

good to hear that you have a clou what might be wrong with your ADE X.

And yes, it seems to be a bug in ADE, if you choose 'Meters' for distance.

Look at my units! Working with this on a lot of files without any problems.

Btw. you choosed the 'dot' as decimal separator on a german OS?

Regards Hans
 

Attachments

  • ADEX_options_units.jpg
    ADEX_options_units.jpg
    22.5 KB · Views: 497
We did think to remove the option of using meters or feet for distance since Nm is the most likely to be used. I would certainly set distance to Nm and keep dimension (used for everything except large distances such as navaid range) at meters.

In the meantime it does appear to be a bug so I have added it to the list. The workaround is above.
 
Thank you all for this thread, you solved my problem.
Over the years a Mate & I have been building WW2 Airfields around Bedfordshire based on RAF Tempsford as the main & cheating a bit by giving some of them an ILS. One runway ILS wouldn't work so I changed the frequency & it still didn't work - Both frequencies belonged to another Airport nearby.
jvile gave me the clue.
 
You must log in or register to reply here.
Back
Top