I’m not sure it matters, but could you recommend not using 0 and 1 as serials?
With dump1090-fa being able to use the device index as well as the serial number that can lead to problems.
Just using anything but 0 and 1 should be fine with two dongles. But using 0 or 1 can be ambiguous.
Also when stopping dump1090-fa you should always stop piaware, it will restart dump1090-fa otherwise.
Hmmmm. Dusting off my 978 gear. Appears it has been unplugged for a bit and I didn’t notice. Looking forward to testing the new 3.7.0 SD image when it arrives.
Cheers!
Lit
Yes, I have also realized recently that using 1 & 0 as serial number will create confusion as these are used as device numbers also. If you see my posts above, I have used serial numbers 00000011, 00000012 in one case (RPI) and 00000101, 00000102 in another case (Debian on VM).
One more thing. Assigning two or three digit serial to eeprom of dongle has caused corruption of serial number in one of my Pro Sticks. It is recommended to assign an eight digit number like 00000013 or 00000104 instead of simply 3 and 4 or 13 and 104.
I did want to update the “how to” to accomodate these points, but unfortunately the current Discourse format does NOT allow editing a post older than say a month or so. 
I thought it was two month and it would still be within the timeframe. Hmmm.
Edit: welcome to 2019 wiedehopf! (the post is dated Feb 18)
Good morning, I could use a bit of help / clarification as i am setting up a new separate pi with only 978 capability. Here is where i am at and what I need some help with ( I am pretty light on Linux so have patience please with me)
Now what I need help with is how to connect Dump978-FA output into either dump1090-fa ( so I can use the dump1090-fa map - if that is possible, or just push it to pi-aware directly.
I am a bit confused as to the communications architecture between these 3 applications
I have tried to keep this setup as simple as possible
Any assistance is appreciated and thank you.
ESCOD
● dump978-fa.service - dump978 ADS-B UAT receiver
Loaded: loaded (/lib/systemd/system/dump978-fa.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-04-04 02:33:32 UTC; 9h ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 1032 (dump978-fa)
CGroup: /system.slice/dump978-fa.service
└─1032 /usr/bin/dump978-fa --sdr driver=rtlsdr --format CS8 --raw-port 30978 --j
dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor preset: enabled
Active: active (running) since Thu 2019-04-04 02:32:23 UTC; 9h ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 984 (dump1090-fa)
CGroup: /system.slice/dump1090-fa.service
└─984 /usr/bin/dump1090-fa --net-only --net-bo-port 0 --fix --max-range 360 --ne
The release has been announced for tomorrow so until then you can’t feed with piaware 3.7.0
And dump978-fa produces UAT format which the current piaware doesn’t understand, so you should wait for the release.
When compiling dump978-fa as a package, the skyview978-fa package is created as well.
That provides the map for dump978-fa, just install the skyview978-fa .deb package.
(The map is then reachable at http://pi/skyview978/)
This will not work, 30978 is producing UAT format messages, piaware 3.6.3 does not have the code to interpret those.
Oh i somehow suspected something along those lines.
The old setups somehow translated the messages?
The old custom setups used uat2esnt to turn UAT messages into 1090ES-format TIS-B messages (and necessarily lost some detail along the way)
3.7.0 interprets the UAT messages directly.
I suppose that could still be used to put the data into a dump1090-fa if someone wants a combined map?
That particular dump1090-fa instance should of course then not be used to feed, just for display purposes.
If you want UAT978 ONLY:
dump978-fa_3.7.0.deb AND skyview978_3.7.0.deb packages.NOTE:
If you want only local UAT978 map, and dont want to feed Flightaware, then you can skip building and installing Piaware package from source code. Just clone dump978-fa source code, and build & install dump978-fa + skyview978
As always, my impatient self won out and I couldn’t wait till tomorrow for the SD card image. Did an initial build following @abcd567’s initial build sequence. Everything came up fine on 1090, even though this is my 978 feeder. 
Now I just need to shut down the 1090, build 978, and fire that up.
Cheers!
LitterBug
@LitterBug
When you will clone source code of dump978-fa, and build the package, it will built two packages
Install both.
https://discussions.flightaware.com/t/version-3-7-0-of-dump1090-fa-piaware/47874/51
Currently roughly the same targets with the “new” version, with a slightly inferior dongle. . .
[EDITED]
Still see people above 18,000 on uat including this Cirrus Jet
https://flightaware.com/live/flight/N1408X/history/20190404/1845Z/KCMI/KAGC
[Edit#2]
Nexrad overlay works too.
All the discussion of 3.7.0 has centred on the addition of UAT for the inclusion of UAT which is only in operation in the US.
Is there any information on changes, enhancements, additions and bugfixes for 1090 and MLAT?
For those of us in countries without UAT will it be possible to turn all the 978 code off to reduce any additional cpu, power and heat with the new code?
And finally, I didn’t like the change in 3.6.3 to put the info for the target aircraft in the bottom of the table in Piaware. I preferred the popup over the map as I generally use a 28" monitor. All my Pis are running 3.6.2 or older. Will there be any imperative to upgrade them to 3.7 if I don’t want UAT?
Thanks,
S.
Check out the notes on Github
I’ll try the official release when its available
Last night’s Flughtaware maintenance seems to have fixed the issue with 3.7 feeding data. My 3.7 UAT only site started showing statistics updates after the ha he window.
I expect we will hear more about in today’s announcement.
There is a packaged dump978-fa available
sudo apt-get install dump978-fa
I spent a couple hours last night playing around with getting dump978 installed + piaware3.7 + raspbian stretch on a pizero W with the FA blue dongle and then also the nooelec nano 978 dongle (only on at a time) Mixed results in both cases – the nooelec had dump978 complaining about an overflow, removing soapy audio got me a little farther down the road but in the end I decided I’d wait for the “official” build. Thank you to everyone who posted all their findings in what felt like real time as I walked through the entire thread. Compiling everything manually on the pizw gave me a lot of free time to clean up the apartment 
