Announcing PiAware 3.8.1!

So, if I am running a Pi 3B+ with the Stretch PiAware image, and have successfully updated to 3.8.0 - is there any benefit to reimaging with the new Buster image?

I kind of have everything configured the way I want it, so it would be a medium-annoying amount of work to redo everything… Just wondering if it would be worth the effort.

Current config is the 3B+ > FlightAware Pro Stick > FlightAware 1090 Filter > about 2’ of coax > FlightAware 1090 antenna (hanging from a string inside a north-facing window)

Or, should I just buy a Pi4 and new dongle, filter, antenna and set up a second station? :wink:

Eventually, I plan to move the antenna to the roof, but the challenge is that the best position would be at the peak of the roof on the west end of the house, while the only place I could put the Pi (without drilling a hole in the house somewhere) would be in the garage, on the ground floor on the east end. That would mean a run of 80-100 feet of coax. Point being, if I am going to do that, I am going to need a bias-tee powered LNA at the antenna, which means a different dongle…so…

Thanks for any thoughts on the matter!

Also, if I use cable like this: Amazon.com, How would I attach an LNA at the antenna? I would hate to use a couple of pigtail adapters. Would it be worthwhile in that case to put the amplifier at the dongle end?

Mount the Pi in a weather proof box under eve near to the antenna and have only a short coax.

Connect the Pi to your network with Ethernet cable and power the Pi with Power over Ethernet (PoE).

Here is a build using PoE

There is much discussion on this forum.

S

I have thought about that, but honestly I doubt I will do it. In my use case, it is the greater of the many potential evils.

In the “con” column:

  • I don’t currently have PoE capability, So I would need to come up with a PoE capable switch or router. (or, a PoE injector, I guess)

  • Most of my house is WiFi - the nearest ethernet connection (including routing the wire inside the house) would be 40 or 50 feet farther than the potential coax run.

  • I’m not thrilled with the concept of going up on my roof in the first place (I have an almost debilitating fear of heights), so the idea of having to go up & down a ladder to 30 feet above ground level for maintenance issues doesn’t appeal to me.

  • I travel most weeks for my job and am only home on the weekend. When my SD card failed a couple of months ago I was able to call my wife and have her swap it out with another as I was trying to troubleshoot from afar. No way she’s going up a ladder to do that.

So, for me, I need a system that is mostly accessible from within the house. I appreciate the suggestion though!

1 Like

In the short to medium term, no need to upgrade - stretch will still get security updates and so on for some time yet, I expect. If you don’t need any of the updates in Buster, and you don’t need the newer kernels (e.g. for Pi 4 support) then stretch will be fine.

Perfect, thank you. That’s exactly the level of detail I was looking for!

If I have to rebuild due to some other reason I will go with the new image, but otherwise, I’ll stick with what I’ve got.

:+1: “if it ain’t broke, don’t fix it”

Where’s the fun in THAT??? :smiley:

“If it ain’t broke, don’t fi… ooh what happens if I edit this?!.. Erm, oh!” :grin:

That cable is very good, so it’s not necessary to have the LNA at the antenna.

Due to the better filtering users have still reported better reception using an external filtered LNA and dongle instead of the Flightaware Prostick+.
For example this combination would work for you:
https://rtl-sdr.com/new-product-rtl-sdr-blog-1090-mhz-ads-b-lna/
https://www.amazon.com/NooElec-NESDR-SMArTee-SDR-R820T2-Based/dp/B079C3FHPG

That way you don’t need to tweak the software to enable the bias-t or use an extra bias-t.
I’m personally not a fan of the uputronics amp and the performance in most cases is a bit worse, but it’s not too bad either.

You also might want to add the backports repository for Stretch:

vi /etc/apt/sources.list.d/debian-backports.list

Add this line:

deb http://httpredir.debian.org/debian stretch-backports main contrib non-free

Add the trusted key:

apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 04EE7237B7D453EC

and run apt-get update. All as user root, otherwise use sudo.

Why would you do this on the piaware sd-card?
Not going to work.

Ah, good to mention. I’m on “the ADS-B Receiver Project”, which is Raspbian GNU/Linux 9.11 (stretch).

While not ideal performance wise, it’s nice to be able to ‘service’ the receiving station anytime of day or night, with no regard for weather conditions, etc.

I’m not doing to badly with my indoor station. It’s either this or nothing.

Hi. My raspberry p3b refuses to work with versions 3.7.x and 3.8.
Stable only works 3.6.3. With other versions, a message appears just about every minute

“Problem fetching data from dump1090. AJAX call failed (timeout: timeout).
Maybe dump1090 is no longer running? The displayed map data will be out date”

Some time later my Raspberry rebooted. After a few reloads it no longer works.
Only after rewriting the sd card does it work again.

Does this mean that the last running stable version of the Raspberry Pi 3B remains only 3.6.3?

Does it continue updating the aircraft though?
Or does the error stay?

Maybe your sd-card is just damaged and 3.6.3 has been working by chance.

You can always use Raspbian Buster Lite and install piaware/dump1090-fa via the packages as another option.

Anyhow if you want to further debug the problem, you will need ssh access to the system:
For Beginners - How-to SSH to RPi - Setup Putty in Windows

Otherwise it’s just guessing what could be going wrong.

With ssh you can check several logs, lighttpd and dump1090-fa would be the first ones to check: Debug commands · wiedehopf/adsb-wiki Wiki · GitHub

No, current versions work fine on a 3B.

I own a raft of Pis. Two Pi4, two Pi3, a Pi2, a Pi1b, and two Pizero-W for a total of 8 devices. I’ve found out the hard way that SDCard reliability is a definite cause of odd behaviours on the Pis. I’ve had two of my Pis run for years without issue, and I have had others that were crashing randomly until I used a different SD card. I have also had two of my ADSB listener PIs have SD cards that died in the past two weeks and those were behaving weirdly for the past while…

@Tiboh In your instance, I would strongly recommed you use a new SDcard for that Pi, as I would suspect that the card is misbehaving somehow. Taking a complete disk image is a recommended step as well, though if the card is misbehaving that might cause the card to stop responding as well.

Thank you all for trying to help me. Enough to create a file ssh.txt and PiAware started to run stable.

Does this mean that for ver 3.8.0, fetching SkyView/SkyAware from another computer on the same network requires SSH ENABLED on RPi?