I've just built a new feeder using a Pi with Stretch Lite. I'm feeding to three other sites and have just added ADSBX. When I check the myip page, I can see my main connection is good and has been up for about an hour. However, the MLAT link has only been there for a short while. It appears, stays up for a while and then disappears. The longest I've seen is about ten minutes for an MLAT link. Is this normal or should the MLAT link stay connected continually as per the main feed? I'm in a very good location and expect to see around 4,000 aircraft/day with well over 1,300,000 position reports. Thanks. /edit - I tried to add a picture but the forum thinks it's spam and won't let me post it. lines out output: 13 Data incoming from: xxx.xxx.xxx.xxx Route: beast_front Port: 30005 Backend: beast_back Connected: golang-merge-10-0 Age: 1h5m Data incoming from: xxx.xxx.xxx.xxx Route: MLAT_front Port: 31090 Backend: MLAT_back_3 Connected: mlat-c Age: 1m51s
It connects up and down. Perfectly normal. Especially if we are doing work on the infrastructure and proxy server is restarted.
Thank you James - I can see it's now been connected for over four hours so that's good. Is there any benefit to asking for a custom port or is it OK as a generic feed into the pot?
No real benefit to a custom port. Staring at your own data on ADSBx is the same as staring at your own data from your feeder. Some people want that. It's a waste of money for ADSBx, considering your Pi can have a much more advanced dashboard with ease.
No, I don't care about that. I have two receivers (one indoors, one outdoors) and I'm responsible for a remote one as well. If I want to look at a map, I've got plenty here!
James, although the /myip site is showing me connected, when I look at the feeder list 3A for the UK, I'm not listed any more although I was before. My site name is Kirby_Cross. Any idea please?
It's back on the map but not the MLAT page. When I search, I get this: Kirby_Cross 0.0% 0 No synced peers And then this on the myip page: lines out output: 13 Data incoming from: xxx.xxx.xxx.xxx Route: MLAT_front Port: 31090 Backend: MLAT_back_3 Connected: mlat-c Age: 1h27m Data incoming from: xxx.xxx.xxx.xxx Route: beast_front Port: 30005 Backend: beast_back Connected: golang-merge-8 Age: 1h27m
Hmm ... Make sure you name each feeder to ADSBx individually if they are in the same region. Names must be unique.
I'm glad it's not only me with the same problem. Mine is up for an hour, then gone and the only way to bring it back is to reboot the pi. I've even reinstalled a fresh setup but it's still the same. FR24 and Flightaware I have no problem with. ps. I am also on feeder 3A in the UK near Manchester. Regards Doug
Well that's great .. FR24 and FA are multi-million dollar for profit business built from free data from feeders. I so love it when people start with the "Well I have no problem with FR24 and FA" Guess what my response is: I don't care ... go feed them so they can sell your data .. shit happens .. live with it .. if you don't have peers synced then you have something wrong on your end ... 1000's of other feeds have no issues ...
Also that sync matrix is not real-time. reboot the Pi has nothing to do with getting mlat to reconnect. install scripts will reconnect mlat-client automatically ...
PS I don't see a Kirby_Cross client anywhere in the MLAT matrices .. so this guy probably not even feeding ..
I'm sorry if i have upset you, but your response has upset me. All I want to do is have a stable feed for the benefit of hobbyists and aviation enthusiasts like myself, which is why i wish to feed to an open site. I understand FR24 and FA's position and have to agree with you. All i wanted to do was help your site and I understand that the sync-matrix is not real time.
It's stable. We give out too much information which leads to people staring at the connections every 5 minutes. email me your IP and I can monitor.. https://adsbexchange.com/myip/ Screenshot or copy paste and send that output to me. [email protected]
http://www.adsbx.org/sync/3A/ UK slice is always interesting ... there's a lot of load on it during peak times