Announcement

Collapse
No announcement yet.

Archived - Beta test MLAT software for Raspberry Pi

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

  • mrcarlos
    replied
    try this:

    sudo nano /etc/resolv.conf

    add this lines to the file
    nameserver 8.8.8.8
    nameserver 8.8.4.4

    save the file restart your rpi and try again but first run apt update and apt upgrade.

    Sent from my SM-N910F using Tapatalk

    Leave a comment:


  • JoeinAK
    replied
    Originally posted by mrcarlos View Post
    are you on Linux or Windows? do you have any proxy or are vpn?

    Sent from my SM-N910F using Tapatalk
    I am running on Raspberry Pi, Raspbian, Linux. No VPNs or Proxys. It seems to be repo issue on fr24 side but I'm not sure. Was hopping somebody can recognize the errors.

    Leave a comment:


  • mrcarlos
    replied
    are you on Linux or Windows? do you have any proxy or are vpn?

    Sent from my SM-N910F using Tapatalk

    Leave a comment:


  • JoeinAK
    replied
    Hello,
    I was hopping to get some help with the installation, I get this error when I run the automated script. However I just tried posting the error message but it's not letting me beacuse it has links in it, so I'm attaching an image of the error. please help as I'd love to contribute.

    Screen Shot 2017-04-15 at 9.53.15 PM.png

    Thanks
    Joe

    Leave a comment:


  • Oblivian
    replied
    Originally posted by takshing2001 View Post
    excuse me May i ask how to see RPI3 Running status

    in the past i use windows fr24feed in the program i can see




    RPI3 how Show to running status by ssh ?
    It's been explained a few times in this thread.
    But also laid out in some help guides.. You cannot get the same information all the time so the web page and your account stats should be used to check status
    https://forum.flightradar24.com/thre...-FAQs-and-Info

    Leave a comment:


  • takshing2001
    replied
    excuse me May i ask how to see RPI3 Running status

    in the past i use windows fr24feed in the program i can see

    [i]sent * planes in 1 packets
    ...

    RPI3 how Show to running status by ssh ?

    Leave a comment:


  • Skorpion
    replied
    Originally posted by elljay View Post
    Looks ok yes.

    T- are for people running the client on RPi, Linux etc

    F- are for people with one of the FR24 boxes
    received. thanks a lot!

    Leave a comment:


  • elljay
    replied
    Looks ok yes.

    T- are for people running the client on RPi, Linux etc

    F- are for people with one of the FR24 boxes (https://www.flightradar24.com/apply-for-receiver)

    Leave a comment:


  • Skorpion
    replied
    So my Mlat is running correctly? Why i'm still T-LIBP and not F-LIBP?

    Leave a comment:


  • elljay
    replied
    Hi, no idea, but mine says the same but is happily uploading mlat data! frfeed24.log says:

    2017-01-22 11:56:56 | [mlat][i]Pinging the server
    2017-01-22 11:56:56 | [mlat][i]Stats 86527432/1398

    Leave a comment:


  • Skorpion
    replied
    Hi, i'm T-LIBP17. In the monitor.txt page i've this log:
    mlat-mode="UDP"
    mlat-number-seen="8"
    mlat-ok="YES"
    mlat-started="YES"
    mlat-time-last-ping="1485083155"
    mlat-time-last-push="1485083161"
    mlat-time-last-push_count="18"
    mlat-time-last-seen="1485083162"
    mlat-time-stats="1485083166"
    mlat-uplink-stats="0"
    mlat_problem="no-config"
    what's mean mlat_problem="no-config"?

    Leave a comment:


  • Dundee
    replied
    Originally posted by Kemistry View Post
    Do we have to prepare for leap-second event on 1 Jan 2017? Just reboot after midnight and all will be fixed?
    FR24feed software will synchronize time via NTP server every 10 minutes automatically...
    I think no need to worry about it...

    Leave a comment:


  • Kemistry
    replied
    Do we have to prepare for leap-second event on 1 Jan 2017? Just reboot after midnight and all will be fixed?

    Leave a comment:


  • Wolli
    replied
    2nd Update concerning: [mlat][e]Received MLAT timestamp error: 0 seconds!

    After several days of MLAT "working as it should" (seen with my eyes) the - by me myself - stated "error" ...
    -> [mlat][e]Received MLAT timestamp error: 0 seconds!
    is again back here.

    Though I explicitely appreciate this posting of @WolfInTheAir (many thanks!), my wish is to see an "official FR24 posting" concerning FR24's handling of volunteer MLAT feeders' (like e.g. me) problems.

    Motivation for my request:
    We - the volunteers - are investing time and money to help/assist FR24 being able to spread good/best quality flight data to "the world". We like to do so. However, when problems (seen with our eyes) arise, we would like to have some info, why.

    * Maybe, the data quality of an individual feeder is not so good, as FR24 requires. A suggestion by FR24, what the feeder (person) could do to enhance data quality, would be warmly welcome.

    * Maybe, participation in MLAT feeding generally requires the individual feeder to supply data of many dozens of ACs at the same time to ensure "good quality MLAT data". Maybe, MLAT-feeders seeing just a few dozens of ACs have a "natural" MLAT data quality problem.

    I understand, that FR24 probably won't put all its cards "open on the table", due to business secrets. That's ok.

    However, my current feeling is, that we currently do not receive sufficient information concerning MLAT problems/issues.

    Consequently, it would be nice to see/read some more official FR24 info about MLAT issues.

    So I politely invite FR24 to supply us with some more info concerning MLAT problems. This would be very rewarding. May we have hope? Kind regards, -Wolli-
    Last edited by Wolli; 2016-12-06, 19:59.

    Leave a comment:


  • Wolli
    replied
    Update concerning: [mlat][e]Received MLAT timestamp error: 0 seconds!

    Hi all,

    after several days "living" with that error (I checked that every 2 days or so), today I noticed that the reported
    -> [mlat][e]Received MLAT timestamp error: 0 seconds!
    is no more appearing in my feeder's log. I don't know, why.

    I assume the FR24 guys are - from time to time - changing the behaviour of their MLAT-servers, in a continuously ongoing process of enhancing MLAT quality. However, this is just speculation.

    Greetings, -Wolli-

    Leave a comment:

Working...
X