What did I do wrong? (custom feed)

Discussion in 'Feeding' started by alleyoopie, Mar 9, 2018.

Tags:
  1. alleyoopie

    alleyoopie New Member

    I picked one of the zCons in the list without visible traffic on the global map (I chose zCons-51255)
    I edited the netcat file and changed the port number from 30005 to 51255 followed by a sudo reboot.
    After a couple of hours I checked again and there's still no traffic for zCons-51255, something must have changed because the tag with my original feeder name (img-1.2-c7e602) has now dissapeared from the mlat-coverage map.
    How to proceed?
     
  2. MDA

    MDA Administrator Staff Member

    Did you use latest MLAT client from github (Joe Prochazka)?
     
  3. alleyoopie

    alleyoopie New Member

    Yup, the one described in the tutorial.
     
  4. MDA

    MDA Administrator Staff Member

  5. alleyoopie

    alleyoopie New Member

    Thank you MDA, problem solved, custom feed is active now.
    One remark about the form to customize the feed, it doesn't mention the type of notation for the coordinates, i.e. 51.98 degrees or 51.59 degrees (decimal or 60)
     
  6. James

    James Guest

    decimal degrees please
     
  7. alleyoopie

    alleyoopie New Member

    Well, my custom feed is okay (alleyoopie-51255) but I'm still waiting to see my nickname appear on the mlat sync matrix & mlat coverage graphs, maybe I need to wait some time?
     
  8. James

    James Guest

    How long have you been feeding the MLAT? I should connect very quickly or in a few hours at most.

    How SSH savy are you? Can you ssh into the pi and run htop?

    sudo install htop

    if you aren't using our image

    Hit f5 to tree process them

    look for mlat-client
     
  9. alleyoopie

    alleyoopie New Member

    I have teamviewer running on my Pi (pixel gui), I did a ps -ef in terminal mode and was unable to locate the mlat-client in the process list.
    My setup is Piaware 3.5.3, mlat was broken after having installed the prochazka script, I assumed it included the mlat-client but this doesn't seem the case?
     
  10. James

    James Guest

    It should have worked. All you feed is FA and ADSBx?

    I would just use Dan's Piaware Image that includes the scripts to feed us.

    You can always rerun the script. From the directory.

    sudo ./setup.sh

    scripts are in home/pi/adsb-exchange I think
     
  11. alleyoopie

    alleyoopie New Member

    Well I reran setup.sh but alas no avail, feeding is okay but still no mlat.
    The only reference to adsbexchange mlat I can find in the process tree is:
    /bin/sh /home/pi/adsb-exchange/adsbexchange-mlat_main.sh
    contents of this file is:

    while true
    do
    sleep 30
    /usr/bin/mlat-client
    --input-type dump1090
    --input-connect localhost:30005
    (+ usual lat, long, alt, nickname)
    --server feed.adsbexchange.com:31090
    --no-udp
    --results beast.connect.localhost:30104
    done
     
  12. James

    James Guest

    That's it.
     
  13. James

    James Guest

  14. alleyoopie

    alleyoopie New Member

    Just install htop and checked the mlat_main.sh thread
    First difference: this process is running in /root instead of /pi
    Second difference: only sleep30 seems to be running, nothing else!
    (tried to add screen dump but got "there was a problem uploading your file")
     
  15. James

    James Guest

    root is fine. That's how his script sets it up.

    sleep means it's not connected and sleeping for 30 secs before trying to connect again.
     
  16. alleyoopie

    alleyoopie New Member

    If it's sleeping continuously does this mean that /usr/bin/mlat-client cannot be executed?
     
  17. James

    James Guest

    well every 30 secs it will try to run the mlat-client statement in that file

    cd /home/pi/adsbexchange

    sudo ./adsbexchange-mlat_maint.sh

    see if any errors other than it can't handshake come up
     
  18. alleyoopie

    alleyoopie New Member

    Think we're finally there!
    mlat-client: error: the following arguments are required: --user
    Initially, I replaced 'user' by my nickname while the correct syntax should be --user nickname, stupid error that I overlooked!

    Thank you for the troubleshooting James
     
  19. James

    James Guest

    Excellent!
     
  20. MDA

    MDA Administrator Staff Member

    You're not a first one :D.
    BTW massive setup!