Announcement

Collapse
No announcement yet.

MLAT Driving me mad

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • MLAT Driving me mad

    It says it is enabled and active but its not doing a thing.

    I am using a Pi and the guy closest to me is using a similar setup and his shows as active.

    How can I tell if its working?

  • #2
    Got it sorted, had to reinstall piaware for some reason. But all is working and I am now a happy man.

    Comment


    • #3
      MLAT does not work with locacl feedback from FR24 package. Only PiAware has the ability to feed back from server. I would expect you won't see it doing a thing. Other than saying OK meaning it is uploading non ADSB data to the servers
      Posts not to be taken as official support representation - Just a helpful uploader who tinkers

      Comment


      • #4
        Originally posted by K4RLMORG4N View Post
        Got it sorted, had to reinstall piaware for some reason. But all is working and I am now a happy man.
        Glad it's working for you. Are you up to date on RPi fr24feed too? (currently 1.0.18-5) it prevents MLAT leaks to FR24.

        Comment


        • #5
          Is MAT now working for the Pi Feeders ?

          I only every see the following in log;

          2016-03-29 08:51:36 | [mlat][i]Pinging the server
          2016-03-29 08:51:36 | [mlat][i]Stats 0/0

          Comment


          • #6
            Originally posted by awitty View Post
            Is MAT now working for the Pi Feeders ?

            I only every see the following in log;

            2016-03-29 08:51:36 | [mlat][i]Pinging the server
            2016-03-29 08:51:36 | [mlat][i]Stats 0/0
            yes its working wait for a mlat plane to appear the stats values will change then u knows its working

            Mauritius T-FIMP4 (Offline)
            Mauritius F-FIMP7 (Online)

            Comment


            • #7
              Thanks, but my Mlat status in the log file always reads;

              2016-03-29 16:47:05 | [mlat][i]Stats 0/0

              even thought "Service fr24feed status" reports;

              [ ok ] FR24 Feeder/Decoder Process: running.
              [ ok ] FR24 Stats Timestamp: 2016-03-29 16:45:50.
              [ ok ] FR24 Link: connected [UDP].
              [ ok ] FR24 Radar: T-EGXU10.
              [ ok ] FR24 Tracked AC: 24.
              [ ok ] Receiver: connected (8461 MSGS/0 SYNC).
              [ ok ] FR24 MLAT: ok [UDP].
              [ ok ] FR24 MLAT AC seen: 22.


              So i don't think it's working correctly.

              Incidentally, when was it announced that MLAT for Pi feeders was switched back on ?

              Comment


              • #8
                Originally posted by awitty View Post
                Thanks, but my Mlat status in the log file always reads;

                2016-03-29 16:47:05 | [mlat][i]Stats 0/0

                even thought "Service fr24feed status" reports;

                [ ok ] FR24 Feeder/Decoder Process: running.
                [ ok ] FR24 Stats Timestamp: 2016-03-29 16:45:50.
                [ ok ] FR24 Link: connected [UDP].
                [ ok ] FR24 Radar: T-EGXU10.
                [ ok ] FR24 Tracked AC: 24.
                [ ok ] Receiver: connected (8461 MSGS/0 SYNC).
                [ ok ] FR24 MLAT: ok [UDP].
                [ ok ] FR24 MLAT AC seen: 22.


                So i don't think it's working correctly.

                Incidentally, when was it announced that MLAT for Pi feeders was switched back on ?
                Same issue here; I think it happens because new RPi feeds have to be "evaluated" before:
                Originally posted by vinnyspb View Post
                Please note that you won't see the immediate result on FR24 map. The reason for that is that we want first to evaluate the data and configure our smoothing filters appropriately as normal errors for RPi MLAT can easily be around 10km (this is due to non precise system clock of RPi). That will take some time, but we will all benefit from having smooth trails instead of ugly jumps.
                T-LEVT5

                Comment


                • #9
                  Originally posted by awitty View Post
                  Thanks, but my Mlat status in the log file always reads;

                  2016-03-29 16:47:05 | [mlat][i]Stats 0/0

                  even thought "Service fr24feed status" reports;

                  [ ok ] FR24 Feeder/Decoder Process: running.
                  [ ok ] FR24 Stats Timestamp: 2016-03-29 16:45:50.
                  [ ok ] FR24 Link: connected [UDP].
                  [ ok ] FR24 Radar: T-EGXU10.
                  [ ok ] FR24 Tracked AC: 24.
                  [ ok ] Receiver: connected (8461 MSGS/0 SYNC).
                  [ ok ] FR24 MLAT: ok [UDP].
                  [ ok ] FR24 MLAT AC seen: 22.

                  How did you install yours?
                  I ran the setup script on the website here but when running service fr24feed status don't get anything about MLAT

                  ● fr24feed.service - LSB: Flightradar24 Decoder & Feeder
                  Loaded: loaded (/etc/init.d/fr24feed)
                  Active: active (running) since Wed 2016-03-30 14:23:19 UTC; 1h 19min ago
                  Process: 1074 ExecStop=/etc/init.d/fr24feed stop (code=exited, status=0/SUCCESS)
                  Process: 1103 ExecStart=/etc/init.d/fr24feed start (code=exited, status=0/SUCCESS)
                  CGroup: /system.slice/fr24feed.service
                  ├─1121 /usr/bin/fr24feed -- --monitor-file=/dev/shm/fr24feed.txt --write-pid=/var/run/fr24feed.pid --quiet --log-base=/var/log/fr24feed --log-rotate=2
                  └─1143 /usr/lib/fr24/dump1090 --net --net-http-port 8080 --raw --mlat

                  Mar 30 14:23:19 raspberrypi fr24feed[1103]: Starting FR24 feeder: fr24feed.
                  Mar 30 14:23:19 raspberrypi systemd[1]: Started LSB: Flightradar24 Decoder & Feeder.

                  Comment


                  • #10
                    Originally posted by spudd View Post
                    How did you install yours?
                    I ran the setup script on the website here but when running service fr24feed status don't get anything about MLAT
                    Spudd

                    I used to get that error why my PI was running the Jessie Raspbian build. It worked fine when i reinstalled under Wheezy.

                    try;

                    cat /etc/os-release

                    and see what it says. Mine reads;


                    PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)"
                    NAME="Raspbian GNU/Linux"
                    VERSION_ID="7"
                    VERSION="7 (wheezy)"
                    ID=raspbian
                    ID_LIKE=debian
                    ANSI_COLOR="1;31"
                    HOME_URL="http://www.raspbian.org/"
                    SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
                    BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

                    Comment


                    • #11
                      That's very interesting! I am certainly running the Jessie raspbian build.

                      What kernel version are you using in wheezy?

                      I am running Linux raspberrypi 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux on Raspbian Jessie

                      Comment


                      • #12
                        Originally posted by spudd View Post
                        How did you install yours?
                        I ran the setup script on the website here but when running service fr24feed status don't get anything about MLAT
                        I've just had a look and a play and it seems it's a bug with fr24feed on Jessie.

                        Raspbian Wheezy uses an older method to start and stop services and daemons, and that lets the fr24feed scripts run those diagnostics when "sudo service fr24feed status" is run. However, Raspbian Jessie uses a new system called "systemd" to do it, which is faster and more efficient but it's different enough that it can sometimes tickle bugs.

                        SystemD intercepts the "status" request and instead reports detailed information on the status of the service (the program/daemon only) all by itself, unfortunately this means the fr24feed software doesn't get a chance to add its extra information.

                        The solution is for fr24feed to *not* use "status" as a hook for getting detailed information about the fr24feed service and instead use another term (e.g. "diagnostics".) Alternatively, in order to preserve backwards compatibility with any software and information out there for running on Wheezy, it could trigger on either "diagnostics"/"status" on Wheezy and or only "diagnostics" on Jessie by changing just two lines.

                        Here's a patch that'll do it (also in the file attached)-


                        --- /etc/init.d/fr24feed 2016-03-04 15:17:12.000000000 +0000
                        +++ /etc/init.d/fr24feed.new 2016-04-01 22:03:27.593210225 +0100
                        @@ -157,7 +157,7 @@
                        stop)
                        stop
                        ;;
                        - status)
                        + status|diagnostics)
                        status
                        ;;
                        restart)
                        @@ -170,7 +170,7 @@
                        status_of_proc $DAEMON "fr24feed server"
                        ;;
                        *)
                        - echo "Usage: $0 {start|stop|restart|status}"
                        + echo "Usage: $0 {start|stop|restart|status|diagnostics}"
                        exit 2
                        ;;
                        esac


                        I'll report this to the people behind fr24feed, but to make such a change now, download the attached textfile to your pi and run the following command on it-

                        sudo patch < fr24feed-patch-jessie.txt


                        After doing this, issue-

                        sudo systemctl daemon-reload


                        Then to display the diagnostics on Jessie you can use-

                        sudo service fr24feed diagnostics

                        Hope that helps?

                        Warm Regards
                        Julie
                        x

                        PS Presumably because I'm a newbie here, a message told me this attachment will disappear if not downloaded/viewed within an hour of posting?
                        Attached Files
                        Last edited by geekycow; 2016-04-01, 21:38. Reason: I was wrong, it IS a bug with fr24feed - patch created

                        Comment


                        • #13
                          Originally posted by awitty View Post
                          Thanks, but my Mlat status in the log file always reads;

                          2016-03-29 16:47:05 | [mlat][i]Stats 0/0

                          even thought "Service fr24feed status" reports;

                          [ ok ] FR24 Feeder/Decoder Process: running.
                          [ ok ] FR24 Stats Timestamp: 2016-03-29 16:45:50.
                          [ ok ] FR24 Link: connected [UDP].
                          [ ok ] FR24 Radar: T-EGXU10.
                          [ ok ] FR24 Tracked AC: 24.
                          [ ok ] Receiver: connected (8461 MSGS/0 SYNC).
                          [ ok ] FR24 MLAT: ok [UDP].
                          [ ok ] FR24 MLAT AC seen: 22.


                          So i don't think it's working correctly.

                          Incidentally, when was it announced that MLAT for Pi feeders was switched back on ?
                          Can I ask a question? Given that MLAT was working for you (but not us) do you know what MLAT server you're connected to? It's in the logs (/var/log/fr24feed.) We've not had any luck with the server we've been assigned to (mlat-1.fr24.com) so I'd be interested to know if anyone having even partial success with MLAT is also connected to that server or not.

                          Comment


                          • #14
                            Originally posted by geekycow View Post
                            I've just had a look and a play and it seems it's a bug with fr24feed on Jessie.

                            Raspbian Wheezy uses an older method to start and stop services and daemons, and that lets the fr24feed scripts run those diagnostics when "sudo service fr24feed status" is run. However, Raspbian Jessie uses a new system called "systemd" to do it, which is faster and more efficient but it's different enough that it can sometimes tickle bugs.

                            SystemD intercepts the "status" request and instead reports detailed information on the status of the service (the program/daemon only) all by itself, unfortunately this means the fr24feed software doesn't get a chance to add its extra information.

                            The solution is for fr24feed to *not* use "status" as a hook for getting detailed information about the fr24feed service and instead use another term (e.g. "diagnostics".) Alternatively, in order to preserve backwards compatibility with any software and information out there for running on Wheezy, it could trigger on either "diagnostics"/"status" on Wheezy and or only "diagnostics" on Jessie by changing just two lines.

                            Here's a patch that'll do it (also in the file attached)-


                            --- /etc/init.d/fr24feed 2016-03-04 15:17:12.000000000 +0000
                            +++ /etc/init.d/fr24feed.new 2016-04-01 22:03:27.593210225 +0100
                            @@ -157,7 +157,7 @@
                            stop)
                            stop
                            ;;
                            - status)
                            + status|diagnostics)
                            status
                            ;;
                            restart)
                            @@ -170,7 +170,7 @@
                            status_of_proc $DAEMON "fr24feed server"
                            ;;
                            *)
                            - echo "Usage: $0 {start|stop|restart|status}"
                            + echo "Usage: $0 {start|stop|restart|status|diagnostics}"
                            exit 2
                            ;;
                            esac


                            I'll report this to the people behind fr24feed, but to make such a change now, download the attached textfile to your pi and run the following command on it-

                            sudo patch < fr24feed-patch-jessie.txt


                            After doing this, issue-

                            sudo systemctl daemon-reload


                            Then to display the diagnostics on Jessie you can use-

                            sudo service fr24feed diagnostics

                            Hope that helps?

                            Warm Regards
                            Julie
                            x

                            PS Presumably because I'm a newbie here, a message told me this attachment will disappear if not downloaded/viewed within an hour of posting?
                            Download worked for me.
                            That worked like a charm. I now receive the following diagnostic info from fr24feed

                            sudo service fr24feed diagnostics
                            [ ok ] FR24 Feeder/Decoder Process: running.
                            [ ok ] FR24 Stats Timestamp: 2016-04-02 13:10:33.
                            [ ok ] FR24 Link: connected [UDP].
                            [ ok ] FR24 Radar: T-E*****.
                            [ ok ] FR24 Tracked AC: 27.
                            [ ok ] Receiver: connected (2578 MSGS/0 SYNC).
                            [FAIL] FR24 MLAT: not running ... failed!

                            Comment


                            • #15
                              Regarding the MLAT server question, it appears there are 5. My post yesterday with them in appears to have been deleted.

                              Comment

                              Working...
                              X