Feeding FA and ADS-B Exchange

Hi everyone,

I am currently feeding 1090 and 978 to FA with a pretty good set-up. I would like to feed ADSBX at the same time. Every time I read into doing it, I get discouraged and quit, plus I don’t want to lose what I have going. 856 streak LOL

Today I attempted to install ADSBX using putty and I think I installed the “image OS” by accident and not the script for current FA users. Its still reporting to FA but now I installed the wrong stuff.

“curl -L -o /tmp/axfeed.sh https://github.com/adsbxchange/adsb-exchange/raw/master/install.sh
sudo bash /tmp/axfeed.sh”

“sudo bash /tmp/axfeed.sh”

I closed Putty at this time

I have a few questions and maybe some guidance would help.

-How do I check what’s on the SD card currently and delete it if necessary?
-What is the best operating system FA or ADSBX for a fresh SD install?
-I can feed both clients regardless of OS correct?

JeepRubicon2k3 ADS-B Feeder Statistics - FlightAware

Do NOT re-image your existing microSD card. Preserve it as a backup. Instead reimage a spare microSD card.

In case something goes wrong, slip out the newly re-imaged microSD card, and slip in the preserved old one and your streak will not be lost. :slightly_smiling_face:

 

(1) Download & write Image

(1.1) Go to:
https://flightaware.com/adsb/piaware/build/

(1.2) Scroll down and download this image:

 

(1.3) Write above image to SPARE microSD card

(2) Configure dump1090-fa & dump978-fa with serial numbers of dongles

Note:

  1. In commands below replace 00001090 and 00000978 by serial numbers you have assigned to your dongles.
  2. Replacexxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx by your actual feeder id (Unique Identifier)
sudo piaware-config feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  

sudo piaware-config uat-receiver-type sdr   

sudo piaware-config rtlsdr-device-index 00001090  

sudo piaware-config uat-sdr-device driver=rtlsdr,serial=00000978  


sudo reboot   

 

(3) Install Adsbexchange feeder

wget -O /tmp/axfeed.sh https://adsbexchange.com/feed.sh   

sudo bash /tmp/axfeed.sh   

 

(4) Install Performance Graphs:

sudo bash -c "$(wget -q -O - https://raw.githubusercontent.com/wiedehopf/graphs1090/master/install.sh)"   

1 Like

What you quote below is not the “image OS” …

Those are the two feed clients you’ll need, 1090 and 978.
https://github.com/adsbxchange/adsb-exchange
https://github.com/adsbxchange/adsbexchange-978

Thanks for all the help guys! I’m up and running on a new SD, I ended up just copying the pi config data off the old card and pasting it into the new install config file. Network settings, Feeder ID and 1090-978 all transferred and work!

I used Putty to get ADSBX and the graphs which are awesome!

Any tips to max out my set-up?

I’m running a Pi3B with blue and orange dongles, about 35ft of LMR400 to both antennas on the roof peak about 20ft AGL 26ft MSL.

The 1090 can get about 270 miles for the high stuff and about 50 miles for low 1000ft aircraft, aircraft disappear when close.

The 978 is not as far but I’m guessing 40 miles for the low aircraft. Oddly I pick up some 978 in class A and our local MedFlight transmits on both.

Some day I’ll install a mast :slight_smile:

Your gain’s too high. Look at your ADS-B Message Rate graph in graphs1090. The red Messages > 3dBFS should be at around 5% or less, or up to 10% if you live near an airport and have lots of nearby aircraft. If it’s higher than that, reduce your gain and watch it for a day or so. Keep adjusting until the number’s lower and you stop losing nearby aircraft from the map.

Maybe or likely.
But there are other reasons, why aircraft disappear

True, maybe due to being blocked by a building or tree when they get close and/or are low in altitude. I would still check the messages >3dBFS percentage first because gain adjustments are easiest to fix vs. moving the antenna.

I think you’re onto something, my 6 day average is 9.8%. I have a small GA airport nearby but it gets very little traffic this time of year. What’s the best way to go about adjusting gain? Try to get around 5% like you stated.

Using Putty:

Both 1090 and 978 are “MAX”

I have changed 1090 to “49.6” as a starting point and it looks like the red has almost completely gone away. This is the max programable gain correct?

Just had a GA 1090 fly by a few miles away and did not loose them

Max gain in version 7.2 is 60

 Initial receiver gain, in dB. If adaptive gain is enabled (see below) the act>
# may change over time
RECEIVER_GAIN=60

# Adjust gain to try to achieve optimal dynamic range / noise floor?
ADAPTIVE_DYNAMIC_RANGE=yes
# Target dynamic range in dB (leave blank to autoselect based on SDR type)
ADAPTIVE_DYNAMIC_RANGE_TARGET=
# Reduce gain when loud message bursts from nearby aircraft are seen?
ADAPTIVE_BURST=no
# Gain range to allow when changing gain, in dB (empty = no limit)
ADAPTIVE_MIN_GAIN=
ADAPTIVE_MAX_GAIN=

I’m sorry its like you’re speaking a different language here lol. What is the coding?

Do you have the FA version 7.2 available manual gain numbers? I’m running v7.1 is v7.2 out yet?

Is there a post where I can read up on graph interpretation and what it all means?

The coding is the settings of the of the dump1090-fa file in /etc/default/dump1090-fa
You can adapt the coding when you edit that file :slight_smile:

In the following file you can read all about the adaptive gain and it’s inner workings.
https://github.com/flightaware/dump1090/commit/08c7ccbc8e65c92f7d518ff573ea3c6d1ff4a70d
Max gain was defined in the past in the settings as -10 (AGC)

Actually 60-ish is the new -10. 49.6 is still the highest gain with AGC disabled.

Version 7.2 is indeed availble since 2 days ( I discovered this only today) and available for both dump1090-fa and piaware.
You can upgrade via the options in the flightfeeder page.
Under the gray icon you will find the option device commands( when you enabled them on installation).

Icon

Piaware

Dump1090

after running these commands your setup will upgrade to version 7.2 and that can be seen on the flightfeeder page.

flightfeeder page

Dump1090-FA Version 7.2 brings minor changes

  • dump1090: Fix Makefile syntax error for Darwin OS build
  • dump1090: set _POSIX_C_SOURCE to fix build failure with uclibc-ng
  • SkyAware: Remove obselete map interface at /dump1090-fa
  • SkyAware: Remove OSM Black & White layer which is no longer in service

Piaware version 7.2 brings no change, just an updated version number:

1 Like

Is ver 7.2 released?
To my knowledge latest version is 7.1

2 Likes

After updating to v7.2 I still only see 49.6 for max programable but that may be because its testing the 978 dongle. How do I test dongle #1?

Using:
pi@piaware:~ $ rtl_test -t

Found 2 device(s):
0: Realtek, RTL2832U, SN: 00000978
1: Realtek, RTL2832U, SN: 00001090

Using device 0: Generic RTL2832U
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
[R82XX] PLL not locked!
Sampling at 2048000 S/s.
No E4000 tuner found, aborting.

Also my -3dBFS is down to 0.9% @ 49.6 gain, it appears to be getting more planes and messages.

8 hour graphs, what do you think?


dump1090-localhost-signal-8h

To test device 0
rtl_test -t (by default)
rtl_test -t -d 0 (explicit)

To test device 1
rtl_test -t -d 1 (explicit)

To test device n
rtl_test -t -d n (explicit)

 

It looks better but your noise level and the level of your weakest messages are almost the same. If you reduce the gain even further you may be able to drop the noise floor even lower. See if you can get it to where the weakest signals are stronger than the noise.

Here’s what mine looks like, for comparison (default 24 hour graph):
ads-b signal levels

1 Like

No piaware changes in 7.2, I guess that you’re looking at a diff and misreading it. The only change was to change the version number.

7.2 is mostly about (a) getting the libpolkit security update into the sdcard image and (b) adding the tcl-tls rebuild back in (though that unfortunately seems ineffective so far). No need to update if everything is working OK for you.

“60” is a synthetic gain number, it’s not directly supported by librtlsdr and the rtl_* tools.

(I’d like to go and fix librtlsdr at some point to fix up the gain mess, but it’s been really hard to find the time)

2 Likes

thanks for the clarification :slight_smile:

yes it is since 2 days, I accidently discovered it when searching the adaptive gain documentation on Github.
But as obj said, no need to update if you don’t have issues.