Radio Navigation - MOARdV/AvionicsSystems GitHub Wiki

Avionics Systems supports emulating radio navigation using VOR, NDB, DME, and ILS.

Using Radio Navigation

TODO: More details. But not a full-on tutorial on how to navigate using radio navigation systems. Just how to use navaids in MAS.

MAS assumes that all radio navigation beacon frequencies are in MHz for simplification of the design.

MAS also assumes that there is an infinite number of radio units on board. The IVA maker could set any arbitrary radio to any frequency - if the radio navigation prop allows the user to set "radio 7", MAS will set radio 7.

Radio Navigation Beacons

MAS includes a number of radio navigation beacons in GameData/MOARdV/AvionicsSystems/MAS-NavAid.cfg by default. These beacons are all defined in the Jebbesen Guide by alexustas.

Additional beacons may be defined in additional config files using the format described below.

Configuring Beacons

All beacons must be placed in a config file under a top-level node of MAS_NAVAID. Each beacon is in its own NAVAID config node, as shown below. Unless otherwise noted, all nodes are required. MAS will detect multiple config files that define MAS_NAVAID, so navigation beacon creators may create their own mod-specific MAS_NAVAID config file. There is no need to add NAVAIDs to an existing config file.

MAS_NAVAID
{
  NAVAID
  {
    name = CENTER
    id = KST
    celestialName = Kerbin
    frequency = 113.30
    latitude = -0.050277777
    longitude = -74.5175
    altitude = 160
    type = VOR DME
    //maximumRangeLocalizer = 30000
    //maximumRangeGlidePath = 8000
    //approachHeadingILS = 90
    //localizerSectorILS= 17.5
    //glidePathSectorILS= 1.5
    //glidePathDefault = 3.0
  }
}

• name: The name of the navaid station.
• id: A three letter code used to identify the station. It is also used to generate a Morse code audio signal.
• celestialName: The name of the body where the station is placed. Yes, you can put radio nav beacons on the Mun if you really want to.
• frequency: The frequency of the station. Nav beacons are selected by setting a nav radio to a specified frequency.
• latitude, longitude: The latitude and longitude of the beacon, in decimal degrees (eg, 10* 30'N is 10.5).
• altitude: The ASL (or Altitude above Datum for oceanless worlds) of the transmitter.
• type: The type of the transmitter. The type must be exactly one of the entries under 'Supported Beacon Types'.
• maximumRangeLocalizer: Required only for ILS and ILS DME sites, otherwise ignored. The maximum range of the ILS localizer signal, in meters.
• maximumRangeGlidePath: Required only for ILS and ILS DME sites, otherwise ignored. The maximum range of the ILS glide path signal, in meters.
• approachHeadingILS: Required only for ILS and ILS DME sites, otherwise ignored. The heading for which the ILS system provides guidance.
• localizerSectorILS: Required only for ILS and ILS DME sites, otherwise ignored. The maximum horizontal deflection from the approach heading where the ILS signal is detected.
• glidePathSectorILS: Required only for ILS and ILS DME sites, otherwise ignored. The maximum vertical deflection from the glide slope where the ILS signal is detected.
• glidePathDefault: Required only for ILS and ILS DME sites, otherwise ignored. The default recommended glide path for the ILS beacon. Since KSP allows a very wide variety of space planes, not all craft may be able to fly the recommended glide path.

Supported Beacon Types

• NDB - Non-directional beacon.
• NDB DME - Non-directional beacon with co-located Distance Measuring Equipment.
• VOR - VHF Omni-directional Range beacon.
• VOR DME- VHF Omni-directional Range beacon with co-located Distance Measuring Equipment.
• ILS - Instrument Landing System.
• ILS DME - Instrument Landing System with co-located Distance Measuring Equipment.