No Supported Devices Found

Discussion in 'Feeding' started by Racer X, Jul 9, 2022.

  1. Racer X

    Racer X New Member

    New install of adsbexchange image on Pi Zero W and Flighaware Flightstick SDR. Getting "problem fetching data from server error" and showing no feeder connection.

    Using sudo journalctl -u readsb | tail -n30 gives me the following and shows "no supported devices found". I changed out the SDR for another of the same and get the same response.

    [email protected]:~ $ sudo journalctl -u readsb | tail -n30

    Jul 09 21:45:29 adsbexchange readsb[1738]: Sat Jul 9 21:45:29 2022 UTC readsb starting up.

    Jul 09 21:45:29 adsbexchange readsb[1738]: readsb version: wiedehopf git: a12dec2 (committed: Mon Jun 6 21:53:41 2022 0200)

    Jul 09 21:45:29 adsbexchange readsb[1738]: WARNING: Reducing preamble threshold / decoding performance as this system has only 1 core (explicitely set --preamble-threshold to disable this behaviour)!

    Jul 09 21:45:29 adsbexchange readsb[1738]: Using lat: 23.7842, lon: 90.4151

    Jul 09 21:45:29 adsbexchange readsb[1738]: 30002: Raw TCP output port 30005: Beast TCP output port

    Jul 09 21:45:29 adsbexchange readsb[1738]: 30154: Position json output port 30003: SBS TCP output ALL port

    Jul 09 21:45:29 adsbexchange readsb[1738]: 30152: API output port

    Jul 09 21:45:29 adsbexchange readsb[1738]: 30001: Raw TCP input port

    Jul 09 21:45:29 adsbexchange readsb[1738]: 30004: Beast TCP input port 30104: Beast TCP input port

    Jul 09 21:45:29 adsbexchange readsb[1738]: rtlsdr: no supported devices found.

    Jul 09 21:45:29 adsbexchange readsb[1738]: Sat Jul 9 21:45:29 2022 UTC sdrOpen() failed, exiting!

    Jul 09 21:45:29 adsbexchange readsb[1738]: Sat Jul 9 21:45:29 2022 UTC Abnormal exit.

    Jul 09 21:45:29 adsbexchange systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE

    Jul 09 21:45:29 adsbexchange systemd[1]: readsb.service: Failed with result 'exit-code'.

    Jul 09 21:45:44 adsbexchange systemd[1]: readsb.service: Scheduled restart job, restart counter is at 8.

    Jul 09 21:45:44 adsbexchange systemd[1]: Stopped readsb ADS-B receiver.

    Jul 09 21:45:44 adsbexchange systemd[1]: Started readsb ADS-B receiver.

    Jul 09 21:45:45 adsbexchange readsb[1960]: Sat Jul 9 21:45:45 2022 UTC readsb starting up.

    Jul 09 21:45:45 adsbexchange readsb[1960]: readsb version: wiedehopf git: a12dec2 (committed: Mon Jun 6 21:53:41 2022 0200)

    Jul 09 21:45:45 adsbexchange readsb[1960]: WARNING: Reducing preamble threshold / decoding performance as this system has only 1 core (explicitely set --preamble-threshold to disable this behaviour)!

    Jul 09 21:45:45 adsbexchange readsb[1960]: Using lat: 23.7842, lon: 90.4151

    Jul 09 21:45:45 adsbexchange readsb[1960]: 30152: API output port 30002: Raw TCP output port

    Jul 09 21:45:45 adsbexchange readsb[1960]: 30005: Beast TCP output port 30154: Position json output port

    Jul 09 21:45:45 adsbexchange readsb[1960]: 30003: SBS TCP output ALL port 30001: Raw TCP input port

    Jul 09 21:45:45 adsbexchange readsb[1960]: 30004: Beast TCP input port 30104: Beast TCP input port

    Jul 09 21:45:45 adsbexchange readsb[1960]: rtlsdr: no supported devices found.

    Jul 09 21:45:45 adsbexchange readsb[1960]: Sat Jul 9 21:45:45 2022 UTC sdrOpen() failed, exiting!

    Jul 09 21:45:45 adsbexchange readsb[1960]: Sat Jul 9 21:45:45 2022 UTC Abnormal exit.

    Jul 09 21:45:45 adsbexchange systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE

    Jul 09 21:45:45 adsbexchange systemd[1]: readsb.service: Failed with result 'exit-code'.
     
  2. Racer X

    Racer X New Member

    Just tried a third SDR. This time a Nooelec NESDR Mini and still having the same problem.
     
  3. James

    James Guest

    lsusb

    Pi Zero is suspect.
     
  4. Racer X

    Racer X New Member

    FML..... I had the USB ports swapped. Only one on the Zero transmits data. Picking up aircraft now but status page still showing no feeder connection. Stats log has message asking if I installed the stats package but I was thinking I shouldn't need to since I used the adsbx image correct?
     
  5. wiedehopf

    wiedehopf Administrator Staff Member

    The image comes ready to go.

    You have a bad network configuration maybe?

    Could also be VPN or CGNAT giving the pi and you a different external IP address.

    Check if you're he're, if you are you're sending data: https://map.adsbexchange.com/mlat-map/

    rpi zero unless it's a pi zero 2 will give pretty limited results usually.
    But every bit helps, thanks for feeding!

    I checked, it's working fine.
     
    Last edited: Jul 10, 2022
  6. Racer X

    Racer X New Member

    Yeah, I see it's working.... and I'm the only one in the country feeding. Maybe it is a CGNAT issue as https://www.adsbexchange.com/myip/ keeps showing a different external IP every few min. I think switching between two different ones. On the Custom Image System Info Page the external and internal IP do not change and the external is not the same as what comes up on the /myip/ page.

    On the network config the only thing that is not correct is that I cannot select BD for Bangladesh as it does not come up in the list of countries to choose from.

    If you don''t see anything in the logs here then I'll just let it go as is since it's working somehow.

    Thanks for the help.

    readsb log gives me this

    Jul 10 23:14:11 adsbexchange readsb[30733]: Lost 5 packets on USB, MLAT could be UNSTABLE, check sync! (ppm: -8345) (or the system clock jumped for some reason)
    Jul 10 23:14:41 adsbexchange readsb[30733]: SDR ppm out of specification (could cause MLAT issues) or local clock jumped / not syncing with ntp or chrony! ppm: 5365
    Jul 10 23:15:11 adsbexchange readsb[30733]: SDR ppm out of specification (could cause MLAT issues) or local clock jumped / not syncing with ntp or chrony! ppm: 2977
    Jul 10 23:16:11 adsbexchange readsb[30733]: Lost 2 packets on USB, MLAT could be UNSTABLE, check sync! (ppm: -4252) (or the system clock jumped for some reason)
    Jul 10 23:16:41 adsbexchange readsb[30733]: SDR ppm out of specification (could cause MLAT issues) or local clock jumped / not syncing with ntp or chrony! ppm: 4250
    Jul 10 23:30:12 adsbexchange readsb[30733]: Lost 4 packets on USB, MLAT could be UNSTABLE, check sync! (ppm: -6508) (or the system clock jumped for some reason)
    Jul 10 23:30:42 adsbexchange readsb[30733]: SDR ppm out of specification (could cause MLAT issues) or local clock jumped / not syncing with ntp or chrony! ppm: 6508
    Jul 10 23:33:12 adsbexchange readsb[30733]: Lost 7 packets on USB, MLAT could be UNSTABLE, check sync! (ppm: -13142) (or the system clock jumped for some reason)

    and feeder log gives

    Jul 10 23:30:12 adsbexchange systemd[1]: Started adsbexchange-feed.
    Jul 10 23:30:12 adsbexchange adsbexchange-feed[16811]: Sun Jul 10 23:30:12 2022 UTC readsb starting up.
    Jul 10 23:30:12 adsbexchange adsbexchange-feed[16811]: readsb version: wiedehopf git: a12dec2 (committed: Mon Jun 6 21:53:41 2022 0200)
    Jul 10 23:30:12 adsbexchange adsbexchange-feed[16811]: Using lat: 23.7842, lon: 90.4151
    Jul 10 23:30:13 adsbexchange adsbexchange-feed[16811]: Beast TCP input: Connection established: 127.0.0.1 port 30005
    Jul 10 23:30:13 adsbexchange adsbexchange-feed[16811]: BeastReduce TCP output: Connection established: feed1.adsbexchange.com (216.48.109.64) port 30004 (sending UUID: xxxx-xxx-xxx-879d65a510d7)

    and meat log

    Jul 10 23:30:31 adsbexchange adsbexchange-mlat[16909]: Beast-format results connection with 127.0.0.1:30104: connection established
    Jul 10 23:30:34 adsbexchange adsbexchange-mlat[16909]: Server says:
    Jul 10 23:30:34 adsbexchange adsbexchange-mlat[16909]:
    Jul 10 23:30:34 adsbexchange adsbexchange-mlat[16909]: The multilateration server source code is available under
    Jul 10 23:30:34 adsbexchange adsbexchange-mlat[16909]: the terms of the Affero GPL (v3 or later). You may obtain
    Jul 10 23:30:34 adsbexchange adsbexchange-mlat[16909]: a copy of this server's source code at the following
    Jul 10 23:30:34 adsbexchange adsbexchange-mlat[16909]: location: https://github.com/adsbexchange/mlat-server
    Jul 10 23:30:34 adsbexchange adsbexchange-mlat[16909]:
    Jul 10 23:30:34 adsbexchange adsbexchange-mlat[16909]: Handshake complete: Compression zlib2, UDP transport disabled, Split sync disabled
    Jul 10 23:30:34 adsbexchange adsbexchange-mlat[16909]: Input connected to 127.0.0.1:30005
    Jul 10 23:30:34 adsbexchange adsbexchange-mlat[16909]: Input format changed to BEAST, 12MHz clock
    Jul 10 23:31:31 adsbexchange adsbexchange-mlat[16909]: Receiver: connected 0.0 msg/s received 0.0 msg/s processed (0%)
    Jul 10 23:31:31 adsbexchange adsbexchange-mlat[16909]: Server: ready 0.0 kB/s from server 0.0 kB/s to server
    Jul 10 23:31:31 adsbexchange adsbexchange-mlat[16909]: Results: 0.0 positions/minute
    Jul 10 23:31:31 adsbexchange adsbexchange-mlat[16909]: Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used
    Jul 10 23:31:38 adsbexchange adsbexchange-mlat[16909]: peer_count: 0 outlier_percent: 0.0 bad_sync_timeout: 0

    and stats log

    Jul 09 22:19:28 adsbexchange systemd[1]: Started ADSBexchange Stats.
    Jul 09 22:19:29 adsbexchange adsbexchange-stats[318]: Note: 'USE_OLD_PATH' is set.
    Jul 09 22:19:29 adsbexchange adsbexchange-stats[318]: No valid data source directory found, do you have the adsbexchange feed scripts installed? Tried each of: [/run/readsb /run/adsbexchange-feed]
    Jul 09 22:19:51 adsbexchange adsbexchange-stats[318]: Using UUID [xxxx-xxx-xxx-879d65a510d7] for stats uploads
    Jul 09 22:19:51 adsbexchange adsbexchange-stats[318]: Using JSON directory [/run/readsb] for source data
    Jul 09 22:19:51 adsbexchange adsbexchange-stats[318]: Using script's DNS cache (600 seconds)
    Jul 10 13:04:17 adsbexchange adsbexchange-stats[7962]: curl: (28) Operation timed out after 10000 milliseconds with 0 bytes received
    Jul 10 13:04:17 adsbexchange adsbexchange-stats[318]: WARNING: curl process returned non-zero (28): []; Sleeping a little extra.
    Jul 10 13:04:30 adsbexchange adsbexchange-stats[8070]: curl: (7) Failed to connect to adsbexchange.com port 443: Network is unreachable
    Jul 10 13:04:30 adsbexchange adsbexchange-stats[318]: WARNING: curl process returned non-zero (7): []; Sleeping a little extra.
    Jul 10 13:04:46 adsbexchange adsbexchange-stats[8137]: curl: (7) Failed to connect to adsbexchange.com port 443: Network is unreachable
    Jul 10 13:04:46 adsbexchange adsbexchange-stats[318]: WARNING: curl process returned non-zero (7): []; Sleeping a little extra.
    Jul 10 18:22:07 adsbexchange adsbexchange-stats[14107]: curl: (7) Failed to connect to adsbexchange.com port 443: Network is unreachable
    Jul 10 18:22:07 adsbexchange adsbexchange-stats[318]: WARNING: curl process returned non-zero (7): []; Sleeping a little extra.
    Jul 10 18:22:32 adsbexchange adsbexchange-stats[14218]: curl: (28) Connection timed out after 10004 milliseconds
    Jul 10 18:22:32 adsbexchange adsbexchange-stats[318]: WARNING: curl process returned non-zero (28): []; Sleeping a little extra.
    Jul 10 18:22:42 adsbexchange adsbexchange-stats[14255]: curl: (7) Failed to connect to adsbexchange.com port 443: Network is unreachable
    Jul 10 18:22:42 adsbexchange adsbexchange-stats[318]: WARNING: curl process returned non-zero (7): []; Sleeping a little extra.
     
  7. wiedehopf

    wiedehopf Administrator Staff Member

    The SDR isn't quite getting enough voltage ... or the SDR isn't quite perfect.
    This can be the power supply not supplying 5.1 V consistently or the USB cables dropping too much voltage.

    Anyhow it's working good enough and the pi zero doesn't work that great anyhow.

    I need to add a button for the pi zero so that you can disable graphs1090, the pi zero doesn't quite have enough CPU for that.
    You can disable manually using these commands:
    Code:
    sudo system disable --now graphs1090
    sudo system disable --now collectd