Announcement

Collapse
No announcement yet.

MLAT enabled but not running

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • MLAT enabled but not running

    I am running on a raspberry pi 2

    When running set up i respond with "yes" to the enable MLAT option.
    If i look at the status page on port 8754 I am tracking planes (flight radar dashboard tells me I have uploaded and tracked close to a 1000 planes but MLAT always says MLAT running: NO on the local webpage

    How do I enable MLAT. Do i need to install different software on the PI? (I have seen piaware mentioned in a few posts)
    I'm currently just using
    sudo bash -c "$(wget -O - http ://repo.feed.flightradar24.com/install_fr24_rpi.sh)" to install the software.

    EDIT: See post #55 for current status and potential fixes for MLAT issues including with systemd http://forum.flightradar24.com/threa...ll=1#post77715
    Last edited by spudd; 2016-04-04, 18:58.

  • #2
    It has not been verified by any of the devs as yet, But the status appears to come and go dependent on aircraft being tracked. Or may currently be offline to new feeders for a while.

    All about feeding data to Flightradar24 (The Flightradar24 receiver, Raspberry Pi and Windows feeding software). No discussions about Flightradar24 web or apps.


    Your best method of checking is using the 'sudo service fr24feed status' instead as the page does not refresh well.
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

    Comment


    • #3
      This is what I get from the web page
      Flightradar24 Feeder/Decoder

      Linux/generic/armv7l/1.0.18-5

      Updated: 12:16:02 GMT+0100 (GMT Summer Time)

      FR24 Link: Connected via UDP
      FR24 Radar Code: T-EGBK15
      Aircraft Tracked (ModeS & ADS-B): 16
      Aircraft Uploaded: 10
      Receiver: dvbt, Connected
      MLAT running: NO
      This is what I get from status
      root@raspberrypi:/home/pi# service fr24feed status
      ● fr24feed.service - LSB: Flightradar24 Decoder & Feeder
      Loaded: loaded (/etc/init.d/fr24feed)
      Active: active (running) since Wed 2016-03-30 10:55:09 UTC; 21min ago
      Process: 15553 ExecStop=/etc/init.d/fr24feed stop (code=exited, status=0/SUCCESS)
      Process: 15637 ExecStart=/etc/init.d/fr24feed start (code=exited, status=0/SUCCESS)
      CGroup: /system.slice/fr24feed.service
      ├─15651 /usr/bin/fr24feed -- --monitor-file=/dev/shm/fr24feed.txt --write-pid=/var/run/fr24feed.pid --quiet
      └─15674 /usr/lib/fr24/dump1090 --raw --mlat

      Mar 30 10:55:09 raspberrypi fr24feed[15637]: Starting FR24 feeder: fr24feed.
      Mar 30 10:55:09 raspberrypi systemd[1]: Started LSB: Flightradar24 Decoder & Feeder.
      MLAT is enabled in the fr24feed.ini file.

      Comment


      • #4
        Not sure why my previous response isn't showing.

        This is the output I get

        root@raspberrypi:/home/jt# service fr24feed status
        ● fr24feed.service - LSB: Flightradar24 Decoder & Feeder
        Loaded: loaded (/etc/init.d/fr24feed)
        Active: active (running) since Wed 2016-03-30 11:33:23 UTC; 2h 3min ago
        Process: 561 ExecStart=/etc/init.d/fr24feed start (code=exited, status=0/SUCCESS)
        CGroup: /system.slice/fr24feed.service
        ├─615 /usr/bin/fr24feed -- --monitor-file=/dev/shm/fr24feed.txt --write-pid=/var/run/fr24feed.pid --quiet
        └─635 /usr/lib/fr24/dump1090 --raw --mlat

        Mar 30 11:33:23 raspberrypi fr24feed[561]: Starting FR24 feeder: fr24feed.
        Mar 30 11:33:23 raspberrypi systemd[1]: Started LSB: Flightradar24 Decoder & Feeder.
        Last edited by spudd; 2016-03-30, 13:37.

        Comment


        • #5
          Do you need to have piaware installed or mlat client or does the fr24feed install that for you?

          Comment


          • #6
            the mlat part of it all is built into the fr24 client.
            T-EGLF8

            Comment


            • #7
              I've just checked the log and its full of

              2016-03-30 17:54:56 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
              2016-03-30 17:54:56 | [mlat][i]Registering MLAT station
              2016-03-30 17:54:56 | [mlat][i]Registering MLAT station: FAILURE
              I see when this was in beta lots of people had this issue but it was fixed with an update. I'm currently on the latest version as far as i know. Fresh install last week

              EDIT: I have not installed any driver for the RTL2838 DVB-T stick. I see back in past forum posts people have. Is this still needed or is it built in to the latest version of raspbian?
              Last edited by spudd; 2016-03-30, 17:20.

              Comment


              • #8
                Originally posted by spudd View Post
                I've just checked the log and its full of



                I see when this was in beta lots of people had this issue but it was fixed with an update. I'm currently on the latest version as far as i know. Fresh install last week

                EDIT: I have not installed any driver for the RTL2838 DVB-T stick. I see back in past forum posts people have. Is this still needed or is it built in to the latest version of raspbian?
                Linux doesn't need drivers. The libraries for RTL chipset are bundled during install of either package. If they weren't you also wouldn't see normal ADSB traffic along with MLAT.
                Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                Comment


                • #9
                  Yes makes sense. ADS-b is working fine.

                  My guess is that my radar code is very new so as you said above, they probably aren't accepting new feeders at the moment.

                  Edit: it would be nice if they could clarify this as it's a bit disconcerting when you find a 5Mb log file full of [mlat][i]Registering MLAT station: FAILURE


                  If MLAT starts getting accepted anytime soon I will post back

                  Comment


                  • #10
                    I'm seeing the same thing here with a clean updated Pi 2 Jessie install over the last week: ADS-B working 100% but MLAT has never worked (always get that FAILURE message when it tries to register.)

                    Additionally, it seems to be trying to connect multiple times a second and therefore filling the logfile up very quickly (given both the I/O performance hit on Pi's and the fact that memory cards have a limited number of writes this doesn't seem to be a very clever.)

                    I've wasted a lot of time trying to get MLAT working and trying to diagnose the what the network problem is (given that fr24feed.txt says "mlat_problem=udp-firewall".) I've tried port-forwarding directly to the Pi, having the Pi as a DMZ, etc. ADS-B is working, so I really don't see how it can be a local UDP problem or firewall if the firewall gets completely bypassed.

                    I do wish we'd get some form of official information on what's going on, it's very frustating.

                    Comment


                    • #11
                      Yes i checked all the firewall logs to see if UDP was being blocked anywhere but nothing there.
                      How long have you had your radar running for?

                      Hopefully we will get some official information on this!

                      Comment


                      • #12
                        Originally posted by geekycow View Post
                        I'm seeing the same thing here with a clean updated Pi 2 Jessie install over the last week: ADS-B working 100% but MLAT has never worked (always get that FAILURE message when it tries to register.)

                        Additionally, it seems to be trying to connect multiple times a second and therefore filling the logfile up very quickly (given both the I/O performance hit on Pi's and the fact that memory cards have a limited number of writes this doesn't seem to be a very clever.)

                        I've wasted a lot of time trying to get MLAT working and trying to diagnose the what the network problem is (given that fr24feed.txt says "mlat_problem=udp-firewall".) I've tried port-forwarding directly to the Pi, having the Pi as a DMZ, etc. ADS-B is working, so I really don't see how it can be a local UDP problem or firewall if the firewall gets completely bypassed.

                        I do wish we'd get some form of official information on what's going on, it's very frustating.
                        Be wary that that message in the variable page is only indicative of the LAST message received (may not be current) Mine often says no_config - simply means it started both app aspects before the connection to server was established to be able to download the config from one of them.

                        As I posted in other thread check your GPS co-ords are correct on startup too. And I'd turn off log if you havn't already. It's not terrible informative. Disabling as a service and running normal mode for a while can give better info.
                        sudo service fr24feed stop
                        sudo fr24feed start

                        Youll get a better visual

                        Then stop it and restart as service (may need reboot as leaves chunks running background)
                        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                        Comment


                        • #13
                          Thanks Oblivian, you do get more info that way

                          Coordinates I get are spot on so I don't think thats the issue. It does say "Connecting to Beast receiver via (exe:///usr/lib/fr24/dump1090 --net --net-http-port 8080 --raw --mlat)" when it starts up although i definitely set it to dvbt

                          Full output below


                          2016-03-30 22:15:35 | [main][i]FR24 Feeder/Decoder
                          2016-03-30 22:15:35 | [main][i]Version: 1.0.18-5/generic
                          2016-03-30 22:15:35 | [main][i]Built on Mar 4 2016 15:21:10 (HEAD-d11ca48.git/Linux/armv7l)
                          2016-03-30 22:15:35 | [main][i]Copyright 2012-2016 Flightradar24 AB
                          2016-03-30 22:15:35 | [main][i]http://flightradar24.com
                          2016-03-30 22:15:35 | [main][i]DNS mode: LIBC
                          2016-03-30 22:15:35 | [main][i]Automatic updates are DISABLED
                          2016-03-30 22:15:35 | ERROR
                          2016-03-30 22:15:35 | [w]Detected --net argument for dump1090, disabling internal RAW feed!
                          2016-03-30 22:15:35 | [w]Detected --net argument for dump1090, disabling internal BS feed!
                          2016-03-30 22:15:35 | [httpd][i]Server started, listening on 0.0.0.0:8754
                          2016-03-30 22:15:35 | [main][i]Reader thread started
                          2016-03-30 22:15:35 | [reader][i]Initializing reader
                          2016-03-30 22:15:35 | [master][i]Starting processing thread
                          2016-03-30 22:15:35 | [reader][i]Connecting to Beast receiver via (exe:///usr/lib/fr24/dump1090 --net --net-http-port 8080 --raw --mlat)
                          2016-03-30 22:15:35 | [main][i]MLAT data feed started
                          2016-03-30 22:15:35 | [reader][i]Connected to the receiver, configuring
                          2016-03-30 22:15:35 | [reader][i]Configured, processing messages
                          2016-03-30 22:15:35 | [mlat][i]Waiting for MLAT configuration
                          Found 1 device(s):
                          0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
                          Found Rafael Micro R820T tuner
                          Max available gain is: 49.60
                          Setting gain to: 49.60
                          Exact sample rate is: 2000000.052982 Hz
                          Gain reported by device: 49.60
                          2016-03-30 22:15:36 | [time][i]Synchronizing time via NTP
                          2016-03-30 22:15:37 | [reader][w]Setting new UTC offset: 0!
                          2016-03-30 22:15:45 | [time][i]Time synchronized correctly, offset +0.0001 seconds
                          2016-03-30 22:15:45 | [main][i]Feed Network client started
                          2016-03-30 22:15:45 | [feed][i]Downloading configuration
                          2016-03-30 22:15:45 | [feed][c]Interval: 5s
                          2016-03-30 22:15:45 | [feed][c]Latitude: xx.xxx
                          2016-03-30 22:15:45 | [feed][c]Longitude: -x.xxxx
                          2016-03-30 22:15:45 | [feed][c]GND: YES
                          2016-03-30 22:15:45 | [feed][c]NonADSB: YES
                          2016-03-30 22:15:45 | [feed][c]Timestamps: optional
                          2016-03-30 22:15:45 | [feed][c]Max range AIR: 350.0nm
                          2016-03-30 22:15:45 | [feed][c]Max range GND: 100.0nm
                          2016-03-30 22:15:45 | [stats][i]Stats thread started
                          2016-03-30 22:15:45 | [feed][i]defined 5 servers
                          2016-03-30 22:15:45 | [feed][n]EGBK15@83.140.21.87:8099/UDP
                          2016-03-30 22:15:45 | [feed][n]connecting
                          2016-03-30 22:15:45 | [feed][n]connected via UDP (fd 7)
                          2016-03-30 22:15:45 | [feed][n]working
                          2016-03-30 22:15:45 | [feed][i]sent 1, filtered 0 AC in 1 packet
                          2016-03-30 22:15:46 | [mlat][i]MLAT configuration received, service ENABLED
                          2016-03-30 22:15:46 | [mlat][i]Starting MLAT with preconfigured position: xx.xx,-x.xx,330.0
                          2016-03-30 22:15:46 | [mlat][i]MLAT bandwidth reduction active, level 1
                          2016-03-30 22:15:46 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
                          2016-03-30 22:15:46 | [mlat][i]Registering MLAT station
                          2016-03-30 22:15:46 | [mlat][i]Registering MLAT station: FAILURE
                          2016-03-30 22:15:47 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
                          2016-03-30 22:15:47 | [mlat][i]Registering MLAT station
                          2016-03-30 22:15:47 | [mlat][i]Registering MLAT station: FAILURE
                          2016-03-30 22:15:48 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
                          2016-03-30 22:15:48 | [mlat][i]Registering MLAT station
                          2016-03-30 22:15:48 | [mlat][i]Registering MLAT station: FAILURE
                          2016-03-30 22:15:49 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
                          2016-03-30 22:15:49 | [mlat][i]Registering MLAT station
                          2016-03-30 22:15:49 | [mlat][i]Registering MLAT station: FAILURE
                          2016-03-30 22:15:50 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
                          2016-03-30 22:15:50 | [mlat][i]Registering MLAT station
                          2016-03-30 22:15:50 | [mlat][i]Registering MLAT station: FAILURE
                          2016-03-30 22:15:50 | [feed][i]sent 3, filtered 0 AC in 1 packet
                          2016-03-30 22:15:51 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
                          2016-03-30 22:15:51 | [mlat][i]Registering MLAT station
                          2016-03-30 22:15:51 | [mlat][i]Registering MLAT station: FAILURE
                          2016-03-30 22:15:52 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
                          2016-03-30 22:15:52 | [mlat][i]Registering MLAT station
                          2016-03-30 22:15:52 | [mlat][i]Registering MLAT station: FAILURE
                          2016-03-30 22:15:53 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
                          2016-03-30 22:15:53 | [mlat][i]Registering MLAT station
                          2016-03-30 22:15:53 | [mlat][i]Registering MLAT station: FAILURE
                          2016-03-30 22:15:54 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
                          2016-03-30 22:15:54 | [mlat][i]Registering MLAT station
                          2016-03-30 22:15:54 | [mlat][i]Registering MLAT station: FAILURE
                          ^C2016-03-30 22:15:55 | [main][i]Terminating on user request
                          EDIT: the MLAT coordinates are much shorter than ADB-s "Starting MLAT with preconfigured position: xx.xx,-x.xx,330.0"
                          Last edited by spudd; 2016-03-30, 21:21.

                          Comment


                          • #14
                            I raised the name change issue with them - confusing and made me think someone had selected beast and not dvbt *shakes head*

                            As long as they appear to be the same location you should be OK. And not out by miles.

                            Pay to copy that to an email and flick to support so they officially get notified. Olov is active on forums but monitoring the bugs on the website more at present.
                            Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                            Comment


                            • #15
                              Oh, have you got the server options enabled in the web config? Can turn them off

                              --net over-rides

                              2016-03-30 22:15:35 | [w]Detected --net argument for dump1090, disabling internal RAW feed!
                              2016-03-30 22:15:35 | [w]Detected --net argument for dump1090, disabling internal BS feed!
                              2016-03-30 22:15:35 | [httpd][i]Server started, listening on 0.0.0.0:8754
                              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                              Comment

                              Working...
                              X