As of version 1.0.6.5 of the TFDi Design 717, company routes were supported via an XML file stored in the aircraft directory. These files will be located here:
{Simulator}\SimObjects\Airplanes\TFDi_Design_717\Documents\Company Routes\
This document provides a description of how the XML format is organized.
The company route read and produced by the MCDU is an XML file. The root is called Version 1. This will not change. The root is named this way so that in the event of changes to the format in the future, a different version root can be used to differentiate formats, therefore maintaining backward compatibility.
Within this route are 5 elements: Departure, Arrival, Cost Index, Cruise Level, and Legs. Departure and Arrival elements are always required, as the MCDU needs to know which airport the aircraft is departing from and arriving. However, the Cost Index and Cruise Level elements are not always required.
The last element is the Legs. Within this element are an arbitrary number of sub-elements that represent each waypoint, navaid, airway, and or airport/pilot defined waypoint entered in the MCDU. This document describes each type of sub-element that can be read by the MCDU.
There is an option to export the current flight plan as a company route via the MAINT page in the MCDU.
This sub-element represents a waypoint. The attributes required are:
Example:
<Leg Type="Waypoint" Ident="ATHOS" Latitude="42.2471" Longitude="-73.8121"/>
This sub-element represents a navaid. The attributes required are:
Example:
<Leg Type="Navaid" Ident="CMK" Latitude="41.2801" Longitude="-73.5813" />
This sub-element represents an airway leg/path. The attributes that are required are:
What the airway will be displayed on the MCDU
Example:
<Leg Type="AirwayLeg" Level="H" Wpt2Ident="CAE" Wpt2Latitude="33.8573" Wpt2Longitude="-81.0539" Airway="J75" />
This sub-element represents an airport. The attributes required are:
Example:
<Leg Type="Airport" ICAO="KIAD" Latitude="38.9474" Longitude="-77.4599"/>
This sub-element represents a waypoint as defined by the pilot. The attributes required are:
The PBDPlace, PBDDist, and PBDBearing sub-elements may be left out if the pilot defined waypoint is not a PBD waypoint.
Example:
<Leg Type="PilotDefinedWaypoint" Ident="PBD01" Latitude="33.7197" Longitude="-84.4191" PBDPlace="KATL" PBDDist="5" PBDBearing="5" />
This sub-element represents a route discontinuity displayed on the MCDU F-PLAN page. The attributes required are:
Example:
<Leg Type="Discontinuity" />
<?xml version="1.0" encoding="UTF-8"?>
<Version1>
<Departure>KALB</Departure>
<Arrival>KBWI</Arrival>
<CostIndex>24</CostIndex>
<CruiseLevel>28000</CruiseLevel>
<Legs>
<Leg Type="Waypoint" Ident="ATHOS" Latitude="42.2471" Longitude="-73.8121"/>
<Leg Type="Navaid" Ident="CMK" Latitude="41.2801" Longitude="-73.5813" />
<Leg Type="AirwayLeg" Level="H" Wpt2Ident="CAE" Wpt2Latitude="33.8573" Wpt2Longitude="-81.0539" Airway="J75" />
<Leg Type="Airport" ICAO="KIAD" Latitude="38.9474" Longitude="-77.4599"/>
<Leg Type="PilotDefinedWaypoint" Ident="PBD01" Elevation="0" Latitude="33.7197" Longitude="-84.4191" PBDPlace="KATL" PBDDist="5" PBDBearing="5" />
<Leg Type="Discontinuity" />
</Legs>
</Version1>