Feeding from PiAware

Hi,
I have a Raspberry Pi and Flight Aware set up, using PiAware 3.5.3 with ADSBExchange feeding capability.

I have edited the piaware-config file but I am getting errors like

Oct 16 14:02:18 piaware piaware[1963]: warning: /boot/piaware-config.txt:132: unrecognized option adsbx-lon
Oct 16 14:02:18 piaware piaware[1963]: warning: /boot/piaware-config.txt:140: unrecognized option adsbx-nickname
Oct 16 14:02:18 piaware piaware[1963]: warning: /boot/piaware-config.txt:150: unrecognized option adsbx-feederid
Oct 16 14:02:18 piaware piaware[1963]: warning: /boot/piaware-config.txt:160: unrecognized option send978
Oct 16 14:02:18 piaware piaware[1963]: warning: /boot/piaware-config.txt:167: unrecognized option adsbxemail

I have been going round in circles but cant seem to feed a custom port, or get these errors away.

Anything I can do ???

Regards

Nick

 

Hi,

Why don’t you upgrade to 3.6.3 and follow the instructions from the 3.6.3 thread. Setup is straightforward and works out of the box without getting into confit files edit.

I bet it will be easier than trying to fix a 3.5.3 setup.

Olivier

 

Cheers for the replies:

I used the FA image ( with built in ADSBExchange addon ) as it was the first one I used for FlightAware, the one I contribute to. I found it never censored mil data/planes as the others did,
this is the reason I stuck with it, have not deleted it as I may not get it back again. (When viewed from my internal viewer)

Upgrading may disable something, however, I may just prepare another sd card, try get it going , if I can then migrate to that.

I just thought it may have been easier to ask why I can do it, see if I can get it going, then still stay with the same build I have used for the past few months.

If it can't be done then fair enough, I wont have to contribute to ADSBExchange and just stick with FA.

I run VRS when I started , on my computer , but I never leave it on and started getting emails asking if the feed was still alive, hence I want to use my Pi, feed FA as usual but also feed AE
as well, and at least contribute something in the process, or not as the case may be.

I am happy just to use FA, no loss to me, however, I may just be a missing link somewhere and have at least something to contribute..or not now if I can't get it working.

Cheers anyways, I'll have to stay as I am...
Regards

Nick

Just on FlightAware.

 

Hi Nick. Well, in part I guess it depends on what traffic you want to see. In our area, for example, I see LOTS of traffic on ADSBX that FA filters out -- like all military, for example. If you wanna see who owns the B757 overhead -- and don't care about some of the other "interesting" stuff around you FA will fill your need well. Personally? I could give a sh?t about the airliners but find the stuff fascinating that FA intentionally throws into the bit bucket. So, YMMV, as they say!

I'm certainly no LINUX guru. In fact, although I understand networking pretty well, I've had some challenges similar to yours. But I'll say that the folks here on the forum have been very helpful and I've found several ways to do almost anything I wanted to do. When FA broke one of my feeders the folks here pointed me in the right direction to fix it. When the creeps at Google stopped letting us have height data I was the recipient of help once again. So, in the end it's all about what you want to do. Personally? I think the challenge is absolutely worth the benefit -- which is why I have four feeders. (These things are almost "dirt cheap.") And, I'm learning a bit about LINUX along the way. If I can do it so can you!

Rick

 

You're using the FlightAware ADSBx combo image? People dig through logs and find the most random shit to post about. Mind boggling.

I have guys sending me 'error' logs and reformatting Pi images because it writes some normal log entries but for some reason they have a freak out about it.

ADSBx adds some ADSBx specific fields to the piaware config file, so of course PiAware isn't going to understand them. Why is this an issue, everything should work.

Apps write logs for all kinds of stuff. Unless FlightAware specifically changed so anything put in the file that isn't FlightAwarew specific is ignored or not written to ENV.

I have a 3.6.3 base FlightAware image that I ran the script setup method on and it works flawlessly.

You may need to run update to get package lists.

sudo apt update
sudo apt upgrade

sudo apt-get install git
git clone https://github.com/adsbxchange/adsb-exchange.git
cd adsb-exchange
chmod +x setup.sh
sudo ./setup.s

And please install ZT and join ADSBx network. No support will be given in the future unless I can just fix it and move on. Spending days on forums explaining things to those how can't explain the problem or don't understand what they are telling us is counter productive. Days get wasted on user error.

https://www.zerotier.com/download.shtml


curl -s https://install.zerotier.com/ | sudo bash

sudo zerotier-cli join c7c8172af18c605f

Email me the output of below. james (at) adsbexchange.com

sudo zerotier-cli status
sudo zerotier-cli listnetworks

 

I got my pi with an FA image pre-installed, then setup ASDBx with the following:
sudo apt-get install git
git clone https://github.com/adsbxchange/adsb-exchange.git
cd adsb-exchange
chmod +x setup.sh
sudo ./setup.sh

I feel this is a super easy process for a newbie like me. 5 commands on top of an out-of-the-box system, that’s pretty good to get to feed ADSBx.
I always had the intention to feed ADSBx. I ended up with an FA image by accident, following the “how to feed” here and bought a bundle that came with an FA image.

When I get more experience I’ll probably give a go at an install from scratch though.

This thread started on a FA image question, hence my experience sharing

 

You can feed FA, up to you.

If you don't feed FA (using a base Raspbian image) then you need to install dump1090 first, and set it to run at boot.

https://www.raspberrypi.org/downloads/raspbian/

Use stretch lite or desktop. Either way works, all things are entered in terminal.

Then install ADSBx feeder using script method.

That might need to be added to the tutorials, since some people seem to not want to feed FA.

 

That's make sense. What do you mean you 'got it pre installed with FlightAware"?

Are you using the FlightAware image from FlightAware or are you using the FlightAware ADSBx combo that was on the ADSBexchange.com forum.


If you are using the FlightWare ADSBx image that was on the forum then it had ADSBx already setup and you didn't need to run :

sudo apt-get install git
git clone https://github.com/adsbxchange/adsb-exchange.git
cd adsb-exchange
chmod +x setup.sh
sudo ./setup.sh


This is the problem, 100% user error then they can't explain what is going on.

 

1) If you used the image that was on ADSBx: https://www.adsbexchange.com/forum/...e-working-mlat-requires-manual-update.618956/

Then all you had to do was fill out the text file variables and it would work. All but MLAT anyway. Fixing Google breaking MLAT is detailed on the forum. One line of code to edit.

--

2) If you used the FlightAware image from FlightAware: https://flightaware.com/adsb/piaware/build

Then you run the script setup and enter the correct parameters.

--


If you used #1 then ran the script setup - you overwrote a bunch of files and probably messed the image up.


We've gotten to the problem there are multiple ways to setup a feeder, people start mixing them up, they can't explain what they did because they have no idea what they did.

We have 5 pages of forums trying to help them when they aren't explaining what they did correctly, which leads to solutions that don't fix the problem (if there even is a problem).

 

"I am happy just to use FA, no loss to me, however, I may just be a missing link somewhere and have at least something to contribute..or not now if I can't get it working.

Cheers anyways, I'll have to stay as I am...
Regards"


--


What?! Seriously.

If you are getting those errors then the piaware-config.txt you used is from the forum, but you are on a base FlightAware image, that's the only way I can see you got those variables in PiAware config file.

Then you ran the script method setup, which probably worked unless you didn't fill in the items it asked for.

So .. who knows what's working. It's probably feeding ADSBx.

I have no idea. and we can't help because you can't explain what you did where it makes sense.

https://www.adsbexchange.com/forum/...with-fa-piaware-3-6-3-keyboard-screen.624272/

Use this tutorial. re-image the SD with latest FightAware PiAware. You liked the post ... so you've read it.

 

First, let me confirm I have no problem and I understand the difference between FA image and the ADSBx image.

I bought a kit with pi, power supply usb stick, antenna and FA 3.6.2 image. Then I setup ADSBx with setup.sh and it works. I feed custom port 51345 and can see my traffic ;-)

 

Cheers guys, It's sorted now. It must have been sorted before, however , I am a bit impatient and the receiver never updated quick enough. All good now, feeding FA and ADSBE from the Pi at the same time, just as I intended.
Patience is a virtue, and I ain't got any.
I read all the instructions as people described above and it worked.
So, it wasn't what was told to me, it was me , and I admit it.
Regards

Nick

 

The receiver is called EGNJ if anyone is interested, Located in Kingston upon Hull, NE coast of the UK

 

https://customglobal4.adsbexchange.com/VirtualRadar/desktop.html#

Receiver -> EGNJ

Cheers!