AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: QC91 on December 29, 2022, 10:01:19 PM
-
I have Radarcape ADS-B Receiver, and I like to feed it to Radarbox Network, would the RBFeeder work for Debian 10 that's the os the Radarcape uses I like to feed directly from Radarcape, any help would be appreciated
-
I have Radarcape ADS-B Receiver, and I like to feed it to Radarbox Network, would the RBFeeder work for Debian 10 that's the os the Radarcape uses I like to feed directly from Radarcape, any help would be appreciated
Radarbox24 have Linux Debian / RaspberryPi OS data feeder for RPi (architectures armhf and arm64/aarch64). They dont have feeder for AMD64/x86_x64 architecture.
For AMD64/x86_x64 architecture, you can install RB24 armhf feeder (for RPi) using Docker.
What is output of following commands on your Debian 10 computer?
uname -a
uname -m
-
Thanks for the reply. Here is the output.
jetvision@radarcape:~$ uname -a
Linux radarcape 5.4.25-1-bone #1 Thu Mar 12 13:28:30 CET 2020 armv7l GNU/Linux
jetvision@radarcape:~$ ^C
jetvision@radarcape:~$ uname -m
armv7l
-
Your device's architecture armv7l is suitable for installing RB24's RPi feeder on your device running Debian 10, by following command:
sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"
Full instructions are here:
https://www.radarbox.com/sharing-data/guide (https://www.radarbox.com/sharing-data/guide)
.
-
Thanks for the help I did the sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)" but I see some errors
Here is the Pastebin https://pastebin.com/iJSGDSkw
-
while copy-pasting command into terminal, you have broken it into two lines
Line-1 sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbf
Line-2 eeder.sh)"
You must use it as a single line command like below
sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"
Please see screenshot below
Click on screenshot to see large size, and scroll right to see the right-most portion
-
I ran the single-line command
sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"
I'm getting this Error Don't know how to install for a distribution named
Here is the Pastebin https://pastebin.com/NMrm4pNE
-
I'm getting this Error Don't know how to install for a distribution named
Issue following commands, and post their outputs
lsb_release -c
lsb_release -sc
-
I get this errors
jetvision@radarcape:~$ lsb_release -c
-bash: lsb_release: command not found
jetvision@radarcape:~$ lsb_release -sc
-bash: lsb_release: command not found
jetvision@radarcape:~$
-
-bash: lsb_release: command not found
The RB24 feeder installation script uses command "lsb_release -c"
The installation script failed due to missing package "lsb-release" which provides this command.
Install package lsb-release, then run the RB24 installation script. It will work OK
NOTE: The command is lsb_release, but package name is lsb-release. Note the difference _ and -
sudo apt install lsb-release
lsb_release -c
lsb_release -sc
sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"
-
Thanks here is the output.
jetvision@radarcape:~$ lsb_release -c
Codename: buster
jetvision@radarcape:~$ lsb_release -sc
buster
jetvision@radarcape:~$
I have tried the sudo nano /etc/rbfeeder.ini, but the file is blank
-
Thanks here is the output.
jetvision@radarcape:~$ lsb_release -c
Codename: buster
jetvision@radarcape:~$ lsb_release -sc
buster
jetvision@radarcape:~$
Great!
I have tried the sudo nano /etc/rbfeeder.ini, but the file is blank
Did you run installation script after installing the package "lsb-release"? What did the script announce when it finished installation?
Please issue following command and post its output. The output will show if the script succeeded or not in installing rbfeeder
apt-cache policy rbfeeder
-
Yes I did run sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"
I now see the sudo nano /etc/rbfeeder.ini file I will attach screen shot
Here is the Pastebin for rbfeeder https://pastebin.com/4WzzUFGd
Here is the output for
jetvision@radarcape:~$ apt-cache policy rbfeeder
rbfeeder:
Installed: 1:1.0.8+deb10
Candidate: 1:1.0.8+deb10
Version table:
*** 1:1.0.8+deb10 500
500 https://apt.rb24.com buster/main armhf Packages
100 /var/lib/dpkg/status
jetvision@radarcape:~$
-
should I run sudo rbfeeder --set-network-mode on --set-network-host ‹host› --set-network-port ‹port› --set-network-protocol ‹beast/raw› --no-start ?
-
Open configuration file (locate at /etc/rbfeeder.ini)
(1) Make sure option "network_mode" is set to "true" under "[client]" section.
(2) under section "[network]", change the option to following:
mode=raw
External_port=10003
external_host=127.0.0.1
Mode defines protocol to use. It can be "beast" or "raw". Anything else will be ignored.
You may try alk tgree below, but only one at a time:
External_port=10003
External_port=10003
External_port=10004
External_port=10005
NOTE: "external_host" defines the host that feeder will connect to fetch data and "external_port" defines the port to connect on this host.
REFERENCES & GUIDES
======================================
GUIDE 1 of 2: FROM RBFEEDER INSTALLATION WEB PPAGE
https://www.radarbox.com/sharing-data/guide
======================================[
2b
If you want to use the RBFeeder software with an existing decoder program
Open configuration file (locate at /etc/rbfeeder.ini) and change option "network_mode" to "true" under "[client]" section.
Now, under section "[network]", change these options:
"mode", "External_port", "external_host".
Mode defines protocol to use. It can be "BEAST" or "RAW". Anything else will be ignored. "external_host" defines the host that feeder will connect to fetch data and "external_port" defines the port to connect on this host.
≠==========================
GUIDE 2 of 2: FROM JETVISION RADARCAPE WEPAGE
https://wiki.jetvision.de/wiki/Radarcape:Software_Features
============================
Raw Data Streaming to Network (TCP and UDP)
The binary and AVR raw data formats are identical to those of the Mode-S Beast and documented in Mode-S_Beast:Data_Output_Formats. For the Radarcape, there is one additional message that contains timestamp and FPGA configuration information, which is triggered by each 1PPS from the GPS module.
TCP or UDP port 10002
This is a CRC-checked mirror of the data as it comes from the FPGA, DF-11, DF-17 and DF-18 are CRC checked if enabled in FPGA. Includes Mode-A/C data with respect to the configuration setting.
TCP or UDP port 10003
Binary formatted raw data with all Modes-S data formats CRC-prechecked (eliminates transmission of the erroneous frames, reduces load on the network). All data from the FPGA is disassembled into messages and verified if correct.
TCP or UDP port 10004
Binary formatted raw data, pre-checked DF-11, DF-17 and DF-18 only: minimum load for the transmission path but contains most information. No Mode-A/C data.
TCP or UDP port 10005
Binary formatted raw data, only raw data frames of those aircraft where the location (latitude and longitude) is unknown. Used for special MLAT purposes. No Mode-A/C data.
Port 30003 Service (TCP, UDP, and USB-serial)
Port 30003 style output (e.g., for use with SBS Plotter) can be provided without the need of an additional application on your PC.
The Radarcape provides this data stream on TCP port 30003, UDP port 30003, and the serial USB interface.
-
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
-
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.
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.
.
-
Thanks I tried sudo systemctl restart rbfeeder I looked at /etc/rbfeeder.ini but there is no key
-
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
-
Hi, Here are the outputs
sudo systemctl status rbfeeder pastebin https://pastebin.com/EBCZqs4q
sudo journalctl -u rbfeeder pastebin https://pastebin.com/P2xpTiUC
Thanks
-
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.
sudo apt purge rbfeeder
sudo reboot
sudo apt install rbfeeder
STEP-4: After last command I checked key by following command:
pi@raspberrypi:~ $ 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:
pi@raspberrypi:~ $ 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
sudo rbfeeder
register your receiver, go to this link -
https://www.radarbox.com/sharing-data/claim
STEP-3: Check if key is generated
sudo rbfeeder --showkey --no-start
STEP-4: If key is generated, then reboot Debian 10 machine.
STEP-5: After reboot check status
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]
-
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
jetvision@radarcape:~$ 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
jetvision@radarcape:~$ ^C
jetvision@radarcape:~$ 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
jetvision@radarcape:~$ sudo nano /etc/rbfeeder.ini
jetvision@radarcape:~$ sudo nano /etc/rbfeeder.ini
jetvision@radarcape:~$ 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
-
I also wanted to confirm when I save the /etc/rbfeeder.ini file do I save in DOS Format?
-
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.
-
jetvision@radarcape:~$ 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)
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
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
-
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
-
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=???
-
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
-
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
-
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
-
Here is screen shot
-
I change the external_port=10003 /etc/rbfeeder.ini but sill not sending I found few errors
-
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
.
-
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
-
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
-
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"
-
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:~$
-
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:
-
I did the sudo docker container ls -a but I get
sudo: docker: command not found
-
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)
-
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.
-
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.
-
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 :
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.
-
Thank you. I do see it now, and it's showing MLAT active (No stations synced) radarbox.com