Page 15 of 91 FirstFirst ... 513141516172565 ... LastLast
Results 141 to 150 of 901

Thread: Archived - Beta test MLAT software for Raspberry Pi

  1. #141
    Purser
    Join Date
    Jan 2015
    Location
    Kallangur, Brisbane
    Posts
    168
    Does this MLAT version of fr24feed expose the MLAT positions in a beast/basestation feed? so they can be plotted in VRS?

  2. #142
    Purser
    Join Date
    Jun 2012
    Location
    Bangkok
    Posts
    100
    Upgrade to 1.0.14-5 breaks my FR24 and FA. Used to run smoothly with dump1090 mutability. Have to scratch my head finding way to make them works again.

    Kanok


    Sent from my iPad using Tapatalk
    T-VTBD1 : RadarBox 3km North of VTBD
    T-VTBD2 : RPi MLAT 300m South of VTBD


  3. #143
    Passenger
    Join Date
    Nov 2014
    Posts
    31
    Quote Originally Posted by bhaal View Post
    I hope I am not breaking a cardinal rule by talking about other feeders

    You have to let the fr24feeder and it's version of dump1090 start first. Then the FA feeder can connect to the same dump1090, but you need to configure FA's MLAT beta so it doesn't try and feed MLAT positions back to dump1090 if you go through their forum post for their Pi MLAT beta test it will tell you how to do this (it's in relation to viewing MLAT data in VRS without sending it into dump1090 for display on it's own webpage)...
    The simplest way to disable the feedback entirely is:
    Code:
    $ sudo piaware-config -mlatResults 0
    $ sudo service piaware restart
    Or as you say you can use piaware-config -mlatResultsFormat if you do want to receive MLAT results but show them separately e.g. in VRS.

    FWIW, at the time this was released some weeks ago I contacted FR24 with details of how the feedback mechanism works and how to identify and ignore those messages if they want, but I've had no response at all.
    Planefinder did respond and their feeder now directly handles that with no special config needed.

    Note that the FlightAware mlat client requires an unmodified 12MHz timestamp as produced by stock dump1090 / dump1090-mutability / the Mode-S Beast / etc. This currently works with the modified FR24 dump1090 because the FR24 modifications only mangle the timestamp on the "raw" AVR output, and FlightAware uses the "binary" Beast output. That's mostly luck, though. I'd encourage FR24 to use a separate port for their modified timestamps to avoid breaking other software.

  4. #144
    Purser
    Join Date
    Jan 2015
    Location
    Kallangur, Brisbane
    Posts
    168
    Quote Originally Posted by obj View Post
    FWIW, at the time this was released some weeks ago I contacted FR24 with details of how the feedback mechanism works and how to identify and ignore those messages if they want, but I've had no response at all.
    Planefinder did respond and their feeder now directly handles that with no special config needed.

    Note that the FlightAware mlat client requires an unmodified 12MHz timestamp as produced by stock dump1090 / dump1090-mutability / the Mode-S Beast / etc. This currently works with the modified FR24 dump1090 because the FR24 modifications only mangle the timestamp on the "raw" AVR output, and FlightAware uses the "binary" Beast output. That's mostly luck, though. I'd encourage FR24 to use a separate port for their modified timestamps to avoid breaking other software.
    I really hope FR24 get on board with this. I am using this setup and it's working well, although I really wish MLAT planes could be colorised in VRS, I'm looking at the JS for VRS but I think the main code base for VRS needs mods first, as has been mentioned when people have asked questions about plane color changes... And hopefully "luck" prevails
    T-YBBN50 - Kallangur, QLD, Australia

  5. #145
    Purser
    Join Date
    Jan 2015
    Location
    Kallangur, Brisbane
    Posts
    168
    vinnyspb,

    Can I make a suggestion that a stick is made or the initial post for this thread is edited to contain a howto for people who feed multiple sites, for instance FR and FA, describing how to setup the MLAT version of fr24feed so that both FR and FA can benefit from these advances, because I've seen a number of people not going ahead with the upgrade because it breaks feeding to other sites without clear instructions on how to do things so it works all round? I replied to the Aussie feeders thread with a quick howto because there was some complaint about all this..

    Also, thanks for all the work you and whoever else has worked on this have put in! It helps me see a lot more aircraft then I used to! Now I can sometimes see that pesky police helicopter which never turns it's ADS-B transponder on! Good work! But we need more feeders taking part, but I fear they won't unless they know how to make it work with as little effort as possible.. Thanks
    T-YBBN50 - Kallangur, QLD, Australia

  6. #146
    Passenger
    Join Date
    Jan 2013
    Location
    next to Linz airport
    Posts
    43
    i also upgraded to 1.0.14-5. all stopped working. --signup and choosing MLAT causes only to choose usb dongele as receiver
    the version before gave me the option to use sbs1/3.
    now it is gone. when i signup again and use MLAT no i get all hardware options back,
    but when i switch on MLAT at the webinterface all is hanging up and webinterface is gone.
    Last edited by LOWL1; 2015-07-18 at 15:38.

  7. #147
    Purser
    Join Date
    Jan 2015
    Location
    Kallangur, Brisbane
    Posts
    168
    So, going back to my NTP issue... can an option to turn off ntp sync be added? or use the localhost ntp server? I can see that fr24feed is going it alone and using pool.ntp.org but for some reason it's not using any local servers by default.. Just would think that as you are relying on ADS-B transponder timestamps for then the local timestamp could be taken from system clock.. If anything, check for presence of ntp and make sure its running..? And Raspbian installs ntp by default..

    I don't know what to suggest, I cannot see why fr24feed is not getting NTP sync very often... I have been watching the ntp traffic from that machine via my border router and ALL requests are being answered. Is there a debug mode which might expose the ntp requests and the responses and why they are being disregarded? Help?
    T-YBBN50 - Kallangur, QLD, Australia

  8. #148
    Passenger
    Join Date
    Jan 2013
    Location
    next to Linz airport
    Posts
    43
    #146
    found a solution:
    --signup without MLAT and change mlat to yes in fr24feed.ini not in webinterface.
    restart service - ok!

  9. #149
    Purser
    Join Date
    Jan 2015
    Location
    Kallangur, Brisbane
    Posts
    168
    Quote Originally Posted by LOWL1 View Post
    #146
    found a solution:
    --signup without MLAT and change mlat to yes in fr24feed.ini not in webinterface.
    restart service - ok!
    From what I have read the mlat feeding only works with the DVB-T dongles, no other inputs at this stage..
    T-YBBN50 - Kallangur, QLD, Australia

  10. #150
    Passenger
    Join Date
    Jan 2013
    Location
    next to Linz airport
    Posts
    43
    Quote Originally Posted by bhaal View Post
    From what I have read the mlat feeding only works with the DVB-T dongles, no other inputs at this stage..
    the version before it worked also with sbs1 and with the trick above it seems to work with 1.0.14-5 too:

    webinterface:

    Flightradar24 Feeder/Decoder
    Linux/generic/armv7l/1.0.14-5
    Updated: 18:38:56 GMT+0200 (CEST)

    FR24 Link: Connected via UDP
    FR24 Radar Code: T-LOWL1
    Aircraft Tracked (ModeS & ADS-B): 156
    Aircraft Uploaded: 134
    Receiver: sbs1tcp, Connected
    MLAT running: YES

    terminal:

    FR24 Feeder/Decoder Process: running.
    FR24 Stats Timestamp: 2015-07-18 16:40:30.
    FR24 Link: connected [UDP].
    FR24 Radar: T-LOWL1.
    FR24 Tracked AC: 134.
    Receiver: connected (546843 MSGS/0 SYNC).
    FR24 MLAT: ok [UDP].
    FR24 MLAT AC seen: 136.

    ... but maybe the shown info isn't correct?!
    Last edited by LOWL1; 2015-07-18 at 16:44.

Posting Permissions

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