Announcement

Collapse
No announcement yet.

Online - No Data after moving my setup

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Online - No Data after moving my setup

    Hi fellows,

    I had my setup installed on a temporary place for 20 days, just like the photo, on my desk.
    IMG_20191001_145000.jpg

    Have been tracking around 200 to 260 aircrafts daily with range up to 170nm, but with a great restriction on line of sight.
    fr24 a.jpg

    Yesterday I moved the antenna to the roof and the raspberry to the attic.
    IMG_20191001_170923.jpg
    IMG_20191001_170942.jpg

    After all, I have no data being sent.
    fr24 b.jpg
    What kind of tests can I run to solve the issue?
    Also, I´ve noticed a lot of down time as shown in the daily availability. Maybe wifi problem?

    I very newbie to raspberry and hope to get some help.

    Thanks a lot.
    SBNF
    Brazil

    My setup:
    Raspberry pi 3B+ with a iphoenix Case
    FlightAware 1090 MHz ADS-B Antenna - 66 cm / 26 in
    FlightAware Pro Stick Plus FA-PROSTICKPLUS-1 ADS-B USB Receiver with Built-in Filter
    and 10m cable

  • #2
    That pattern often doesn't mean that the feed isn't working.

    You can try if adding these options helps:
    use-http=yes
    http-timeout=20

    Use this command to edit the options:
    sudo nano /etc/fr24feed.ini

    Add the 2 lines at the bottom:
    use-http=yes
    http-timeout=20

    Ctrl-O and enter to save, Ctrl-X to exit.
    Then do a reboot
    sudo reboot

    One user here could never quite figure out the problem and his network connection wasn't the issue.

    You might want to have some independent statistics as those you showed don't work.
    https://github.com/wiedehopf/graphs1090#graphs1090

    Comment


    • #3
      no luck.
      I´ll back to the roof and recheck the antenna conections.
      the graphs only show cpu memory and such. All other adsb functions won´t open.
      fr24.jpg

      Comment


      • #4
        Run this command and have look what is actually happening on your RasPi
        sudo journalctl -n 400 --no-pager

        Comment


        • #5
          fr24feed doesn't log to the system log, so journalctl is of limited use.

          Hmm, if you want to make the graphs work install this, you'll have a nicer local web interface as well:
          https://github.com/wiedehopf/adsb-sc...for-dump1090fa

          You might have to re-run the graphs install script as well after changing to dump1090-fa.


          I doubt very much that it's any kind of antenna issue.
          It's probably just the FR24 servers acting up.

          Let's check which version you are running:
          fr24feed --help | grep Version
          Last edited by wiedehopf; 2019-10-02, 17:37.

          Comment


          • #6
            I guess about the antenna because the problem started after I moved it.

            fr24.jpg

            Comment


            • #7
              After installing dump1090-fa as shown in the previous post, you can check the log for that, it's much easier to handle than the fr24feed log.

              The log for that:
              sudo journalctl --no-pager -u dump1090-fa

              Otherwise the easiest way to check the fr24feed log is actually:
              sudo systemctl stop fr24feed
              sudo fr24feed

              It will now run on the console and you can see the log.
              If you are done, you'll need to stop it and restart the service:
              Ctrl-C to interrupt
              sudo systemctl restart fr24feed

              Obviously this isn't a permanent solution to check the logs, but it might show if the problem appears immediately.

              Might be a power supply problem if the dongle stopped working, can you try another power supply?
              Is the dongle plugged in directly? You can try another USB port.

              Comment


              • #8
                is there a problem if the antenna is in the same pole of the tv antenna?

                Comment


                • #9
                  If you get the graphs going as suggested, it'll be much easier to see where the issue is.

                  Just guessing won't help.

                  Comment


                  • #10
                    got this installing as requested

                    sed: não foi possível abrir o arquivo temporário /etc/default/sedB3691K: Permissão negada
                    sed: não foi possível abrir o arquivo temporário /etc/default/sedBIixaK: Permissão negada

                    Comment


                    • #11
                      sudo journalctl --no-pager -u dump1090-fa
                      -- Logs begin at Thu 2019-02-14 08:11:59 -02, end at Wed 2019-10-02 15:46:44 -03. --
                      out 02 15:37:38 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
                      out 02 15:37:38 raspberrypi dump1090-fa[6122]: Wed Oct 2 15:37:38 2019 -03 dump1090-fa 3.7.2 starting up.
                      out 02 15:37:38 raspberrypi dump1090-fa[6122]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000)
                      out 02 15:37:38 raspberrypi dump1090-fa[6122]: Found Rafael Micro R820T tuner
                      out 02 15:37:38 raspberrypi dump1090-fa[6122]: rtlsdr: enabling tuner AGC
                      out 02 15:37:38 raspberrypi dump1090-fa[6122]: Allocating 4 zero-copy buffers
                      out 02 15:38:04 raspberrypi dump1090-fa[6122]: Wed Oct 2 15:38:04 2019 -03 Caught SIGTERM, shutting down..
                      out 02 15:38:04 raspberrypi systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)...
                      out 02 15:38:04 raspberrypi dump1090-fa[6122]: Wed Oct 2 15:38:04 2019 -03 Waiting for receive thread termination
                      out 02 15:38:05 raspberrypi dump1090-fa[6122]: Wed Oct 2 15:38:05 2019 -03 Normal exit.
                      out 02 15:38:05 raspberrypi systemd[1]: dump1090-fa.service: Succeeded.
                      out 02 15:38:05 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
                      out 02 15:38:05 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
                      out 02 15:38:05 raspberrypi dump1090-fa[6614]: Wed Oct 2 15:38:05 2019 -03 dump1090-fa 3.7.2 starting up.
                      out 02 15:38:05 raspberrypi dump1090-fa[6614]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000)
                      out 02 15:38:05 raspberrypi dump1090-fa[6614]: Found Rafael Micro R820T tuner
                      out 02 15:38:06 raspberrypi dump1090-fa[6614]: rtlsdr: enabling tuner AGC
                      out 02 15:38:06 raspberrypi dump1090-fa[6614]: Allocating 4 zero-copy buffers
                      out 02 15:39:57 raspberrypi dump1090-fa[6614]: Wed Oct 2 15:39:57 2019 -03 Caught SIGTERM, shutting down..
                      out 02 15:39:57 raspberrypi systemd[1]: Stopping dump1090 ADS-B receiver (FlightAware customization)...
                      out 02 15:39:57 raspberrypi dump1090-fa[6614]: Wed Oct 2 15:39:57 2019 -03 Waiting for receive thread termination
                      out 02 15:39:58 raspberrypi dump1090-fa[6614]: Wed Oct 2 15:39:58 2019 -03 Normal exit.
                      out 02 15:39:58 raspberrypi systemd[1]: dump1090-fa.service: Succeeded.
                      out 02 15:39:58 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
                      out 02 15:39:58 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
                      out 02 15:39:58 raspberrypi dump1090-fa[7901]: Wed Oct 2 15:39:58 2019 -03 dump1090-fa 3.7.2 starting up.
                      out 02 15:39:58 raspberrypi dump1090-fa[7901]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000)
                      out 02 15:39:59 raspberrypi dump1090-fa[7901]: Found Rafael Micro R820T tuner
                      out 02 15:39:59 raspberrypi dump1090-fa[7901]: rtlsdr: enabling tuner AGC
                      out 02 15:39:59 raspberrypi dump1090-fa[7901]: Allocating 4 zero-copy buffers

                      Comment


                      • #12
                        Looks good, do you have aircraft on the local map?

                        http://192.168.1.146/tar1090/

                        As i said if you re-run the graphs install, that should work now as well.

                        Comment


                        • #13
                          Originally posted by wiedehopf View Post
                          After installing dump1090-fa as shown in the previous post, you can check the log for that, it's much easier to handle than the fr24feed log.

                          The log for that:
                          sudo journalctl --no-pager -u dump1090-fa

                          Otherwise the easiest way to check the fr24feed log is actually:
                          sudo systemctl stop fr24feed
                          sudo fr24feed

                          It will now run on the console and you can see the log.
                          If you are done, you'll need to stop it and restart the service:
                          Ctrl-C to interrupt
                          sudo systemctl restart fr24feed

                          Obviously this isn't a permanent solution to check the logs, but it might show if the problem appears immediately.

                          Might be a power supply problem if the dongle stopped working, can you try another power supply?
                          Is the dongle plugged in directly? You can try another USB port.
                          yes, it s plugged in directly.
                          Changed ports and the same.

                          Ill get a new power supply for testing purpose.

                          Comment


                          • #14
                            Captain wiedehopf
                            graphs working now. In blank but working.
                            nothing on tar1090.

                            I'll leave a few minutes and will check it back soon.

                            So far, thanks a lot!

                            Comment


                            • #15
                              Hmm, it could be that one of the connections is loose?

                              If you want, you can run a spectrum scan, that should show if it's very strong interference or a loose connection
                              https://forum.flightradar24.com/thre...ignals-In-Area

                              (The TV antenna itself should not be a problem, but if there is a bad amplifier or something else there, it could be interference.)
                              Last edited by wiedehopf; 2019-10-02, 19:19.

                              Comment

                              Working...
                              X