Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on October 20, 2013, 10:20:59 AM
-
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
-
Running here now on W2k and the timestamp on custom commands is appreciated...
Stuart
-
Thanks Stuart.
-
Many thanks for this latest update Eric.
I have downloaded the updated package and will be able to give it a good test tomorrow.
-
I look forward to it. :)
-
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?
-
That's when the PC is on standby
When it restarts it shows the intervening period when nothing was recorded as a dotted line.
-
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. :doh:
-
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
-
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.
-
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.
-
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).
-
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.
-
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.
-
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.
-
Eric it was just immediately after updating to this release from the previous one. I seem to remember I had to alter the sequence of commands because I had a date command in there which became redundant, but assumed that as everything was ticked it would be OK. I simply unticked and reticked everything and its been fine since.
Stuart
-
I see, thanks Stuart. I'll see if I can identify how this happened, but it may have to go down as "one of those things".
-
A quick note to confirm that after a period of testing, yesterday, I see that all the Snapshot graphs are of the expected size once they contain plotted data.
Hence the 'something odd', which I reported earlier, can be disregarded and moved to 'file 13'.
-
Thanks for that. I'll still see if I can find out the reason for the small anomaly, but I won't spend a lot of time on it. :)
-
Only if you have nothing better to do! ;)
-
thanks for the update and including QLN/HLOG snapshots :)
seems to be working great for me, aint tested any screenshots yet
:)
-
Thanks Snadge :)
-
Eric
do you know of anyone thats used DSL-Stats on a Netgear DGN2200 (thats in the list)...?? if so how did they get it working? Im trying to help someone get this working on that router but the debug enable returns a 404? (and they say the router is on the same regular IP of 192.168.0.1)
thanks
-
I see that Kitz has already answered that elsewhere. :)
-
I see that Kitz has already answered that elsewhere. :)
but has the DGN2200 been tested on DSL-Stats as ive read it uses different commands and layouts?
thanks
-
Since telnet is totally disabled on that router and there's nothing in the firmware to tenable it, then you're snookered an dslstats won't work.
I just found a link on Idnetters which says there's an alternative firmware that you can install if you want to give it a shot.
http://www.idnetters.co.uk/forums/index.php/topic,23123.25.html?PHPSESSID=b412e3acb32445b9af116cd97af84b81
-
Also on IDNet there's a method to enable telnet on the DGN2200: http://www.idnetters.co.uk/forums/index.php/topic,23123.msg559926.html#msg559926 (http://www.idnetters.co.uk/forums/index.php/topic,23123.msg559926.html#msg559926)
I've got a DGN2200v3 and successfully used that method to enable telnet and get DSLstats working after a fashion with it, but it lacks several features and I abandoned the test. I should remove it from the compatibility list really.
[I see that's the same method as mentioned in the Routerstats forum, which Kitz linked to earlier]
-
i thought that method from my other thread unlocked it? telnetEnable.exe and BAt file? so, it does...but DSL-stats dont work proper on it?
-
It does work to a degree - see this: http://forum.kitz.co.uk/index.php?topic=12730.msg240570#msg240570
-
what doesnt work on it? can you remember?
thanks
-
I'm trying to remember, but I can't find any notes from my testing. I do remember that one DSLstats user found that DSLstats persistently crashed with this router, and I acquired one to try to diagnose the problem. As I couldn't reproduce it myself I never found the cause of his problem. It may be that this was the only issue with the DGN2200, but its general performance wasn't very good on my connection, so I stopped using it.
Apologies for the vagueness. I put it down to my age.
-
no problems - but the features such as SNR, Bit-Loading, QLN and SNRM Adjusting worked?
-
no problems - but the features such as SNR, Bit-Loading, QLN and SNRM Adjusting worked?
SNRM and bitloading certainly, but I'm not sure about the other items.
-
no problems - but the features such as SNR, Bit-Loading, QLN and SNRM Adjusting worked?
SNRM and bitloading certainly, but I'm not sure about the other items.
do all versions of DGN2200 have this issue? I believe there are three...the one in question is a v1
-
I'm afraid I have no idea. The person who reported the problem was using a v3, and the one I obtained was also a v3.
-
Many thanks for the continuous development of DSLstats.
Sadly the new VDSL2 band plan detection seems not to work properly on my connection. QLN, Hlog and Bitloading graphs are affected.
I've attached screenshots from v4.02 and v4.1 as well as the the pbParams data. Maybe you can find the cause of this issue.
-
You're quite right. In fixing one issue concerning band plan detection I exposed another. I've fixed it properly now (hopefully) and I'll soon be uploading the next version.
-
I started 4.1 running whilst 4.01 was still running and was pleasantly surprised to find all of the 4.01 configuration was in place and correct in 4.1. The config also seems fine when it is started on its own :) Have I missed something - I was used to setting it up each time I used a new version
-
I started 4.1 running whilst 4.01 was still running and was pleasantly surprised to find all of the 4.01 configuration was in place and correct in 4.1. The config also seems fine when it is started on its own :) Have I missed something - I was used to setting it up each time I used a new version
From v4.0 onwards the configuration files are saved by default in the correct location as advised by the OS, instead of the same directory as the other DSLstats files. If you look at the event log you'll see that the first line informs you of the path where the files are saved. For Windows users this is now an option in the Misc section, where you can choose between two locations for the config files.