Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[roseway]

Several small fixes and tweaks, no major new features.

Changes since v4.02:
- added QLN and HLog to the auto snapshot list
- corrected the unintended daily saving of Bitswaps XML data
- option to save Bitswaps XML data is now greyed out with Thomson routers
- enabling auto snapshots of ES/hour chart now persists between runs of the program
- in Windows version there is now an option to save config files in either the OS-advised directory or the directory where the other DSLstats files are stored
- when starting DSLstats, the first line in the event log now records the location of the config files
- the output of custom commands is now timestamped
- added an option to send the output of custom commands to the event log
- corrected faulty VDSL2 band plan detection with new BT band plan
- on VDSL2 connections the tone range displayed in graphs is restricted to the highest value seen in the medley phase band plan
- the order of tabs under the main Configuration tab was slightly rearranged, and "Options" has been renamed "Items to Monitor"
- some minor cosmetic changes

http://dslstats.plainroad.me.uk

[broadstairs]

Running here now on W2k and the timestamp on custom commands is appreciated...

Stuart

[roseway]

Thanks Stuart.

[burakkucat]

Many thanks for this latest update Eric.

I have downloaded the updated package and will be able to give it a good test tomorrow.

[roseway]

I look forward to it.

[renluop]

Within the time blocks 17:32 to 18:52 both SNRMs' graphs show a long stretch with dotted rather than firm lines. Were the stats not being recorded, as I can see nothing in Event log? Or what esle could have been happening?

[c6em]

That's when the PC is on standby
When it restarts it shows the intervening period when nothing was recorded as a dotted line.

[renluop]

Looks like I need to alter my computer's settings then, as I want on going stats to 'prove' that a problem is solved. Should have remembered that a windows reinstall mucks settings up.

[broadstairs]

Eric I noticed that the custom commands did not start when I initially started the program, however un-checking and checking the options and it is now working including writing to the event log. Just thought I'd mention it in case anyone else has the same issue.

Stuart

[roseway]

I'll check that out Stuart. It doesn't seem to be the case here, but I have an idea about what might be causing it.

[burakkucat]

I have not been able to perform any routine testing today but I did notice something odd concerning the size of the 'snapshot' graphs. It seems as if only the SNRM graph is saved in its full size. 

I attach a ZIP format file, the contents of which shows what I have observed.

[roseway]

At the moment I don't have an explanation for that. Nothing has changed recently in the way graphs are saved, and I don't see the same effect here. The snapshot code simply saves the whole graph area including the captions, and all of the graphs are the same width (though they do vary in height).

[kitz]

Eric I noticed that the custom commands did not start when I initially started the program, however un-checking and checking the options and it is now working including writing to the event log. Just thought I'd mention it in case anyone else has the same issue.

Stuart

If it helps eric, it worked ok for me after Ive just updated.
Need to do a full system boot later, but not yet as Ive got too much open I need to save.

The blue in the graphs look kinda strange now..   its not a complaint eric, I cant see any other way it could be done...  it just looks different 
Not spotted any problems as yet, other than I too had the dotted lines today, but that was because an instance of HG612 modem stats got stuck, which meant DSLstats also stopped harvesting any data too.

[roseway]

The blue in the graphs look kinda strange now..

Yes, the blue represents ranges of tones which are either undefined in the band plan, or are in an overlapping section. Since this update I've realised that there was a longstanding bug in the band plan detection which had gone unnoticed. Now I've made this change it doesn't work properly with the 'old' band plan (which had some overlapping bands). I'll be uploading a version which should work with all band plans soon.

[roseway]

Eric I noticed that the custom commands did not start when I initially started the program, however un-checking and checking the options and it is now working including writing to the event log. Just thought I'd mention it in case anyone else has the same issue.

Stuart

Has this oddity repeated itself, Stuart? I can't reproduce it, and I can't see any reason for it to happen. If you can reproduce it, what sequence of actions leads to it? Thanks.