UAvionix ?failed to generate report? cause

[BobTurner]

Yes, it should show pressure altitude and squawk code. If you are hard wired to your transponder, something is wrong - maybe the baud rates or format. If your UAT ?sniffs? this data wirelessly, you may need to lower the threshold sensitivity in the UAT setup.

[alpinelakespilot2000]

Originally Posted by BobTurner

Yes, it should show pressure altitude and squawk code. If you are hard wired to your transponder, something is wrong - maybe the baud rates or format. If your UAT ‘sniffs’ this data wirelessly, you may need to lower the threshold sensitivity in the UAT setup.

Thanks Bob. Yes, it is the latter. No hardwire. If I recall correctly my threshold sensitivity default from the factory was pretty high compared to what other threads indicated theirs needed to be lowered to in order to get good reports. I just wasn’t aware that the sensitivity setting might prevent me from getting a report period. No harm in trying that though as it makes sense that the echo is just not reading the transponder very well. Thanks for the suggestion.

[RobertD]

I posted this in another thread today but it sure seems like the way to do it to me:
I wasn't getting anything in the baro alt line so Uavionix said to start pretty high and reduce the threshold number by 50-75 at a time and watch the monitor on the app to see when something shows up in baro alt. So I started at 1500 and reduced it as instructed every couple of minutes until the baro alt showed up. It dropped out so I reduced it a time or two more until it stabilized.
This method seems way better than setting a threshold number, going for a flight, running a report, then repeating the process. The monitor function in the app gives more or less instant results for any changes you make in configuration.

[alpinelakespilot2000]

Originally Posted by RobertD

I posted this in another thread today but it sure seems like the way to do it to me:
I wasn't getting anything in the baro alt line so Uavionix said to start pretty high and reduce the threshold number by 50-75 at a time and watch the monitor on the app to see when something shows up in baro alt. So I started at 1500 and reduced it as instructed every couple of minutes until the baro alt showed up. It dropped out so I reduced it a time or two more until it stabilized.
This method seems way better than setting a threshold number, going for a flight, running a report, then repeating the process. The monitor function in the app gives more or less instant results for any changes you make in configuration.

Did you do this in flight or on the ground, Robert?

I just went back out and changed mine from the about 1500 default down to 1350 on the ground. Almost immediately this gave me both baro alt and squawk on the echo app monitor while on the ground. I then went and flew and found two things:

1. I still wasn't being picked up by ATC with ADS-B out data. Moreover, I wasn't being picked up by other aircraft anymore apprently.
2. As I got higher, baro alt and squawk showed up even when I switched back to 1500. However, when I started descending again, I needed to go back down on the threshold (ended up/picked 1350) for both to show up when I was nearing pattern altitude or below.

Not sure what all this tells me, except that a call/email to UAvionix to make sure every single configuration setting is as it should be for my equipment set-up is in order. A bit frustrating, but I've heard their customer support is good, so fingers crossed.

[N941WR]

A friend installed one of these in his high wing and flew the test and, like the OP, didn't get any results.

Turns out he installed it on the right wing and made turns to the left.

When he went up for the second test hop, he made turns to the right and received a report.

He mentioned that he had heard of similar results from others.

I have not idea if this is true or not, but I trust the guy who told me the story.

It would be nice to verify this is possible.

[RobertD]

Originally Posted by alpinelakespilot2000

Did you do this in flight or on the ground, Robert?

absolutely in the air. that was what was cool about it. I could lower the threshold through the config menu and then switch to the monitor and see the result. Kept lowering until the baro alt came alive and then until it stabilized.
There's apparently a tower very near SCR and I had coverage (with a baro alt reading) even as I taxied back to the hangar.

[DNeufeld]

Below is right from the horse's mouth... Uavionix web site.

Adjusting the threshold value on the echoUAT can improve the performance of the transponder monitor. uAvionix does not recommend changing the value unless directed to do so by uAvionix.

The threshold value adjusts the sensitivity of the echoUAT transponder monitor. Higher values reduce sensitivity, lower values increase sensitivity.

To modify the threshold value perform the following steps:


1. Turn the avionics master on.

2. Place the Transponder in "ALT" mode.

3. Connect a mobile device to the echoUAT Wi-Fi.

4. Open the echo mobile application.

5. Verify the app shows "Connected to Device"



6. Tap two fingers simultaneously on the echo logo.


7. Scroll to the bottom of the app screen and find the Transponder Threshold values.


8. Lower the Transponder Threshold by 50 points and press Update Advanced.

9. Switch to the Monitor screen and watch for pressure altitude and squawk.
Please note transponder must be receiving radar interrogations for the fields to populate and this is usually best done while flying. Most transponders have a reply light or indicator.
Note Mode S does not reply with pressure altitude in a ground state.

10. When the appropriate threshold has been reached the Squawk and Pressure altitude will display. Repeat 8 & 9 until ALL fields are showing data



11. Values lower than 1000 should not be used..

If you are still having difficulty and cannot get a reliable/stable readout please contact support@uavionix.com

[alpinelakespilot2000]

Thank you. Do you have the weblink for that? I looked all over their site unsuccessfully even though it was probably right in front of me.

Originally Posted by DNeufeld

Below is right from the horse's mouth... Uavionix web site.

Adjusting the threshold value on the echoUAT can improve the performance of the transponder monitor. uAvionix does not recommend changing the value unless directed to do so by uAvionix.

The threshold value adjusts the sensitivity of the echoUAT transponder monitor. Higher values reduce sensitivity, lower values increase sensitivity.

To modify the threshold value perform the following steps:


1. Turn the avionics master on.

2. Place the Transponder in "ALT" mode.

3. Connect a mobile device to the echoUAT Wi-Fi.

4. Open the echo mobile application.

5. Verify the app shows "Connected to Device"



6. Tap two fingers simultaneously on the echo logo.


7. Scroll to the bottom of the app screen and find the Transponder Threshold values.


8. Lower the Transponder Threshold by 50 points and press Update Advanced.

9. Switch to the Monitor screen and watch for pressure altitude and squawk.
Please note transponder must be receiving radar interrogations for the fields to populate and this is usually best done while flying. Most transponders have a reply light or indicator.
Note Mode S does not reply with pressure altitude in a ground state.

10. When the appropriate threshold has been reached the Squawk and Pressure altitude will display. Repeat 8 & 9 until ALL fields are showing data



11. Values lower than 1000 should not be used..

If you are still having difficulty and cannot get a reliable/stable readout please contact support@uavionix.com

[Saber25]

I'm wondering, with all these pilots flying around and being inside fiddling with avionics, is anyone on board to maintain a lookout for traffic? Wouldn't it be ironic to cause a mid-air while having these ADS-B adventures and discoveries.

[PCHunt]

My understanding is that a "bad"Transponder Threshold setting should NOT result in a "No Report". You would get a report, but there would be failures (Red Boxes).

A "No Report" means that the system never saw anything that was attached to your N-number.

This can be caused by being in the "anonymous" mode. [In the App, make sure that the anonymous mode is DISABLED.] Or by having an incorrect ICAO Hex code programmed. Or by an incorrect N-number programmed. Or by no power to the uAvionix unit.

Before you do a test flight, make sure that the APP is properly responding to the ADSB out signals on the ground.

Also, as you mentioned, make sure the UTC date is correct. Try a date one day before, and one day after your flight.

Hope this helps