AirNav Radar
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 


Author Topic: Troubleshooting the RBFeeder to send data to AirNav if FR24 is already working.  (Read 702 times)

0 Members and 1 Guest are viewing this topic.

KRIShark

  • New Member
  • *
  • Posts: 2
Hello,

I am experiencing an issue with my rbfeeder setup for airnavradar where my station page (https://www.airnavradar.com/) displays “no data” (i.e. ADS‑B: 0, Messages: 89) despite my Flightradar24 feed running correctly. I am using rbfeeder on my Raspberry Pi to send data to airnavradar, and my current configuration is intended to pull ADS‑B data from my existing dump1090 output (which is providing data on port 30005). Below are the details of my current setup and the troubleshooting steps I have taken:

[client]
network_mode=true
log_file=/var/log/rbfeeder.log
key=<key>
sn=EXTRPI642782
lat=<val>
lon=<val>
alt=85

[network]
mode=beast
external_port=30005
external_host=127.0.0.1

[mlat]
autostart_mlat=false
#mlat_cmd=/usr/bin/python3.9 /usr/bin/mlat-client

[dump978]
#dump978_enabled=true

The logs of rbfeeder looking good. It shows thet it sends packets to airnavradar.

Starting RBFeeder Version 1.0.11 (build 20241022110000)
[2025-02-19 19:27:54] Using configuration file: /etc/rbfeeder.ini
[2025-02-19 19:27:54] Network-mode enabled.
[2025-02-19 19:27:54] Remote host to fetch data: 127.0.0.1
[2025-02-19 19:27:54] Remote port: 30005
[2025-02-19 19:27:54] Remote protocol: BEAST
[2025-02-19 19:27:54] Using GNSS (when available)
[2025-02-19 19:27:54] Start date/time: 2025-02-19 19:27:54
[2025-02-19 19:27:54] Socket for ANRB created. Waiting for connections on port 32088
[2025-02-19 19:27:55] Connection established.
[2025-02-19 19:27:56] Client type: Other
[2025-02-19 19:27:56] Connection with RadarBox24 server OK! Key accepted by server. [2025-02-19 19:27:56] This is your station serial number: EXTRPI642782
[2025-02-19 19:28:54] ** Statistics updated every 60 seconds **
[2025-02-19 19:28:54] Packets sent in the last 60 seconds: 2, Total packets sent since startup: 2
[2025-02-19 19:28:54] Data sent: 176 B
[2025-02-19 19:28:54] Data received: 31 B
[2025-02-19 19:29:55] ** Statistics updated every 60 seconds **
[2025-02-19 19:29:55] Packets sent in the last 60 seconds: 1, Total packets sent since startup: 3
[2025-02-19 19:29:55] Data sent: 183 B
[2025-02-19 19:29:55] Data received: 31 B
[2025-02-19 19:30:56] ** Statistics updated every 60 seconds **
[2025-02-19 19:30:56] Packets sent in the last 60 seconds: 1, Total packets sent since startup: 4
[2025-02-19 19:30:56] Data sent: 190 B
[2025-02-19 19:30:56] Data received: 31 B
[2025-02-19 19:31:57] ** Statistics updated every 60 seconds **
[2025-02-19 19:31:57] Packets sent in the last 60 seconds: 1, Total packets sent since startup: 5
[2025-02-19 19:31:57] Data sent: 197 B
[2025-02-19 19:31:57] Data received: 31 B
....

I have verified that my FL24 system (dump1090) is working and providing ADS‑B data on port 30005. My rbfeeder configuration is set to network_mode=true, so it should be connecting to 127.0.0.1:30005. I have disabled the MLAT functionality within rbfeeder (autostart_mlat=false) to avoid potential conflicts with my existing FL24 MLAT feed. I have confirmed that my latitude, longitude, and altitude are correctly set.



What could be the cause of the issue?
What should I do to fix my feed?
Is there anything wrong with the configuration?

Runway 31

  • Moderator
  • Hero Member
  • *****
  • Posts: 34301
I note you are now feeding, what did you do to fix the issue?

Alan

KRIShark

  • New Member
  • *
  • Posts: 2
I changed the data source of the rbfeeder to:

[network]
mode=raw
external_port=30002
external_host=127.0.0.1

and it fixed the issue.
Even though fl24 is working with:

[network]
mode=beast
external_port=30005
external_host=127.0.0.1

It seems that rbfeeder does not work with beast protocol.

So I would mark the post as solved, but I don't know how.

Runway 31

  • Moderator
  • Hero Member
  • *****
  • Posts: 34301
I dont know as I dont know much abount Linux, you would need to ask support but I dont see why it wouldnt, maybe just needed to point it to the correct port

Alan