Announcement

Collapse
No announcement yet.

Pi feeding. USB stick dropping offline

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

  • #31
    pi@raspberrypi:~ $ sudo fr24feed-status
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2018-11-10 22:08:59.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: T-EGSC81.
    [ ok ] FR24 Tracked AC:.
    [FAIL] Receiver: down ... failed!
    [FAIL] FR24 MLAT: not running ... failed!
    pi@raspberrypi:~ $ lsusb
    Bus 001 Device 004: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
    Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
    Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    pi@raspberrypi:~ $

    Comment


    • #32
      Using sudo systemctl stop fr24feed, the. sudo fr24feed:


      Sat Nov 10 22:25:03 2018 GMT dump1090-mutability v1.15~dev starting up.
      Using sample converter: UC8, integer/table path
      Found 1 device(s):
      0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
      usb_claim_interface error -5
      Error opening the RTLSDR device: No such file or directory
      2018-11-10 22:25:03 | [reader][i]Connection terminated
      2018-11-10 22:25:03 | [main][i]Terminating child process 2642 with SIGTERM

      Comment


      • #33
        Crikey, slow down. 1 min between 3 posts gets confusing when a reply is mid-being written and more information comes in.

        Try to test, collate findings. And then produce rather than jump ahead hoping a quick update/command will fix it going offline.

        What we kinda know -
        your stick is going offline despite a presumed OK power supply.
        You now have a 2nd or 3rd radar ID with different airport code somehow - wrong GPS settings or miss-matched signup information
        Part way through my attempts to assist diagnosing you magically went from 1.14Dev (included in FR24feed package) to 1.15Dev - using ABCD567s guide? - that is not exactly what I mean't by using a vanilla OS and building on it to test the stick first.

        Since its not clear. We will assume you are running commands SUDO <command> - this will effect how software packages as outlined in the mutability 1.15-dev thread were installed. And if it completed all packages successfully. And the stopping of services with needing full permission.

        Are you running a USB extention cable?. These can cause power loads. If not, try a different bank of USB ports

        But to outline from data you have provided thus far. There are 2 distinct claim errors.
        usb_claim_interface error -6 = device in use
        usb_claim_interface error -5 = I/O data error.

        your most recent
        Using sudo systemctl stop fr24feed, the. sudo fr24feed:

        Sat Nov 10 22:25:03 2018 GMT dump1090-mutability v1.15~dev starting up.
        Using sample converter: UC8, integer/table path
        Found 1 device(s):
        0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
        usb_claim_interface error -5
        Error opening the RTLSDR device: No such file or directory
        2018-11-10 22:25:03 | [reader][i]Connection terminated
        2018-11-10 22:25:03 | [main][i]Terminating child process 2642 with SIGTERM
        Is still indicative of the stick data not being able to be accessed directly/chip offline

        However,
        Sat Nov 10 22:25:03 2018 GMT dump1090-mutability v1.15~dev starting up.
        Tends to indicate every time you run fr24feed - its force starting dump1090 as part of the startup. As if it has been specified in the config file - I would have thought during the full suite setup guide abcd567 produced, (or at least the fr24feed setup wizard) During Step 7 - this was loaded as a system service. And shouldn't be starting with fr24feed launch.

        Your setup should be like the middle shown here https://forum.flightradar24.com/thre...ll=1#post85177
        in particular
        - Don't populate COM/DEV/PATH field*
        * - Only populate COM/DEV/PATH to dump1090 version installed if FR24FEED required to force start it on loading (not already running as service)
        Per ABCD567 - do NOT select 'DVBT' as a feed type option if running dump1090-mutability 1.15-dev. It will mess things more

        If you stop the services (and confirm they are after each step..)
        sudo systemctl stop fr24feed
        <try to access :8754 config page - if still there, its still active = bad>
        sudo systemctl stop dump1090-mutability

        What does
        sudo rtl_test produce if left for 2-3mins (once you have reset the stick and its actually accessible)

        It should be like this.

        Ctrl-C will quit after a few mins.

        pi@raspberrypi:~ $ rtl_test
        Found 1 device(s):
        0: Realtek, RTL2838UHIDIR, SN: 00000001

        Using device 0: Generic RTL2832U OEM
        Found Rafael Micro R820T tuner
        Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
        [R82XX] PLL not locked!
        Sampling at 2048000 S/s.

        Info: This tool will continuously read from the device, and report if
        samples get lost. If you observe no further output, everything is fine.

        Reading samples in async mode...
        THEN if it appears OK.

        Run

        Sudo dump1090-mutability --interactive

        Hands off. Watch the table, see if it picks up planes. Or suddenly crashes because the stick has once again fallen off.
        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

        Comment


        • #34
          And finally, to make sure the last 2 not able to upload errors
          [FAIL] Receiver: down ... failed!
          [FAIL] FR24 MLAT: not running ... failed!
          (if starting OK on a clean reboot)

          aren't caused by address lookups.

          Make sure this is applied-

          https://forum.flightradar24.com/thre...l=1#post110885
          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

          Comment


          • #35
            Ok I have made a reinstall of the image to switch back to 1.14 mutability since I may have messed things up during the 1.15 install. So, after setting it up email etc, I do get the the mlat not running failed error. I have added the upload error fix. Would you like me to update to 1.15 dev?

            Comment


            • #36
              Gah.

              Which image? the cut down Pi24 and yet another radar ID. Or vanilla Stretch and then run the installer script. Both set the OS up very differently. The former, totally incompatible with the 1.15-DEV setup (as its pointed out in bold - it is not made to be messed with)

              Sit and test a fresh standard install as it is now.

              The IPV6 changes need a restart

              The goal is. Don't mess with it. If it aint broke. Leave it. But we still don't know if yours is. They way you described it going dead after 15mins is a legitimate issue if theres a USB Stick issue (overheating/power)

              However you compounded it by changing versions mid way, and changed the config from default, and re-running the feeder programms (there are 2, fr24feed and dump1090) while one config likely already set it up to run as a service on boot already.
              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

              Comment


              • #37
                Yes I know I had messed things up yesterday, sorry about that. I reinstalled raspbian stretch. I used the same sharing key as yesterday, so basically same radar. I have switched the USB stick from one port and moved it to another.

                After configuration, i have stopped the fr24feed service, then typed sudo fr24feed, I am getting this:

                2018-11-11 10:50:53 | [main][i]FR24 Feeder/Decoder
                2018-11-11 10:50:53 | [main][i]Version: 1.0.23-8/generic
                2018-11-11 10:50:53 | [main][i]Built on Oct 16 2018 08:10:47 (HEAD-2d57e58.git/Linux/static_armel)
                2018-11-11 10:50:53 | [main][i]Running on: raspbian9
                2018-11-11 10:50:53 | [main][i]Local IP(s): 192.168.0.12
                2018-11-11 10:50:53 | [main][i]Copyright 2012-2018 Flightradar24 AB
                2018-11-11 10:50:53 | [main][i]https://www.flightradar24.com
                2018-11-11 10:50:53 | [main][i]DNS mode: PING
                2018-11-11 10:50:53 | [main][i]Automatic updates are ENABLED
                2018-11-11 10:50:53 | OK
                2018-11-11 10:50:53 | [httpd][i]Server started, listening on 0.0.0.0:8754
                2018-11-11 10:50:53 | [main][i]Reader thread started
                2018-11-11 10:50:53 | [main][i]MLAT data feed started
                2018-11-11 10:50:53 | [reader][i]Initializing reader
                2018-11-11 10:50:53 | [mlat][i]Waiting for MLAT configuration
                2018-11-11 10:50:53 | [master][i]Starting processing thread
                2018-11-11 10:50:53 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
                2018-11-11 10:50:53 | [reader][i]Connected to the receiver, configuring
                2018-11-11 10:50:53 | [reader][i]Configured, processing messages
                Sun Nov 11 10:50:53 2018 GMT dump1090-mutability v1.14 starting up.
                Found 1 device(s):
                0: , , SN: (currently selected)
                rtlsdr_write_reg failed with -1
                Resetting device...
                2018-11-11 10:50:54 | [time][i]Synchronizing time via NTP
                rtlsdr_write_reg failed with -4
                rtlsdr_write_reg failed with -4
                rtlsdr_write_reg failed with -4
                rtlsdr_write_reg failed with -4
                rtlsdr_write_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_read_reg failed with -4
                rtlsdr_write_reg failed with -4
                rtlsdr_read_reg failed with -4
                rtlsdr_write_reg failed with -4
                rtlsdr_read_reg failed with -4
                rtlsdr_write_reg failed with -4
                rtlsdr_read_reg failed with -4
                rtlsdr_write_reg failed with -4
                No supported tuner found
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                Enabled direct sampling mode, input 1
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                Max available gain is: 0.00 dB
                Setting gain to: 0.00 dB
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                Exact sample rate is: 2000000.052982 Hz
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_demod_write_reg failed with -4
                rtlsdr_demod_read_reg failed with -4
                rtlsdr_write_reg failed with -4
                rtlsdr_write_reg failed with -4
                Gain reported by device: 0.00 dB
                Failed to submit transfer 0!
                Sun Nov 11 10:50:55 2018 GMT Warning: lost the connection to the RTLSDR device.
                rtlsdr_write_reg failed with -4
                Sun Nov 11 10:51:00 2018 GMT Trying to reconnect to the RTLSDR device..
                Found 1 device(s):
                0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
                rtlsdr_demod_write_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

                And couple mins later:

                2018-11-11 11:01:06 | [time][i]Synchronizing time via NTP
                2018-11-11 11:01:07 | [feed][n]ping 20
                2018-11-11 11:01:07 | [stats][i]sent 16 bytes
                2018-11-11 11:01:08 | [feed][n]syncing stream result: 1
                2018-11-11 11:01:08 | [reader][w]Global timeout exceeded, 0 msgs, 0 resyncs, reconnecting
                2018-11-11 11:01:08 | [reader][i]Connection terminated
                2018-11-11 11:01:08 | [main][i]Terminating child process 10911 with SIGTERM
                Sun Nov 11 11:01:08 2018 GMT Caught SIGTERM, shutting down..

                2018-11-11 11:01:11 | Could not terminate child process 10911 with SIGTERM, trying SIGKILL
                2018-11-11 11:01:17 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
                2018-11-11 11:01:17 | [reader][i]Connected to the receiver, configuring
                2018-11-11 11:01:17 | [reader][i]Configured, processing messages
                Sun Nov 11 11:01:17 2018 GMT dump1090-mutability v1.14 starting up.
                Found 1 device(s):
                0: , , SN: (currently selected)
                rtlsdr_write_reg failed with -1
                Resetting device...
                2018-11-11 11:01:19 | [time][i]Time synchronized correctly, offset +0.0027 seconds
                rtlsdr_write_reg failed with -4

                20 seconds later:
                Error setting tuner gains
                Sun Nov 11 11:01:30 2018 GMT Trying to reconnect to the RTLSDR device..
                Found 1 device(s):
                0: , , SN: (currently selected)
                usb_claim_interface error -6
                Error opening the RTLSDR device: Device or resource busy
                Sun Nov 11 11:01:35 2018 GMT Trying to reconnect to the RTLSDR device..
                Found 1 device(s):
                0: , , SN: (currently selected)
                usb_claim_interface error -6
                Error opening the RTLSDR device: Device or resource busy
                2018-11-11 11:01:37 | [feed][n]ping 21
                2018-11-11 11:01:38 | [feed][n]syncing stream result: 1
                Sun Nov 11 11:01:40 2018 GMT Trying to reconnect to the RTLSDR device..

                16 minutes later:

                Sun Nov 11 11:16:22 2018 GMT Trying to reconnect to the RTLSDR device..
                No supported RTLSDR devices found.
                Sun Nov 11 11:16:27 2018 GMT Trying to reconnect to the RTLSDR device..
                No supported RTLSDR devices found.


                lsusb:

                pi@raspberrypi:~ $ lsusb
                Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
                Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
                Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

                After reinserting,

                pi@raspberrypi:~ $ lsusb
                Bus 001 Device 025: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
                Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
                Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
                Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
                Last edited by DarkPlatinum; 2018-11-11, 11:20.

                Comment


                • #38
                  It's not just FR24feed you need to stop. If it crashes, it often leaves dump1090 running. (the bit that actually locks up and talks to the chips)

                  Need to stop both manually.
                  sudo systemctl stop dump1090-mutability

                  And after doing so, dont run fr24feed. But dump1090 in interactive. It should give better output if it is randomly failing.
                  sudo dump1090-mutability --interactive

                  But going by all those changing errors - most likely. Different USB stick or power supply needed more than a SW/setup issue.

                  All those come back to chip initialised, de-powering, RTL chip offline
                  Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                  Comment


                  • #39
                    Ok ill restart the pi and stop those services, on second.

                    Comment


                    • #40
                      Here is the dump mutability interactive:

                      Sun Nov 11 11:27:43 2018 GMT 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
                      rtlsdr_write_reg failed with -4
                      rtlsdr_write_reg failed with -4
                      rtlsdr_write_reg failed with -4
                      rtlsdr_demod_write_reg failed with -4
                      rtlsdr_demod_read_reg failed with -4
                      rtlsdr_demod_write_reg failed with -4
                      rtlsdr_demod_read_reg failed with -4


                      After waiting a bit, the aircraft screen loads up, but no aircraft shows up.
                      Last edited by DarkPlatinum; 2018-11-11, 11:37.

                      Comment


                      • #41
                        i left the raspberry pi running for over an hour, and just came back to see that the receiver is down. I checked lsusb, and it does not show the reciever though it is still being powered (There is a indicator light on it) does this mean my power supply is not adequate enough? Could I downclock the Pi so it takes less power consumption, but can still provide enough power to the dongle ?(I am going to assume now that the power supply cannot provide the enough power)

                        Comment


                        • #42
                          Ok, I have ordered a 3 amp power supply: https://www.ebay.co.uk/itm/DC-5V-3A-...72.m2749.l2649

                          I have downclocked the pi to 800 mhz, and disabled bluetooth. Also, the antenna I have recieved with my dongle, i have cut it down to 68mm as that is what people have told me to do. How do I get a good signal from aircraft? the antenna is right at my window(attached to the window with bluetack). Is there any setting you recommend?

                          Comment


                          • #43
                            Setting it up in a laptop/desktop will allow antenna tuning and confirm if the stick itself hadn't come out of a cheaper China factory.

                            Sent from my XT1092 using Tapatalk
                            Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                            Comment


                            • #44
                              Originally posted by Oblivian View Post
                              Setting it up in a laptop/desktop will allow antenna tuning and confirm if the stick itself hadn't come out of a cheaper China factory.

                              Sent from my XT1092 using Tapatalk
                              Could you tell me the name of the software that is available for antenna tuning, how to tune it, and running off of a Mac or Raspberry Pi running linux.

                              Comment

                              Working...
                              X