Graphs for dump1090 -- my version with install script

I’d suggest going to Raspbian Buster, seems there is an issue with the Stretch repository.

You can just re-image with the new 3.8.0 piaware sd-card.

I am happy to have a go but if I were to re-image I would be concerned that I might over write a system that has been collecting and storing data without interruption for a year.
Does Buster run on 3B?

cat /etc/apt/sources.list

No difference

sudo sed -i -e 's?http://flightaware.com/mirror/raspbian/raspbian/?http://mirrordirector.raspbian.org/raspbian/?' /etc/apt/sources.list

Did you type or copy paste this command?

Always copy and paste, so I re-ran in case I had made an error.

cat /etc/apt/sources.list

#deb Index of /raspbian stretch main contrib non-free rpi
#Uncomment line below then ‘apt-get update’ to enable ‘apt-get source’
deb-src Index of /raspbian stretch main contrib non-free rpi

I manually editted sources.list using nano so now have
sources.list is now

deb Index of /raspbian stretch main contrib non-free rpi
#Uncomment line below then ‘apt-get update’ to enable ‘apt-get source’
deb-src Index of /raspbian stretch main contrib non-free rpi

But no change, packages not available

It was commented out with the #?
That would explain the issue, i didn’t even see that before.

Run again:

sudo apt update

Then try again.
I have no clue why that line would be commented out ever.

Sorted, thanks for your help. Lovely graphs and I look forward to trying other projects of yours.

absolutely as you can see it on my 3B:

PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

and the output of cat /proc/device-tree/model && echo:
`

Raspberry Pi 3 Model B Rev 1.2

`

Do you have any idea why that line was commented out?

Do you have any idea why that line was commented out?

No idea at all. I have gone back through my backups and can see that the file has never been changed since the first install.
Thanks again for your time.

1 Like

I recently re-imaged standalone UAT978 site# 101266 to move up to v3.8.0 from v3.7.0.1.
Then installed graphs using graphs1090.

I now see a 404 error every minute in the collectd log. How can I resolve this error?

pi@piaware978:~ $ journalctl -u collectd --no-p
-- Logs begin at Fri 2020-01-31 18:17:40 PST, end at Mon 2020-02-03 16:47:24 PST. --
Jan 31 18:36:34 piaware978 systemd[1]: Condition check resulted in Statistics collection and monitoring daemon being skipped.
Jan 31 18:36:44 piaware978 systemd[1]: Starting Statistics collection and monitoring daemon...
Jan 31 18:36:44 piaware978 collectd[2400]: plugin_load: plugin "syslog" successfully loaded.
Jan 31 18:36:44 piaware978 collectd[2400]: plugin_load: plugin "rrdtool" successfully loaded.
Jan 31 18:36:44 piaware978 collectd[2400]: plugin_load: plugin "table" successfully loaded.
Jan 31 18:36:44 piaware978 collectd[2400]: plugin_load: plugin "interface" successfully loaded.
Jan 31 18:36:44 piaware978 collectd[2400]: plugin_load: plugin "cpu" successfully loaded.
Jan 31 18:36:44 piaware978 collectd[2400]: plugin_load: plugin "aggregation" successfully loaded.
Jan 31 18:36:44 piaware978 collectd[2400]: plugin_load: plugin "match_regex" successfully loaded.
Jan 31 18:36:44 piaware978 collectd[2400]: plugin_load: plugin "df" successfully loaded.
Jan 31 18:36:44 piaware978 collectd[2400]: plugin_load: plugin "disk" successfully loaded.
Jan 31 18:36:44 piaware978 collectd[2400]: plugin_load: plugin "python" successfully loaded.
Jan 31 18:36:45 piaware978 collectd[2400]: Systemd detected, trying to signal readyness.
Jan 31 18:36:45 piaware978 systemd[1]: Started Statistics collection and monitoring daemon.
Jan 31 18:36:45 piaware978 collectd[2400]: Initialization complete, entering read-loop.
Jan 31 18:36:45 piaware978 collectd[2400]: HTTP Error 404: Not Found
Jan 31 18:36:46 piaware978 collectd[2400]: Exiting normally.
Jan 31 18:36:46 piaware978 collectd[2400]: collectd: Stopping 5 read threads.
Jan 31 18:36:46 piaware978 systemd[1]: Stopping Statistics collection and monitoring daemon...
Jan 31 18:36:46 piaware978 collectd[2400]: collectd: Stopping 1 write threads.
Jan 31 18:36:46 piaware978 collectd[2400]: rrdtool plugin: Shutting down the queue thread.
Jan 31 18:36:46 piaware978 systemd[1]: collectd.service: Succeeded.
Jan 31 18:36:46 piaware978 systemd[1]: Stopped Statistics collection and monitoring daemon.
Jan 31 18:36:54 piaware978 systemd[1]: Starting Statistics collection and monitoring daemon...
Jan 31 18:36:54 piaware978 collectd[2938]: plugin_load: plugin "syslog" successfully loaded.
Jan 31 18:36:54 piaware978 collectd[2938]: plugin_load: plugin "rrdtool" successfully loaded.
Jan 31 18:36:54 piaware978 collectd[2938]: plugin_load: plugin "table" successfully loaded.
Jan 31 18:36:54 piaware978 collectd[2938]: plugin_load: plugin "interface" successfully loaded.
Jan 31 18:36:54 piaware978 collectd[2938]: plugin_load: plugin "cpu" successfully loaded.
Jan 31 18:36:54 piaware978 collectd[2938]: plugin_load: plugin "aggregation" successfully loaded.
Jan 31 18:36:54 piaware978 collectd[2938]: plugin_load: plugin "match_regex" successfully loaded.
Jan 31 18:36:54 piaware978 collectd[2938]: plugin_load: plugin "df" successfully loaded.
Jan 31 18:36:54 piaware978 collectd[2938]: plugin_load: plugin "disk" successfully loaded.
Jan 31 18:36:54 piaware978 collectd[2938]: plugin_load: plugin "python" successfully loaded.
Jan 31 18:36:54 piaware978 collectd[2938]: Systemd detected, trying to signal readyness.
Jan 31 18:36:54 piaware978 systemd[1]: Started Statistics collection and monitoring daemon.
Jan 31 18:36:54 piaware978 collectd[2938]: Initialization complete, entering read-loop.
Jan 31 18:36:54 piaware978 collectd[2938]: HTTP Error 404: Not Found
Jan 31 18:37:54 piaware978 collectd[2938]: HTTP Error 404: Not Found
Jan 31 18:38:54 piaware978 collectd[2938]: HTTP Error 404: Not Found
Jan 31 18:39:54 piaware978 collectd[2938]: HTTP Error 404: Not Found
Jan 31 18:40:54 piaware978 collectd[2938]: HTTP Error 404: Not Found
Jan 31 18:41:54 piaware978 collectd[2938]: HTTP Error 404: Not Found
Jan 31 18:42:54 piaware978 collectd[2938]: HTTP Error 404: Not Found
Jan 31 18:43:54 piaware978 collectd[2938]: HTTP Error 404: Not Found
Jan 31 18:44:54 piaware978 collectd[2938]: HTTP Error 404: Not Found
Jan 31 18:45:54 piaware978 collectd[2938]: HTTP Error 404: Not Found
Jan 31 18:46:54 piaware978 collectd[2938]: HTTP Error 404: Not Found
Jan 31 18:47:54 piaware978 collectd[2938]: HTTP Error 404: Not Found
Jan 31 18:48:54 piaware978 collectd[2938]: HTTP Error 404: Not Found
Jan 31 18:49:54 piaware978 collectd[2938]: HTTP Error 404: Not Found

It’s not an issue besides logging.
You can remove the line with the dump1090-fa URL from /etc/collectd/collectd.conf and then restart collectd or reboot.

Done.

Thank you. :sunglasses:

1 Like

Hi @widehopf and great people of this forum…

I have 4 diferent receivers working in diferent locations… in the last year i´ve experiment SD cards failures so i lost my history graphics so, i have an idea and request…

There is any chance to get a script, or maybe better some addon integrated to graphs1090 to upload a backup of the data used to a webserver via FTP or something similar, maybe every 24hrs or something like that so in case of a sd card failure we dont lose our data?

Thankyou very much

I don’t personally need it and not many people would use it, so i don’t feel to inclined to write such a script.

Also it depends very much where you want to upload the data to.
Easiest would be another RPi or linux computer you have ssh access to.
In that case it would be as easy as a crontab that runs scp -r

And then copying that back and everything … if you want to do sth like that you should be able to do it yourself in the first place.
A script won’t help much in other words.

I can give you some pointers i suppose, maybe you can manage setting it up yourself.

You can do this really easily. I use a cron job to call a script once each night that rsyncs whatever data to a NAS drive.

The script just contains lines like this for each directory I want to copy:

sudo rsync -av /var/lib/collectd/ /mnt/backup/adsb/

If you only want to backup graph data that’s all you need and can run it direct from cron.

1 Like

Since I have started to use an Airspy R2 some 3 months ago, noticed that messages > 3db do not appear on my ADS-B Message Rate graph. Any ideas?

Thanks…

image

That data comes from the dump1090 decoder which isn’t being used when dump1090 is in net only mode. It’s not quite so critical with the airspy, since it can handle strong signals much better than the rtl dongles.

Thanks for the quick reply!

Will experiment with increasing gain a point or two, see what happens over a couple of days.

Currently using gain of 19 with OPTIONS= -v -f 1 -p -w 5 -e 8.5 -t 300.

Also using Uputronics ceramic preamp

1 Like

In theory dump1090 could collect this data from remote messages, but currently it doesn’t and I think the airspy is using a different scale for signal strength anyway so…

1 Like

Thanks, yes gain at 19 now, can go up to 21 max setting.

Gain isn’t too critical with the airspy.
“Typical” signal levels for an airspy at 20 MHz sample rate:

Targeting around -24 to -30 for the weak signal graph normally gives good results.
With the sample rate at 12 MHz, you might want to make that between -18 and -24.

1 Like

Quick question here, what is the deal with the many false messages I get

Could this be cellphone interference?
Or is it maybe just the airport nearby with aircrafts down on the runway sending around tons of signals that never fully decode to anything meaningful or the nearby alps reflecting all sorts of real positions in random ways?

I’ve just setup a new pi 4 and see that the new version of graphs has a minimum time range of 2 hours. Is that configurable? I’d like to have the option of the 1 hour period if its possible.

Scroggie