Updated TAS605A - on the way back

My TAS605 was sent in 30th Aug, it is now 11th Sept, and a return tracking number is now available. Should be here before the end of the week, say 13th Sept, so it will have been 10 days exclusive of shipping. Right on schedule, if not early.

I have heard that the turnaround time may be climbing. As folks find out about availability, I expect there may be large glut of units sent in, in a short period of time. I may have got in before the initial wave.

It will be nice to have it back, I feel a little "threatened" flying around right now. ;)

Will report back after the install, with any observations.

* Orest

Should be installed this coming Mon/Tues.

So how does your Lynx display its two target types on the 540? Also as different icon types?

Looking forward to seeing the new TAS-"A" finally.  Won't have "dual" ADSB IN or air-to-air 980 hz Traffic (just 1090), but almost...

Tom W.

 

Does the Lynx send and display ADSB Wx to the IFD540/440?

On a similar note, does the Lynx ADSB-Wx populate the Avidyne "Info" Wx -Metars on the IFDX40, or are you only able to see this from your Lynx9000 box?

Thanks.

Tom W.

1) The installation manual was not clear as to what GPS data input was required, email from Avidyne support:

1. Garmin ADS-B+ GPS Protocol over RS-232.
2. ARINC-743A over ARINC-429.

From what we have seen on these -A units, the GAMA variety 429 GPS data doesn't include the specific ADS-B labels the TAS is looking for.  I need to have them spell this out far more clearly in the IM, because right now, it's not very clear.  

So beware. We had wired the 429 out from the IFD, to the proper pins, but cannot use the setting as noted in (2.), as this is used for other purposes and requires a different setting on that channel. Had to get back under the panel, and add the extra connector to use com port 5, as the first 4 are in use, and change the settings.

2) Symbology remains the classic diamonds, rather than the new arrowed icons. I suspect this has to do with needing a 232 input, vice the 429 that was the preferred before 10.2 -- actually as noted in the message above. Will investigate. Might mean yet another dip under the panel.

* Orest

I thought the same, but don't think that works.

I have channel 4 on both IFD 1 and 2 (they are parallel wired).  Ryan TCAD/RyanTCAD.

On Channel 6 out on IFD1, we ran an RS-232 configured ADS-B +(G), to i believe open RS-232 port 5 on the TAS-A.

We're planning systems checkout tomorrow morning (had to work today).  Will let you know, but per tech support, both in and out on the channel has to be Ryan TCAD for display purposes, thus the additional wire run.

But, if you want to “take advantage” of the -A feature - you have to do some other conifiguration to enable that.  The pre -A unit had a dedicated COM port for serial communications.  The -A unit doesn’t.  You have to sort of jury rig an access and use Hyperterminal or Putty, fashioning a home brew DB9 female connector, as well as a USB to serial cord.  {Memories of Compserve - remember 9600 baud 8 bits no parity?)

We spent hours yesterday and can’t get serial communications established.  Could be a port conflict but who the he** knows.

The device has a USB connector but did they make this simple?  Or configurable from the IFD.  Noooooo.

Will follow up later.  

My Lynx is connected to the IFD through ARINC 429.  It does not transfer ADS-B weather over that channel, only traffic.  The Lynx has an RS422 output that does send both ADS-B weather and traffic, and the IFD can receive it over RS232, now that Avidyne has increased the baud rate with the latest software update.  I have not had the update done, so my IFD is limited to receiving Lynx traffic only over ARINC.  And as someone pointed out, and I found during a recent flight, the IFD only displays basic traffic icons when ARINC is the input.  I prefer to have XM weather displayed on the IFD in a coming software update, so getting my Lynx and IFD to communicate over RS has not been a priority for me.

Since my Lynx ARINC connection to the IFD does not include weather, the METARs from the Lynx are not populated to the IFD.  I assume they would be if you wired the Lynx and IFD to communicate over RS422/232.

Does ANYONE see the new ADS-B type symbology, from their TAS-A unit?

* Orest

So the main advantage is the greater range (definitely improved, from 7nm to 30nm now), and more accurate azimuth -- at least for stations transmitting ADS-B position either directly on 1090, or if you are picking up ADS-R rebroadcasted 978, on 1090.

Cost me a little under 1 AMU for labor & shipping to/from, but N/C on the hardware itself.

* Orest

+1

* Orest

The range is impressively increased (for ADS-B targets), up to 30nm at least. It looks like the azimuth (where I had a visual on bogies) is dead on now and tracks precisely as they move. Before it was often a bit off, 30* to 45* sometimes, and tended to jump a bit when they got close.

Nice to now blend in the ADS-B data, but still have the TAS Mode C, as a fallback backup. Definitely a worthwhile improvement.

* Orest

Expect it is a connection (pins) or baud rate issue.

* Orest

Looking forward to the increased Simplex Range (as Orest experienced for the 1090 ADS-B) greater than the TAS605 range.

Just as an aside, I will continue to have my ES-transponder set as "978-In" client so as to have all of my 978 Simplex and ADS-R Incoming as UAT 978 Icons on my IFD#2 540 (TAS-A on #1 IFD540 for N-Numbers and dual Aspens - no N-numbers).

Maybe Avidyne will develop the 1090-In with UAT display capability... future upgrade??

Tom W.

I sent you an email.  Unfortunately, I have the PuTTY program on my PC from last century!

Tom

Looks to me like the conversation is largely over.  The TAS-A with sky trax trfc and Wx gives pretty strong coverage.  I’m letting go of the dual frequency issue.

Somehow, even though only 540 WiFi #1 ON (#2 = Off) both 540's displayed ADS-B/R traffic sources seem to be ported out over active WiFi to my iPad FlyQ EFB.  Non-FIS-B traffic like TAS and Mode-S display with N-numbers on 540#1.

IMHO, interfacing Avidyne with Garmin GTN - all bets are off.

My experience using TAS605"A" (and Skytrax/MLB 987-In) is that the full display of the full speed vector stuff (the new FAA terminology ATAS symbology AKA UAT) is that it appears to be Software Dependent...

So, even though our Avidyne IFD's does display full UAT symbology (987-In using Avidyne Skytrax aka MLB) with speed vectors, etc, when using TAS605A (1090-In), our IFD's only display diamonds, tail numbers, and vertical info - No Speed Vectors...

I discovered however, that using FlyQ on iPad and IFD540 WiFi porting out the 1090 ADSB traffic, the iPad display contains all the cool Speed Vector, tail number, and vertical info... So, my conclusion is that the IFD540 software just isn't up to speed on the full display capability of 1090-In traffic, even though the 987-UAT display shows all.

With your Garmin GTN, I have to assume the same software discrepancy with cross vendor incompatibility.

Tom W.

So many possible answers about the current situation in the UK dance through my head, none of them appropriate...