That only changes the assumed accuracy of the clock? It should run fine with the default options, shouldn't it? But my theory about the configuration file is wrong, as he needed to edit that anyway and then restart the services. Maybe one indeed needs to change the input type, curious though. Restarting the mlat service before the configuration file is written is still a bug though, sorry for that.
we tested it before with port 10006 ant radarcape_gps as input type. Look into logs, clock is changing to 20MHz (if i good remember).
To make MLAT work you'll have to do some more shenanigans apparently: Code: cd /tmp/adsb-exchange git checkout -f git pull -f sudo bash setup.sh sudo nano /etc/default/adsbexchange Change the INPUT again (it will be back to defaults). This time there should be a new line named INPUT_TYPE, there change dump1090 to radarcape_gps Then restart the services: sudo systemctl restart adsbexchange-feed adsbexchange-mlat And now hopefully everything should work.
Thank you all! Re-installing, configuring and restart is done. myip tells since 20 min feedertest: Data incoming from: 213.153.90.177 Route: beast_front Port: 30005 Backend: feedertest_back Connected: feedertest Age: 21m4s And although adsbx.org / sync / feeder.html?4B&Scharnhausen-01 is the same as before. I'm waiting patiently for anything to change or for you to give me instructions.
Let's just check what parameters the mlat-client is running with: pgrep -a mlat-client Also i'm curious what is your antenna setup, does the Radarcape have an additional GPS antenna connected?
[email protected]:~/adsb-exchange$ pgrep -a mlat-client 21804 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:10006 --input-type radarcape --results ext_basestation,listen,30106 --no-modeac-results --udp-transport 70.42.6.224:6853:4082735841 25955 /usr/bin/python3.5 /usr/bin/mlat-client --input-type radarcape_gps --no-udp --input-connect 127.0.0.1:10006 --server feed.adsbexchange.com:31090 --user Scharnhausen-01 --lat 48.711 --lon 9.26528 --alt 374.143 --results beast,connect,localhost:30104 --results basestation,listen,31003 [email protected]:~/adsb-exchange$ Yes, an extra GPS antenna is attached to the Radarcape directly on the bottom of an A3 ADS-B antenna from Jetvision. Between ADS-B antenna and Radarcape I even bought a 1090 MHz 3 pole cavity filter from Jetvision. Here you can have a closer look onto the Radarcape: t958ehxgihvoitij.myfritz.net:8082/map.html
Ah the fa-mlat-client is using radarcape and not radarcape_GPS. You could try that as the INPUT_TYPE, maybe it works then Just change it in the config file and restart the service as before. Edit: that probably doesn't change anything, just some sort of autodetection which should use radarcape_gps in your case. Any chance you could link your FA stats, i'm curious if your MLAT for FA is working.
The computer in the radarcape might just be too slow for MLAT To disable MLAT so it doesn't use up your CPU: sudo systemctl disable --now adsbexchange-mlat I'm all out of ideas in regards to MLAT sorry
Yes you are right. radarcape as INPUT_TYPE changed nothing. Ok I see. This way it seems not to be as easy as I hoped it would be. Jetvision/Guenter & Co. apparently has a way to send to FR24, PP, FA, OpenSky and the own Jetvision MLAT data independently or in parallel. I manually installed the Linux ARMHF Debian package via SSH from Planefinder.net, which should also contain MLAT. Of course I don't know if MLAT data is actually sent. AirNav RadarBox24.com's RBFeeder for RPi can't be persuaded to fetch Radarcape data from other that default. But this thread is about ADSBx. You specialists might be able to fix this somehow, but it's also about showing other Radarcape owners an easy way. Just an idea: Is UDP data streaming an way to go? There are fields to fill in "Receiving Server(s) for Port 10003/4/5/6/30003/JSON UDP Data". But I guess that would also not include the MLAT data as we actual already set up with the adsbxchange script method and your changes. Too slow for MLAT? MLAT is one of the key feature of Radarcape for the own Jetvision MLAT. BTW: These data can also be configured to send in parallel to other server(s) : port.
It's running the fa mlat-client, which is the same mlat-client code that adsbexchange uses. So it should work, really don't know why it doesn't. Only thing i can think of: Maybe the altitude with decimals is a problem, grasping at straws. Maybe change it to just 374
Okay. Intermediate status: /etc/default/adsbexchange RECEIVERPORT="30005" USER="Scharnhausen-01" RECEIVERLATITUDE="48.71102" RECEIVERLONGITUDE="9.26538" RECEIVERALTITUDE="374" RESULTS="beast,connect,localhost:30104 --results basestation,listen,31003" MLATSERVER="feed.adsbexchange.com:31090" INPUT="127.0.0.1:10006" INPUT_TYPE="radarcape_gps" [email protected]:~$ pgrep -a mlat-client 422 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:10006 --input-type radarcape --results ext_basestation,listen,30106 --no-modeac-results --udp-transport 70.42.6.224:8764:1894092800 9028 /usr/bin/python3.5 /usr/bin/mlat-client --input-type radarcape_gps --no-udp --input-connect 127.0.0.1:10006 --server feed.adsbexchange.com:31090 --user Scharnhausen-01 --lat 48.71102 --lon 9.26538 --alt 374 --results beast,connect,localhost:30104 --results basestation,listen,31003 https://adsbexchange.com/myip/ lines out output: 13 Data incoming from: 213.153.90.177 Route: beast_front Port: 30005 Backend: feedertest_back Connected: feedertest Age: 2h20m Data incoming from: 213.153.90.177 Route: MLAT_front Port: 31090 Backend: MLAT_back_4B Connected: mlat-c Age: 1h15m Does this mean my MLAT data are accepted from the ADSBExchange server? But still no MLAT results on https://adsbx.org/sync/feeder.html?4B&Scharnhausen-01 and also clicking onto my pin at the http://www.adsbexchange.com/coverage-4B/?new map. We can stay in touch even if one of you would like to have a remote look at it.
you can check this log: sudo journalctl -eu adsbexchange-mlat but i doubt it's gonna say much that is interesting. Edit: so i checked your feeder logs for the FA feeder: Sep 18 08:18:16 radarcape piaware[10795]: mlat-client(10851): Input format changed to RADARCAPE, 1000MHz clock Sep 18 08:18:15 radarcape piaware[10795]: mlat-client(10851): Input format changed to BEAST, 12MHz clock Sep 18 08:18:15 radarcape piaware[10795]: mlat-client(10851): Input connected to localhost:10006 Note that it says input format changed to beast, 12 MHz. That's not radarcape_gps. So maybe just use radarcape as the input_type, so it can autodetect it.
[email protected]:~$ sudo /bin/journalctl -eu adsbexchange-mlat Sep 18 08:38:13 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:38:13 2019 Server explicitly rejected our connection, saying: Sep 18 08:38:13 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:38:13 2019 Bad values in handshake: User Scharnhausen-01/Scharnhausen-01 is already connected Sep 18 08:38:13 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:38:13 2019 Connection to feed.adsbexchange.com:31090 lost: Server rejected our connection attempt Sep 18 08:38:13 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:38:13 2019 Lost connection to feed.adsbexchange.com:31090 Sep 18 08:38:13 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:38:13 2019 Reconnecting in 823.0 seconds Sep 18 08:38:40 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:38:40 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 08:39:10 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:39:10 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 08:39:40 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:39:40 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 08:40:08 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:40:08 2019 Receiver status: disconnected Sep 18 08:40:08 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:40:08 2019 Server status: disconnected Sep 18 08:40:08 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:40:08 2019 Receiver: 0.0 msg/s received 0.0 msg/s processed (0%) Sep 18 08:40:08 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:40:08 2019 Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server Sep 18 08:40:08 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:40:08 2019 Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used Sep 18 08:40:10 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:40:10 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 08:40:40 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:40:40 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused [...] Sep 18 08:51:11 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:51:11 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 08:51:41 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:51:41 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 08:51:57 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:51:57 2019 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Sep 18 08:52:12 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:52:12 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 08:52:42 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:52:42 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 08:52:57 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:52:57 2019 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Sep 18 08:52:57 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:52:57 2019 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Sep 18 08:53:12 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:53:12 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 08:53:42 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:53:42 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 08:53:58 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:53:58 2019 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Sep 18 08:54:01 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:54:01 2019 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Sep 18 08:54:12 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:54:12 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 08:54:42 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:54:42 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 08:55:01 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:55:01 2019 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Sep 18 08:55:08 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:55:08 2019 Receiver status: disconnected Sep 18 08:55:08 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:55:08 2019 Server status: disconnected Sep 18 08:55:08 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:55:08 2019 Receiver: 0.0 msg/s received 0.0 msg/s processed (0%) Sep 18 08:55:08 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:55:08 2019 Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server Sep 18 08:55:08 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:55:08 2019 Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used Sep 18 08:55:12 radarcape adsbexchange-mlat[9028]: Wed Sep 18 08:55:12 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 08:55:16 radarcape systemd[1]: Stopping adsbexchange-mlat... Sep 18 08:55:16 radarcape systemd[1]: Stopped adsbexchange-mlat. Sep 18 08:55:16 radarcape systemd[1]: Started adsbexchange-mlat. Sep 18 08:55:18 radarcape adsbexchange-mlat[14846]: Wed Sep 18 08:55:18 2019 mlat-client 0.2.10 starting up Sep 18 08:55:18 radarcape adsbexchange-mlat[14846]: Wed Sep 18 08:55:18 2019 Listening for Basestation-format results connection on port 31003 Sep 18 08:55:18 radarcape adsbexchange-mlat[14846]: Wed Sep 18 08:55:18 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused The restart was after I ensured to stop adsbexchange on my RPi from my first test installation. Maybe another new Username would help??
The log i looked at was in reverse, so it was using radarcape_gps, my bad. No need to change anything. (you can leave it on setting radarcape_gps) Edit: for whatever reason, it's working fine now! Rejoice! Also it seems i clicked a wrong button and your Radarcape is doing a GPS position survey
Well now it seems something happen. https://adsbx.org/sync/feeder.html?4B&Scharnhausen But the "Connection refused" irritates me. Sep 18 09:16:32 radarcape adsbexchange-mlat[14846]: Wed Sep 18 09:16:31 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 09:16:41 radarcape systemd[1]: Stopping adsbexchange-mlat... Sep 18 09:16:41 radarcape systemd[1]: Stopped adsbexchange-mlat. Sep 18 09:16:42 radarcape systemd[1]: Started adsbexchange-mlat. Sep 18 09:16:43 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:16:43 2019 mlat-client 0.2.10 starting up Sep 18 09:16:43 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:16:43 2019 Listening for Basestation-format results connection on port 31003 Sep 18 09:16:43 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:16:43 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 09:17:14 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:17:14 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 09:17:44 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:17:44 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 09:18:14 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:18:14 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 09:18:44 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:18:44 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 09:18:56 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:18:56 2019 Connection to feed.adsbexchange.com:31090 lost: [Errno 110] Connection timed out Sep 18 09:18:56 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:18:56 2019 Reconnecting in 30.0 seconds Sep 18 09:19:14 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:19:14 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 09:19:44 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:19:44 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 09:20:14 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:20:14 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 09:20:45 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:20:45 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 09:21:15 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:21:15 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 09:21:40 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:21:40 2019 Connection to feed.adsbexchange.com:31090 lost: [Errno 110] Connection timed out Sep 18 09:21:40 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:21:40 2019 Reconnecting in 30.0 seconds Sep 18 09:21:45 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:21:45 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 09:22:15 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:22:15 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 09:22:25 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:22:25 2019 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Sep 18 09:22:45 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:22:45 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 09:23:15 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:23:15 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 09:23:25 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:23:25 2019 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds Sep 18 09:23:33 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:23:33 2019 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking Sep 18 09:23:45 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:23:45 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 09:24:05 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:24:05 2019 Server says: Sep 18 09:24:05 radarcape adsbexchange-mlat[18182]: In-development v2 server. Expect odd behaviour. Sep 18 09:24:05 radarcape adsbexchange-mlat[18182]: The multilateration server source code is available under Sep 18 09:24:05 radarcape adsbexchange-mlat[18182]: the terms of the Affero GPL (v3 or later). You may obtain Sep 18 09:24:05 radarcape adsbexchange-mlat[18182]: a copy of this server's source code at the following Sep 18 09:24:05 radarcape adsbexchange-mlat[18182]: location: https://github.com/mutability/mlat-server Sep 18 09:24:05 radarcape adsbexchange-mlat[18182]: Sep 18 09:24:05 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:24:05 2019 Handshake complete. Sep 18 09:24:05 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:24:05 2019 Compression: zlib2 Sep 18 09:24:05 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:24:05 2019 UDP transport: disabled Sep 18 09:24:05 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:24:05 2019 Split sync: disabled Sep 18 09:24:05 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:24:05 2019 Input connected to 127.0.0.1:10006 Sep 18 09:24:05 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:24:05 2019 Input format changed to RADARCAPE, 1000MHz clock Sep 18 09:24:15 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:24:15 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 09:24:46 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:24:46 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 09:25:16 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:25:16 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 09:25:46 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:25:46 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 09:26:16 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:26:16 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused Sep 18 09:26:47 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:26:47 2019 Beast-format results connection with ::1:30104: [Errno 111] Connection refused Sep 18 09:27:17 radarcape adsbexchange-mlat[18182]: Wed Sep 18 09:27:17 2019 Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
That can be fixed, go to the config file and make the results line say the following: RESULTS="basestation,listen,31003"
Interestingly the GPS survey found an altitude of 365 m. (the one i triggered out of curiosity) But that's not that significant for MLAT, so you don't have to change it.
