Also, only request/claim a custom feed if you have a reliable feed. I would guess 1/3 of the custom feeders, request ports, I manually configure the port, and they feed for about a month, maybe more, maybe less. If I check on custom feeds and I repeatedly don't see data, I'll send one email then remove the configuration. Over all the custom feeds might be the way we'll go in the future.
@James Thanks for this comprehensive info. I'm pretty sure that upgrade from Win to "Pi" should be done asap as I'm struggling with Win dump1090 & mlat-client. Also to get the possibility of the great ADSBx to be used Thanks!
Pi is certainly more energy efficient and minimal maintenance. But if you don't worry about power usage - linux PC is easy to feed with as well. The Pi operating system is Debian linux.
Yep, I've got a background info and Linux in those fields (like time issues) just works. Windows, as always - doesn't So PI will come soon, but dealing on Win with dump1090 and mlat-client is in progress. By the way - was I succesful in connecting mlat-client ? I've noticed connection with server feed but the transfer packets looks empty (or no mlat calculations are requested) ;/ Code: python mlat-client --input-type beast --input-connect 127.0.0.1:30005 --lat 51.09864 --lon 17.01013 --alt 143.52 --user zladic71 --server feed.adsbexchange.com:31090 --no-udp --results beast,connect,127.0.0.1:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 than VRS to get the data but I'm afraid that I've screw something... p.s. Please move this post to MLAT thread if needed. Thanks!
There are plenty of feeders in range around Warsaw. Normally feeds sync up to the matrix fairly quickly, the map dots take an hour or so to refresh.
Your feed is not on sync matrix. Config looks a bit strange (especially end for receiving data). Can you post screenshot of your dump1090? (or some info about amount of aircrafts per day and average positions rate).
Ok, I don not find myself on map and on Matrix, so I'm not synced at all. As wondered I missed something... @MDA thanks for your confirmation that the fault is on my site I'm attaching screens from dump1090 and VRS [this eveing flights, however the last hour looks like miissing a lot of lat/lon coordinates]. Maybe it will be helpful and gives an idea what I really screwed. Thanks!
First of all install software which will sync your Widows PC clock (search forum for Shalomblessing posts). Modify your mlat-client script to standard one, and be patient... Serwer jest przeciążony, połączenie może zająć sporo czasu. Lot of fun with feeding. Marcin
Cześć @MDA OK, this does ring the bell - I'll give it a try. Regarding modification to the 'standard one' - do you mean mutability and following update to get the updates for VRS : from this Code: --results beast,connect,127.0.0.1:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 to Code: --results basestation,listen,31003 Thanks!
Exactly For MLAT aircrafts on dump1090 map Code: --results beast,connect,localhost:30104 For VRS Code: --results basestation,listen,31003
Still not on sync matrix. Try to uninstall actual version of MLAT client and install one from adsbexchange Github repository. You can be affected by same issue as adsb-tech-007. Try to search this forum and use same solution. I can't remember all of my answers, all of them are on this forum. Success with feeding. Marcin
Hi, I thought I was feeding 51141 but under custom ports I appear to be connected to a feeder named NickHead. I am not familiar with that name at all but the map location is my area. Geoff Lane
Multiple requests on that same port. And in the same geographic area. I configured most recent. Picko one on https://customglobal4.adsbexchange.com/VirtualRadar/desktop.html .. and send to it.
Working here. We had to ban a bunch of IP today. Someone was connected to TCP feed and rebroadcasting our own data back to us. Here is the current firewall ban list.
Correct me if I'm wrong but custom feed view will only show ADSB traffic while global view shows ADSB and MLAT traffic combined?
That is correct. We cannot show MLAT on custom feed because we can't forward MLAT due to FlightAware, FR24 etc all feeders needing to be installed on the same Pi as ADSBx.
