Still the same issue with current state of Debian bookworm on Raspberry Pi 4 64-bit.
I’ll pause feeding FlightAware/PiAware and stay on bookworm, meanwhile Flightradar24 gets fed without any issues.
I am feeding Flightaware through Debian Bookworm RC2, by omitting building of fa-mlat-client when I built piaware package from source-code.
Feed to FA is OK, but MLAT is missing.
Thanks and yes, I saw Ubuntu 22.04 (Jammy): Install Pre-built Packages of piaware 8.2 - #11 by abcd567 but hope that eventually there will be a something from PiAware to solve the whole situation, but when reading Debian 12 Bookworm - bump dependencies to uptodate versions of cx_Freeze, zipp and importlib_metadata · Issue #23 · flightaware/piaware_builder · GitHub, this might take quite a while…
Thank you, @abcd567, for amending your build script @ GitHub - abcd567a/piaware-ubuntu-debian-amd64 to encompass Debian 12!
The script sucessfully builds piaware on Debian12, but without mlat capability. This notice is displayed when the script builds piaware on Debian12.
This half-baked built is for those who anyhow want to install piaware on Debian12, and are ready to sacrifice mlat option.
I recommend users to wait till Flightaware releases its source code fully compatible to Debian12.
1 Like
I guess that I found an solution for that. May you can test the changes from my PR?
2 Likes
Just successfully build your PR and can confirm that MLAT-Client is now working on Bookworm.
- Linux 6.1.0-10-arm64 Debian 6.1.37-1 (2023-07-03) aarch64 GNU/Linux
- Pine64 Rock64 running Debian Bookworm.
Is it possible not to use PIP? As from my experience it creates more of a Headache, but I am not a progammer by any means.
Processing /home/adsb/piaware_builder/package-bookworm/mlat-client
Preparing metadata (setup.py) … done
Installing collected packages: MlatClient
DEPRECATION: MlatClient is being installed using the legacy ‘setup.py install’ method, because it does not have a ‘pyproject.toml’ and the ‘wheel’ package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the ‘–use-pep517’ option. Discussion can be found at pypa/pip#8559
Running setup.py install for MlatClient … done
Successfully installed MlatClient-0.2.12
1 Like
Built on Debian 12 amd64 (installed on Oracle VM on Windows 10) using source-code at your fork of piaware_builder (https://github.com/WhoAmI0501/piaware_builder)
In addition to other tools/dependencies, your fork requires to install python3-pip and cmake.
https://flightaware.com/adsb/stats/user/abcd567#stats-133993
cc: @obj @eric1tran
CLICK ON SCREENSHOT TO SEE LARGER SIZE
@PureLinux
cc: @obj @eric1tran
Mlat is enabled, but no stations synchronized even after one hour of running
https://flightaware.com/adsb/stats/user/abcd567#stats-133993
Jul 19 19:42:42 ADSB-Receiver piaware[447]: mlat-client(485): Receiver status: connected
Jul 19 19:42:42 ADSB-Receiver piaware[447]: mlat-client(485): Server status: synchronized with 586 nearby receivers
Jul 19 19:42:42 ADSB-Receiver piaware[447]: mlat-client(485): Receiver: 1669.6 msg/s received 271.9 msg/s processed (16%)
Jul 19 19:42:42 ADSB-Receiver piaware[447]: mlat-client(485): Server: 0.1 kB/s from server 0.1kB/s TCP to server 2.8kB/s UDP to>
Jul 19 19:42:42 ADSB-Receiver piaware[447]: mlat-client(485): Results: 28.8 positions/minute
Jul 19 19:42:42 ADSB-Receiver piaware[447]: mlat-client(485): Aircraft: 34 of 48 Mode S, 74 of 112 ADS-B used
For me the MLAT-Client works.
For me, mlat is connected, but NOT synchronised with any nearby receivers
CLICK ON SCREENSHOT TO SEE LARGER SIZE
Works here as well:
NN@NNN:~ $ uname -a
Linux NNN 6.1.38-v8+ #1663 SMP PREEMPT Mon Jul 17 12:22:57 BST 2023 aarch64 GNU/Linux
NN@NNN:~ $ sudo journalctl -u piaware -n 15
Jul 19 23:39:26 NNN piaware[899]: mlat-client(1693): Route MTU changed to 1500
Jul 19 23:39:26 NNN piaware[899]: mlat-client(1693): Input connected to localhost:30005
Jul 19 23:39:26 NNN piaware[899]: mlat-client(1693): Input format changed to BEAST, 12MHz clock
Jul 19 23:39:26 NNN piaware[899]: piaware has successfully sent several msgs to FlightAware!
Jul 19 23:39:26 NNN piaware[899]: mlat-client(1693): Beast-format results connection with ::1:30104: connection established
Jul 19 23:39:55 NNN piaware[899]: 76 msgs recv'd from dump1090-fa; 76 msgs sent to FlightAware
Jul 19 23:44:55 NNN piaware[899]: 340 msgs recv'd from dump1090-fa (264 in last 5m); 340 msgs sent to FlightAware
Jul 19 23:49:55 NNN piaware[899]: 621 msgs recv'd from dump1090-fa (281 in last 5m); 621 msgs sent to FlightAware
Jul 19 23:54:25 NNN piaware[899]: mlat-client(1693): Receiver status: connected
Jul 19 23:54:25 NNN piaware[899]: mlat-client(1693): Server status: synchronized with 311 nearby receivers
Jul 19 23:54:25 NNN piaware[899]: mlat-client(1693): Receiver: 200.8 msg/s received 39.3 msg/s processed (20%)
Jul 19 23:54:25 NNN piaware[899]: mlat-client(1693): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.4kB/s UD>
Jul 19 23:54:25 NNN piaware[899]: mlat-client(1693): Results: 2.6 positions/minute
Jul 19 23:54:25 NNN piaware[899]: mlat-client(1693): Aircraft: 9 of 10 Mode S, 9 of 9 ADS-B used
Jul 19 23:54:55 NNN piaware[899]: 844 msgs recv'd from dump1090-fa (223 in last 5m); 844 msgs sent to FlightAware
Success on RaspberryPI Model 4 With RaspberryPi OS Bookworm
To: @PureLinux
cc: @obj @eric1tran
Built on 64-bit Raspberry Pi OS Bookworm using source-code at PureLinux’s fork of piaware_builder
STEP-1: Wrote on a spare microSD card latest image of 64-bit Raspberry Pi OS Bullseye
STEP-2: Edited file /etc/apt/sources.list and replaced all occurances of “bullseye” by “bookworm”
STEP-3: Ran following commands
sudo apt update
sudo apt full-upgrade
Steps 2 & 3 above resulted in upgrading RaspberryPi OS from Bullseye to Bookworm. Took about 50 minutes on RPi Model 4.
STEP-4: After upgrade to Bookworm completed, build piaware package cloning source-code by following command:
git clone https://github.com/WhoAmI0501/piaware_builder
NOTE: In addition to other tools/dependencies, your fork requires to install python3-pip and cmake.
https://flightaware.com/adsb/stats/user/abcd567#stats-5252
CLICK ON SCREENSHOT TO SEE LARGER SIZE
https://flightaware.com/adsb/stats/user/abcd567#stats-5252
Thanks all for the testing. We expect to do the official package updates when the official Raspberry Pi OS based on Bookworm is released.
3 Likes
Your graph is “Overall CPU Utilization”.
What is CPU usage of piaware itself? You can know it by command “top”
Please see screenshot below.
The maximum CPU usage is that of dump1090-fa which is standard version of Flightaware.
In above screenshot of “top” you will see 4 instances of mlat-clients running. Some members may wonder why?
The answer is that each instance of mlat-client is run by a different app as follows:
- First instance of mlat-client (fa-mlat-client) was started by piaware
- Second instance of mlat-client was started by Radarbox24 feeder
- Third instance of mlat-client was started by adsbexchange feeder
- Fourth instance of mlat-client was started by adsbfi feeder
I’m trying to collect Debian “bookworm”
mistake could not open the file debian/changelog: No such file or directory
how to safely copy debian/changelog ?
Click link below to download file ChangeLog.bin, and open with a text editor like Notepad. You may need to change file extension from .bin to .txt
,
https://mirror.surf/debian/dists/bookworm/ChangeLog
https://mirror.surf/debian/dists/bookworm/
how and where to copy it?