I have the same engine, it would be great if the G3X Touch could also read engine faults instead of my having to wire up the diagnostic software on a computer after I land.

I'd like the ability to display GDL-39R FIS-B info on either display (in a dual display setup.) Currently, it's only available to the GDU that the serial line is physically connected to.

Hello maus92,

Although it is true that the GDL 39 supports only a single wired RS-232 connection, you may optionally display FIS-B weather information on a second GDU 4xx display using the Bluetooth interface. This is documented in section 8.11 of the G3X Touch pilot's guide: http://static.garmin.com/pumac/190-01754-00_E.pdf

- Matt

Yes, and it works very well indeed!

Looks like 4.10 is now out, can we get a mailing list or some sort of official notification going Garmin? Maybe they already have it and i'm the odd man out

Changes made from version 4.00 to 4.10:
Add support for UMA N1EU70D 0-70 PSI differential fuel pressure sensor
Add support for configuring Vne in terms of true airspeed using a different value from indicated Vne
Add support for high-resolution SXM TFR data
Add support for ETE To Destination and ETA At Destination fields in data bar
Add menu option to transponder page to test Mode S ALT reporting when on the ground
Add option to configure external light flash priority
Improve Connext Bluetooth interface
Improve weather data processing
Improve contrast when editing numeric values for PFD bugs and baro setting
Improve configuration pages
Improve gauge display for turbine engine torque and RPM
Improve display of highlighted traffic targets
Improve GPS data sharing between displays
General improvements to system operation
Includes update to GSU25 software version 3.50
Includes GAD27 software version 2.00
Includes GAD29 software version 2.20
Includes GDL39 software version 4.60
Includes GEA24 software version 2.60
Includes GI260 software version 2.70
Includes GPS20A software version 2.10
Includes GSA28 software version 3.00
Includes GSU73 software version 3.40
Includes GTR20/200 software version 2.70

I might be a little paranoid about flap position sensor failure but.......

Unless I'm mistaken it looks like you can't set a 'max run time' for the flaps in the way that you can with the trim. This would be useful to protect against some form of position sensor failure if you're not using the optional end point microswitches.

Maybe it could also have functionality to quickly disable the flap position sensor operation completely, via the touch screen, so that you can still 'manually' raise and lower the flaps if the flap position sensor does fail?

It might also be useful if the system could provide backup control via the touch screen to allow trims to be returned to centre and flaps raised/lowered (as long as this doesn't introduce worse failure mechanisms) as an emergency redundant backup.

Setup the new ETAD (estimated time arrival at destination)

It consistently displayed the central time ETAD when my destination was in eastern time zone- is that the intent of the setting?

Hello siclick33,

The GAD 27 does not have a user-configurable maximum run time for the flap motor, but if the flap position sensor gets "stuck", it is smart enough to not run the motor forever. There are various ways one could imagine a flap position sensor misbehaving, but the GAD 27 is designed such that none of them will ever prevent the pilot from raising or lowering the flaps if he really wants to.

- Matt

Hello Brian,

The ability to display a field showing estimated time of arrival at the destination waypoint in the data bar simply repeats the same ETA information that was always available on the flight plan page. These values are always displayed using the currently selected system time zone.

- Matt

Feature Request - ETAD displays time at destination timezone :)

there was a Super Bowl party planning incident that involved relying on that ETAD field to determine when guests should arrive, it said ETAD: 16:11 which of course ended up being 17:11 EST

She was happy she did the military time conversion, not so forgiving when I explained the fancy avionics don't factor in time zones

4.10 does seem more stable, I intentionally tried to reproduce my bluetooth-induced software reboots and was not able to, thanks for all the hard work you guys do