MLAT help

Discussion in 'Feeding' started by davlinds, Dec 27, 2019.

Tags:
  1. davlinds

    davlinds Member

    I would appreciate some suggestions, I have a working system feeding FA and ADSBEx but I want to use the MLAT feed primarily from ADSBEx (as its better!) but use the FA if I have a disconnect from ADSBEx. However this could lead to data duplication, I guess. Is there a solution to this problem? Already written software?
     
  2. wiedehopf

    wiedehopf Administrator Staff Member

    Just use the MLAT results from both, it produces somewhat jagged tracks sometimes as a downside.
    Otherwise decide which one you want, or display them in a separate webinterface.

    tar1090 does some rudimentary position filtering so it can help a bit with the jagged tracks when using multiple mlat sources: https://github.com/wiedehopf/tar1090#tar1090
     
  3. MDA

    MDA Administrator Staff Member

    Both mlat-clients are sending results to local dump1090
    Code:
    --results beast,connect,localhost:30104
    .
    Sometimes FA uses fake ICAO (displayed italic). That's not an issue, you don't need to change anything.
     
  4. davlinds

    davlinds Member

    Thanks do I just add
    basestation,listen,192.168.0.59:30107 so I can use the data in a heatmap program
     
  5. wiedehopf

    wiedehopf Administrator Staff Member

    Not quite, don't use the IP address with listen, only the port.

    Code:
     --results RESULTS     <protocol>,connect,host:port 
    or 
    <protocol>,listen,port
    Protocol may be 'basestation', 'ext_basestation', or 'beast'. Can be specified multiple times.
    
    (From the mlat-client help)