Even if the SN3500 accepts GDL90 or whatever, that then leaves me with the TCAS1 functionality (which is still the most universal, due to the wide use of transponders) not working.
Ok I see, yeah in my case I wont go for the certified TAS solution over ARINC 429 at this moment. At least I will be making my bearing distance clearer to all around with the GNX.
The SN3500 gets traffic via ARIN429, from the TAS605. Avidyne are offering the TAS605A and they “guarantee” the data stream out of that is exactly the same (whether it contains just Mode C/S or ADS-B IN data) but I choose to not take that at face value, so I am waiting for an exchange TAS605A, otherwise I could be screwed and nobody will help me. I might have to purchase a TAS605A and then sell the TAS605 on Ebay…
The key point is that the TAS605A is supposed to merge TCAS1 and ADS-B IN data into the single ARINC429 traffic stream and do it totally transparently so any “ADS-B” related config on the SN3500 should be totally irrelevant, and if such a config is needed then some basic point has been missed. If such a config is made, that suggests somebody is setting up an ADS-B only system, with no TCAS1. That is not what I am doing.
Even if the SN3500 accepts GDL90 or whatever, that then leaves me with the TCAS1 functionality (which is still the most universal, due to the wide use of transponders) not working.
And I still have the KMD550 not displaying anything other than ex-Avidyne ARINC429.
It is very easy in this game to talk about acronyms and labels and whatever but in the end if you install something and it doesn’t “quite work” you are screwed. I am super sceptical 
I think for me for ADS-B IN a TAS605A (“A”) would be a great solution which will work with everything I have, and everything I might have (2×IFD540).
And for ADS-B OUT I could put in the GTX345. That is a standalone function, installable “surgically”.
I still won’t see uncertified emitters, mostly SIL=0. Back to that old topic A DIY data merging box.
Peter wrote:
EHSIs are in the primary field of view.
At least for ADS-B Traffic a SN3500 software upgrade will solve that hopefully, (it has been available for the 4500) next year what I understood, however not sure how the filtering of this SIL 0-3 will be handled software wise. ADL outputs GDL90 Garmin has its own model. SInce both FIS-B and ADS-B are on the same pins I am not sure if it would be better to use the Garmin or GDL model…hence two different system inputs ADL with ADS-B and FIS-B over GDL90 or the same over Garmin protocol
Looking at the install manual for the 4500 the following TCAS processing protocols are supported:
Thank you, but I do not want display of traffic on a tablet.
Lots of reasons, starting with Ipad shutdowns in sunlight. I have 2 x SN3500 EHSI and that is the primary TCAS 1 display, plus the KMD550 which will one day be replaced by 2x IFD540 (also removing the KLN94). The IFD boxes may do this but the EHSIs are in the primary field of view.
One alternative today for your case @Peter would be fixed installation of an ADL/PowerFlarm/ADLRS232 combo. That gives you Wx & combined Flarm/ADS-B In tfc over wifi, and on a panel unit if compatible, via GDL90 protocol. Only needs a logbook signoff. Installation time likely the biggest expense item.
Peter,
Thanks for your reply. I have just had my GTX330 upgraded to ES and already had GNS430W so I should be SIL=3
if you know who (A) has got it working.
I am aware, Stanley, that an uncertified ADS-B IN box will receive both uncertified (SIL=0-2) and certified (SIL=3) ADS-B OUT emissions, and that is quite a good thing, but I prefer to avoid gadgets around the plane which need to be kept charged, etc. The TB20 has very little room for that sort of thing. I would much prefer to have everything in the panel, and unfortunately the options for that are all in the certified arena. There are obvious “illegal” routes for merging data but unfortunately the protocols are hard to find; nobody who works in the relevant fields has thus far been willing to help.
I am still looking at the GTX335 and the TAS605 “A” upgrade. That would give me both ADS-B OUT and (certified emitters only) ADS-B IN, and would be quite easy and low risk in terms of the installation. I will probably do it at my next Annual, which will be my next opportunity for a hangar where work is permitted. I was going to do it at the last Annual (Jan/Feb 2019) but the installer who I use for wiring (I can do it all myself but as with house electrics somebody who does it all day does it a lot faster) went elsewhere for a number of weeks…
Peter,
I have not read every jot and tittle of the above posts, but you could get a PilotAware Rosetta, stick it with a suction pad
to a rear window and see the local aircraft that is ADS-B out (it might surprise you). The cost £260 plus a 5v power bank
maybe £20, ram suction cup £?. Whilst flying you can wifi the traffic to an iPad and get critical verbal traffic warnings via
SkyDemon (if you have it) over Bluetooth into your headset, if you do not have this facility Bluetooth earpieces fitting
under your headset cost £5 – they should work. A 10,000mah 5v power bank will run the PilotAware for 10hrs.
After each flight one can download all the traffic data acquired onto a laptop and run through the route and see what was
flying near or far from you, a free service using the AIRCREW site. You will also see other traffic tx-ing GPS position
but that is another matter. With this info you can consider your future options.
I have posted on some US sites (avionics market at least 10x bigger than Europe) about whether anyone is feeding a TAS605A from a GTX335, and got zero, zilch, no input at all.
Perhaps this scenario is very rare now and everybody (well those few who have bought or upgraded to a TAS605A, which has not been out all that long) is feeding it from their panel mount WAAS GPS.
In that case I would expect Garmin to have the same output data stream in say a GTN650 as in a GTX335. But you never quite know…
If the WAAS GPS output stream document was available, there would be an easy solution…
Yes indeed; a bigger job than I am able to take on at present – either way (GTN650+750 or 2x IFD540). I would have to do it freelance because e.g. the autopilot interface from the 2x SN3500 is not something I feel able to explain to any shop I know which does GA and which I would want to use. It is covered by STCs but there is a risk of the shop deciding part way through that there is some issue. It has happened to too many people. It would be 1-2 weeks in a hangar, with special issues like this just to make it more “fun”
I contacted one UK company about installing a GTX335 and they cannot do anything for about 6 months! But a GTX is an easy freelance job (N-reg) in ~ 2 days, much of which will be the WAAS antenna.
That Avidyne page is interesting. However, I am fairly sure that for non SIL=3 ADS-B OUT targets the behaviour of the system is exactly the same as presently.
