Integration Overview

Introduction

To fully integrate the Epic2 avionics package, both panel.xml options must be configured, and a plugin must be setup to allow for Engine Indications to be displayed and other options to be taken advantage of.

Model Behaviours

For information on setting up the model behaviours required, see Epic2 Model Behaviours

Panel Configuration

For information on the basics of the panel.xml configuration, see Panel.xml Basics For documentation on panel.xml tags, see Panel.xml Tag Documentation

For documentation checklists, see Electronic Checklists

Setting Up Logic For MFD Swapping

Inorder for MFD swapping to function properly, the <Logic> tag must be defined as part of the panel.xml, and the <MFD_UPPER> and <MFD_LOWER> tags must point to the instrument names as displayed in the Coherent GT debugger. The <Handler> tag must also be defined as it is below and should not be changed.

Example:

  <Logic>
		<Handler>Systems_Epic2</Handler>
		<MFD_UPPER>Epic2UpperMfd_2</MFD_UPPER>
		<MFD_LOWER>Epic2LowerMfd_3</MFD_LOWER>
	</Logic>

Panel.cfg Configuration

We recommend that the following panel.cfg configuration is used to ensure there are no issues:

[VCockpit01]
 size_mm            = 1024,768
 pixel_size         = 1024,768
 texture            = [PFD_MATERIAL_HERE]
 background_color   = 42,42,40
 htmlgauge00        = NavSystems/Epic2v2/PFD/Epic2Pfd.html?Index=1, 0,0,1024,768

[VCockpit02]
 size_mm            = 1024,768
 pixel_size         = 1024,768
 texture            = [UPPER_MFD_MATERIAL_HERE]
 background_color   = 42,42,40
 htmlgauge00        = NavSystems/Epic2v2/MFD/UpperMFD/Epic2UpperMfd.html?Index=2, 0,0,1024,768

[VCockpit03]
 size_mm            = 1024,768
 pixel_size         = 1024,768
 texture            = [LOWER_MFD_MATERIAL_HERE]
 background_color   = 42,42,40
 htmlgauge00        = NavSystems/Epic2v2/MFD/LowerMFD/Epic2LowerMfd.html?Index=3, 0,0,1024,768

[VCockpit04]
 size_mm            = 1024,768
 pixel_size         = 1024,768
 texture            = [PFD_2_MATERIAL_HERE]
 background_color   = 42,42,40
 htmlgauge00        = NavSystems/Epic2v2/PFD/Epic2Pfd.html?Index=4, 0,0,1024,768

[VCockpit05]
 size_mm            = 800,600
 pixel_size         = 800,600
 texture            = [TSC_MATERIAL_HERE]
 htmlgauge00        = NavSystems/Epic2v2/Tsc/Epic2Tsc.html, 0, 0, 800 ,600

The exact indexes of the VCockpit items do not matter, but the order of these configuration items should be preserved.

Aircraft Systems Configuration

Aircraft systems must be configured in a specific manner to ensure that the radios work correctly. If amber dashes are displayed persistently in any of the radio slots on the PFD, one or more of the DMEs dont work, or if the frequency adjustment knob on the PFD controller directly adjusts the active frequency instead of the standby frequency, then the configuration of the radios or their electrics is incorrect.

In the systems.cfg file, as part of the [RADIO] section, there must be:

• 2 COM systems
• 4 NAV systems
• 1 ADF system

The first 2 of each of these should have the standby frequency enabled, and the glideslope should be enabled for NAV radios. NAV 1 and 2 are used for VOR/LOC 1 and 2, while NAV 3 and 4 are used for DME 1 and 2. Currently, we only support dual DME installations while the real unit supports single DME installs.

Example:

[RADIOS]
Audio.1 = 1
Audio.2 = 1
Com.1 = 1,1
Com.2 = 1,1
Nav.1 = 1,1,1
Nav.2 = 1,1,1
Nav.3 = 1,0,0
Nav.4 = 1,0,0
Adf.1 = 1,1
Transponder.1 = 1
Marker.1 = 1

Each of these must also have a corresponding electrical circuit associated, such as:

[ELECTRICAL]
circuit.1 = Type:CIRCUIT_NAV:1#Connections:bus.1#Power:4,5,20#Name:NAV1 ; VOR/LOC 1
circuit.2 = Type:CIRCUIT_NAV:2#Connections:bus.1#Power:4,5,20#Name:NAV1 ; VOR/LOC 2
circuit.3 = Type:CIRCUIT_NAV:3#Connections:bus.1#Power:4,5,20#Name:NAV1 ; DME 1
circuit.4 = Type:CIRCUIT_NAV:4#Connections:bus.1#Power:4,5,20#Name:NAV1 ; DME 2
circuit.5 = Type:CIRCUIT_COM:1#Connections:bus.1#Power:4,5,20#Name:COM1 ; COM 1
circuit.6 = Type:CIRCUIT_COM:2#Connections:bus.1#Power:4,5,20#Name:COM1 ; COM 2
circuit.7 = Type:CIRCUIT_AUDIO:1#Connections:bus.1#Power:12,15,20#Name:Audio1 ; Audio1
circuit.8 = Type:CIRCUIT_AUDIO:2#Connections:bus.1#Power:12,15,20#Name:Audio2 ; Audio2
circuit.9 = Type:CIRCUIT_ADF_DME:1#Connections:bus.1#Power:32,35,20#Name:ADF1 ; ADF 1
circuit.10 = Type:CIRCUIT_XPNDR:1#Connections:bus.1#Power:20,25,20#Name:XPNDR1 ; Transponder 1
circuit.11 = Type:CIRCUIT_MARKER_BEACON:1#Connections:bus.1#Power:20,25,20#Name:Marker1 ; Marker Beacon 1

Other Airframe Configuration Information

The Epic2 includes a readonly lvar L:WT_Epic2_AP_Abnormal_Disengage which is set when the AP disengages due to an abnormal condition, such as entering a stall. When this is true, the autopilot disconnect cavalry chime will be played repeatedly until the AP quick disconnect (the AUTOPILOT_OFF key event) is pressed to acknowledge the disconnect.

For information on the autopilot control lvars and the control html events, review the model behaviour files included as part of the Epic2 package.

The epic2 additionally sets the following lvars:

Variable	Readonly	Description
L:WT_Epic2_GPWS_Steep_Approach_Mode	True	Is set when the steep approach mode has been enabled on the TSC or MFD. This should be used to set up a CAS message.
L:WT_Epic2_Fuel_Burned	True	The quantity of fuel burned according to the Epic2 fuel totalizer, in gallons.
L:WT_Epic2_Fuel_Remaining	True	The quantity of fuel remaining according to the Epic2 fuel totalizer, in gallons.

Aircraft Plugin Configuration

To properly take advantage of the Epic2, you must create aircraft plugins. These plugins are required for:

• rendering the PFD engine indication display
• rendering the aircraft system summary synoptics on the right side of the lower MFD
• overriding the default FADEC with an aircraft specific fadec
• providing aircraft climb information for top of climb predictions
• overriding default autothrottle options

For more information on aircraft plugins, see the plugin basics and other related information