I flew for first time the EchoUAT replacement units for the Navworx EXP. I did previously have my Navworx in service for 2 yrs and it worked flawlessly and got a perfect performance score when initially installed.
Worked through the Echo configuration process and think I have it correct.
I made the first test flight today in the Portland, OR area. Max altitude I could reach was 3500 ft due to weather, flight lasted 58 min. On the ground, ForeFlight was displaying traffic with no UAT tower reception. Airborne, it took about 15 min and above 2500 ft before receiving any ADSB towers, which varied from 1-3, sometimes none. Traffic and ADSB Status was being correctly displayed on my GRT Sport EFIS. During the flight I dropped down for two touch N Go?s then climbed back up 2000 ft. At 30 min into the flight I stared having Same Ship ghost returns, with my N# being displayed. Local ATC said my transponder signal was cutting in and out and something about a Mode 3A error. I rebooted both the Echo unit first and ghosting returned, then the GTX 327, afterward which ATC said everything returned normal, AND the ghosting stopped for the remainder of the flight.
I don?t know if the EchoUAT did something to the GTX327 (it?s serial data line is hard wired to EchoUAT) to make it become erratic or just the 327 went on the blink until rebooting it.
My performance report failed.... (Mode 3A / Flight Id / BaroAlt) probably because I down powered the transponder to reboot it. Everything else in the report is clean. Currently frustrated given the Navworx work fine.....