These files should not grow like that. Maybe check with obj in a separate thread?
There is no way I can put it before the script is downloaded.
Guess I could add the command to the instructions.
Yeah thatās not right try to tail the file see if there are any errors being repeated over and over filling this file up.
tail -c N dump1090-mutability.log
Where -c tells the command to only output the last N bytes. (1000000 = 1mb)
That way your not having to try and open the entire file.
Hi,
No repetative errors that I can see.
Just:
snip
*5d342118fb5712;
CRC: 000000
RSSI: -29.7 dBFS
Score: 1600
Time: 364470231370.50us (phase: 0)
DF 11: All Call Reply.
Capability : 5 (Level 2+, airborne)
ICAO Address: 342118
IID : II-00
*8d4ca53f99415e28e80490a9786e;
CRC: 000000
RSSI: -26.4 dBFS
Score: 1800
Time: 364470234045.17us (phase: 120)
DF 17: ADS-B message.
Capability : 5 (Level 2+, airborne)
ICAO Address : 4ca53f
Extended Squitter Type: 19
Extended Squitter Sub : 1
Extended Squitter Name: Airborne Velocity
EW status : Valid
EW velocity : 349
NS status : Valid
NS velocity : 326
Vertical status : Valid
Vertical rate src : 0
Vertical rate : 0
HAE - Barometric : -375 ft
*5d34369436e147;
CRC: 00004f
RSSI: -24.9 dBFS
Score: 1000
Time: 364470237703.25us (phase: 180)
DF 11: All Call Reply.
Capability : 5 (Level 2+, airborne)
ICAO Address: 343694
IID : SI-63
*5d34369436e147;
CRC: 00004f
RSSI: -25.0 dBFS
Score: 1000
Time: 364470249327.83us (phase: 240)
DF 11: All Call Reply.
Capability : 5 (Level 2+, airborne)
ICAO Address: 343694
IID : SI-63
snip
Phill
You have the dump1090 option to log all decoded messages turned on. Run
sudo dpkg-reconfigure dump1090-mutability
and make sure that option is turned off! 
how can I adjust the graphic on my real max rangeā¦ ? My Max Range are about 220km
lignumaqua, you are correct! Now I know Iām getting seniā¦er old, but I have no recollection of making that change on the 2nd of February. 
Thanks
Phill
@jprochazka and mgunter, sorry for wasting your time.
antonov124,
Do you have an older setup?
My graphs peak at the red line.
jonhawkes2030, you are correct. I updated that graph recently to remove the surplus 250nm line.
antonov124, update the script and just run the portal section again; this will update the graph definitions.
EDIT: Waitā¦ I meant to remove it but donāt think I have actually done it. Let me check and post again when done.
i had do deleted the adsb-feeder an reinstall everything 
now it looks okay
BUT the rest looks veeeeerrryy emty:
You currently have the range graph set to nautical miles and that always displayed OK. Itās the metric graph that still as an extra line at 250nm but I have submitted a request to remove that. As for the other empty graphsā¦ I donāt know what is causing them.
i changed it to metric now the range is km
Yes but I think you still have a black line at 250 NM. This should be removed soon with the next update of the scripts.
Oh okay, the red line is okay
the black line at 250nm is over the top ^^
@mgunther fix has been merged.
Yes folks, growing pains, there are more bugs to be worked out, but getting smoother.
If you have issues, just drop me a note on the contact form. Most of the time, itās a temporary issue and will correct itself once I get things fixed on my end.
Thanks,
Dan
If you refresh and re-run the install.sh again now, that black line should disappear.
yeah - thx
[quote=āmguntherā]
Where can that graph be changed to miles and not nautical miles?
Thatās not easily done right now. If you are comfortable editing files yourself, it is in:
/home/pi/adsb-feeder/build/portal/graphs/make-collectd-graphs.sh
You would want to edit the following routine:
range_graph_imperial()
and change the calculations.
Anything you do there will be overwritten next time you run the install.sh script.
OK.
Is the install.sh script what we use for routine upgrades also? Are you guys notifying of changes
and mods to the project?? Or should we just watch the github page for that info?