UAvionix Echo

[jselvatici]

Thanks for the feedback. Will work on mine in few months.

[Eddie P]

I wanted to thank the guys who have posted here. It helped me prepare for my Echo test flights.

It took me 3 test flights to dial my unit in and one call to Uavionix tech support. Lessons learned for me:

1) Follow the guidance int he manual, it's pretty good to a point. So in other words page 20-25 using the app and making sure the initial settings are in, and for me, page 34, because I'm using the simple "Legacy Transponder" setup and this page is the "application note" to set some of the remaining app settings.
2) The manual does not cover the "advanced setup" mode. More on this in a second.
3) Pull the airplane out of the hangar so the GPS can get a good lock and turn on the systems you have required to power up the Echo box (for me it's just my battery and avionics switch).
4) In your phone, make sure the wireless network "pingxxx" is chosen. No worries that your phone may show "! no internet" on the ping network. ADSB never gives internet, just ADSB, so that's by design.
5) Now open your Echo app that you downloaded previously, per the instructions on page 20.
6) You see "setup" and "monitor". Once your app connects to the Echo, you'll see some figures populate in the monitor page. Page 21-24 will walk you through some of the settings (and a visit to FAA.gov to look at your registration with your custom aircraft Mode S code). The displayed values (or not displayed as it was for me) that seem to be the types that may not populate in your "monitor" page, are the "Squawk" and "Altitude, Pressure". If these are blank, that means you have to change your transponder threshold. The only way into that setting is in your advanced configuration menu.
7) To get to the advances menu, go to "configuration". Then use 2 fingers to tap on the "echo" logo on the top of the page. Then scroll down and you'll now see input fields for transponder threshold. Don't change any of the other ones.
8) This setting starts at a higher value than would work for me. IOW, I had to lower mine to 1050 for the unit to work best. I lowered my setting 100 at a time until the transponder code showed along with the pressure altitude. Now, just because it shows does not mean it will pass a flight test yet. You'll notice you can adjust the settings and "send" the settings to the Echo. And there is a range where those settings will still show transponder codes and pressure altitude. But as said already, it's like tuning a FM radio with a dial. The settings along the high water mark and the low end, that display the code and altitude, are on the edge of working properly.
9) Bracket the values that work, and then pick a value in the middle. You can use numbers finer than 100 at this point. For example, 900 was too low - not showing values in the app. 1000 was ok on the low end, and 1125 was ok. But both of those values were the edges of the transponder reception by the Echo. when I'd change my transponder code to 1201, the app did not register it right away. At a range of 1025 to 1075, any code changes showed up right away in the app. I split the difference and used 1050 for my last flight, and then flew. Got a pass with all perfect scores at transponder threshold of 1050.
10) I flew two failed test flights early on not realizing the value of "fine ground tuning the system". And by the way, when I was ground tuning, I did not have my engine running yet. I was just using battery and avionics switch on. And no not for long, the exercise took about 3 minutes once I figured out how to "tune" the system quickly using the app. If it took longer I might have started up. Knowing what I know now I am sure I could tune one of these and probably pass on the first flight.
11) This is just my experience. There may in fact be far better ways to do it. I also want to thank David Wagner at Uavionix for talking me through some of this, especially the ground tuning trick.
12) Dave wants to remind everyone once you get a "pass" on your check (no red boxes) be sure to sign off your ADSB installation and also state the installation and test flight was IAW 91.225 and 91.227 and the date of the test pass. Print off the test pass and keep it in your records "just in case".

All the best guys, fly safe.

[RWoodard]

I installed an echoUAT along with a skyFYX external GPS source in my RV-3 over the last day or two. I had planned to have a complete G3x system installed by now, but things keep getting in the way and I?m never excited about taking it out of service for any length of time. I installed the uAvionix solution in such a way that it is easily removable if/when I get around to doing the Garmin system.

I found this and other similar threads to be extremely useful when it came time to tweak my settings. I received 2 red boxes on my first PAPR report yesterday... 100% failure in the Mode 3A and Baro Alt boxes.

Thanks to those who?ve blazed the trail ahead of me, I figured I needed to adjust my transponder threshold setting. I did that (ended up at 1125), and received a passing PAPR report on the next flight. In fact the second report shows 0.00% failure rate in every box. Woo, hoo.

The ADSB in works great, too. It seems to show more traffic and a stronger signal than my Stratux box ever did. It?s also really nice to have everything hardwired and more or less hidden. It?ll even be cooler when I install the G3x system so I won?t have to display traffic on my iPhone!

[jliltd]

Originally Posted by RWoodard

I installed the uAvionix solution in such a way that it is easily removable if/when I get around to doing the Garmin system.

Rod. No need at all for that. Your Echo will still be viable with yout G3X system! Leave it installed and working and then add a GDL 5x or 5xR ADS B "in" to the G3X install. I did this in my RV-3B and it works excellent. So for less than $1K you get more than most any other airframe. You will have the Garmin equipment covered by the GDL 5x ADS-B "in" data. That includes G3X and any Garmin portables or on Pilot app a tablet and/or cell phone. Meanwhile, you will have the Echo feeding ADS-B "in" data to any other portable, tablet, phone or app on the planet not made by Garmin. There is nothing saying you can't have two independent "in" systems on the aircraft and your Echo investment stays intact. Cheap, redundant and your airplane plays well with all equipment.

As an aside I would suggest installing the G3X GDU screen without built-in Sirius XM. Save that dough and then go for the GDL 52(or R) which has SXM music and weather on top of ADS-B weather and traffic with attitude. I used the portable non-R GDL 52 so I can swap between airplanes with one SXM subscription. I use external antenna for the GDL 52.

[RWoodard]

The echoUAT already provides in and out. No need for a GDL. The Garmin systems I?m considering will provide in and out without a separate box.

I?m just looking forward to having an integrated system. Not too worried about redundancy for ADSB in or out.

[gmohr]

Originally Posted by Skysailor

The setup options on the Echo are required. I have installed several of these for friends and can help. I'm on the Falcon RV email list. You can email me there, here or just PM. I'm local as well.

Maj

I am getting ready to install my EchoUAT today and just realized that I need a
cable to go from the short one provided to the antenna. Can someone please
tell me what connectors I need and/or where to order a cable from. I probably
need about 5-6 feet.

Thanks.

[RWoodard]

Originally Posted by gmohr

I am getting ready to install my EchoUAT today and just realized that I need a
cable to go from the short one provided to the antenna. Can someone please
tell me what connectors I need and/or where to order a cable from. I probably
need about 5-6 feet.

Thanks.

I?m thinking you?re talking about a cable to go from the short adapter from the UAT box to the stubby transponder-like antenna for the ADS-B in. If that?s the case, you?re looking for coax with BNC ends. Personally, I used RG400 coax because that?s what I had available in my workshop. The installation manual has a chart showing various flavors of coax along with the lengths permitted to stay below the maximum acceptable signal loss.

It?s not a huge deal to squeeze BNC connectors on coax, but it does require the correct crimping tool. If you don?t have easy access to the correct tool or the wire, I understand that Aircraft Spruce will make custom coax cables to your specification and length.

Hope this helps.

[flyer46]

connector
https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1

Cable:
https://www.amazon.com/Eightwood-Dou...7607844&sr=8-2

This assumes you have the proper crimp tool.
Here is the Amphenol assy sheet, showing the proper strip lengths and die sizes for the center pin and the outer collar:
https://www.amphenolrf.com/downloads...er_drawing.pdf

Note instruction 5C in the Amphenol sheet. The cable will bottom in the connector with a slight "click". Make sure it bottoms fully so the center pin is correctly seated before crimping the outer collar.

[CAVU Mark]

12/21 my first performance flight. All passed expect ICAO code which I transposed. XPNDR Threshold at default 1550, BARO ALT passed.
12/29 second flight with corrected ICAO code. Failed BARO ALT.
12/29 Email FAA and ask for manual review. They responded Monday! and said error was FID mismatch. Set FID to N number and all good. Can't find FID setting, FAA documentation says if VFR don't worry about FID.. whatever that is? Flight ID is best guess which will not accept an N number.
12/31 third flight with threshold at 1100 and still failed BARO ALT.

Two weeks ago I asked FSDO what to do if PAPR is after Jan 1. They said don't worry about it and maybe call ATC and tell them what is going on.

Great. Anyone know where FID is in the menu? Hidden, visible, or ?

[BH1166]

Originally Posted by CAVU Mark

12/31 third flight with threshold at 1100 and still failed BARO ALT.

Great. Anyone know where FID is in the menu? Hidden, visible, or ?

Flight I?d is NOT used. Using the echo setup app, it is in the middle of screen. No matter what you have heard, crank the threshold down as needed. Pull your plane outside, fire up the panel. If you can get interrogation replies (light flashes as in most transponders), using setup app enter 900 in threshold, save and update. Using echo app, go to monitor page and verify you see 1200 and pressure altitude. If so you should be good for another quick flight and report. You can play around with threshold by bumping it up by say 25-50 and see if all is good with same ground check. Probably good to only set as low as needed for a good report. EchoUAT is sniffing the electrical system for a specific micro voltage emitted from you transponder that carries your squawk 1200 and pressure altitude.