I’m not new to Linux but I am new to setting up a feed for flightaware and have some questions pertaining to UAT/978 and the physical setup.
My past experience tells me that there is by orders of magnitude more 1090 traffic than UAT and should the WX be lousy there maybe very little if any UAT traffic to be seen so this might factor into what I’m currently seeing (local airport is reporting 3miles, mist, and a low overcast.).
I can confirm that I am sending 1090 traffic to FA but piaware-status shows “PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)” however I do see dump978 is running with the following “/usr/bin/dump978-fa --sdr driver=rtlsdr,serial=00000103 --format CS8 --raw-port 30978 --json-port 30979” and a quick look at the loopback interface with tcpdump confirms there is data between ports 30978 & 52800. (port 52800 is skyaware978).
So am I properly forwarding UAT traffic to FA even though I see this message from piaware-status - “PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)” ??? FA only shows a feeder mode of 1090. If not, what do I need to do to properly enable UAT?
Next question, I built two small 1/4wave ground plane antennas, they are mounted in the attic about 3ft apart, I mounted the SDR directly to the antenna and used a couple of 3ft USB extension cables to reach the raspberry pi. I was wondering if anybody has tried using the USB extenders that work over UTP? I would rather move the RP to the basement where I can get to it easily should there be an issue and 1 ethernet type cable is a lot easier to run than 3 antenna wires (I’m also feeding liveatc).
PiAware master process (piaware) is running with pid 588.
PiAware ADS-B client (faup1090) is running with pid 793.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is running with pid 790.
Local ADS-B receiver (dump1090-fa) is running with pid 583.
dump1090-fa (pid 583) is listening for ES connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is connected to FlightAware.
dump1090 is producing data on localhost:30005.
Your feeder ID is db0ba867-d7d2-4.............. (from /var/cache/piaware/feeder_id)
from /etc/default/dump978-fa
# dump978-fa configuration
# This is sourced by /usr/share/dump978-fa/start-dump978-fa as a
# shellscript fragment.
# If you are using a PiAware sdcard image, this config file is regenerated
# on boot based on the contents of piaware-config.txt; any changes made to this
# file will be lost.
# dump978-fa won't automatically start unless ENABLED=yes
ENABLED=yes
RECEIVER_OPTIONS="--sdr driver=rtlsdr,serial=00000103 --format CS8"
DECODER_OPTIONS=""
NET_OPTIONS="--raw-port 30978 --json-port 30979"
/etc/default/dump1090-fa
# dump1090-fa configuration
# This is sourced by /usr/share/dump1090-fa/start-dump1090-fa as a
# shellscript fragment.
# dump1090-fa won't automatically start unless ENABLED=yes
ENABLED=yes
# SDR device type. Use "none" for a net-only configuration
RECEIVER=rtlsdr
# serial number or device index of device to use (only needed if there is more than one SDR connected)
RECEIVER_SERIAL=00000101
# Initial receiver gain, in dB. If adaptive gain is enabled (see below) the actual gain
# 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=
# Turn on options to reduce load on slower CPUs, at the expense of slightly worse decoder performance.
# Setting "auto" will enable these options only if the CPU appears to be a slow CPU (currently this
# means armv6 only, e.g. Pi Zero)
SLOW_CPU=auto
# Local wisdom file used to select DSP implementations; uses built-in ranking if the file is missing
WISDOM=/etc/dump1090-fa/wisdom.local
# Correct CRC errors where possible
ERROR_CORRECTION=yes
# Receiver location, used for some types of position decoding. Provide the location as
# signed decimal degrees. If not given here, dump1090 will also try to read a receiver
# location from /var/cache/piaware/location.env (written automatically by PiAware, if installed)
RECEIVER_LAT=
RECEIVER_LON=
# Maximum range, in NM. Positions more distant than this are ignored. No limit if not set.
MAX_RANGE=360
# Network ports to listen on for connections
NET_RAW_INPUT_PORTS=
NET_RAW_OUTPUT_PORTS=30002
NET_SBS_OUTPUT_PORTS=30003
NET_BEAST_INPUT_PORTS=30004,30104
NET_BEAST_OUTPUT_PORTS=30005
# Accuracy of location written to JSON output
JSON_LOCATION_ACCURACY=1
# Additional options can be added here:
EXTRA_OPTIONS=""
# If OVERRIDE_OPTIONS is set, only those options are used; all other options
# in this config file are ignored.
OVERRIDE_OPTIONS=""
# This is a marker to make it easier for scripts to identify a v6-style config file
CONFIG_STYLE=6
and I have the following running that are associated with piaware (might have missed something)
ok, I added to /etc/piaware.conf “uat-receiver-type sdr” and that seems to have made the system happy. Now I’ll have to see when I get UAT traffic as the vast majority of traffic is 1090.
Now my other outstanding question… using a USB extender to extend the USB from the basement to the attic and supporting 3 SDR modules, the power supply that came with the extender is only 1amp @ 5v, not sure if that is the max the unit can support or a larger power supply might be in order, eg 2amp @ 5v.
Just on that point, I tried that too and it ruined my MLAT numbers. I can only presume it either introduced a small enough delay which took the timings over the threshold of usefulness, or the cable quality was in some way not adequate for the job. Though if it was the cable quality I would expect all numbers to be affected, not just MLAT.
You are getting positions on the 978 decoder, not that many aircraft but at least you are catching them. In Europe we don’t have 978 traffic at all so it’s all 1090Mhz here.
In my experience, USB over Cat5/Cat6 doesn’t work well. It tends to be slow and signal can drop in and out, plus there tends to be signal conversion latency. It’s fine if you have a label printer that doesn’t play well over a network and needs to be in a different room, for example, but not as a USB extension running constant communication. Trying to use it in place of antenna cable isn’t very practical.
If you want to run ethernet instead of antenna cables, then I’d suggest you move your ADS-B decoder (RPi or whatever) closer to the antennas instead.
I have two issues with leaving the RPi in the attic, first is heat, the attic does get quite warm in the summer. the other issue is getting the the RPi in the event something goes wrong. There is a big A/C unit running the width of the attic between the RPi and the entrance to the attic, the entrance to the attic is through an access panel in the ceiling of a closet.
I am powering the RPi via a PoE switch so I can control power if need be (wish the RPi supported PoE without an adapter) but getting to the unit in the event of a failure of some sort is a big ordeal.
Right now the RPi is sitting in the attic with 3 - USB extension cables (USB-A Male to Female) about 6 to 8 ft long, those cables are plugged directly into the RPi and the other end is connected directly to the SDR, the SDR is connected directly to their respective antenna, two for FA and one for liveatc.
I’ve never had issues with heat in the attic even though I’m in Clearwater, FL.
If I had to do it again, I’d stick with a long length of LMR coax and keep the electronics out of the attic. (my second example) There is no performance difference between the setups because the antennas are similarly located in the attic. I’d like to have exterior antennas, but the HOA does not allow anything mounted on the exterior.
@tech0 there may be a workaround for your HOA if you live in the United States. It’s against the law for your HOA to prevent you from setting up an antenna for picking up over-the-air broadcast or satellite TV (47 C.F.R. Section 1.4000).
Your HOA can set certain limitations (e.g. if you live in a condo, you may be restricted from setting up the antenna where it pokes out beyond your balcony; and you may not be allowed to attach something to the side of the building if the HOA is responsible for exterior maintenance). There are some other limitations, such as if the HOA has installed a centralized TV/Satellite receiver that you have access to use. However, it’s up to the HOA to prove that their restrictions aren’t a burden under the law, and any language in HOA rules, contracts, etc., are invalidated unless they can prove it’s not an excessive burden.
Let’s say you have a TV on the far side of your house from where it can pick up OTA TV with an indoor antenna; or you live too far away to receive reliable OTA television; or you live in the shadow of a hill or mountain. You have good cause to put up an exterior antenna, and the HOA has to prove that their restrictions are reasonable.
Your HOA could argue they provide access to cable TV, and I don’t know if that’s a “reasonable” workaround. However, other antenna types are also covered. It could be argued that ADS-B qualifies, but it’s not spelled out as one in the regulations.
As a result, you could co-locate a TV or other specifically covered antenna with an ADS-B antenna and your HOA would most likely be upset with you, but there’s very little they can do to stop it. Most likely they’d be none-the-wiser about the two different antenna types.
The association has complete control of the exterior of the building. Owner’s control the interior but it stops at the wall paint. The association does all exterior maintenance except washing windows. I’m well versed on the subject because I am VP of the association.
As I understand it, for satellite TV there’s some kind of blanket exemption for a 1-ft dish. Apparently the HOA can’t rule against that – even when the dish is a rusting hulk no longer in use and is kind of an eye-sore. A 1090 MHz antenna looks different, just a vertical pole, and isn’t that intrusive. However I would hate to go to the expense and trouble of putting something up to later having to take it down.
@tech0 I can’t speak to your knowledge or expertise of the subject. In my experience, most HOAs think they have more power than they do on this subject, but the rule also isn’t a Trump Card to play against them. Every situation is going to be a bit different, and you are going to be much more familiar with your situation than I could ever be.
My brother-in-law successfully fought an HOA over satellite receivers facing a street. I was once able fight for a couple of months (until I moved out) over a prohibition of window-mounted leaf-style antennas.
@jimMerk2 it’s not that there’s a “blanket” exemption. It’s that the HOA has to show that its limitations are reasonable. In the case of the Association having responsibility for exterior maintenance, as ua549 mentioned, that gives them significantly more leeway.
In my experience, USB over Cat5/Cat6 doesn’t work well. It tends to be slow and signal can drop in and out, plus there tends to be signal conversion latency. It’s fine if you have a label printer that doesn’t play well over a network and needs to be in a different room, for example, but not as a USB extension running constant communication. Trying to use it in place of antenna cable isn’t very practical.
If you want to run ethernet instead of antenna cables, then I’d suggest you move your ADS-B decoder (RPi or whatever) closer to the antennas instead.
I still want the SDR modules either attached to the antennas or with very short CoAX runs in attic and put the RPi in the basement, currently I’ve run the antenna wires to the basement, UAT is running over RG-58u, 1090es is over RG-400, and a third SDR is using RG8 (live ATC). I just picked up an active USB extender that is 40ft long, claims to be able to run full speed USB 2.0, so fingers are crossed that it does what it claims.
The RPi needs to be accessible in case of issues and it is not easily accessible and would take about an hour to get a ladder, climb through the attic over or around the A/C unit to get to the RPi, not fun. The RPi is running more than just the flightaware and LiveATC software, it is also my WiFi controller for the house. Actually it started as my WiFi controller first then the other stuff has been added. I did however pick up a PoE HAT, it is a lot cleaner than the PoE dongle splitters, probably more reliable too, although I’ve only had on PoE splitter fail in the 6 or 7 years I’ve been using them.
ok, the RPi is in the basement, the SDR modules are in the attic and attached directly to their respective antenna’s.
First I picked up an ACTIVE USB repeater, got a “Lindy 42783” it is 40ft long and claims to support full speed (480Mb/s) USB 2.0 at that length. Only caveat is it needs to be powered at the far end (attic) and I don’t have good source of power up there without extension cords which I really don’t like. In order to power it I took an existing unused CAT 3 wire (yes CAT 3) and put RJ-45 ends on it, plugged one end into my PoE switch and the other into a PoE/Ethernet splitter, I then plugged the PoE adapter into the USB repeater (had to make an adapter for the different power plug size) and everything came up and seems to be working nicely. Side note, CAT 3 is approved for PoE per the spec, only issue is, it only supports 10Mb/s throughput, but since I’m not using the ethernet it doesn’t matter.
Time will tell if it is stable but so far it is supporting 3 SDR modules.
