Page 21 of 71 FirstFirst ... 11192021222331 ... LastLast
Results 201 to 210 of 707

Thread: Linux feeder software for Flightradar24 (Old software)

  1. #201
    Captain
    Join Date
    Jan 2012
    Location
    Dudley area, UK
    Posts
    1,410
    Is that using the dynamicly linked feeder software or the static (I'm sure someone said static is more reliable)

    BTW - for the static version, the instruction ...
    Use "FR24AUTHIP=83.140.247.20 ./fr24feed_arm-le_232s --fr24key=YOUR_SHARING_KEY" to run the software.

    should read
    Use "export FR24AUTHIP=83.140.247.20; ./fr24feed_arm-le_232s --fr24key=YOUR_SHARING_KEY" to run the software.

    Disclaimer: I'm no expert I've just been using theis 2 days

  2. #202
    Passenger
    Join Date
    Mar 2013
    Location
    T-KCLT1, Near CLT TDWR
    Posts
    16
    I also witnessed the same problem (reported several posts ago) on both dynamic and static versions of 232. I rolled back to 225 which seems stable.
    T-KCLT1, Also the man behind the curtain working on the dump1090 webgui and the dump1090-helper project.

  3. #203
    Passenger JinbaIttai's Avatar
    Join Date
    Dec 2012
    Location
    Perth, Western Australia
    Posts
    30
    Quote Originally Posted by peterhr View Post
    BTW - for the static version, the instruction ...
    Use "FR24AUTHIP=83.140.247.20 ./fr24feed_arm-le_232s --fr24key=YOUR_SHARING_KEY" to run the software.

    should read
    Use "export FR24AUTHIP=83.140.247.20; ./fr24feed_arm-le_232s --fr24key=YOUR_SHARING_KEY" to run the software.
    Hi Peter

    Both commands will work.

    The first method (prepend a command with a VARIABLE=) sets the FR24AUTHIP variable for this instance of the fr24feed_arm-le_232s process only. It is a handy way of quickly setting variables that don't affect anything else.
    The second method is in fact two commands seperated by a ; and you could run them on seperate lines. The first sets a "global" variable using the export command. All subsequent processes run within that shell will have access to that variable which is why the subsequent ./fr24feed command (after the ; ) doesn't have the variable prepended.

    Also, if your fr24feed process stops working every few hours you could use the following dirty little trick to automatically restart the process every hour:

    First add an entry for the system scheduler "cron" to automatically kill any running fr24feed process every hour

    Code:
    crontab -e
    An editor will come up, at the bottom of that file add this line:
    Code:
    0 * * * * killall fr24feed_arm-le_232s
    And then do the following that sets the global variable, and then runs the fr24feed process in a loop - if it dies or is killed it waits 10 seconds and then starts it up again.

    Code:
    export FR24AUTHIP=83.140.247.20
    while true
    do
       ./fr24feed_arm-le_232s --fr24key=YOUR_SHARING_KEY
      sleep 10
    done
    - Matt
    T-YPPH2

  4. #204
    Passenger
    Join Date
    May 2013
    Posts
    4
    Hello!

    I've got some linux developer board and now i'm trying to use this for feeding data. But:
    I installed RTLSDR, ADSBOX and FR24Feeder.
    RTL_ADSB works
    ADSBOX works
    FR24Feeder works BUT I get messages like:
    [e]Data feed time difference too big abs( - )=33015
    [i]sent 0 planes in 0 packets

    ntpd on the board is running, time is very correct. How to fix this?

    Thank you!

    Regards
    Skyscraper

  5. #205
    Passenger
    Join Date
    May 2013
    Posts
    3
    I have the same problem with with stopping feeding data after x hours with linux fr24feed_arm-le_232s
    In console i have:
    Code:
    ...
    [n]UKKK6@europe.fr24.com:8099/UDP
    [n]connecting
    [n]waiting 18 seconds
    [n]UKKK6@europe.fr24.com:8099/UDP
    [n]connecting
    [n]waiting 24 seconds
    [n]UKKK6@83.140.247.21:8099/UDP
    [n]connecting
    [n]waiting 5 seconds
    [n]UKKK6@australia.fr24.com:8099/UDP
    [n]connecting
    [n]waiting 14 seconds
    [n]UKKK6@australia.fr24.com:8099/UDP
    [n]connecting
    [n]waiting 15 seconds
    [n]UKKK6@europe.fr24.com:8099/UDP
    [n]connecting
    [n]waiting 24 seconds
    [n]UKKK6@83.140.247.21:8099/UDP
    [n]connecting
    [n]connected
    [n]switching to UDP
    [n]working
    [i]Removed 1 of 2 AC
    After restarting all is ok, but, imho, this is not the best solution (

  6. #206
    Passenger
    Join Date
    Feb 2013
    Location
    London, UK
    Posts
    43
    There are reports of fr24feed_arm-le_232s failing as you describe.
    Some of us have reverted to using the older (and more stable) version fr24feed_arm-le_225s

  7. #207
    Passenger
    Join Date
    May 2013
    Posts
    3
    roofer, where i can find them?

  8. #208
    Passenger
    Join Date
    Jan 2013
    Posts
    43
    Quote Originally Posted by zend View Post
    roofer, where i can find them?
    https://dl.dropboxusercontent.com/u/...rm-le_225s.tgz

  9. #209
    Passenger
    Join Date
    May 2013
    Posts
    4
    Thank you!
    This version works great without any messages like:
    [e]Data feed time difference too big abs( - )=33015

  10. #210
    Passenger
    Join Date
    Jun 2013
    Location
    LSZB (Bern, Switzerland)
    Posts
    5

    Question adsbox stopping after some time

    Hello FR24-Feeders

    I have the following installation which is basically working, but is stopping after some random time (see below for problem):

    Hardware:

    MicroADSB-Stick --> Raspberry Pi (New B Model 512MB RAM) --> USB WLAN Dongle
    iPad2 Power Plug

    Software:

    adsbox --> fr24feed_arm-le_225s

    My start Script:
    Code:
    #!/bin/bash
    
    BAUD=3000000
    FR24FEEDER=fr24feed_arm-le_225s
    FR24KEY=123456789
    
    # stop/start decoder
    echo Stop/start adsbox...
    killall -v adsbox
    cd /home/pi/adsb/adsbox
    ./adsbox --daemon --baud $BAUD --serial /dev/ttyACM0 --lat XX.XXXX --lon Y.Y --seed --seed-port 30004
    echo adsbox started
    echo ----
    
    # wait and let decoder start
    sleep 1
    
    # stop/start feeder
    echo Stop/start feeder...
    killall -v $FR24FEEDER
    cd /home/pi/adsb
    export FR24AUTHIP=83.140.247.20
    #./$FR24FEEDER --fr24key=$FR24KEY > /dev/null &
    echo feeder started
    As I wrote, basically everything works. But only for some time. And as opposed to others, who are seeing the fr24 feeder script stopping, I see the adsbox decoder stopping. Sometimes after a few seconds, sometimes after 3 hours.

    I can check the status of adsbox at port 8080 where I can monitor its flight table being updated - until it stops.
    Or at port 30003, where the decoded message are sent - until it stops.

    I am not sure, but it could be the serial usb interface between the stick and the raspberry pi. I have the feeling, that it stops earlier, if I am using a higher baudrates. And I have the feeling, that it stops earlier if there is more traffic. If I am using 576000 baud and the antenna is in my room (with reduced packet reception), it seems to run a bit longer than with the antenna placed on the outside.

    Does anybody have an idea what this could be?
    • Overload of the serial communication the the Pi?
    • Missconfiguration of the serial communication?
    • Should I send an init string to the stick in order to filter the packets?
    • Hardware fault?
    • Power stability problem? (I have tried several recommended power plugs without any change)


    Thanks & have a nice weekend!

    Thomas
    Last edited by thowe; 2013-06-02 at 07:30. Reason: lat/lon hidden

Tags for this Thread

Posting Permissions

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