Piaware 2.1-5

Worked like magic here. Upgrade complete, logs are clean, traffic is flowing.

Upgrade seems to have gone like a dream here too…

I upgraded and I am now seeing these statements:

[2015-12-24 14:37 CST] mlat(2527): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2015-12-24 14:38 CST] mlat(2527): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
[2015-12-24 14:38 CST] mlat(2527): Beast-format results connection with localhost:30104: [Errno 111] Connection refused

I returned to v2.1-2 and the messages went away.

Marty

upgrade your dump1090

I am running the latest dump1090-mutability v1.15~dev, so there is nothing to upgrade.

That is a change that dates back to 2.1-3. You need to either reconfigure dump1090 to listen on port 30104 for beast mlat data, or reconfigure piaware to feed to a port of your choice. See ads-b-flight-tracking-f21/piaware-2-1-3-released-t36047.html

Upgrade to 2.1-5 completed, restarted and running nicely without issue :smiley:

Merry Christmas Oliver.

hello all, so i got a 5" touch screen for my piaware, can’t wait to get it up and going.( need a larger sd card)… can someone direct me to some info in regards to installing it with flightaware/ dump1090… i seen afew vids on it but they don’t explain much… thanks

Installation instructions

flightaware.com/adsb/piaware/build

Did not encounter any issues upgrading to the latest version.

there is no info there for what i asked …

That link tells you how to build a piaware install running on a Pi. If that’s not what you’re looking for, what are you trying to build?

I think they might be asking for instructions on how to display the information on the touchscreen?

Seems to be using less CPU than 2.1-3 did, a Good Thing.

looking for instructions on ruining the touch screen with piaware running dump1090…i know i have to install the software for the screen and piaware. just not sure what i will need to tweak to make it work.

I guess you will need to configure X to use the touchscreen, and start a web browser to point at the dump1090 map. Not sure how useable that will be.

Morning all,

Noticed over the Christmas period that

a) The new Station Stats UI now show MLAT vs ADSB vs Other stats
b) My daily stats have plummted, from c2900 birds per day, to c800

Just updated to PiAware 2.1-5 - now Mut shows zero aircraft, and the console in the Station Stats on FA shows Mut isnt sending anything to FA…

"
[2015-12-31 07:55 GMT] 0 msgs recv’d from dump1090-muta (0 in last 5m); 0 msgs sent to FlightAware

"

The BEAST port change required for 2.1.3 was done some weeks ago, and showed some (if reduced) birds before upgrade to 2.1.5.
I take it the “Send command to device > Upgrade and restart PiAware” wont have reset this, it shouldnt have done anything to mut?

Also, running Mut 1.14 - can someone point me at upgrade instructions for 1.15 etc?

Thanks - and an early Happy New Year! :slight_smile:

Hi all,

So, upgraded to PiAware 2.1-5 succesfully.

Upgraded (via Build) Mutability to 1.15 dev.

My earlier query regarding drop in reports is no doubt due to the changes in the stats as reported by Obj earlier.
(2900 down to 800 birds/day??)

However, Mut’s still not showing any aircraft… ?

(I went through Mut’s config again, and as Obj mentioned elsewhere, the updated BEAST port for pA is now the default, so shouldnt be that).

Will wait and see if any birds appear (sure there’s a song there somewhere… :wink: ) .

FWIW… (NB 0 msgs recvd…)

[2015-12-31 09:37 GMT] Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --results beast,connect,localhost:30104 --results ext_basestation,listen,30106 --results beast,connect,feed.adsbexchange.com:30005 --udp-transport 70.42.6.198:9917:3212521599
[2015-12-31 09:37 GMT] mlat(2396): fa-mlat-client 0.2.4 starting up
[2015-12-31 09:37 GMT] mlat(2396): Using UDP transport to 70.42.6.198:9917
[2015-12-31 09:37 GMT] mlat(2396): Listening for Extended Basestation-format results connection on port 30106
[2015-12-31 09:37 GMT] mlat(2396): Input connected to localhost:30005
[2015-12-31 09:37 GMT] mlat(2396): Beast-format results connection with localhost:30104: connection established
[2015-12-31 09:37 GMT] mlat(2396): Beast-format results connection with feed.adsbexchange.com:30005: connection established
[2015-12-31 09:37 GMT] 0 msgs recv’d from dump1090-mutab; 0 msgs sent to FlightAware
[2015-12-31 09:42 GMT] 0 msgs recv’d from dump1090-mutab (0 in last 5m); 0 msgs sent to FlightAware

Update

Been running for a while now…

[2015-12-31 09:52 GMT] 7 msgs recv’d from dump1090-mutab (0 in last 5m); 7 msgs sent to FlightAware
[2015-12-31 09:57 GMT] 26 msgs recv’d from dump1090-mutab (19 in last 5m); 26 msgs sent to FlightAware
[2015-12-31 10:02 GMT] 26 msgs recv’d from dump1090-mutab (0 in last 5m); 26 msgs sent to FlightAware
[2015-12-31 10:07 GMT] mlat(2396): Receiver status: connected
[2015-12-31 10:07 GMT] mlat(2396): Server status: not synchronized with any nearby receivers
[2015-12-31 10:07 GMT] mlat(2396): Receiver: 0.2 msg/s received 0.0kB/s from receiver
[2015-12-31 10:07 GMT] mlat(2396): Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
[2015-12-31 10:07 GMT] mlat(2396): Aircraft: 0 of 0 Mode S, 0 of 0 ADS-B used
[2015-12-31 10:07 GMT] 29 msgs recv’d from dump1090-mutab (3 in last 5m); 29 msgs sent to FlightAware
[2015-12-31 10:12 GMT] 40 msgs recv’d from dump1090-mutab (11 in last 5m); 40 msgs sent to FlightAware

The lack of sync for MLAT reported at 10:07 looks interesting, though the Stats page status alert doesnt show it as not being synced, so I guess it got sync in the end.

pA is reporting msgs (very few), but Mut (using the /gmaps UI) only occasionally shows 1 or 2 birds intermittantle, but never with any position data.

Hoping this isnt a physical antenna issue (external roof line) following the bad weather… dont really fancy getting up there!