Page 1 of 5 123 ... LastLast
Results 1 to 10 of 45

Thread: FR24 Link disconnected and nothing is uploaded. PlanePlotter and Plane Finder work OK

  1. #1
    Passenger
    Join Date
    Apr 2018
    Posts
    35

    FR24 Link disconnected and nothing is uploaded. PlanePlotter and Plane Finder work OK

    T-EGKK139 is located inside my former work location within a large organisation at Gatwick airport. The aerial is inside a window that overlooks the airport directly, hence excellent coverage of aircraft on the ground there. As I am retired, I can only access the machine myself remotely through AnyDesk (an alternative to TeamViewer). As with two other identical (former Windows XP, then Windows 7) 32-bit Panasonic CF-18 Toughbooks (running in other locations) this machine is running Linux (Ubuntu 18.04) and uses Dump1090 Mutability to upload to FR24 and Plane Finder within Linux and to PlanePlotter through Wine (virtual windows). I know that this works perfectly to all three flight tracking organisations because of my experience with T-EGKB81 and T-EIKK20.

    However, since the T-EGKK139 machine was placed into service in late September, uploading to both PlanePlotter and Plane Finder has been working perfectly. Not so to FR24! I can see that the programme is correctly working and that many aircraft are being tracked by the FR24 software, but the FR24 Link is disconnected and no aircraft are being uploaded.

    There follows many screenshoots, as I have tried to troubleshoot the problem. For information, I tried with MLAT selected as both “yes” then “no” to see if this made a difference. It didn’t!

    I am assuming that the issue is a conflict with (or within) the organisation’s free staff wifi (possibly a blocking of a UDP port). However, given that I am uploading successfully to PlanePlotter and Plane Finder, I believe that there must be a FR24 “work around” to this problem.


    Many thanks,
    Ian

  2. #2
    Captain
    Join Date
    Apr 2018
    Posts
    863
    What is the output of
    fr24feed-status

    Can you check the log output for fr24feed?
    I'm not sure how it's started, just stop it and start it on the console:

    sudo fr24feed

    That should show you the error if there is any.
    In case it's using AVR on port 30002, try switching it to beast-tcp and port 30005
    AVR via port 30002 is sometimes bugged in the feeder, no clue why.

  3. #3
    Passenger
    Join Date
    Apr 2018
    Posts
    35
    Status output follows. Tried AVR-TCP and Beast-TCP - same end result.

    Ian

    av6@Aerovision6:~$ fr24feed --status
    /dev/shm/decoder.txt: Permission denied
    [main][e]Could not create monitor file!
    2019-10-03 15:49:44 | [main][i]FR24 Feeder/Decoder
    2019-10-03 15:49:44 | [main][i]Version: 1.0.18-5/generic
    2019-10-03 15:49:44 | [main][i]Built on Mar 2 2016 20:06:10 (devel-d11ca48.git/Linux/i686)
    2019-10-03 15:49:44 | [main][i]Copyright 2012-2016 Flightradar24 AB
    2019-10-03 15:49:44 | [main][i]http://flightradar24.com
    2019-10-03 15:49:54 | [main][i]DNS mode: LIBC
    2019-10-03 15:49:54 | [main][i]Automatic updates are DISABLED
    2019-10-03 15:49:54 | [main][i]Reader thread started
    2019-10-03 15:49:54 | [time][i]Synchronizing time via NTP
    2019-10-03 15:49:54 | [reader][i]Initializing reader
    2019-10-03 15:49:54 | [reader][i]Connecting to Beast receiver via (avr-tcp://127.0.0.1:30002)
    2019-10-03 15:49:54 | [reader][i]Connected to the receiver, configuring
    2019-10-03 15:49:54 | [reader][i]Configured, processing messages
    2019-10-03 15:49:54 | [master][i]Starting processing thread
    2019-10-03 15:49:54 | [httpd][e]bind function failed, errno: 98
    2019-10-03 15:49:54 | [httpd][d]Master thread terminated
    2019-10-03 15:49:55 | [reader][w]Setting new UTC offset: 0!
    2019-10-03 15:49:57 | [time][i]Time synchronized correctly, offset -0.0007 seconds
    2019-10-03 15:49:57 | [main][i]Feed Network client started
    2019-10-03 15:49:57 | [feed][i]Downloading configuration
    2019-10-03 15:49:57 | [feed][c]Interval: 5s
    2019-10-03 15:49:57 | [feed][c]Latitude: 51.1451
    2019-10-03 15:49:57 | [feed][c]Longitude: -0.1653
    2019-10-03 15:49:57 | [feed][c]GND: YES
    2019-10-03 15:49:57 | [feed][c]NonADSB: YES
    2019-10-03 15:49:57 | [feed][c]Timestamps: optional
    2019-10-03 15:49:57 | [feed][c]Max range AIR: 350.0nm
    2019-10-03 15:49:57 | [feed][c]Max range GND: 100.0nm
    2019-10-03 15:49:57 | [feed][i]defined 4 servers
    2019-10-03 15:49:57 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-03 15:49:57 | [feed][n]connecting
    2019-10-03 15:49:57 | [stats][i]Stats thread started
    2019-10-03 15:52:27 | [feed][e]Could not connect!
    2019-10-03 15:52:27 | [feed][n]Error: Could not connect! (fd -1)
    2019-10-03 15:52:27 | [feed][n]waiting 9 seconds
    2019-10-03 15:52:36 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-03 15:52:36 | [feed][n]connecting

  4. #4
    Captain
    Join Date
    Apr 2018
    Posts
    863
    beast-tcp needs port 30005 as i said.

    Your log shows port 30002 being used.

    Also i didn't ask for fr24feed --status but for fr24feed-status, quite the difference.

    Configure it like this please:
    Code:
    receiver="beast-tcp"
    fr24key="xxxxxxxxxxxxxxxx"
    host="127.0.0.1:30005"
    bs="no"
    raw="no"

  5. #5
    Passenger
    Join Date
    Apr 2018
    Posts
    35
    fr24feed-status does not work for me. Sorry. I am now on Beast-TCP and 30005. Same end result unfortunately.

    Ian


    av6@Aerovision6:~$ fr24feed-status: command not found
    fr24feed-status:: command not found
    av6@Aerovision6:~$ sudo fr24feed-status
    sudo: fr24feed-status: command not found


    FR24 Feeder Settings

    Please note that changes will not take place until you save settings and restart the application!
    Setting Config file Live setting Comment
    Sharing key: f99d1b7efab37c1a [16 characters]
    Receiver:
    beast-tcp
    Host/IP: 127.0.0.1:30005 [192.168.10.1:10000,localhost:30334]
    COM/DEV/PATH: n/a [/dev/ttyUSB0, COM8, /usr/bin/dump1090]
    Process arguments: [Extra arguments for dump1090, ex --net-http-port 8080 ]
    Baudrate:
    default [COM/DEV only]
    RAW data (30002/30334):
    no Enable/Disable raw data stream on port 30002(dvbt) or 30334(other)
    SBS Feed (10001):
    no SBS1 compatible feed, port 10001, Kinetic Avionics RX only!
    Decoded data (30003):
    no Enable/Disable decoded data stream on port 30003
    Logfile mode:
    0
    Log file location: disabled
    Window mode:
    0 (Microsoft Windows Only)
    MLAT:
    no Participate in MLAT calculations (Raspberry Pi B+ / Raspberry Pi 2 only)
    Extra settings: (Edit config file to modify these settings)

  6. #6
    Captain
    Join Date
    Apr 2018
    Posts
    863
    How is fr24feed started?

    You should stop it and start it manually on the console, then the log will be interesting.

    (fr24feed-status seems to only be available in the packaged version for the Raspberry Pi)

  7. #7
    Passenger
    Join Date
    Apr 2018
    Posts
    35
    Dump1090 Mutability, FR24 and Plane Finder are all auto started on machine start-up. The installation was using The ADS-B Receiver Project (https://www.adsbreceiver.net/). All three of my Toughbooks are identical and the other two are cloned HDDs off this one. All three work fine under test here at home, so the FR24 issue seems to relate to a WiFi restriction at my old workplace. However, whatever the problem, it does not impact on Plane Finder or PlanePlotter functionality.

    I can manually stop and restart on the Terminal Emulator. But, no difference so far.

  8. #8
    Captain
    Join Date
    Apr 2018
    Posts
    863
    No i mean stop the running fr24feed.
    Then type on the console
    fr24feed

    That way you see the output, which is what i want to see.

  9. #9
    Passenger
    Join Date
    Apr 2018
    Posts
    35
    av6@Aerovision6:~$ service fr24feed status
    ● fr24feed.service - LSB: Flightradar24 Decoder & Feeder
    Loaded: loaded (/etc/init.d/fr24feed; generated)
    Active: active (running) since Thu 2019-10-03 17:01:10 BST; 1min 40s ago
    Docs: man:systemd-sysv-generator(8)
    Process: 21758 ExecStop=/etc/init.d/fr24feed stop (code=exited, status=0/SUCCESS)
    Process: 21928 ExecStart=/etc/init.d/fr24feed start (code=exited, status=0/SUCCESS)
    Tasks: 9 (limit: 3513)
    CGroup: /system.slice/fr24feed.service
    └─21941 /usr/bin/fr24feed -- --monitor-file=/dev/shm/fr24feed.txt --write-pid=/var/run/fr24feed.pid --quiet

    Oct 03 17:01:09 Aerovision6 systemd[1]: Starting LSB: Flightradar24 Decoder & Feeder...
    Oct 03 17:01:09 Aerovision6 fr24feed[21928]: * Starting FR24 feeder fr24feed
    Oct 03 17:01:10 Aerovision6 fr24feed[21928]: ...done.
    Oct 03 17:01:10 Aerovision6 systemd[1]: Started LSB: Flightradar24 Decoder & Feeder.

  10. #10
    Passenger
    Join Date
    Apr 2018
    Posts
    35
    av6@Aerovision6:~$ fr24feed
    /dev/shm/decoder.txt: Permission denied
    [main][e]Could not create monitor file!
    2019-10-03 17:05:44 | [main][i]FR24 Feeder/Decoder
    2019-10-03 17:05:44 | [main][i]Version: 1.0.18-5/generic
    2019-10-03 17:05:44 | [main][i]Built on Mar 2 2016 20:06:10 (devel-d11ca48.git/Linux/i686)
    2019-10-03 17:05:44 | [main][i]Copyright 2012-2016 Flightradar24 AB
    2019-10-03 17:05:44 | [main][i]http://flightradar24.com
    2019-10-03 17:05:54 | [main][i]DNS mode: LIBC
    2019-10-03 17:05:54 | [main][i]Automatic updates are DISABLED
    2019-10-03 17:05:54 | [main][i]Reader thread started
    2019-10-03 17:05:54 | [time][i]Synchronizing time via NTP
    2019-10-03 17:05:54 | [reader][i]Initializing reader
    2019-10-03 17:05:54 | [reader][i]Connecting to Beast receiver via (tcp://127.0.0.1:30005)
    2019-10-03 17:05:54 | [reader][i]Connected to the receiver, configuring
    2019-10-03 17:05:54 | [reader][i]Configured, processing messages
    2019-10-03 17:05:54 | [httpd][i]Server started, listening on 0.0.0.0:8754
    2019-10-03 17:05:54 | [master][i]Starting processing thread
    2019-10-03 17:05:54 | [reader][w]Setting new UTC offset: 0!
    2019-10-03 17:05:56 | [time][i]Time synchronized correctly, offset -0.0002 seconds
    2019-10-03 17:05:56 | [main][i]Feed Network client started
    2019-10-03 17:05:56 | [feed][i]Downloading configuration
    2019-10-03 17:05:57 | [feed][c]Interval: 5s
    2019-10-03 17:05:57 | [feed][c]Latitude: 51.1451
    2019-10-03 17:05:57 | [feed][c]Longitude: -0.1653
    2019-10-03 17:05:57 | [feed][c]GND: YES
    2019-10-03 17:05:57 | [feed][c]NonADSB: YES
    2019-10-03 17:05:57 | [feed][c]Timestamps: optional
    2019-10-03 17:05:57 | [feed][c]Max range AIR: 350.0nm
    2019-10-03 17:05:57 | [feed][c]Max range GND: 100.0nm
    2019-10-03 17:05:57 | [feed][i]defined 4 servers
    2019-10-03 17:05:57 | [feed][n]EGKK139@185.218.24.23:8099/UDP
    2019-10-03 17:05:57 | [feed][n]connecting
    2019-10-03 17:05:57 | [stats][i]Stats thread started

Posting Permissions

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