Radarcape ADS-B Receiver Feeding Radarbox Network

[QC91]

Thanks for the help I have updated the /etc/rbfeeder.ini

But I don't see the rbfeeder running on htop

also when I run sudo rbfeeder --showkey --no-start

Your sharing key is not set or is not valid. If is not set, a new sharing key will be create on first connection.
Configuration file: /etc/rbfeeder.ini





[client]
network_mode=true
log_file=/var/log/rbfeeder.log

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

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

[dump978]
#dump978_enabled=true

[abcd567]

But I don't see the rbfeeder running on htop

also when I run sudo rbfeeder --showkey --no-start

Your sharing key is not set or is not valid. If is not set, a new sharing key will be create on first connection.

You have to RESTART the rbfeeder by following command. A key will be automatically added to file /etc/rbfeeder.ini on restart.

Code: [Select]


sudo systemctl restart rbfeeder   



After restart, wait for few minutes, then check file /etc/rbfeeder.ini to make sure key has been added in following format:

key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
sn=EXTRPIxxxxxx 

If the key is there, Register your Receiver.
Registering or claiming your receiver is an important step in the setup process, as data is not shared with AirNav RadarBox unless this step is complete.

To register your receiver, go to this link -
https://www.radarbox.com/sharing-data/claim 

Enter your SHARING KEY in the field provided and then click CLAIM.
That's it! You'll also get an email stating that your receiver has been successfully registered with AirNav RadarBox.

.

[QC91]

Thanks I tried sudo systemctl restart rbfeeder I looked at  /etc/rbfeeder.ini but there is no key

[abcd567]

Please post output of following comands
(Increase width of terminal to maximum so that right-most part of output text is not cut-off)

sudo systemctl status rbfeeder   

sudo journalctl -u rbfeeder   

[QC91]

Hi, Here are the outputs

sudo systemctl status rbfeeder  pastebin   https://pastebin.com/EBCZqs4q

sudo journalctl -u rbfeeder  pastebin   https://pastebin.com/P2xpTiUC

Thanks

[abcd567]

You can try the steps below which I have tried to successfully create a new key.


STEP-1: I purged existing rbfeeder. This removed the existing rbfeeder AND file /etc/rbfeeder.ini (which contained the existing key).

STEP-2: I then rebooted.

STEP-3: Ater reboot, installed rbfeeder again.

Please see the following 3 commands.

Code: [Select]

sudo apt purge rbfeeder 

sudo reboot   

sudo apt install rbfeeder 


STEP-4: After last command I checked key by following command:

Code: [Select]

[email protected]:~ $ sudo rbfeeder --showkey --no-start

Your sharing key is not set or is not valid. If is not set, a new sharing key will be create on first connection.
Configuration file: /etc/rbfeeder.ini

STEP-5: Next I manually started rbfeeder by giving following command, which generated a new key on manual start:

Code: [Select]

[email protected]:~ $ sudo rbfeeder 

[2023-01-02 18:27:55]  Starting RBFeeder Version 1.0.8 (build 20220708190411)
[2023-01-02 18:27:55]  Using configuration file: /etc/rbfeeder.ini
[2023-01-02 18:27:55]  Network-mode enabled.
[2023-01-02 18:27:55]           Remote host to fetch data: 127.0.0.1
[2023-01-02 18:27:55]           Remote port: 30005
[2023-01-02 18:27:55]           Remote protocol: BEAST
[2023-01-02 18:27:55]  Using GNSS (when available)
[2023-01-02 18:27:55]  Start date/time: 2023-01-02 18:27:55
[2023-01-02 18:27:55]  Socket for ANRB created. Waiting for connections on port 32088
[2023-01-02 18:27:56]  TCP Client (ANRB) requesting to connect...
[2023-01-02 18:27:56]  [Slot 0] New ANRB connection from IP 10.0.0.10, remote port 60514, socket: 11
[2023-01-02 18:27:56]  Connection established.
[2023-01-02 18:27:56]  Empty sharing key. We will try to create a new one for you!
[2023-01-02 18:27:57]  Your new key is xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. Please save this key for future use. You will have to know this key to link this receiver to your account in RadarBox24.com. This key is also saved in configuration file (/etc/rbfeeder.ini)
[2023-01-02 18:28:55]  ******** Statistics updated every 60 seconds ********



NOTE: If above 5 steps fail to generate the kay, then do following to force key generation

STEP-1: Modify file /etc/rbfeeder.ini as follows, and save file.

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

STEP-2: Start rbfeeder manually

Code: [Select]


sudo rbfeeder 



register your receiver, go to this link -
https://www.radarbox.com/sharing-data/claim 

STEP-3: Check if key is generated

Code: [Select]


sudo rbfeeder --showkey --no-start 


STEP-4: If key is generated, then reboot Debian 10 machine.

STEP-5: After reboot check status

Code: [Select]


sudo systemctl status rbfeeder   


STEP-6: Go to this link to register your receiver

https://www.radarbox.com/sharing-data/claim 


STEP-7: After registering/Claiming, try different settings of "mode" and "external_port" under [network]

[QC91]

I tried both setting but I still get  Your sharing key is not set or is not valid. If is not set, a new sharing key will be create on first connection.
Configuration file: /etc/rbfeeder.ini


but I do see this error Segmentation fault  I will post the outputs


[email protected]:~$ sudo rbfeeder
[2023-01-03 01:21:27]  Starting RBFeeder Version 1.0.8 (build 20220708190410)
[2023-01-03 01:21:27]  Using configuration file: /etc/rbfeeder.ini
[2023-01-03 01:21:27]  Network-mode enabled.
[2023-01-03 01:21:27]           Remote host to fetch data: 127.0.0.1
[2023-01-03 01:21:27]           Remote port: 10003
[2023-01-03 01:21:27]           Remote protocol: RAW
[2023-01-03 01:21:27]  Using GNSS (when available)
[2023-01-03 01:21:27]  Start date/time: 2023-01-03 01:21:27
Segmentation fault
[email protected]:~$ ^C
[email protected]:~$ sudo rbfeeder --showkey --no-start

Your sharing key is not set or is not valid. If is not set, a new sharing key will be create on first connection.
Configuration file: /etc/rbfeeder.ini

[email protected]:~$ sudo nano /etc/rbfeeder.ini
[email protected]:~$ sudo nano /etc/rbfeeder.ini
[email protected]:~$ sudo rbfeeder
[2023-01-03 01:29:17]  Starting RBFeeder Version 1.0.8 (build 20220708190410)
[2023-01-03 01:29:17]  Using configuration file: /etc/rbfeeder.ini
[2023-01-03 01:29:17]  Network-mode enabled.
[2023-01-03 01:29:17]           Remote host to fetch data: 127.0.0.1
[2023-01-03 01:29:17]           Remote port: 30005
[2023-01-03 01:29:17]           Remote protocol: BEAST
[2023-01-03 01:29:17]  Using GNSS (when available)
[2023-01-03 01:29:17]  Start date/time: 2023-01-03 01:29:17
Segmentation fault

 

[QC91]

I also wanted to confirm when  I save the /etc/rbfeeder.ini file do I save in DOS Format?

[abcd567]

I also wanted to confirm when  I save the /etc/rbfeeder.ini file do I save in DOS Format?

To save the file /etc/rbfeeder.ini, do NOT select any format.
To save, first press Ctrl and O keys together. It will display:

File Name to Write:   /etc/rbfeeder.ini

Then press Enter Key, and that is all.

[abcd567]

[email protected]:~$ sudo rbfeeder
[2023-01-03 01:29:17]  Starting RBFeeder Version 1.0.8 (build 20220708190410)
[2023-01-03 01:29:17]  Using configuration file: /etc/rbfeeder.ini
[2023-01-03 01:29:17]  Network-mode enabled.
[2023-01-03 01:29:17]           Remote host to fetch data: 127.0.0.1
[2023-01-03 01:29:17]           Remote port: 30005
[2023-01-03 01:29:17]           Remote protocol: BEAST
[2023-01-03 01:29:17]  Using GNSS (when available)
[2023-01-03 01:29:17]  Start date/time: 2023-01-03 01:29:17
Segmentation fault

After all this effort, it now says segmentation fault!
It is said that segmentation fault's possible causes are:
- Manually starting the process.
- Broken package
- Outdated package

OK, one last try, This time we will NOT start it manually (i.e. not by command "sudo rbfeeder"), but by systemctl (last command below)

Code: [Select]


sudo apt purge rbfeeder 

sudo reboot

sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"   

sudo systemctl restart rbfeeder   

## Now Check Status By Followig Command:

sudo systemctl status rbfeeder


Check key

Code: [Select]


sudo nano /etc/rbfeeder.ini   



What Is Segmentation Fault?
In a nutshell, segmentation fault refers to errors due to a process's attempts to access memory regions that it shouldn't. When the kernel detects odd memory access behaviors, it terminates the process issuing a segmentation violation signal (SIGSEGV).

Sometmes it may be caused by manually starting the process

[QC91]

I wanted to thank you for all the help unfortunately, it will not work on my Radarcape, but I do have good news the rb24 feeder works on my jetvision air squitter the air squitter is using Linux air-squitter 5.4.11-1-opz  but the Radarcape uses Linux radarcape 5.4.25-1-bone

I like to turn on MLAT for the air squitter I just wanted to confirm these are the commands I should use

1. sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"
2. sudo apt-get install mlat-client -y
3. reboot

[abcd567]

I wanted to thank you for all the help unfortunately, it will not work on my Radarcape, but I do have good news the rb24 feeder works on my jetvision air squitter the air squitter is using Linux air-squitter 5.4.11-1-opz  but the Radarcape uses Linux radarcape 5.4.25-1-bone

I like to turn on MLAT for the air squitter I just wanted to confirm these are the commands I should use

1. sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"
2. sudo apt-get install mlat-client -y
3. reboot

Yes, the rbfeeder installion script adds rb24 repository to your OS's /etc/apt/sources.list.d folder.. Once this is done, you can install mlat-client from their repository by command "sudo apt-get innstall mlat-client".

Please see attached screenshot from my RPi model 4 running RaspberryPi OS Bullseye.

By the way what settings under [network] worked OK on air squitter?

[network]
mode=???
external_port=???
external_host=???

[QC91]

Thanks agin. Here is the setting I have for the  air squitter

[client]
network_mode=false
log_file=/var/log/rbfeeder.log

key= Removed

sn=Removed

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

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

[dump978]
#dump978_enabled=true

[abcd567]

Thanks agin. Here is the setting I have for the  air squitter

[client]
network_mode=false

Oops!!!
Seems failure with Radarcape was due to using this setting:
[client]
network_mode=true

[QC91]

Thanks. Yes tried the same setting on the Radarcape but still not working, there is a problem with my feeding of air squitter it shows my feeder online, but it's not sending any aircraft data. Should I change the   mode=raw External_port=10003