Weird scenario, but here goes.
Equipment: AFS 5000 EFIS, with a Trig 22 transponder.
Had a Dynon ADSB-472 installed in Jan--traffic icons then displayed normally on the EFIS and weather information populated in the right places. (Turns out the ADSB installation generated another problem not worth going into here, but it led to the next step...)
Fast forward to last week, when I had dual ADAHRs (Dynon 200 and 201) installed. The avionics tech kept the Dynon ADSB input on the same EFIS serial port from before.
Now I get METAR and TAF info on the EFIS, but the map display will show traffic icons for about 30-45 seconds, and then (like Kaizer Sozè) poof...they all vanish from the screen. Fast forward a couple of minutes and they'll reappear, only to disappear 30 to 45 seconds later. It's not their range--they are far closer than the 15 nm cutoff range. And the aircraft are still out there, as verified on my iPad powered by another ADSB-In source.
My friend Jonathan at AFS is stumped. Any ideas from the brain trust?
Equipment: AFS 5000 EFIS, with a Trig 22 transponder.
Had a Dynon ADSB-472 installed in Jan--traffic icons then displayed normally on the EFIS and weather information populated in the right places. (Turns out the ADSB installation generated another problem not worth going into here, but it led to the next step...)
Fast forward to last week, when I had dual ADAHRs (Dynon 200 and 201) installed. The avionics tech kept the Dynon ADSB input on the same EFIS serial port from before.
Now I get METAR and TAF info on the EFIS, but the map display will show traffic icons for about 30-45 seconds, and then (like Kaizer Sozè) poof...they all vanish from the screen. Fast forward a couple of minutes and they'll reappear, only to disappear 30 to 45 seconds later. It's not their range--they are far closer than the 15 nm cutoff range. And the aircraft are still out there, as verified on my iPad powered by another ADSB-In source.
My friend Jonathan at AFS is stumped. Any ideas from the brain trust?
