Audio Output Gone

Seems that the TAS-A software update has a problem in that configuration settings (which should be set and forget) are volatile and can reset to default on boot up without notice.  This leaves a situation where you can assume you are going to have audible traffic alerts, but they have become inaudible.  The only way to readjust the input volume is to open up the empennage, attach a laptop with a terminal comm program, and reset the value to whatever it was.  Only to find, however, it may reset to inaudible next boot, or several boots in the future.

Avi has done a Service Letter Bulletin with a *.bin file to lock the config files, citing issues with config resets, particularly audio.

I will bet most owners are not aware of this SB.  It involves adjusting the audio volume, and then rebooting the unit from the external micro SD slot with the bin file.

This issue became obvious in my install.  Adjust the audio to a comfortable volume, shut down the unit - would think all good, right?  Not so fast, cowboy.  In my case, the adjustment got undone on subsequent boot cycles, and since had to get a technician, open the empennage, and repeat the cycle.

Now, a fellow Avi owner with the same configuration as mine except different comm panel has lost his audio too.  So now he gets to repeat the cycle.

This is a safety of flight issue.  A pilot assuming he/she has audible alerting and then, well, maybe not, is at risk.  

I am posting on this to alert other TAS-A upgrade owners that in the case of the TAS-A, silence isn’t goldden, and may indicate a problem.

I went out to hangar, and reset my default Volume setting of 201 up to 415.  Seemed to hold through 2-3 re-boots of the TAS box, so did a flight yesterday - the TAS Traffic alert at 415 is way too loud.

Maybe someone smarter than me can come up with a Panel-Controlled Volume for the TAS Alert.  Look at the TAS Install manual, page 90 which refers to the Avidyne ATI panel Volume Control for the TAS-A box...

Just saying.

Tom W.

* Orest

* Orest

We undid the parallel, and now the TAS-A audio is alone on the unswitched input of the PMA450.  It can be heard.

But then, a fellow pilot, same airport, different airplane but same equipment basically as mine (and also recent -A upgrade to TAS605) lost his audio.  Don't know if he had the same install parallel as mine but obviously same, so same problem.

Practically speaking, doing the SB procedure is problematic for me because each time the upholstery has to be removed and multiple parts of the bulkhead have to be undone to expose the unit in the empennage and gain access to the TAS box.  There is double uncertainty about the apparent fragility of the external SD drive (and to some degree, absence of DOS/Unix like manipulations of the avionics technicians.)  So for me solving the input issue was the better choice assuming that it holds up and the problem doesn't drop the config to below the midrange level.

In the case of the Piper pilot I mentioned, don't know what his comm panel connection is but his issue is likely to be similar.

On another note:  we both have other questions about the TAS-A functionality, and have gotten variable answers from different Avi sources.  So, dryan, you are the guru on this system so let me ask this and maybe other questions: 

-To maximixe the functionality of the TAS-A upgrade, and with both TAS-A and MLB-100 units installed, does it serve better to indicate on our TXPs that we have 1090-in or 978-in? I.e., does the TAS-A unit make use of the 978 ADS-R broadcase which we could in theory receive on 1090?

Thanks, and happy holidays.

Seems not ready for prime time.

I had the "WHITE LIGHT OF DEATH" on my TAS and it was a blown board, or so they said. 

I don't have any recommendations for improving the traffic display yet, but stand by...we intend to continue improving the TAS-A.

Pleased to know you will engage on this.  I think that is the ingredient necessary to get to a fix.

Thanks and happy holidays.