Installation manual

Avidyne | DFC90, 100 FAQs (Last updated: 26 June 2012)
1
DFC90 and DFC100 FAQs
Updated 26 June 2012
General Questions
(DFC90, 100) What are the main differences between the DFC90 and DFC100?
There are two functional differences between and the autopilots and two architectural
differences. Functionally, the DFC100 supports the R9 Vectors mode and it adds a
VNAV capability. Architecturally, the DFC90 autopilot takes its input from the Avidyne
or Aspen PFD and the Garmin 430s (or GPS/Nav/Coms connected to the Aspen PFD)
while the DFC100 is driven by the IFD and the Avidyne FMS 400/900w system, and the
DFC100 system communicates to the rest of the R9 system via the Byteflight digital
databus while the DFC90 does not. (updated 17 April 2012)
(DFC90, 100) What are the main features of these autopilots? First and foremost,
since it is taking advantage of the on-board PFD digital ADAHRS, they are able to
provide a much more precise operation (e.g. no overshoots, no wandering, no divergent
behavior inside the FAF, etc). Secondly, they add some very specific safety features such
as Straight and Level and Envelope Protection. Thirdly, they add new modes such as
IAS (Indicated Air Speed) mode. Finally, the Flight Director becomes much easier to use
and follow.
(DFC90, 100) How does IAS mode work? Just like VS mode, IAS mode can be used to
follow a commanded indicated airspeed as set by a new IAS bug or it can be used to
perform an altitude capture at a specified airspeed. Once set via the IAS bug and
engaged, the autopilot will adjust the aircraft flight path angle as required to track the
commanded IAS. The system will not “descend to climb” or “climb to descend”. In
other words, if you were currently flying at 120 KIAS and commanded a 1000’ climb at
140 KIAS, the aircraft will not first descend to pick up airspeed before climbing to the
new altitude target. Likewise, if you were currently flying at 120 KIAS and commanded
a 1000’ descent at 90 KIAS, the aircraft will not first climb to bleed off airspeed before
descending to the new altitude target at 90 KIAS. In both cases, since the autopilot
determines that it cannot comply with the contradictory input requests, it was hold current
state until the pilot takes an action such as a power change or a target speed change.
(DFC90, 100) Why did you retain some of the same user interface as the S-TEC? This
was purposely done to minimize the amount of re-training required for the S-TEC user
community since that represented the vast majority of our early customers. Habit
patterns are a powerful force and we wanted to leave that as intact as feasible. (updated
24 July 2011)
(DFC90, 100) Where can I learn more about the “button-ology” of the DFC
autopilots? These are fully addressed in the autopilot user’s manuals. The link for the
DFC90 Pilot Guide is here and the link for the DFC100 Pilot Guide is here.

Summary of content (17 pages)