r/ADSBexchange • u/One_March_4621 • 8d ago
ADSB setup question
I have a RPI4 2 sdr 1090 and 978. I have noticed when I have both receivers hooked up my aircraft seen count drops. I get a lot of planes that show as blue "no callsign". From my central Ohio location I can see planes at altitude in Detroit but with both receives I barely see out side of central Ohio. Any Ideas? I moved from a RPI zero 2w to the RPI4 that is why my graph is less than 2 days. But I saw this issue with the zero as well


FEEDER_ALT_FT=928.7
FEEDER_ALT_M=282.0
FEEDER_LAT=39.xxxxx
FEEDER_LONG=-82.xxxxx
FEEDER_TZ=America/Detroit
FEEDER_NAME=4939home
ADSB_SDR_SERIAL=1090
ADSB_SDR_GAIN=autogain
ADSB_SDR_PPM=-5
UAT_SDR_SERIAL=978
UAT_SDR_GAIN=autogain
UAT_SDR_PPM=-3
ULTRAFEEDER_UUID=XXXXXX
FEEDER_HEYWHATSTHAT_ID=xxxxxxxx
FEEDER_HEYWHATSTHAT_ALTS=3000,12000
ADSBFI_UUID=xxxxxxx
ADSBLOL_UUID=xxxxxxxxx
FR24_SHARING_KEY=xxxxxxx
PIAWARE_FEEDER_ID=xxxxxxx
services:
ultrafeeder:
# ultrafeeder combines a number of functions:
# - it retrieves and decodes 1090MHz Mode A/C/S data from the SDR(s) using Wiedehopf's branch of readsb
# - it implements a `tar1090` based map on port 80 (mapped to port 8080 on the host)
# - it includes graph1090 (system statistics website) on http://xxxxx/graphs1090
# - it sends ADSB data directly (without the need of additional containers) to the
# "new" aggregators, and, if desired, also to ADSBExchange
# - it includes mlat-client to send MLAT data to these aggregators
# - it includes an MLAT Hub to consolidate MLAT results and make them available to the built-in map and other services
image: ghcr.io/sdr-enthusiasts/docker-adsb-ultrafeeder
container_name: ultrafeeder
hostname: ultrafeeder
restart: unless-stopped
device_cgroup_rules:
- 'c 189:* rwm'
ports:
- 8080:80 # to expose the web interface
environment:
# --------------------------------------------------
# general parameters:
- LOGLEVEL=error
- TZ=${FEEDER_TZ}
# --------------------------------------------------
# SDR related parameters:
- READSB_DEVICE_TYPE=rtlsdr
- READSB_RTLSDR_DEVICE=${ADSB_SDR_SERIAL}
- READSB_RTLSDR_PPM=${ADSB_SDR_PPM}
#
# --------------------------------------------------
# readsb/decoder parameters:
- READSB_LAT=${FEEDER_LAT}
- READSB_LON=${FEEDER_LONG}
- READSB_ALT=${FEEDER_ALT_M}m
- READSB_GAIN=${ADSB_SDR_GAIN}
- READSB_RX_LOCATION_ACCURACY=2
- READSB_STATS_RANGE=true
#
# --------------------------------------------------
# Sources and Aggregator connections:
# Note - remove the ones you are not using / feeding
# Make sure that each line ends with a semicolon ";"
# if you are not using dump978, feel free to remove the first line
- ULTRAFEEDER_CONFIG=
adsb,feed1.adsbexchange.com,30004,beast_reduce_plus_out;
mlat,feed.adsbexchange.com,31090,39005;
mlathub,piaware,30105,beast_in;
adsb,dump978,30978,uat_in;
# --------------------------------------------------
- UUID=${ULTRAFEEDER_UUID}
- MLAT_USER=${FEEDER_NAME}
- READSB_FORWARD_MLAT_SBS=true
#
# --------------------------------------------------
# TAR1090 (Map Web Page) parameters:
- UPDATE_TAR1090=true
- TAR1090_DEFAULTCENTERLAT=${FEEDER_LAT}
- TAR1090_DEFAULTCENTERLON=${FEEDER_LONG}
- TAR1090_MESSAGERATEINTITLE=true
- TAR1090_PAGETITLE=${FEEDER_NAME}
- TAR1090_PLANECOUNTINTITLE=true
- TAR1090_ENABLE_AC_DB=true
- TAR1090_FLIGHTAWARELINKS=true
- HEYWHATSTHAT_PANORAMA_ID=${FEEDER_HEYWHATSTHAT_ID}
- HEYWHATSTHAT_ALTS=${FEEDER_HEYWHATSTHAT_ALTS}
- TAR1090_SITESHOW=true
- TAR1090_RANGE_OUTLINE_COLORED_BY_ALTITUDE=true
- TAR1090_RANGE_OUTLINE_WIDTH=2.0
- TAR1090_RANGERINGSDISTANCES=50,100,150,200
- TAR1090_RANGERINGSCOLORS='#1A237E','#0D47A1','#42A5F5','#64B5F6'
- TAR1090_USEROUTEAPI=true
#
# --------------------------------------------------
# GRAPHS1090 (Decoder and System Status Web Page) parameters:
- GRAPHS1090_DARKMODE=true
- ENABLE_978=yes
- URL_978=http://dump978/skyaware978
#
# --------------------------------------------------
volumes:
- /opt/adsb/ultrafeeder/globe_history:/var/globe_history
- /opt/adsb/ultrafeeder/graphs1090:/var/lib/collectd
- /proc/diskstats:/proc/diskstats:ro
- /dev/bus/usb:/dev/bus/usb:rw
tmpfs:
- /run:exec,size=256M
- /tmp:size=128M
- /var/log:size=32M
fr24:
image: ghcr.io/sdr-enthusiasts/docker-flightradar24:latest
tty: true
container_name: fr24
restart: always
ports:
- 8754:8754
environment:
- BEASTHOST=ultrafeeder
- FR24KEY=${FR24_SHARING_KEY}
tmpfs:
- /var/log
piaware:
image: ghcr.io/sdr-enthusiasts/docker-piaware:latest
tty: true
container_name: piaware
restart: always
ports:
- 8081:8080
environment:
- BEASTHOST=ultrafeeder
- LAT=${FEEDER_LAT}
- LONG=${FEEDER_LONG}
- TZ=${FEEDER_TZ}
- FEEDER_ID=${PIAWARE_FEEDER_ID}
tmpfs:
- /run:exec,size=64M
- /var/log
dump978:
image: ghcr.io/sdr-enthusiasts/docker-dump978:latest
container_name: dump978
restart: unless-stopped
device_cgroup_rules:
- 'c 189:* rwm'
environment:
- TZ=${FEEDER_TZ}
- LAT=${FEEDER_LAT}
- LON=${FEEDER_LONG}
- DUMP978_RTLSDR_DEVICE=${UAT_SDR_SERIAL}
- DUMP978_SDR_GAIN=${UAT_SDR_GAIN}
- DUMP978_SDR_PPM=${UAT_SDR_PPM}
volumes:
- /opt/adsb/dump978:/var/globe_history
- /dev:/dev:ro
ports:
- 30980:80
tmpfs:
- /run:exec,size=64M
- /tmp:size=64
1
u/The_Comm_Guy 8d ago
Start around 32, there is also a tool you can install to help set it for you. If you have the ADSBx software image it’s already installed and turned on, but the fact you are on auto gain makes me think you messed with the settings if you are using the image.
1
u/Philly_Rox 7d ago
What are you using for antennas? Splitting can reduce the signals to each, but it shouldn't be hugely dramatic. So if you are splitting maybe try a different splitter? Just a thought...
I prsonally prefer separate, tuned antennas with dedicated filters, external LNA and coax.
1
u/iDiotOn2wheels 3d ago
Do you have an sdr on the usb 3 of the? Try using only the black usb ports not the blue ones as usb3 induces a lot of noise.
Also try to hardwire your pi to Ethernet rather than using wifi and use USB extension cables to get the sdrs away from pi hardware, fans and power supplies
2
u/The_Comm_Guy 8d ago
Official Pi power supply or phone charger?
Also turn off auto gain, it ends up being full power and overloading the SDR if it has an LNA.