EASYNAVS 2000 - FS2000 ILS,VOR and NDB EDITORS
----------------------------------------------------------------------------------
Version 3.0
---------
FILES
---------
EN2KILS.EXE ILS editor program (version 3.0)
EN2KVOR.EXE VOR editor program (version 3.0)
EN2KNDB.EXE NDB editor program (version 3.0)
EN2K30.TXT This file
----------------------------------------------
WHAT DOES EASYNAVS 2000
----------------------------------------------
EASYNAVS 2000 is a set of 3 Windows utilities that can:
1) Extracts ILS,VOR and NDB records from any FS2K BGL-format scenery file and writes them into a "standardized" binary database (with an ILS,VOR or NDB extension according to the program used) ; these files can be edited within the program
2) Creates a stand alone ILS, VOR or NDB FS2K Navaids BGL file from the corresponding database file
--------------------------------
ABOUT VERSION 3.0
--------------------------------
This new version is a major release of the EasyNavs 2000 utility since it takes into account all information provided in the recently released FS2000 Scenery SDK ; In addition, version 3.0 is now FS2000 "only" and will not handle anymore FS9x navaids BGL files. If you intend to modify navaids for FS95 or FS98, I will recommend you go on using Version 2.0 ; on the other hand, if you want to edit and modify FS2000 navaids, this new version is much more powerful and accurate and greatly improves database management ; EasyNavs 2000 Version 3.0 database files have now a safe and robust "binary" format but they cannot be edited with a text editor. Finally the navaids database editor has been redesigned in order to take into account all the new FS2K options ; a few bugs have been corrected and some new options have been added
-----------------------------------------------------------------------------------
NOTE ABOUT FS2000 ILS, VOR and NDB BGL structure
-----------------------------------------------------------------------------------
The structure of ILS, VOR and NDB BGL records have significantly changed in FS2K
1) In original FS2000 files, all VOR,ILS and NDB are grouped in bgl files named *vor.bgl, *ils.bgl and *ndb.bgl respectively ; these files are located in the \SCENEDB\EASTHEM\..\SCENERY, \SCENEDB\USGL\SCENERY and \SCENEDB\WESTHEM\..\SCENERY directories
2) Some (but not all) navaids bgl files are compressed ; EasyNavs 2000 is unable to extract navaids from such compressed files ; before editing navaids files, you will have to decompress them with the MicroSoft BGLZIP.EXE program.
To do that, you can use my ZBGL.EXE program (ZBGL.ZIP) or another similar utility. You can also use directly the MS BGLZIP.EXE program ; in this case, the safest procedure is to copy the BGLZIP.EXE program and all BGLs you want to decompress in a temporary folder, then open a DOS windows, go to it and type the following: BGLZIP -v -d -a bgl (beware of the spaces after each command)
After you create a new FS2K BGL file with any EasyNavs 2000 module, you can compress it back (although this is not mandatory) by using again ZBGL.EXE or BGLZIP.EXE (by typing the following: BGLZIP -v -c -a bgl ; the -v option is optional and will only tell you what has been done..)
3) Some new fields have appeared (especially distinct DME position for VOR and ILS) and the coding of some others (such as the range byte) is different.
If you replace any existing navaids bgl file, I STRONGLY RECOMMEND THAT YOU KEEP A COPY OF THE ORIGINAL FILE IN A SAFE PLACE
Just copy the 3 exe files EN2KILS.EXE, EN2KVOR.EXE and EN2KNDB.EXE in a new directory.
These programs are Visual Basic 4.0 32-bit programs and require that the appropriate runtime files have been installed
Also copy this file (EN2K30.TXT) in the program directory for future reference.
-------------------------------------------------
CONFIGURATION AND OPTIONS
-------------------------------------------------
Starting with version 2.0, EasyNavs 2000 will configure itself automatically ; it will keep track of the last directories used as well as of the most recently edited database files ; it will also locate your FS2000 directory in order to use the MAGDEC.BGL file in order to calculate magnetic variation
Each program has a specific ini configuration file
Version 3.0 add several "permanent" options that can be set in the menu:
- [Disable non critical messages and warnings]..self-explanatory
- [Always compute FS magnetic variation] (EN2KVOR only, see below for details)
- [Only use "standard" ranges] (see range fields for details)
- [Display Lat/Lon using seconds] will display all latitudes and longitudes either as degrees, minutes and decimal fraction of minute -or- as degrees, minutes, seconds and second decimal
--------------------------------------------------------------------------------------------------------------------------
EXTRACTION OF NAVAIDS FROM BGL FILES ( --------------------------------------------------------------------------------------------------------------------------
The option, depending on the module, will identify, show and extracts navaids in any selected FS2K BGL file which contains such kind of information. Successful extraction of navaids from a BGL file will allow you to create for future edition a database file with an .ILS, .VOR or .NDB extension
Database files are binary files in which all FS2K navaids informations are stored for any future edition
----------------------------------------
ILS INFORMATION FIELDS
----------------------------------------
ILS structure has changed in FS2K as compared with previous versions ; this version of the program will create ILS BGL files which are fully compatible with the FS2K BGL structure
1) Identifier
----------------
This is the string identifier of the ILS (minimum 1 and maximum 5 characters) ; usually ILS identifiers are 2 to 4 letters long ; all characters are accepted (including hyphens) although the Jeppesen convention only use letters (and no hyphen between the I and the ILS identifier)
2) Frequency
------------------
This is the frequency of the ILS localizer
In the real life all ILS frequencies are between 108.00 and 112.00 MHz on odd-tenths decimal values (ex: 108.10, 108.15, 111.90,) ; however, when extracting ILS data and creating a BGL file, the program will warn you if the ILS frequency is invalid but will accept any frequency as far as it is between 108.00 and 117.95 (inclusive) in order to take into account possible departures from this rule
3) Name
------------
This is the name of the ILS facility (1 to 24 characters maximum ; no character restriction)
4) Flags
--------
This hexadecimal string value describes the available functions of the ILS:
bit 0: 1 if DME is available ; 0 otherwise
bit 1: Always 0
bit 2: Always 0
bit 3: Always 0 in FS2K BGL's
bit 4: 1 if DME transmitter is at glide slope (no extra DME section needed) ; 0 if DME antenna has a specific position (see DME section)
bit 5: 1 if back course tracking is not available, 0 otherwise (although you can still set this option, it is disabled in FS2K after patch ; 7.01)
bit 6: 1 if glide slope is available (Full ILS), 0 for localizer only
bit 7: Always 1
5) Localizer antenna latitude
----------------------------------------
This is the latitude of the VHF localizer antenna (this antenna is typically on centerline 1000 ft beyond rwy end)
Latitude format is N(S)dd mm.x(xx) where dd are degrees, mm minutes and xxx, decimal fraction of minutes -or- N(S)dd mm ss.x if you use the [Display Lat/Lon using seconds] option ; this precision could be required due to the 24-bit internal coding of latitude in BGL files
6) Localizer antenna longitude
-------------------------------------------
Longitude of the VHF localizer antenna
Required format is E(W)ddd mm.x(xx) -or- E(W)ddd mm ss.x accordingly
7) Range
------------
This is the range of ILS reception in nautical miles (NM)
MS uses in its own BGL files a fixed "standard" range byte of &H10 (decimal 16) ; this value has a special meaning since it provides an ILS reception range of 26 to 27 NM ; when editing ILS you can choose to use this special value (called "standard range") or to define any custom range from 1 to 50 NM unless you enabled the [Only use "standard" FS2000 ILS range] option
A particularity of FS2K is that the ILS range seems to be internally limited to about 36-38 NM ; the use of any greater value will not increase the ILS reception range (this is the reason why I limited the maximum custom ILS range to 50 NM)
8) Localizer antenna elevation
------------------------------------------
This is the elevation of the localizer antenna above see level (AMSL) in feet (not meter); accepted values range from -9,999 to 99,999 ft (unrealistic ranges, I know..)
9) Localizer course
---------------------------
This is the TRUE approach course of the ILS, usually identical to the runway true heading
Format is ddd.x where ddd are degrees (000 to 360) and x the decimal fraction
Note that 0 and 360 will be interpreted the same
10) Glide slope
---------------------
This parameter is only significant if the glide slope flag is on (full ILS)
It sets the glide slope value of the ILS in degrees + decimal fraction of degrees
Accepted values range from 0.1 to 20.0° (the most usual value is 3.0°)
11) Glide slope transmitter latitude
-------------------------------------------------
In FS, this is the latitude of the point of intersection of the extended glide slope and runway surface (touchdown zone)
Same format as other latitudes fields and no meaning if the glide slope function is not available
12) Glide slope transmitter longitude
----------------------------------------------------
Idem ; See (6) and (11)
13) Glide slope transmitter elevation
---------------------------------------------------
Elevation (Feet AMSL) of the runway at the point of intersection of the extended glide slope and runway
14) Localizer beam width
------------------------------------
This is a new FS2K ILS parameter which sets the course width of the localizer, i.e. the lateral distance from full scale fly-left to full scale fly-right ; since runways are of varying lengths, the angular width of localizer beams will vary (a typical angular width is 2.5° either side of the localizer course centerline, but for different localizers this may vary from 1.5° to 10°) ; this parameter will set this angle ; lower values are to be used for long runways while higher values are to be used for small runways.
15) DME transmitter location
-----------------------------------------
FS2K gives you the new opportunity to describe the position of the DME antenna if it exists (ILSDME) ; the program will enable the DME transmitter latitude, longitude and elevation if the DME check box is checked ; for full ILS (i.e. with a glide slope definition), the "DME at glide slope" checkbox will also add a DME at the position of the glide slope antenna (i.e. at TDZ)
------------------------------------------
VOR INFORMATION FIELDS
------------------------------------------
Main VOR structure has not changed in FS2K as compared with previous versions ; however FS2K gives the additional option of adding a DME lat/long/alt field when the VOR and DME are not colocated (this of course is only true for VORDME and VORTAC navaids) ; FS2K also distinguish properly TACAN and DME only navaids which did not provide azimuth information (this was not the case with FS95 and FS98)
1) Identifier
----------------
This is the string identifier of the VOR (minimum 1 and maximum 5 characters) ; usually VOR identifiers are 1 to 3 letters long ; all characters are accepted
2) Frequency
------------------
This is the frequency of the VOR beacon
VORs operate within the 108.0 to 117.95 MHz frequency on even-tenths of MHz between 108.00 and 111.80 MHz and even and odd tenths of MHz from 112.00 to 117.95 MHz ; however, when extracting VOR data and creating a BGL file, the program will warn you if the VOR frequency is invalid but will accept any frequency as far as it is between 108.00 and 117.95 (inclusive) in order to take into account possible departures from this rule
3) Name
------------
This is the name of the VOR facility (1 to 24 characters maximum ; no character restriction)
4) Flags
-----------
This value describes the available functions of the VOR:
bit 0: 1 if DME is available ; 0 otherwise
bit 1: 1 for a TACAN (bit 0 must be set since TACAN always provide distance information)
bit 2: 1 if Voice transmission is made on radio beacon (no clear meaning in FS2K...)
bit 3: 0 if Nav signal available (VOR, VORDME and VORTAC) ; 0 for TACAN and DME only
bit 4: always 0
bit 5: always 0
bit 6: always 0
bit 7: always 0
5) VOR latitude
----------------------
This is the latitude of the VOR facility
As before, latitude format is N(S)dd mm.x(xx) where dd are degrees, mm minutes and xxx, decimal fraction of minutes -or- N(S)dd mm ss.x depending on the display option
6) VOR longitude
------------------------
Longitude of the VOR facility
Required format is E(W)ddd mm.x(xx) -or- E(W)ddd mm ss.x
7) Range
-------------
This is the range of VOR reception in nautical miles (NM)
The database editor allows the following standard service volumes:
- High altitude (or unrestricted) VOR class which is at least 130 NM
- Low altitude VOR class which range which is at least 40 NM
- Terminal VOR class which range which is at least 25 NM
MS uses in its own FS2K navaids BGL files 3 "special" values to describe these 3 classes, i.e, &H55 (decimal 85) for high altitude VORs, &H24 (decimal 36) for low altitude VORs and &H16 (decimal 22) for terminal VORs ; these values have a special meaning since the reception ranges are respectively 195, 60 and 37 NM, i.e. much higher than they should be ; you will have the possibility to use the special MS range values for high, low and terminal VORs by selecting the appropriate check box. Alternatively, you can define a "custom" VOR range from 1 to 255 NM unless you enabled the [Only use "standard" FS2000 VOR range] option
Note: the signification of the range byte has changed in FS2K as compared to FS9x ; in FS9x, this byte represents the range of VOR reception in 2048 meters units, while in FS2K this value seems to be directly coded in NM.
8) VOR elevation
------------------------
This is the elevation of the VOR beacon above see level (AMSL) in feet (not meter); accepted values range from -9999 to 99,999 ft
9) Magnetic variation at VOR position
-----------------------------------------------------
This is the value of the magnetic variation at the VOR navaid position
This value is important when azimuth information is provided (VOR, VORDME and VORTAC)
Format is E(W) dd.x were dd are degrees and x decimal fraction of degrees
Many values are not concordant with the FS "standard" values which depend only on the geographic location. The autoMV button will extract a "FS compliant" value from the MAGDEC.BGL file.
Note that if you enabled the [Always compute FS magnetic variation] option all magnetic variations will be automatically corrected when creating or saving any VOR database. I suggest you do that unless you have a good reason not to do so.
10) DME transmitter location
-----------------------------------------
FS2K also gives you the opportunity to describe the specific position of the DME transmitter of ILSDME and VORTAC when it is not located at the same place as the VOR beacon ; checking the [DME not colocated] box will enable the DME transmitter latitude, longitude and elevation fields where you can enter these additional informations.
------------------------------------------
NDB INFORMATION FIELDS
------------------------------------------
NDB structure has also changed in FS2K as regard NDB range which can now coded as a "class" byte rather than a NM distance
1) Identifier
----------------
This is the string identifier of the NDB (minimum 1 and maximum 5 characters) ; usually VOR identifiers are 1 to 3 letters/numbers long ; all characters are accepted
2) Frequency
-------------------
This is the frequency of the NDB transmitter
Usually NDB frequencies range between 200 and 1750 KHz (round numbers or .5 only)
However a few word values range between 100 and 200 KHz ; any value between 100 and 1750 will therefore be accepted by the program.
Format is [x]xxx.x with a decimal fraction of 0 or 5
3) Name
------------
This is the name of the NDB facility (0 to 24 characters maximum ; no character restriction)
A string is here accepted since some NDB do not have any name!
4) NDB latitude
----------------------
This is the latitude of the NDB facility
As before, latitude format is N(S)dd mm.x(xx) where dd are degrees, mm minutes and xxx, decimal fraction of minutes -or- N(S)dd mm ss.x depending on the Lat/Lng option
5) NDB longitude
------------------------
Longitude of the NDB facility
Required format is E(W)ddd mm.x(xx) -or- E(W)ddd mm ss.x
6) Range
-------------
This is a byte describing the NDB range class
In FS2K, 4 special ("magic") values are used for HH, H, HM and HL NDB's
- 00 for HH class (range 75 NM or more ; MS SDK: 75 NM)
- 01 for H class (range 50-74 NM ; MS SDK: 50 NM)
- 02 for HM class (range 25-49 NM ; MS SDK: 37.5 NM)
- 03 for HL class (locators ; range less than 25 NM ; MS SDK: 22.5 NM)
Other values (custom) directly set the NDB range (which is here, as before, coded in 2048 m units while it seems this is not the case anymore for VOR and ILS..but don't worry the program will ask you for NM only and make the conversion)
7) NDB elevation
------------------------
This is the elevation of the NDB transmitter above see level (AMSL) in feet (not meter); accepted values range from -9,999 to 99,999 ft
The command enables you to edit all navaids data from any database file (modify existing navaids, add or delete) ; the syntax of each parameter will be carefully checked by the editor ; a contextual help field is provided at the bottom of the edit form.
Although the program does not allow to create a new database from scratch, if you want to do so, I suggest that:
1) you rename any extracted database (e.g. mydb.vor)
2) then remove all navaids with the editor (you will not be able to remove the last one)
3) modify the first record as wanted and then add new records as needed
IMPORTANT: The EasyNavs 3.0 database structure has changed a lot and you will not be able to edit a database created with a previous version, even if the file extensions are the same..If you want to recover any previous work, I will suggest:
1) You first convert your data to a BGL using the previous version of EasyNavs 2000 (probably 2.0)
2) You extract your data and make a new database from this BGL using the 3.0 version
This is the only way...
------------------------------
MAKING BGL FILES
------------------------------
The function enables you to create a FS2000 BGL file from a database file. Lat_bands (latitude sections) will be optimized in accordance with navaids latitudes and ranges. The program will create a single BGL file including all data which are defined in the database. Note again that this BGL is for FS2000 ONLY and will probably not work with FS9x and crash the program..I'm not aware of all of the consequences of doing so..FS9x users must go on using the EasyNavs 2.0 version although it will not be anymore upgraded (but it's working rather fine..)
-------------------------------------------------------
RELEASE HISTORY AND CHANGES
-------------------------------------------------------
Version 1.5
----------------
1) Redefine VOR and ILS ranges according to the new FS2K convention and correctly set the range byte in both versions of the simulator
2) Ask for database save when directly closing the database edit form
3) Manage more friendly the cancel key in several situations
4) Add the possibility to enter latitudes and longitudes with 1 to 3 decimals for fraction of minutes
5) Set version number to 1.5 for all 3 exe files
6) Change in documentation
Version 2.0
----------------
1) Major rework of the program interface (especially as regard file selections)
2) Manual configuration removed and replaced by an autoconfiguration routine
3) Lower accepted NDB frequency decreased to 100 KHz
4) Maximum ILS range reduced to 50 NM, due to FS2K internal limitation
5) Set version number to 2.0 for all 3 exe files
6) Change in documentation
Version 3.0 (this version)
-----------------------------------
1) Complete change of the navaids editing interface
2) Complete change of the database structure
3) Implementation of all FS2K navaids settings according to the SDK
4) Several bugs corrected in common routines
5) Several new options
EN2KVOR.EXE, EN2KILS.EXE and EN2KNDB.EXE are provided "as is" without warranty of any kind. The author of the programs disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall the author be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if the author has been advised of the possibility of such damages. Because some states or jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, the foregoing limitation may not apply.
------------------------------------------------------------------------
COPYRIGHT, DISTRIBUTION AND LEGAL STUFF
------------------------------------------------------------------------
Copyright (C) Hervé Sors for the Prevair Group
EASYNAVS 2000 is released as FREEWARE
As freeware you are permitted to distribute it as a complete and unchanged package on any free media and on any mailbox or network that does not have a per-file download charge.
If you like to include it to your own program or package:
1) ask me for my prior permission..I will give it!
2) include all program files and documentation (together 4 files)
After reading this text file (EN2K30.TXT), you are aware that whatever the way this program is used, I won't be liable for any damage that may be caused by it and any consequence of using it (see Disclaimer section)
-------------
AUTHOR
-------------
Hervé Sors
hsors@wanadoo.fr
The Prevair group (http://www.Prevair.com)
Please feel free to e-mail me any criticism or suggestion
October 2000
