Recent Posts1
AirNav Radar Discussion / Re: HOW TO ACTIVATE THE MLAT FOR RADARBOX24
« Last post by abcd567 on Today at 06:23:41 PM »I am using Debian GNU/Linux 13 (trixie).
Here is my rbfeeder.ini file:
Ini, TOML
[client]
network_mode=true
log_file=/var/log/rbfeeder.log
key=6cb57e6d30d670331670f1c3bc38xxx
sn=EXTRPI723871
lat=41.078221999999997
lon=16.782668000000001
alt=99
[network]
mode=beast
external_port=30005
external_host=127.0.0.1
[mlat]
#autostart_mlat=true
#mlat_cmd=/usr/bin/mlat-client
enable=true
mlat_connector=127.0.0.1:30005
(1) The first line (Ini, TOML) and last line (mlat_connector=127.0.0.1:30005), in your rbfeeder.ini file are unnecessary, and possibly causing connection problem of mlat-data. Please delete these 2 lines, and after deleting these lines, restart rbfeeder
(2) After deleting these extra lines & restarting rbfeeder, determine if mlat is active on your Pi by following method
(2.1) Issue command:
Code: [Select]
sudo systemctl status rbfeeder
(2.2) In the output, under CGroup, do you see a line starting with:
/usr/bin/python3 /usr/bin/mlat-client
If not, then most likely mlat-client package is either not installed, or installed but incompatible with trixie or is corrupted....
Please see below output on trixie, with mlat-working normally.
Code: [Select]
CGroup: /system.slice/rbfeeder.service
├─1802 /usr/bin/rbfeeder
└─1835 /usr/bin/python3 /usr/bin/mlat-client --input-type dump1090 --input-connect 127.0.0.1:32457 --server mlat1.rb24.com:40900 --lat 43.5xxxxx --lon -79.6xxxxx --alt 155 --user EXTRPI002103 --results beast,connect,127.0.0.1:32004