Announcement

Collapse
No announcement yet.

problem with dump1090-mutability 1.15

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

  • problem with dump1090-mutability 1.15

    Hello,
    I changed my setup for the feed from windows to Pi.

    everything is working fine except that every some time the dump1090-mutability (1.15) stops working and I have to do
    "sudo service dump1090-mutability restart" to get it working again.

    thanks in advance,
    Bar
    Bar Levy
    T-LLSD4

  • #2
    Such problems are often caused by dc power supply and changing DC adapter often solves it.
    What is the nameplate rating (DC Volts & Amps) of your DC adaptor?

    Comment


    • #3
      Originally posted by abcd567 View Post
      Such problems are often caused by dc power supply and changing DC adapter often solves it.
      What is the nameplate rating (DC Volts & Amps) of your DC adaptor?
      Switching power supply
      5V 3000mah

      this is what came with the Pi
      Bar Levy
      T-LLSD4

      Comment


      • #4
        In theory that is sufficient. It may still be the problem if it is a cheap/knockoff one. (You could try getting a "Official Raspberry Pi 3 power supply" and see if that helps)

        On the remote chance that something is in the logs, could you share the output of this command it may contain a clue:

        tail -n80 /var/log/dump1090-mutability.log

        Comment


        • #5
          i uploaded the full file here:
          https://drive.google.com/open?id=18v...njPPAfDGzJLdHK

          this is the command result:
          tail -n80 /var/log/dump1090-mutability.log
          Fri Apr 5 17:28:01 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:29:02 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:30:02 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:31:02 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:32:02 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:33:03 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:34:03 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:35:03 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:36:03 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:37:04 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:38:04 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:39:04 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:40:04 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:41:05 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:42:05 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:43:05 2019 IDT No data received from the dongle for a long time, it may have wedged


          Statistics: Fri Apr 5 16:43:41 2019 IDT - Fri Apr 5 17:43:41 2019 IDT
          Local receiver:
          0 samples processed
          0 samples dropped
          0 Mode A/C messages received
          0 Mode-S message preambles received
          0 with bad message format or invalid CRC
          0 with unrecognized ICAO address
          0 accepted with correct CRC
          0 accepted with 1-bit error repaired
          0 messages with signal power above -3dBFS
          Messages from network clients:
          0 Mode A/C messages received
          0 Mode S messages received
          0 with bad message format or invalid CRC
          0 with unrecognized ICAO address
          0 accepted with correct CRC
          0 accepted with 1-bit error repaired
          0 total usable messages
          0 surface position messages received
          0 airborne position messages received
          0 global CPR attempts with valid positions
          0 global CPR attempts with bad data
          0 global CPR attempts that failed the range check
          0 global CPR attempts that failed the speed check
          0 global CPR attempts with insufficient data
          0 local CPR attempts with valid positions
          0 aircraft-relative positions
          0 receiver-relative positions
          0 local CPR attempts that did not produce useful positions
          0 local CPR attempts that failed the range check
          0 local CPR attempts that failed the speed check
          0 CPR messages that look like transponder failures filtered
          0 non-ES altitude messages from ES-equipped aircraft ignored
          0 unique aircraft tracks
          0 aircraft tracks where only one message was seen
          CPU load: 0.3%
          0 ms for demodulation
          0 ms for reading from USB
          10277 ms for network input and background tasks
          Fri Apr 5 17:44:05 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:45:06 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:46:06 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:47:06 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:48:06 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:49:07 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:50:07 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:51:07 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:52:07 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:53:08 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:54:08 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:55:08 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:56:09 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:57:09 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:58:09 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 17:59:09 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 18:00:10 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 18:01:10 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 18:02:10 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 18:03:11 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 18:04:11 2019 IDT No data received from the dongle for a long time, it may have wedged
          Fri Apr 5 18:05:11 2019 IDT No data received from the dongle for a long time, it may have wedged
          Bar Levy
          T-LLSD4

          Comment


          • #6
            Originally posted by wiedehopf View Post
            In theory that is sufficient. It may still be the problem if it is a cheap/knockoff one. (You could try getting a "Official Raspberry Pi 3 power supply" and see if that helps)

            On the remote chance that something is in the logs, could you share the output of this command it may contain a clue:

            tail -n80 /var/log/dump1090-mutability.log
            I tried uploading the full file with a link but my post won't show..

            but in the file I can see a lost of these:
            Fri Apr 5 11:32:17 2019 IDT No data received from the dongle for a long time, it may have wedged
            Fri Apr 5 11:33:17 2019 IDT No data received from the dongle for a long time, it may have wedged
            Fri Apr 5 11:34:17 2019 IDT No data received from the dongle for a long time, it may have wedged
            Fri Apr 5 11:35:17 2019 IDT No data received from the dongle for a long time, it may have wedged
            Fri Apr 5 11:36:18 2019 IDT No data received from the dongle for a long time, it may have wedged
            and after some time:
            Fri Apr 5 11:36:19 2019 IDT Caught SIGTERM, shutting down..

            Fri Apr 5 11:36:19 2019 IDT Waiting for receive thread termination
            Fri Apr 5 11:36:50 2019 IDT dump1090-mutability v1.15~dev starting up.
            Using sample converter: UC8, integer/table path
            Found 1 device(s):
            0: , RTL2838UHIDIR, SN: 00000001 (currently selected)
            rtlsdr_demod_read_reg failed with -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
            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
            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
            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
            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
            rtlsdr_demod_write_reg failed with -1
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            weirdness: rtlsdr gave us a block with an unusual size (got 0 bytes, expected 262144 bytes)
            Bar Levy
            T-LLSD4

            Comment


            • #7
              Most likely it's insufficient power.

              Is the dongle plugged directly into the RPi?
              Try another USB port.

              Maybe you have a good phone charger that you could try instead of the power supply you have?
              (Only powerful phone chargers will work and even with those the mini usb cable is often limiting the power)

              Which RPi is it?

              (New users aren't allowed links, that's why your post didn't appear)
              Last edited by wiedehopf; 2019-04-05, 19:03.

              Comment


              • #8
                my RPi is 3 B+
                and the dongle is connected with a USB extender, this might make the problem I guess (it was working fine for years on windows PC)
                Bar Levy
                T-LLSD4

                Comment


                • #9
                  Don't use a range extender

                  Can't you just place the RPi where the receiver is?

                  Comment


                  • #10
                    Originally posted by wiedehopf View Post
                    Don't use a range extender

                    Can't you just place the RPi where the receiver is?
                    I am doing it now to test it, but I preferred to have it wired to the internet and not on wifi, but will check
                    Bar Levy
                    T-LLSD4

                    Comment


                    • #11
                      Can't you just use Ethernet cable where the USB range extender cable was?

                      Comment


                      • #12
                        it will not reach, but I planned to do it anyway, just waiting for equipment needed in the mail
                        Bar Levy
                        T-LLSD4

                        Comment


                        • #13
                          well it looks life now it is working ok when the dongle Is connected straight to the Pi

                          Thanks for the help!
                          Bar Levy
                          T-LLSD4

                          Comment

                          Working...
                          X