FWIW... I'm in the middle of wiring my dual G5s now. I have a GNS430, GTX345, and an Stec30. Currently I view weather and traffic from the 345 on the 430 (and 796)

To interface the G5 with the autopilot, the install requires a box called the GAD 29.

To wire the system, the GNS430 needs to ingest EFIS/Air Data streams from the GAD29 into BOTH the available AIRINC 429 ports (pins 48/49 and 50/51) (Fig 5-12 in the install manual)

Why does this matter? To get WX/Traffic from the 345, the 430 uses one of the 429 streams (pins 48/49.) Apparently, Garmin F'd up and there is not enough space. Soooo... Garmin just told me I had to choose. If I wanted to use the 2nd G5 as and HSI w/ my autopilot and GPS/VHF Navigator, I will NOT be able to get WX/Traffic on the 430.

BTW, this is the same for the GTN6XX/7XX, 5XX, and 480.

WTF!?!?!?

That said... There is a glimmer of hope. Garmin knows this SNAFU and says they are working on it. They wouldn't give me a time frame, but the next software REV is suppose to fix this. They have already done the programming, they just need the approval. The new update will allow for all EFIS/Air Data junk to talk to the 430 via one 429 channel rather than two, allowing for the 2nd to be used for the traffic from the 345.

Ugh.....

If anyone wants to look at the install, it is here: http://static.garmin.com/pumac/190-01112-10_11.pdf

Yeah. Ran into this and prolly shoulda posted about it. I just reserved the 2nd 430 for traffic.

Good info!

Jim

Apparently Avidyne is a bit smarter and the 440 does not have this issue.

What a headache, I frequently look at taking the plunge into a GPS Navigator - and constantly run into these sorts of compatibility issues and gotchas which stop me from doing the install and pulling the trigger.

I'm leaning towards the 440 now, but I'm seeing it still has compatibility issues with my ESGi

Frankly, I’m amazed how much of this stuff actually talks to each other. Considering all the combinations and permutations possible.

I suspect that avionics is one of the most frustrating fields in aviation.

MTV

mtv wrote:Frankly, I’m amazed how much of this stuff actually talks to each other. Considering all the combinations and permutations possible.

I suspect that avionics is one of the most frustrating fields in aviation.

MTV

Especially as cockpits become more integrated. Can be exceedingly frustrating.

mtv wrote: Frankly, I’m amazed how much of this stuff actually talks to each other. Considering all the combinations and permutations possible. ....

A friend is currently trying to sort out an issue with his Garmin 430 not giving GPS location to his Stratus ADS-B transponder.
Probably not an insurmountable problem, but I could understand it if Garmin (and everyone else) designed their avionics to only talk to their own stuff-- in other words, proprietary.
That would piss everyone off, but really, it only makes good business sense.

@bigrenna Any update on the software?

I am about to do a dual g5 with a 430W and a gad29, And was considering adding the gtx345 and wanted to ensure compatibility before I spend the money.

I'm curious if using a separate external antenna just for the G5 would eliminate the need for the extra hookup to the 430?

Sent from my SM-G960W using Tapatalk

I recently looked at the install manual for the G5 system. If you use the GA-56 antenna into the G5, then it will use its own internal GPS to do the attitude smoothing, relieving the need for the external GPS data from a 430 for example. After looking at all the elements of the G5 system, it actually is within a few dollars of the latest Aspen offering. The Aspen system has a lot more ARINC ports in addition to more RS-232 ports. They do nickel and dime you for the additions of traffic, SVT and AOA, but they are simply software activations, not wiring changes. There is a recent SB about traffic bombing the system, but they should have that worked out in short order.

I was somewhat disappointed on the lack of input ports on the G5 system. It seamless integration for the Garmin autopilot make it very attractive, but apparently the True-Track system offers many of the same simplified installation of the Garmin system and applicable to something like the Aspen. I have not used either, so my comments are just based on conversation and paper specs. From having sat behind both the G5 and the Aspen, I personally think the Aspen has a much clearer display.

It is not so much that the interfaces are propitiatory, but rather getting the input output matched with the rather caviler naming of data types makes it seem so. I just finished up putting a 345R into my G1000 system, all Garmin, so you would think this would be straight forward. Not so quick. First I had to update the Cessna software to the latest version to allow ADS-B, but then I had to use a G1000 loader for the 345 system, something they neglected to mention on the SB for the install. I also had to use another software tool plugged into the USB port via a laptop on the 345 to program it. Of course, you can't just elect the GTX345 from there port pages, you have to put in the GDL-90 as the box talking to the system, like this would be apparent. The Garmin rep told me I was using the wrong install manual version I needed the -10 version, program and call back. The next time I called, oh your using the -10 version, well its wrong, change so and so to this and then it should work. Well it all works now. Naturally, now my autopilot is off line. Well you need to talk to the Cessna rep, as that part of the software is under their control as they own that TC. So lets see what they say tomorrow.

None of the new stuff is straight forward. They seem to like certain ports to do certain things. If your putting data out on a 430, it is preferred to use ARINC, but the 650 likes to use RS-232 ports for the same thing. It not like the old days of VOR's where you used composite and resolver outputs, along with AC XYZ for heading. In the future, the talk is just having the boxes bluetooth to each other, eliminating the wiring, the largest source of failure. This might lead to your autopilot accidentally paired to your music so it would flying some kind of Samba on the approach, could be fun.