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

[loganschapker]

Any update on when this will be final and UAT traffic will display publicly?

[cyclosaur]

Any updates since beta 1.0.3 or if/when the UAT data might be displayed on the map? I like the fr24 app since it opens quickly but either UAT is not getting displayed or my UAT beta feeder isn't working. Heard a plane overhead and opened the app. It showed a plane and said it was using Satellite ADS-B, but it gave a tail number which displayed the UAT plane on FA and ADSBX.

[abcd567]

@Marc_Compere

Did you install either dum978-fa or dump978-rb?

The Fr24 uat_reader does not use the 978 MHz receiver directly. It is dump978 which uses 978 Mhz receiver and produces aircraft data in json format. The uat_reader grabs this json data and sends to FR24 server.

If there is no dump978 installed, there will be no json data available, and uat_reader will give json error message.

[Marc_Compere]

Hello, I've had a 1090 receiver working and reporting properly to FlightRadar24. It's a Nooelec NESDR SMArTee v2 Bundle.

The instructions I followed were for the Raspberry Pi here. That installed great and has been working for a few months.

I just got a Red Radarbox 978MHz ADS-B receiver (and antenna) and tried following the instructions from Khan on this thread, page 1.

The package install of uat_reader_1.0.3_armhf.deb went fine, although it reported uat_reader (1.0.0) during installation.

I unplugged the 1090 usb device and plugged in the 978 device, and ran the registration and setup command: sudo -u fr24 uat_reader

It walked through the email, the airport, lat, lon, elevation, then barfs with this:

2022-03-26 20:40:54.196 | $:terminate called after throwing an instance of 'nlohmann::detail::type_error'
2022-03-26 20:40:54.196 | what(): [json.exception.type_error.302] type must be string, but is null
Aborted

Any tips? Something is failing on simple textual inputs with a json error.

Raspbian 10 Buster. Rpi3. python 3.7.3

[abcd567]

Khan
Is there a way to stop logging of uat_reader? It keeps on writing the log to following file. I am worried about life of my microSD card:

/var/log/uat_reader/uat_reader.log

I added logmode="0" in file "/etc/uat_reader/uat_reader.conf" and restarted uat_reader, but logging did not stop.

[abcd567]

I recently got a 978 receiver and antenna and want to share that data with my 1090 data. Are the steps the same that were listed on page 1?

I have piaware running with version 7.1.

(1) Yes, the steps are same as in the 1st post of this thread.
(2) FR24 uat data sharer works OK with dump978-fa version 7.1

[orangegecko]

I recently got a 978 receiver and antenna and want to share that data with my 1090 data. Are the steps the same that were listed on page 1? If not, can someone post precise commands and instructions to do so? I have piaware running with version 7.1.

Thanks.

[wiedehopf]

UAT / 978 is only used in the US by some of the smaller aircraft.

[sadeedp]

Hi,
Could you please explain the advantage of 978 MHz data sharing compared to 1090mhz feeding

[herren]

Any chances of getting an amd64 version of this?

[jackal]

Every time I reboot my Pi, uat_reader fails to start. Looks like it has trouble resolving DNS and times out:

2022-01-19 22:38:09.627 | [feed][e] Couldn't resolve host name
2022-01-19 22:38:09.627 | [feed][e] Couldn't resolve host name
2022-01-19 22:38:10.395 | [feed][e] Couldn't resolve host name
2022-01-19 22:38:10.395 | [e]Could not retrieve configuration from Flightradar24: Request failed, code
2022-01-19 22:38:10.888 | [feed][e] Couldn't resolve host name
2022-01-19 22:38:10.888 | [e]Could not retrieve configuration from Flightradar24: Request failed, code
2022-01-19 22:38:10.894 | 22-01-19 22:38:10.894 [E] Local time: 2022-01-19 22:38:10 -0600
2022-01-19 22:38:10.895 | 22-01-19 22:38:10.894 [E] GMT+0 time: 2022-01-20 04:38:10 -0600
2022-01-19 22:38:10.895 | 22-01-19 22:38:10.890 [E] Your machine should be set as GMT+0 time zone!
2022-01-19 22:38:10.895 | 22-01-19 22:38:10.890 [W] Time zone is not set to GMT+0
2022-01-19 22:38:10.895 | 22-01-19 22:38:10.894 [E] Couldn't get network configuration, exiting

This could be because my Pi is also serving as a caching BIND 9 DNS server, so uat_reader may be opening before BIND is fully loaded and operational.

If I remember or notice that my UAT feeder is offline, I can cure it by manually issuing a sudo systemctl restart uat_reader and everything works swimmingly. It's just that initial startup on boot that's problematic.

Any way to either increase the number of retries or delay starting uat_reader until after the system is up and stable? (I don't have this issue with other UAT packages like FA's and ADSBX's.)

[cyclosaur]

Same result here, searched for current UAT aircraft on feeder web interface and none were showing up on fr24 webpage. Feeder statistics for UAT feeder, just missing the data conversion into the main fr 24 map.

[speedycab]

I see that logging as well. However, I do not see a single locally tracked UAT aircraft on the main page when I filter for my radar. Instead the logged aircraft are simply not visible in FR24 (some but not all are tracked by MLAT).

[cyclosaur]

After reinstalling v1.03 seeing results in sharing statistics

[cyclosaur]

Correction: they all say v1.0.0 when installed
-rw-r--r-- 1 pi pi 2805346 Apr 27 06:34 uat_reader_1.0.1_armhf.deb
-rw-r--r-- 1 pi pi 2805346 Apr 27 06:34 uat_reader_1.0.1_armhf.deb.1
-rw-r--r-- 1 pi pi 2851292 May 12 08:10 uat_reader_1.0.2_armhf.deb
-rw-r--r-- 1 pi pi 2850076 Jun 8 04:55 uat_reader_1.0.3_armhf.deb
-rw-r--r-- 1 pi pi 2850076 Jun 8 04:55 uat_reader_1.0.3_armhf.deb.1
pi@c121746:~ $ sudo dpkg -i uat_reader_1.0.2_armhf.deb
(Reading database ... 50799 files and directories currently installed.)
Preparing to unpack uat_reader_1.0.2_armhf.deb ...
Unpacking uat_reader (1.0.0) over (1.0.0) ...
Setting up uat_reader (1.0.0) ...
useradd: user 'fr24' already exists
Enabling uat_reader service
pi@c121746:~ $ sudo dpkg -i uat_reader_1.0.3_armhf.deb
(Reading database ... 50799 files and directories currently installed.)
Preparing to unpack uat_reader_1.0.3_armhf.deb ...
Unpacking uat_reader (1.0.0) over (1.0.0) ...
Setting up uat_reader (1.0.0) ...
useradd: user 'fr24' already exists
Enabling uat_reader service
pi@c121746:~ $ sudo dpkg -i uat_reader_1.0.1_armhf.deb
(Reading database ... 50799 files and directories currently installed.)
Preparing to unpack uat_reader_1.0.1_armhf.deb ...
Unpacking uat_reader (1.0.0) over (1.0.0) ...
Setting up uat_reader (1.0.0) ...
useradd: user 'fr24' already exists
Enabling uat_reader service
pi@c121746:~ $ sudo dpkg -i uat_reader_1.0.3_armhf.deb
(Reading database ... 50799 files and directories currently installed.)
Preparing to unpack uat_reader_1.0.3_armhf.deb ...
Unpacking uat_reader (1.0.0) over (1.0.0) ...
Setting up uat_reader (1.0.0) ...
useradd: user 'fr24' already exists
Enabling uat_reader service