hgerhardt
Well Known Member
I know, but I already use those fields. Besides, the clock is so small that having Zulu right next to it seems like a no-brainer.
The Info page (which shows the GPS satellites in use) has Zulu time shown.
I know, but I already use those fields. Besides, the clock is so small that having Zulu right next to it seems like a no-brainer.
.......... Currently when you download the engine data onto Savvy Analysis the only two data points that not included are the Hobbs and Tach time. ..............
Ability to get into System Info, to see FADEC error msgs, without needing to boot into config mode.
FADEC information has been available in normal mode in the GDU 4xx since version 8.81, and a System Diagnostics page has been available in the main menu since version 9.10.
I’d still love the ability to mark which fuel tank is draining based on an input from a switch. If pin (pulled) high, then fuel flow is from the left tank, if pin low, from the right. I’d totally glue a magnet to the bottom of my andair selector knob and put a reed switch or hall effect sensor behind it, but for someone hat didn’t want to bother, just wire a switch you flip at the same time.
Here are a few things I’d like to see after using my 10” G3X touch for the 19 months:
<snip>
- Currently when you download the engine data onto Savvy Analysis the only two data points that not included are the Hobbs and Tach time. I’ve mentioned this to Garmin several times over the last year with no response. It seems to me a very simple modification to the data logging. Although this is not a big deal why not include these two parameters. If I want to look at engine data 6 or 9 months ago on Savvy Analysis why should I have to search my logbook to estimate what my engine time was.
<snip>
.
Justin,Mehrdad,
No change here. You likely have VNAV enabled on your GTN 650 Xi, and did not on the GTN 650. It has always worked like this. If VNAV is enabled on the external navigator, that is where you will program a VNAV descent. If VNAV is not enabled on the external navigator, you will program the VNAV descent in the G3X Touch.
Thanks,
Justin
If you open the .csv file in excel, the header includes Tach and Hobbs time. But you'd like those added to the rest of the columns I suppose.
So, a workaround could be to open the file in a spreadsheet, get the tach/hobbs time and then close and rename the file with those numbers included in the filename.
View attachment 35405
A "Switch Tank" type pop up warning for OAT when it is approaching freezing temp for the pitot heat.
Thanks Matt, but I have just the plain and standard pitot heat. Hopefully they can add the CAS message for that as well.If you have the heated/regulated GAP 26 this is already supported via a CAS message.
Thanks Matt, but I have just the plain and standard pitot heat. Hopefully they can add the CAS message for that as well.
I wish I could have a single GDU with and ADAHRS and select to be either MFD or PFD. Currently it will default to PFD when an ADAHRS is present and will not select to MFD with that setup. I’d love to have a G5 as PFD and GDU as MFD but have the option for selecting PFD if I want.
No I actually want to be able to do it with the ADAHRS there. So that’s why it is a wish. I already know it doesn’t do what I want.
The reason I want this is to have a g5 as PFD. But if the g5 dies I’d like to have the ADAHRS support the GDU as a PFD. I’m only wanting one GDU.
So a discrete input that allowed MDF/pfd selection in addition to the current reversion mode select would be my answer.
Hi Matt,You can still get the CAS message today if you have an unused discrete input. You don't even need to add any additional wiring. See "Pitot Temp" in section 29.4.32.26 of the current installation manual (revision AS).
No I actually want to be able to do it with the ADAHRS there. So that’s why it is a wish. I already know it doesn’t do what I want.
The reason I want this is to have a g5 as PFD. But if the g5 dies I’d like to have the ADAHRS support the GDU as a PFD. I’m only wanting one GDU.
So a discrete input that allowed Mfd/pfd selection in addition to the current reversion mode select would be my answer.
However, I have now persistent yellow advisories on the GDU for ‘AHARS #2 fail’ and ‘ADC # 2 fail’: it isn’t there a second GSU25 after all!
Disabling ADAHRS #2 (G3X LRU Config) effectively removes the GMU11 and associated heading failover.
Seems I have stumbled across an undocumented ‘work in progress’ feature, maybe?
You answered your own question... it doesn't support having a greater number of magnetometers than ADAHRS units, so by telling it to expect two ADAHRS units you have caused it to show you an error message to tell you that one of them is missing.
You shouldn't need a GMU 11 if you have a GMU 22 in the system. Your system is exactly like mine except I only have one GMU 22 and two GSU 25s. And a single G5.
You shouldn't need a GMU 11 if you have a GMU 22 in the system. Your system is exactly like mine except I only have one GMU 22 and two GSU 25s. And a single G5.
As I've already wrote, I have only one G3X and one GSU25, so we do not have the same system. 90% of IFR-rated SEP (eg SR22) have two magnetometers for a reason (and the 10% without redundancy, may have troubles in IMC: https://aviation-safety.net/wikibase/16857). I'm looking for GA-standard IFR/IMC capability and redundancy for my plane.
Request for an LRU interfaced with the G3X system that could control multiple external low power circuits (LEDs or relays) based on user programmed logic signals in the G3X Touch.
Being one that has built many projects like this, it is not not fun to do but it is also very powerful.Garmin already provides an easy-to-decode RS-232 format intended for applications like this, which would be trivial to support with something like an Ardunio. Either find a high school kid to program it for you, or spend a few weekends looking at tutorials.
Garmin already provides an easy-to-decode RS-232 format intended for applications like this, which would be trivial to support with something like an Ardunio. Either find a high school kid to program it for you, or spend a few weekends looking at tutorials.
Being one that has built many projects like this, it is not not fun to do but it is also very powerful.
There is also an “airplane” quality hardened Arduino based controller design/board available by one of our VAF friends.
https://vansairforce.net/community/showthread.php?t=151119&highlight=Arduino+board
Garmin already provides an easy-to-decode RS-232 format intended for applications like this, which would be trivial to support with something like an Ardunio. Either find a high school kid to program it for you, or spend a few weekends looking at tutorials.
Which LRU has the serial interface? Link to documentation?
automatic start on the timer would be a nice add
A feature that would be very nice to have is to ability to set 'Missed Approach' Altitude that when we push the GoTo it will use that as the selected altitude instead of what is in the altitude bug.
You should set the MA altitude after you've captured the GP, then when you TOGA out, it will go to that altitude and fly the MA.