Hi MDA, thanks for all your help your a lifesaver, just have to wait until my feed is added have asked for Zcons 53088 with user JBBHackney. Jonny
Hi MDA, Thank you mlat is now connecting and then disconnecting so once mlat server is back up it should be ok. Jonny
Hi Marcin, getting connected and disconnected the aircraft known 0 and aircraft requested 0 is that normal or is it mlat server?. Jonny
Hi Jonny Synchronise Windows system clock. Time drift about 200ms is causing rejecting of data. Marcin
You mean NTP? Windows clock is trying to synchronise with NTP server. You can force synchronisation manually (in W10 access to this function is more difficult than in W7). I'm happy W7 user, google a bit and you'll find how... Marcin
Hi Marcin, mlat is still connecting and disconnecting I have synchronised windows clock with NTP. Jonny
It looks that MLAT server don't accept new connections. One of my remote feeders was down for 24 hours and can't reconnect. Wait... Marcin
MDA I've got exactly the opposite problem. MLAT is fine but I cannot reconnect my feed to 51152. It's been like this all day, do you know if the maintenance is finished yet? I can connect from another feeder to port 30005, but not to the one that I usually feed to. Both Lezardrieux03 and Lezardrieux04 are showing MLAT activity but neither is showing on the sync stats page.
We are going to phase out VRS feeders in the next year or two. VRS just doesn't handle the timestamps, it sends bad data. You can feed direct from dump1090 that would be great - to a 51xxx port.
James, Some of us are still having problems connecting to the 51xxx ports. I've got MLAT activity and can connect netcat to 35005, but cannot get my normal feed onto 51152.
Hi James,here is my dump1090 bat: dump1090.exe --interactive --net --net-ro-port 30002 --net-beast --oversample --phase-enhance --mlat --lat 51.532173 --lon -0.084662 --gain -10 pause What would I need to change to feed from dump to ADSB exchange servers? Jonny
I use a Pi or Linux. Here is my linux config. Try another 51xxx port ... people do stupid stuff like connect to a port and don't send data - which then plugs up the port The only script you have to edit is the netcat one or socat one - depending on who's image you are using /usr/bin/dump1090-mutability --quiet --net --ppm 0 --fix --lat $MLATITUDE --lon $MLONGITUDE --max-range 300 --net-ri-port 0 --net-ro-port 30002 --net-bi-port 30004,30104 --net-bo-port 30005 --net-sbs-port 30003 --net-heartbeat 30 --net-ro-size 5000 --net-ro-interval 1 --net-buffer 2 --stats-every 3600 --write-json /run/dump1090-mutability --write-json-every 5 --write-json-every 5 --json-location-accuracy 1' my dump1090 from dump1090-mutability ... if you are using dump1090-fa .. I have no idea -- good luck All you need to do is send dump1090 30005 output to feed.adsbexchange.com:30005 like so /usr/bin/socat TCP:localhost:30005 TCP:feed.adsbexchange.com:30005 netcat is documented in the forum or @MDA can post it
