![uavionix.com](/community/proxy.php?image=https%3A%2F%2Fuavionix.com%2Fwp-content%2Fuploads%2F2020%2F03%2FuAvionix_Logo_Standard.png&hash=dee693ef7900660e992b8b7d3ff4e7b3&return_error=1)
Not really surprising to me as I sold mine years ago due to not having a wired altitude encoder and transponder connection. Credit to the manufacturers though for offering a free fix.
![]()
Not really surprising to me as I sold mine years ago due to not having a wired altitude encoder and transponder connection. Credit to the manufacturers though for offering a free fix.
Yeah, that was the problem I had from the start with the Echo-uat. It failed the performance report baro-alt category. The sniffers just don't have anything to sniff if the transponder isn't being pinged. So there are times we were in ads-b reception but not radar contact causing the failure rate. It would have been a non-issue had they included another serial port for altitude encoder data.Reports are that when flying in areas of little ADS-B coverage or places where the transponder is not often interrogated that there are periods of time where altitude reports are not frequent enough to satisfy the powers that be (read FAA) ...![]()
It would have been a non-issue had they included another serial port for altitude encoder data.
Waiting.Has anyone here received / installed their echoAlt?
I will go read those threads. Thanks for the find.few over on VAF seem to be having issues
Is there a reason why some are plumbing it into the static system? I realize it is easy and set up for it. But the directions don't require it.have some extra tubing for the static line
So it reports an altitude that is consistent with the Mode C and your altimeter.Is there a reason why some are plumbing it into the static system?