Recieve MLAT data within VRS

Discussion in 'Other technical not related to ADSBx Feeding' started by RobKo, Nov 10, 2019.

  1. RobKo

    RobKo New Member

    Hi,
    I'd live a couple of miles away from a militairy airbase and from a small local private airstrip and like to follow the (military) aircraft around my home.

    Because i'd like to hobby with computers, it was a nicely project setting up my own reciever using a Rpi, FlightAware stick PRO and a small Antenna from China. As base for the software i use the ADSB-X image.
    That works great, good feeder statistics and also recieve MLAT data so i can follow the local F16's and the small private planes on my local dump1090/gmap.html.

    Because of the better UI and detailled aircraft information, next step was to set up a local VRS.
    I found a tut wich helps me step by step setting up VRS. This also works great, but there is one thing i can't get wordking into VRS.. Showing up MLAT aircraft.

    I put an reveiver in VRS for MLAT with 127.0.0.1:30104 but no messages are achieved. The reciever has state "connected".
    Part of the connection log into VRS:

    0-Nov-2019 11:32:02
    ADSB MLAT
    Miscellaneous
    Establishing connections on background thread
    10-Nov-2019 11:32:02
    ADSB MLAT
    Connected
    SOCKET (local=127.0.0.1:41316, remote=127.0.0.1:30104) connected
    10-Nov-2019 11:33:03
    ADSB MLAT
    Miscellaneous
    Background thread check has determined that connection SOCKET (local=127.0.0.1:41316, remote=127.0.0.1:30104) is idle - abandoning it
    10-Nov-2019 11:33:03
    ADSB MLAT
    Exception
    Exception caught by connection SOCKET (local=127.0.0.1:41316, remote=127.0.0.1:30104): interrupted
    10-Nov-2019 11:33:03
    ADSB MLAT
    Disconnected
    SOCKET (local=127.0.0.1:41316, remote=127.0.0.1:30104) disconnected
    10-Nov-2019 11:33:08
    ADSB MLAT
    Connected
    SOCKET (local=127.0.0.1:41418, remote=127.0.0.1:30104) connected
    10-Nov-2019 11:35:03
    ADSB MLAT
    Miscellaneous
    Background thread check has determined that connection SOCKET (local=127.0.0.1:41418, remote=127.0.0.1:30104) is idle - abandoning it
    10-Nov-2019 11:35:03
    ADSB MLAT
    Exception
    Exception caught by connection SOCKET (local=127.0.0.1:41418, remote=127.0.0.1:30104): interrupted
    When i look into Grafana i see MLAT aircraft count and those are showing up on the dump1090/gmap.html map.

    I read a lot of information, and tried some things, but notting helped.

    Please can some help me complete this last step setting up my reciever?

    Thanks a lot.
     
  2. wiedehopf

    wiedehopf Administrator Staff Member

    Try basestation protocol on 31003.

    Otherwise you'll have to modify the mlat-client command line to open a beast listen port for the mlat results, adding this:
    --results beast,listen,31005

    Then connect to that port.
    Port 30104 is not for data output, only for input. The mlat-client connects to that port to push the data to dump1090.
    As described above, you need a listen, not a connect port in mlat-client.

    To check the current command-line:
    pgrep -a mlat-client
     
  3. MDA

    MDA Administrator Staff Member

    Add
    Code:
    --results basestation,connect,<IP of VRS>:31003
    and create receiver in VRS.
     
  4. RobKo

    RobKo New Member

    Thanks Guys! I modify adsbexchange-mlat_maint.sh with the additional ports and that's fixes it! :)
     
    James likes this.