What did you already do?
Anyway installing my graphs is explained on the github page i linked.
It's a different version of graphs, i based them on the adsb receiver graphs but made several improvements and no fancy web portal is necessary.
Announcement
Collapse
No announcement yet.
Automated Installation of Dump1090-Mutability, Data Feeders, and Performance Graphs
Collapse
This topic is closed.
X
X
-
Odd. I thought I had done that before at the prompting of abcde....but now I'm not sure.
This is the output I received:
$ wget -O /tmp/collectd.deb http://raspbian.raspberrypi.org/rasp...-1.3_armhf.deb
--2019-06-16 17:10:10-- http://raspbian.raspberrypi.org/rasp...-1.3_armhf.deb
Resolving raspbian.raspberrypi.org (raspbian.raspberrypi.org)... 93.93.128.193, 2a00:1098:0:80:1000:75:0:3
Connecting to raspbian.raspberrypi.org (raspbian.raspberrypi.org)|93.93.128.193|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://mirrors.gigenet.com/raspbian/...-1.3_armhf.deb [following]
--2019-06-16 17:10:10-- http://mirrors.gigenet.com/raspbian/...-1.3_armhf.deb
Resolving mirrors.gigenet.com (mirrors.gigenet.com)... 69.65.16.171, 2001:1850:f000:f000:f000:f000::
Connecting to mirrors.gigenet.com (mirrors.gigenet.com)|69.65.16.171|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1040512 (1016K) [application/octet-stream]
Saving to: '/tmp/collectd.deb'
/tmp/collectd.deb 100%[===================>] 1016K 1.32MB/s in 0.8s
2019-06-16 17:10:11 (1.32 MB/s) - '/tmp/collectd.deb' saved [1040512/1040512]
pi@PiAware24:~ $ sudo dpkg -i /tmp/collectd.deb
(Reading database ... 57466 files and directories currently installed.)
Preparing to unpack /tmp/collectd.deb ...
Unpacking collectd-core (5.8.1-1.3) over (5.7.1-1.1) ...
Setting up collectd-core (5.8.1-1.3) ...
Processing triggers for systemd (232-25+deb9u11) ...
Processing triggers for man-db (2.7.6.1-2) ...
pi@PiAware24:~ $
What URL would I use now to pull the graphs?
Do I need to reboot?
Thanks for all the help you have been.
Leave a comment:
-
disk usage not working is caused by the current collectd version.
you can install a new version like this:
Code: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
Graphs for readsb / dump1090-fa / dump1090 (based on dump1090-tools by mutability) - wiedehopf/graphs1090
It will overwrite the adsb receiver version of graphs and you'll have to use another URL to access the graphs.
Also you would want to remove the old automatic graph generation (sudo rm /etc/cron.d/adsb-receiver-performance-graphs)
You can also of course look at how i included the WiFi bandwidth in the graph and modify the adsb receiver shell script.
Leave a comment:
-
Are the graphs configurable in any way?
I moved my feeder Pi up to that attic a few hours ago.
Disc Bandwidth 19-06-16 at 4.24.14 PM.png
I know I am feeding because I have checked my stats but, my bandwidth is only showing for eth and I'm now connected via WiFi, not Ethernet.
Disk usage is showing but disk I/O has no data.
I've rebooted a couple of times too.
Leave a comment:
-
Just a thought: FR24 can fork dump1090 from Flightaware github, and simply remove the logo if it is offending for them. Then they can compile it and use with their feeder.
Or may be I can do above forking, remove Flightaware logo, and name the fork "dump1090-generic" ... just kidding, dont want to get involved into this
Leave a comment:
-
Yeah it would be nice if that branding was optional.
On the other hand they are paying for the code to be maintained.
If you know it doesn't change who you are feeding, it really doesn't matter.
That bar at the top is a little annoying though and for my personal use i normally change it.
Leave a comment:
-
The dump1090-fa is a bit more advance than mutability ver 1.15, is regularly maintained & updated, and has a prettier map and aircraft table layout.
The main issue with dump1090-fa to be officially used by other tracking site is that it is not "Generic" like mutablity, as its map carries logo of a competetor "Flightaware", even though its source code has been made open source by Flightaware.Last edited by abcd567; 2019-06-12, 19:27.
Leave a comment:
-
Well 1.15 is no longer maintained either.
Mutability moved on to developing dump1090-fa and is no longer fixing bugs or problems in dump1090-mutability.
The fact that it still works fine doesn't change that fact.
There is quite some information that is not displayed in dump1090-mutability
Stuff like mach number, indicated airspeed and selected altitude.
It's not supported by all transponders and needs to be actively queried by ATC radar to be broadcast, but it's still nice to have if you want to look at it.Last edited by wiedehopf; 2019-06-12, 18:31.
Leave a comment:
-
Originally posted by glen4cindy View PostThis is exactly this hurdle I'm running into.
I see guides on here that have a lot of pages to them. I do not want to be lazy, but, if there are say 12 or 13 pages, it takes a very long time to read through everything.
The First post is the actual "How-to" and contains all necessary instructions AND it is regularly updated.
Subsequent posts are either questions/answers raised by users or optional items.
Originally posted by glen4cindy View Postonly to find out like Oblivion says the information is no longer valid. . What would be great is if these threads could somehow be archived so the information is still there but it would be clear they are no longer valid.
Originally posted by glen4cindy View PostI did notice the Github page on Mutability says it's old code that is no longer maintained
The Mutability ver 1.15~dev is still good, and up to date.
Leave a comment:
-
asdb-receiver which is talked about in this thread should work.
mutability moved to maintaining dump1090-fa but dump1090-mutability 1.15 still works fine.
you should be able to use both without a problem.
If you want to use dump1090-fa, i've written a guide on how to install it with fr24feed in mind:
Leave a comment:
-
Originally posted by Oblivian View PostBah. Too many similar guides.
I'd go on a delete spree but someone would be bound to tell me off.
I see guides on here that have a lot of pages to them. I do not want to be lazy, but, if there are say 12 or 13 pages, it takes a very long time to read through everything only to find out like Oblivion says the information is no longer valid.
What would be great is if these threads could somehow be archived so the information is still there but it would be clear they are no longer valid.
I did notice the Github page on Mutability says it's old code that is no longer maintained but I see quite a bit that seems to still be using it.
Leave a comment:
-
Originally posted by abcd567 View PostThere seems to be some mixup.
Current thread was NEVER a sticky.
The thread which was sticky since its creation, and became outdated was "Raspberry PI installation made too easy with extra feature" (started by zahidulhasan in Oct 2017). This is the thread you un sticked recently.
I'd go on a delete spree but someone would be bound to tell me off.
Leave a comment:
-
Originally posted by Oblivian View PostSomeone already asked me recently to un stick this thread due to it being out of date and no longer working. (So I did)
Current thread was NEVER a sticky.
The thread which was sticky since its creation, and became outdated was "Raspberry PI installation made too easy with extra feature" (started by zahidulhasan in Oct 2017). This is the thread you un sticked recently.
Leave a comment:
-
Someone already asked me recently to un stick this thread due to it being out of date and no longer working. (So I did)
So the root answer is likely no, not any more.
but most places allow you to join them with basic instructions like the link above
Sent from my EML-L09 using Tapatalk
Leave a comment:
-
Originally posted by Oblivian View PostThe logical place to ask would be their own support area..
https://www.radarbox24.com/blog/rada...erry-pi-client
I wasn’t sure that their site would be the best place to begin a question about multiple feeds since it was already being addressed here.
Leave a comment:
Leave a comment: