Page 41 of 91 FirstFirst ... 31394041424351 ... LastLast
Results 401 to 410 of 901

Thread: Archived - Beta test MLAT software for Raspberry Pi

  1. #401
    Passenger
    Join Date
    Feb 2015
    Location
    Woodland Hills, California, USA
    Posts
    5
    Quote Originally Posted by bhaal View Post
    FA = Flightaware
    FR = Flightradar24

    [...] The trouble is, and as obj has pointed out, even though the data is clearly distinguishable as MLAT data and not ADS-B data from dump1090, fr24feed just assumes it's ADS-B data because it has position information. Therefore, those T-feeders set up that way are sending MLAT positions to FR as ADS-B positions... So, instead of the data properly showing up as MLAT6 or MLAT7 it's show up as [some T-radar...].
    Ah! Finally an explanation for T-KIZA2, which for over a month now has been showing up on FR24 as the radar for almost all northern Los Angeles County MLAT aircraft. Basically almost all MLAT aircraft suddenly disappeared from my area, and now I know why.

    Stacey
    T-KIZA1
    Woodland Hills, California, US

  2. #402
    Passenger
    Join Date
    Aug 2015
    Posts
    17
    Indeed. I feel your pain, neighbor.

    J.R.
    T-KIZA3

  3. #403
    Flight attendant
    Join Date
    Apr 2015
    Location
    Sydney, Australia
    Posts
    68
    Quote Originally Posted by numbat View Post
    Ah! Finally an explanation for T-KIZA2, which for over a month now has been showing up on FR24 as the radar for almost all northern Los Angeles County MLAT aircraft. Basically almost all MLAT aircraft suddenly disappeared from my area, and now I know why.
    We have the same issue here in Sydney - T-YSSY51 is feeding "synthetic" (FA generated) MLAT data to FR... and is probably oblivious to the fact.

    I really wish FlightRadar admin would get off their butts and contact the operators of the T feeders doing this and get them to sort it out. It's not as though they won't know about them - the rest of us whinge about it on here enough
    T-YSBK22

  4. #404
    Passenger
    Join Date
    Feb 2015
    Location
    Woodland Hills, California, USA
    Posts
    5
    I think T-KBUR1 might be doing the same thing. I watched a non-ADS-B Southwest 737 (A8A860, LAX->OAK) go overhead on port 30003, and T-KIZA2 picked it up, then on the other side of the Grapevine it kicked over to T-KBUR1, then T-KMHV1 in Kern County, then T-MLAT2 west of Bakersfield, then T-KOAR1, and now finally back to T-MLAT2 just south of Kettleman City.

    Looks like this is a very common problem. At least FR24 can handle an aircraft apparently going from ADS-B to non-ADS-B, then apparently back to ADS-B in one flight! :-)

    Stacey
    T-KIZA1

  5. #405
    Passenger
    Join Date
    Feb 2015
    Location
    Woodland Hills, California, USA
    Posts
    5

    Feed no longer working

    My feed appears to no longer be working. The last accepted AC was:

    Code:
    2015-10-17 03:49:31 | [mlat][i]Pinging the server
    2015-10-17 03:49:31 | [mlat][i]Stats 564633/14
    2015-10-17 03:49:35 | [feed][i]sent 1 AC in 1 packet
    2015-10-17 03:49:52 | [mlat][i]Pinging the server
    2015-10-17 03:49:52 | [mlat][i]Stats 564633/0
    Here's the startup sequence:

    Code:
    2015-10-17 19:02:30 | [main][i]FR24 Feeder/Decoder [0x02117000]
    2015-10-17 19:02:30 | [main][i]Version: 1.0.14-11/generic
    2015-10-17 19:02:30 | [main][i]Built on 20150828-0958 (r:master-8c35732.git/Linux/armv7l)
    2015-10-17 19:02:30 | [main][i]Automatic updates are ENABLED
    2015-10-17 19:02:30 | [main][i]Copyright 2008-2015 (c) Piotr Pawluczuk
    2015-10-17 19:02:30 | [main][i]Flightradar24 AB(http : //flightradar24.com)
    2015-10-17 19:02:30 | [main][i]DNS mode: LIBC
    2015-10-17 19:02:30 | ERROR
    2015-10-17 19:02:30 | [w]Detected --net argument for dump1090, disabling internal BS feed!
    2015-10-17 19:02:30 | [main][i]Reader 0 started
    2015-10-17 19:02:30 | [main][i]MLAT data feed started
    2015-10-17 19:02:30 | [mlat][i]Waiting for MLAT configuration
    2015-10-17 19:02:30 | [reader][i][0]Initializing reader
    2015-10-17 19:02:30 | [reader][i][0]Connecting to Generic receiver via (exe : ///usr/lib/fr24/dump1090 --net --raw --mlat)
    2015-10-17 19:02:30 | [reader][i][0]Connected to the receiver, authenticating
    2015-10-17 19:02:30 | [master][i]Starting processing thread
    2015-10-17 19:02:30 | [httpd][i]Server started, listening on 0.0.0.0:8754
    2015-10-17 19:02:30 | [reader][i][0]Authenticated, processing messages
    2015-10-17 19:02:31 | [time][i]Synchronizing time via NTP
    2015-10-17 19:02:35 | [time][i]Time synchronized correctly, offset +0.0023 seconds
    2015-10-17 19:02:35 | [main][i]Feed Network client started
    2015-10-17 19:02:35 | [feed][i]Downloading configuration
    2015-10-17 19:02:35 | [feed][c]Interval: 5s
    2015-10-17 19:02:35 | [feed][c]Latitude: [deleted]
    2015-10-17 19:02:35 | [feed][c]Longitude: [deleted]
    2015-10-17 19:02:35 | [feed][c]GND: YES
    2015-10-17 19:02:35 | [feed][c]NonADSB: YES
    2015-10-17 19:02:35 | [feed][c]Timestamps: optional
    2015-10-17 19:02:35 | [feed][c]Max range AIR: 350.0nm
    2015-10-17 19:02:35 | [feed][c]Max range GND: 100.0nm
    2015-10-17 19:02:35 | [feed][i]defined 1 server
    2015-10-17 19:02:35 | [feed][n]KIZA1@83.140.21.66:8099/UDP
    2015-10-17 19:02:35 | [feed][n]connecting
    2015-10-17 19:02:35 | [stats][i]Stats thread started
    2015-10-17 19:02:36 | [mlat][i]MLAT configuration received, service ENABLED
    2015-10-17 19:02:36 | [mlat][i]Starting MLAT with preconfigured position: [deleted]
    2015-10-17 19:02:36 | [mlat][i]MLAT bandwidth reduction active, level 1
    2015-10-17 19:02:36 | [mlat][i]Configuring UDP connection udp : //usa-2.fr24.com:19788
    2015-10-17 19:02:36 | [mlat][i]Registering MLAT station
    2015-10-17 19:02:56 | [mlat][i]Registering MLAT station: FAILURE
    2015-10-17 19:02:57 | [feed][n]connected via TCP
    2015-10-17 19:02:57 | [feed][n]switching to UDP
    2015-10-17 19:02:57 | [feed][n]working
    2015-10-17 19:02:57 | [mlat][i]Configuring UDP connection udp : //usa-2.fr24.com:19788
    2015-10-17 19:02:57 | [mlat][i]Registering MLAT station
    2015-10-17 19:02:58 | [mlat][i]Registering MLAT station: SUCCESS
    2015-10-17 19:03:00 | [mlat][i]Pinging the server
    Then after a few minutes:

    Code:
    2015-10-17 19:12:20 | [mlat][i]Stats 564633/0
    2015-10-17 19:12:32 | [feed][n]ping 19
    2015-10-17 19:12:35 | [time][i]Synchronizing time via NTP
    2015-10-17 19:12:36 | [stats][e]Cached feed_id=15792 for network T
    2015-10-17 19:12:36 | [stats][i]sent 16 bytes
    2015-10-17 19:12:39 | [time][i]Time synchronized correctly, offset +0.0016 seconds
    2015-10-17 19:12:46 | [reader][w][0]Global timeout exceeded, 0 msgs, 0 resyncs, reconnecting
    2015-10-17 19:12:46 | [reader][i][0]Connection terminated
    2015-10-17 19:12:46 | [main][i]Terminating child process 17482 with SIGETERM
    2015-10-17 19:12:50 | [mlat][i]Pinging the server
    2015-10-17 19:12:50 | [mlat][i]Stats 564633/0
    2015-10-17 19:12:51 | [reader][i][0]Connecting to Generic receiver via (exe:///usr/lib/fr24/dump1090 --net --raw --mlat)
    2015-10-17 19:12:51 | [reader][i][0]Connected to the receiver, authenticating
    2015-10-17 19:12:51 | [reader][i][0]Authenticated, processing messages
    2015-10-17 19:13:02 | [feed][n]ping 20
    2015-10-17 19:13:19 | [mlat][i]Pinging the server
    Thanks for any help,

    numbat
    T-KIZA1

    p.s. I had to break up things that look like links to get past the forum link filter.

  6. #406
    Passenger
    Join Date
    Feb 2013
    Posts
    2
    These non-ADS-B MLAT tracks are causing issues in the San Francisco Bay Area - I'm seeing the same thing, but unfortunately we have two different T-SJCNN receivers posting two different aircraft coordinates with different ICAO numbers for the same aircraft! So flightradar24 is showing TWO airplanes where there are none actually transmitting ADS-B coordinates.

    I'm all for more aircraft but these need to be handled properly (throwing away the aircraft with the invalid ICAO and categorizing the valid track as MLAT would be nice). Seeing two aircraft near each other with nearly the same altitude is a bit surprising but I've gotten used to filtering it mentally. The inaccuracy of the MLAT receivers is a little jarring as well when you're used to observing solid ADS-B coordinates too but that is another topic.

  7. #407
    Passenger
    Join Date
    Feb 2015
    Location
    Woodland Hills, California, USA
    Posts
    5
    Quote Originally Posted by falcongsr View Post
    TSo flightradar24 is showing TWO airplanes where there are none actually transmitting ADS-B coordinates.
    Yes, at various times tonight there have been two Goodyear Blimps over the Cal UCLA game at the Rose Bowl; T-KBUR1 reporting Flightaware MLAT.

    blimp.jpg

  8. #408
    Passenger
    Join Date
    May 2015
    Posts
    11
    For all you FR24 feeders, check out adsbexchange.com - completely unfiltered and can be fed in addition to FR24 with a simple command.


    Sent from my iPhone using Tapatalk

  9. #409
    Passenger
    Join Date
    Oct 2015
    Location
    Romford JO01CO
    Posts
    3

    Raspberry Pi problem with RTL2838UH Dongle - Not receiving any aircraft to upload

    Hi there,

    I have been using Windows 10 to share flight data without problems.

    I decided to use my Raspberry Pi to share data with Flightradar24 and followed the online installation instructions so that I could use my RTL2838UH Dongle. I am not sure why, but I am not receiving any aircraft to upload and I'm uncertain what to do next.

    My set-up is as follows:
    Raspberry Pi type B
    a powered hub
    a loft antenna fed with a short length of RG213

    I used the following command "service fr24feed status" and this is the result.

    pi@raspberrypi ~ $ service fr24feed status
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2015-10-28 13:45:11.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-EGLC51.
    [ ok ] FR24 Tracked AC:.
    [ ok ] Receiver: connected (0 MSGS/0 SYNC).
    [ ok ] FR24 MLAT: ok [UDP].
    [ ok ] FR24 MLAT AC seen: 0.

    My home location is London, so there are plenty of aircraft nearby.

    I have checked my antenna and it is connected.

    Could it be a driver issue?

    I am new to Raspberry Pi, so any help would be gratefully received.

    Many thanks,

    Bob.

  10. #410
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    5,028
    If you drop the service you will get more output to diagnose from

    sudo service fr24feed stop
    sudo fr24feed start

    That will let you see the startup procedure and any errors/issues contacting the USB stick. Does the version have the right frequency range?
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •