updated config for Radarcape feeder?

Discussion in 'Feeding' started by Larry Sampas, Jun 26, 2020.

  1. Larry Sampas

    Larry Sampas New Member

    I was wondering if there is a documented config for adsbexchange for Radarcape version 181213.1005.02. I've tried data from ports 10003 and 10006, and I get green smileys on the status page, but then no data on the feeder UUID page. I don't want to leave it running in case I'm sending data in the wrong format. I've checked the one radarcape thread from 2019 on this forum with no joy.

    Thanks.
     
  2. wiedehopf

    wiedehopf Administrator Staff Member

    It depends on the settings i believe.

    The format needs to be set to binary for those output ports.

    For mlat you need to change the INPUT_FORMAT to radarcape_gps
    Otherwise it will not sync.
     
  3. Larry Sampas

    Larry Sampas New Member

    Of the output options, I have it set to port 10003. I seem to also be having issues with results:
    Beast-format results connection with x.x.x.x:30104: [Errno 111] Connection refused. Same result with localhost:30104 for results.
    Default port settings for my radarcape:
    10003:
    Binary formatted raw data with all Mode-S and Mode-A/C data formats (CRC pre-checked)
    10004:
    Binary formatted raw data with DF-11, DF-17 and DF-18 only
    10005:
    Binary formatted raw data of aircrafts without position
    10006:
    Binary formatted raw data with all Mode-S data formats (CRC pre-checked, no Mode-A/C)
    30003:
    Pre decoded aircraft data in CSV style

    Feed looks empty, status page green.
     
  4. wiedehopf

    wiedehopf Administrator Staff Member

    10006 should be the correct thing.

    I'm not quite clear what device you are running this stuff on?
    On the radarcape?

    When did you install the feed scripts?

    MLAT results can't be passed to the Radarcape as i don't even know what local interface they are running and if you can even add adsbexchange mlat results to that.
    That is only for your display though, doesn't affect adsbexchange calculating MLAT and getting results on the global radar.
     
  5. Larry Sampas

    Larry Sampas New Member

    It's running on the radarcape. ssh in, git clone, etc. I ran flightaware that way before they released a version that supported it natively. It's debian 8.

    Jun 26 02:26:23 radarcape adsbexchange-mlat[538]: The multilateration server source code is available under
    .....
    The following error occurred:


    Your content can not be submitted. This is likely because your content is spam-like or contains inappropriate elements. Please change your content or try again later. If you still have problems, please contact an administrator.

    Jun 26 02:26:49 radarcape adsbexchange-mlat[538]: Fri Jun 26 02:26:49 2020 Beast-format results connection with x.x.x.x:30104: [Errno 111] Connection refused
     
  6. wiedehopf

    wiedehopf Administrator Staff Member

    If this command shows aircraft, you are feeding:

    cat /run/adsbexchange-feed/aircraft.json

    You should also check your MLAT sync: https://adsbx.org/sync

    Have you used the configuration file to change the INPUT_PORT and INPUT_TYPE?
    /etc/default/adsbexchange

    These are the two settings you should need:
    INPUT="127.0.0.1:10003"
    INPUT_TYPE="radarcape_gps"


    If you have issues, can you please try reinstalling the feed script with this command:
    Code:
    sudo bash -c "$(wget -nv -O - https://raw.githubusercontent.com/adsbxchange/adsb-exchange/master/install.sh)"
    
    That will make it easier to fix any issues as i know you're on the most recent version.
     
  7. Larry Sampas

    Larry Sampas New Member

    cat /run/adsbexchange-feed/aircraft.json reveals 64 entries.
    input is set to port 10003:
    INPUT="x.x.x.x:10003" where x is my private IP rather than localhost/127.0.0.1
    INPUT_TYPE="radarcape_gps"
    I grabbed the source yesterday, so it should be fresh. I'm going to leave it running a while and see if I show up on the map.

    Logs:

    Jun 26 12:10:31 radarcape adsbexchange-mlat[13759]: location: https://github.com/adsbexchange/mlat-server
    Jun 26 12:10:31 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:10:31 2020 Handshake complete.
    Jun 26 12:10:31 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:10:31 2020 Compression: zlib2
    Jun 26 12:10:31 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:10:31 2020 UDP transport: disabled
    Jun 26 12:10:31 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:10:31 2020 Split sync: disabled
    Jun 26 12:10:31 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:10:31 2020 Input connected to x.x.x.x:10003
    Jun 26 12:10:31 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:10:31 2020 Input format changed to RADARCAPE, 1000MHz clock
    Jun 26 12:10:47 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:10:47 2020 Accepted Beast-format results connection from ::1:47531
    Jun 26 12:10:47 radarcape adsbexchange-feed[13742]: Beast TCP input: Attempting connection to localhost port 30157 ...
    Jun 26 12:10:47 radarcape adsbexchange-feed[13742]: Beast TCP input: Connection established: localhost :):1) port 30157
     
  8. Larry Sampas

    Larry Sampas New Member

    I'm showing up on the map now. Thanks for the help.

    Jun 26 12:25:26 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:25:26 2020 Receiver status: connected
    Jun 26 12:25:26 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:25:26 2020 Server status: ready
    Jun 26 12:25:26 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:25:26 2020 Receiver: 229.4 msg/s received 94.0 msg/s processed (41%)
    Jun 26 12:25:26 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:25:26 2020 Server: 0.0 kB/s from server 1.0kB/s TCP to server 0.0kB/s UDP to server
    Jun 26 12:25:26 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:25:26 2020 Results: 5.8 positions/minute
    Jun 26 12:25:26 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:25:26 2020 Aircraft: 7 of 10 Mode S, 35 of 38 ADS-B used
    Jun 26 12:40:26 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:40:26 2020 Receiver status: connected
    Jun 26 12:40:26 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:40:26 2020 Server status: ready
    Jun 26 12:40:26 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:40:26 2020 Receiver: 300.0 msg/s received 116.7 msg/s processed (39%)
    Jun 26 12:40:26 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:40:26 2020 Server: 0.0 kB/s from server 1.2kB/s TCP to server 0.0kB/s UDP to server
    Jun 26 12:40:26 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:40:26 2020 Results: 7.6 positions/minute
    Jun 26 12:40:26 radarcape adsbexchange-mlat[13759]: Fri Jun 26 12:40:26 2020 Aircraft: 10 of 13 Mode S, 48 of 52 ADS-B used