735
edits
FG1000: Difference between revisions
Jump to navigation
Jump to search
Formatting
(Formatting) |
|||
| Line 55: | Line 55: | ||
== Aircraft Installation == | == Aircraft Installation == | ||
Adding the FG1000 to an aircraft is intended to be fairly straightforward. | |||
=== Add the GDU to the cockpit === | |||
Place one or more of the display (GDU) units in your model. The XML files | |||
are in GDU104X directory and are named <model>.<device-number>.xml, e.g. | are in GDU104X directory and are named <model>.<device-number>.xml, e.g. | ||
| Line 64: | Line 68: | ||
though you can mix and match the GDU models. | though you can mix and match the GDU models. | ||
=== Load the Interfaces to provide data === | |||
This is used to provide airdata, navdata, NAV/COM settings, engine information | |||
to the GDUs. There is a | |||
generic interface (GenericInterfaceController) that uses the standard FG route | generic interface (GenericInterfaceController) that uses the standard FG route | ||
manager, GPS, navigation data and NAV/COM settings, and engine data for a single | manager, GPS, navigation data and NAV/COM settings, and engine data for a single | ||
| Line 71: | Line 78: | ||
You need to load it as follows: | You need to load it as follows: | ||
<syntaxhighlight lang="nasal"> | |||
var nasal_dir = getprop("/sim/fg-root") ~ "/Aircraft/Instruments-3d/FG1000/Nasal/"; | var nasal_dir = getprop("/sim/fg-root") ~ "/Aircraft/Instruments-3d/FG1000/Nasal/"; | ||
var interfaceController = fg1000.GenericInterfaceController.new(); | var interfaceController = fg1000.GenericInterfaceController.new(); | ||
interfaceController.start(); | interfaceController.start(); | ||
</syntaxhighlight> | |||
You may want to create your own version depending on what properties you are | You may want to create your own version depending on what properties you are | ||
using for the NAV/COM, and your engine configuration. | using for the NAV/COM, and your engine configuration. | ||
Note that you should only start the interface after you've | Note that you should only start the interface after you've started the FG1000 | ||
as they will publish information at start of day that the displays need. | as they will publish information at start of day that the displays need. | ||
=== Create an EIS Display === | |||
This is the Engine Information System and displays on the left side of the MFD. | |||
There is a generic EIS provided | |||
(see FG1000/Nasal/EIS, and FG1000/MFDPages/EIS.svg) that is intended to match | (see FG1000/Nasal/EIS, and FG1000/MFDPages/EIS.svg) that is intended to match | ||
a Cessna 172. If you need something different, you should create your own | a Cessna 172. If you need something different, you should create your own | ||
| Line 89: | Line 102: | ||
Interfaces/GenericEISPublisher.nas for a reference implementation. | Interfaces/GenericEISPublisher.nas for a reference implementation. | ||
=== Load and start the FG1000 system === | |||
See FG1000/Nasal/FG1000.nas for full details, | |||
including how to pass in the EIS. A simple FG1000 using the generic EIS, and | including how to pass in the EIS. A simple FG1000 using the generic EIS, and | ||
displaying PFD on device-number 1 and an MFD on device-number 2 is as follows: | displaying PFD on device-number 1 and an MFD on device-number 2 is as follows: | ||
<syntaxhighlight lang="nasal"> | |||
var nasal_dir = getprop("/sim/fg-root") ~ "/Aircraft/Instruments-3d/FG1000/Nasal/"; | var nasal_dir = getprop("/sim/fg-root") ~ "/Aircraft/Instruments-3d/FG1000/Nasal/"; | ||
io.load_nasal(nasal_dir ~ 'FG1000.nas', "fg1000"); | io.load_nasal(nasal_dir ~ 'FG1000.nas', "fg1000"); | ||
| Line 109: | Line 125: | ||
# Display a GUI version of device 1 at 50% scale. | # Display a GUI version of device 1 at 50% scale. | ||
#fg1000system.displayGUI(1, 0.5); | #fg1000system.displayGUI(1, 0.5); | ||
</syntaxhighlight> | |||
== Page Status == | == Page Status == | ||