# Back again

**URL:** <https://discussions.flightaware.com/t/back-again/78663>\
**Category:** ADS-B Flight Tracking\
**Created:** [August 16, 2021, 1:19am UTC](https://discussions.flightaware.com/t/back-again/78663 "2021-08-16T01:19:06Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jlb56](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jlb56/32/133275_2.png) [@jlb56](https://discussions.flightaware.com/u/jlb56)\
**Post date:** [August 16, 2021, 1:19am UTC](https://discussions.flightaware.com/t/back-again/78663/1 "2021-08-16T01:19:06Z")

</div>

Hi all, with Covid lockdowns and plenty of time now, I thought I might set back up my ADSB trackers. I still follow the posts but just some clarifications re best guide to set up now days. I think I can determine that Joe is no longer actively involved, but ABCD etc still going strong. My equipment for testing and tracking will comprise Odroid N2s and RPi 4’s. Still keen to be using the graphs etc and will be feeding Flighaware, flighttrader24 and Opensky. If someone can point me to the current best guides for these set ups. Appreciate the N2’s cant use the standard piaware flight aware set up and believe RPI side of thing, an imminent release of Raspberry PI OS 64, which might suit the N2’s?? Thanks in advance :).

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [August 16, 2021, 1:48am UTC](https://discussions.flightaware.com/t/back-again/78663/2 "2021-08-16T01:48:12Z")

</div>

> [@jlb56](#):
>
> Appreciate the N2’s cant use the standard piaware flight aware set up and believe RPI side of thing, an imminent release of Raspberry PI OS 64, which might suit the N2’s?? Thanks in advance :).

Brows automated install scripts at following GitHub page.

## [https://github.com/abcd567a/piaware-ubuntu20-amd64/blob/master/README.md](https://github.com/abcd567a/piaware-ubuntu20-amd64/blob/master/README.md)

&nbsp;

**Not sure if it will work for Odroid N2s.**  
However **[I have tested and it works on many Hardware/OS](https://discussions.flightaware.com/t/install-piaware-5-0-on-x86-64-machines-and-rpi-armv7l-aarch64/74699)** including following:

**RPI Model 4 (32-bit & 64-bit) Raspbian, Ubuntu, and Kali (armv7l & aarch64)**

&nbsp;

It builds and installs following using **source-code** :  
(1) dump1090-fa  
(2) paware  
(3) dump978-fa  
(4) piaware web

&nbsp;

&nbsp;

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [August 16, 2021, 1:56am UTC](https://discussions.flightaware.com/t/back-again/78663/3 "2021-08-16T01:56:51Z")

</div>

> [@jlb56](#):
>
> Still keen to be using the graphs etc and will be feeding Flighaware, flighttrader24 and Opensky. If someone can point me to the current best guides for these set ups.

&nbsp;

# [Re-imaging Made Easy](https://discussions.flightaware.com/t/re-imaging-made-easy/72347)

### Scroll down to:

- **3.1 - Planefinder**
- **3.2 - Flightradar24**
- **3.3 - Radarbox24** :
- **3.4 - Graphs by @wiedehopf**

### Not included in above How-to:

**ADSBEXCHANGE**

```auto
sudo bash -c "$(wget -nv -O - https://raw.githubusercontent.com/adsbxchange/adsb-exchange/master/install.sh)"  

```

&nbsp;

**OPENSKY NETWORK**

```auto
wget https://opensky-network.org/files/firmware/opensky-feeder_latest_armhf.deb  

sudo dpkg -i opensky-feeder_latest_armhf.deb 

```

---

<div class="post-metadata">

**Author:** ![jlb56](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jlb56/32/133275_2.png) [@jlb56](https://discussions.flightaware.com/u/jlb56)\
**Post date:** [August 16, 2021, 3:08am UTC](https://discussions.flightaware.com/t/back-again/78663/4 "2021-08-16T03:08:27Z")

</div>

> [@abcd567](#):
>
> **Not sure if it will work for Odroid N2s.**  
> However [I have tested and it works on many Hardware/OS](https://discussions.flightaware.com/t/install-piaware-5-0-on-x86-64-machines-and-rpi-armv7l-aarch64/74699) including following:  
> **RPI Model 4 (32-bit & 64-bit) Raspbian, Ubuntu, and Kali (armv7l & aarch64)**

Hey thanks for the reply. I had sus’d out some of those links in research but just wanted some confirmation in what I was looking at was the latest. Re the RPI OS 64, if it works with Raspbian and Ubuntu, you would think it will work with a N2. I will let you know after I throw it on a test unit. With the added extras and re imaging, would you suggest using this procedure, which I imagine is the same as installing it cold?? Oh one thing I forgot to add re equipment, using Airspy R2, so I suppose that nifty script you have made for attaching an Airspy to your rig.

Jeff

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [August 16, 2021, 5:38am UTC](https://discussions.flightaware.com/t/back-again/78663/5 "2021-08-16T05:38:31Z")

</div>

N2 needs a 64bit system, you’ll have issues installing fr24.

> [@abcd567](#):
>
> **OPENSKY NETWORK**
> 
> ```auto
> 
> ```

This will also not work as N2 is aarch64 and not armhf.

RPI OS 64 bit won’t help you either it’s aarch64 just the same.  
You can install multi-arch support to run armhf stuff on aarch but it’s a bit annoying.

Just use an RPi4 if you want to feed fr24 and stuff. Or suffer incompatibilites and a lenghty install process.

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [August 16, 2021, 7:46am UTC](https://discussions.flightaware.com/t/back-again/78663/6 "2021-08-16T07:46:50Z")

</div>

> [@wiedehopf](#):
>
> > [@abcd567](#):
> >
> > **OPENSKY NETWORK**
> 
> This will also not work as N2 is aarch64 and not armhf.

Thanks for pointing out  
Use this one for 64-bit

```auto
wget https://opensky-network.org/files/firmware/opensky-feeder_latest_arm64.deb  

sudo dpkg -i opensky-feeder_latest_arm64.deb  

```

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [August 16, 2021, 7:54am UTC](https://discussions.flightaware.com/t/back-again/78663/7 "2021-08-16T07:54:23Z")

</div>

> [@wiedehopf](#):
>
> N2 needs a 64bit system, you’ll have issues installing fr24.

Try this

```auto
sudo dpkg add-architecture armhf 

sudo apt-get update 

dpkg --print-foreign-architectures 

dpkg --print-architecture 

```

Hopefully after this FR24 32-bit armhf will be installed.

Unfortunately I dont have Odroid N2 to test all this

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [August 16, 2021, 8:02am UTC](https://discussions.flightaware.com/t/back-again/78663/8 "2021-08-16T08:02:27Z")

</div>

> [@abcd567](#):
>
> Unfortunately I dont have Odroid N2 to test all this

You can try with Raspbian OS 64bit if you feel like it, that should behave very similar as it’s aarch64 as well.  
You can use it on a RPi3 or 4 without issues.  
[Index of /raspios\_arm64/images/raspios\_arm64-2021-05-28](https://downloads.raspberrypi.org/raspios_arm64/images/raspios_arm64-2021-05-28/)

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [August 16, 2021, 8:07am UTC](https://discussions.flightaware.com/t/back-again/78663/9 "2021-08-16T08:07:12Z")

</div>

> [@wiedehopf](#):
>
> You can try with Raspbian OS 64bit if you feel like it, that should behave very similar as it’s aarch64 as well.  
> You can use it on a RPi3 or 4 without issues.

All feeder how-tos I have posted above is what I have successfully installed on RPI Model 4 with following OS:  
`2021-05-07-raspios-buster-arm64-lite.img`

&nbsp;

```auto
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.10.17-v8+ #1414 SMP PREEMPT Fri Apr 30 13:23:25 BST 2021 aarch64 GNU/Linux

pi@raspberrypi:~ $ dpkg --print-architecture  
arm64

pi@raspberrypi:~ $ dpkg --print-foreign-architectures
armhf

```

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [August 16, 2021, 8:23am UTC](https://discussions.flightaware.com/t/back-again/78663/10 "2021-08-16T08:23:14Z")

</div>

> [@abcd567](#):
>
> Try this

```auto
sudo dpkg --add-architecture armhf
sudo apt update
sudo apt dist-upgrade
sudo apt install libc6:armhf libstdc++6:armhf libusb-1.0-0:armhf

```

I believe this was required on the N2 to make the airspy armhf binary work.  
But this has now aarch64 as well so it’s not needed for that anymore.  
But it might be needed for the feed client binaries as well.

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [August 16, 2021, 9:16am UTC](https://discussions.flightaware.com/t/back-again/78663/11 "2021-08-16T09:16:12Z")

</div>

> [@wiedehopf](#):
>
> But it might be needed for the feed client binaries as well.

In the " `2021-05-07-raspios-buster-arm64-lite.img`" on RPI Model 4, **both architectures (arm64 and armhf) are enabled by default**, i.e. one does not have to issue command `sudo dpkg --add-architecture armhf `.

Because of above situation, when the bash scripts for feeders tries to install dependencies for a 32-bit (armhf) feeder binary, the apt automatically select dependencies for armhf. User dont have to specify `package_name:armhf`.

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [August 16, 2021, 9:41am UTC](https://discussions.flightaware.com/t/back-again/78663/12 "2021-08-16T09:41:35Z")

</div>

&nbsp;

_CLICK ON IMAGE TO SEE FULL SIZE_

 ![image](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/2/b/2ba5f4910104d7b2b9c9fd8cb1ac169a28c25af7.png)

---

<div class="post-metadata">

**Author:** ![jlb56](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jlb56/32/133275_2.png) [@jlb56](https://discussions.flightaware.com/u/jlb56)\
**Post date:** [August 18, 2021, 8:33am UTC](https://discussions.flightaware.com/t/back-again/78663/13 "2021-08-18T08:33:35Z")

</div>

Wiedehopf, I did try your Raspbian Lite: ADS B receiver install, but it did not work. But scratching the chin, not sure whether that dodgy lead that has been running me around thinking Airspy failures, wasn’t the lead that might have been connected. At the moment, I have 2 PI4’s set up with ABCD’s latest suggestion, but can you install the graphs on such an install. And I think the other thing I was interested in was gain changes and from what I think, you can manually change the gain with your set up, can’t use the auto version as running Airspy.

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [August 18, 2021, 10:31am UTC](https://discussions.flightaware.com/t/back-again/78663/14 "2021-08-18T10:31:16Z")

</div>

> [@jlb56](#):
>
> And I think the other thing I was interested in was gain changes and from what I think, you can manually change the gain with your set up, can’t use the auto version as running Airspy.

No auto for airspy indeed.  
And you’d have to be more specific than “does’t work” …

---

<div class="post-metadata">

**Author:** ![jlb56](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jlb56/32/133275_2.png) [@jlb56](https://discussions.flightaware.com/u/jlb56)\
**Post date:** [August 18, 2021, 10:59pm UTC](https://discussions.flightaware.com/t/back-again/78663/15 "2021-08-18T22:59:21Z")

</div>

I am thinking it was the lead that caused the problem now, so won’t give exact details re your install. But once I have this current install where I like it, I will try your scripts again 🙂 . Working on the current install, that so far is looking like what I might be happy with. Have installed graphs and great to see this feature has survived from the mutability days. Optimizing gain though and as mentioned, Airspy, so no auto feature, but find the task of tweaking things to get the best invigorating …(you should see what I tweak with my Blitzortung lightning detector systems…)

I have tried your manual method script (will be shown shortly) to get a percentage of strong messages and got this result possible error highlighted??:  
grep -sh /run/{dump1090,dump1090-fa,readsb}/stats.json -e ‘’ | jq ‘.total.local | ((.accepted | add), .strong\_signals, .signal, .noise)’ | xargs -n4 echo | awk ‘{printf “\nPercentage of strong messages: %.3f\nSignal: %.1f\nNoise: %.1f\n”, $(2) \* 100 / $(1), $(3), $(4)}’  
_ **-bash: jq: command not found** _

Percentage of strong messages: nan  
Signal: 0.0  
Noise: 0.0

Now in your github description, you state you can use your graph data of: **““the percentage given in graphs1090,””** What data field are you getting this percentage from, can’t see something obvious that is “measuring message strength” ?

---

<div class="post-metadata">

**Author:** ![jlb56](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jlb56/32/133275_2.png) [@jlb56](https://discussions.flightaware.com/u/jlb56)\
**Post date:** [August 18, 2021, 11:12pm UTC](https://discussions.flightaware.com/t/back-again/78663/16 "2021-08-18T23:12:34Z")

</div>

Another graph question. Has anyone tried to install these graph scripts on a Radarcape set up??

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [August 19, 2021, 5:54am UTC](https://discussions.flightaware.com/t/back-again/78663/17 "2021-08-19T05:54:19Z")

</div>

> [@jlb56](#):
>
> Has anyone tried to install these graph scripts on a Radarcape set up??

Radarcape doesn’t run dump1090 or readsb so no data source for the graphs.  
The radarcape has limited CPU so you can either try it or run it on another device that uses the radarcape as datasource.  
In both cases you’d install like readsb like this and tell it to get the data via network instead of an SDR: [Automatic installation for readsb · wiedehopf/adsb-scripts Wiki · GitHub](https://github.com/wiedehopf/adsb-scripts/wiki/Automatic-installation-for-readsb#remote-data-source-radarcape-or-similar-configure-net-only-and-a-receiver-with-another-ip-address-as-a-data-source)

> [@jlb56](#):
>
> _ **-bash: jq: command not found** _

Well install jq.

With the airspy all this gain stuff will not work.  
Rough guideline is to put the weakest signal (cyan line in graphs1090) around -30 dBFS.  
You’ll likely notice that going up an down in gain a bit will not influence the results at all with the airspy, it’s pretty tolerant to running a wide range of gains.

Have you increased -e to 8 or 9?  
That’s one of the things compared to the defaults you will want to do if you have enough CPU for it.

---

<div class="post-metadata">

**Author:** ![jlb56](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jlb56/32/133275_2.png) [@jlb56](https://discussions.flightaware.com/u/jlb56)\
**Post date:** [August 19, 2021, 6:32am UTC](https://discussions.flightaware.com/t/back-again/78663/18 "2021-08-19T06:32:51Z")

</div>

> [@wiedehopf](#):
>
> Well install jq.

What is jq??? I do not eat or sleep linux scripts sorry, thats why I ask the community.

> [@wiedehopf](#):
>
> Have you increased -e to 8 or 9?

Sorry you lost me there, might have remembered that 2 years ago … lol

> [@wiedehopf](#):
>
> Rough guideline is to put the weakest signal (cyan line in graphs1090) around -30 dBFS.

I take it that line is in the ADBS signal level, only data field with negative numbers, but how do I alter something to get that level?

Jeff

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [August 19, 2021, 6:43am UTC](https://discussions.flightaware.com/t/back-again/78663/19 "2021-08-19T06:43:39Z")

</div>

> [@jlb56](#):
>
> What is jq??? I do not eat or sleep linux scripts sorry, thats why I ask the community.

Then google how to install packages on the system you’re running.  
Google what jq is …  
It says command not found: jq

Anyhow it won’t be useful as with airspy you can’t get a percentage of strong messages.

> [@jlb56](#):
>
> Sorry you lost me there,

The -e setting is in the airspy configuration file, read the explanations in the config file: [GitHub - wiedehopf/airspy-conf: Configure airspy\_adsb for use with readsb or piaware.](https://github.com/wiedehopf/airspy-conf#airspy-conf)

> [@jlb56](#):
>
> I take it that line is in the ADBS signal level, only data field with negative numbers, but how do I alter something to get that level?

Change the gain in the airspy configuration.

---

<div class="post-metadata">

**Author:** ![foxhunter](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/foxhunter/32/113733_2.png) [@foxhunter](https://discussions.flightaware.com/u/foxhunter)\
**Post date:** [August 19, 2021, 7:28am UTC](https://discussions.flightaware.com/t/back-again/78663/20 "2021-08-19T07:28:11Z")

</div>

> [@jlb56](#):
>
> Has anyone tried to install these graph scripts on a Radarcape set up??

It’s not working because significant things are missing.  
Radarcape is running rcd as data source and does not provide any of the data in the way graphs1090 can use it. Most of the things are running in RAM to reduce SDCard write attempts.

Beside that the device does not have a sufficient CPU for doing that.  
You will need to setup a seperate device which collects the information via the network port.

It should work running a Raspberry with dump1090 or readsb in network mode, capturing the stream from the Radarcape network port.

[Next page](https://discussions.flightaware.com/t/back-again/78663.md?page=2)
