BETA UAT 978 MHz data sharing (DEPRECATED - DO NOT USE THIS PROCEDURE ANYMORE)

[Khan]

Hi all,

I am uploading a beta version of our UAT data sharing software. Do note that this version does not contain a decoder. Mostly, everyone who already has a UAT setup running, would probably already have dump978-fa installed, and assuming you do, please follow the installation procedure below.


1. Download the .deb package:

wget http://repo.feed.flightradar24.com/uat_reader_1.0.3_armhf.deb

2. Install it:

sudo dpkg -i uat_reader_1.0.3_armhf.deb

3. Run and sign up. You MUST sign up for a new UAT sharing key if you don’t already have one. This will be true for everyone using this software for the first time. DO NOT USE YOUR 1090MHz ADS-B sharing key:

sudo -u fr24 uat_reader

You will be asked to enter your email address, sharing key (leave it blank and press ENTER if you are running the software for the first time), and Coordinates (decimal format). A key will be created for you, saved in your config file as well as emailed to you.



4. This completes the setup and now restart the software:

sudo systemctl restart uat_reader

The log file is located at:
/var/log/uat_reader/uat_reader.log

The config file is located at:
/etc/uat_reader/uat_reader.conf

[markr468]

pi@piaware:~ $ sudo -u fr24 uat_reader
Could not open /var/log/uat_reader/uat_reader.log for writing!
21-04-26 18:37:49.448 [E] Couldn't open log file, exiting

Step 3 errors for me, exits the setup process...

Step 2 seemed to work.

pi@piaware:~ $ sudo dpkg -i uat_reader_1.0.0_armhf.deb
Selecting previously unselected package uat_reader.
(Reading database ... 51701 files and directories currently installed.)
Preparing to unpack uat_reader_1.0.0_armhf.deb ...
Unpacking uat_reader (1.0.0) ...
Setting up uat_reader (1.0.0) ...
useradd: user 'fr24' already exists
Enabling uat_reader service
Created symlink /etc/systemd/system/multi-user.target.wants/uat_reader.service → /etc/systemd/system/uat_reader.service.

[Khan]

Can you run the status command and share what it shows?

sudo systemctl status uat_reader

[markr468]

Here it is:

pi@piaware:~ $ sudo systemctl status uat_reader
● uat_reader.service - Flightradar24 UAT Reader
Loaded: loaded (/etc/systemd/system/uat_reader.service; enabled; vendor preset: enabled)
Active: inactive (dead)

Now here's the interesting part.....restart uat_reader:

pi@piaware:~ $ sudo systemctl restart uat_reader
pi@piaware:~ $ sudo systemctl status uat_reader
● uat_reader.service - Flightradar24 UAT Reader
Loaded: loaded (/etc/systemd/system/uat_reader.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-04-27 10:09:14 UTC; 6s ago
Process: 24960 ExecStartPre=/usr/lib/fr24/uat_reader/create_missing_directories.sh (code=exited, status=0/SUCCESS)
Main PID: 24966 (uat_reader)
Tasks: 2 (limit: 2062)
CGroup: /system.slice/uat_reader.service
└─24966 /usr/bin/uat_reader

Apr 27 10:09:14 piaware systemd[1]: Starting Flightradar24 UAT Reader...
Apr 27 10:09:14 piaware systemd[1]: Started Flightradar24 UAT Reader.

And when I check the /var/log/uat_reader/uat_reader.log (Notice the number of lines it's reading! Never asked for email, but it continues on and on)

Screenshot 2021-04-27 061041.jpg

Checking /etc/uat_reader/uat_reader.conf

File is blank.

And it's increasing the load average dramatically (Raspberry Pi 3b+) Usually around 1 to 1.2. Stuck in the loop with the sign up wizard, guess?
load average: 2.89, 2.63, 1.94

[Khan]

Run this command first

 sudo /usr/lib/fr24/create_missing_directories.sh

And then

 sudo -u fr24 uat_reader

See if it starts working like this.

[Khan]

Correction:

The link was pointing to the wrong file. Sorry about that. Please delete that one and download this .deb file

wget http://repo.feed.flightradar24.com/uat_reader_1.0.1_armhf.deb

NOTE: Anyone who has downloaded the uat_reader_1.0.0, please delete that and download version 1.0.1.

[markr468]

New version is successful. Had to change Step 2 to reflect the version # change to /uat_reader_1.0.1_armhf.deb

Thanks!!!

pi@piaware:~ $ sudo systemctl status uat_reader
● uat_reader.service - Flightradar24 UAT Reader
Loaded: loaded (/etc/systemd/system/uat_reader.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2021-04-27 11:00:08 UTC; 30s ago
Process: 9566 ExecStartPre=/usr/lib/fr24/uat_reader/create_missing_directories.sh (code=exited, status=0/SUCCESS)
Main PID: 9570 (uat_reader)
Tasks: 4 (limit: 2062)
CGroup: /system.slice/uat_reader.service
└─9570 /usr/bin/uat_reader

Apr 27 11:00:08 piaware systemd[1]: Starting Flightradar24 UAT Reader...
Apr 27 11:00:08 piaware systemd[1]: Started Flightradar24 UAT Reader.

[markr468]

So two things I've noticed so far;

1) STATS page doesn't show anything for this new Radar: NO RECENT DATA FOR THIS RADAR. uat_reader.log seems to indicate I'm feeding, and status uat_reader doesn't show any obvious errors

2) UAT aircraft I feed are still not shown on the FR24 website. They do show on other sites that I feed (FA, ADSBx, RB24) and do show on my local map.

At this point, is this indeed what's expected or is there something wrong on either end? Thanks!

[Khan]

Yes, this is expected at the moment. And it is good to hear that you are not seeing any errors in log file. We are of course working on getting both the points you have raised implemented asap.

[Khan]

markr468 If you download the updated version and install that, it will fix the stats issue. I have updated the original link. You can use the same method to download and install the newer version as done previously.

[markr468]

markr468 If you download the updated version and install that, it will fix the stats issue. I have updated the original link. You can use the same method to download and install the newer version as done previously.

Updated. Stats appear to be working. Thank you for updating that!

[SoNic67]

I have updated my alpha version too.

sudo systemctl status uat_reader
● uat_reader.service - Flightradar24 UAT Reader
Loaded: loaded (/etc/systemd/system/uat_reader.service; enabled; vendor prese
Active: active (running) since Fri 2021-05-14 18:32:29 EDT; 17s ago
Process: 14326 ExecStartPre=/usr/lib/fr24/create_missing_directories.sh (code=
Main PID: 14327 (uat_reader)
Tasks: 4 (limit: 2062)
CGroup: /system.slice/uat_reader.service
└─14327 /usr/bin/uat_reader

May 14 18:32:29 pi3 systemd[1]: Starting Flightradar24 UAT Reader...
May 14 18:32:29 pi3 systemd[14326]: uat_reader.service: Executable /usr/lib/fr24
May 14 18:32:29 pi3 systemd[1]: Started Flightradar24 UAT Reader.
lines 1-12/12 (END)

The website page says:

Online - No data

[markr468]

After a power outage, UAT Reader did not restart automatically (it tried and failed) . It also did not send "offline" emails so I only stumbled upon the UAT Reader being offline. A manual restart does the trick. The "ADSB" feeder restarted just fine. Maybe something in the logs will provide an answer? Provided those below.

STATUS

pi@piaware:~ $ sudo systemctl status uat_reader
● uat_reader.service - Flightradar24 UAT Reader
Loaded: loaded (/etc/systemd/system/uat_reader.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2021-08-11 14:17:39 UTC; 20h ago
Process: 903 ExecStartPre=/usr/lib/fr24/uat_reader/create_missing_directories.sh (code=exited, status=0/SUCCESS)
Process: 905 ExecStart=/usr/bin/uat_reader (code=exited, status=255/EXCEPTION)
Main PID: 905 (code=exited, status=255/EXCEPTION)

Aug 11 14:17:39 piaware systemd[1]: uat_reader.service: Service RestartSec=100ms expired, scheduling restart.
Aug 11 14:17:39 piaware systemd[1]: uat_reader.service: Scheduled restart job, restart counter is at 5.
Aug 11 14:17:39 piaware systemd[1]: Stopped Flightradar24 UAT Reader.
Aug 11 14:17:39 piaware systemd[1]: uat_reader.service: Start request repeated too quickly.
Aug 11 14:17:39 piaware systemd[1]: uat_reader.service: Failed with result 'exit-code'.
Aug 11 14:17:39 piaware systemd[1]: Failed to start Flightradar24 UAT Reader.

LOG shows multiple errors like this. Restart attempts stop after a few of these.

2021-08-11 14:17:39.781 | [feed][e] Couldn't resolve host name
2021-08-11 14:17:39.781 | [e]Could not retrieve configuration from Flightradar24: Request failed, code
2021-08-11 14:17:39.785 | 21-08-11 14:17:39.781 [E] Couldn't get network configuration, exiting

MANUALLY RESTART UAT READER (all is well it appears).

pi@piaware:~ $ sudo systemctl status uat_reader
● uat_reader.service - Flightradar24 UAT Reader
Loaded: loaded (/etc/systemd/system/uat_reader.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2021-08-12 10:29:54 UTC; 52s ago
Process: 18074 ExecStartPre=/usr/lib/fr24/uat_reader/create_missing_directories.sh (code=exited, status=0/SUCCESS)
Main PID: 18076 (uat_reader)
Tasks: 5 (limit: 2059)
CGroup: /system.slice/uat_reader.service
└─18076 /usr/bin/uat_reader

Aug 12 10:29:54 piaware systemd[1]: Starting Flightradar24 UAT Reader...
Aug 12 10:29:54 piaware systemd[1]: Started Flightradar24 UAT Reader.

pi@piaware:~ $ tail -n 30 /var/log/uat_reader/uat_reader.log
2021-08-12 10:29:54.995 | [n]KCAK3@185.218.24.53:8099/UDP
2021-08-12 10:29:54.996 | [n]connecting
2021-08-12 10:29:54.996 | 21-08-12 10:29:54.991 [I] [stats]Stats thread started
2021-08-12 10:29:54.996 | 21-08-12 10:29:54.995 [I] UAT Reader client started on port 30979
2021-08-12 10:29:54.996 |
2021-08-12 10:29:54.996 | 21-08-12 10:29:54.991 [I] defined 2 servers
2021-08-12 10:29:55.136 | [n]connected via UDP (fd 11)
2021-08-12 10:29:55.136 | [n]working
2021-08-12 10:30:25.140 | [n]ping 1
2021-08-12 10:30:26.140 | [n]syncing stream result: 1

[spiltpickle]

I've installed the 1.0.3 version as well and am getting the same as SoNic67. The stats page says online but 'no recent data for this radar'. The uat_reader.log file is showing I am receiving messages, about 8 per second according to dump978. status on the service shows active (running)

Is there any way to limit the logging? Logging every message might be ultimately hurting the SD card. I've mounted a small ram disk at /var/log/uat_reader for now.

[rjanke]

I just added FR24 feeding to my Raspberry Pi 4B running the FA PiAware 6 image - released last week. When I added FR24 I had to go to <pi ip>:8754 to adjust the Receiver to AVR (TCP) for my 1090 antenna - the status page at FR24 was reporting that I was Online - No Data and that fixed it.

On this same Pi I have a second dongle for UAT 978, which works perfectly well with FA but is still reporting the same "Online - No Data" on the status page. Is there another port I should place after my Pi's IP address to access the setting for UAT so that I can change the receiver type there?

UPDATE (12 SEPT 2021): I have gone into the uat_reader.log file and it appears to be capturing data from a/c, but I can't get it to pass that along to FR24. The status still reads "Online - No Data" on the website.

UPDATE (13 SEPT 2021): NEVER MIND! Thanks to Muazzam at FR24 support, it turns out that I am set up correctly. I knew that there was very little UAT traffic in my area, but was concerned about the No Data message. Muazzam confirmed that there was some data fed yesterday. Consider this case CLOSED.

Thanks!