UAT with the Stratux v3 978 dongle

FlightAware ADS-B Flight Tracking
1

I’ve searched! I know I’m new but I’ve been building and coding rpi / arduino / everything else for many years. Only new here.

Anyways, I wanted to try one of these ADS-b feeders.
Installed on a rpi zero 2w with bullseye 64bit. Fresh install, fully updated.
I’m up and running with the ADS-B data, no problem at all. For UAT however I can’t get this dump978 to work at all. I have the Stratux V3 UAT dongle, the little red low power one. Other people seem to have this working, and I’ve done the following.

configure the dump978-fa options in /etc/default/dump978-fa
Replace the existing RECEIVER_OPTIONS with --stratuxv3 /dev/uatradio

Here’s a dump of the dump978 config

# dump978-fa won't automatically start unless ENABLED=yes
ENABLED=yes

RECEIVER_OPTIONS="--stratuxv3 /dev/uatradio"
DECODER_OPTIONS=""
NET_OPTIONS="--raw-port 30978 --json-port 30979"

Also edited the piaware.conf file

allow-auto-updates yes   # updated by fa_piaware_config
allow-manual-updates yes   # updated by fa_piaware_config
uat-receiver-type stratuxv3   # updated by fa_piaware_config

I’ve tried a ton of variations in both. Only running the UAT dongle, etc. It never sees it.
The light on the dongle blinks, which is supposed to mean its getting signals.

LSUSB sees the dongle as
Bus 001 Device 003: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)

It’s not RTL so rtl_test doesn’t see it

Can anyone who has this working let me know what I’m missing? If this is a dead end I’ll just get a different sdr for 978, this one came as a package for stratux and was very cheap, but I won’t be able to get another one until next week so this is my project for now.
Thanks!

1 Like
2

Pi aware status and log for dump978

PiAware master process (piaware) is running with pid 609.

PiAware ADS-B client (faup1090) is running with pid 777.

PiAware ADS-B UAT client (faup978) is not running.

PiAware mlat client (fa-mlat-client) is running with pid 897.

Local ADS-B receiver (dump1090-fa) is running with pid 464.

Local ADS-B UAT receiver (dump978) is not running.

dump1090-fa (pid 464) is listening for ES connections on port 30005.

no program appears to be listening for UAT connections on port 30978.

faup1090 is connected to the ADS-B receiver.

faup978 is NOT connected to the ADS-B UAT receiver.

piaware is connected to FlightAware.

got 'couldn't open socket: connection refused'

dump978 is NOT producing data on localhost:30978.

dump1090 is producing data on localhost:30005.


Jan 19 21:51:08 raspberrypi systemd[1]: dump978-fa.service: Scheduled restart job, restart counter is at 45.

Jan 19 21:51:08 raspberrypi systemd[1]: Stopped dump978 ADS-B UAT receiver.

Jan 19 21:51:08 raspberrypi systemd[1]: Started dump978 ADS-B UAT receiver.

Jan 19 21:51:08 raspberrypi dump978-fa[6232]: raw-port: listening for connections on 0.0.0.0:30978

Jan 19 21:51:08 raspberrypi dump978-fa[6232]: raw-port: listening for connections on [::]:30978

Jan 19 21:51:08 raspberrypi dump978-fa[6232]: json-port: listening for connections on 0.0.0.0:30979

Jan 19 21:51:08 raspberrypi dump978-fa[6232]: json-port: listening for connections on [::]:30979

Jan 19 21:51:08 raspberrypi dump978-fa[6232]: Message source reports error: No such file or directory

Jan 19 21:51:08 raspberrypi dump978-fa[6232]: Abnormal exit

Jan 19 21:51:08 raspberrypi systemd[1]: dump978-fa.service: Main process exited, code=exited, status=1/FAILURE

Jan 19 21:51:08 raspberrypi systemd[1]: dump978-fa.service: Failed with result 'exit-code'.
4

This means that /dev/uatradio (the USB-serial port) doesn’t exist.

dump978-fa ships with some udev rules to set this symlink up, but they assume USB IDs of 0403:7028. Your device has 0403:6015. It may be sufficient to edit /lib/udev/rules.d/60-dump978-fa.rules with the new IDs (but I can’t test that) – or ideally you’d copy the existing rules to /etc/udev/rules.d/ and modify them there, so your changes aren’t lost on package upgrade.

If it does work with the new IDs let me know and I can add extra rules to the standard package for it?

2 Likes
5

Changed everything that said 7028 to 6015 in the 60-dump978-fa.rules file.
Looks like this now.

# Stratux uatradio.

# 0403:6015 (Stratux UATRadio)

ATTRS{idProduct}=="6015", ATTRS{idVendor}=="0403", RUN+="/sbin/modprobe -q ftdi_sio" RUN+="/bin/sh -c 'echo 0403 6015 > /sys/bus/usb-serial/drivers/ftdi_sio/new_id'"

ATTRS{idProduct}=="6015", ATTRS{idVendor}=="0403", SUBSYSTEM=="tty", OWNER="root", MODE="0666", SYMLINK+="uatradio"

Damn, reboot and UAT is working. Thank you!
So I just copied the rules file to the other location, same file in both?
sudo cp /lib/udev/rules.d/60-dump978-fa.rules /etc/udev/rules.d/

Anything else you want to know or test?

2 Likes
6

Thanks for testing, I just needed confirmation that it did work OK after the new ID was added. (A different ID implies different hardware, but it sounds like it is close enough to the original that everything else still works).

I’ll add that ID to the package rules.

3 Likes