TAS600 Systems and ADS-B - TAS "A" Output

TAS "A" Output

Printed From: Avidyne
Category: Avidyne General
Forum Name: TAS600 Systems and ADS-B
Forum Description: Topics related to the Avidyne TAS600 Traffic Advisory Systems and ADS-B
URL: http://forums.avidyne.com/forum_posts.asp?TID=1359
Printed Date: 21 Nov 2024 at 4:13pm
Software Version: Web Wiz Forums 12.01 - http://www.webwizforums.com

Topic: TAS "A" Output

Posted By: ddgates
Subject: TAS "A" Output
Date Posted: 19 Jul 2017 at 7:04pm

Operating on indications that the "A" upgrade is in process and going to happen.

Have questions about display formatting.

-Is a rewire to the IFD(s) going to be required for display there? What is the display going to look like there? Direction vectors and N-numbers like ADS-B?

-TAS output is currently displayed on my Aspen MFD. Will that wiring or format change? RS-232 or ARINC?

This isn't a casual inquiry. Plane will be in shop with empennage open to do this. Want to get it right the first time.

Please advise, and thank you.

-------------
David Gates

Replies:

Posted By: AviSimpson
Date Posted: 20 Jul 2017 at 9:49am

In general terms:

- Any display that works with TAS or TAS-A now should work with TAS-A after the ADS-B updates.

· The ARINC-429 interface currently being used (ARINC-735 TCAS format) will continue to work, but will not show additional ADS-B data (ADS-B targets will be displayed, but they will look the same).

· The current RS-232 interface will also remain unchanged. ADS-B targets will be displayed, but they will look the same.

· The RS-232 interface will be updated so that display manufacturers can update their software to request additional ADS-B data. In this case direction, flight ID and on-ground status for ADS-B targets will be provided on the interface.

· There should be no need to rewire connections to the displays since the current interfaces are remaining unchanged.

· A connection to a compliant GPS source will need to be provided.

-------------
Simpson Bennett
Avidyne Corporation
Product Manager

Posted By: ddgates
Date Posted: 20 Jul 2017 at 10:05am

AviSimpson wrote:

In general terms:

- Any display that works with TAS or TAS-A now should work with TAS-A after the ADS-B updates.

Thanks, Simpson.

Does 10.2 have the display software enablement to do that, or is that going to require another software update?

-------------
David Gates

Posted By: n7ifr
Date Posted: 20 Jul 2017 at 10:41am

The current RS-232 interface will also remain unchanged. ADS-B targets will be displayed, but they will look the same.

. Skytrax100 Traffic already presently displays via RS232 --> 540 with full UAT target/Speed Vector Icons

. TAS 605 targets currently display via RS232, without Velocity Vectors, but With altitude trends.

The RS-232 interface will be updated so that display manufacturers can update their software to request additional ADS-B data. In this case direction, flight ID and on-ground status for ADS-B targets will be provided on the interface.

. This sounds like great news, assuming the new RS232 interface will provide the same format as Aspen & Lynx Traffic/Wx RS232 format: 115,200 baud & GDL90 Format. This is what we need from the Avidyne Software update.

. When the TAS "A" software unlock becomes available, Will there be an Avidyne STC'd Unlock ($$) for Avidyne --> Aspen STC Unlock to display TAS"A" Traffic and Skytrax100 Wx via RS232 to Aspens?

Lets hope Avidyne comes through with improved cooperative efforts to display on Aspens, etc.

Tom W.

ffff