Announcement

Collapse
No announcement yet.

New Pi receiver - please help

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

  • New Pi receiver - please help

    I am trying to set up a new pi based receiver but would like to ask for help to make it work. The unit appears to boot ok (to a login prompt seen on a monitor) and its availability is shown in statistics on flightradar24.com when it is on but at the same time it shows as offline and also no planes are shown as being received (also on viewing port 8754). The antenna and DVB stick do show plane data when connected to an XP laptop running rtl1090 so these appear to be ok. The Pi is an early model B paired with a 1G SD card on which I loaded 1.0.18-7 software. Any suggestions on how to proceed to debug this would be gratefully received. I am not very familiar with linux. I have disabled MLAT on setup page as my Pi is not a B+.

  • #2
    I am a newbie, but I don't think a 1G card is big enough. I am running mine with 32G (overkill, I am sure) and I think I saw somewhere that 4G was absolute minimum. Hopefully you will get a more authoritative answer shortly.

    Comment


    • #3
      Just to add to the above the command "sudo service fr24 status" shows as "active (running)" in green + other info, but "sudo service dump1090 status" shows "Loaded: not-found (Reason: No such file or directory) Active:inactive (dead)"

      I have tried rewriting the image to a different (2G) SD card but this gives the same results.

      The Pi is a revision 0002.

      There are no obvious startup errors and the web settings and status page can be viewed ok on a PC and the hdmi output and login to pi via a keyboard appear to work ok.

      Thanks to jcinnb for reply - If no luck I'll try to find a 4G card but the 1 and 2 appear to boot ok and the unzipped image file size is only 972.8KB. Also the info page does say a 1GB card is ok though for my Pi it's SD not microSD as listed there.

      Comment


      • #4
        Configured wrong or producing an error (likely can't connect to stick due to blacklist)

        Lose the word service from the lines and look for errors

        http://forum.flightradar24.com/showthread.php?p=74834

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

        Comment


        • #5
          Thanks for replies but still struggling...
          Have looked through all of boot up sequence (by videoing it and looking frame by frame!) and can see no errors. USB dongle is recognised as Realtek RTL2838UHIDIR and no errors shown.
          I am not clear whether I'm looking for a hardware or software error (especially blacklist comment). I thought this was an "appliance" image that would just work with the hardware parts I have. Even connecting a monitor and keyboard was more than I expected to do! My command line experience is very limited.
          I am not sure how much of the additional FAQs and info applies to the image I am using and in particular whether dump1090 should be running or not in my system (it appears not - see above).
          I am also still puzzled why my system shows available time, when powered up, in my fr24 account, but also always shows as offline.
          Finally, are there ANY software settings I should be doing to suit my hardware? The only thing I have tried changing from default in the :8754 web config page is to set MLAT to off.
          Could anyone else also confirm if using a 1 or 2G SD card with this image in an early Pi works ok? It would be good to hear if it's worked for you (or not!).

          Comment


          • #6
            Hi Sandbar,

            I think the best option is to start simple and check the logs first to see what error you are getting. Log in to your pi and use this command if you didn't change the log file location: tail -f /var/log/fr24feed.log
            Once you know the error that you are getting, it would become easier to figure out what the problem is.
            --

            Comment


            • #7
              Thanks Khan, After the initial few lines the log file command you gave produces the following result:

              These 5 lines repeated every 5 to 6 seconds with different values of xxxx

              [reader] [i]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --raw --mlat)
              [reader] [i]Connected to the receiver, configuring
              [reader] [i]Configured, processing messages
              [reader] [i]Connection terminated
              [main] [i] Terminating child process xxxx with SIGETERM

              Also these 2 lines interspersed about every 30 seconds:

              [feed][n]ping xx
              [feed][n]syncing stream result: 1

              Also occasionally

              [time][i]Synchronizing time via NTP
              [time][i]Time synchronized correctly, offset +0.0003 seconds

              [stats][e] Cached feed_id 107052 for network T
              [stats][i]sent 16 bytes

              Comment


              • #8
                The value of xxxx in the SIGETERM line increments by 4 each time
                The ping value increments by 1

                Comment


                • #9
                  Page
                  http://IP:8754/settings.html

                  Comment


                  • #10
                    These settings work good. I copied them in and off to races!

                    Comment


                    • #11
                      I have started again from scratch with reflashed SD card, having tried changes suggested by abcd567 without success. I am no longer getting the reader restarts posted previously (not sure why). Latest logfile (as suggested by Khan) after software restart posted below - I'd appreciate to know if this indicates a problem. Still no aircraft tracked apparently and showing offline though available!

                      2016-09-16 22:20:41 | [main][i]FR24 Feeder/Decoder
                      2016-09-16 22:20:41 | [main][i]Version: 1.0.18-7/generic
                      2016-09-16 22:20:41 | [main][i]Built on Jul 11 2016 09:24:44 (HEAD-91e2757.git/Linux/armv7l)
                      2016-09-16 22:20:41 | [main][i]Copyright 2012-2016 Flightradar24 AB
                      2016-09-16 22:20:41 | [main][i]http://flightradar24.com
                      2016-09-16 22:20:41 | [main][i]DNS mode: LIBC
                      2016-09-16 22:20:41 | [main][i]Automatic updates are DISABLED
                      2016-09-16 22:20:41 | ERROR
                      2016-09-16 22:20:41 | [main][i]Reader thread started
                      2016-09-16 22:20:41 | [main][i]Socket server started
                      2016-09-16 22:20:41 | [time][i]Synchronizing time via NTP
                      2016-09-16 22:20:41 | [reader][i]Initializing reader
                      2016-09-16 22:20:41 | [reader][i]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --raw)
                      2016-09-16 22:20:41 | [reader][i]Connected to the receiver, configuring
                      2016-09-16 22:20:41 | [bs][i]Initializing server
                      2016-09-16 22:20:41 | [bs][i]Starting server on 0.0.0.0:30003
                      2016-09-16 22:20:41 | [master][i]Starting processing thread
                      2016-09-16 22:20:41 | [httpd][i]Server started, listening on 0.0.0.0:8754
                      2016-09-16 22:20:41 | [reader][i]Configured, processing messages
                      2016-09-16 22:20:45 | [time][i]Time synchronized correctly, offset +0.0001 seconds
                      2016-09-16 22:20:45 | [main][i]Feed Network client started
                      2016-09-16 22:20:45 | [main][i]RAW data server started
                      2016-09-16 22:20:45 | [raw][i]Initializing server
                      2016-09-16 22:20:45 | [raw][i]Starting server on 0.0.0.0:30002
                      2016-09-16 22:20:45 | [feed][i]Downloading configuration
                      2016-09-16 22:20:45 | [feed][c]Interval: 5s
                      2016-09-16 22:20:45 | [feed][c]Latitude: 51.0504
                      2016-09-16 22:20:45 | [feed][c]Longitude: -1.3299
                      2016-09-16 22:20:45 | [feed][c]GND: YES
                      2016-09-16 22:20:45 | [feed][c]NonADSB: YES
                      2016-09-16 22:20:45 | [feed][c]Timestamps: optional
                      2016-09-16 22:20:45 | [feed][c]Max range AIR: 350.0nm
                      2016-09-16 22:20:45 | [feed][c]Max range GND: 100.0nm
                      2016-09-16 22:20:45 | [feed][i]defined 5 servers
                      2016-09-16 22:20:45 | [feed][n]EGHI83@83.140.21.87:8099/UDP
                      2016-09-16 22:20:45 | [feed][n]connecting
                      2016-09-16 22:20:45 | [stats][i]Stats thread started
                      2016-09-16 22:20:45 | [feed][n]connected via UDP (fd 27)
                      2016-09-16 22:20:45 | [feed][n]working
                      2016-09-16 22:21:15 | [feed][n]ping 1
                      2016-09-16 22:21:16 | [feed][n]syncing stream result: 1
                      2016-09-16 22:21:46 | [feed][n]ping 2
                      2016-09-16 22:21:47 | [feed][n]syncing stream result: 1
                      2016-09-16 22:22:16 | [feed][n]ping 3
                      2016-09-16 22:22:17 | [feed][n]syncing stream result: 1
                      2016-09-16 22:22:46 | [feed][n]ping 4
                      2016-09-16 22:22:47 | [feed][n]syncing stream result: 1
                      2016-09-16 22:23:16 | [feed][n]ping 5
                      2016-09-16 22:23:17 | [feed][n]syncing stream result: 1

                      Comment


                      • #12
                        Originally posted by Sandbar View Post
                        I have started again from scratch with reflashed SD card, having tried changes suggested by abcd567 without success. I am no longer getting the reader restarts posted previously (not sure why). Latest logfile (as suggested by Khan) after software restart posted below - I'd appreciate to know if this indicates a problem. Still no aircraft tracked apparently and showing offline though available!


                        2016-09-16 22:20:45 | [feed][c]GND: YES
                        2016-09-16 22:20:45 | [feed][c]NonADSB: YES
                        2016-09-16 22:20:45 | [feed][c]Timestamps: optional
                        2016-09-16 22:20:45 | [feed][c]Max range AIR: 350.0nm
                        2016-09-16 22:20:45 | [feed][c]Max range GND: 100.0nm
                        2016-09-16 22:20:45 | [feed][i]defined 5 servers
                        2016-09-16 22:20:45 | [feed][n]EGHI83@83.140.21.87:8099/UDP
                        2016-09-16 22:20:45 | [feed][n]connecting
                        2016-09-16 22:20:45 | [stats][i]Stats thread started
                        2016-09-16 22:20:45 | [feed][n]connected via UDP (fd 27)
                        2016-09-16 22:20:45 | [feed][n]working
                        2016-09-16 22:21:15 | [feed][n]ping 1
                        2016-09-16 22:21:16 | [feed][n]syncing stream result: 1
                        2016-09-16 22:21:46 | [feed][n]ping 2
                        2016-09-16 22:21:47 | [feed][n]syncing stream result: 1
                        2016-09-16 22:22:16 | [feed][n]ping 3
                        2016-09-16 22:22:17 | [feed][n]syncing stream result: 1
                        2016-09-16 22:22:46 | [feed][n]ping 4
                        2016-09-16 22:22:47 | [feed][n]syncing stream result: 1
                        2016-09-16 22:23:16 | [feed][n]ping 5
                        2016-09-16 22:23:17 | [feed][n]syncing stream result: 1
                        Per my common errors...

                        Code:
                        2016-01-27 00:35:36 | [feed][n]ping 1
                        2016-01-27 00:36:06 | [feed][n]ping 2
                        2016-01-27 00:36:36 | [feed][n]ping 3
                        2016-01-27 00:37:06 | [feed][n]ping 4
                        2016-01-27 00:37:36 | [feed][n]ping 5
                        2016-01-27 00:38:06 | [feed][n]ping 6
                        2016-01-27 00:38:36 | [feed][n]ping 7
                        No data is being received by hardware to upload
                        - Check connections
                        - Incorrect data format received from receiver or software for chosen receiver type
                        - Wrong port/type specified from software supplying data
                        Now is the time to confirm you can actually receive distant signals
                        Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                        Comment


                        • #13
                          Thanks Oblivian, I had seen that in your common errors but was not sure if the "syncing" line inbetween meant it was ok. As I said earlier, my antenna and stick do work using rtl1090 and zadig driver on an old xp laptop and see 10+ aircraft up to about 100km away (currently seeing about 35) but I am yet to see even one using the fr24 1G image in my Pi with the same stick/antenna. This should be enough for testing surely? I assume the setup defaults in the fr24 image should be ok, including the DVB stick - the options posted by abcd567 didn't improve things (though thanks for the suggestion). Regarding the "Incorrect data format..." and "Wrong port/type...", is there anything I should need to change in the supplied software image? Having changed psu, SD card and with a working stick/antenna the only common factor is the Pi itself - this is an early one with 256K memory - should this definitely be ok (it works ok with other software such as Runeaudio)? Last question, the help pages suggest trying command "sudo service dump1090 status" - what should be the result of this? (See mine above).

                          Comment


                          • #14
                            'Syncing Stream' appears to be a simple response to acknowledge the server got the 'nothing to upload' keep-alive ping you see going out.

                            I see the same with my test unit when the TV antenna is not able to see the current 3 contacts above 25,000ft that my external antenna and Beast currently is

                            A result of no data for a period of time also appears to cause the feeder to auto restart. I just experienced this..
                            2016-09-17 23:11:51 | [reader][w]Global timeout exceeded, 0 msgs, 0 resyncs, reconnecting

                            The Dump1090 command would normally report the status of the 2nd portion of the uploader required to connect to the stick and tune to the frequency and translate the data (mentioned in the first how it works post). This will only work if fr24feed that spawns it is running at the time. As seen by reader]Connecting to DVBT receiver via (exe:///usr/lib/fr24/dump1090 --raw --mlat) output.

                            However... in testing, it appears the bundle version may infact have the status ability since removed (yipee :/) in favour of saving confusion and allowing users to run separate versions of it.
                            And I'll need to update to reflect. But in general its not needed as long as you can see it spawn during startup without errors and 'pgrep -l dump1090' shows an instance running.

                            It may infact just be a case of the earlier models do not have the grunt to run the 2-level processing Dump1090 does. But until someone running the same version attempts to test we may not know
                            Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                            Comment


                            • #15
                              Thanks again Oblivian for the help. "pgrep -l dump1090" gets the response "572 dump1090" so I guess that's ok.
                              I will try to borrow another DVB stick to try. I have no other Pi, or access to one currently, so hopefully someone who has tried an early Pi will respond to report success or otherwise.
                              I thought I'd found a good use for my old Pi but maybe not...

                              Comment

                              Working...
                              X