Announcement

Collapse
No announcement yet.

fr24feed not connecting

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

  • fr24feed not connecting

    Did the fr24feed setup, relaunched but I'm unable to connect it seems... I have RTL1090v3 and adsbscope currently running and showing all the aircraft. no-go on fr24feed it seems... any ideas?

    This is on a Win10 btw. latest downloaded fr24feed
    Last edited by razorseal; 2016-01-27, 03:40.

  • #2
    Here is the log:

    Code:
    2016-01-26 22:20:05 | [main][i]FR24 Feeder/Decoder [0x02107000]
    2016-01-26 22:20:05 | [main][i]Version: 1.0.16-9/generic
    2016-01-26 22:20:05 | [main][i]Built on Jan 18 2016 15:51:45 (r:284/Windows/i386)
    2016-01-26 22:20:05 | [main][i]Copyright 2012-2016 Flightradar24 AB
    2016-01-26 22:20:05 | [main][i]http://flightradar24.com)
    2016-01-26 22:20:05 | [main][i]Reader thread started
    2016-01-26 22:20:05 | [main][i]Socket server started
    2016-01-26 22:20:05 | [time][i]Synchronizing time via NTP
    2016-01-26 22:20:05 | [bs][i]Initializing server
    2016-01-26 22:20:05 | [bs][i]Starting server on 0.0.0.0:30003
    2016-01-26 22:20:05 | [bs][e]Could not bind socket to *:30003, errno=0
    2016-01-26 22:20:05 | [httpd][i]Server started, listening on 0.0.0.0:8754
    2016-01-26 22:20:05 | [reader][i]Initializing reader
    2016-01-26 22:20:05 | [master][i]Starting processing thread
    2016-01-26 22:20:05 | [reader][i]Connecting to Generic receiver via (exe://mr-dump1090.exe  --raw)
    2016-01-26 22:20:05 | [reader][i]Connected to the receiver, authenticating
    2016-01-26 22:20:05 | [reader][i]Authenticated, processing messages
    2016-01-26 22:20:07 | [reader][i]Connection terminated
    2016-01-26 22:20:12 | [reader][i]Connecting to Generic receiver via (exe://mr-dump1090.exe  --raw)
    2016-01-26 22:20:12 | [reader][i]Connected to the receiver, authenticating
    2016-01-26 22:20:12 | [reader][i]Authenticated, processing messages
    2016-01-26 22:20:14 | [reader][i]Connection terminated
    2016-01-26 22:20:19 | [reader][i]Connecting to Generic receiver via (exe://mr-dump1090.exe  --raw)
    2016-01-26 22:20:19 | [reader][i]Connected to the receiver, authenticating
    2016-01-26 22:20:19 | [reader][i]Authenticated, processing messages
    2016-01-26 22:20:21 | [reader][i]Connection terminated
    2016-01-26 22:20:24 | [time][i]Time synchronized correctly, offset +0.0055 seconds
    2016-01-26 22:20:24 | [main][i]Feed Network client started
    2016-01-26 22:20:24 | [main][i]RAW data server started
    2016-01-26 22:20:24 | [feed][i]Downloading configuration
    2016-01-26 22:20:24 | [raw][i]Initializing server
    2016-01-26 22:20:24 | [raw][i]Starting server on 0.0.0.0:30002
    2016-01-26 22:20:24 | [feed][c]Interval: 5s
    2016-01-26 22:20:24 | [feed][c]Latitude: 26.6832
    2016-01-26 22:20:24 | [feed][c]Longitude: -80.0955
    2016-01-26 22:20:24 | [feed][c]GND: YES
    2016-01-26 22:20:24 | [feed][c]NonADSB: YES
    2016-01-26 22:20:24 | [feed][c]Timestamps: optional
    2016-01-26 22:20:24 | [feed][c]Max range AIR: 350.0nm
    2016-01-26 22:20:24 | [feed][c]Max range GND: 100.0nm
    2016-01-26 22:20:24 | [stats][i]Stats thread started
    2016-01-26 22:20:24 | [feed][i]defined 1 server
    2016-01-26 22:20:24 | [feed][n]KPBI4@83.140.21.66:8099/UDP
    2016-01-26 22:20:24 | [feed][n]connecting
    2016-01-26 22:20:26 | [reader][i]Connecting to Generic receiver via (exe://mr-dump1090.exe  --raw)
    2016-01-26 22:20:26 | [reader][i]Connected to the receiver, authenticating
    2016-01-26 22:20:26 | [reader][i]Authenticated, processing messages
    2016-01-26 22:20:28 | [reader][i]Connection terminated
    2016-01-26 22:20:33 | [reader][i]Connecting to Generic receiver via (exe://mr-dump1090.exe  --raw)
    2016-01-26 22:20:33 | [reader][i]Connected to the receiver, authenticating
    2016-01-26 22:20:33 | [reader][i]Authenticated, processing messages
    2016-01-26 22:20:35 | [reader][i]Connection terminated
    2016-01-26 22:20:40 | [reader][i]Connecting to Generic receiver via (exe://mr-dump1090.exe  --raw)
    2016-01-26 22:20:40 | [reader][i]Connected to the receiver, authenticating
    2016-01-26 22:20:40 | [reader][i]Authenticated, processing messages
    2016-01-26 22:20:42 | [reader][i]Connection terminated

    Comment


    • #3
      You have BS= yes enabled (basestation out) this is conflicting, hence the unable to open socket. That means you have it already enabled in RTL1090

      RTL1090 connects to the USB directly.
      So does FR24feed. This can't be done at the same time.

      Either make FR24feed launch (it has its own web based view) and reconfigure RTL1090 to use TCP, or configure FR24feed to TCP and attach to RTL1090

      Both cannot run without reconfiguring one
      Posts not to be taken as official support representation - Just a helpful uploader who tinkers

      Comment


      • #4
        how can I configure FR24feed to TCP and attach it to RTL1090?

        and I have to disable BS. how is that done without doing the wizard thingy? through .ini file?
        Last edited by razorseal; 2016-01-27, 04:50.

        Comment


        • #5
          http://localhost:8754 when running.
          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

          Comment


          • #6
            Originally posted by Oblivian View Post
            http://localhost:8754 when running.
            Well I just shut off RTL1090, and now like you said, it's up and running. I appear to be online and transmitting AC out.

            now gotta figure out how to do the TCP thing and attach to RTL1090?

            I'm in settings with that address and not sure what to do after... lol

            Comment


            • #7
              Change receiver type to AVR-TCP, and enter the port as localhost:<port>

              <port> being one of the ones that RTL outputs on. Which I think is 31001
              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

              Comment


              • #8
                Originally posted by Oblivian View Post
                Change receiver type to AVR-TCP, and enter the port as localhost:<port>

                <port> being one of the ones that RTL outputs on. Which I think is 31001
                ok let me try that now.

                I actually just restarted the fr24feed and now it won't connect. (haven't done that tcp thing yet) Not sure what I did.. can't access http://localhost:8754 now =/ RTL1090 not running

                Code:
                2016-01-27 00:04:31 | [main][i]FR24 Feeder/Decoder [0x02107000]
                2016-01-27 00:04:31 | [main][i]Version: 1.0.16-9/generic
                2016-01-27 00:04:31 | [main][i]Built on Jan 18 2016 15:51:45 (r:284/Windows/i386)
                2016-01-27 00:04:31 | [main][i]Copyright 2012-2016 Flightradar24 AB
                2016-01-27 00:04:31 | [main][i]http://flightradar24.com)
                2016-01-27 00:04:31 | [main][i]Reader thread started
                2016-01-27 00:04:31 | [main][i]Socket server started
                2016-01-27 00:04:31 | [time][i]Synchronizing time via NTP
                2016-01-27 00:04:31 | [master][i]Starting processing thread
                2016-01-27 00:04:31 | [reader][i]Initializing reader
                2016-01-27 00:04:31 | [bs][i]Initializing server
                2016-01-27 00:04:31 | [reader][i]Connecting to Generic receiver via (exe://mr-dump1090.exe  --raw)
                2016-01-27 00:04:31 | [httpd][i]Server started, listening on 0.0.0.0:8754
                2016-01-27 00:04:31 | [bs][i]Starting server on 0.0.0.0:30003
                2016-01-27 00:04:31 | [reader][i]Connected to the receiver, authenticating
                2016-01-27 00:04:31 | [reader][i]Authenticated, processing messages
                2016-01-27 00:04:33 | [reader][i]Connection terminated
                2016-01-27 00:04:34 | [time][i]Time synchronized correctly, offset +0.0048 seconds
                2016-01-27 00:04:34 | [main][i]Feed Network client started
                2016-01-27 00:04:34 | [main][i]RAW data server started
                2016-01-27 00:04:34 | [feed][i]Downloading configuration
                2016-01-27 00:04:34 | [raw][i]Initializing server
                2016-01-27 00:04:34 | [raw][i]Starting server on 0.0.0.0:30002
                2016-01-27 00:04:34 | [feed][c]Interval: 5s
                2016-01-27 00:04:34 | [feed][c]Latitude: 26.6832
                2016-01-27 00:04:34 | [feed][c]Longitude: -80.0955
                2016-01-27 00:04:34 | [feed][c]GND: YES
                2016-01-27 00:04:34 | [feed][c]NonADSB: YES
                2016-01-27 00:04:34 | [feed][c]Timestamps: optional
                2016-01-27 00:04:34 | [feed][c]Max range AIR: 350.0nm
                2016-01-27 00:04:34 | [feed][c]Max range GND: 100.0nm
                2016-01-27 00:04:34 | [feed][i]defined 1 server
                2016-01-27 00:04:34 | [feed][n]KPBI4@83.140.21.66:8099/UDP
                2016-01-27 00:04:34 | [feed][n]connecting
                2016-01-27 00:04:34 | [stats][i]Stats thread started
                2016-01-27 00:04:38 | [reader][i]Connecting to Generic receiver via (exe://mr-dump1090.exe  --raw)
                2016-01-27 00:04:38 | [reader][i]Connected to the receiver, authenticating
                2016-01-27 00:04:38 | [reader][i]Authenticated, processing messages
                2016-01-27 00:04:40 | [reader][i]Connection terminated
                Last edited by razorseal; 2016-01-27, 05:08.

                Comment


                • #9
                  Windows version doesn't close properly. There will probably be a dump1090 instance already running in the background in task manager
                  Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                  Comment


                  • #10
                    Originally posted by Oblivian View Post
                    Windows version doesn't close properly. There will probably be a dump1090 instance already running in the background in task manager
                    Well this is annoying. it's not running. I also got it back up and running (unplugged the SDR dongle and replugged in)

                    shows it as sending packets (Sent 1 AC in 1 packet) but when I try to go to http://localhost:8754 it's not letting me

                    This webpage is not available

                    ERR_CONNECTION_REFUSED

                    maybe try a restart of computer. lol

                    edit: restart worked.
                    Last edited by razorseal; 2016-01-27, 05:20.

                    Comment


                    • #11
                      Originally posted by Oblivian View Post
                      Change receiver type to AVR-TCP, and enter the port as localhost:<port>

                      <port> being one of the ones that RTL outputs on. Which I think is 31001
                      Seems like that did the trick!!!

                      Comment


                      • #12
                        So why would my stats show offline, but fr24feed shows working?

                        T-KPBI4 Stats
                        Stats for:

                        Status: Offline
                        Current upload rate: 0 KB/s
                        First seen online: 2016-01-27 03:18:38
                        All dates and times are UTC

                        FR24 Link: Connected via UDP
                        FR24 Radar Code: T-KPBI4
                        Aircraft Tracked (ModeS & ADS-B): 0
                        Aircraft Uploaded: N/A
                        Receiver: avr-tcp, Connected
                        MLAT running: N/A

                        Also, what are the pings? just a ping because no a/c are seen and it's keeping connection alive?

                        Code:
                        2016-01-27 00:34:45 | [stats][i]Stats thread started
                        2016-01-27 00:35:05 | [feed][n]connected via TCP (fd 844)
                        2016-01-27 00:35:05 | [feed][n]switching to UDP
                        2016-01-27 00:35:06 | [feed][n]working
                        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

                        Comment


                        • #13
                          Correct.

                          Upload rate is for F- feeders only.
                          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                          Comment


                          • #14
                            Originally posted by Oblivian View Post
                            Correct.

                            Upload rate is for F- feeders only.
                            so the "offline" status is wrong? (not sure what F- feeder is)

                            Comment


                            • #15
                              If it receives data it needs, And processes it. It will bundle and send to server, state will change to Online.

                              F- are supplied boxes from FR24, not software based like you are working on. They are live and able to report connection data
                              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                              Comment

                              Working...
                              X