Announcement

Collapse
No announcement yet.

MLAT enabled but not running

Collapse
X
Collapse
 
  • Page of 6
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 5 6 template Next
  • #16
    Disabled those but still no joy.

    Will email support about the above

    Comment

    • #17
      Hmmmm the MLAT coordinates do seem to be quite a way off by 350m. Is there anyway to manually set the MLAT coordinates? I'm not sure where it is getting them from

      Comment

      • #18
        It seems it's rounding up the last 2 digits for longitude and latitude and that rounding up produces about a 350m offset from my actual coordinates used by ADS-b

        Comment

        • #19
          Originally posted by Oblivian View Post
          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)
          Yeah, already saw the posts about wrong location and checked them - definitely correct Long/Lat etc. Didn't realise it'd give extra info run foreground though. This is what I get with MLAT enabled-


          pi@pollypi:~ $ sudo fr24feed start
          2016-03-30 22:59:06 | [main][i]FR24 Feeder/Decoder
          2016-03-30 22:59:06 | [main][i]Version: 1.0.18-5/generic
          2016-03-30 22:59:06 | [main][i]Built on Mar 4 2016 15:21:10 (HEAD-d11ca48.git/Linux/armv7l)
          2016-03-30 22:59:06 | [main][i]Copyright 2012-2016 Flightradar24 AB
          2016-03-30 22:59:06 | [main][i]flightradar24.com
          2016-03-30 22:59:06 | [main][i]DNS mode: LIBC
          2016-03-30 22:59:06 | [main][i]Automatic updates are DISABLED
          2016-03-30 22:59:06 | ERROR
          2016-03-30 22:59:06 | [httpd][i]Server started, listening on 0.0.0.0:8754
          2016-03-30 22:59:06 | [main][i]Reader thread started
          2016-03-30 22:59:06 | [reader][i]Initializing reader
          2016-03-30 22:59:06 | [master][i]Starting processing thread
          2016-03-30 22:59:06 | [reader][i]Connecting to Beast receiver via (exe:///usr/lib/fr24/dump1090 --net --raw --mlat)
          2016-03-30 22:59:06 | [main][i]MLAT data feed started
          2016-03-30 22:59:06 | [reader][i]Connected to the receiver, configuring
          2016-03-30 22:59:06 | [reader][i]Configured, processing messages
          2016-03-30 22:59:06 | [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:59:07 | [reader][w]Setting new UTC offset: 0!
          2016-03-30 22:59:07 | [time][i]Synchronizing time via NTP
          2016-03-30 22:59:10 | [time][i]Time synchronized correctly, offset -0.0006 seconds
          2016-03-30 22:59:10 | [main][i]Feed Network client started
          2016-03-30 22:59:10 | [feed][i]Downloading configuration
          2016-03-30 22:59:10 | [feed][c]Interval: 5s
          2016-03-30 22:59:10 | [feed][c]Latitude: (deleted here for privacy reasons but correct - matched against Google Maps to be sure)
          2016-03-30 22:59:10 | [feed][c]Longitude: (deleted here for privacy reasons but correct - matched against Google Maps to be sure)
          2016-03-30 22:59:10 | [feed][c]GND: YES
          2016-03-30 22:59:10 | [feed][c]NonADSB: YES
          2016-03-30 22:59:10 | [feed][c]Timestamps: optional
          2016-03-30 22:59:10 | [feed][c]Max range AIR: 350.0nm
          2016-03-30 22:59:10 | [feed][c]Max range GND: 100.0nm
          2016-03-30 22:59:10 | [stats][i]Stats thread started
          2016-03-30 22:59:10 | [feed][i]defined 5 servers
          2016-03-30 22:59:10 | [feed][n](deleted for privacy reasons)@83.140.21.87:8099/UDP
          2016-03-30 22:59:10 | [feed][n]connecting
          2016-03-30 22:59:10 | [feed][n]connected via UDP (fd 8)
          2016-03-30 22:59:10 | [feed][n]working
          2016-03-30 22:59:11 | [feed][i]sent 2, filtered 0 AC in 1 packet
          2016-03-30 22:59:11 | [mlat][i]MLAT configuration received, service ENABLED
          2016-03-30 22:59:11 | [mlat][i]Starting MLAT with preconfigured position: (deleted here for privacy reasons but correct - matched against Google Maps to be sure)
          2016-03-30 22:59:11 | [mlat][i]MLAT bandwidth reduction active, level 1
          2016-03-30 22:59:11 | [mlat][i]Configuring UDP connection newbiesoitwontletmepostthisifitlookslikealinkudp colon slash slash mlat-1.fr24.com:19788
          2016-03-30 22:59:11 | [mlat][i]Registering MLAT station
          2016-03-30 22:59:11 | [mlat][i]Registering MLAT station: FAILURE
          2016-03-30 22:59:12 | [mlat][i]Configuring UDP connection newbiesoitwontletmepostthisifitlookslikealinkudp colon slash slash mlat-1.fr24.com:19788
          2016-03-30 22:59:12 | [mlat][i]Registering MLAT station
          2016-03-30 22:59:12 | [mlat][i]Registering MLAT station: FAILURE
          2016-03-30 22:59:13 | [mlat][i]Configuring UDP connection newbiesoitwontletmepostthisifitlookslikealinkudp colon slash slash mlat-1.fr24.com:19788
          2016-03-30 22:59:13 | [mlat][i]Registering MLAT station
          2016-03-30 22:59:13 | [mlat][i]Registering MLAT station: FAILURE
          2016-03-30 22:59:14 | [mlat][i]Configuring UDP connection newbiesoitwontletmepostthisifitlookslikealinkudp colon slash slash mlat-1.fr24.com:19788
          2016-03-30 22:59:14 | [mlat][i]Registering MLAT station
          2016-03-30 22:59:14 | [mlat][i]Registering MLAT station: FAILURE
          2016-03-30 22:59:15 | [mlat][i]Configuring UDP connection newbiesoitwontletmepostthisifitlookslikealinkudp colon slash slash mlat-1.fr24.com:19788
          2016-03-30 22:59:15 | [mlat][i]Registering MLAT station
          2016-03-30 22:59:15 | [mlat][i]Registering MLAT station: FAILURE
          2016-03-30 22:59:16 | [feed][i]sent 5, filtered 0 AC in 1 packet
          2016-03-30 22:59:16 | [mlat][i]Configuring UDP connection newbiesoitwontletmepostthisifitlookslikealinkudp colon slash slash mlat-1.fr24.com:19788
          2016-03-30 22:59:16 | [mlat][i]Registering MLAT station
          2016-03-30 22:59:16 | [mlat][i]Registering MLAT station: FAILURE


          Happy to supply the deleted bits on a one-to-one basis - by default I thought it best to trim if I'm posting publicly on a forum - although I'm not sure how realistic it is to keep the location private anyway.

          Comment

          • #20
            Interesting. Difference being now, new users. And using bundled Dump1090. I note my working one is using DUmp1090-MU (bundled with Piaware but I installed independantly)

            I wonder if these make a diff too. Hopefully support come back with a valid one, but if soemones happy to tinker, worth a shot.
            Posts not to be taken as official support representation - Just a helpful uploader who tinkers

            Comment

            • #21
              Originally posted by spudd View Post
              It seems it's rounding up the last 2 digits for longitude and latitude and that rounding up produces about a 350m offset from my actual coordinates used by ADS-b
              That's interesting, it's the same for me to. My offset is 320m.

              Comment

              • #22
                Originally posted by geekycow View Post
                That's interesting, it's the same for me to. My offset is 320m.
                Good to know its not just me.
                I have emailed support with this, it might be worth you doing it too

                No idea if this is the cause for MLAT not working but it seems like this would be a real issue for MLAT

                Comment

                • #23
                  Originally posted by spudd View Post
                  Good to know its not just me.
                  I have emailed support with this, it might be worth you doing it too

                  No idea if this is the cause for MLAT not working but it seems like this would be a real issue for MLAT
                  Good idea, will do.

                  Comment

                  • #24
                    Out of curiosity, what firewall are you running?

                    If i look through localhost:8754/monitor.txt the MLAT error there is still stating mlat_problem="udp-firewall" so this maybe an independent issue from the coordinates problem

                    Comment

                    • #25
                      350m isn't really a big gap. When you are taking the altitudes and speed they go. I can't recall the exact distance, but its only over something like 1.2km it has a real detrimental effect
                      Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                      Comment

                      • #26
                        I keep having this problem:

                        [mlat][w]Could not ping MLAT server, result=-1000, number of errors=1.

                        And always have zero for -> [mlat][i]Stats 0/0

                        Emailed support, no reply yet.

                        2016-03-30 14:48:35 | [main][i]FR24 Feeder/Decoder
                        2016-03-30 14:48:35 | [main][i]Version: 1.0.18-5/generic
                        2016-03-30 14:48:35 | [main][i]Built on Mar 4 2016 15:21:10 (HEAD-d11ca48.git/Linux/armv7l)
                        2016-03-30 14:48:35 | [main][i]Copyright 2012-2016 Flightradar24 AB
                        2016-03-30 14:48:35 | [main][i]http://flightradar24.com
                        2016-03-30 14:48:35 | [main][i]DNS mode: LIBC
                        2016-03-30 14:48:35 | [main][i]Automatic updates are DISABLED
                        2016-03-30 14:48:35 | [httpd][e]bind function failed, errno: 98
                        2016-03-30 14:48:35 | [httpd][d]Master thread terminated
                        2016-03-30 14:48:35 | [main][i]Reader thread started
                        2016-03-30 14:48:35 | [main][i]MLAT data feed started
                        2016-03-30 14:48:35 | [master][i]Starting processing thread
                        2016-03-30 14:48:35 | [reader][i]Initializing reader
                        2016-03-30 14:48:35 | [mlat][i]Waiting for MLAT configuration
                        2016-03-30 14:48:35 | [reader][i]Connecting to Beast receiver via (tcp://localhost:30005@Cg)
                        2016-03-30 14:48:35 | [reader][i]Connected to the receiver, configuring
                        2016-03-30 14:48:35 | [reader][i]Configured, processing messages
                        2016-03-30 14:48:35 | [reader][w]Setting new UTC offset: 0!
                        2016-03-30 14:48:36 | [time][i]Synchronizing time via NTP
                        2016-03-30 14:48:44 | [time][i]Time synchronized correctly, offset +0.0005 seconds
                        2016-03-30 14:48:44 | [main][i]Feed Network client started
                        2016-03-30 14:48:44 | [feed][i]Downloading configuration
                        2016-03-30 14:48:45 | [feed][c]Interval: 5s
                        2016-03-30 14:48:45 | [feed][c]Latitude: 34.2028
                        2016-03-30 14:48:45 | [feed][c]Longitude: -118.6926
                        2016-03-30 14:48:45 | [feed][c]GND: YES
                        2016-03-30 14:48:45 | [feed][c]NonADSB: YES
                        2016-03-30 14:48:45 | [feed][c]Timestamps: optional
                        2016-03-30 14:48:45 | [feed][c]Max range AIR: 350.0nm
                        2016-03-30 14:48:45 | [feed][c]Max range GND: 100.0nm
                        2016-03-30 14:48:45 | [stats][i]Stats thread started
                        2016-03-30 14:48:45 | [feed][i]defined 5 servers
                        2016-03-30 14:48:45 | [feed][n]KIZA3@83.140.21.66:8099/UDP
                        2016-03-30 14:48:45 | [feed][n]connecting
                        2016-03-30 14:48:45 | [mlat][i]MLAT configuration received, service ENABLED
                        2016-03-30 14:48:45 | [mlat][i]Starting MLAT with preconfigured position: 34.20,-118.69,1280.0
                        2016-03-30 14:48:45 | [mlat][i]MLAT bandwidth reduction active, level 1
                        2016-03-30 14:48:45 | [mlat][i]Configuring UDP connection udp://usa-2.fr24.com:19788
                        2016-03-30 14:48:45 | [mlat][i]Registering MLAT station
                        2016-03-30 14:48:45 | [mlat][i]Registering MLAT station: SUCCESS
                        2016-03-30 14:48:55 | [mlat][i]Pinging the server
                        2016-03-30 14:48:55 | [mlat][i]Stats 0/0
                        2016-03-30 14:49:06 | [feed][n]connected via TCP (fd 8)
                        2016-03-30 14:49:06 | [feed][n]working
                        2016-03-30 14:49:06 | [feed][i]sent 1, filtered 0 AC in 1 packet
                        2016-03-30 14:49:11 | [feed][i]sent 21, filtered 0 AC in 1 packet
                        2016-03-30 14:49:15 | [mlat][i]Pinging the server
                        2016-03-30 14:49:15 | [mlat][i]Stats 0/0
                        2016-03-30 14:49:16 | [feed][i]sent 19, filtered 0 AC in 1 packet
                        2016-03-30 14:49:21 | [feed][i]sent 21, filtered 0 AC in 1 packet
                        2016-03-30 14:49:26 | [feed][i]sent 23, filtered 0 AC in 1 packet
                        2016-03-30 14:49:32 | [feed][i]sent 24, filtered 0 AC in 1 packet
                        2016-03-30 14:49:35 | [mlat][i]Pinging the server
                        2016-03-30 14:49:36 | [mlat][w]Could not ping MLAT server, result=-1000, number of errors=1
                        2016-03-30 14:49:37 | [feed][i]sent 20, filtered 0 AC in 1 packet
                        2016-03-30 14:49:42 | [feed][i]sent 20, filtered 0 AC in 1 packet
                        2016-03-30 14:49:47 | [feed][i]sent 22, filtered 0 AC in 1 packet
                        2016-03-30 14:49:48 | [feed][n]syncing stream: 0
                        2016-03-30 14:49:52 | [feed][i]sent 23, filtered 0 AC in 1 packet
                        2016-03-30 14:49:57 | [feed][i]sent 20, filtered 0 AC in 1 packet
                        2016-03-30 14:50:02 | [feed][i]sent 25, filtered 0 AC in 1 packet
                        2016-03-30 14:50:07 | [feed][i]sent 23, filtered 0 AC in 1 packet
                        2016-03-30 14:50:12 | [mlat][i]Pinging the server
                        2016-03-30 14:50:12 | [mlat][w]Could not ping MLAT server, result=-1000, number of errors=2
                        2016-03-30 14:50:12 | [mlat][i]Terminating connection
                        2016-03-30 14:50:12 | [feed][i]sent 24, filtered 0 AC in 1 packet
                        2016-03-30 14:50:13 | [mlat][i]Configuring UDP connection udp://usa-2.fr24.com:19788
                        2016-03-30 14:50:13 | [mlat][i]Registering MLAT station
                        2016-03-30 14:50:13 | [mlat][i]Registering MLAT station: SUCCESS
                        2016-03-30 14:50:17 | [feed][i]sent 26, filtered 0 AC in 1 packet
                        2016-03-30 14:50:21 | [mlat][i]Pinging the server
                        2016-03-30 14:50:21 | [mlat][i]Stats 0/0
                        2016-03-30 14:50:22 | [feed][i]sent 24, filtered 0 AC in 1 packet
                        2016-03-30 14:50:28 | [feed][i]sent 23, filtered 0 AC in 1 packet
                        2016-03-30 14:50:33 | [feed][i]sent 23, filtered 0 AC in 1 packet
                        2016-03-30 14:50:38 | [feed][i]sent 25, filtered 0 AC in 1 packet
                        2016-03-30 14:50:42 | [mlat][i]Pinging the server
                        2016-03-30 14:50:42 | [mlat][i]Stats 0/0

                        Comment

                        • #27
                          Originally posted by Oblivian View Post
                          350m isn't really a big gap. When you are taking the altitudes and speed they go. I can't recall the exact distance, but its only over something like 1.2km it has a real detrimental effect
                          I remember reading in a thread that even a tiny time offset on the pi can cause the plane to be out by miles, surely a receiver being 350m off would also have this affect? I maybe wrong and it's late for working out the maths.

                          I see in the monitor.txt file it states mlat-mode="UDP". Is there a TCP mode?
                          Last edited by spudd; 2016-03-30, 23:05.

                          Comment

                          • #28
                            Originally posted by KK6LDW View Post
                            I keep having this problem:

                            [mlat][w]Could not ping MLAT server, result=-1000, number of errors=1.

                            And always have zero for -> [mlat][i]Stats 0/0

                            Emailed support, no reply yet.
                            Thats it being dropped.. slightly diff issue (and don't beleive the 0/0 stats) that some of us are also seeing. At least yours reregisters.

                            And do you actually have a beast, seems strange to be running of 30005 which is the beast format output of dump1090 - AVRtcp to 30002 is confirmed, but not sure itll work from 30005 as modified data format.
                            Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                            Comment

                            • #29
                              Originally posted by KK6LDW View Post
                              I keep having this problem:

                              [mlat][w]Could not ping MLAT server, result=-1000, number of errors=1.

                              And always have zero for -> [mlat][i]Stats 0/0

                              Emailed support, no reply yet.
                              Being unable to "ping" (if they really mean ICMP PING packets) can be caused by ICMP filtering - this may either be caused by your ISP, your firewall, a network peer blocking them or (unlikely) the remote host blocking them.

                              Comment

                              • #30
                                Originally posted by Oblivian View Post
                                Thats it being dropped.. slightly diff issue (and don't beleive the 0/0 stats) that some of us are also seeing. At least yours reregisters.

                                And do you actually have a beast, seems strange to be running of 30005 which is the beast format output of dump1090 - AVRtcp to 30002 is confirmed, but not sure itll work from 30005 as modified data format.
                                Even stranger since my settings in fr24feed.ini are:

                                receiver="avr-tcp"
                                fr24key="*mykeyhere*"
                                host="127.0.0.1:30002"
                                bs="no"
                                raw="no"
                                logmode="1"
                                windowmode="0"
                                mpx="no"
                                mlat="yes"
                                mlat-without-gps="yes"
                                Last edited by KK6LDW; 2016-03-30, 23:11.

                                Comment

                                Previous 1 2 3 4 5 6 template Next
                                Working...
                                X

                                We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                                By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                                I Agree