Updated instructions for feeding from piaware 7.2 to FR24?

FlightAware Feature Requests and Ideas
1

Anyone have any “current” instructions for being able to feed from PiAware 7.2 over to FR24? I should be able to use Dump1090-fa but the instructions within the general area only talk about installing a fresh version and not how to link an existing FR24 account to the feed.

A while ago I did see some instructions but they were back in piaware version 6.1. which is I don’t think will work with the current releases.

I need a stable environment since it might take me a couple of weeks to get to the feeder if it crashes and I can’t ssh into it. Am I crazy attempting to feed to multiple vendors? (The only vendor I’m mainly interested in is FlightRadar24)

Thoughts / suggestions?

Thanks,
Eric

2

Hello,

If you follow the steps in point 10 of the instructions made by Wiedehopf then you can indeed feed FR24 over Piaware 7.2

It might be usefuull to have your FR24 sharing key at hand in order to finish the process in one go.

3 
sudo bash -c "$(wget -O - http://repo.feed.flightradar24.com/install_fr24_rpi.sh)"

 

During signup, you will get following message. Please accept auto-config by typing yes and pressing Enter Key

 

CAUTION: Never choose option “receiver=dvbt” OR “1 - DVBT Stick (USB)”. It will result in FR24 feeder installing dump1090-mutability which will create a mess and break your install.

 

4

Thank you… Thank you… Thank you…

Hopefully this build will be more stable than the last time I tried to feed to multiple sites with my feeder. Plan to get it back up on the hill on Friday.

Eric

5

then we all would be crazy. The majority has a huge list of providers where we feed to.

If you have Flightaware (Piaware/dump1090) running properly, FR24 setup script will detect the running dump1090 instance and use it accordingly.

I have done this setup meanwhile > 10 times, never had an issue with it.j

6

Thanks for the words of encouragement…

I previously had a very stable setup running for over 2 years without any crashes. But since the first of the year, I’ve had nothing but trouble keeping a receiver up and running. Between internet and power issues things have been a headache. For the last 6 months the receiver would just hang and I was able to ssh into it and reboot and it was happy but the last failure rendered the device inaccessible.

I tried to re-configure it with the same feeders I previously had but started thinking that maybe there was a conflict going on between them. So, I’ve rebuilt the OS with PiAware 7.2 and with the recent help, I re-installed the FR24 feeder. (I also re-built the Pi with a Geekwork UPS battery module to aid with the crappy power at the site)

Hope to get it back up on the mountain top on Friday…

7

Did you try some investigation what causes the issue?
Normally a Raspberry is not getting stuck without serious reason.

8

The site is located on a mountain top and the power and internet are kind of flaky. That is the reason I’m re-installing the Pi back up at the site with a geekworm UPS designed for a Pi. Hopefully the soft shutdown will preserve the SD card. Also, I’ve reduced the number of feeders from 4 to 2 in the hope there aren’t any conflicts with just 2.

So, the latest build is as close to “off the shelf” as I can get it. with the only the addition of the FR24 feeder.

Cheers,
Eric

9

You could consider using a small SSD instead of a SD card.
That can minimize the risk of a SD card damage.

If you want to keep the SD card, Google for Log2Ram - that is a solution to reduce the write attempts to the SD card for the logfile folder.

The number of feeds should not matter.

10

 

 

If internet is flaky, then number of feeds should matter.

 

11

Why?

If the internet is broken none is working. If not, all are working.
They are all using similar bandwidth except ADSBx which is consuming more depending on the setup.