adsb problem

[bigsteve]

for the last month, my adsb display is showing adsb-no radar.  The left side of the screen says I'm rcving adsb and i seem to be getting wx & current metars. I get traffic  and it says tis-ok, however, I get a  ghost image alot and 00 trafic alerts. Is this an issue with my sil , sda problem we heard about for 2016 with the gps-250 ? I'm in southern WI, and as i remember it, my screen previously always said adsb-ok, not no radar. This summer i did the faa test on my adsb  & everything came back ok except for sda, sil, which i expected. I'm still using version 11 software because i don't have the canopy latch switch installed yet on my Vans Rv-12 slsa.    thanks

 

[dynonsupport]

Here's the explanation in the Pilot's User Guide for the NO RADAR message:

SkyView will annunciate “No Radar” traffic when it has ADS-B reception capability, but that ADS-B reception does not include either ADS-B groundstation coverage or radar targets included within those ground-based ADS-B traffic reports. Therefore, the ADS-B ground station is not able to convey a full traffic picture and cannot make you aware of all possible detectable traffic.

This is an ADS-B ground infrastructure issue in your area.

The "ghost traffic" where you're seeing yourself may be a side-effect of this issue.

for the last month, my adsb display is showing adsb-no radar.  The left side of the screen says I'm rcving adsb and i seem to be getting wx & current metars. I get traffic  and it says tis-ok, however, I get a  ghost image alot and 00 trafic alerts. Is this an issue with my sil , sda problem we heard about for 2016 with the gps-250 ? I'm in southern WI, and as i remember it, my screen previously always said adsb-ok, not no radar. This summer i did the faa test on my adsb  & everything came back ok except for sda, sil, which i expected. I'm still using version 11 software because i don't have the canopy latch switch installed yet on my Vans Rv-12 slsa.    thanks

 

[dynonsupport]

Looks like Wisconsin and Michigan is having some issues. There are a few people over at VAF with the same issues:

http://www.vansairforce.com/community/showthread.php?t=130998

We've sent an email to our FAA ADS-B contact to see if there are any known issues right now.

 

[N100MG]

I am running version 13 of the software and just started seeing this issue in the last couple of weeks. This is flying in areas where I have always had excellent coverage. Th class C airport I fly out of isn't exactly in the middle of nowhere.

 

[Schorsch]

I saw similar but only temporary ADSB anomalies for the last few weeks in Georgia & NC with 13.0.2. Thought it might be related to the Armed Forces' "interference" which the FAA announced about a month ago... But just a guess

 

[bigsteve]

Flew today & adsb read ok vs No-radar & TIS-ok in southern WI, still alot of 00 traffic alerts though FYI

 

[swatson999]

Flew today, saw the same ghost traffic (i.e., myself), several times (this in an area in which I've flown *a lot* and never, to the best of my recollection, ever seen this). Always when I had ADS-B OK and NO RADAR shown on the map display.

First time was, well, disconcerting, but I've seen ghosting before (as far back as when the Garmin XPDR first started supporting traffic info, in rented Cherokees ), so no panic, but it got annoying the 4th or 5th time it happened...

 

[swatson999]

Flew today, saw the same ghost traffic (i.e., myself), several times (this in an area in which I've flown *a lot* and never, to the best of my recollection, ever seen this).  Always when I had ADS-B OK and NO RADAR shown on the map display.

First time was, well, disconcerting, but I've seen ghosting before (as far back as when the Garmin XPDR first started supporting traffic info, in rented Cherokees ), so no panic, but it got annoying the 4th or 5th time it happened...

Well, at least it's repeatable...same area, different day, same problem (well, more of a distraction than a problem).

You mentioned that you spoke with the FAA about this...any feedback?

 

[jc2da]

This sounds like exactly my issue as well, in my other thread. TIS OK only traffic. Lots of false alarms with hits on myself. No resolution yet. Quite frustrating.

http://dynonavionics.com/cgi-bin/yabb2/YaBB.pl?num=1451071895

Was there any resolution to this? Is there an ADS-B outage or issue in my area possibly as well? Not sure how i would look this up.

 

[Garrett]

TIS has always had this problem since day one.

 

[Garrett]

TIS has always had this problem since day one. It does not matter who's equipment you use it is an FAA problem.

 

[swatson999]

I just don't recall this being such an issue before...this is the same area where I do a lot of flying, and until quite recently, I don't think I got a phantom traffic alert more than once a year. Now, it's virtually every flight in that same area at the same altitude...which leads me to believe it might be a V13 software problem??? Or just a coincidental issue with something changing on the FAA's side?

 

[Garrett]

I installed the 1st KT 73 transponder serial# 001 to put traffic on an MFD in 2002 and it intermittently saw it's own shadow. Discussed the problem with an engineer at Honeywell and was told it was an inherent problem on the FAA's ATC side of the system development was complete contractually and there were no intentions to address the issue just live with it. With the addition Dynon's ADB S the problem seems to be masked over. Over the years since TIS I have seen the problem on various other transponders. I fly in Florida and have not noticed any problems as described above with Dynon's SkyView lately.

 

[jc2da]

On darn phone. Yeah I am assuming if SV can't get adsb traffic, it falls back to TIS. At first I couldn't understand he ghosting issue but then realized adsb traffic was not on. Seems TIS is interior. However still trying to figure out why adsb traffic not taking over. Someone mentioned it was related to an adsb infrastructure problem. However nobody else complaining. Seems like its my local issue. Thus I'm still trying to debug my system. Next I need to borrow someone's stratus and see if that gets traffic fine.

 

[dynonsupport]

As it appears was figured out, "TIS OK" means you are using the TIS-A service from your transponder, not from ADS-B. This is totally different than ADS-B, and you can only use one at a time.

If you have Dynon's ADS-B reciever and transponder, but are seeing "TIS OK" then in most cases something is configured wrong, either in SkyView or on the FAA's ground station side. Knowing where you saw this in the world is very helpful.

If you don't have both our ADS-B IN and transponder, than "TIS OK" is expected. Yes, TIS-A gets a fair number of ghost targets when you go in and out of coverage or maneuver aggressively, and this is on the FAA's side and nothing we can do about it.

V13 has been out for a while and we haven't heard of any unusual number of traffic issues with it. The FAA always seems to be playing with the ADS-B system in various areas so there's a lot of coincidental situations with a software upgrade and another change.

 

[jc2da]

Ok, thanks for the detailed reply (also in the other thread). Yes, i do have have both Skyview ADS-B and XPNDR-261. This is for the SFO area. I haven't had time to test at KSQL which i believe is where our ADS-B signal is coming from. I will try to do that this week. I am hoping i can get the signal while on the ground. It will make fiddling so much easier on the ground, rather than while flying.

Everything had been working great for a year, and then all of a sudden it changed slightly. IE, "TIS Only." Very strange.

Thanks again for the updates.

 

[Dynon]

For those of you in NorCal that are seeing ADS-B issues, see this thread.