Announcement

Collapse
No announcement yet.

0 Aircraft tracked - Not sure what settings to use

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

  • 0 Aircraft tracked - Not sure what settings to use

    I just setup Raspian and installed PiAware and it works great, I then setup the ADSBExchange script and that worked too

    I went through the config for FlightRadar but zero airfract tracked, and I got the following in the log

    HTML Code:
    2019-02-12 21:00:18 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2019-02-12 21:00:18 | [reader][e]Could not connect to tcp://localhost:30005
    2019-02-12 21:00:23 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2019-02-12 21:00:23 | [reader][e]Could not connect to tcp://localhost:30005
    2019-02-12 21:00:28 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2019-02-12 21:00:28 | [reader][e]Could not connect to tcp://localhost:30005
    2019-02-12 21:00:33 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2019-02-12 21:00:33 | [reader][e]Could not connect to tcp://localhost:30005
    2019-02-12 21:00:38 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2019-02-12 21:00:38 | [reader][e]Could not connect to tcp://localhost:30005
    2019-02-12 21:00:43 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2019-02-12 21:00:43 | [reader][e]Could not connect to tcp://localhost:30005
    2019-02-12 21:00:47 | [feed][n]ping 9
    2019-02-12 21:00:48 | [feed][n]syncing stream result: 1
    2019-02-12 21:00:48 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2019-02-12 21:00:48 | [reader][e]Could not connect to tcp://localhost:30005
    2019-02-12 21:00:53 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2019-02-12 21:00:54 | [reader][e]Could not connect to tcp://localhost:30005
    2019-02-12 21:00:59 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2019-02-12 21:00:59 | [reader][e]Could not connect to tcp://localhost:30005
    I played around with some settings and ended up with it set on beast-tcp looking at port 30002.

    Now I have this

    HTML Code:
    2019-02-12 21:05:53 | [feed][n]KAAP22@185.218.24.22:8099/UDP
    2019-02-12 21:05:53 | [feed][n]connecting
    2019-02-12 21:05:53 | info | Stopping ReceiverACSender threads for feed
    2019-02-12 21:05:53 | info | Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.24:8099, feed: KAAP22, send_interval: 5s, max age: 15s, send metadata: true, mode: 1, filtering: true
    2019-02-12 21:05:53 | info | Network thread connecting to 185.218.24.22:8099 for feed KAAP22
    2019-02-12 21:05:53 | [feed][n]connected via UDP (fd 32)
    2019-02-12 21:05:53 | [feed][i]Feed connected
    2019-02-12 21:05:53 | [feed][n]working
    2019-02-12 21:06:23 | [feed][n]ping 1
    2019-02-12 21:06:24 | [feed][n]syncing stream result: 1
    2019-02-12 21:06:53 | [feed][n]ping 2
    2019-02-12 21:06:54 | [feed][n]syncing stream result: 1
    2019-02-12 21:07:23 | [feed][n]ping 3
    2019-02-12 21:07:24 | [feed][n]syncing stream result: 1
    2019-02-12 21:07:53 | [feed][n]ping 4
    2019-02-12 21:07:54 | [feed][n]syncing stream result: 1
    2019-02-12 21:08:23 | [feed][n]ping 5
    2019-02-12 21:08:24 | [feed][n]syncing stream result: 1
    2019-02-12 21:08:53 | [feed][n]ping 6
    2019-02-12 21:08:54 | [feed][n]syncing stream result: 1
    2019-02-12 21:09:23 | [feed][n]ping 7
    2019-02-12 21:09:24 | [feed][n]syncing stream result: 1
    2019-02-12 21:09:53 | [feed][n]ping 8
    2019-02-12 21:09:54 | [feed][n]syncing stream result: 1
    But still zero planes tracked...

    Can someone point me in the direction of what the correct settings should be for a bone stock Raspian install with PiAware installed on-top?

  • #2
    replace 'localhost' with 127.0.0.1 (odd self lookup bug) and 30005

    It's either that, or 30005 hasn't been opened by Piaware. But I would expect it to be.
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

    Comment


    • #3
      your fr24feed.ini should have these values for receiver and host:
      Code:
      receiver="beast-tcp"
      host="127.0.0.1:30005"

      Comment


      • #4
        Thanks for the help guys, I made sure it was on beast-tcp and moved it to port 30005, and now all is working!

        Comment

        Working...
        X