HOW TO ACTIVATE THE MLAT FOR RADARBOX24

[Runway 31]

Please post your ini file with your credential key redacted

Alan

[didou]

Hello Alan,

Here is my rbfeeder.ini (key, latitude and longitude redacted):

Code Select Expand

[client]
lat=MASQUE
lon=MASQUE
alt=353
network_mode=false
log_file=/var/log/rbfeeder.log
key=MASQUE
sn=EXTRPI736563

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

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

[dump978]
#dump978_enabled=true

Thank you for your help.

[didou]

Hello Alan,

Following the AirNav support link (Trixie guide by abcd567), here is what I checked on my Raspberry Pi 4, Raspberry Pi OS Trixie, rbfeeder 1.0.17, network_mode=false:

- python3 3.13.5; "import asyncore" works (python3-pyasyncore 1.0.2-3 installed).
- mlat-client 0.2.13+trixie1 is installed from the repository (not compiled by me); no package on hold.
- /usr/bin/mlat-client --help runs normally.
- No error related to mlat, asyncore or Traceback in journalctl -u rbfeeder, and nothing about mlat in /var/log/rbfeeder.log.
- The only error at service start was ExecStartPre setfacl status=203/EXEC (acl was not installed). I installed acl: now status=0/SUCCESS. No change for MLAT.
- I tried [mlat] with autostart_mlat=true and mlat_cmd=/usr/bin/python3 /usr/bin/mlat-client; then both commented out; then enable=true. After each rbfeeder restart (waited 5 minutes), "ps aux" shows only dump1090-rb (started with --mlat --forward-mlat --gnss). No mlat-client process is ever started.
- Position (lat, lon, alt=353) is set in rbfeeder.ini and on the website. Station serial EXTRPI736563.

Questions: is MLAT perhaps not enabled for my station on the server side? Which exact condition makes rbfeeder start mlat-client? Is there a debug option to make rbfeeder log why it does not start it?

Thank you for your help,didou

[Runway 31]

MLAT is enabled when you add your exact lat/lon and altitude on the grid of your map

I have very little Linux knowledge but note that your mlat on the ini file is different from the one shown by the reply previous to yours, it reads

[mlat]
#autostart_mlat=true
#mlat_cmd=/usr/bin/mlat-client
enable=true

Try changing yours to that

Hopefully abcd will note the conversation and help out

Alan

[didou]

Hi Alan,

Thank you for your help. Good news: MLAT is now working on my station (EXTRPI736563) after correcting the configuration. It came up last night at about 22:37 and has been stable ever since, for more than 12 hours now.

Thanks also to abcd for following the thread. I'll report back if anything changes, but for now you can consider this solved.

Best regards,