Announcement

Collapse
No announcement yet.

New UAT feeder

Collapse
This is a sticky topic.
X
X
Collapse
 
  • Page of 4
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 template Next
    #46
    Originally posted by joey911 View Post

    Same.

    I spent a few hours last night looking at it and logs. I found some issues with my setup but they were all unrelated. Right now it's saying it's attempting to connect to 185.218.24.53 but that site is not pinging back. I can mtr / traceroute all the way to the hop before it.
    I am also having this issue an am unable to reach this IP in any way.

    Comment

      #47
      I had the same problem all weekend with 185.218.24.53 not responding, guess someone came in today (Monday AM) and brought it up, cuz its working fine today.

      Comment

        #48
        FlightRadar24 just recently sent me a UAT antenna and a new SDR and I have been trying to get this setup on my existing ADS-B RaspberryPi that is imaged with FlightRadar24's images.

        I keep running into an issue between `librtlsdr0` being `0.6.1+rpt1` but `dump978-fr24` depending on `0.6.0-0`. Removing `librtlsdr0` removes `dump1090-mutability`

        This issue seems to be causing the following from my fr24feed:
        Code:
        May 28 20:06:02 raspberrypi fr24feed[4797]: [reader][i]Connecting to the UAT demodulator on tcp://127.0.0.1:30978
May 28 20:06:02 raspberrypi fr24feed[4797]: [reader][e]Failed to connect to the UAT demodulator on tcp://127.0.0.1:30978​
        My page at http://#.#.#.#:8755/index.html show the receiver has `uat-fr24, Connected`.​

        I saw others posting about an install_dump978 script but I am unable to locate that.

        EDIT: For additional information, changing back to 10978 seems to have brought stuff back to life but no data is being transmitted:
        Code:
        May 28 20:19:18 raspberrypi fr24feed[4797]: [main][i]Terminated successfully
May 28 20:19:18 raspberrypi systemd[1]: fr24uat-feed.service: Succeeded.
May 28 20:19:18 raspberrypi systemd[1]: Stopped Flightradar24 UAT Decoder & Feeder.
May 28 20:19:18 raspberrypi systemd[1]: Starting Flightradar24 UAT Decoder & Feeder...
May 28 20:19:18 raspberrypi migrate_from_uat_reader.sh[4895]: Failed to get unit file state for uat_reader.service: No such file or directory
May 28 20:19:18 raspberrypi install_dump978.sh[4900]: dump978-fr24 is not found, downloading...
May 28 20:19:18 raspberrypi install_dump978.sh[4900]: Hit:1 https://repo-feed.flightradar24.com flightradar24 InRelease
May 28 20:19:18 raspberrypi install_dump978.sh[4900]: Hit:2 http://archive.raspberrypi.org/debian buster InRelease
May 28 20:19:19 raspberrypi install_dump978.sh[4900]: Hit:3 http://raspbian.raspberrypi.org/raspbian buster InRelease
May 28 20:19:24 raspberrypi install_dump978.sh[4900]: Reading package lists...
May 28 20:19:24 raspberrypi install_dump978.sh[4900]: Reading package lists...
May 28 20:19:25 raspberrypi install_dump978.sh[4900]: Building dependency tree...
May 28 20:19:25 raspberrypi install_dump978.sh[4900]: Reading state information...
May 28 20:19:26 raspberrypi install_dump978.sh[4900]: Some packages could not be installed. This may mean that you have
May 28 20:19:26 raspberrypi install_dump978.sh[4900]: requested an impossible situation or if you are using the unstable
May 28 20:19:26 raspberrypi install_dump978.sh[4900]: distribution that some required packages have not yet been created
May 28 20:19:26 raspberrypi install_dump978.sh[4900]: or been moved out of Incoming.
May 28 20:19:26 raspberrypi install_dump978.sh[4900]: The following information may help to resolve the situation:
May 28 20:19:26 raspberrypi install_dump978.sh[4900]: The following packages have unmet dependencies:
May 28 20:19:26 raspberrypi install_dump978.sh[4900]: dump978-fr24 : Depends: librtlsdr0 (>= 0.6.0-0) but 0.6-1+rpt1 is to be installed
May 28 20:19:26 raspberrypi install_dump978.sh[4900]: E: Unable to correct problems, you have held broken packages.​
        Last edited by goodrichdev; 2024-05-29, 03:26.

        Comment

          #49
          On my previous post above, the only way to get dump978 working was to install the FlightAware version for `dump978-fa` which now properly attaches to my "Nooelec RTL-SDR v5 SDR". I haven't seen any data come through and I am unsure if that's just because there is no data coming in nearby or there is something wrong. I have switched around the three SDRs I have and all provide the same result. ADS-B is now working fine however.

          EDIT: It looks like another process was taking up 30978/TCP and dump978-fa was using 30978/UDP. In networking this is possible but changing the port to 30970 on dump978-fa and fr24uat-feed was able to start collecting data! Hope this helps someone because this took forever to figure out every little quirk!

          Code:
          May 29 11:34:46 raspberrypi fr24feed[3952]: [reader][i]Connecting to the UAT demodulator on tcp://127.0.0.1:30970
May 29 11:34:46 raspberrypi fr24feed[3952]: [reader][i]Connected to the UAT demodulator on tcp://127.0.0.1:30970
May 29 11:34:47 raspberrypi fr24feed[3952]: [feed][n]ping 1
May 29 11:34:47 raspberrypi fr24feed[3952]: [feed][i]sent 1,0 AC
May 29 11:34:48 raspberrypi fr24feed[3952]: [feed][n]syncing stream result: 1
May 29 11:34:52 raspberrypi fr24feed[3952]: [feed][i]sent 1,0 AC
May 29 11:34:58 raspberrypi fr24feed[3952]: [feed][i]sent 1,0 AC
May 29 11:35:28 raspberrypi fr24feed[3952]: [feed][n]ping 1​
          ​
          Last edited by goodrichdev; 2024-05-29, 18:37.

          Comment

            #50
            Hi! I am getting the Disconnected error on FR24uat-feed, despite the fact that it does work on dump978-fa

            Any thoughts?
            You do not have permission to view this gallery.
            This gallery has 1 photos.

            Comment

              #51
              Originally posted by meneses24 View Post
              Hi! I am getting the Disconnected error on FR24uat-feed, despite the fact that it does work on dump978-fa

              Any thoughts?
              This error means the connection to FR24 servers is not working. Are you behind a firewall?
              --

              Comment

                #52
                Originally posted by Khan View Post

                This error means the connection to FR24 servers is not working. Are you behind a firewall?
                Hi Khan,

                I checked with my ISP and no ports are blocked. And dump978-fa is currently feeding to FA 978 data. I checked with FR24 support and told me to run sudo systemctl restart fr24uat-feed

                And when I do this, it shows the following data

                fruat.png

                Comment

                  #53
                  Do you see the disconnection message on the web interface (http://IP:8755). Also, since you have dump978-fa installed, make sure your /etc/fr24uat-feed.ini file looks like this

                  receiver=uat-tcp
                  fr24key=KEY
                  uat-port=30978
                  bs=no
                  --
                  • Likes 1

                  Comment

                    #54
                    Originally posted by Khan View Post
                    Do you see the disconnection message on the web interface (http://IP:8755). Also, since you have dump978-fa installed, make sure your /etc/fr24uat-feed.ini file looks like this

                    receiver=uat-tcp
                    fr24key=KEY
                    uat-port=30978
                    bs=no

                    Looks just like this

                    receiver="uat-tcp"
                    fr24key="thekey"
                    bs="no"
                    raw="no"
                    mpx="no"
                    mlat="no"
                    mlat-without-gps="no"
                    uat-port="30978"

                    Comment

                      #55
                      Can you post some more logs? Are you still getting the Disconnected error?
                      --

                      Comment

                        #56
                        Following is not a complaint or erro report. It is meant to show other members what is normal and healthy behaviour of fr24uat-feed.

                        Here in Toronto, very few UAT flights, 1 to 4 flights per day. My fr24uat-feed remains connected to FR24 Servers 24/7, but because of this low flight density, my fr24uat-feed is mostly in pinging-synchronizing cycle. This is normal, healthy, and logical behaviour.



                        IP-OF-PI:8755
                        Screenshot_20240619_103559_Samsung Internet.jpg


                        Log for Aicraft sent to FR24​

                        Code:
                        sudo journalctl -u fr24uat-feed -n 100 | grep sent
                        .Screenshot_20240619_103314_Termux.jpg


                        FULL LOG (LATEST LINES OF LOG WHICH ARE VISIBLE ON TERMINAL)​

                        Code:
                        sudo journalctl -u fr24uat-feed -e ​

                        Screenshot_20240619_103048_Termux.jpg


                        ....
                        Last edited by abcd567; 2024-06-19, 15:09.

                        Comment

                        Previous 1 2 3 4 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