After every reboot, when I log in, I get the failed message
FR24 MLAT: not running ... failed!
sudo systemctl restart fr24feed
and MLAT is fine, until the next reboot.
This is on a Raspberry Pi 3 with the PiAware image, and then added FR24. It works fine, except for this boot timing issue.
/etc/systemd/system/fr24feed.service
After=network-online.target
Maybe I need to have something about PiAware in the "After" line?
Announcement
Collapse
No announcement yet.
PiAware Compatibility with FR24
Collapse
X
-
It's actually configured by the user unless you run one of the decoder installs (which isn't the case here as dump1090-fa is already installed i'd assume).
You configured it wrong, redo the configuration, follow the instructions on the page.
Or just run the readsb decoder install linked on the page, it fixes most configuration errors (no more dump1090-fa anymore though, it's a replacement).
Leave a comment:
-
If your 'feeder type' is anything other than avr-tcp (or beast-tcp.. I forget) on 30005 that his automation does, or you overrode to something else.
Thats the answer
Leave a comment:
-
PiAware Compatibility with FR24
Good Evening All,
I’m hoping someone can help me out. I have followed Wiedehopf’s guide (https://github.com/wiedehopf/adsb-wi...ADS-B-receiver) to attempt to feed FR24 using my existing dump1090-fa data.
All seems to have gone through okay - however the FR24 status webpage is reporting no flights tracked, and I am getting 2 fails when using the “sudo FR24feed-status” command:
Code:pi@raspberrypi:~ $ sudo fr24feed-status [ ok ] FR24 Feeder/Decoder Process: running. [ ok ] FR24 Stats Timestamp: 2022-04-11 19:23:57. [ ok ] FR24 Link: connected [UDP]. [ ok ] FR24 Radar: T-EGBJ276. [ ok ] FR24 Tracked AC: 0. [FAIL] Receiver: down ... failed! [FAIL] FR24 MLAT: not running ... failed!
Tags: None
Leave a comment: