You’re missing something to feed piaware on 30005.
It could be dump1090-mut, airspy_adsb, modesdeco, VRS, Planeplotter etc.
How do you plan to feed the data?
It’s a vanilla install of Debian Jessie on a Sheevaplug (armel) and piaware built from github.
I have an RTL2838 dongle attached and hoped it would start feeding to FlightAware, much like my R-Pi did !
I think I need to edit some config file as piaware-config comes up empty.
Nigel.
Try building/installing the dump1090-fa package from github.com/flightaware/dump1090
The piaware package is just the data feeding bit, it doesn’t include a source for the data (the piaware sdcard image has piaware + dump1090-fa + some infrastructure packages to do the network config etc)
OK, one step forward…
Built it but then an error
root@sheeva:/home/pi/git# ls
dump1090 dump1090_3.1.0_all.deb dump1090-fa_3.1.0_armel.changes dump1090-fa_3.1.0_armel.deb piaware_builder
root@sheeva:/home/pi/git# dpkg-buildpackage -b
tail: cannot open ‘debian/changelog’ for reading: No such file or directory
dpkg-buildpackage: error: tail of debian/changelog gave error exit status 1
cd dump1090 first
then run
dpkg-buildpackage -b
OK, success !
Thanks for the help guys, it’s quite satisfying to get there in the end.
The packages will build on an Armel box with a little persuasion.
It won’t install as user ‘pi’ even with sudo - had to run as SU or root.
It was my bad and missed the dpkg -i …
Installed a few more missing dependencies and it’s away now.
Do I need some kind of local config file to make changes to?
Need some sleep now.
Nigel.
For piaware:
It’ll read configuration from /etc/piaware.conf
You can check the current config (including defaults) with “piaware-config -showall”
The defaults are generally fine.
Many of the settings only apply to sdcard installs.
For dump1090-fa:
Look at /etc/default/dump1090-fa
Great, thanks.
g’night
I did a scratch load of the new piaware and it works and looks great. I have just one problem. I’m seeing a few of the following messages during the course of a day…
timed out waiting for alive message from FlightAware, reconnecting…
I have an older B+ V1.2 and a new version 3. The version 3 exhibits the problem more frequently. And I never logged that error when I was running the older versions of the software.
I checked and both iwconfig shows Power Management:off so the network adapters aren’t snoozing. And they are maybe 10 feet away from my wireless network switch.
anyone have any suggestions?
Here is all the log from the drop through reconnecting…
Oct 23 21:08:28 piaware piaware[502]: timed out waiting for alive message from FlightAware, reconnecting…
Oct 23 21:08:28 piaware piaware[502]: multilateration data no longer required, disabling mlat client
Oct 23 21:08:29 piaware piaware[502]: fa-mlat-client exited normally
Oct 23 21:08:29 piaware piaware[502]: reconnecting in 57 seconds…
Oct 23 21:08:29 piaware piaware[502]: mlat-client(709): Disconnecting from localhost:30005: Lost connection to multilateration server, no need for input data
Oct 23 21:08:29 piaware piaware[502]: mlat-client(709): Exiting on connection loss
Oct 23 21:09:26 piaware piaware[502]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Oct 23 21:09:26 piaware piaware[502]: Connection with adept server at piaware.flightaware.com/1200 established
Oct 23 21:09:27 piaware piaware[502]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Oct 23 21:09:27 piaware piaware[502]: FlightAware server certificate validated
Oct 23 21:09:27 piaware piaware[502]: encrypted session established with FlightAware
Oct 23 21:09:27 piaware piaware[502]: logged in to FlightAware as user XXXXXXXXXXXXX
Oct 23 21:09:27 piaware piaware[502]: multilateration data requested
Oct 23 21:09:27 piaware piaware[502]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.198:9746:113899870
Oct 23 21:09:28 piaware piaware[502]: mlat-client(1210): fa-mlat-client 0.2.6 starting up
Oct 23 21:09:28 piaware piaware[502]: mlat-client(1210): Using UDP transport to 70.42.6.198 port 9746
Oct 23 21:09:28 piaware piaware[502]: mlat-client(1210): Listening for Beast-format results connection on port 30105
Oct 23 21:09:28 piaware piaware[502]: mlat-client(1210): Listening for Extended Basestation-format results connection on port 30106
Oct 23 21:09:28 piaware piaware[502]: mlat-client(1210): Input connected to localhost:30005
Oct 23 21:09:28 piaware piaware[502]: mlat-client(1210): Input format changed to BEAST, 12MHz clock
Oct 23 21:09:28 piaware piaware[502]: mlat-client(1210): Beast-format results connection with 127.0.0.1:30104: connection established
Could be a network problem anywhere between your Pi and FA.
It’s working as intended in that piaware notices that the connection has wedged and reconnects.
The “World Charts” are out of date, but the “Sectional Charts” are up to date in FAA regions. Different database maintainers, I guess.
There has been some talk about version 3.2.0 coming out shortly, what are the main changes to expect?
3.2.0 is actually done and released, mostly to support a FlightFeeder release. There aren’t many changes so I’m not sure if it’s worth releasing it more widely or whether we’ll just skip to 3.3.0
And is 3.2.0 also available for x86(_64) Jessie ?
It takes a few commands to build it
git clone github.com/flightaware/piaware_builder.git (You may need to resolve dependencies)
./sensible-build.sh jessie
cd package
dpkg-buildpackage -b
sudo dpkg -i …/piaware_3.2.0_armhf.deb (the file name will change for x86 OSes). You can see it at the end of the build
sudo piaware-config -restart (to restart and update the website)
Hi all,
After talking with Oliver, I’m wanting to build 3.2.0 - for the “manual mac address” feature if nothing else…
Im new to building these things, though it looks relatively straight forwards and I get the general idea.
So, lets say - on a Pi Zero running pA 2.xx and ADSBReceiver image - I run those build commands…
Does that build 3.2.0 on that local machine - do I then have to install that “built” package, or does it update whats there automatically?
How would I basically clean out everything currently on that device SD, and install a clean pA 3.2?
building package piaware' in …/piaware_3.1.0_amd64.deb’.
Not available it’s still 3.1.0
master branch is still 3.1.0, you need the 3.2.0 tag if you want 3.2.0
(nb: reason 3.2.0 is not generally released is that the time required to do the release outweighs the benefits right now; for the same reason I can’t provide much/any support for building or running it; you should probably stick with 3.1.0 unless you know what you’re doing)
Can we add the ‘Heywhatsthat’ range rings into our piaware3.1 configs?
if so how?
I know it will involve getting a json file from “http://www.heywhatsthat.com/api/upintheair.json?id=${HEYWHATSTHATVIEWID}&refraction=0.25&alts=3048,12192”
where does that need to go, and what other changes are needed to make piaware use it?
Hi
I can and do currently run v2.1 of piaware
My feed is being sent to flight aware and I can see the result on the website
I am running this on gentoo rPi machine
When I installed v3 I get the following error
rpgen piaware # piaware
invalid command name "receiver_host_and_port"
while executing
"receiver_host_and_port piawareConfig"
(procedure "setup_faup1090_vars" line 17)