Announcement

Collapse
No announcement yet.

Setting up

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

  • Setting up

    Hi

    Just received my ADS-B antenna USB from Noobs something. I have the driver's installed and it's listed in device manager. I've run the software to setup feeding but stuck on the black screen asking what the com port / device address is?


    I've tried looking in device manager, but doesn't say what com port it's on.. any help?

  • #2
    I got it working ish.. In the fr24feed page, I'm showing as connected.....

    Windows/generic/i386/1.0.19-15
    Updated: 18:20:52 GMT+0000 (GMT Standard Time)
    FR24 Link: Connected via UDP
    FR24 Radar Code: hidden
    Local IP(s):

    Aircraft Tracked: 0
    (ModeS & ADS-B)
    Aircraft Uploaded: N/A
    Receiver: dvbt, Connected
    MLAT running: N/A

    In the feeder terminal, it says connected, processing images, terminated constantly.. Is this normal?


    Not so sure as to why its not seeing anything tho, Antenna to small, to low?

    Comment


    • #3
      No, terminating and no reception is a stick/config issue.

      https://forum.flightradar24.com/thre...4834#post74834

      Code:

      2016-01-26 22:20:05 | [reader][i]Connecting to Generic receiver via (exe://*dump1090* --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://*dump1090* --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

      Incorrect configuration set - Hardware not starting. Check for:
      - USB stick does NOT have the required Realtek RTL28xx chipset or Rafael Tuner
      - Conflicting software locking USB device to 'in-use'
      - Missing zadig driver installation step for windows (cannot read USB devices)
      - Error with additional commands causing Dump1090 to terminate
      - Dump1090 (or similar) already currently running
      - Windows detected and using wrong USB. Add: --device-index x
      Need to perform the visual checks there and look at the starting window as it is launched for indications of what is failing.

      Probably stick type, or driver

      It shouldn't ask for a com port for a dvbt stick unless the wrong device was selected

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

      Comment


      • #4
        Thanks, I didn't know about the uncheck Hub setting on the driver install. Installed that and it seemed to worked, detected 2 aircraft, not saying terminated any more, but, now I'm showing as Online - No Data

        Heres what feeder says

        [main][i]Feed Network client started
        [main][i]RAW data server started
        [feed][i]Downloading configuration
        [raw][i]Initializing server
        [raw][i]Starting server on 0.0.0.0:30002
        [feed][c]Interval: 5s
        [feed][c]Latitude: 55.9500
        [feed][c]Longitude: -3.3725
        [feed][c]GND: YES
        [feed][c]NonADSB: YES
        [feed][c]Timestamps: optional
        [feed][c]Max range AIR: 350.0nm
        [feed][c]Max range GND: 100.0nm
        [feed][i]defined 4 servers
        [stats][i]Stats thread started
        [feed][n]EGPH177@185.218.24.22:8099/UDP
        [feed][n]connecting
        [feed][n]connected via UDP (fd 1064)
        [feed][n]working
        [feed][n]ping 1
        [feed][n]syncing stream result: 1

        just always pinging?

        I've not put the antenna outside yet, so maybe could be that

        Comment


        • #5
          Did you manage to get any further, I have installed an antenna, it appears to he syncing with FlightRadar24 but I'm not detecting any aircraft. There are generally a lot of aircraft going overhead, but usually at their cruise altitudes where I live, I thought the indoor antenna would be able to detect those with a clear line of sight.

          2019-03-13 01:54:23 | [feed][n]ping 6901
          2019-03-13 01:54:24 | [feed][n]syncing stream result: 1
          2019-03-13 01:54:53 | [feed][n]ping 6902
          2019-03-13 01:54:54 | [feed][n]syncing stream result: 1
          2019-03-13 01:55:23 | [feed][n]ping 6903
          2019-03-13 01:55:24 | [feed][n]syncing stream result: 1
          2019-03-13 01:55:53 | [feed][n]ping 6904
          2019-03-13 01:55:54 | [feed][n]syncing stream result: 1
          2019-03-13 01:56:23 | [feed][n]ping 6905
          2019-03-13 01:56:24 | [feed][n]syncing stream result: 1
          2019-03-13 01:56:53 | [feed][n]ping 6906
          2019-03-13 01:56:54 | [feed][n]syncing stream result: 1
          2019-03-13 01:57:23 | [feed][n]ping 6907
          2019-03-13 01:57:24 | [feed][n]syncing stream result: 1

          sudo fr24feed-status
          [ ok ] FR24 Feeder/Decoder Process: running.
          [ ok ] FR24 Stats Timestamp: 2019-03-13 02:01:55.
          [ ok ] FR24 Link: connected [TCP].
          [ ok ] FR24 Radar: T-EILT2.
          [ ok ] FR24 Tracked AC:.
          [ ok ] Receiver: connected (0 MSGS/0 SYNC).
          [FAIL] FR24 MLAT: not running ... failed!

          I don't have MLAT running, but that was a configuration I set. Normally when scripting a return code of 0 would indicate success. I'm not sure if 1 is failure or success in this case. I can't seem to find any documentation

          Comment


          • #6
            Originally posted by grantlittle View Post
            Did you manage to get any further, I have installed an antenna, it appears to he syncing with FlightRadar24 but I'm not detecting any aircraft. There are generally a lot of aircraft going overhead, but usually at their cruise altitudes where I live, I thought the indoor antenna would be able to detect those with a clear line of sight.

            2019-03-13 01:54:23 | [feed][n]ping 6901
            2019-03-13 01:54:24 | [feed][n]syncing stream result: 1
            2019-03-13 01:54:53 | [feed][n]ping 6902
            2019-03-13 01:54:54 | [feed][n]syncing stream result: 1
            2019-03-13 01:55:23 | [feed][n]ping 6903
            2019-03-13 01:55:24 | [feed][n]syncing stream result: 1
            2019-03-13 01:55:53 | [feed][n]ping 6904
            2019-03-13 01:55:54 | [feed][n]syncing stream result: 1
            2019-03-13 01:56:23 | [feed][n]ping 6905
            2019-03-13 01:56:24 | [feed][n]syncing stream result: 1
            2019-03-13 01:56:53 | [feed][n]ping 6906
            2019-03-13 01:56:54 | [feed][n]syncing stream result: 1
            2019-03-13 01:57:23 | [feed][n]ping 6907
            2019-03-13 01:57:24 | [feed][n]syncing stream result: 1

            sudo fr24feed-status
            [ ok ] FR24 Feeder/Decoder Process: running.
            [ ok ] FR24 Stats Timestamp: 2019-03-13 02:01:55.
            [ ok ] FR24 Link: connected [TCP].
            [ ok ] FR24 Radar: T-EILT2.
            [ ok ] FR24 Tracked AC:.
            [ ok ] Receiver: connected (0 MSGS/0 SYNC).
            [FAIL] FR24 MLAT: not running ... failed!

            I don't have MLAT running, but that was a configuration I set. Normally when scripting a return code of 0 would indicate success. I'm not sure if 1 is failure or success in this case. I can't seem to find any documentation
            That may be a sign for a stick with the wrong chipset.

            Stop fr24 and run rtl_test (or note the very first couple of lines when launching sudo fr24feed.. no 'service').

            If it reports a Fitpower, you won't be able to tune to adsb.

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

            Comment


            • #7
              After stopping fr24feed, and then running rtf_test I get the following output

              $ 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...

              If I then try and start fr24feed up again I get this output

              2019-03-13 11:32:47 | ______ _ _ _ _ _ _____ ___
              2019-03-13 11:32:47 | | ___|| |(_) | | | | | | / __ \ / |
              2019-03-13 11:32:47 | | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
              2019-03-13 11:32:47 | | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
              2019-03-13 11:32:47 | | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
              2019-03-13 11:32:47 | \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
              2019-03-13 11:32:47 | __/ |
              2019-03-13 11:32:47 | |___/
              2019-03-13 11:32:47 | [main][i]FR24 Feeder/Decoder
              2019-03-13 11:32:47 | [main][i]Version: 1.0.23-8/generic
              2019-03-13 11:32:47 | [main][i]Built on Oct 11 2018 18:27:28 (HEAD-3c696a7.git/Linux/static_armel)
              2019-03-13 11:32:47 | [main][i]Running on: raspbian9
              2019-03-13 11:32:47 | [main][i]Local IP(s): 172.16.0.4
              2019-03-13 11:32:47 | [main][i]Copyright 2012-2018 Flightradar24 AB
              2019-03-13 11:32:47 | [main][I] (link URL removed due to forum restrictions)
              2019-03-13 11:32:47 | [main][i]DNS mode: PING
              2019-03-13 11:32:47 | [main][i]Automatic updates are ENABLED
              2019-03-13 11:32:48 | ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded
              2019-03-13 11:32:48 | [httpd][i]Server started, listening on 0.0.0.0:8754
              2019-03-13 11:32:48 | [main][i]Reader thread started
              2019-03-13 11:32:48 | [master][i]Starting processing thread
              2019-03-13 11:32:48 | [main][i]MLAT data feed started
              2019-03-13 11:32:48 | [reader][i]Initializing reader
              2019-03-13 11:32:48 | [mlat][i]Waiting for MLAT configuration
              2019-03-13 11:32:48 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
              2019-03-13 11:32:48 | [reader][i]Connected to the receiver, configuring
              2019-03-13 11:32:48 | [reader][i]Configured, processing messages
              2019-03-13 11:32:49 | [time][i]Synchronizing time via NTP
              2019-03-13 11:33:35 | [time][i]Time synchronized correctly, offset +0.0000 seconds
              2019-03-13 11:33:35 | [feed][i]Downloading configuration
              2019-03-13 11:33:35 | [main][i]Feed Network client started
              2019-03-13 11:33:35 | [feed][d]fetching configuration
              2019-03-13 11:33:35 | [feed][i]configuring decoder
              2019-03-13 11:33:35 | [feed][c]Max range AIR: 350.0nm
              2019-03-13 11:33:35 | [feed][c]Max range GND: 100.0nm
              2019-03-13 11:33:35 | [feed][i]configuration changed
              2019-03-13 11:33:35 | [feed][i]defined 3 servers
              2019-03-13 11:33:35 | [feed][c]Timestamps: optional
              2019-03-13 11:33:35 | [stats][i]Stats thread started
              2019-03-13 11:33:35 | [feed][n]EILT2@185.218.24.22:8099/UDP
              2019-03-13 11:33:35 | [feed][n]connecting
              2019-03-13 11:33:35 | [feed][n]connected via UDP (fd 15)
              2019-03-13 11:33:35 | [feed][i]Feed connected
              2019-03-13 11:33:35 | [feed][n]working
              2019-03-13 11:33:35 | info | Stopping ReceiverACSender threads for feed
              2019-03-13 11:33:35 | info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.2 4:8099, feed: EILT2, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
              2019-03-13 11:33:35 | info | Network thread connecting to 185.218.24.22:8099 for feed EILT2
              2019-03-13 11:34:05 | [feed][n]ping 1
              2019-03-13 11:34:06 | [feed][n]syncing stream result: 1
              2019-03-13 11:34:35 | [feed][n]ping 2
              2019-03-13 11:34:36 | [feed][n]syncing stream result: 1
              2019-03-13 11:35:05 | [feed][n]ping 3
              2019-03-13 11:35:06 | [feed][n]syncing stream result: 1
              2019-03-13 11:35:35 | [feed][n]ping 4
              2019-03-13 11:35:36 | [feed][n]syncing stream result: 1
              2019-03-13 11:36:05 | [feed][n]ping 5
              2019-03-13 11:36:06 | [feed][n]syncing stream result: 1
              2019-03-13 11:36:35 | [feed][n]ping 6
              2019-03-13 11:36:36 | [feed][n]syncing stream result: 1

              The only thing I can see is the ERROR on an rmmod, but it's trying to remove a module that isn't loaded already, so is that an error really?

              Any other suggestions would be great, I'm really struggling to figure out what the issue is.

              Cheers in advance

              Comment

              Working...
              X