Unfortunately I can't reproduce this. After shutting down DSLstats, can you check ~/.dslstats/dslstats.ini, and look in the [graphs] section for the item "Samplerate=NNNNN". This is the sample timing in milliseconds. Does it show the correct value as it was set in the GUI?
Yes, I can confirm the correct "Samplerate" is stored --
[Duo2 .dslstats]$ grep Samplerate dslstats.ini
Samplerate=60000
[Duo2 .dslstats]$I've just started up DSLstats and will check its sampling rate in a couple of minutes.
(Two minutes later . . . ) On checking the value via the configuration tab I see it is set to 60 seconds.
I've no idea what has happened, for the problem was apparent on four separate days. The moment I make a report, it mysteriously fixes itself.
Something to consider --
Perhaps all the configuration options could be "greyed out" whilst the utility is in its recording state? Maybe the ability to change certain settings whilst the utility is in its active mode could be the source of weird results. For example, I can obtain (repeatedly and upon demand) an exception by going to the
Configuration --->
Traffic Monitoring tab and changing the string in the "Modem/router model:" box by a manual process. By that I mean if "HG622 [1]" is currently selected and I place the cursor directly to the right of the "]", any press of the
Backspace key (with the aim of changing the string from "HG622 [1]" to "HG622[2]") will cause an exception . . .
Finally, a comment about the size of the y-axis scale for the
QLN and
HLog plots. I have never seen a QLN plot where the curve is below -150 dBm/Hz. So perhaps using the range -80 to -160 dBm/Hz would make better use of the space? Similarly I have never seen a HLog plot where the curve is below -100 dB. So, again, using a range of 0 to -120 dB would make better use of the space? Perhaps
Bald_Eagle1, having viewed many
QLN and
HLog plots from different circuits over the last few years, has an opinion upon the y-axis scales?