TIS or TAS

I have an IFD 540, AXP340 and a Ryan 9900BX.  Currently it appears I only get TIS traffic.  If I can only display one or the other, I think I would be happier with TAS from my Ryan.  What do you guys think?  I think that would involve making the Ryan the sole supplier of traffic info to the IFD.

Edited by Warrenwhis - 06 May 2017 at 4:06pm

I see some of the traffic with N numbers. Is this possible with the Ryan. Thx Orest

oskrypuch wrote: It is certainly possible with the rebadged TAS units (like mine), I expect the Ryan does much the same with other planes that have Mode S transponders. * Orest

oskrypuch wrote: The TAS-A units will accept direct 1090 transmissions as well. * Orest

n7ifr wrote: Orest, Can you give us some approximate timeline for TAS "A".    Also, has anybody at Avidyne yet determined a way to have our SkyTrax100 display on Aspen's? Tom W.

"Also, has anybody at Avidyne yet determined a way to have our SkyTrax100 display on Aspen's?"

Mine does.

I have active traffic (SkyWatch) and it's traffic output was originally displayed on all my screens (Aspen EFD, 540/440 and EX5000 MFD) prior to 10.2 and 4.1 software updates.

After my software was upgraded, I had my avionics shop "turn on" ADS-B traffic to the IFD 540/440. I forgot to tell them that the Aspen was also enabled to show traffic. The avionics tech and I were both surprised to see ADS-B traffic showing up on the Aspen. There is no direct link between the MLB100 and the Aspen so that traffic info must be coming from the IFD's.

Targets are displayed in the older style diamond shape with relative altitude rather than the newer arrowheads with a trend vector line that I see on the IFD's but they are definitely ADS-B derived. I still have Skywatch displayed on the MFD so it's easy to compare sources.

I don't know if it's actually supposed to work but it definitely does in my case.

Edited by ronl - 09 Jun 2017 at 9:23am

ronl wrote: "Also, has anybody at Avidyne yet determined a way to have our SkyTrax100 display on Aspen's?" Mine does. I have active traffic (SkyWatch) and it's traffic output was originally displayed on all my screens (Aspen EFD, 540/440 and EX5000 MFD) prior to 10.2 and 4.1 software updates. After my software was upgraded, I had my avionics shop "turn on" ADS-B traffic to the IFD 540/440. I forgot to tell them that the Aspen was also enabled to show traffic. The avionics tech and I were both surprised to see ADS-B traffic showing up on the Aspen. There is no direct link between the MLB100 and the Aspen so that traffic info must be coming from the IFD's. Targets are displayed in the older style diamond shape with relative altitude rather than the newer arrowheads with a trend vector line that I see on the IFD's but they are definitely ADS-B derived. I still have Skywatch displayed on the MFD so it's easy to compare sources. I don't know if it's actually supposed to work but it definitely does in my case.

ronl wrote: My MLB100 is configured to communicate with the IFD's using the "Aviation" protocol. The avionics tech had it configured using the "ADS-B (G)+" protocol but then my Garmin 796 would not automatically download the flight plan from the IFD's so I had him switch it back. The only downside that I can see is that the yellow "ADS-B degraded" flag is constantly displayed on the IFD's traffic thumbnail. Everything else seems to work fine.

If you change the wiring to put the MLB100 on a different output port than the 796, you could then feed each unit with the appropriate data stream, and have it all.

David Bunin