I’ll try via Oracle VM. Windows’ Hyperv-V might not be that smart.
1 Like
Even on Debian 10.1.0 amd64 same problem
abcd@debian10:~$ sudo systemctl status piaware
... ... ...
Nov 03 23:27:17 debian10 piaware[514]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --inpu
Nov 03 23:27:18 debian10 piaware[514]: mlat-client(5389): Fatal Python error: initfsencoding: Unable to get the locale encoding
Nov 03 23:27:18 debian10 piaware[514]: mlat-client(5389): ImportError: invalid flags 1554269952 in 'encodings'
Nov 03 23:27:18 debian10 piaware[514]: mlat-client(5389): Current thread 0x00007f54468b6f00 (most recent call first):
Nov 03 23:27:18 debian10 piaware[514]: got EOF from multilateration client
Nov 03 23:27:19 debian10 piaware[514]: fa-mlat-client exited with SIG SIGABRT
.
.
@obj
Too many versions of Python installed. May be wrong version being used???
abcd@debian10:~$ ls /usr/bin/python*
/usr/bin/python /usr/bin/python2.7 /usr/bin/python3.7 /usr/bin/python3.7m /usr/bin/python3-config /usr/bin/python3m-config
/usr/bin/python2 /usr/bin/python3 /usr/bin/python3.7-config /usr/bin/python3.7m-config /usr/bin/python3m
.
abcd@debian10:~$ /usr/bin/python -V
Python 2.7.16
abcd@debian10:~$ /usr/bin/python3 -V
Python 3.7.3
1 Like
Give this a whirl - also with Buster if needed:
sudo rm -rf cx_Freeze-5.1.1
wget https://github.com/anthony-tuininga/cx_Freeze/archive/511f4733e6fb0070409a654cf5e8d2aea2dc5417.zip
unzip 511f4733e6fb0070409a654cf5e8d2aea2dc5417.zip
mv cx_Freeze-511f4733e6fb0070409a654cf5e8d2aea2dc5417 cx-Freeze-5.1.1
1 Like
Well, I was pretty unhappy with my older hardware, the laptop is marginal performer (i5 second gen), my other older desktop is not that much better (i7 860, first gen).
I bid $160 on a Dell Latitude E6540 with an i7-4810MQ and surprisingly I won. I guess is Merry Christmas to me 
PassMark Single Thread Rating: 2069 (CPU Mark 8657) so hopefully will do a better job… than a Pi4
2 Likes
Thanks for the tip to use older source code of cx_Freez.
.
Now it is clear that problem is caused by latest commit of cx_Freez (commit #0ce8086 Oct 26, 2019), and older code (commit #511f473 on Sep 28, 2019) should be used.
I used a slightly different method to clone the old source code of cx_Freez, as shown below:
cd piaware_builder/package-stretch
sudo rm -rf cx_Freeze-5.1.1
git clone https://github.com/anthony-tuininga/cx_Freeze.git cx_Freeze-5.1.1
cd cx_Freeze-5.1.1
git reset --hard 511f473
HEAD is now at 511f473 Ignore files built when using "develop" mode.
cd ../
sudo dpkg-buildpackage -b
.
Result:
abcd@debian10:~$ sudo systemctl status piaware
... ... ...
Nov 04 12:05:06 debian10 piaware[501]: mlat-client(570): Using UDP transport to 70.42.6.224 port 6737
Nov 04 12:05:06 debian10 piaware[501]: mlat-client(570): Listening for Beast-format results connection on port 30105
Nov 04 12:05:06 debian10 piaware[501]: mlat-client(570): Listening for Extended Basestation-format results connection on por
Nov 04 12:05:06 debian10 piaware[501]: mlat-client(570): Input connected to localhost:30005
Nov 04 12:05:06 debian10 piaware[501]: mlat-client(570): Input format changed to BEAST, 12MHz clock
Nov 04 12:05:07 debian10 piaware[501]: mlat-client(570): Beast-format results connection with ::1:30104: connection establis
Nov 04 12:05:11 debian10 piaware[501]: piaware received a message from dump1090-fa!
Nov 04 12:05:29 debian10 piaware[501]: piaware has successfully sent several msgs to FlightAware!
Nov 04 12:05:36 debian10 piaware[501]: 9 msgs recv'd from dump1090-fa; 9 msgs sent to FlightAware
Nov 04 12:10:36 debian10 piaware[501]: 133 msgs recv'd from dump1090-fa (124 in last 5m); 133 msgs sent to FlightAware
3 Likes
You got it my friend 
cxfreeze branching is a dog’s breakfast and things tend to break when a lot of hard-code is employed. It appears as though they’ve been chasing tail on this for quite some time, so what’s one more hack in the meantime I guess.
If you want to take it a step further - can create a patch file (man diff) for sensible-build.sh on the OS switches and show those who are interested how to apply during the process (or as part of). It would be a bit cleaner until (if?) we see new commits on the piaware side with the proper fixes.
2 Likes
.
Please see this post. Waiting for release of version 3.8 
.
1 Like
Work on v3.8 is getting underway now.
4 Likes
I have installed Ubuntu natively on my Latitude E6420 with dual boot under Windows 10.
Then I have installed the dump1090-fa and piaware following the first post (without any fixes for cxfreeze).
Everything worked as a charm, thanks abcd567!
I am testing now the linux version of airspy_adsb and it seems that it doesn’t lose MLAT anymore, since the decoded data doesn’t have to travel over Ethernet anymore…
Great!
Which version of Ubuntu?
Only ver 18.04 (Bionic) does NOT require fix for cx_Freez.
Ver 19.04 and 19.10 (Disco) do require fix for cx_Freez.
Ooops, I forgot to say. Ubuntu 18.04.3 LTS.
1 Like
.
Just like me…
1 Like
I have tried that first and… Debian (netconfig) didn’t auto-recognize the WiFi or the Ethernet!
Dell sold this laptop also with Ubuntu 10, so I figured out that the drivers might be still in the distribution. And indeed, no problems.
I am testing now the linux version of airspy_adsb and it seems that it doesn’t lose MLAT anymore, the Linux chipset/USB drivers are working better than the Windows drivers.
Fixed that for you
Beast data traveling via network are not a problem.
I can run MLAT just fine with beast data from SFO, that’s quite some latency.
It’s not an issue at all.
I mean the Pi3 wouldn’t have been doing anything but handling some data, not running airspy or an rtl dongle, right?
But i don’t know your network, maybe it’s worse than the internet from SFO to me, can’t be excluded as a possibility.
I don’t know if the MLAT fix works anymore on the 19 Disco. I have those errors:
2019-11-27 09:07 EST] got EOF from multilateration client
[2019-11-27 09:07 EST] fa-mlat-client exited with SIG SIGABRT
[2019-11-27 09:08 EST] fa-mlat-client exited with SIG SIGABRT
[2019-11-27 09:08 EST] mlat-client(24395): ImportError: invalid flags 1574241712 in 'encodings'
[2019-11-27 09:08 EST] mlat-client(24395): Current thread 0x00007f8b5cbf7740 (most recent call first):
Try 3.8.0~dev and see if that works
1 Like
I don’t know how to change it to the dev branch. I have used the directions from the first post until now.
Here it is.
NOTE: With dev branch, use buster, not bionic (i.e. use ./sensible-build.sh buster and cd package-buster)
sudo rm -rf piaware_builder
git clone https://github.com/flightaware/piaware_builder.git
cd piaware_builder
git checkout dev
# Branch 'dev' set up to track remote branch 'dev' from 'origin'.
# Switched to a new branch 'dev'
./sensible-build.sh buster
# .... .... ....
# 7df58ec (HEAD, origin/dev) 3.8.0~dev, add buster build support, make stretch build a backport
# Retrieving cxfreeze
# 2019-11-27 11:29:37 URL:https://codeload.github.com/anthony-tuininga/cx_Freeze/tar.gz/6.0 [89326] -> "-" [1]
# Ok, package is ready to be built in ./package-buster
# run 'dpkg-buildpackage -b' there (or move it to a Pi and do so there, or use pbuilder, etc)
cd package-buster
## Install dependencies first, else packe building will fail
sudo apt install libboost-system-dev libboost-program-options-dev libboost-regex-dev libboost-filesystem-dev
# Now build the package
sudo dpkg-buildpackage -b
1 Like
Thanks, I did that. How do I check the version of piaware? I think it went well:
dpkg-deb: building package ‘piaware-dbgsym’ in ‘debian/.debhelper/scratch-space/build-piaware/piawar e-dbgsym_3.8.0~dev_amd64.deb’.
Renaming piaware-dbgsym_3.8.0~dev_amd64.deb to piaware-dbgsym_3.8.0~dev_amd64.ddeb
mv debian/.debhelper/scratch-space/build-piaware/piaware-dbgsym_3.8.0~dev_amd64.deb …/piaw are-dbgsym_3.8.0~dev_amd64.ddeb
dpkg-genbuildinfo --build=binary
dpkg-genchanges --build=binary >…/piaware_3.8.0~dev_amd64.changes
dpkg-genchanges: info: binary-only upload (no source code included)
dpkg-source --after-build .
dpkg-buildpackage: info: binary-only upload (no source included)
Do I need to re-do the dump1090-fa too?
[2019-11-27 12:01 EST] mlat-client(2039): Current thread 0x00007f68b53d2740 (most recent call first):
[2019-11-27 12:01 EST] got EOF from multilateration client
[2019-11-27 12:01 EST] mlat-client(2039): ImportError: invalid flags 1574241712 in 'encodings'
[2019-11-27 12:01 EST] mlat-client(2039): Fatal Python error: initfsencoding: Unable to get the locale encoding
[2019-11-27 12:01 EST] fa-mlat-client exited with SIG SIGABRT