Three of the planes our airport just installed UAT. Two are uAvionix skyBeacons and one is a Garmin. According to one of the uAvionix owners his unit’s serial number is 1002137. Assuming uAvionix started at 100001, that’s over 2,000 units sold since December and they are not caught up on their backlog. Further, uAvionix expects to get FAA approval to ship their tailBeacon UAT unit this month. It will probably be as in-demand as the skyBeacon.
The deadline to install is 31 December. So I expect that those of you living near major terminals and larger airports will start seeing a lot more UAT traffic “real soon now”.
Does anyone know whether the FlightAware PiAaware update will display 978 UAT traffic on the same map as the 1090 traffic? I’ve looked around and cannot find anything about that. The ADSB Receiver project uses two independent maps which (as far I can can figure out) cannot be combined.
I hope to run a separate, 978, instance on a different computer, to see if it is worth the electricity (to me).
The separate computer is a BeagleBone Black, which used to be my primary PiAware agent, but I’ve switched to a Raspberry Pi 1B in a Wicked Aluminum Pi Holder, for the primary, because the BBB generates a lot of RFI. The BBB interferes with my 70 cm scanner.
The RPi 1B doesn’t seem to have the horsepower to run PiAware w/1090 & 978, but I could be incorrect.
Just wanted to catch up on the latest, does PiAware automatically detect and support 2 dongles in one Pi yet? One for 1090 and the other for 978? Hoping for a simple install / update and go without much manual tweaking.
Any idea when there will be native support for 978 UAT with both aircraft (1090 and 978) both being displayed on a single web page instance? Is this being worked on?
Erm, no I didn’t know. My instance doesn’t seem to have that file in /etc. (Which likely means I don’t have the tar1090 file. So I’m guessing maybe I’m on an earlier rev?? Here’s what my system reports:
pi@piaware** : **~ $** uname -a
Linux piaware 4.14.62-v7+ #1134 SMP Tue Aug 14 17:10:10 BST 2018 armv7l GNU/Linux
pi@piaware** : **~ $** piaware -v
3.8.1
So I’m guessing there is a bigger picture here that I’m missing