Announcement

Collapse
No announcement yet.

Connection terminated - receiver disappears

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

  • Connection terminated - receiver disappears

    HW: RPi 3B+
    OS: Buster (10)

    When the RTL-SDR is connected it receives a USB-instance/number and in visible with command "lsusb".

    But upon starting fr24feed there seems to be a problem writing to the device and then it disappears and is not longer reachable nor visible in "lsusb". A physical disconnect/connect is needed to make the RTL-SDR re-appear.

    So, it seems to be the correct hardware, I can't find any other program using the device so what is left is power-issues.
    The RPi have a power supply with 2,5A. Not sure what the RPi itself needs but the RTL-SDR can't need that much? It it not transmitting..


    [I]2021-02-26 21:16:57 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
    2021-02-26 21:16:57 | [reader][i]Connected to the receiver, configuring
    2021-02-26 21:16:57 | [reader][i]Configured, processing messages
    2021-02-26 21:16:57 | [mlat][i]Waiting for MLAT configuration
    Fri Feb 26 21:16:57 2021 CET dump1090-mutability v1.14 starting up.
    Found 1 device(s):
    0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)

    Found Rafael Micro R820T tuner
    r82xx_write: i2c wr failed=-1 reg=0f len=1
    r82xx_init: failed=-1
    rtlsdr_demod_write_reg failed with -1
    rtlsdr_demod_read_reg failed with -1
    rtlsdr_demod_write_reg failed with -1
    rtlsdr_demod_read_reg failed with -1
    r82xx_write: i2c wr failed=-1 reg=05 len=1
    rtlsdr_demod_write_reg failed with -1
    rtlsdr_demod_read_reg failed with -1
    Max available gain is: 49.60 dB
    Setting gain to: 49.60 dB
    rtlsdr_demod_write_reg failed with -1
    rtlsdr_demod_read_reg failed with -1
    r82xx_write: i2c wr failed=-1 reg=05 len=1
    rtlsdr_demod_write_reg failed with -1
    rtlsdr_demod_read_reg failed with -1
    Error setting tuner gains
    2021-02-26 21:16:57 | [reader][i]Connection terminated
    2021-02-26 21:16:57 | [main][i]Terminating child process 17590 with SIGTERM
    2021-02-26 21:16:58 | [time][i]Synchronizing time via NTP
    2021-02-26 21:16:58 | [time][i]Time synchronized correctly, offset +0.007 seconds
    2021-02-26 21:16:58 | [main][i]Feed Network client started
    2021-02-26 21:16:58 | [feed][i]Downloading configuration
    2021-02-26 21:16:58 | [feed][d]fetching configuration
    2021-02-26 21:16:59 | [feed][i]configuring decoder
    2021-02-26 21:16:59 | [feed][c]Max range AIR: 350.0nm
    2021-02-26 21:16:59 | [feed][c]Max range GND: 100.0nm
    2021-02-26 21:16:59 | [feed][i]configuration changed
    2021-02-26 21:16:59 | [feed][i]defined 3 servers
    2021-02-26 21:16:59 | [feed][c]Timestamps: optional
    2021-02-26 21:16:59 | [feed][n]ESNZ13@185.218.24.22:8099/UDP
    2021-02-26 21:16:59 | [feed][n]connecting
    2021-02-26 21:16:59 | info | [stats]Stats thread started
    2021-02-26 21:16:59 | info | Stopping ReceiverACSender threads for feed
    2021-02-26 21:16:59 | info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.2 4:8099, feed: ESNZ13, send_interval: 5s/1s, max age: 15s, send metadata: true, mode: 1, filtering: true
    2021-02-26 21:16:59 | info | Network thread connecting to 185.218.24.22:8099 for feed ESNZ13
    2021-02-26 21:16:59 | [feed][n]connected via UDP (fd 27)
    2021-02-26 21:16:59 | [feed][i]Feed connected
    2021-02-26 21:16:59 | [feed][n]working
    2021-02-26 21:17:02 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
    2021-02-26 21:17:02 | [reader][i]Connected to the receiver, configuring
    2021-02-26 21:17:02 | [reader]Configured, processing messages
    Fri Feb 26 21:17:02 2021 CET dump1090-mutability v1.14 starting up.
    Found 1 device(s):
    0: , , SN: (currently selected)

    rtlsdr_write_reg failed with -1
    Resetting device...
    rtlsdr_write_reg failed with -4
    rtlsdr_write_reg failed with -4
    :




  • #2
    SDR failure or insufficient voltage at the SDR.

    SDR failure means you just need a new SDR.

    Insufficient voltage would be either the power supply going bad or it can be a USB extension used dropping too much voltage.

    This command will show nothing unless the power is bad:
    sudo dmesg --ctime | grep voltage

    It's not necessarily there if the SDR has low voltage but if it has any output then get a better power supply. (official RPi power supply highly recommended)
    Phone chargers might say 2.5 A but that doesn't mean the output voltage is stable enough for an RPi.
    Last edited by wiedehopf; 2021-02-27, 06:45.

    Comment


    • #3
      I have the original RPi-power supply but maybe it has deteriorated. I tried to change the USB-cord to the RTL-SDR. Now it doesn't crash upon start but it seems that the device is not responding as it should - or is it just that there are no flights passing by right now? Anyway - it seems to be a power problem. I will measure how much current that the device really need.

      How should "Global timeout exceeded" be interpreted? Good or bad?

      [I]2021-02-27 21:55:40 | [feed][n]syncing stream result: 1
      2021-02-27 21:55:51 | [reader][w]Global timeout exceeded, 0 msgs, 0 resyncs, reconnecting
      2021-02-27 21:55:51 | [reader][i]Connection terminated
      2021-02-27 21:55:51 | [main][i]Terminating child process 2309 with SIGTERM
      Sat Feb 27 21:55:51 2021 CET Caught SIGTERM, shutting down..

      2021-02-27 21:55:56 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw)
      2021-02-27 21:55:56 | [reader][i]Connected to the receiver, configuring
      2021-02-27 21:55:56 | [reader]Configured, processing messages
      Sat Feb 27 21:55:56 2021 CET dump1090-mutability v1.14 starting up.
      Found 1 device(s):
      0: Realtek, RTL2838UHIDIR, SN: 00000000 (currently selected)
      Found Rafael Micro R820T tuner
      Max available gain is: 49.60 dB
      Setting gain to: 49.60 dB

      Exact sample rate is: 2000000.052982 Hz
      Gain reported by device: 49.60 dB
      2021-02-27 21:56:09 | [feed][n]ping 55
      2021-02-27 21:56:10 | [feed][n]syncing stream result: 1


      Comment


      • #4
        The current usually isn't the issue but the voltage drop is.

        USB extensions can drop quite a bit of voltage ... some of them use barely any copper.
        And SDRs can have issues at 4.7 V probably which the RPi itself might still be able to cope with.

        Comment


        • #5
          I used the supplied cord and it works well with Win7 but maybe the USB-port is better in keeping the voltage. Or the setting/writing to SDR is causing the voltage to drop just a bit extra, and very short in time, to make is reboot or whatever is does when it fails.

          Maybe I'll try a Y-cable and a separate power supply for the SDR.

          Comment


          • #6
            So, what about the Global Timeout then?

            They come regularly but it seems that the fr24feed can recover. Is it just a Watchdog?

            [I]2021-02-27 22:16:09 | [feed][n]ping 95
            2021-02-27 22:16:10 | [feed][n]syncing stream result: 1
            Sat Feb 27 22:16:33 2021 CET Caught SIGTERM, shutting down..

            2021-02-27 22:16:33 | [reader][w]Global timeout exceeded, 0 msgs, 0 resyncs, reconnecting
            2021-02-27 22:16:33 | [reader][i]Connection terminated
            2021-02-27 22:16:33 | [main]Terminating child process 2427 with SIGTERM
            Sat Feb 27 22:16:33 2021 CET Normal exit.


            Comment


            • #7
              I'm not familiar with that as i run a standalone decoder.
              https://github.com/wiedehopf/adsb-sc...ion-for-readsb

              But that uses 2.4 MHz sample rate like dump1090-fa / mutability 1.15
              That higher sample rate might be an issue if the SDR is on its way out.

              Or even when the SDR is technically working now, the signal stage is damaged by static electricity or something.

              Comment


              • #8
                I believe

                reader][w]Global timeout exceeded, 0 msgs, 0 resyncs, reconnecting

                Is 'we got 0 messages and sync from you in x time as expected. So we're killing the connection to restart it just incase'
                Have over 55 keep-alive pings in your first post alone. Only does that when there's no traffic being uploaded
                Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                Comment


                • #9
                  Now that I look on another receiver, that works, it has the same Global Timeout-stuff but when an aeroplane passes over then it receives that transponder code. There is one incomming within 30 mins so lets see if it gets received by one or both receivers.

                  Comment


                  • #10
                    So I attached the USB voltage/current-meter (USB-inline).
                    It shows, on a working stick:
                    Voltage: 4,80V (during operation)
                    Current: 0,23A (during operation)

                    The one I had trouble with is working now that I changed to a shorter USB-cable. So maybe the problem was a combination of weak UAB-port on RPi and weak cable (thin wires)..

                    Comment


                    • #11
                      The Raspberry Pi 3B+ needs a stable 5.1 volt voltage, 2.5 amps. I also often had problems of that kind. Until I bought an original 15 Watt Raspberry power supply. Many other power supplies that bring the voltage have cables that are too thin. This leads to voltage losses. And the system no longer works reliably.
                      Last edited by MillerBerlin; 2021-03-01, 09:03.
                      EDDI90 | RaspberryPi3B, Nooelec NESDR SMArt, homemade 7Element Collinear Antenna.

                      Comment


                      • #12
                        Well, again, the power supply is the original RPi one that came with the bundle i.e. 5,1V / 2,5A. I have a spare one to swap but if the power supply was fault then it should not be giving anything at all. I could shorten the power cable to reduce the loss and maybe try with separate power supply to the receiver using a Y-cable.

                        However, it seems be be an issue after all with the installation. If I start it with "systemctl" I get Connection Terminated but if I run "sudo fr24feed" from the command line it seems to work. I can't see the difference really.

                        Comment


                        • #13
                          4.8 V is still not great but probably not terrible either.
                          USB extensions for SDRs are problematic that's all there is to it.

                          You seem to have a really old installation.
                          I'd just recommend starting from scratch with a fresh sd-card
                          https://github.com/wiedehopf/adsb-wi...ADS-B-receiver

                          Alternatively you can just run the automatic readsb installation on the current system it will reconfigure fr24feed to use data from readsb.
                          If that also fails it's likely a hardware issue, somehow i doubt it's a software issue.

                          > However, it seems be be an issue after all with the installation. If I start it with "systemctl" I get Connection Terminated but if I run "sudo fr24feed" from the command line it seems to work. I can't see the difference really.
                          It could just be random chance and either the 4.8 V is insufficient or the SDR is just beyond hope and you need a new one.
                          The metal case rtl-sdr blog v3 SDRs are very nice.
                          The NESDR sdrs are nice also.

                          Or you could get an FA Pro+ SDR with builtin 1090 Mhz filter / LNA.

                          Comment


                          • #14
                            Originally posted by folkeorg View Post
                            Well, again, the power supply is the original RPi one that came with the bundle i.e. 5,1V / 2,5A. ....

                            Okay, just read it again. So you have a power supply that came in a bundle. And you use a USB extension for the SDR stick. I also had problems with an USB extension. While the Flightaware Pro+ SDR runs without problems with an extension, a Nooelec NESDR stick with the same extension does not work at all.
                            EDDI90 | RaspberryPi3B, Nooelec NESDR SMArt, homemade 7Element Collinear Antenna.

                            Comment


                            • #15
                              I connected another of these receivers yesterday. That one had a cable that was DOA i.e. it did not provide power to the receiver at all. I swapped it for another cable and then the receiver started and worked as it should. The supplied cables seems to be rubbish!

                              Here I connected a 5m extension USB-cable and is measuring voltage and current. It is working well on 4,87VDC (and some 230mA). Also using non-supplied cord to the receiver.

                              USB.jpg

                              Comment

                              Working...
                              X