MLAT feeding - noob after guidance

forum wont let me post my question, saying its spam content?

 

Hi, seems the forum configuration limits the content in the first posts for new members. I expect admins fix that.

 

Hi Superg3,

Thanks for the reply. Nice to know its not just me. I seem to have managed to make myself work, no idea what ive done. two days of testing and nothing, post on forum and its kicked in to life. see myself on the sync-3 page now so think im good.

 

brains-lans, please tell me from what country are you feeding.

 

Berkshire, England, UK.

mlat-client kicked in to action earlier after being left disconnecting itself due to no keepalives every 60 seconds and was working. I killed it and moved it to a screen session so it stayed running when I logged off and its now still doing the no keep alives thing.

Im right in thinking it should re-connect by itself eventually?

 

What image are you using un your Raspberry?

 

Its a pi3 with dump-mutability 1.15~dev and has been feeding to flightaware successfully both ADSB and MLAT for about a year. Just thought id fill in your patchy UK coverage and get some extra MLAT data for myself.

Running mlat-client 0.2.6 which was installed by the adsbexchange setup.sh script.

Linux above 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux

cat /etc/debian_version

8.0

 

Please run from the command line

Code:

sudo systemctl status mlat-client -l

and post the output.

 

Hi,

username: brains-lans

● mlat-client.service - LSB: Multilateration client

Loaded: loaded (/etc/init.d/mlat-client)

Active: active (exited) since Thu 2017-11-02 13:27:47 UTC; 2h 18min ago


Nov 02 13:27:47 above mlat-client[3162]: Not starting mlat-client daemon, disabled via /etc/default/mlat-client ... (warning).

Nov 02 13:27:47 above systemd[1]: Started LSB: Multilateration client.

 

I think it could be a good idea remove and reinstall:

Code:

sudo service mlat-client stop
sudo apt-get remove mlat-client
sudo apt-get purge mlat-client
sudo rm -rf adsb-exchange
sudo apt-get install git
sudo git clone https://github.com/jprochazka/adsb-exchange.git
cd adsb-exchange
sudo chmod +x setup.sh
sudo ./setup.sh
sudo reboot

Wait 5 minutes and find your station name in the sync matrix.

 

Hi,

Sorry for the bad output, if I copy and paste directly it doesnt permit me to post as its classed as spam for some bizzare reason

OK so restarted mlat-client, restarts clean no error. Made no difference to the mlat-client, still getting the same 'No Data for 60 secs'

NC is installed yes

It worked for a period earlier, im wondering if I leave it for a few hours it might re-connect?

Many thanks for the help

Brian

 

doing this now

 

Also check raspy regional an time settings

Code:

sudo raspi-config 

reboot after.

 

Followed your commands and looks like a clean-reinstall, have also checked the localisation, was all correct but set it all again and rebooted.

I note that mlat-client started automatically, which id didn't before, Just need to see if I appear on the sync-3 page in a few mins

 

I bet it will appear

 

Gave it ten minutes, didnt show so I killed the PID and manually ran the line
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

to see the output, its still the same handshaking > no data > handshaking.

Brian