Do you think there is value to remove the red line at -3 when the feed is coming from an Airspy?
1 Like
The peak signal graph is regularly above that line no matter if you are using airspy or rtl-sdr.
Actually it’s a good maximum for the average airspy signal i would say.
I’m at -10 for the average right now.
It’s just a fixed line, so you have to give it meaning anyway and i don’t see any harm in it.
I could also make a -7 dB line for rtl-sdr probably, which would be my guideline for what the average signal shouldn’t go above.
I’ve rerun the install script and then done the tweaks for my temperature sensor but the ADS-B signal graph isn’t being populated.
You with your extra version 
I’ve merged the new stuff into the extra version.
It’s just two commands but i obviously don’t think of it.
The “tweaks” is the install script from a different version. No need to run the normal install script.
the bash install.sh test installs the version in that git repository, so it overwrites the regular install anyway.
It’s good now, thanks 
wiedehopf - I found if you have a collectd.conf that has been modified post install (in my case, I added graphite plugins) when you go to reinstall the setup complains it cant start collectd because it can’t load modules yet. The workaround for me is to just rename the collectd.conf to collectd.conf.safe, then do the re-install & copy the file back in place & restart. Good to go!
Yeah the graphs assume they are being used standalone with collectd.conf.
I guess i could make a command line switch to not touch collectd.conf.
But the vast majority of users doesn’t modify collectd.conf.
And if they do they usually know how to fix the resulting problem.
Maybe i’ll check if the dump1090 part is in the config and in that case just leave it alone.
That actually sounds like a sensible plan.
1 Like
Yes… I do not want the cluttered ADS-B Receiver Project extra stuff… I just want the bare bone Project Performance Graph… thanks for the tutorial guide.
Rodney
http://rodyeo.dyndns.org/
1 Like
I’ve changed the code a bit, this will affect the aircraft tracked and signal graph for non rtl devices.
So be aware when updating that changing numbers might be slightly changed data collection.
Change the cutoff for considering old aircraft
Aircraft not seen for 30 seconds are ignored when parsing aircraft.json
adsb-receiver project used 15 seconds but that is a little harsh for
cases where the aircraft is not seen for long.
Using a longer timeout is also problematic as aircraft no longer seen
are still counted.
Anyway this is not an exact science.
For more accurate stats, parsing more often than every 60 seconds would
be required, but i'm not sure how to implement that.
I’ve also noticed tmpfs (ramdisk) usage is not counted towards “used” but towards “cache” in the memory graph.
That’s quite misleading because cached memory should basically be available for other uses when required.
But there is no good way to change it so i’ll just leave it as it is for now.
2 Likes
Are there any updates for these graphs im not getting at mo on my Airplay
Also after rssi tab on main skyview page i did try and blanked page
TIA
Regarding the disk graphs, that’s a collectd bug.
If you want you can install a newer version:
wget -O /tmp/collectd.deb http://raspbian.raspberrypi.org/raspbian/pool/main/c/collectd/collectd-core_5.8.1-1.3_armhf.deb
sudo dpkg -i /tmp/collectd.deb
1 Like
Thankyou for them all done,
i was after code for adding rssi to this tab line please
LOL @ my figures rather low at present
In regards to troubleshooting the signal graph, if after the update the graphs still doesn’t show, please show the output of this:
rrdtool info /var/lib/collectd/rrd/localhost/dump1090-localhost/dump1090_dbfs-signal.rrd | grep value -m8
And the output of this:
wget -q http://localhost/dump1090-fa/data/aircraft.json -O /tmp/aircraft.json
head -n5 /tmp/aircraft.json
ds[value].index = 0
ds[value].type = “GAUGE”
ds[value].minimal_heartbeat = 120
ds[value].min = NaN
ds[value].max = 0.0000000000e+00
ds[value].last_ds = “-4.4877094972067”
ds[value].value = -1.2116815642e+02
ds[value].unknown_sec = 0
{ “now” : 1560620009.7,
“messages” : 9110224,
“aircraft” : [
{“hex”:“40133e”,“alt_baro”:2200,“alt_geom”:2300,“gs”:144.5,“track”:63.3,“geom_rate”:64,“squawk”:“4575”,“emergency”:“none”,“lat”:51.756080,“lon”:0.565872,“nic”:8,“rc”:186,“seen_pos”:0.1,“version”:0,“nac_p”:8,“nac_v”:2,“sil”:2,“sil_type”:“unknown”,“mlat”:,“tisb”:,“messages”:16,“seen”:0.1,“rssi”:-4.2},
{“hex”:“405b67”,“alt_baro”:5350,“squawk”:“0505”,“version”:0,“nac_p”:8,“sil”:2,“sil_type”:“unknown”,“mlat”:,“tisb”:,“messages”:11,“seen”:4.0,“rssi”:-6.5},
Let’s check graph generation then:
sudo /usr/share/graphs1090/graphs1090.sh
But i honestly don’t know why the signal graph shouldn’t be working.
I have the impression you just didn’t update yesterday.
I have still no idea what you want.
Oh, looking for code.
That’s discussed in this post from quite some time ago:
Announcing PiAware 3! (Latest version: 3.8.0) - #910 by wiedehopf
all updated now and working thankyou
also updated rssi page which i missed couple months ago
manythanks
john
I’m curious, why did you think the signal graph would change without updating?
It updated, saw it was working then i uninstalled adsb-receiver then it stopped
so not really sure what i did but sure all is ok now
john