Thought I might share some of my experience, so far, in migrating from my legacy g3x (non touch) single PFD to a 116B screen. Just considering the 7 day elapsed time from receipt of the unit to getting into the air, I would call that a success given the age of some of my LRUs and the first rev of the product software. I am thrilled with the upgrade and looking forward to spending more time behind it in the air. Garmin has been very supportive and so has my reseller (Sarasota avionics) throughout the entire process.
My system is simple and includes a G5, 2 GNS430w, GMC 305, GSU 25 and GTX 23ES as well as supporting LRUs
Issues/observations I ran into so far
Tom
My system is simple and includes a G5, 2 GNS430w, GMC 305, GSU 25 and GTX 23ES as well as supporting LRUs
- First step: read the install manual!!! Lots of valuable info here
- Record all sensor settings from the original PFD
- Practically no wiring changes, add power pins to the original connector and swap out the config module
- Power up and start configuration.
- As devices are added to the new system, their firmware will be updated if part of the AXIS package
Issues/observations I ran into so far
- GTX 23es firmware needed to be updated
- Getting the axis to generate a mode s code was funky - had to attempt it more than once.. garmin is aware of this anomaly. Note, system will show GTX 23es device as “green” without a valid mode s id
- Transponder adsb status is indicated as ‘Fail’ on the screen despite being fully functional and passing the FAA performance criteria
- AHRS needs AXIS vfr gps to be enabled to avoid an alert to degraded function - this still needs to be resolved
- G5 had to be removed and put back into the device list to get the integration to take - this could be pilot error but not sure. Either way it works now.
- EIS is much quicker to report things getting out of range than previous .. for example alternator current spike when gear pump operates. I have a charging threshold alert set to 20 amps
- Gns 430 indicates “system id missing” which turns its status yellow but otherwise functionally fine - as far as I can see, for now p! Eating on answer from garmin
- An undefined instrument will show as an eis fault (eg fuel sensor calibration)
- GMC mismatch fault - reported to garmin
- Yet to confirm if I can import original checklists
- The TIS channel between GTX and GNS has been disabled
Tom
