FlightAware Discussions

Cant get UAT 978 to work on new pi

Been trying for hours, had to reflash the card a few times because of settings getting messed up.

I have a new pi 3 that will be specifically used for 978 only, no 1090 at all. only using the orange flightaware dongle.

there is so much conflicting information online that I have no idea if it is right or not.

if i go to the ip address of the pi, piaware and flightaware is green, but the 978 UAT radio icon stays red with the error NOT CONNECTED TO UAT RECEIVER. every so many seconds everything turns red with the error “piaware doesnt appear to be running”

my other pi with 1090 works perfectly.

I have no idea what im doing wrong. I have been fighting this for hours and about to give up on it

Have you tried this guide?
If not, reading it in full will help.
Below is quote of that part of the guide which is specific to your issue.

I have read the guide and used those exact commands before posting here, but still getting the exact errors in the first post

sudo journalctl --no-pager -u dump978-fa
sudo journalctl --no-pager -u piaware

Show the last 20 or so lines of output from each of those please.

2 Likes

After changing the power supply to using one of the samsung quick phone chargers has stopped the piaware from constantly going offline/online, and the UAT icon at the home screen on the PI using the IP address is now orange instead of red, but thats because the antenna is inside the house and I havent heard any small aircraft flying about, so I am not overly concerned since there may be nothing about for it to hear at 978 mhz

from dump978-fa

May 28 14:33:47 piaware dump978-fa[622]: [::]:30978: accepted a connection from [::1]:58578
May 28 14:33:48 piaware dump978-fa[622]: [::]:30978: accepted a connection from [::1]:58580
May 28 14:34:30 piaware dump978-fa[622]: [::]:30978: accepted a connection from [::1]:36435
May 28 14:34:40 piaware dump978-fa[622]: [::1]:36435: connection closed
May 28 15:37:46 piaware dump978-fa[622]: [::1]:58580: connection closed
May 28 15:37:47 piaware dump978-fa[622]: Caught signal 15, exiting
May 28 15:37:47 piaware systemd[1]: Stopping dump978 ADS-B UAT receiver…
May 28 15:37:52 piaware dump978-fa[622]: Reattached kernel driver
May 28 15:37:52 piaware dump978-fa[622]: Abnormal exit
May 28 15:37:52 piaware systemd[1]: dump978-fa.service: Main process exited, code=exited, status=1/FAILURE
May 28 15:37:52 piaware systemd[1]: dump978-fa.service: Failed with result ‘exit-code’.
May 28 15:37:52 piaware systemd[1]: Stopped dump978 ADS-B UAT receiver.
May 28 15:37:53 piaware systemd[1]: Started dump978 ADS-B UAT receiver.
May 28 15:37:53 piaware dump978-fa[1226]: raw-port: listening for connections on 0.0.0.0:30978
May 28 15:37:53 piaware dump978-fa[1226]: raw-port: listening for connections on [::]:30978
May 28 15:37:53 piaware dump978-fa[1226]: json-port: listening for connections on 0.0.0.0:30979
May 28 15:37:53 piaware dump978-fa[1226]: json-port: listening for connections on [::]:30979
May 28 15:37:53 piaware dump978-fa[1226]: Detached kernel driver
May 28 15:37:53 piaware dump978-fa[1226]: Found Rafael Micro R820T tuner
May 28 15:37:53 piaware dump978-fa[1226]: Reattached kernel driver
May 28 15:37:54 piaware dump978-fa[1226]: Detached kernel driver
May 28 15:37:54 piaware dump978-fa[1226]: Found Rafael Micro R820T tuner
May 28 15:37:54 piaware dump978-fa[1226]: Exact sample rate is: 2083333.135571 Hz
May 28 15:37:54 piaware dump978-fa[1226]: [R82XX] PLL not locked!
May 28 15:37:54 piaware dump978-fa[1226]: SoapySDR: using maximum manual gain 49.6 dB
May 28 15:37:54 piaware dump978-fa[1226]: SoapySDR: using stream setting buffsize=262144
May 28 15:37:54 piaware dump978-fa[1226]: Allocating 15 zero-copy buffers
May 28 15:37:57 piaware dump978-fa[1226]: [::]:30978: accepted a connection from [::1]:58582
May 28 15:38:22 piaware dump978-fa[1226]: [::]:30978: accepted a connection from [::1]:58584

from piaware

May 28 15:37:46 piaware piaware[476]: no new messages received in 3838 seconds, it might just be that there haven’t been any aircraft nearby but I’m going to try to restart everything, just in case…
May 28 15:37:47 piaware piaware[476]: faup978 exited with SIG SIGHUP
May 28 15:37:47 piaware piaware[476]: attempting to restart dump978…
May 28 15:37:47 piaware sudo[1188]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=list /usr/sbin/invoke-rc.d --query dump978-fa restart
May 28 15:37:47 piaware sudo[1190]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/invoke-rc.d --query dump978-fa restart
May 28 15:37:47 piaware sudo[1190]: pam_unix(sudo:session): session opened for user root by (uid=0)
May 28 15:37:47 piaware sudo[1190]: pam_unix(sudo:session): session closed for user root
May 28 15:37:47 piaware piaware[476]: attempting to restart dump978-fa using ‘systemctl --no-block try-restart dump978-fa.service < /dev/null’…
May 28 15:37:47 piaware sudo[1201]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=list /usr/bin/systemctl --no-block try-restart dump978-fa.service
May 28 15:37:47 piaware sudo[1203]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl --no-block try-restart dump978-fa.service
May 28 15:37:47 piaware sudo[1203]: pam_unix(sudo:session): session opened for user root by (uid=0)
May 28 15:37:47 piaware sudo[1203]: pam_unix(sudo:session): session closed for user root
May 28 15:37:47 piaware piaware[476]: dump978 restart appears to have been successful
May 28 15:37:57 piaware sudo[1244]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
May 28 15:37:57 piaware sudo[1244]: pam_unix(sudo:session): session opened for user root by (uid=0)
May 28 15:37:57 piaware sudo[1244]: pam_unix(sudo:session): session closed for user root
May 28 15:37:57 piaware piaware[476]: ADS-B data program ‘dump978-fa’ is listening on port 30978, so far so good
May 28 15:37:57 piaware piaware[476]: Starting faup978: /usr/lib/piaware/helpers/faup978 --connect localhost:30978
May 28 15:37:57 piaware piaware[476]: Started faup978 (pid 1253) to connect to dump978-fa
May 28 15:37:57 piaware piaware[476]: faup978(1253): Connecting to localhost:30978
May 28 15:37:57 piaware piaware[476]: faup978(1253): Connected to [::1]:30978
May 28 15:38:17 piaware piaware[476]: 0 msgs recv’d from dump978-fa (0 in last 5m); 0 msgs sent to FlightAware

1 Like

Was almost gonna suggest that first.
Intermittent issues are very often power problems indeed.

The phone charger isn’t really a good fit either, only power supplies i can really recommend are the Official Raspberry Pi power supplies.

2 Likes

That was the closest I had that would output 5 volt/2 amp. Hopefully since it isnt overclocked or overly taxed that it would be enough to get by for now.

1 Like

It’s obviously doing a better job than the previous one, just something to keep in mind.

1 Like

An update, it is still online and has tracked and sent UAT data to flightaware via the stats page. I would guess the power supply with the PI was a piece of junk. Got a new one ordered.

Thanks for the help in this thread

1 Like

This is the official power supply I use and recommend for Pi4

5.1V, 3.0A

Note:
It has a USB C plug, wont fit Pi3 without USB C to micro USB adapter

20200528_225003

 

1 Like