Ivan-Pekar wrote in Wed Nov 14, 2018 6:10 pm:Thank you very much, WoodSTokk!
But what about the ILS Frequency that I input into F12 to make an ILS landing?
For that, you need all datas and write it in a nav.dat file.
In your directory 'TerraLocal/NavData' create a new directory named 'nav'
Inside this directory you can create files with the extation '.dat' (like 'USMM.dat')
This file is similarly to the 'apt/<ICAO>.dat' file, but the lines have another meaning.
I havn't found any article in the wiki, but i have a quick look in the default.
In general the file have this structure:
- Code: Select all
810 this is the header line and must be the first line
… [one or more records]
99
A record looks mostly like this:
<type> <lat> <lon> <elev> <frequency> <range> <direction> <ident> <airport> <rwy> <description>
I think the most of it is self explaining.
But here some notes:
'lat' and 'lon' is in decimal degrees and give the exact position of the antennas
'elev' is in feet
'range' is in nautic miles
But not all types have all entries.
Here is a list, sorted by 'type', what i found out until now:
Type 2 = NDB (Non Directional Beacon)
2 <lat> <lon> <elev> <frequency> <range> 0.0 <ident> <description>
A NDB is omnidirectional, therefor the 'direction' is allways 0.0
'frequency' is in kHz
Type 3 = VOR ( Very-High-Frequency Omnidirectional Range)
3 <lat> <lon> <elev> <frequency> <range> <direction> <ident> <description>
'frequency' is in MHz plus 2 digits. This means the freq 117.35 will be written as 11735
'direction' is the declination. This means the magnetic deflection from the geografic north
Type 4 = LOC (Localizer) for ILS Cat I, II, III
Type 5 = LOC (Localizer)
4 <lat> <lon> <elev> <frequency> <range> <direction> <ident> <airport> <rwy> <description>
'frequency' is in MHz plus 2 digits (like VOR)
'direction' is the exact direction of the beam (take the declination into account)
'airport' is the ICAO code of the airport
'rwy' is the runway designation (like 05 or 28L)
Type 6 = GS (Glide Sloop)
6 <lat> <lon> <elev> <frequency> <range> <direction> <ident> <airport> <rwy> <description>
all the same as 4 and 5 (LOC) with one exception:
'direction' describe the vertical and lateral angle
As example, if the beam goes to 123.45 degrees lateral and the glide sloop is on 3.2 degrees, 'direction' will be writtes as 320123.450
So, the first 3 digits are the glide sloop angle (320 is 3.20 deg), and there after comes the beam lateral direction
Type 7 = OM (Outher Marker)
Type 8 = MM (Middle Marker)
Type 9 = IM (Inner Marker)
7 <lat> <lon> <elev> 0 0 <direction> ---- <airport> <rwy> <description>
all 3 makers dont have a frequency and range, therefor this values are allways 0
also the 'ident' is allways '----', at least i dont have found any marker with ident
Type 12 = DME (Distance Measurement Equipment)
Type 13 = DME (Distance Measurement Equipment)
If the DME is part of a ILS
12 <lat> <lon> <elev> <frequency> <range> <displacement> <ident> <airport> <rwy> <description>
otherwise 'airport' and 'rwy' is omitted
12 <lat> <lon> <elev> <frequency> <range> <displacement> <ident> <description>
The most ILS have also a DME, but the antenna is mostly located at the GS antenna (beside the TZ = touchdown zone)
But a DME for ILS should give the pilot the distance to the runway threshold.
Therefor, the DME has a 'displacement' setting (insteed of 'direction').
'displacement' is in nautic miles and is non zero if the DME is part of a ILS and not direct beside the runway threshold.
Otherwise it is allways 0.0
I have not found any difference between 12 and 13.
Types 1, 5, 10 and 11 is unknown for me. I havn't found it in the default nav.dat.
Here is a example (i have filtered the default file for 'LOWS', this is Salzburg in Austria):
- Code: Select all
4 47.77909200 013.01294700 1411 10990 18 157.534 OES LOWS 16 ILS-cat-III
6 47.80089400 013.00110600 1399 10990 10 300157.085 OES LOWS 16 GS
7 47.87933300 012.94986400 1411 0 0 157.085 ---- LOWS 16 OM
12 47.80094200 013.00129400 1446 10990 18 0.200 OES LOWS 16 DME-ILS