kbehrent
Well Known Member
I have the ADS600-B transceiver that it has functioned really well connected to one of my AFS 4500 screens. I just updated the firmware on the ADS600B to 3.12.5 in order to display the N numbers for ADSB traffic that AFS now supports the displaying of.
Since upgrading the firmware, the UAT Fail annunciator is getting momentarily set (on for a couple of secs, than off) every few minutes or so. Navworx's provide this annunciator connection in case you want to drive a annunciator lamp to signal a failed condition. I have mine connected to the 4500 so I get a warning msg.
I am still getting traffic and it appears I still get wx, although I've only been able to confirm that I receive metars since we've been having incredible clear skies for the Pacific NW..
Has anyone else had this issue? Anyway to find our what is causing the failed condition? I could easily just connect the light, but since it hasn't done this before, I would like to know why it's doing it now. I've been trying to reach Bill over the last few days and have not been successful contacting him.
Thanks,
Kevin
Since upgrading the firmware, the UAT Fail annunciator is getting momentarily set (on for a couple of secs, than off) every few minutes or so. Navworx's provide this annunciator connection in case you want to drive a annunciator lamp to signal a failed condition. I have mine connected to the 4500 so I get a warning msg.
I am still getting traffic and it appears I still get wx, although I've only been able to confirm that I receive metars since we've been having incredible clear skies for the Pacific NW..
Has anyone else had this issue? Anyway to find our what is causing the failed condition? I could easily just connect the light, but since it hasn't done this before, I would like to know why it's doing it now. I've been trying to reach Bill over the last few days and have not been successful contacting him.
Thanks,
Kevin