It is hard for me to troubleshoot or test dump978 due to the fact I do not have an antenna up in the air receiving much as far as UAT data is concerned. That and the fact I did not write it and have very little experience actually running it besides as an after thought in the background collecting no data makes it hard for me to support dump978 on an application level. However it is my understanding uat2esnt is used to convert UAT messages to Mode S messages. These messages are then in turn sent to dump1090 via port 30001 which listen for AVR format input using Netcat. That being said there are a couple things you can check.
Lets make sure itās not a configuration issue.
First off as mentioned earlier confirm the file /var/log/dump978.log exists and check there are no errors reported there.
Confirm the uat2esnt process is running and a Netcat process which looks like ā/bin/nc -q1 127.0.0.1 30001ā is running. (āps -aux | grep uat2esntā and āps -aux | grep ncā)
Make sure the setting RAW_INPUT_PORT located in the file /etc/default/dump1090-mutability is set to 30001.
You might want to make sure you did not assign port 30001 to another application such as PiAware as well which will cause dump1090 to be unable to use port 30001.
You could also comment out the line in /etc/rc.local that executes the file dump978-maint.sh then reboot so dump978 is not running and manually startup dump978 using the directions Obj has made available in the dump978 GitHub repository located at github.com/mutability/dump978 to see if any more information can been seen regarding a possible issue. (BTW be sure to add -d <YOUR_RTL-SDR_DEVICE_ID> to the line used to execute dump978 if you are using two dongles.)
Any information or errors would be helpful. If you see any errors reported in the dump978 log or even syslog would be helpful. Itās hard to blindly troubleshoot an issue hence the reason I am offering some basics to go over first. Let me know how it goes and if you find anything.