AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: foehammer on February 26, 2022, 08:41:23 PM
-
Hello,
I already had a Flight Aware 1080 dongle feeding Flight Aware, Airnav Radar Box, ADSB Exchange etc.
I recently received my AirNav Radabox UAT 978 dongle and antenna and added it to my RPi 4, following the instructions on how to change the serial numbers one dongle at a time. I was able to get Flight Aware to receive both ADSB and UAT data with a few config file changes to specify which device to use for what protocol.
I cannot for the life of me get rbfeeder to take in both ADSB and UAT. I've found some forum posts from 2020 stating that you can only do one or the other. I was hoping that is outdated info seeing as Flight Aware supports it.
My rbfeeder.ini file, with certain data redacted.
client]
network_mode=true
log_file=/var/log/rbfeeder.log
key=XXXXXXXXXXXXXXXXXXX
sn=XXXXXXXXX
lat=XXXXXXX
lon=XXXXXXXXX
alt=269
sat_used=0
sat_visible=0
[network]
mode=beast
external_port=30005
external_host=192.168.X.XXX
[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.5 /usr/bin/mlat-client
[dump978]
dump978_enabled=true
dump978_port=30979
-
The forum posts will have been refering to are regarding using the V6 software and UAT. You are feeding RB on the web so no issues with that
Unfortunately I know very little about Pi's so cant help but have a look at
https://forum.radarbox24.com/index.php?topic=104911.msg486421#msg486421
https://forum.radarbox24.com/index.php?topic=104861.msg483961#msg483961
https://forum.radarbox24.com/index.php?topic=103271.msg444091#msg444091
Hopefully abcd123 will be around soon to guide you
Alan
-
Thank you for the response Alan. Those were helpful links. I believe I may have created an issue by having both dump978-fa and dump978-rb enabled, both trying to use the same dongle.
I've disabled dump798-rb for now since I had seen UAT tracks on FA. I have also tried adding the undocumented dump978_port=30979 flag to rbfeeder.ini.
Now I wait for UAT tracks. I need the snow to melt off the roof so I can take the antenna out of the attic and onto the roof.
-
That did the trick!
Thank you for your help, and for the 978 dongle and antenna!
-
Great, well done
Alan
-
I ran into a similar problem.
I was successfully feeding only 1090 to ADSBexchange and radarbpox24. I received the RB24 978 USB stick & antenna, added the HW and SW to the raspberry PI and all feeds stopped working. If I disconnect the 978 USB stick, the 1090 feed to ADSBexchange works again but still nothing being sent to RB24.
Read several threads here and this is what I've got now for rbfeeder.ini plus some output Any help would be greatly appreciated.
=============================================================================
cat /etc/rbfeeder.ini
[client]
network_mode=false
log_file=/var/log/rbfeeder.log
key=<redacted>
sn=<redacted>
lat=<redacted>
lon=<redacted>
alt=<redacted>
sat_used=0
sat_visible=0
[network]
mode=beast
external_port=30005
external_host=127.0.0.1
[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.5 /usr/bin/mlat-client
[dump978]
dump978_enabled=true
==================================================================================
pi@raspberrypi:/etc/default $ nc localhost 28380
pi@raspberrypi:/etc/default $ sudo netstat -anp|grep -w 28380
pi@raspberrypi:/etc/default $
=====================================================================
Excerpt from /var/log/rbfeeder.log. At [2022-03-01 01:01:20] is when I restarted everything and the feeds stopped.
[2022-03-01 00:58:44] ******** Statistics updated every 30 seconds ********
[2022-03-01 00:58:44] Packets sent in the last 30 seconds: 0, Total packets sent since startup: 0
[2022-03-01 00:58:44] Data sent: 3.8 KB
[2022-03-01 00:58:44] Data received: 1.4 KB
[2022-03-01 00:59:15] ******** Statistics updated every 30 seconds ********
[2022-03-01 00:59:15] Packets sent in the last 30 seconds: 0, Total packets sent since startup: 0
[2022-03-01 00:59:15] Data sent: 3.8 KB
[2022-03-01 00:59:15] Data received: 1.4 KB
[2022-03-01 00:59:46] ******** Statistics updated every 30 seconds ********
[2022-03-01 00:59:46] Packets sent in the last 30 seconds: 0, Total packets sent since startup: 0
[2022-03-01 00:59:46] Data sent: 3.8 KB
[2022-03-01 00:59:46] Data received: 1.4 KB
[2022-03-01 01:01:20] Starting RBFeeder Version 0.4.3 (build 20210909231001)
[2022-03-01 01:01:20] Using configuration file: /etc/rbfeeder.ini
[2022-03-01 01:01:20] Network-mode disabled. Using local dongle.
[2022-03-01 01:01:20] System: raspberry
[2022-03-01 01:01:20] Start date/time: 2022-03-01 01:01:20
[2022-03-01 01:01:20] Socket for ANRB created. Waiting for connections on port 32088
[2022-03-01 01:01:21] Connection established.
[2022-03-01 01:01:21] Connection with RadarBox24 server OK! Key accepted by server.
[2022-03-01 01:01:21] Your station serial number is: <redacted>
[2022-03-01 01:01:23] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:01:28] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:01:33] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:01:38] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:01:43] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:01:48] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:01:50] ******** Statistics updated every 30 seconds ********
[2022-03-01 01:01:50] Packets sent in the last 30 seconds: 0, Total packets sent since startup: 0
[2022-03-01 01:01:50] Data sent: 1.6 KB
[2022-03-01 01:01:50] Data received: 1.0 KB
[2022-03-01 01:01:53] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:01:58] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:02:03] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:02:08] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:02:13] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:02:18] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:02:21] ******** Statistics updated every 30 seconds ********
[2022-03-01 01:02:21] Packets sent in the last 30 seconds: 0, Total packets sent since startup: 0
[2022-03-01 01:02:21] Data sent: 2.1 KB
[2022-03-01 01:02:21] Data received: 1.1 KB
[2022-03-01 01:02:23] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:02:28] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:02:33] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:02:38] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:02:43] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:02:48] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
[2022-03-01 01:02:52] ******** Statistics updated every 30 seconds ********
-
I note that at the very top of your ini file you have
cat /etc/rbfeeder.ini
[client]
network_mode=false
change to network mode=true
Alan
-
Thanks.
That fixed the problem of getting 1090 fed to both adsb and radarbox24 when the 978 stick is *not* plugged in.
If I plug in the 978 stick, nothing is sent to either site.
-
Have you renumbered the sticks 0 and 1
Alan
-
You did not give very important information that
(1) which image you have written to your microSD card? There are many images such as:
- Raspberry Pi OS image
- Piaware sd card image
- FR24's Pi24 image
- Adsbexchsanqe iimage
(2) which decoders you have installed. What is the output of these commands?
apt-cache policy dump1090-fa
apt-cache policy dump978-rb
apt-cache policy dump978-fa
apt-cache policy readsb
.
-
If both 1090 mhz and 978 mhz decoder are installed and two dongles are pluggex in, one with 1090 mhz filter and antenna, other with 978 mhz filter and antenna.
If configuration is not done properly, it is very likely that at startup the dump1090 grabs 978 dongle and dump978 grabs 1090 dongle. This will result in very poor performance (even zero) for both frequencies.
Also there are following decoders available. The configuration varies with decoder installed. With improper configuration either or both 1090 & 978 may fail
For 1090 mhz:
- dump1090-mutability
- dump1090-fa
- dump1090
- readsb
- modesdeco2
For 978 mhz:
- dump978-rb
- dump978-fa
- dump978
CONCLUSION: Which decoders are installed must be known exactly, and configuration done accordingly.
.
-
Thanks for the advice abc
Alan
-
Thanks for the advice abc
Alan
Hi Alan,
Because of multiple decoders, and because of multiple images using different decoders, situation is messy.
Unfortunately the users dont specify what OS image they have written to their microSD card and what decoders are installed. They come up with problems without mentioning anything or very little about their installation. As a result it becomes impossible to diagnose and cure the problem. When they are asked to issue diagnostic commands and post the output, many just ignore it. They are like a patient who comes to Doctor, says I have pain in abdomen area (which can be due to indigestion, constipation, pulled or strained muscles, or appendicitis or kidney stone etc), and asks Doctor to give him prescription without telling anything more. When Doctor tells him to take the blood and urine test and ultrasound, he ignores it.
Regards,
ab cd
-
If configuration is not done properly, it is very likely that at startup the dump1090 grabs 978 dongle and dump978 grabs 1090 dongle. This will result in very poor performance (even zero) for both frequencies.
Hi Alan
I forgot to mention that the very basic technique with all types of decoders to prevent situation described above and force dump1090 to grab only the donglee with 1090 antenna and 1099 filter is to serialize the 1090 dongle, and then add this number to configuration of dump1090. Numbers, or alphabets, or a combination of alphabets and number can be used (maximum 8). However general practice is to use either 8-digit 00001090 (Flightaware) or simply 1090 (Adsbexchange) without leading zeros .
Serializing just 1090 mhz dongle is not enough. The 978 mhz dongle should also be serialized with a different serial number, and this number added to configuration of dump978. Numbers, or alphabets, or a combination of alphabets and number can be used (maximum 8). However general practice is to use either 8-digit 00000401 (Radarbox24), or 8-digit 00000978 (Flightaware) or simply 978 without leading zeros (Adsbexchange).
Regards,
ab cd
-
Thanks abcd, all understood. That is why I asked if the sticks had been re-numbered. Can you provide a simple guide for users as to how that can be done
Alan
-
Thanks abcd, all understood. That is why I asked if the sticks had been re-numbered. Can you provide a simple guide for users as to how that can be done
Alan
It is two-fold action:
- serialize dongles
- configure dump978 matching with the dongle's serial number
It requires detailed instructions, which varies with type of installation. Please see below:
(1) If Raspberry Pi OS is used and on it Radarbox24's dump978-rb is installed, follow this guide:
https://www.radarbox.com/flightstick978/guide
(2) If Adsbexchange image is used, it has dump978-fa and "readsb" (1090 mhz decoder) pre-installed, use following guide:
https://www.adsbexchange.com/how-to-feed/adsbx-custom-pi-image/
Scroll down to item:
978 for US based 2 SDR receivers
(3) If Flightaware's Piaware SD card image is used, it has dump978-fa pre installed. Follow this guide:
https://discussions.flightaware.com/t/how-to-install-and-configure-piaware-5-0-sd-card-image-quickstart-guide/48262
Scroll down to items
5 - Serialize dongles if using UAT 978
6 - Configure UAT 978
(4) If Raspberry Pi OS is used and on it dump1090-fa and dump978-fa are installed, use this guide
https://discussions.flightaware.com/t/outdated-package-install-of-piaware-6-1-on-bullseye-32-bit-64-bit/80272
Scroll down to item:
STEP-6: configure dump978-fa (do this step only if you have installed dump978-fa, otherwise skip this step)
.
-
Many thanks abcd
Alan
-
You did not give very important information that
(1) which image you have written to your microSD card? There are many images such as:
- Raspberry Pi OS image
- Piaware sd card image
- FR24's Pi24 image
- Adsbexchsanqe iimage
(2) which decoders you have installed. What is the output of these commands?
apt-cache policy dump1090-fa
apt-cache policy dump978-rb
apt-cache policy dump978-fa
apt-cache policy readsb
.
Been out of town. Here's the output:
pi@raspberrypi:/boot $ uname -a
Linux raspberrypi 4.19.118-v7+ #1311 SMP Mon Apr 27 14:21:24 BST 2020 armv7l GNU/Linux
pi@raspberrypi:~ $ apt-cache policy dump1090-fa
N: Unable to locate package dump1090-fa
pi@raspberrypi:~ $ apt-cache policy dump978-rb
dump978-rb:
Installed: 1.0.1+buster
Candidate: 1.0.1+buster
Version table:
*** 1.0.1+buster 500
500 https://apt.rb24.com buster/main armhf Packages
100 /var/lib/dpkg/status
pi@raspberrypi:~ $ apt-cache policy dump978-fa
N: Unable to locate package dump978-fa
pi@raspberrypi:~ $ apt-cache policy readsb
readsb:
Installed: 3.8.4~dev
Candidate: 3.8.4~dev
Version table:
*** 3.8.4~dev 100
100 /var/lib/dpkg/status
pi@raspberrypi:~ $
==========================================
Got the rtl_eeprom working. Here's what I did:
sudo systemctl stop readsb
With only 978 dongle attached:
rtl_eeprom
Found 1 device(s):
0: Generic RTL2832U OEM
Using device 0: Generic RTL2832U OEM
Detached kernel driver
Found Rafael Micro R820T tuner
Current configuration:
__________________________________________
Vendor ID: 0x0bda
Product ID: 0x2838
Manufacturer: Realtek
Product: RTL2838UHIDIR
Serial number: 00000001
Serial number enabled: yes
IR endpoint enabled: yes
Remote wakeup enabled: no
__________________________________________
Reattached kernel driver
pi@raspberrypi:~ $ !1112
sudo rtl_eeprom -d 0 -p UAT_978 -s 00000401
Found 1 device(s):
0: Generic RTL2832U OEM
Using device 0: Generic RTL2832U OEM
Detached kernel driver
Found Rafael Micro R820T tuner
Current configuration:
__________________________________________
Vendor ID: 0x0bda
Product ID: 0x2838
Manufacturer: Realtek
Product: UAT_978
Serial number: 00000401
Serial number enabled: yes
IR endpoint enabled: yes
Remote wakeup enabled: no
__________________________________________
New configuration:
__________________________________________
Vendor ID: 0x0bda
Product ID: 0x2838
Manufacturer: Realtek
Product: UAT_978
Serial number: 00000401
Serial number enabled: yes
IR endpoint enabled: yes
Remote wakeup enabled: no
__________________________________________
Write new configuration to device [y/n]? y
Configuration successfully written.
Please replug the device for changes to take effect.
Reattached kernel driver
Then with only 1090 dongle installed:
rtl_eeprom
Found 1 device(s):
0: Generic RTL2832U OEM
Using device 0: Generic RTL2832U OEM
Detached kernel driver
Found Rafael Micro R820T tuner
Current configuration:
__________________________________________
Vendor ID: 0x0bda
Product ID: 0x2838
Manufacturer: Realtek
Product: RTL2838UHIDIR
Serial number: 00000001
Serial number enabled: yes
IR endpoint enabled: yes
Remote wakeup enabled: no
__________________________________________
Reattached kernel driver
pi@raspberrypi:~ $ sudo rtl_eeprom -d 0 -p ADSB_1090 -s 00000010
Found 1 device(s):
0: Generic RTL2832U OEM
Using device 0: Generic RTL2832U OEM
Detached kernel driver
Found Rafael Micro R820T tuner
Current configuration:
__________________________________________
Vendor ID: 0x0bda
Product ID: 0x2838
Manufacturer: Realtek
Product: RTL2838UHIDIR
Serial number: 00000001
Serial number enabled: yes
IR endpoint enabled: yesh
Remote wakeup enabled: no
__________________________________________
New configuration:
__________________________________________
Vendor ID: 0x0bda
Product ID: 0x2838
Manufacturer: Realtek
Product: ADSB_1090
Serial number: 00000010
Serial number enabled: yes
IR endpoint enabled: yes
Remote wakeup enabled: no
__________________________________________
Write new configuration to device [y/n]? y
Configuration successfully written.
Please replug the device for changes to take effect.
Reattached kernel driver
pi@raspberrypi:~ $ rtl_eeprom
Found 1 device(s):
0: Generic RTL2832U OEM
Using device 0: Generic RTL2832U OEM
Detached kernel driver
Found Rafael Micro R820T tuner
Current configuration:
__________________________________________
Vendor ID: 0x0bda
Product ID: 0x2838
Manufacturer: Realtek
Product: ADSB_1090
Serial number: 00000010
Serial number enabled: yes
IR endpoint enabled: yes
Remote wakeup enabled: no
__________________________________________
Reattached kernel driver
sudo poweroff
When power came back up and both 1090 and 978 dongles inserted no feed from either dongle.
Did another sudo poweroff, unplugged 978 dongle, left 1090 in and restarted. Now the 1090 is working again but there's still something wrong when both 1090 and 978 are plugged in.
-
Hi Vantage
Good that you have serialized the dongles, 978 one with 00000401 and 1090 one with 00000010.
The dump978-rb software is pre-configured for serial number 00000401, so your 978 dongle and dump978-rb have mathing setting and should work OK.
Did you configure readsb to match serial number 00000010 0f 1090 dongle?
.
-
No. Here's the procedure I was given:
I think that the ADS-B and UAT flightsticks may have mixed up during the process which is why there is no data, so I suggest the following steps:
1 - Physically disconnect the ADS-B stick and and leave the UAT one in the Raspberry Pi
2 - Run the command to correctly identify it: sudo rtl_eeprom -d 0 -p UAT_978 -s 00000401
3 - Disconnect the UAT stick and replace it with the the ADS-B one
4 - Run the command to correctly identify it: sudo rtl_eeprom -d 0 -p ADSB_1090 -s 00000010
5 - Connect the UAT dongle back and restart the Pi - it should work as soon as it comes up.
Obviously it didn't work as it came up. If you'll point me to the procedure to configure readsb, I'll try it.
-
No. Here's the procedure I was given:
I think that the ADS-B and UAT flightsticks may have mixed up during the process which is why there is no data, so I suggest the following steps:
1 - Physically disconnect the ADS-B stick and and leave the UAT one in the Raspberry Pi
2 - Run the command to correctly identify it: sudo rtl_eeprom -d 0 -p UAT_978 -s 00000401
3 - Disconnect the UAT stick and replace it with the the ADS-B one
4 - Run the command to correctly identify it: sudo rtl_eeprom -d 0 -p ADSB_1090 -s 00000010
5 - Connect the UAT dongle back and restart the Pi - it should work as soon as it comes up.
Obviously it didn't work as it came up. If you'll point me to the procedure to configure readsb, I'll try it.
The procedure you followed is OK, but is half-baked, i.e. it told you to serialize two dongles differently, BUT did not tell you the other equally important part, that is how to configure dump978-rb and readsb to match these serial numbers.
Since dump978-rb is pre-configured for serial number 00000401, and you serialized the dongle with same number 00000401, they matched.
However in case of readsb, it is configured for --device 0, which does NOT match 1090 dongle's serial 00000010 which you have assigned. This caused mismatch and failure. You have to edit the readsb config file and change --device 0 to --device 00000010
After changes, Save file, then REBOOT the RPi.
pi@raspberrypi:~ $ sudo nano /etc/default/readsb
# readsb configuration
# This is sourced by /etc/systemd/system/default.target.wants/readsb.service as
# daemon startup configuration.
RECEIVER_OPTIONS="--device 0 --device-type rtlsdr --gain -10 --ppm 0"
DECODER_OPTIONS="--max-range 360 --write-json-every 1"
NET_OPTIONS="--net --net-heartbeat 60 --net-ro-size 1250 --net-ro-interval 0.05 --net-ri-port 30001 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005"
JSON_OPTIONS="--json-location-accuracy 2 --range-outline-hours 24"
-
That was it. Thanks.
One things that's conspicuos by its absence: When I do
ps -ef|grep 978
no processes show up.
The 978 SW is installed:
$ apt-cache policy dump978-rb
dump978-rb:
Installed: 1.0.1+buster
Candidate: 1.0.1+buster
Version table:
*** 1.0.1+buster 500
500 https://apt.rb24.com buster/main armhf Packages
100 /var/lib/dpkg/status
--------------------------------------------------------------------
cat dump978-rb
# dump978-rb configuration
# This is sourced by /usr/share/dump978-rb/start-dump978-rb as a
# shellscript fragment.
# dump978-rb won't automatically start unless ENABLED=yes
ENABLED=yes
RECEIVER_OPTIONS="--sdr driver=rtlsdr,serial=00000401 --sdr-auto-gain --format CS8"
DECODER_OPTIONS=""
NET_OPTIONS="--raw-port 30978 --json-port 28380"
Thoughts?
-
That was it. Thanks.
Glad to know your problem is solved :)
One things that's conspicuos by its absence: When I do
ps -ef|grep 978
no processes show up.
The 978 SW is installed:
... ... ...
... ... ...
Thoughts?
No idea why.
I have "dum978-fa" and it's map "skyaware978" installed, and get this output:
pi@raspberrypi:~ $ ps -ef | grep 978
dump978 528 1 7 13:36 ? 00:00:28 /usr/bin/dump978-fa --sdr driver=rtlsdr,serial=00000978 --format CS8 --raw-port 30978 --json-port 30979
skyaware 558 1 0 13:36 ? 00:00:00 /usr/bin/skyaware978 --connect localhost:30978 --reconnect-interval 30 --history-count 120 --history-interval 30 --lat 43.5xxxx --lon -79.6xxxx --json-dir /run/skyaware978
piaware 1332 970 0 13:36 ? 00:00:00 /usr/lib/piaware/helpers/faup978 --connect localhost:30978
pi 5972 2405 0 13:42 pts/0 00:00:00 grep --color=auto 978
pi@raspberrypi:~ $
.
-
I think I've got the 978 SW finally running. This seemed to do the trick. Thanks to abcd567.
sudo apt update
sudo apt install --reinstall dump978-rb
sudo systemctl restart dump978-rb
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
17808 dump978 15 -5 74260 15532 6104 S 28.5 1.6 242:37.55 dump978-rb
470 readsb 15 -5 30544 6900 2468 S 20.2 0.7 803:23.41 readsb
409 root 20 0 113300 14656 5220 S 2.0 1.5 54:38.47 rbfeeder
542 root 20 0 17140 9872 5560 S 1.7 1.0 32:48.25 mlat-client
1231 adsbexc+ 20 0 16484 9392 5548 S 1.7 1.0 39:05.76 python3
1232 adsbexc+ 20 0 34840 3636 2284 S 1.0 0.4 26:12.08 feed-adsbx
One question for those in the USA: Are you getting any 978 detections? I seem to be getting none.
Messages
2022-03-14 2022-03-15 2022-03-16
ADS-B 5,077,033 5,540,079 3,710,369
With Position 2,323,795 2,521,196 1,640,244
MLAT
29,303 (0.6%)
41,325 (0.7%)
35,050 (0.9%)
UAT
0 (0.0%)
0 (0.0%)
0 (0.0%)
Total 5,086,732 5,550,287 3,714,610
Bandwidth 153.58 MB 166.89 MB 110.02 MB
-
I was looking at the UAT station list and while they are mostly ADSB, there are UAT plots out there
Whats your station number?
Alan
-
EXTRPI010179
-
To check if uat planes are being detected:
(1) Install netcat
sudo apt install netcat
Now give following command and wait for some time till UAT978 equipped plane are detected. These will be displayed:
To STOP, press Ctrl and C keys together
Raw data format
nc 127.0.0.1 30978 &
.
-
Installed and ran nc command but don't know how to interpret results. I had to delete a lot of nc output otherwise forum SW thought was spam.
~ $ sudo apt install netcat
Reading package lists... Done
Building dependency tree
Reading state information... Done
netcat is already the newest version (1.10-41.1).
0 upgraded, 0 newly installed, 0 to remove and 287 not upgraded.
$ nc 127.0.0.1 30978 &
[1] 5269
-0aaa1b392ee6b960d58c0df811a80ae07f09e5bc9d05c40bc295c2a0000db0000000;rssi=1.9;t=1647462975.205;
Don't know if this is significant:
pi@raspberrypi:~ $ sudo systemctl status dump978-rb
● dump978-rb.service - dump978 ADS-B UAT receiver
Loaded: loaded (/lib/systemd/system/dump978-rb.service; disabled; vendor preset: enabled)
Active: active (running) since Wed 2022-03-16 13:33:40 MST; 19min ago
Docs: https://www.radarbox.com
Main PID: 3444 (dump978-rb)
Tasks: 4 (limit: 2200)
Memory: 12.6M
CGroup: /system.slice/dump978-rb.service
└─3444 /usr/bin/dump978-rb --sdr driver=rtlsdr,serial=00000401 --sdr-auto-gain --format CS8 --raw-port 30978 --json-port 28380
Mar 16 13:33:41 raspberrypi dump978-rb[3444]: Allocating 15 zero-copy buffers
Mar 16 13:33:41 raspberrypi dump978-rb[3444]: 0.0.0.0:30978: accepted a connection from 127.0.0.1:54360
Mar 16 13:33:41 raspberrypi dump978-rb[3444]: Failed to allocate zero-copy buffer for transfer 8
Mar 16 13:33:41 raspberrypi dump978-rb[3444]: Falling back to buffers in userspace
Mar 16 13:36:15 raspberrypi dump978-rb[3444]: 0.0.0.0:30978: accepted a connection from 127.0.0.1:54424
Mar 16 13:36:41 raspberrypi dump978-rb[3444]: 127.0.0.1:54424: connection closed
Mar 16 13:47:20 raspberrypi dump978-rb[3444]: 0.0.0.0:30978: accepted a connection from 127.0.0.1:54692
Mar 16 13:47:38 raspberrypi dump978-rb[3444]: 127.0.0.1:54692: connection closed
Mar 16 13:52:05 raspberrypi dump978-rb[3444]: 0.0.0.0:30978: accepted a connection from 127.0.0.1:54808
Mar 16 13:52:24 raspberrypi dump978-rb[3444]: 127.0.0.1:54808: connection closed
pi@raspberrypi:~ $
-
Installed and ran nc command but don't know how to interpret results.
-0aaa1b392ee6b960d58c0df811a80ae07f09e5bc9d05c40bc295c2a0000db0000000;rssi=1.9;t=1647462975.205;
Try this:
Human-readable (json) format
nc 127.0.0.1 28380 &
.
-
You are picking up around 60 aircraft in Tuscon at this time but they all appear to be ADSB equipped
Alan
-
Tons of output. Is there some string I can have grep search for to detect 978? Like this:
nc 127.0.0.1 28380 |grep <some 978 unique string>
-
You are picking up around 60 aircraft in Tuscon at this time but they all appear to be ADSB equipped
Alan
... or my 978 SW isn't picking anything up.
If I reboot the Pi these messages start appearing in the logs again. This is what was happening before:
2022-03-07 20 09 12 Can't connect to 978 source (127.0.0.1 28380). Waiting 5 second...
I have to "sudo systemctl restart dump978-rb" to get rid of them and get the 978 task running.
-
You also need UAT aircraft to pick them up
Alan
-
Tons of output. Is there some string I can have grep search for to detect 978? Like this:
nc 127.0.0.1 28380 |grep <some 978 unique string>
The output of following command will keep pouring data in json format when a uat equipped plane appears.
nc 127.0.0.1 28380
Within this heap of data you will see icao number also immediately after "address"
{"address":"a3a878","address_qualifier":"adsb_icao","airground_state":"airborne", .....
All these icao numbers are of uat978 equipped plane currently flying within say 100 nm of the receiver.
You can see any of these on Adsbexchange map. For example I want to see plane with icao a3a878, i will use this url in my browser:
https://globe.adsbexchange.com/?icao=a3a878 (https://globe.adsbexchange.com/?icao=a3a878)
.
-
I tried as you suggest and there's *tons* of data pouring out. When I put some of the ICAO numbers in the URL as you describe adsbexchange says their source is ADSB.
????
-
You also need UAT aircraft to pick them up
Alan
Just an FYI: This station is four miles from me and he's picking up UAT.
https://www.radarbox.com/stations/EXTRPI016058
-
I tried as you suggest and there's *tons* of data pouring out. When I put some of the ICAO numbers in the URL as you describe adsbexchange says their source is ADSB.
????
Both 1090 MHz and 978 MHz are ADS-B
ADS-B 1090 ES (Extended Squitter) operates on 1090 MHz and is required for aircraft operating above 18,000 FT MSL. The information sent over a Mode S transponder is greater and is called an "extended squitter" (ES). These aircraft will be able to display traffic directly from other ADS-B equipped aircraft and those with Mode S transponders without the need to rely on ground based systems.
ADS-B 978 UAT (Universal Access Transceiver) operates on 978 MHz and are available for aircraft that operate below 18,000 FT MSL.
The ADS-B “Out” broadcast on 978 MHz carries all the same tracking data sent by Extended Squitter (ES) transponders on 1090 MHz. However, on the ADS-B “In” side, the additional bandwidth afforded by the 978 MHz spectrum allows for a much more extensive list of data uplink services.
-
I tried as you suggest and there's *tons* of data pouring out.
Yes, even if there is only one uat equipped plane in your range, it transmitts data every say 10 seconds, so you will get lot of messages. However if you check icao numbers in every message, you will find it is repeat of same icao address. If there are 5 uat equipped planes in your range, you will find 5 different icao addresses repeating.
.
-
Thanks. I took some of the nc data, filtered and sorted it and that's what it shows.
There seems to be (at least) one piece still missing. This station is four miles from me and he's displaying plenty of UAT. The two stations are sync'd for MLAT
(https://i.imgur.com/VZ0rrmq.jpg)
My station displays nothing for UAT so there seems to be some disconnect between what I'm sending to RB24 and what their stats display shows.
(https://i.imgur.com/IrC8B8d.jpg)
-
As you are so close and will be picking up some of the same aircraft are you noting aircraft marked as UAT on the other system marked at ADSB on yours
I note that you are getting way more MLAT and ADSB messages than the other station. It may be the way the aircraft are being reported rather than not picking up any
Alan
-
Out of interest, did you ask support for advice?
Alan
-
My station EXTRPI000036 with Radarbox24's dump978-rb shows UAT Planes.
https://www.radarbox.com/stations/EXTRPI000036
-
As it should
Looking at your flight list none of them are UAT at this time
Alan
-
As you are so close and will be picking up some of the same aircraft are you noting aircraft marked as UAT on the other system marked at ADSB on yours
I note that you are getting way more MLAT and ADSB messages than the other station. It may be the way the aircraft are being reported rather than not picking up any
Alan
Thanks Alan. I compared the RB24 webpage output of EXTRPI010179 and EXTRPI016058 live (four miles away) , side-by-side, and it shows the former webpage displays two aircraft as ADS-B and on the latter as UAT. The latter also shows many UAT detections while the former shows none.
At this point we know that my station is detecting 978/UAT from the nc command but for some reason the RB24 webpage shows them as ADSB while the same AC is shown as UAT on the other stations' RB24 webpage. I've emailed all this, including screenshots, to support
Out of interest, did you ask support for advice?
Alan
Many times over the past 10 days. I send them info, suggest I try something, they ask for more info which I send, and after a day they stop replying. I've gotten much farther with the help from you and abcd567.
-
The main thing is that they are being picked up and displayed even if the source is incorrect
Alan
-
So the rhetorical question now is:
Are they being sent correctly to RB24 as UAT and RB24 are misinterpreting/misdisplaying the source
or
they're being *sent* to RB24 incorrectly even though my station is detecting them as UAT?
I've sent all the info to support with nc command output and screenshots and am waiting to hear back.
-
No idea, however be advised that support personnel are not tech so dont expect an answer that will satisfy you
Alan
-
I've already gotten to two separate email requests from support:
First: can you send us the last few lines of the log file please.
and then: That does show all is connected, can you send the ini file again please?
I assumed support was the tech people. Apparently they're just a pass-through between the feeders and the tech people.
-
That is correct
Alan
-
My diagnosis is that in vantage's rbfeeder installation, some files are broken, corrupted or missing. I formed this opinion because dump978-rb is giving proper output on both ports 30978 and 28380. This was confirmed by
commands "nc 127.0.0.1 30978" and "nc 127.0.0.1 28380".
On the other hand rbfeeder, which collects dats from dump978 and dump1090 and passes these to Air Nav Servers complints it cannot connect to port 30978.
In view of above, the best option is to completely purge rbfeeder and all its files, and then install it fresh.
(1) open file /etc/rbfeeder.ini and from it copy-paste key to you PC Notepad and save it.
(2) Give following command to remove rbfeeder
sudo apt purge rbfeeder
sudo reboot
(3) Make a fresh install of rbfeeder
sudo apt update
sudo apt install rbfeeder
sudo reboot
(4) After reboot check status
sudo systemctl status rbfeeder
https://www.radarbox.com/stations/EXTRPI010179 (https://www.radarbox.com/stations/EXTRPI010179)
-
I'll keep that in mind... and at some point I would need to copy back the /etc/rbfeeder.ini. Correct?
In the meantime I'm doing this as requested by RB24 support:
Just as a test can you remove the line
dump978_port=30978
Save and restart and wait 1 hour. Check whether the log is complaining if not double check whether UAT is appearing on the website. If that all fails add the line back and restart and let us know and we will investigate on our server regarding the data being sent to us.
-
Looks like it was passed to the tech guys
Alan
-
Conratulations, it started working.
-
Thanks. The support guys had me do this experiment which was *not* the total solution:
Sent: Thursday, March 17, 2022 1:51 PM
Just as a test can you remove the line
dump978_port=30978
Save and restart and wait 1 hour. Check whether the log is complaining if not double check whether UAT is appearing on the website. If that all fails add the line back and restart and let us know and we will investigate on our server regarding the data being sent to us.
That alone still resulted in this repeating over & over in /var/log/rbfeeder.log:
[2022-03-17 22:20:36] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
I also had to do this to get dump978-rb working and stop the "Can't connect" messages above :
sudo systemctl restart dump978-rb
For some still unknown reason a reboot/cold start always results in Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second.... At this point it's just an annoyance.
I'm thinking about documenting all the steps I had to take to get 978 working so others don't have to go through this.
Thanks to Alan and abcd567 for the help.
-
Thanks. The support guys had me do this experiment which was *not* the total solution:
Sent: Thursday, March 17, 2022 1:51 PM
Just as a test can you remove the line
dump978_port=30978
Save and restart and wait 1 hour. Check whether the log is complaining if not double check whether UAT is appearing on the website. If that all fails add the line back and restart and let us know and we will investigate on our server regarding the data being sent to us.
How come you got following line in config file of rbfeeder? I have also installed rbfeeder and added dump978-rb. I dont have this line in my rbfeeder's config file. Did you add it manually yourself?
dump978_port=30978
That alone still resulted in this repeating over & over in /var/log/rbfeeder.log:
[2022-03-17 22:20:36] Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second...
I also had to do this to get dump978-rb working and stop the "Can't connect" messages above :
sudo systemctl restart dump978-rb
For some still unknown reason a reboot/cold start always results in Can't connect to 978 source (127.0.0.1:28380). Waiting 5 second.... At this point it's just an annoyance.
Very strange.
Tonight I will reboot and check the behaviour of rbfeeder on my RPi.
I'm thinking about documenting all the steps I had to take to get 978 working so others don't have to go through this.
I am thinking of finding the root cause and a fix, provided I can recreate your situation on my Pi.
-
How come you got following line in config file of rbfeeder? I have also installed rbfeeder and added dump978-rb. I dont have this line in my rbfeeder's config file. Did you add it manually yourself?
dump978_port=30978
Here's why:
From: RadarBox Support
Sent: Sunday, March 13, 2022 11:16 AM
After the dump978_enabled = true please add
dump978_port=XXXXX
the XXX should be the port you are sharing the UAT data on.
-
I feel the rbfeeder has got some corrupt/missing files which is causing this issue. The best solution is to purge rbfeeder (sudo apt purge rbfeeder), then reinstall a fresh copy (sudo apt install rbfeeder).
-
My diagnosis is that in vantage's rbfeeder installation, some files are broken, corrupted or missing. I formed this opinion because dump978-rb is giving proper output on both ports 30978 and 28380. This was confirmed by
commands "nc 127.0.0.1 30978" and "nc 127.0.0.1 28380".
On the other hand rbfeeder, which collects dats from dump978 and dump1090 and passes these to Air Nav Servers complints it cannot connect to port 30978.
In view of above, the best option is to completely purge rbfeeder and all its files, and then install it fresh.
(1) open file /etc/rbfeeder.ini and from it copy-paste key to you PC Notepad and save it.
(2) Give following command to remove rbfeeder
sudo apt purge rbfeeder
sudo reboot
(3) Make a fresh install of rbfeeder
sudo apt update
sudo apt install rbfeeder
sudo reboot
(4) After reboot check status
sudo systemctl status rbfeeder
I note that the procedure says copy the /etc/rbfeeder.ini and save it. If I don't put it back in, what's the point other than having a record of what it used to be? Or is there a step missing?
-
I note that the procedure says copy the /etc/rbfeeder.ini and save it. If I don't put it back in, what's the point other than having a record of what it used to be? Or is there a step missing?
The procedure does NOT say to copy and save the whole rbfeeder.ini file.
It tells to copy-paste only the key from it.
(1) open file /etc/rbfeeder.ini and from it copy-paste key to you PC Notepad and save it.
The key will be required by the installer at the end of installation.
sudo rbfeeder --setkey ‹your sharing key›
.