Hi, I feed to several other sites, I'm using the Flight Aware pro dongle attached to a Pi4 and using Piaware as my base 1090 Is it possible to feed ADS-B Ex *without* breaking the existing setup, if so how please. (I had issues previously with ADS-Bex not playing nicely with 360Radar), but it may have been a script overwrite I'd like to be able to do it using the piaware base and no overwriting of existing stuff.
The scripts shouldn't mess with other feeders. https://github.com/adsbxchange/adsb-exchange#ads-b-exchange-setup-scripts-airplane It does install the mlat-client though, if 360Radar is using a custom package called the same, then that might be an issue. Anyhow i'm not familiar with 360Radar. With a piaware base system it won't interfere.
Is there anyway to do it without installing the mlat (I already have it anyway) looking at my logs that was the problem when I fed before. **** The problem is that you've got the ADSB Exchange MLAT client on there. They - like us - use the mutability MLAT-client. Unlike us, they haven't figured out how to create a separate config file ****
This is only ADS-B and shouldn't interfere with anything: https://github.com/wiedehopf/lowBandwidthFeedAdsbX#lowbandwidthfeedadsbx
Thank you, that seems to have done the trick. Although my stats here. https://www.adsbexchange.com/myip/ say no MLAT connection.
I wrote that it's only ADS-B .... I don't care for 360radar and there are enough feeders in the UK, so it's not really a priority for me.
It's ok I'm using just the non MLAT option, the other 6 sites I feed to don't seem to have the problem that this one does. Which really suggests the problem is at your end, not anyone else's...
Do you feed RB24? Their client installs own mlat-client and can cause problems with adsbx mlat. Can you post output of pgrep -a mlat-client ?
487 /usr/bin/python3.7 /usr/bin/mlat-client --user KidderminsterHW --lat 52.38772 --lon -2.22433 --alt 59 --input-type dump1090 --input-connect localhost:30005 --server test.mlat-server.co.uk:41114 609 /usr/bin/python3.7 /usr/bin/mlat-client --input-type dump1090 --input-connect 127.0.0.1:32457 --server mlat1.rb24.com:40900 --lat 52.387768 --lon -2.224405 --alt 111 --user EXTRPI007300 --results beast,connect,127.0.0.1:32004 1779 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.156:15734:3222644337
As you can see, adsbx mlat client is not running. How did you install it (long time ago or using new install scripts)?
The adsbx install script no longer installs or uses the mlat-client package but instead installs to its own folder. This precludes any possibility of issues with rb24 feed programs. https://github.com/adsbxchange/adsb-exchange#ads-b-exchange-setup-scripts-airplane If rb24 ... or whatever else you are using doesn't work now, it's won't be related to adsbexchange. And no matter what the others were saying, if they use the normal package name mlat-client and then using that package name install a non-standard mlat-client, it's very much their problem and not that of adsbexchange. Just to make that clear. But as we are easily annoyed by people claiming that our scripts interfere with their setup and those people are a pain to deal with, we rather changed our scripts to not use any packages, ensuring we don't have to deal with this bull manure.
