[email protected]:~# ping feed.adsbexchange.com PING feed.adsbexchange.com (167.114.60.74) 56(84) bytes of data. 64 bytes from feed.adsbexchange.com (167.114.60.74): icmp_seq=1 ttl=50 time=89.0 ms 64 bytes from feed.adsbexchange.com (167.114.60.74): icmp_seq=2 ttl=50 time=89.2 ms 64 bytes from feed.adsbexchange.com (167.114.60.74): icmp_seq=3 ttl=50 time=89.3 ms 64 bytes from feed.adsbexchange.com (167.114.60.74): icmp_seq=4 ttl=50 time=90.1 ms
I see that you are logged as root. Maybe this is the reason (standard user "pi" has not enough rights to run all necessary scripts). Last idea is: synchronize system time of your Pi. Code: sudo /etc/init.d/ntp restart
time is set by ntp and is correct to within less than 100th of a second. Im going to have to stop for the day shortly but will try and investigate further tomorrow. Current manual run shows Code: [email protected]:~# mlat-client --input-type dump1090 --input-connect localhost:30005 --lat 51.395821 --lon -1.062810 --alt 27 --user brains-lans --server feed.adsbexchange.com:31090 --no-udp --results beast,connect,localhost:30104 Thu Nov 2 16:51:56 2017 mlat-client 0.2.6 starting up Thu Nov 2 16:51:56 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 16:51:57 2017 Beast-format results connection with ::1:30104: connection established Thu Nov 2 16:52:56 2017 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Thu Nov 2 16:52:56 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 16:53:56 2017 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Thu Nov 2 16:53:56 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 16:54:56 2017 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Thu Nov 2 16:54:56 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 16:55:56 2017 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Thu Nov 2 16:55:56 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 16:56:56 2017 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Thu Nov 2 16:56:56 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 16:57:56 2017 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Thu Nov 2 16:57:57 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 16:58:57 2017 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Thu Nov 2 16:58:57 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 16:59:57 2017 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Thu Nov 2 16:59:57 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 17:00:08 2017 Lost connection to feed.adsbexchange.com:31090 Thu Nov 2 17:00:08 2017 Reconnecting in 30.0 seconds Thu Nov 2 17:00:38 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 17:01:38 2017 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Thu Nov 2 17:01:39 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 17:01:50 2017 Lost connection to feed.adsbexchange.com:31090 Thu Nov 2 17:01:50 2017 Reconnecting in 30.0 seconds Thu Nov 2 17:02:20 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 17:02:31 2017 Lost connection to feed.adsbexchange.com:31090 Thu Nov 2 17:02:31 2017 Reconnecting in 30.0 seconds Thu Nov 2 17:03:02 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 17:03:13 2017 Lost connection to feed.adsbexchange.com:31090 Thu Nov 2 17:03:13 2017 Reconnecting in 30.0 seconds Thu Nov 2 17:03:43 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 17:03:54 2017 Lost connection to feed.adsbexchange.com:31090 Thu Nov 2 17:03:54 2017 Reconnecting in 30.0 seconds Thu Nov 2 17:04:25 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 17:05:25 2017 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Thu Nov 2 17:05:25 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 17:05:36 2017 Lost connection to feed.adsbexchange.com:31090 Thu Nov 2 17:05:36 2017 Reconnecting in 30.0 seconds Thu Nov 2 17:06:06 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 17:06:56 2017 Receiver status: disconnected Thu Nov 2 17:06:56 2017 Server status: handshaking Thu Nov 2 17:06:56 2017 Receiver: 0.0 msg/s received 0.0 msg/s processed (0%) Thu Nov 2 17:06:56 2017 Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server Thu Nov 2 17:06:56 2017 Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used Thu Nov 2 17:07:06 2017 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Thu Nov 2 17:07:06 2017 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Thu Nov 2 17:07:18 2017 Lost connection to feed.adsbexchange.com:31090 Thu Nov 2 17:07:18 2017 Reconnecting in 30.0 seconds so it does connect sometimes but dies again.
Got to go for the day now, going to leave this re-connecting and perhaps it will do it itself eventually, but that would suggest a server side congestion issue if it does, which seems unlikely as Id assume everyone would be complaining if that was the case. Im guessing its still going to be my fault somewhere. More later or more probably tomorrow. Thank you to all for your kind advice, appreciated! Brian
just noticed this post, https://www.adsbexchange.com/forum/threads/adsb-exchange-image-not-working.617687/#post-619034 Seems very similar to me, but I've built mine manually and have been doing FlightAware for over a year with MLAT and ADSB no issue. Just wanted to contribute here too, oh and get your MLAT data Brian
I'm back. Could be possible that the problem is in the server side. As I posted in other thread region 3 and exactly Spain is shown without coverage most of the time.
Hi Marcos Everything is possible except of one thing with umbrella (very old joke ). Keep fingers crossed, we'll solve this problem. BR Marcin
Morning All, Indeed MDA and superg3 are correct, this seems to have connected overnight and been sending data all night without issue, suggesting that perhaps it was a server side issue. Ive killed my manual run and rebooting now, so will see if it carries on from the boot scripts, if so I think we are done. Thank you to everyone who kindly helped yesterday with this matter. Brian
Nothing yet, I think this may be a server side issue. Going to leave it running and see if it appears by itself. Process is running at boot by itself ok: Code: root 2082 0.3 0.9 12992 9192 ? S 09:46 0:01 /usr/bin/python3.4 /usr/bin/mlat-client --input-type dump1090 --input-connect localhost:30005 --lat 51.39582 --lon -1.06281 --alt 95.3416595459 --user brains-lans --server feed.adsbexchange.com:31090 --no-udp --results beast,connect,localhost:30104 Brian
Is good to know it started to work for you . I have been testing all the available versions of MLAT-CLIENT last night, including last release 0.2.10 ,and finally I was able to make all versions to work. I'm in region 3 like you, but I'm in Spain, sadly most of the time the MLAT SERVER leaves Spain with the "lights off" and I was not able to receive feedback to try to solve the problem. I supose that maybe it is how loading balance is configured in the server, and in Spain, by now, we are just 10 feeders or so.
My Parents live in spain, maybe I should post them my old pi2? Not sure what they could do about an external antenna though as they arent exactly of the age to be climbing on roofs.
Thanks for your offer but it is no needed . I have 3 PI3B waiting for the FlightAware Pro Stick Plus sticks that will arrive today to my home
Is there an easy way to feed flightaware if I'm already feeding adsbexchange? I tried posting a full question but it the site said it looked like spam.
