I have some custom ports for feeders that are working fine for 1090, both off PiAware loads and one on the new ADSBX 1.28 load. I have manually verified that the 978 radio is receiving packets (both aircraft and local ADSB tower) via the advice at: https://www.adsbexchange.com/how-to-feed/adding-978-mhz-ads-b-capability-to-your-pipi2/ I am not seeing anything on my custom feeder port.. Ideas? Thanks ADSBX build 1.28 Blue and Orange FA dongles Pi3 output of ./check-setup.sh checking setup ============ altitude => <snip> longitude => <snip> latitude => <snip> custom port => 51402 dump => yes mlat => feed.adsbexchange.com:31090 reciever MLAT name => <snip> WIFI = <snip> SSID => <snip> PASSWORD => <snip> ENCRYPT => WPA MLAT-> yes DUMP1090 -> yes SHELLBOX -> yes BLUETOOTH -> no 978 UAT -> yes PORT 51403 CELLULAR -> no CPU temp=55'C GPU temp=55.8'C
So .. I need remote access to get 978 working on those images. 1.29 image improved the whole 978 lego blocks by creating a named pipe and adding monitoring
I can turn on remote on one of them and PM you the details. When does 1.29 drop to us and should we just wait until then?
I am 99.9% sure I am feeding 978 properly from a couple of sites. BUT, when I am looking at my feeder using the adsbx UUID link I do not see them. Where can I go to see the results from my 978 feeds?
I'll have merge it into dump1090 on the feeder. And we should update to the most recent uat code that uses named pipe do you have ZeroTier on them?
They might appear on tar1090.adsbexchange.com .. What the older image does is dump-978 -> uat2esnt -> adsbexchange.com 30005
I have Zerotier on all of them. Just let me know what packages I need to update and scripts to modify and I can get that done across all of them. I have been migrating them from PiAware to ADSBX 1.28 base code as I get to touch each one again.
A lot of us took the UAT 978 device path to compliance. I installed the uAvionix Tailbeacon, several other friends did the wingtip version. All are 978.
