RadarBox ANRB 6.02.003 - no flights shown

[BicNav]

I have the ANRB installed on Windows 11 and have a RasPI running RBFeeder both of which are on the same LAN. The RBFeeder successfully feeds flights to the RadarBox server and my station page shows the flights as expected.

However, I can't see the flights on the ANRB - even though the connection box is green and status bar states:- Hardware: Connected (192.168.1.131) . The message counter remains at zero - Msgs/Sec (0)

I have reinstalled both the ANRB as well as the RBFeeder, and have checked all the settings. I have also installed the ANRB on a Windows 10 laptop on the same LAN and have exactly the same issue - no flights are shown even though the connection box is green.

I have checked that port 32088 has an established connection to the IP address of the RasPI:-

PS C:\WINDOWS\system32> netstat -ano | findstr 32088
  TCP    192.168.1.101:30939    192.168.1.131:32088    ESTABLISHED     30220

I have also connected to port 32088 via Telnet and can see that data is being delivered with this command:-

Microsoft Telnet> open 192.168.1.131 32088

Here is the result:-
RTI3JU0jIl1ZUlJIU1JRUVBTUlZQVldWU1JPSFNWUVNUTk9ITFNSVlFOT0hNTk9IUE5P~*
RTI3JU1WU1JYVlRIU1JRUVBTUlZQVldWU1JPSFNbVFFRTk9IUFRQVE1OT0hNTk9VTU4=~*
RTI3JU1WU1NXWiJIU1JRUVBTUlZQVldWU1JPSFhUUVFNTk9ITU5PSE1OUkhN~*
..... and so on.

The output continues which shows that the handshake must be working which proves the ANRB is accepting the data, but is refusing to process it.

I have the feeling that the data is somehow malformed, so that the ANRB cannot decode it.

Does anyone have any experience in this type of data exchange? As far as I know it's not raw BEAST format, but is post processed by RBFeeder to output the format ANRB expects.

Clearly something is wrong either with the RBFeeder installation / configuration on the RasPI or the Windows installation of ANRB.

[Runway 31]

I take it that By ANRB you mean the V6.02.03 software

Have you entered your Pi network details on the File/Preferences/ tab, thats needed to connect the Pi to the software

Before configuring the software, make sure that the receiver is connected to the same network as your computer. Next, follow the instructions to configure the application:

Start up the application;
Go to "File" then click "Preferences";
Next click on the "RadarBox" tab;
In the "RadarBox New Firmware" section, please enter the local IP address of the unit;
Make sure that the "Port" is set to 32088;
Click “OK”;
The application should be able to detect the receiver automatically. If not, please restart the application.

Alan

[BicNav]

As I said, I have checked all the settings - especially the correct IP address and port of the RasPI. I had purposely entered incorrect IP address and port number to ensure the green status indicator changes. It only went green if the connection was correct. This was confirmed by the netstat -ano | findstr 32088 command that showed the ANRB was connected to the correct IP address and port.

I believe the data is being received but ignored due to the wrong format.

[Runway 31]

I cant say for sure but I would expect it will be looking for BEAST format.  The network mode in the RB feeder gives Network mode=BEAST and if you connect the V6 software and the Pi on the same network together the and aircraft show so that would suggest to me that BEAST format is needed for V6 to display and that should be the output being sent to V6

While you are not seeing aircraft, are you seeing the map outline ok

Others are running it with no issues with a Pi but I have seen the issue raise its ugly head previously but cant remember how it was fixed

Alan

[abcd567]

However, I can't see the flights on the ANRB - even though the connection box is green and status bar states:- Hardware: Connected (192.168.1.131) . The message counter remains at zero - Msgs/Sec (0)

Most likely you are missing a check mark on "Process Hardware  Flights".
Please see two screenshots attached below.

[BicNav]

I have found that the output from RBFeeder on port 32088 is malformed as I originally suspected.

I have a RadarBox Xrange2 running at a remote location which is feeding into the RadarBox Network. I checked using ANRB 6.02.003 installed on a PC at the remote location correctly processed and showed the flights from the XRange2, by using it's LAN IP and port 32088. I was able to forward port 32088 through the remote router internet gateway, and could telnet to port 32088 on the remote network from this location.

I found that the telnet dump from my local RBFeeder running on the local RasPi compared to the XRange2 dump were similar but not quite the same. I do know that the feed from port 32088 is definitely not BEAST format as Alan (@Runway 31) has suggested.

The final confirmation was to point my local ANRB to the remote XRange2 forwarded port - however this didn't work as the IP address associated with the source must be on the same private Class C subnet as the PC the ANRB is hosted on. Clearly a remote address does not qualify. I overcame the issue by using a local Windows port proxy. In that way I could point the ANRB to the local loopback host 127.0.0.1 port 32088 instead of the remote IP. This was the Powershell command:-

netsh interface portproxy add v4tov4 listenport=32088 connectaddress=<remote IP address> connectport=32088 listenaddress=127.0.0.1

So I'm still left with the original issue that the RBFeeder on my local RasPi is ouputting garbage on port 32088.

[BicNav]

Screenshot of the remote XRange2 flights shown on my local ANRB

[abcd567]

So I'm still left with the original issue that the RBFeeder on my local RasPi is ouputting garbage on port 32088.

Please see attached 2 screen shots which show:
(1) Data received from port 30288 of RPi / rbfeeder
(2) Perfectly normal display on ANRB software


LATER ADDITION:
If you are still convinced that rbfeeder is supplyin garbage on port 30288, then it means during installation of rbfeeder, some corruption occured. In this case purge rbfeeder and then install a fresh copy.

IMPORTANT:
Before issuing following commands, open file /etc/rbfeeder.ini and copy key from there, paste key on notepad, and save notepad. You will need this key when a new copy of rbfeeder is installed.

Code: [Select]

sudo apt purge rbfeeder 

sudo apt autoremove 

sudo apt autoclean 

sudo apt update   

sudo apt install rbfeeder   

sudo systemctl restart rbfeeder 

sudo systemctl status rbfeeder