Radarcape ADS-B Receiver Feeding Radarbox Network

[QC91]

Here is screen shot

[QC91]

I change the external_port=10003  /etc/rbfeeder.ini  but sill not sending I found few errors

 

[abcd567]

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

No harm in trying different settings of data type and port. You may finally find the right one by trial & error.

You may try different value of external_host as well.

On Airsquitter Linux air-squitter 5.4.11-1-opz :

(1) Check file /etc/fr24feed.ini to see what data type & port it is using

(2) Issue following commands to find what data type & port Flightaware is using

sudo piaware-config -show receiver-port   

sudo piaware-config -show receiver-host   



.

[QC91]

I tried to look at /etc/fr24feed.ini, but it's blank

sudo piaware-config -show receiver-port  is showing  30005

sudo piaware-config -show receiver-host  showing nothing

[QC91]

I also wanted to mention that I'm feeding to adsbexchange  using this ADS-B Exchange Setup Scripts https://www.adsbexchange.com/forum/threads/help-with-ads-b-exchange-setup-scripts-on-radarcape.637122/

Here is my output for ADS-B Exchange https://pastebin.com/RS0xZSqu

[abcd567]

I tried to look at /etc/fr24feed.ini, but it's blank

May be FR24 is through Docker??
How did you install fr24feed?

sudo piaware-config -show receiver-port  is showing  30005

Piaware uses Beast format. So at port 3005 Beast format is made available by Airsquitter. Radarbox24 also uses Beast and port 30005

sudo piaware-config -show receiver-host  showing nothing

No output means host is not set. In this case it uses default host which is 127.0.0.1

I also wanted to mention that I'm feeding to adsbexchange  using this ADS-B Exchange Setup Scripts https://www.adsbexchange.com/forum/threads/help-with-ads-b-exchange-setup-scripts-on-radarcape.637122/

cat /etc/default/adsbexchange will show settings

Possibly it may be as follows:

INPUT="IP-OF-AIRSQUITTER:10003" (or 127.0.0.1:10003)
and
INPUT_TYPE="radarcape_gps"

[QC91]

I did not install FR24. It was  integrated with the  Airsquitter

Here is the output for adsbexchange



jetvision@air-squitter:~$ cat /etc/default/adsbexchange
INPUT="127.0.0.1:10003"
REDUCE_INTERVAL="0.5"

# feed name for checking MLAT sync (adsbx.org/sync)
# also displayed on the MLAT map: map.adsbexchange.com/mlat-map
USER=

LATITUDE=
LONGITUDE="

ALTITUDE="44m"

RESULTS="--results beast,connect,localhost:30104"
RESULTS2="--results basestation,listen,31003"
RESULTS3="--results beast,listen,30157"
RESULTS4="--results beast,connect,localhost:30154"
# add --privacy between the quotes below to disable having the feed name shown on the mlat map
# (position is never shown accurately no matter the settings)
PRIVACY=""
INPUT_TYPE="radarcape_gps"

MLATSERVER="feed.adsbexchange.com:31090"
TARGET="--net-connector feed.adsbexchange.com,30004,beast_reduce_out,feed.adsbexchange.com,64004"
NET_OPTIONS="--net-heartbeat 60 --net-ro-size 1280 --net-ro-interval 0.2 --net-ro-port 0 --net-sbs-port 0 --net-bi-port 30154 --net-bo-port 0 --net-ri-port 0 --write-json-every 1"
jetvision@air-squitter:~$

[abcd567]

INPUT="127.0.0.1:10003"
INPUT_TYPE="radarcape_gps


To check if fr24feed is through docker, issue following command

sudo docker container ls -a 

Please see attached screenshot:

[QC91]

I did the sudo docker container ls -a   but I get 
sudo: docker: command not found

[QC91]

Hi, it's now working I changed the port to 10006 and  sudo systemctl restart rbfeeder  and it's now sending but I do see this error Process: 3648 ExecStartPre=/bin/mkdir /var/run/rbfeeder (code=exited, status=1/FAILURE)

[abcd567]

Hi, it's now working I changed the port to 10006 and  sudo systemctl restart rbfeeder  and it's now sending but I do see this error Process: 3648 ExecStartPre=/bin/mkdir /var/run/rbfeeder (code=exited, status=1/FAILURE)

This message at restart is normal. It is caused by fact that the folder "/var/run/rbfeeder" was already created at boot. The attempt to create an existing folder results in error message.

Please see screenshot I have attached. This status was after I restarted rbfeeder.

[QC91]

I wanted to thank you agin for all the help. It's feeding just trying to get MLAT setup. I have the mlat-client installed will post output but looking at the sudo nano /etc/rbfeeder.ini  I don't see (latitude) (longitude) or antenna height should I add them in the instructions post at https://forum.radarbox24.com/index.php?topic=101771.msg389571#msg389571



jetvision@air-squitter:~$ sudo systemctl status mlat-client
● mlat-client.service - LSB: Multilateration client
   Loaded: loaded (/etc/init.d/mlat-client; generated)
   Active: active (exited) since Sun 2023-01-08 23:59:09 UTC; 6min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 252 ExecStart=/etc/init.d/mlat-client start (code=exited, status=0/SUCCESS)

Jan 08 23:59:09 air-squitter systemd[1]: Starting LSB: Multilateration client...
Jan 08 23:59:09 air-squitter mlat-client[252]: Not starting mlat-client daemon, disabled via /etc/defau
Jan 08 23:59:09 air-squitter systemd[1]: Started LSB: Multilateration client.
lines 1-9/9 (END)...skipping...
● mlat-client.service - LSB: Multilateration client
   Loaded: loaded (/etc/init.d/mlat-client; generated)
   Active: active (exited) since Sun 2023-01-08 23:59:09 UTC; 6min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 252 ExecStart=/etc/init.d/mlat-client start (code=exited, status=0/SUCCESS)

Jan 08 23:59:09 air-squitter systemd[1]: Starting LSB: Multilateration client...
Jan 08 23:59:09 air-squitter mlat-client[252]: Not starting mlat-client daemon, disabled via /etc/default/mlat-client ... (warning).
Jan 08 23:59:09 air-squitter systemd[1]: Started LSB: Multilateration client.

[abcd567]

I wanted to thank you agin for all the help. It's feeding just trying to get MLAT setup. I have the mlat-client installed will post output but looking at the sudo nano /etc/rbfeeder.ini  I don't see (latitude) (longitude) or antenna height should I add them in the instructions post at https://forum.radarbox24.com/index.php?topic=101771.msg389571#msg389571

Yes, you have to add your Lat, Lon, and alt in file /etc/rbfeeder.ini under [client] as I have shown in the post yo have linked.

After adding Lat, Lon, Alt and saving the file, restart rbfeeder by sudo systemctl restart rbfeeder.

After restart, check status by command sudo systemctl status rbfeeder. You should see  3rd line (starting with /usr/bin/python3.9) under CGroup :

Code: [Select]

     CGroup: /system.slice/rbfeeder.service
             ├─592 /usr/bin/rbfeeder
             └─674 /usr/bin/python3.9 /usr/bin/mlat-client --input-type dump1090 --input-connect 127.0.0.1:32457 --server mlat1.rb24.com:4>



jetvision@air-squitter:~$ sudo systemctl status mlat-client
● mlat-client.service - LSB: Multilateration client
   Loaded: loaded (/etc/init.d/mlat-client; generated)
   Active: active (exited) since Sun 2023-01-08 23:59:09 UTC; 6min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 252 ExecStart=/etc/init.d/mlat-client start (code=exited, status=0/SUCCESS)

Jan 08 23:59:09 air-squitter systemd[1]: Starting LSB: Multilateration client...
Jan 08 23:59:09 air-squitter mlat-client[252]: Not starting mlat-client daemon, disabled via /etc/defau
Jan 08 23:59:09 air-squitter systemd[1]: Started LSB: Multilateration client.
lines 1-9/9 (END)...skipping...
● mlat-client.service - LSB: Multilateration client
   Loaded: loaded (/etc/init.d/mlat-client; generated)
   Active: active (exited) since Sun 2023-01-08 23:59:09 UTC; 6min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 252 ExecStart=/etc/init.d/mlat-client start (code=exited, status=0/SUCCESS)

Jan 08 23:59:09 air-squitter systemd[1]: Starting LSB: Multilateration client...
Jan 08 23:59:09 air-squitter mlat-client[252]: Not starting mlat-client daemon, disabled via /etc/default/mlat-client ... (warning).
Jan 08 23:59:09 air-squitter systemd[1]: Started LSB: Multilateration client.

Mlat-client is started and kept running by rbfeeder when you add Lat, Lon, and Alt to file rbfeeder.ini. Since you have not done this, the mlat-claient is starting and then stopping.

[QC91]

Thank you. I do see it now, and it's showing MLAT active (No stations synced) radarbox.com

[GeoAir.pt]

Hello all.

Has anyone been successful feeding Radarbox network from a Radarcape receiver?

I tried to follow the steps indicated in this thread but didn't succeed :(

When I run

Code: [Select]

sudo rbfeeder the output is:

[2024-09-26 11:44:40]  Starting RBFeeder Version 1.0.10 (build 20240111143100)
[2024-09-26 11:44:40]  Using configuration file: /etc/rbfeeder.ini
[2024-09-26 11:44:40]  Network-mode enabled.
[2024-09-26 11:44:40]           Remote host to fetch data: 127.0.0.1
[2024-09-26 11:44:40]           Remote port: 30005
[2024-09-26 11:44:40]           Remote protocol: BEAST
[2024-09-26 11:44:40]  Using GNSS (when available)
[2024-09-26 11:44:40]  Start date/time: 2024-09-26 11:44:40
[2024-09-26 11:44:40]  Socket for ANRB created. Waiting for connections on port 32088
Segmentation fault

Thank you for any suggestion.