Announcement

Collapse
No announcement yet.

AVR-(TCP) Configuration ignored

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    AVR-(TCP) Configuration ignored

    When I try to configure the receiver type to be AVR(TCP) with a custom port number via the setting web page, the configuration appears to be ignored and the log indicates that is it using port 30005 as data source (directly from dump1090)

    I also tried using the command line arguments to set this and got the same result in the log - and the feeder started to forward data from dump1090 and not my desired port which is output of uat2esnt

    Command line invoked using --receiver argument:

    Code:
    pi@piaware:~ $ sudo fr24feed --receiver=avr-tcp --host=127.0.0.1:30976
20-06-20 08:33:37.111 [E] Local time: 2020-06-20 08:33:37 -0400
20-06-20 08:33:37.111 [E] GMT+0 time: 2020-06-20 13:33:37 -0400
20-06-20 08:33:37.111 [E] Your machine should be set as GMT+0 time zone!
20-06-20 08:33:37.111 [W] Time zone is not set to GMT+0
2020-06-20 08:33:37 | ______ _ _ _ _ _ _____ ___
2020-06-20 08:33:37 | | ___|| |(_) | | | | | | / __ \ / |
2020-06-20 08:33:37 | | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
2020-06-20 08:33:37 | | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
2020-06-20 08:33:37 | | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
2020-06-20 08:33:37 | \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
2020-06-20 08:33:37 | __/ |
2020-06-20 08:33:37 | |___/
2020-06-20 08:33:37 | [main][i]FR24 Feeder/Decoder
2020-06-20 08:33:37 | [main][i]Version: 1.0.25-3/generic
2020-06-20 08:33:37 | [main][i]Built on Apr 8 2020 07:06:55 (HEAD-5e8ef0c.git/Linux/static_armel)
2020-06-20 08:33:37 | [main][i]Running on: raspbian10
2020-06-20 08:33:37 | [main][i]Local IP(s): 192.168.1.50
2020-06-20 08:33:37 | [main][i]Copyright 2012-2020 Flightradar24 AB
2020-06-20 08:33:37 | [main][i]https://www.flightradar24.com
2020-06-20 08:33:37 | [main][i]DNS mode: PING
2020-06-20 08:33:37 | [main][i]Automatic updates are ENABLED
2020-06-20 08:33:37 | info | [httpd]Server started, listening on 0.0.0.0:8754
2020-06-20 08:33:37 | [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
2020-06-20 08:33:37 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
2020-06-20 08:33:37 | [main][i]Reader thread started
2020-06-20 08:33:37 | [master][i]Starting processing thread
2020-06-20 08:33:37 | [time][i]Synchronizing time via NTP
2020-06-20 08:33:37 | [reader][i]Initializing reader
2020-06-20 08:33:37 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
2020-06-20 08:33:38 | [reader][i]Connected to the receiver, configuring
2020-06-20 08:33:38 | [reader][i]Configured, processing messages
    Is this a known issue and/or is there a workaround to force the use of AVR data from a custom port ?
    Tags: None
  • #2
    You'll need to specify those changes in the config file. I don't believe it does cmdline other than reconfigure or setup.

    It will be reading the ini which is dvbt by default (seems to be avr-tcp with no settings here). So have a go while its running to edit the config via web

    Which is what starts when this is happening

    info | [httpd]Server started, listening on 0.0.0.0:8754

    or sudo nano /etc/fr24feed.ini
    Last edited by Oblivian; 2020-06-20, 12:59.
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

    Comment

    • #3
      That yields the same result:

      Config File
      Code:
      receiver="avr-tcp"
fr24key="xxx"
host="127.0.0.1:30976"
bs="no"
raw="no"
logmode="2"
windowmode="0"
logpath="/var/log/fr24feed"
mpx="no"
mlat="no"
mlat-without-gps="no"
      Startup from log
      Code:
      2020-06-20 09:06:42 | ______ _ _ _ _ _ _____ ___
2020-06-20 09:06:42 | | ___|| |(_) | | | | | | / __ \ / |
2020-06-20 09:06:42 | | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
2020-06-20 09:06:42 | | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
2020-06-20 09:06:42 | | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
2020-06-20 09:06:42 | \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
2020-06-20 09:06:42 | __/ |
2020-06-20 09:06:42 | |___/
2020-06-20 09:06:42 | [main][i]FR24 Feeder/Decoder
2020-06-20 09:06:42 | [main][i]Version: 1.0.25-3/generic
2020-06-20 09:06:42 | [main][i]Built on Apr 8 2020 07:06:55 (HEAD-5e8ef0c.git/Linux/static_armel)
2020-06-20 09:06:42 | [main][i]Running on: raspbian10
2020-06-20 09:06:42 | [main][i]Local IP(s): 192.168.1.50
2020-06-20 09:06:42 | [main][i]Copyright 2012-2020 Flightradar24 AB
2020-06-20 09:06:42 | [main][i]https://www.flightradar24.com
2020-06-20 09:06:42 | [main][i]DNS mode: PING
2020-06-20 09:06:42 | [main][i]Automatic updates are ENABLED
2020-06-20 09:06:42 | info | [httpd]Server started, listening on 0.0.0.0:8754
2020-06-20 09:06:42 | [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
2020-06-20 09:06:42 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
2020-06-20 09:06:42 | [master][i]Starting processing thread
2020-06-20 09:06:42 | [main][i]Reader thread started
2020-06-20 09:06:42 | [time][i]Synchronizing time via NTP
2020-06-20 09:06:42 | [reader][i]Initializing reader
2020-06-20 09:06:42 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
2020-06-20 09:06:42 | [reader][i]Connected to the receiver, configuring
2020-06-20 09:06:42 | [reader][i]Configured, processing messages
2020-06-20 09:06:43 | [time][i]Time synchronized correctly, offset -0.004 seconds
2020-06-20 09:06:43 | [feed][i]Downloading configuration
2020-06-20 09:06:43 | [main][i]Feed Network client started
2020-06-20 09:06:43 | [feed][d]fetching configuration
2020-06-20 09:06:43 | [reader][i]Timestamp source changed from UNKNOWN to SYSTEM-VALIDATED
2020-06-20 09:06:43 | [feed][i]configuring decoder
2020-06-20 09:06:43 | [feed][c]Max range AIR: 350.0nm
2020-06-20 09:06:43 | [feed][c]Max range GND: 100.0nm
2020-06-20 09:06:43 | info | [stats]Stats thread started
2020-06-20 09:06:43 | [feed][i]configuration changed

      Comment

      • #4
        Unsure then. As I just edited my tester to port 6658 and it starts with that fine

        So unless your ini file is in read only mode, or not using the default one.


        2020-06-21 01:21:35 | [main][i]Reader thread started
        2020-06-21 01:21:35 | [master][i]Starting processing thread
        2020-06-21 01:21:35 | [reader][i]Initializing reader
        2020-06-21 01:21:35 | [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://127.0.0.1:6658)
        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

        Comment

        • #5
          Seems like we're both a little confused then..

          There don't seem to be any permissions issues with the config file and if I make a change via the web page then inspect the file manually there changes are reflected there.

          I even deleted the .ini file and created a new one but t made no difference

          I assume you are running the same version ?

          Code:
          Version: 1.0.25-3/generic

          Comment

          • #6
            Tried using an older version - same issue

            Code:
            2020-06-20 10:57:43 | ______ _ _ _ _ _ _____ ___
2020-06-20 10:57:43 | | ___|| |(_) | | | | | | / __ \ / |
2020-06-20 10:57:43 | | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
2020-06-20 10:57:43 | | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
2020-06-20 10:57:43 | | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
2020-06-20 10:57:43 | \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
2020-06-20 10:57:43 | __/ |
2020-06-20 10:57:43 | |___/
2020-06-20 10:57:43 | [main][i]FR24 Feeder/Decoder
2020-06-20 10:57:43 | [main][i]Version: 1.0.23-8/generic
2020-06-20 10:57:43 | [main][i]Built on Oct 16 2018 08:10:47 (HEAD-2d57e58.git/Linux/static_armel)
2020-06-20 10:57:43 | [main][i]Running on: raspbian10
2020-06-20 10:57:43 | [main][i]Local IP(s): 192.168.1.50
2020-06-20 10:57:43 | [main][i]Copyright 2012-2018 Flightradar24 AB
2020-06-20 10:57:43 | [main][i]https://www.flightradar24.com
2020-06-20 10:57:43 | [main][i]DNS mode: PING
2020-06-20 10:57:43 | [main][i]Automatic updates are DISABLED
2020-06-20 10:57:43 | [main][i]Reader thread started
2020-06-20 10:57:43 | [time][i]Synchronizing time via NTP
2020-06-20 10:57:43 | [reader][i]Initializing reader
2020-06-20 10:57:43 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
            This is running on a PiAware image with dump1090-fa

            Does this feeder need to see dump1090-mutability to allow AVR-TCP ?

            Comment

            • #7
              Nope. Don't believe so. I didn't let my example proceed but it would have just failed and not connected.

              Avr-tcp is meant to ignore dump1090 and just goes hunting for source specified using the native reader

              But for whatever reason. Yours isn't taking notice of changes or using a default setting.

              ​​​​May be time for a Purge and --reconfigure last resort
              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

              Comment

              • #8
                I think I'll try installing FR24feed on a different system and see if that behaves differently - thx for taking the time to give some feedback

                Comment

                • #9
                  I've run into similar issues.
                  Try using the beast-tcp and give it that.

                  The fr24feed binary seems extremely buggy.

                  Comment

                  Previous template Next
                  Working...
                  X

                  We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                  By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                  I Agree