Archived from groups: alt.games.microsoft.flight-sim (
More info?)
On Sun, 13 Mar 2005 09:56:59 -0500, pr wrote:
> OK, Bill, you have pulled me back in. Since upgrading to Dialog as my
> newsreader I haven't been using KFs.
>
> First off, nice job on the gauge. I am in love with JPI Engine Monitors
> for light piston aircraft engine monitoring ever since the EDM-800 I fly
> behind saved me during my failed mag incident last year.
>
> One question about your EDM-700: Normally, when stepping to the turbo-
> inlet temperature, both TIT and fuel flow values are shown together.
> However, in your gauge, TIT is shown with cylinder head temperature.
That is correct. I chose not to model all of the actual features of the
EDM700 (such as logging of data) since it would be totally useless as the
sim's values will never change... without extensive "engine wear
programming" at least. Likewise the "trend analysis" would be equally
valueless, since the data inputs are invariant.
Aside from which, unlike the EHSI, the humble EDM700 isn't a "primary
instrument" in most folks minds.
Likewise, since the sim only supplies one CHT variable, I had to "fudge"
the individual cylinder's reported temps with fixed scalars. Even the
"Lean Find" was vastly simplified in order to keep the program code
reasonably short...
Even so, as most folks are going to discover, proper leaning is vital to
flying the A36 efficiently and effectively. Having a precision instrument
to aid the process can only be a boon.
> I realize that fuel monitoring is an option with the EDM-700, whereas it is
> included in the price of the EDM-800, but I would imagine that the owner of
> the real A36 chose this option, given her other nice avionics modifications
> to the aircraft.
Oddly enough, Julie did not choose the fuel monitoring option...
> Secondly, a question about the A36's HSI (I have no idea who programmed
> this gauge, just tossing this out): In my Bonanza, the CDI source of the
> HSI is controlled by the Garmin GNS430 CDI selector switch. However, in
> this aircraft, it seems that the only way to control the CDI source is by
> clicking on the NAV text of the HSI itself? The CDI source selector on the
> GPS has no affect on the CDI.
Ike Slack (formerly of Coyote Avionics) programmed the Sandel 3308.
Dreamfleet chose his over mine simply because he modeled the system more
authentically than I did. I chose to model it as I would have designed
one, and simplified it for the "average simmer" rather than attempting to
replicate the actual EHSI.
On the configuration page there are a set of options which you can choose
to set up the RXP430, one of which is that the RXP will drive the EHSI.
Make certain that is enabled.
AFAIK, the 3308's CDI should respond to any input source providing that GPS
is selected as the primary source for the 3308. With the 3308 set to GPS,
switching the 430 from GPS to VLOC will allow the CDI to be driven by
either the 430's GPS or NAV1 LOC/VOR radios.
Switching the 3308 will allow the CDI to be driven by a standby source,
such as another NAV radio or NAV2 radio.
Bill
If they have
Facebook
Twitter
Instagram