Feeder position on map not shown

Discussion in 'Feeding' started by Toiosoiovoio, Dec 4, 2020.

  1. Toiosoiovoio

    Toiosoiovoio New Member

    Hi all,

    I have one, I hop simple, question. My feeder position is no showing on the mlat map. Why?

    Can anyone help me sort this out?

    Feeder name is "ToisoiovoioV2"
     
  2. steve gee

    steve gee Member

  3. Toiosoiovoio

    Toiosoiovoio New Member

    Hi Steve, right on target. That solved my problem. Thank you.
     
  4. John Young

    John Young New Member

    I have a similar question. My feeder location does not show on the 978 map? It does show on the 1090 map and the mlat map. Any ideas to get it to show on the 978 map?
     
  5. wiedehopf

    wiedehopf Administrator Staff Member

    What install are you using?

    If you're an older version of the image, just consider flashing the new image.
     
  6. John Young

    John Young New Member

    I downloaded all the software just the other day. How would I know the version of the image?

    Thanks.
     
  7. wiedehopf

    wiedehopf Administrator Staff Member

    So you could either say you downloaded the custom image ....
    Or you coud say you have used the install scripts and that stuff?

    If you don't know, i can't help you.
     
  8. John Young

    John Young New Member

     
  9. wiedehopf

    wiedehopf Administrator Staff Member

  10. John Young

    John Young New Member

  11. John Young

    John Young New Member

  12. wiedehopf

    wiedehopf Administrator Staff Member

    Could you please rerun the 978 install, that should fix it.

    Thanks for feeding!
     
  13. John Young

    John Young New Member

    I used the install scripts.
     
  14. wiedehopf

    wiedehopf Administrator Staff Member

    Yes please download the 978 script again and run it again.
    It will fix it. (i changed something)
     
    Last edited: Feb 21, 2022
  15. John Young

    John Young New Member

    From the git hub site of from the adsbexchange site?
     
  16. John Young

    John Young New Member

    I reinstalled the 978 scripts as you suggested. It is still not feeding the adsbexchange.

    No beast data detected from 154.6.24.73.
    No MLAT data detected from 154.6.24.73.

    Those are the messages I get.
     
  17. wiedehopf

    wiedehopf Administrator Staff Member

    You were asking about location on the 978 map before.

    myip being wrong could happen if the pi is on another network or your internet uses CGNAT (common for wireless internet).

    What decoders are you running?
    I'd really recommend just using the adsbexchange image, it's very easy: https://www.adsbexchange.com/how-to-feed/adsbx-custom-pi-image/
     
  18. John Young

    John Young New Member

    The pi is on the same network as my laptop. I don't know about CGNAT but I have spectrum internet.

    [email protected]:~ $ sudo piaware-status
    PiAware master process (piaware) is running with pid 1110.
    PiAware ADS-B client (faup1090) is running with pid 1226.
    PiAware ADS-B UAT client (faup978) is running with pid 24895.
    PiAware mlat client (fa-mlat-client) is running with pid 2788.
    Local ADS-B receiver (dump1090-fa) is running with pid 547.
    Local ADS-B UAT receiver (dump978-fa) is running with pid 24857.

    dump1090-fa (pid 547) is listening for ES connections on port 30005.
    dump978-fa (pid 24857) is listening for UAT connections on port 30978.
    faup1090 is connected to the ADS-B receiver.
    faup978 is connected to the ADS-B UAT receiver.
    piaware is connected to FlightAware.

    dump978 is producing data on localhost:30978.
    dump1090 is producing data on localhost:30005.

    Your feeder ID is 266afada-84ee-457f-90eb-e8267d9b1a63 (configured at /etc/piaware.conf:7)

    I think that should show you the decoders. Plus after I had piaware working, I adsbexchange on 1090 and 978. I don't want to run the adsb image. I just want to get adsb exchange getting my data.

    Thanks.
     
  19. wiedehopf

    wiedehopf Administrator Staff Member

    The same thing for 978 you already ran ... download / run it again.
    It will fix the location issue..

    You're likely already feeding.
    Could also be that you use VPN?

    https://map.adsbexchange.com/mlat-map/

    Check here if you're on there under the name you put as receiver name.

    sudo journalctl -eu adsbexchange-978 | tail -n30
    sudo journalctl -eu adsbexchange-feed | tail -n30

    Those logs will show if you're feeding.
     
  20. John Young

    John Young New Member

    [email protected]:~ $ sudo journalctl -eu adsbexchange-978 | tail -n30
    Feb 20 18:58:43 raspberrypi adsbexchange-978[567]: BeastReduce TCP output: Connection established: feed.adsbexchange.com (216.48.109.64) port 30004 (sending UUID: 7edcc8f6-72c3-4efa-9c48-4abf46c5b5ac)
    Feb 21 04:17:40 raspberrypi adsbexchange-978[567]: BeastReduce TCP output: Connection established: feed.adsbexchange.com (216.48.109.64) port 64004 (sending UUID: 7edcc8f6-72c3-4efa-9c48-4abf46c5b5ac)
    Feb 21 14:49:25 raspberrypi systemd[1]: adsbexchange-978.service: Current command vanished from the unit file, execution of the command list won't be resumed.
    Feb 21 14:49:26 raspberrypi adsbexchange-978[567]: Mon Feb 21 14:49:26 2022 CST Caught SIGTERM, shutting down...
    Feb 21 14:49:26 raspberrypi systemd[1]: Stopping adsbexchange-978.service...
    Feb 21 14:49:26 raspberrypi adsbexchange-978[567]: Mon Feb 21 14:49:26 2022 CST Normal exit.
    Feb 21 14:49:26 raspberrypi systemd[1]: adsbexchange-978.service: Succeeded.
    Feb 21 14:49:26 raspberrypi systemd[1]: Stopped adsbexchange-978.service.
    Feb 21 14:49:26 raspberrypi systemd[1]: adsbexchange-978.service: Consumed 1min 34.788s CPU time.
    Feb 21 14:49:26 raspberrypi systemd[1]: Started adsbexchange-978.service.
    Feb 21 14:49:26 raspberrypi adsbexchange-978[441499]: readsb version: wiedehopf git: 699af6b (commited: Wed Feb 16 20:53:52 2022 0100)
    Feb 21 14:49:26 raspberrypi adsbexchange-978[441499]: Using lat: 33.3826, lon: -86.7141
    Feb 21 14:49:26 raspberrypi adsbexchange-978[441499]: 37985: Beast TCP output port 37981: Raw TCP input port
    Feb 21 14:49:36 raspberrypi adsbexchange-978[441499]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 14:49:37 raspberrypi adsbexchange-978[441499]: BeastReduce TCP output: Connection established: feed.adsbexchange.com (216.48.109.64) port 64004 (sending UUID: 7edcc8f6-72c3-4efa-9c48-4abf46c5b5ac)
    Feb 21 14:49:43 raspberrypi adsbexchange-978[441499]: Mon Feb 21 14:49:43 2022 CST Caught SIGTERM, shutting down...
    Feb 21 14:49:43 raspberrypi systemd[1]: Stopping adsbexchange-978.service...
    Feb 21 14:49:43 raspberrypi adsbexchange-978[441499]: Mon Feb 21 14:49:43 2022 CST Normal exit.
    Feb 21 14:49:43 raspberrypi systemd[1]: adsbexchange-978.service: Succeeded.
    Feb 21 14:49:43 raspberrypi systemd[1]: Stopped adsbexchange-978.service.
    -- Boot 1a474c560643400286e7d25972f0e688 --
    Feb 21 14:49:51 raspberrypi systemd[1]: Started adsbexchange-978.service.
    Feb 21 14:49:52 raspberrypi adsbexchange-978[578]: readsb version: wiedehopf git: 699af6b (commited: Wed Feb 16 20:53:52 2022 0100)
    Feb 21 14:49:52 raspberrypi adsbexchange-978[578]: Using lat: 33.3826, lon: -86.7141
    Feb 21 14:49:52 raspberrypi adsbexchange-978[578]: 37985: Beast TCP output port 37981: Raw TCP input port
    Feb 21 14:49:52 raspberrypi adsbexchange-978[578]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 14:49:53 raspberrypi adsbexchange-978[578]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 14:49:55 raspberrypi adsbexchange-978[578]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 14:49:59 raspberrypi adsbexchange-978[578]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 14:50:07 raspberrypi adsbexchange-978[578]: BeastReduce TCP output: Connection established: feed.adsbexchange.com (216.48.109.64) port 30004 (sending UUID: 7edcc8f6-72c3-4efa-9c48-4abf46c5b5ac)
    [email protected]:~ $ sudo journalctl -eu adsbexchange-feed | tail -n30
    Feb 21 04:00:56 raspberrypi adsbexchange-feed[778]: BeastReduce TCP output: Socket Error: Connection timed out: feed.adsbexchange.com port 64004 (fd 9, SendQ 0, RecvQ 0)
    Feb 21 04:01:01 raspberrypi adsbexchange-feed[778]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 04:01:02 raspberrypi adsbexchange-feed[778]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 04:01:14 raspberrypi adsbexchange-feed[778]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 04:01:19 raspberrypi adsbexchange-feed[778]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 04:01:26 raspberrypi adsbexchange-feed[778]: BeastReduce TCP output: Attempting connection to feed.adsbexchange.com port 30004 ...
    Feb 21 04:01:31 raspberrypi adsbexchange-feed[778]: BeastReduce TCP output: Connection timed out: feed.adsbexchange.com:30004 port (216.48.109.64)
    Feb 21 04:01:42 raspberrypi adsbexchange-feed[778]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 04:02:12 raspberrypi adsbexchange-feed[778]: BeastReduce TCP output: Attempting connection to feed.adsbexchange.com port 30004 ...
    Feb 21 04:02:12 raspberrypi adsbexchange-feed[778]: BeastReduce TCP output: Connection established: feed.adsbexchange.com (216.48.109.64) port 30004 (sending UUID: 7edcc8f6-72c3-4efa-9c48-4abf46c5b5ac)
    Feb 21 14:49:43 raspberrypi adsbexchange-feed[778]: Mon Feb 21 14:49:43 2022 CST Caught SIGTERM, shutting down...
    Feb 21 14:49:43 raspberrypi adsbexchange-feed[778]: Mon Feb 21 14:49:43 2022 CST Normal exit.
    Feb 21 14:49:43 raspberrypi systemd[1]: Stopping adsbexchange-feed...
    Feb 21 14:49:43 raspberrypi systemd[1]: adsbexchange-feed.service: Succeeded.
    Feb 21 14:49:43 raspberrypi systemd[1]: Stopped adsbexchange-feed.
    Feb 21 14:49:43 raspberrypi systemd[1]: adsbexchange-feed.service: Consumed 2min 20.702s CPU time.
    -- Boot 1a474c560643400286e7d25972f0e688 --
    Feb 21 14:49:51 raspberrypi systemd[1]: Started adsbexchange-feed.
    Feb 21 14:49:53 raspberrypi adsbexchange-feed[787]: readsb version: wiedehopf git: 699af6b (commited: Wed Feb 16 20:53:52 2022 0100)
    Feb 21 14:49:53 raspberrypi adsbexchange-feed[787]: Using lat: 33.3826, lon: -86.7141
    Feb 21 14:49:53 raspberrypi adsbexchange-feed[787]: 30154: Beast TCP input port
    Feb 21 14:49:54 raspberrypi adsbexchange-feed[787]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 14:49:54 raspberrypi adsbexchange-feed[787]: Beast TCP input: Attempting connection to 127.0.0.1 port 30005 ...
    Feb 21 14:49:54 raspberrypi adsbexchange-feed[787]: Beast TCP input: Connection established: 127.0.0.1 port 30005
    Feb 21 14:49:55 raspberrypi adsbexchange-feed[787]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 14:49:57 raspberrypi adsbexchange-feed[787]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 14:50:01 raspberrypi adsbexchange-feed[787]: BeastReduce TCP output: Name resolution for feed.adsbexchange.com failed: Temporary failure in name resolution
    Feb 21 14:50:28 raspberrypi adsbexchange-feed[787]: BeastReduce TCP output: Attempting connection to feed.adsbexchange.com port 30004 ...
    Feb 21 14:50:28 raspberrypi adsbexchange-feed[787]: BeastReduce TCP output: Connection established: feed.adsbexchange.com (216.48.109.64) port 30004 (sending UUID: 7edcc8f6-72c3-4efa-9c48-4abf46c5b5ac)
    Feb 21 14:50:42 raspberrypi adsbexchange-feed[787]: Beast TCP input: new c from ::1 port 54018 (fd 10)
    [email protected]:~ $