Thanks for the idea. Sure that does not solve the issue, I was just thinking. Looks like I keep it as it is and run all software on the Pi. As I am currently also redesign my antenna park, I’ll probably move the Pi to a different position. So I have easy access and only the antenna is outside. That also enables the Option to put the Pi again in a metal shielding that reduces a lot of EMI emissions.
Since I write in this forum, the ADSB unit works fine. It feeds FA and FR24 and also the local site works fine.
Nevertheless I do have questions about the status output of the logs:
pi@adsb-pi:~ $ piaware-status
PiAware master process (piaware) is running with pid 422.
PiAware ADS-B client (faup1090) is running with pid 538.
PiAware ADS-B UAT client (faup978) is not running.
PiAware mlat client (fa-mlat-client) is running with pid 15746.
Local ADS-B receiver (dump1090-fa) is running with pid 403.
dump1090-fa (pid 403) is listening for connections on port 30005.
no program appears to be listening for connections on port 30978.
faup1090 is connected to the ADS-B receiver.
faup978 is NOT connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.
got 'couldn't open socket: connection refused'
dump1090 is producing data on localhost:30005.
Your feeder ID is xxxx (from /var/cache/piaware/feeder_id)
Even I get this socket error, I do not see any missing things. And as above everything is looking fine, the error line is missing substantial information to get an idea what might be missing there.
pi@adsb-pi:~ $ fr24feed-status
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2019-09-11 13:13:18.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-xxx.
[ ok ] FR24 Tracked AC: 18.
[ ok ] Receiver: connected (12450574 MSGS/0 SYNC).
[FAIL] FR24 MLAT: not running ... failed!
I know this might be the wrong forum, but do I have to run two MLAT services to feed two different instances?