1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Problem with custom feed

Discussion in 'Feeding' started by MakersOfM, Jan 11, 2019 at 10:00 AM.

Tags:
  1. MakersOfM

    MakersOfM New Member

    I am trying to feed adsbexchange from a linux PC (plain debian ).

    I am using dump1090 (tested both original mutability and dump1090-fa from adsbexchange github).

    But I can not see myself in the customglobal site inside my receiver.

    As far as I understand, it's as easy as connecting the local ports 30005 and the remote feed port (after choosing a free one) using socat.

    I have a dump1090 working, if i do telnet to the local port 30003 I see the correct decoding of flights in csv format, and in port 30005 I see binary format.

    Then I execute socat to send from localhost 30005 to remote feed on 51088 (just changed port on adsbexchange-netcat_maint.sh )

    However, if I connect to customglobal and choose receiver zCons-51088 I do not see any flight (selected my map zone & show all flights).

    Trying to solve this myself try other ports zCons-xxxx, customglobal4, even send from another linux machine running dump1090 (with different public internet IP) and nothing works.

    What I can be doing wrong?
     
    Last edited: Jan 11, 2019 at 11:24 AM
  2. MDA

    MDA Administrator Staff Member

    What do you see in netstat? Is connection to remote port established?
    To test your data you can modify script to temporary send data to: 80.82.23.66 port 40004
    BTW did you activate rc.local service? ADSBx mlat-client scripts will not start without rc.local.
    You will find description howto activate on this forum.
     
    Last edited: Jan 11, 2019 at 4:39 PM
  3. James

    James Administrator Staff Member

    Custom feeds are beast only - they will only accept dump1090 port 30005.
     
  4. MDA

    MDA Administrator Staff Member

    Probably missing rc.local
     
  5. James

    James Administrator Staff Member

    try running socat manually in a terminal ...

    socat -u TCP:localhost:30005 TCP:feed.adsbexchange.com:51088


    There is supposed to be someone on zCons-51088 ..... nothing coming through tho ...

    2/17/2018 19:04:30 51088 JBBHackney London, hackney

    Screenshot_2019-01-11_10-15-18.png
     
  6. MDA

    MDA Administrator Staff Member

    There is something wrong with 51088.
    Trying to push my data to 51081, connected but nothing on map.
    upload_2019-1-11_18-34-21.png
     
  7. James

    James Administrator Staff Member

    Let me force it to reboot ... grr .. VRS
     
  8. MDA

    MDA Administrator Staff Member

    Now OK, I'll try 51088 again
    upload_2019-1-11_18-40-0.png
     
  9. MDA

    MDA Administrator Staff Member

    He's connected :).
    upload_2019-1-11_18-42-10.png
    51081 is free again.
     
  10. James

    James Administrator Staff Member

    OK working for me now ...

    Screenshot_2019-01-11_10-44-10.png
     
  11. James

    James Administrator Staff Member

    Also looks like I have to get on the roof and stand the antenna up again .... I just put it on tripod but didn't anchor it ...
     
    MDA likes this.
  12. MDA

    MDA Administrator Staff Member

    Reboot every 24h, 0:00 UTC
     
  13. MakersOfM

    MakersOfM New Member

    My custom feed is working! :)

    completed the form to request the name for my receiver. Thank you!

    BTW , i have mlat_maint.sh also running (with my lat,lon,alt and username MoM), but i dont see my station at MLAT Syncronization Matrix ( sync-3 ) Is this normal?
     
    Last edited: Jan 11, 2019 at 7:03 PM
  14. MDA

    MDA Administrator Staff Member

    Reboot your machine and check if it's still working.
     
  15. MakersOfM

    MakersOfM New Member

    Done, custom feed working!
     
  16. MDA

    MDA Administrator Staff Member

    Thanks for feeding :).
     
  17. MakersOfM

    MakersOfM New Member

    If i launch mlat-client manually get this... is this ok?

    /usr/local/bin/mlat-client --input-type dump1090 --input-connect 127.0.0.1:30005 --lat XX.XX33499 --lon -XX.XX39156 --alt 115 --user MoM --server feed.adsbexchange.com:31090 --no-udp --results beast,connect,127.0.0.1:30104

    Fri Jan 11 20:22:03 2019 mlat-client 0.2.10 starting up
    Fri Jan 11 20:22:03 2019 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking
    Fri Jan 11 20:22:04 2019 Beast-format results connection with 127.0.0.1:30104: connection established
    Fri Jan 11 20:23:03 2019 Disconnecting from feed.adsbexchange.com:31090: No data (not even keepalives) received for 60 seconds
    Fri Jan 11 20:23:04 2019 Connected to multilateration server at feed.adsbexchange.com:31090, handshaking
    .....

    http://www.adsbexchange.com/coverage-3/ dont show any station in my country (spain) , does that mean that there is no enough stations for mlat?
     
    Last edited: Jan 11, 2019 at 7:32 PM
  18. MDA

    MDA Administrator Staff Member

    Be patient, mlat client sometimes need lot of time to connect. Your station is located in busy region and your station performance is relatively low.
     
  19. MakersOfM

    MakersOfM New Member

    Thanks for your support. I just want to know if everything is correctly setup as it is an unattended linux computer remotely managed.
     
  20. MDA

    MDA Administrator Staff Member

    Install Zerotier, in case you need remote support just join my or James network. More detailed info by PM only.