Piaware amd64 / x86_64

Is there a Linux amd64 / x86_64 version from piaware available, for example for the UP Board ?

Prepackaged? No. But you should be able to build from source on x86(_64) debian systems fairly easily: github.com/flightaware/piaware_builder

How good is your Linux command line knowledge?
You will need to be basically comfortable with that first.

I built a package on an Intel Atom thin client by following this thread (and adapting the file names to suit - check what is created with the ‘ls’ (LS) command).
post177419.html#p177419
You will get some files ending with something like dump1090-mutability_1.15~dev_x86.deb instead of e.g. dump1090-mutability_1.15~dev_armhf.deb

I first made a vanilla install of Debian and added the user ‘Pi’ and built from there.

This is from memory of some months ago and I am on holiday so can’t check/validate anything.

Ah, obj posted whilst I was typing my reply :wink:

Ok, i think i need a little bit more help OBJ,and it’s only for Airspy not Dump1090
This what i tried:


sudo apt-get install git-core
mkdir git
cd git
git clone https://github.com/flightaware/piaware_builder.git
cd piaware_builder
chmod +x sensible-build.sh
sh sensible-build.sh jessie
cd package-jessie
dpkg-buildpackage -b

but then i get:
dpkg-buildpackage: source package piaware
dpkg-buildpackage: source version 3.0.3
dpkg-buildpackage: source distribution stable
dpkg-buildpackage: source changed by Oliver Jowett oliver@mutability.co.uk
dpkg-buildpackage: host architecture amd64
dpkg-source --before-build package-jessie
dpkg-checkbuilddeps: Unmet build dependencies: tcl8.6-dev autoconf python3-dev (>= 3.2) python3-venv libz-dev dh-systemd
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)

You need to install the build prerequisites that it lists (sudo apt-get install tcl8.6-dev autoconf python3-dev python3-venv libz-dev dh-systemd)

Ok thanks OBJ that did the trick


dpkg-buildpackage -b
cd ..
sudo dpkg -i piaware_3.0.3_amd64.deb
sudo apt-get install -fy
sudo /etc/init.d/piaware start

But id did not start piaware


sudo piaware-config -status
piaware is not running

try a reboot.

That did’nt help, i think the problem is v3.0.3 itself

check logs
/var/log/piaware.log
/var/log/dump1090.log
/var/log/messages
lsusb

etc

The jessie package is set up for systemd, try systemctl start piaware
(I don’t think the init.d script should even be installed, but I can’t remember how that is set up)

Also I think piaware-status might be broken. Check if piaware is running by hand.

/var/log/piaware.log


Aug  3 12:56:48 ipv6 piaware[13972]: ****************************************************
Aug  3 12:56:48 ipv6 piaware[13972]: piaware version 3.0.3 is running, process ID 13972
Aug  3 12:56:48 ipv6 piaware[13972]: your system info is: Linux ipv6 4.4.0-ubi3-amd64 #1 SMP Debian 4.4.13-1 (2016-06-17) x86_64 GNU/Linux
Aug  3 12:56:50 ipv6 piaware[13972]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Aug  3 12:56:50 ipv6 piaware[13972]: Connection with adept server at piaware.flightaware.com/1200 established
Aug  3 12:56:50 ipv6 piaware[13972]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Aug  3 12:56:50 ipv6 piaware[13972]: FlightAware server certificate validated
Aug  3 12:56:50 ipv6 piaware[13972]: encrypted session established with FlightAware
Aug  3 12:56:51 ipv6 piaware[13972]: logged in to FlightAware as user guest
Aug  3 12:56:51 ipv6 piaware[13972]: ADS-B data program 'airspy_adsb' is listening on port 30005, so far so good
Aug  3 12:56:51 ipv6 piaware[13972]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
Aug  3 12:56:51 ipv6 piaware[13972]: Started faup1090 (pid 14014) to connect to airspy_adsb
Aug  3 12:56:52 ipv6 piaware[13972]: piaware received a message from airspy_adsb!
Aug  3 12:56:52 ipv6 piaware[13972]: piaware has successfully sent several msgs to FlightAware!
Aug  3 12:57:23 ipv6 piaware[13972]: 343 msgs recv'd from airspy_adsb; 343 msgs sent to FlightAware
Aug  3 12:57:26 ipv6 piaware[13972]: piaware (process 13972) is shutting down because it received a shutdown signal (SIGTERM) from the system...
Aug  3 12:57:26 ipv6 piaware[13972]: faup1090 exited with SIG SIGTERM
Aug  3 12:57:26 ipv6 piaware[13972]: piaware (process 13972) is exiting...
Aug  3 12:57:26 ipv6 piaware[14060]: ****************************************************


Looks fine? It ran for 45 seconds normally and then was terminated (reboot?)

Working now:


Aug  3 16:54:54 ipv6 piaware[1663]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Aug  3 16:54:54 ipv6 piaware[1663]: Connection with adept server at piaware.flightaware.com/1200 established
Aug  3 16:54:55 ipv6 piaware[1663]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Aug  3 16:54:55 ipv6 piaware[1663]: FlightAware server certificate validated
Aug  3 16:54:55 ipv6 piaware[1663]: encrypted session established with FlightAware
Aug  3 16:54:55 ipv6 piaware[1663]: logged in to FlightAware as user guest
Aug  3 16:54:55 ipv6 piaware[1663]: ADS-B data program 'airspy_adsb' is listening on port 30005, so far so good
Aug  3 16:54:55 ipv6 piaware[1663]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 300$
Aug  3 16:54:55 ipv6 piaware[1663]: Started faup1090 (pid 1708) to connect to airspy_adsb
Aug  3 16:54:56 ipv6 piaware[1663]: piaware received a message from airspy_adsb!
Aug  3 16:54:56 ipv6 piaware[1663]: piaware has successfully sent several msgs to FlightAware!
Aug  3 16:55:27 ipv6 piaware[1663]: 325 msgs recv'd from airspy_adsb; 325 msgs sent to FlightAware
Aug  3 17:00:27 ipv6 piaware[1663]: 3286 msgs recv'd from airspy_adsb (2961 in last 5m); 3286 msgs sent to FlightAware
Aug  3 17:05:27 ipv6 piaware[1663]: 6202 msgs recv'd from airspy_adsb (2916 in last 5m); 6202 msgs sent to FlightAware



Only logged in as guest. and can’t claim

Ok did some edit on /etc/piaware.conf and working perfect with v3.0.3


Restarting piaware (via systemctl): piaware.service.
allow-auto-updates             yes                            # value set at /etc/piaware.conf:9
allow-manual-updates           yes                            # value set at /etc/piaware.conf:12
flightaware-password           <hidden>                       # value set at /etc/piaware.conf:11
flightaware-user               <hidden>                       # value set at /etc/piaware.conf:10
mlat-results-format            beast,listen,31003             # value set at /etc/piaware.conf:8


Aug  4 13:22:27 ipv6 piaware[4137]: mlat-client(4165): Receiver status: connected
Aug  4 13:22:27 ipv6 piaware[4137]: mlat-client(4165): Server status:   synchronized with 84 nearby receivers
Aug  4 13:22:27 ipv6 piaware[4137]: mlat-client(4165): Receiver: 2513.5 msg/s received      334.4 msg/s processed (13%)
Aug  4 13:22:27 ipv6 piaware[4137]: mlat-client(4165): Server:      1.5 kB/s from server    0.1kB/s TCP to server     4.1kB/s UDP to server
Aug  4 13:22:27 ipv6 piaware[4137]: mlat-client(4165): Results:  693.2 positions/minute
Aug  4 13:22:27 ipv6 piaware[4137]: mlat-client(4165): Aircraft: 87 of 115 Mode S, 49 of 134 ADS-B used


I will certainly recommend this thread for other users. Thanks!

I am sorry to bring up an old thread, but I am having some issues.

I am trying to compile piaware onto an x86 machine. I am able to compile everything, but the DEB file doesn’t install dump1090 or anything else OTHER than piaware. Am I doing something wrong? It is trying to install the 3.5.0 version of the software.

Thanks in advance!

That is normal; the piaware package is just the data feeder, you need to also provide a source for the data such as dump1090.

You can build a dump1090-fa package from github.com/flightaware/dump1090-fa

Thanks for the quick reply! I was under the impression that dump1090 was included as it was referenced inside the package. Maybe this is just the code that allows it to work with dump1090 though.

Anyways I was able to get it working. Thanks again!

Just for info: today I built amd64 version. With standard settings I received error message about signature.
To build it you need to modify:
from
dpkg-buildpackage -b
to:
dpkg-buildpackage -b -uc -us

@MDA0803
Thanks for the helpful info.

Did you install dump1090-fa on amd64/x86_64? Did it also need -uc -us?