thanks!
managed to install it into the system!
waiting for arm64 deb file
Yes, you are 100% right.
64-Bit Beast-Splitter “beast-splitter_7.1_arm64.deb” Uploaded to Github
To install
sudo wget -O /etc/apt/sources.list.d/abcd567a.list https://abcd567a.github.io/rpi/abcd567a.list
sudo wget -O - https://abcd567a.github.io/rpi/KEY.gpg | sudo apt-key add -
sudo apt update
sudo apt install beast-splitter
sudo nano /etc/default/beast-splitter
In above file, changed
ENABLED=“no”
to
ENABLED=“yes”
Saved file (Ctrl+O) Closed (Ctrl+X)
sudo reboot
pi@raspberrypi:~ $ journalctl -u beast-splitter -n 20
-- Journal begins at Fri 2022-02-04 05:04:04 EST, ends at Sat 2022-02-19 21:29:23 EST. --
Feb 19 21:28:34 raspberrypi beast-splitter[562]: 0.0.0.0:30005: accepted a connection from 127.0.0.1:50660 with settings R
Feb 19 21:28:34 raspberrypi beast-splitter[562]: 127.0.0.1:50660: connection closed
Feb 19 21:28:35 raspberrypi beast-splitter[562]: 0.0.0.0:30005: accepted a connection from 127.0.0.1:50662 with settings R
Feb 19 21:28:43 raspberrypi beast-splitter[562]: [::]:30005: accepted a connection from [::1]:33096 with settings R
Feb 19 21:28:44 raspberrypi beast-splitter[562]: 0.0.0.0:30005: accepted a connection from 10.0.0.22:33840 with settings R
Feb 19 21:28:58 raspberrypi beast-splitter[562]: 0.0.0.0:30005: accepted a connection from 127.0.0.1:50666 with settings R
Feb 19 21:29:01 raspberrypi beast-splitter[562]: [::]:30005: accepted a connection from [::1]:33118 with settings R
Feb 19 21:29:01 raspberrypi beast-splitter[562]: [::1]:33118: settings changed to RCdfj
Feb 19 21:29:01 raspberrypi beast-splitter[562]: [::]:30005: accepted a connection from [::1]:33120 with settings R
Feb 19 21:29:01 raspberrypi beast-splitter[562]: [::1]:33120: settings changed to RCdfjV
Feb 19 21:29:01 raspberrypi beast-splitter[562]: 0.0.0.0:30005: accepted a connection from 127.0.0.1:50692 with settings R
Feb 19 21:29:01 raspberrypi beast-splitter[562]: 127.0.0.1:50692: settings changed to RCdfJV
Feb 19 21:29:08 raspberrypi beast-splitter[562]: 127.0.0.1:50666: connection closed
Feb 19 21:29:08 raspberrypi beast-splitter[562]: 0.0.0.0:30005: accepted a connection from 127.0.0.1:50700 with settings R
Feb 19 21:29:16 raspberrypi beast-splitter[562]: 0.0.0.0:30005: accepted a connection from 127.0.0.1:50710 with settings R
Feb 19 21:29:16 raspberrypi beast-splitter[562]: 127.0.0.1:50710: connection closed
Feb 19 21:29:18 raspberrypi beast-splitter[562]: 127.0.0.1:50700: connection closed
Feb 19 21:29:18 raspberrypi beast-splitter[562]: 0.0.0.0:30005: accepted a connection from 127.0.0.1:50718 with settings R
Feb 19 21:29:19 raspberrypi beast-splitter[562]: 0.0.0.0:30005: accepted a connection from 127.0.0.1:50724 with settings R
Feb 19 21:29:19 raspberrypi beast-splitter[562]: 127.0.0.1:50724: settings changed to RCdfj
1 Like
Hello , I have a Mode-S Beast from the receiver
Flightaware , I bought a RockPi-S 512 MB and want to connect it to the receiver and run the beast-splitter . How do I get it hooked up and running? If you can go step by step, I’m not very good with linux commands.
(1) Write to microSD card of Rockpi-s, Bullseye OS such as Armbian 22.11 Bullseye.
(2) Next install dump1090-fa and beast-splitter from Flightaware repository by following commands:
wget https://flightaware.com/adsb/piaware/files/packages/pool/piaware/f/flightaware-apt-repository/flightaware-apt-repository_1.1_all.deb
sudo dpkg -i flightaware-apt-repository_1.1_all.deb
sudo apt-get update
sudo apt-get install beast-splitter
sudo apt-get install dump1090-fa
sudo apt-get install piaware
(3) Next enable beast-splitter to start automatically at boot:
sudo nano /etc/default/beast-splitter
In above file, change
ENABLED=“no”
to
ENABLED=“yes”
Save file (Ctrl+O) Closed (Ctrl+X)
sudo reboot
(4) Check status:
sudo journalctl -u beast-splitter -n 20
Seems following file has error introduced when you were editing it:
/etc/default/beast-splitter
Please post output of following command:
cat /etc/default/beast-splitter
Please see the red arrow in screenshot below. While editing to make:
ENABLED="yes"
you added an extra " at the end, making it
ENABLED="yes""
Please remove this extra "
Save file
Restart beast-splitter
Check status
Do NOT install dump1090-fa on Rockpi-s. I told this by mistake. If you have already installed it, please disable it by fillowing commands
sudo systemctl stop dump1090-fa
sudo systemctl mask dump1090-fa
`
This OK now. No more extra " after ENABLED="yes"
After saving above file, did you give following commands? If yes, then what are outputs of 2nd & 3rd commands below?
sudo systemctl restart beast-splitter
sudo systemctl status beast-splitter
sudo journalctl -u beast-splitter -n 20
Repeated error messages about failure to connect to port 30104. The port 30104 receives mlat results feedback
In file /etc/default/beast-splitter , see the last line which has this part:
--connect localhost:30104:R
cat /etc/default/beast-splitter
# Configuration for beast-splitter.
# This is a shell-script fragment.
# Lines beginning with "#" are ignored.
# Set to "yes" to allow starting beast-splitter with this configuration.
ENABLED="yes"
# Input options for beast-splitter.
# This tells beast-splitter where to read data from.
# You should provide one of --net or --serial here
INPUT_OPTIONS="--serial /dev/beast"
#INPUT_OPTIONS="--net remotehost:remoteport"
# Output options for beast-splitter.
# This tells beast-splitter where to send output to,
# either by establishing an outgoing connection (--connect)
# or by accepting inbound connections (--listen)
OUTPUT_OPTIONS="--listen 30005:R --connect localhost:30104:R"
I should probably start a new topic, but I thought I’d start here since my issue, which I’ll outline below, only started since I recently updated my Pi OS to Bullseye in addition to the latest PiAware version 8.2.
I was running Stretch initially, with dump1090-mutability so I could run the FR24 feeder software along with PiAware 6.0. I also had the tar1090 interface installed which was my regular go-to for viewing the flights on my feeder setup at home(Big thanks to @abcd567 for the great step-by-step instructions, and @wiedehopf of course for the tar1090 interface, much preferred over piaware interface to me). I also host a FlightFeeder at my workplace at the local airport.
My issue is, since updating everything with a fresh install, I can no longer see details under the FMS SEL section of each flight. Whereas before the new installation I could see that info for most flights (using the tar1090 interface in my web browser.)
Is there something I may have done wrong, or perhaps an mis-configuration that I could somehow correct to get this info back? Otherwise, everything else is working as it should from what I can see.
Thanks in advance for anyone who can point me in the right direction!
abcd567, thank you very much for your help, for the step by step instructions !!!
If you want to get rid of the 30104 error messages, you can do this in two ways:
Option-1: By installing piaware data feeder:
sudo apt install piaware
Option-2: If you dont want to install piaware data feeder, then by blocking mlat feed-back:
In file /etc/default/beast-splitter , edit last line which is given below:
(It is long line. Scroll right to see in full)
OUTPUT_OPTIONS="--listen 30005:R --connect localhost:30104:R"
and delete --connect localhost:30104:R, so that it becomes:
OUTPUT_OPTIONS="--listen 30005:R"
After editing, Save file, and restart beast-splitter. Five 5 minutes after restart, check status by systemctl cmd and log by journalctl command.
Debian 12 x64 bookworm (Raspberry Pi OS) does not support installation from the repository beast-splitter??
Следующие пакеты имеют неудовлетворённые зависимости:
beast-splitter : Зависит: libboost-regex1.74.0-icu67 но он не может быть установлен
What are the outputs of these cpmmansas?
unme -a
lsb_release -a
cat /etc/os-release