loving the new update on the button status! thanks
If you need a little more definition then you can add the following to the colors*.css file in the html directory
.button.activeButton { background-color: orange;}
1 Like
Note that you will need to Ctrl-F5 so that the browser shows the change.
Alternatively you can run the install script, it will leave the content of the colors css file alone but give it a new name, forcing the browser to load it again.
I am missing the small legend with the altitude-color correspondence. Is that by design?
Using a different color gradient, so it wouldn’t be accurate.
Just switch on track labels with K, that should give you a nice color legend/scale.
Well select an aircraft that’s climbing and you have a legend 
(Not a legend in the classic sense)
What i’m saying, with L+O or K you don’t need a legend because the altitude is in the labels.
Dim the map (B), that way the colors are visible quite a bit better.
Yes, but then the grey line between the points (missing signal) is not visible anymore. I kind of like it better not dimmed, but I see what you are saying that the colors “pop” more.
It flew southwest, left your coverage, then on it’s way back came back into your coverage further west.
The grey track is grey for a reason.
Hi, perhaps stupid question, but i have seen you made update on the airspy_adsb.default file on GitHub, and i have a difference with my old version intalled :
In your new version :
#network settings
NET= -l 47787:beast -c localhost:30004:beast
And in my actual version :
#network settings
NET= -l 29999:beast -l 47806:asavr -c localhost:30004:beast
Can i update with this modification, without the risk to kill something ?
Thanks.
Doesn’t really matter.
The -c (connect) to 30004 is the important part.
The rest is irrelevant unless you use those ports.
Thanks for your help !
The problem is that I can not remember if the port 29999:beast was added by me, or if it was there before !
I had that in there.
But why don’t you just remove it and check if anything stops working?
It’s easy enough to add it again -.-
By the way: Finding threads seems really hard on this forum because everyone seems to post in the first one they find.
1 Like
I have do it, installed your new settings, and all seems to work good !
Works fine, thanks! 
This is in regards to graphs1090, not tar1090, but didn’t know where else to put this observation:
New graph1090 style note ADSB tracks on the right:
Old(er) graph1090 - compare ADSB tracks:
In all honesty, when looking at the new updates, I haven’t a clue what’s going on unlike the way it was. Systems are both running Airspy R2’s, latest airspy_adsb, relatively same settings (will get into the test setup in another post tomorrow, but both are running -w 3).
Anyhow, not complaining, just an observation.
Well, the green area before represented all the tracks, including the single message ones.
So when the red area grew, the green area grew with it, leading to ridiculous numbers.
Now the combined area is all tracks, split into the green and red area for multi and single message tracks.
Additionally there is some different averaging going on, but that’s mostly besides the point once you look at the 48h or longer timeframes where you don’t see the averaging.
The red area should be equal between the two devices though.
Can’t tell you why that would be different.
Well it’s an identical but not the same setup, some fluctuation is expected, you’d have to feed both dump1090-fa from the same airspy_adsb to really compare the graphs.
You can always run the old/new graphs.sh script on the same data and check how the graph looks.
Just run sudo ./graphs.sh 1h after downloading the new version of graphs.sh somewhere after saving the “old” style picture from the same system.
1 Like