ADSB "OK" and WX Radar/NEXRAD

[Swaflyer737]

Since, updating to 16.4.4 and 16.5 most recently, I have had little success with ADSB-OK. It is either ADS-B "NO RADAR" or TIS OK. I seldom get WX RADAR, and once in awhile I can get some airport information, but it is sporadic. Contrast this with my Stratus and Ipad at same time I am getting most everything. I have latest update on 472, and have completely checked every wire, connection, and obviously Serial port set up and messages.......all appear to be OK.
I am using a Dynon Transponder and IFD540 WAAS GPS.

Last piece of information, I flew to Oshkosh and regularly fly in Central Georgia where I have had excellent coverage in the past with NEXRAD updating sometimes every 2 minutes. Now I will be lucky to see a NEXRAD or any WX Radar update once in a 2 hour flight.

Any ideas. Thanks

Bryan
Lancair Legacy

 

[Swaflyer737]

Trying to get a little input here. Is anyone having this problem? 3 guys on my field with similar setup is having this issue. Just flew to Colorado and got ADSB OK for 2-3 minutes.........that's it. No WX, No Nexrad, just ADSB NO RADAR OR TIS OK. Talked with Tech support and they are aware and working on Software, but I am surprised I have not seen much about this issue. Thanks, just was to know we aren't an anomaly here in Georgia.

 

[Rhino]

Just guessing here, but the software issue you mention might only affect the IFD 540, which could be why you haven't seen much here. The fact that not everyone will have updated to the latest software versions may also come into play. In the meantime, try going to the transponder setup and turning off TIS traffic. TIS takes preference over ADS-B, and some users have reported it actually prevents ADS-B sometimes.

 

[ned]

I am also having a intermittent issue with ADSB in. I have the SV-ADSB-470 installed for 6 years with no issues until recently. ADSB status will always show receiving when the ADSB NO RADAR issue arises. Targets disappear during wig out. happens at various altitudes. The issue has even occurred in class B airspace. I have already shut off TIS in setup.

 

[skysailor]

Do you have a non Dynon transponder? Support told me my display will always show "ADSB No Radar" because I run a Mode C transponder but my ADSB 472 shows traffic and weather continuously.

 

[Acrosmoke]

I’m having a similar issue. No ADS-B in, no weather. I did see a target for a few seconds but it vanished. I can’t find a loose wire or cable. Any ideas?

 

[Rhino]

You could check for pushed pins. You might also try turning off TIS. Sometimes it interferes with ADS-B.

 

[skysailor]

Acrosmoke, did you check the weather layer is selected on? It is under the Screen menu.

 

[Swaflyer737]

Sorry just getting back to responding. First thanks to Rhino who has always been responsive and knowledgeable to our issues. I can tell you all suggestions here have been done prior to my original post. Spoke with Tech support last week and have been told this is a known issue and that a software update is in works. Class B seems to be one of the main culprits in the issue. I operate under the veil in Atlanta. I have checked all my wires and 472 light sequences to proper operation. I was told to standby and not start sending things back or rewire anything. Waiting for software update. I will keep you all posted if anything changes.

I want to be clear and answer Rhinos first response. I have had no issues with ADSB out, which my IFD540 WAAS feeds my Dynon Transponder.

Thank you all for responses and participation.

 

[RexBrewer]

please clarify:

1. what causes “ADS-B NO RADAR” to display? note that radar image is present and NEXRAD RGNL & NEXRAD CONUS have AGE : 00:10 or less.

2. Is my SV-ADSB-470 (978 MHz only) displaying all traffic? with TIS on? with TIS off?

3. my DYNON WiFi dongle is sending AHRS data and I am unsure about other ADSB data to ForeFlight/iPad, but traffic has stopped showing on iPad, why? (did not changeTIS, it was & is off)? I see Rhino explained TIS off prevents TIS from having priority over ADSB in, but isn’t this a DYNON safety/software issue? (Yes eyeballs are primary collision avoidance tool)

thanks!

 

[skysailor]

Do you have the Dynon transponder? My guess is you do not as your squawk is not displayed but you may have chosen not to display it. Dynon Support told me I would always see "ADSB NO RADAR" unless using a Dynon transponder. They confirmed I am still getting all weather and traffic and that message was normal for any system without the Dynon transponder. I prefer not to use Mode S for security reasons so I always have the message. My ADSB out is supplied by a Uavionix Echo transceiver.

 

[RexBrewer]

I have a DYNON transponder. It is displayed (1200G) at the top of the SVscreen in the picture.

Thanks for the info.

 

[skysailor]

II see that now. I missed it before. Calling Dynon Support directly might be the best answer. They are very good and quite responsive.

 

[Acrosmoke]

Follow up on my issue. It was a bad antenna. Those stubby antennas are very fridges and i found i could turn the post. Replaced it and all is good now. Thanks everyone.

 

[Rhino]

Thanks for coming back and reporting the fix.

 

[IntAvTech]

It should be noted that simply being able to turn the post on a "ball and stick" antenna is, in itself, not necessarily and indicator of failure. It's a simple rod antenna in an insulator sleeve. The ones Dynon provides are splined to index with the plastic but I can easily turn the brand new one I'm holding right now.
So long as it's not shorted and the BNC male pin is making good contact with the contact at the end (you almost don't even need the ground plane on an antenna operating at this frequency), it should be fine.
Not saying the antenna wasn't the problem here, just that you shouldn't be too concerned if your radiating element can be rotated.

 

[Bob Y]

To add to the point, I pull my ADS-B and xponder antennas out from the base when I clean the soot from my aircraft’s belly.

 

[bruceh]

I have been seeing similar issues lately. I used to consistently see ADS-B OK, and lots of traffic (SoCal area). In the past year it seems as though now in the same areas I only see TIS OK. Yesterday I flew up to Corona for an Aircraft Spruce will call pickup. Along the way I hardly saw any traffic on the display. However, my iPhone running Foreflight, was picking up lots of traffic via the SV Wifi dongle (typical for the area on a clear day). I had the autopilot flying, so I went into all of the ADS-B menu/settings and saw that it was receiving just fine, BUT it said the device was the ADS-B 470! I had replaced the 470 with the 472 years ago. I went into the serial data settings and was able to change the device to the 472. It didn't make much difference on the display of traffic, but it again was showing up just fine on the iPhone with Foreflight. The menu mentioned that a 472 firmware update was available. I guess I'll try to get that updated. I'm running the latest 16.5.2 SV. Also, I have a Delta Pop blade antenna for the ADSB, so no worry about the antenna being loose. The wiring is fine, as it has been for the last 9 years of flying.

My guess is that at some point the FW changes between the 470 and 472 have contributed to this lack of traffic display?

 

[Albee]

Do you have the Dynon transponder? My guess is you do not as your squawk is not displayed but you may have chosen not to display it. Dynon Support told me I would always see "ADSB NO RADAR" unless using a Dynon transponder. They confirmed I am still getting all weather and traffic and that message was normal for any system without the Dynon transponder. I prefer not to use Mode S for security reasons so I always have the message. My ADSB out is supplied by a Uavionix Echo transceiver.

I don't have a Dynon transponder (GTX327 & GDL82) and I get "ADSB RADAR OK" routinely.

 

[IntAvTech]

Also, I have a Delta Pop blade antenna for the ADSB, so no worry about the antenna being loose.

Our experience has been that the blade-style L-band antenna have worse bandwidth and are more susceptible to RFI because of groundplane issues that aren't present in the ball-and-stick style. It's now our first move when trying to eliminate clicking noises in the headset on TPX reply to simply replace the blade antenna with a post-style. It's usually the last move as well, because the blade antenna so often turns out to be the culprit.
While the firmware thing could definitely be an issue, and there's no promise that the blade antenna on your aircraft is problematic at all, don't be fooled into thinking that the blades are more reliable or perform better. They generally do not.