Bitchin' Betty

Jake ...

Edited by oskrypuch - 08 Jun 2013 at 10:49am

Now, now.

Edited by oskrypuch - 09 Jun 2013 at 10:38pm

It's part of the baseline.

You will need an audio panel that has some unswitched/unmuted input lines but if you do, you'll be all set. 

One asterisk is associated with that however.  For many installs, there is already a wire connecting the back of the existing 530 tray to the airplane audio panel - in those cases, the system is 100% plug and play.  For those installs that don't have an existing wire connecting the audio out pin of the tray to one of the unswitched/unmuted input lines of the audio panel, it will need to be added in order to hear the various .wav files and TOD chime.  

Yes, the units are told at time of install how many units are installed in the airplane and what position each is in.  They use that information to self-suppress when appropriate.

We agree that it's a neat feature to have some setup/user option influence on the gender/language/phraseology for the various alerts.  We didn't include that capability in the initial release but it is a candidate for possible future adds.

Yup.

Maybe.  Do you have any aural alerting requests?

We'll add that to the stable of stored .wav files.  Not sure when or if we'll actually start using it but we'll have Rene do that extra recording.

One of the aurals we recorded for potential future use is "Minimums" and one of the candidates for future feature adds includes an ability for a user to create a set of personal minimums like you suggest.

We're having a difficult time trying to find a mechanism for a user to create their own set of aurals and their own associated triggers.  That all has to be housed in certified flight code and that's the current rub.

For now, its a deferred feature idea that we'll hopefully come back to at a later date.

Agreed. "Check Gear" is one of those .wav files we've already included in that group of potential future features. To be clear, we're including that file in initial release but we are not triggering it in the initial release.

Are you going to have one that says "You are not allowed to disassemble this software"?

And maybe startup messages (which could be configured off) such as "GPS is active" and "Database is current"?

It really doesn't matter the state of the gear, you still need to make the check.

The more generic "landing checklist" callout, covers it nicely. You would complete (or confirm you have completed) the checklist, all hanging, stable approach, etc.

* Orest

Steve, I'm going to be honest with you.  When you say "a more generic trigger that didn't involve wiring" kinda scares me.  Please don't give me an aural that says check landing gear on every approach because I wont hear it after the third approach.  You are going to have to know the state of the gear. Now with that being said, I would love to have protection from me being an idiot.  That's the one thing I'm afraid I'm going to do someday, forget to put down the gear.

Edited by tony - 14 Jun 2013 at 10:41pm

She should sing "Daisy Bell", better known as "Bicycle Built for Two".  (If you don't know why, look up John Larry Kelly Jr in Wikipedia.)  If she can't sing, just recite the first line.

Edited by Paul - 14 Jun 2013 at 11:16pm

But Daisy would be the perfect Easter egg in the simulator (under an #ifdef so it isn't in the actual product).

Will the GPS be able to say informational messages such as "Minimum decision altitude" or "Going missed" or "disconnecting autopilot"?  Or does it not have enough information?

The IFD540 comes with a full Caution Alerting System (CAS) which provides a message (Red Warning, Yellow Caution, or Cyan Advisory) on those kinds of system conditions.

Isn't RAIM obsolete with the incorporation of WAAS? 

all the more reason to have a WAAS inop aural.

Is an Aspen link available, i.e. altitude bust when the Aspen unit starts to flash?