Announcement

Collapse
No announcement yet.

FR24 MLAT Fail

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

    FR24 MLAT Fail

    Does anyone know how to fix this? I’ve this status message on my Raspberry Pi2:

    [FAIL] FR24 MLAT: not running ... failed!

    #2
    You could try http://192.168.1.xxx:8754/restart.html where xxx is the actual address of your Pi2

    Comment


      #3
      Unless your config is 'DVBT' (don't change to that if it is not!!!!) so it tags it using the proprietary dump1090 fork, they don't want to know about it anyway. So safe to ignore.
      Posts not to be taken as official support representation - Just a helpful uploader who tinkers

      Comment


        #4
        The receiver is a ModeS Beast (TCP).

        Comment


          #5
          I have one too. And for a while it let me continue to contribute mlat tagged data.

          But users have found it change to 'not permitted' or gets disabled. Can't find the reference off hand but more or less stated if you are feeding other aggregators turn it off. Which most people do.

          Limits it to the piaware image which more or less uses their dump1090-mutability fork and sticks only

          I'll check the status of mine when I get home but have a feeling it says not permitted
          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

          Comment


            #6
            I’m feeding only to Flightradar24.

            Comment


              #7
              That still bypasses needing dump1090-mutability and is read directly by the reader thread of fr24feed as it was the original base the software was designed for (beaglebone).

              However that's now outside what the expected mlat data used is.

              But they don't feed the results back to users. And only the website can make use of it.

              So it's not really an issue. Or an error. And safe to ignore.
              It's all but back to square one before mlat was enabled given they told everyone else who does to switch it off.

              Here was the original detail from 2016
              ...or am I doing something wrong? :p Running it with the bundled mr-dump1090 as the bundled dump1090 doesn't have an "--mlat" flag. Seeing plenty of MLAT running messages, but the log file is full of "[mlat][i]Stats 0/0". Thanks.


              And since then it was updated to backtrack
              Lately I have come to the conclusion that T-xxxx receivers based on Raspberrys og other Linux-variants DO NOT really contribute to the MLAT position calculation in FR24 (I would like to be proven wrong). At my local airfield (EKRD, Denmark) the flying club hosts a FR24 provide receiver F-EKRD1. Other F-receivers are located 20


              And as you'll see from the rest of that 2nd thread. Tumbleweeds as to why it still shows for non dvbt selection.


              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

              Comment


                #8
                Nuff said really.

                Check your webpage status. It's been killed for everything but dvbt.
                You do not have permission to view this gallery.
                This gallery has 1 photos.
                Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                Comment

                Working...
                X