ECHOUAT mandatory service bulletin

I wonder how big the encoder will be.
 
I wonder how big the encoder will be.

Photo from the above page:

1702701612294.png

Appears it will have to be tapped into the pitot static system. Don't seem like a big job.
 
Last edited:
From another site a poster states having contacted uAvionix and learned that the encoder will daisy-chain via a connector into the EchoUAT. Not sure whether what appears to be a static port needs to be connected to the static system or left open inside the fuse (alt static source) as many of us have the Echo units mounted far away from the panel.

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) ... :dunno:
 
Last edited:
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) ... :dunno:
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.
 
It would have been a non-issue had they included another serial port for altitude encoder data.

Agreed. I've looked at just taking their encoder and adding it but on the other hand, I've been wanting to install an AV30-E and they have a pretty good bundle going on with that and the TailbeaconX together. Doing so would mean I could lose the weight of the Garmin 320A, the encoder, and two belly antennas. Decisions ... :dunno:
 
Has anyone here received / installed their echoAlt?
I filled out the form in January and am still waiting for my echoAlt to be shipped.
Looks like they started shipping in April or possibly mid-May.
They've been good with the email updates, and I noticed the echoUAT is no longer on the uAvionix site.
 
I assume if you are waiting for the echoALT, you got the same email, but on the off chance...

"This month at EAA AirVenture, uAvionix is offering the chance to pick up your echoALT and receive hands-on training on how to complete the installation and updates right at the event!"

"let us know ASAP if you would like to take advantage of this opportunity. Simply fill out the Google Form linked below to indicate your interest in picking up your echoALT at AirVenture."

"Please note: if you're not planning to pickup, estimated delivery time for your echoALT is 4-6 months"
 
Mine showed up in the mail today. It looks like a simple enough install.
 
A few over on VAF seem to be having issues with the add on baro units. I have the Echo ADS-B but opted to update to the TailbeaconX & AV30E ... yet to be installed.
 
Software updates went off without a hitch. Followed the instructions exactly.
Plugged in the encoder and I get both the gps and baro altitudes from the unit on the Android app.
EchoUAT remembered the N number and stuff originally programmed into it.
It does take both an android app and a winders PC to do the whole thing.
The static port takes a 1/4 inch OD tube.
The jumper harness is pretty short - so unless you want to do some cutting and splicing, the encoder will need to be pretty close to the EchoUAT.

Have not flown it yet to get the PPAR (or whatever the initials are) report.
 
Mine arrived yesterday. Don’t know when I’ll install it; I realized too late that have some extra tubing for the static line, but I don’t have a tee.
 
have some extra tubing for the static line
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.

I haven't installed mine just yet.
 
As far as plumbing it into the static system. The EcholAlt installation instructions say this.

"Like skyBeacon and tailBeacon, echoALT
continuously calibrates to the aircraft transponder’s altitude encoder,
therefore, echoALT does not require bi-annual correspondence checks."

I suspect it doesn't need to be tied in. The instructions don't mention doing it. It cant hurt to do it, but I may see if UAvionix will clarify.
 
Back
Top