Navworx ADS-B

[gyoung]

Originally Posted by Jaws

Don,
How does one tell the difference in 1090 traffic direct broadcast, rebroadcast 1090 traffic, and 978 tower broadcast traffic on the display...it all looks the same to me, except on rare occasion I see an aircraft tail number attached.

The ones with tail numbers or flight numbers attached are direct broadcast from that aircraft. I don't know if there is a way to distinguish 1090 from 978 other than knowing airliners will all be on 1090.

[BobTurner]

If flight number or N number is attached that means the target is 'in the system'. It could be a direct ADSB-out broadcast (not in UAT 'cloaked' mode) or an ATC radar target where the N number has been added (IFR, flight following).

[AllThumbs]

I took another look at the GDL-90 spec and see no obvious way to tell if your traffic source transmitter is 978 or 1090 in the traffic msg (msg 20). Obviously, the receiver knows that info if it came in air-to-air instead of from a ground station.

One thing I'm curious about is if a Mode-S (not ADSB) transponder being re-broadcast as traffic from a ground station includes the N-number. Since part of mode S is the ICAO designator for the aircraft, this should be possible.

Also, I see no reason for any ADS-B re-transmitted traffic to not have the N-number. There's a field for that in the GDL-90 msg. I can't honestly remember if I've seen N-numbers for distant traffic or just obvious air-to-air traffic.

[DennisRhodes]

interesting, Ive seen several with N numbers but most without on my 600EXP. Although I purchased the 1098 along with the UAT bands, Im not sure it( the 1098 air to air) was ever installed. The 600EXP has been in service about 6 months now. The 1098 stuff was advertised as needing a software upgrade which I'm sure has not been done while in my hands. My understanding was that the UAT within ground based transmission range would have both traffic bands within that UAT data. But I have no idea how to identify one from the other.

[Billvt]

5.6.0 which is for the ADS600-EXP configures the box for 978 IN only.

I have the 1090 IN hardware option in my ADS600-EXP but the firmware to make it functional is not out as far as I know.

Last rumor I heard with regard to the 1090 IN was that the firmware for the EXP would be ready in June of this year and for the certified box in July. The rumor came from a fellow pilot who called Navworx and that is what he was told.

CORRECTION - the fellow pilot just informed me that November is the time frame for 1090 IN on the certified box.

We shall see.

[AllThumbs]

I'll follow up with Bill on the 1090-in support time-line. I'll report back when I get a definitive answer.

And, Bill, thanks again for your Onex panel fab a few years back. It turned out great for my friend here at KDVO.

[DennisRhodes]

Bill , Could that be November of 2016 on the 1090 software!! I still admire Navworx for the ability to get an excellent product out to the users in this day and time. I'm sure working with the authorities with a new product like this is a challenge. All of the features of the 600EXP are as advertised and looking forward to whenever the 1090 software becomes avail. Navworx has always been optimistic about their delivery dates, you just factor that in up front!

[bullojm1]

I tried to upgrade from 5.3.1 to 5.6.0. After the original load, I ran into the "NO GPS INPUT DETECTED" error. I erased the EEPROM and rebooted the box, and then all of the sudden it received the GPS input, however, the UAT wasn't fully configured due to the EEPROM being erased. I was able to put in my N-Number into the first configuration tab, and after a power cycle I could get a GPS signal. However, as soon as I changed any setting on the INPUT tab (Altitude Encoder or Transmitter Control Panel), the GPS would report back all 0's for LAT and LONG. The only time I can get the unit to fully work is after a EEPROM erase, I can enter in all of my pertinent information and it works...until I have to reboot the device and then it never gets GPS signal. I have loaded the new firmware at least 10 times from multiple different computers (Microsoft Surface and a Dell Laptop) to no effect.

I would warn people from upgrading to 5.6.0 until this bug has been worked out of the firmware. I will call Bill up Monday to get some support.

For the record, I am using a Garmin GTX327 as my Transmitter Control Panel type, and using the Shadin-Z Altitude encoding protocol at 9,600 bps.

[JBPILOT]

Downloaded 5.6 to laptop. Erased EPROM. Loaded 5.6. Input all required info. Got FAA report. Inputs only UAT. Outputs only UAT. Basically works ok EXCEPT - I still can not see a friends 1090ES plane. No idea why yet.

[MartySantic]

Originally Posted by bullojm1

I tried to upgrade from 5.3.1 to 5.6.0. After the original load, I ran into the "NO GPS INPUT DETECTED" error.

Mike, did you wait long enough for GPS lock? As I recall, it took close to 10 minutes the first time I configured my 600EXP.