TAS-A display question (for Avidyne)

Catani wrote: You don't need the Lynx's extra-cost diversity option with a small GA aircraft.  One antenna works fine.  As it does for the 345 as well, I assume.   The 345 of course lacks a display screen, so they are not strictly speaking equivalent products.  On the Lynx, the screen permits it to display traffic (at shorter display range) and weather while your other display(s) is set to something else (longer range, for instance).  If it's within the budget, the Lynx screen is worth the extra cost and provides redundancy as well.

How many screens do you need? As I said before, which system is best for you will depend on other installed equipment.

If you have a GPS navigator, or two, a PFD (like an Aspen perhaps), one or two iPads, and maybe an MFD as well, you can display all the data that the GTX345 has to offer anywhere you like, and on a much larger display than the little L3 Lynx screen. Of course, if you have one or more of the above options you may display the Lynx data on them as well - which makes the Lynx screen kind of unnecessary in that case.

The GTX345 has internal AHARS - the Lynx does not. With the internal WAAS option and an iPad running the Garmin Pilot or Foreflight app, the GTX345 may act as a completely independent/redundant GPS navigator with backup attitude indicator and synthetic vision on a larger display than even the largest panel mount GPS's have to offer. The GTX is also available as a remote mounted option.

So, if you don't have an alternative display or want an active traffic option at a premium price, the Lynx may be for you if you have the panel space to mount it where you can see it. The GTX offers an alternative feature set that the Lynx does not, but does not have an internal active traffic option.

Both the IFD and the GTN navigators can display traffic and weather data from either unit - but the IFD cannot control the remote mounted version of the GTX.

One is only better than the other depending on your needs and other available equipment.   








Edited by Stiletto1 - 12 Aug 2018 at 6:37am

Catani wrote: Stiletto1 wrote:   How many screens do you need? I don't need any.  I was trained on steam gauges. Stiletto1 wrote: The GTX345 has internal AHARS How many AHARS do you need?

I too was trained on steam gauges some 40+ years ago - but such a comment is irrelevant to this discussion since we are talking about the depiction of traffic awareness on a screen.

As to the number of AHARS you may need, again, it depends on installed equipment. If you are glass panel equipped the answer may be two, unless you are maintaining a sucky-gyro for backup attitude.

If you are only steam gauge equipped, how many sucky-pumps do you "need"? My plane has two, both soon to be relegated to back up AI status only... :)

Edited by Stiletto1 - 12 Aug 2018 at 9:42am

Catani wrote: You took my question too seriously, it was just a play on yours.  Mine was intended to be just as irrelevant.

Yes. "Sucky-gauges" was a very serious comment on my part.

Catani wrote: What we actually settle for in GA is what we can afford.  The additional features of the Lynx 9000+ was in my budget, so I got it.

I guess I don't just buy stuff cuz I could.

Catani wrote: It's all a matter of personal choice, of course.  As it should be.  Get the facts about the products, then decide what's right for you.

Which brings us back full circle to my original point when I entered this discussion to correct some of those "facts" you were spewing about one being better than the other.

Catani wrote: Melohn wrote: Catani wrote: Melohn wrote: I had a Skywatch, and decided on a 345 for ADS-B In/Out. Interfacing the Skywatch to the 345 was straightforward, and provides the same TAS+TIS-B dual frequency capability as the Lynx 9000+ at significantly less expense. Right now, I’m seeing TAS on my EX5000, and merged TAS+TIS-B on my navigator. With MFD 8.2, I’ll have both on my MFD. Thanks Avidyne! Interesting, but need a little more info to evaluate for general application.   Is your Skywatch TAS output now routed to the 345 only, or does it connect to both the MFD and 345? What's the model of navigator you have that displays your 345 output? The TAS is currently connected to both the 345 and the MFD. With release 8.2, I’ll be able to connect the MFD to the 345, which should then display converged traffic (TAS+TIS-B+dual mode ADS-B direct reception). I’m currently seeing converged traffic on my iPad in ForeFlight, and on my 430W navigator. I’m likely to upgrade that navigator to an IFD or a GTN at some point, both of which should work. So you have Skywatch traffic on your MFD with 8.1, which we all know is a compatible combination.  But, do you know whether anyone has confirmed that the 345 traffic output will be compatible with the MFD with 8.2? I ask, because once you connect the 345 to the MFD, the Skywatch connection will have to come off.  You can't have both at the same time feeding the MFD.  Also, do you whether anyone has confirmed the 345 traffic output would be compatible with an IFD?  (No question it would be if you put in a 650 of course.)  It seems these Garmin-Avidyne compatibility assumptions at times have not worked out despite promises.  Just wondering if there is any real-world confirmation of the compatibility of these combinations.

Catani wrote: Stiletto1 wrote: Which brings us back full circle to my original point when I entered this discussion to correct some of those "facts" you were spewing about one being better than the other.   Rather than get into the mud with you, I'll not make any further comments.  I'll let what I've said, and the language you have used, speak for itself.

Salute!

Catani -

Edited by n7ifr - 16 Apr 2019 at 8:22pm

Catani -