My v15.3.3 Issues

[jc2da]

I just did the update and just did a quick 30 min flight. Here are some issues i saw.

1. I still have the original ADSB-470 unit. I was getting really flakey ADS-B updates. Only getting TIS-OK up to 4,000 ft, when in the past, I would get ADSB OK starting around 2,000 ft. In fact, in the entire area, where I would normally get ADSB OK, I was only getting TIS-OK for almost the entire flight.

THe only time I saw ADSB-OK was a minute after take off and a minute before I landed. THe other 28 mins of flight time, was all on TIS-OK. No traffic that I would normally see.

Also, on the takeoff, I had the phantom target (myself). I would normally not get phantom self targets on flights like today.

2. My Fuel PSI was toggling back and forth between 26 and 27 psi. It was a very fast 100Hz or so flicker between the 2 numbers 6 to 7 to 6 to 7 to 6 to 7. I have never seen that kind of flickering before.

3. My Fuel Flow number was very low. Normally, I would see 10 to 12 GPH. Instead, I was seeing only 7 or 8 GPH or so. When sawing the mixture in and out, the numbers would not change or change very slowly from 7 or 8 GPH to 10 GPH. In the past if I did the same thing, I would typically see 7 or 8 GPH up to 16 or 18 GPH swings in time with the sawing motion on the Mixture control. It "felt" more real-time and accurate in the past. Now, it feels sluggish, inaccurate and not reflective of my real FF.

That is all i remember at the moment. Anybody else noticing these things? I wont be able to test again until the weekend, unfortunately.

Jae

 

[swatson999]

I've seen various sensors alternate between two values, though never at that high of a frequency, on a number of occasions. I always figured it was discretization error when the actual value is sitting right at halfway between the two display values...

 

[Dynon]

There aren't any changes to the areas you describe, especially if you were coming from a recent version of software (what version were you coming from?).

The ADS-B isn't likely to be related to the software, but one thing that's worth checking next time you fly is whether your transponder was squawking nominally. The TIS system is a bit more likely than ADS-B to produce self-phantom targets, so that's not terribly unexpected. Also note that ADS-B towers are known to have occasional outages. I'd keep an eye on this and see whether it persists, for now.

Fuel pressure hasn't really changed, although there should be some filtering on it. You might check whether you're running the most recent sensor definitions. If you downloaded the "method 1" package, you are. You can double check under the sensor debug page under ems setup.

For fuel flow, the first thing to check is whether your pulses/gallon setting is where you expect it to be. It shouldn't have changed unless you changed it though.

 

[jc2da]

Thanks for the reply. I did another short test flight today.

Everything worked normally this time, except for maybe possibly the ADS-B. I wasnt focused enough on it, but the last few minutes of flight were on TIS-OK mode again.

I will report again after a few more flights.

 

[Dynon101]

>I still have the original ADSB-470 unit...I had the phantom target (myself).

First time on a long-ish trip and I consistently got Phantom targets. The first indication was really worrisome because the target was directly behind me at my altitude. I made a left turn to let "him" pass but it followed me at a short distance mimicking my every move (but it was not an immediate reaction but slightly delayed). At first I thought it was some pilot out having fun and trying to fly in unannounced formation with me but I did not see any aircraft.

It happens numerous times at various altitudes altitudes during the 3 hour flight and was very annoying.

I have a Dynon transponder and 470 ADSB.

What can I do to fix/trouble shoot this?

 

[airguy]

>
What can I do to fix/trouble shoot this?

Upgrade to the new 472 model in place of the 470 and load the new software.

 

[NASA515]

I have persistent phantom targets and don't have ADS-B IN. Been a long standing problem and seems to be terrain related since it occurs a lot in the same area.

Bob Bogash
RV-12
N737G

 

[alexe]

Ok Bob, curiosity is getting the best of me. If you don’t have ADSB IN, what are you seeing the phantom targets on???

 

[CGameProgrammer]

He would still get TIS-A which is through the transponder.

 

[dlloyd]

jchang, I too have the 470 receiver. In the Charlotte, NC vicinity the display usually shows TIS-OK despite having several ADS-B towers in range. Back and forth several times with Dynon including a diagnostic file, they say it appears to be working normally.

 

[NASA515]

Ok Bob, curiosity is getting the best of me. If you don’t have ADSB IN, what are you seeing the phantom targets on???

You do get traffic advisories without ADS-B IN, you know - via TIS. Works quite well, just not as comprehensive in coverage.

Bob B.

 

[airguy]

Ok Bob, curiosity is getting the best of me. If you don’t have ADSB IN, what are you seeing the phantom targets on???

You do get traffic advisories without ADS-B IN, you know - via TIS.  Works quite well, just not as comprehensive in coverage.

Bob B.

"not as comprehensive in coverage" - that's an understatement! Out here in flyover country you can forget about it unless you want to head to the "big city".

 

[Dynon]

Actually, the TIS-A system is actually quite good. It provides a tailored portrait for your aircraft, that depicts the nearest aircraft that are a factor. There are times when it is elevated above partial ADS-B coverage because in some scenarios it is more comprehensive.