Hi,
After a while I’ve realized that when feeding piaware, rbfeeder do not connect and if I’m feeding rbfeeder, piaware do not connect. It seems that, when I start my Raspberry pi 4, one of those starts first and, remains, blocking the other one. Fr24feed works normaly.
Any clue ?
Thanks
please share the logs for both applications and what exactly happens once you start the services with
sudo systemctl restart piaware
sudo systemctl restart rbfeeder
(one after each other and vice versa and checking the status with journalctl)
Without that detail it’s a mission impossible to check the issue
As mentioned earlier you need to configure rbfeed in network mode.
Just run this:
Automatic installation for dump1090 fa · wiedehopf/adsb-scripts Wiki · GitHub
It will fix your configuration.
1 Like
@foxhunter and @wiedehopf
I’m outside now. When back home I’ll make a trial.
Thanks
This is caused by two dump1090 running (dump1090-fa and integral dump1090 of RB24 feeder). The one which grabs the dongle works, other fails.
To remedy this, block internal dump1090 of RB24 from starting by following method. When running in network mode (network_mode=true), the RB24 feeder will not start its dump1090, and instead use data from dump1090-fa
sudo nano /etc/rbfeeder.ini
Above command will open the config file
Most likely in this file you have:
[client]
network_mode=false
Change it to:
[client]
network_mode=true
After saving above changes, reboot RPi. All should be ok now.
Contents of the file /etc/rbfeeder.ini
[client]
network_mode=true
log_file=/var/log/rbfeeder.log
key=xxxxxxxxxxxx
sn=EXTRPIxxxxxx
lat=xx.xxxx
lon=-xx.xxxx
alt=xxx
sat_used=0
sat_visible=0
[network]
mode=beast
external_port=30005
external_host=127.0.0.1
[mlat]
autostart_mlat=true
#mlat_cmd=/usr/bin/python3.5 /usr/bin/mlat-client
[dump978]
#dump978_enabled=true
2 Likes
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.