Jump to content

Recommended Posts

Posted

Has anyone flying a G3X Touch with v9.17 software experienced the "minimums" audio alert not being there?

A friend recently installed a G3X on a Bonanza and everything checks out except for the "minimums" alert. Garmin is telling him it is a problem with the v9.17 audio file. He asked if I could verify if I was getting the alert with v9.17 but my airplane is down for other maintenance so I can't check it for him for another week or so.

Thanks for the help!

Cheers,
Junkman

Posted
38 minutes ago, Rick Junkin said:

Has anyone flying a G3X Touch with v9.17 software experienced the "minimums" audio alert not being there?

A friend recently installed a G3X on a Bonanza and everything checks out except for the "minimums" alert. Garmin is telling him it is a problem with the v9.17 audio file. He asked if I could verify if I was getting the alert with v9.17 but my airplane is down for other maintenance so I can't check it for him for another week or so.

Thanks for the help!

Cheers,
Junkman

Been a minute since I’ve touched a g3x, but did you go into config mode and check the sound settings?

And then if I recall correctly there are some other settings in aircraft config for these as well.

They might just be turned off.

  • Rick Junkin changed the title to G3X Touch v9.17 missing "minimums" audio alert?
Posted
6 minutes ago, dzeleski said:

My bad, the question is about a certified G3X Touch installation. I updated the title to reflect. The document you referenced is for the original experimental G3X.

He's an independent avionics installer located in St Louis and did some earlier panel work for me when I lived there. He's been communicating with Garmin and I have to assume they've covered all of the basic config stuff, but I'll ask him. Garmin told him it's a problem with the audio file. He's just looking for another data point to verify he's not the only one.

Cheers,
Rick

Posted (edited)
6 minutes ago, Rick Junkin said:

My bad, the question is about a certified G3X Touch installation. I updated the title to reflect. The document you referenced is for the original experimental G3X.

He's an independent avionics installer located in St Louis and did some earlier panel work for me when I lived there. He's been communicating with Garmin and I have to assume they've covered all of the basic config stuff, but I'll ask him. Garmin told him it's a problem with the audio file. He's just looking for another data point to verify he's not the only one.

Cheers,
Rick

Sorry I always do that because it’s the first one that comes up. In this case it’s the same between both install types. 

https://static.garmin.com/pumac/190-02472-00_b.pdf (Page 62)

It sounds like it’s just turned off, but if it’s corrupted I would hope there would be an error message but maybe I expect too much.

Edit: Also if it is turned on, turn it off. Cycle power, and then turn it back on again and see if that helps.

Edited by dzeleski
Posted

I don't know which firmware version, but the local FBO has a G3X Touch 172.

The Minimums call is more like "Muh"

  • Thanks 1
Posted
I don't know which firmware version, but the local FBO has a G3X Touch 172.
The Minimums call is more like "Muh"

That happens if using a Bluetooth audio connection, but the G3X/audio panel should be all wired.
Posted

Closing the loop.

Thanks for the feedback. Further discussion with my friend John revealed he isn’t getting the test audio for Minimums and only a partial one for Vne on the Sound page in configuration mode. All the other alerts tested good.

I was able to verify in config mode all the audio alerts are functional on my airplane with 9.17, and with that info combined with your feedback he’s going to start with a fresh download from the Garmin site and reload the G3X OFP.

Thanks again.

Cheers,
Junkman

  • Like 1
Posted

Ok, so my last post was premature. The s/w reload didn't fix the problem.

My friend John discovered, in his research on this problem, that there have been other instances of audio problems with G3X Touch units out of the box that required a return to Garmin for remedy. He didn't find any specifics on what the problem was, just that the units had to be returned for the fix.

Garmin email and telephone support wasn't able to provide any helpful information beyond the usual reload, restart, power cycle recommendations.

If he's able to get details on the cause and remedy I'll post them here.

Cheers,
Junkman

  • Like 1

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.