Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on November 17, 2013, 11:28:42 AM
-
I've made the custom commands feature more flexible, and added an option to send email alerts. Apart from this, some small improvements and fixes for reported issues.
List of changes since v4.12:
- the tray icon and application icon now change colour depending on connection status
- custom commands can be separately linked to different events
- added option to send email alerts triggered by various events (e.g. low SNRM)
- added a button to manually get the user's IP address
- fixed occasional bug whereby the ES / hour chart didn't rescale correctly
- fixed issue in which the QLN option "Show extended tone range" didn't show the extra data
- added option to save snapshots in category folders
- tidied up the pbParams display for routers which provide badly formatted output
- fixed failure to save event log on exit (if configured)
http://dslstats.plainroad.me.uk (http://dslstats.plainroad.me.uk)
-
Thankyou for the update ;D and the pbParams look great ;)
-
Eric I've updated this fine. On the custom commands page the text beside the radio button for 'Include in event log' seems strange, it has a square character added before the word event and the word log is clipped so it looks like 'lc'. This is on W2K BTW... Just tested my Linux version and the stuff displays fine on the custom commands page.
Stuart
-
Minor niggle
Is it me or is the versioning becoming very confusing?
To me 4.12 is newer version than 4.2.
Perhaps a series of 3 digits would be better ie 4.1.0, 4.1.1, 4.1.2, 4.2.0
-
@NewtronStar: Thanks :)
@Stuart: I can see what's happened here - it's a two-line text label, and I used the Linux newline character #10 which Windows interprets as a non-printable character, so there's only one line which is too long for the space available. I'll correct this in the next release.
@rhohne: I guess you can look at it two ways, but you do have a point. I've been doing it this way all along, so rather than changing at this stage, I think I'll just give two digits to the second part of the number, so 4.2 becomes 4.20.
-
All looks as it was in 4.12 but now getting message "no response from router!
Edit: Event log full message Technical details: Connection timed out
Router failed to respond to telnet request
Edit2:New Event log message No DSL Connection, though router GUI shows DSL alive and well,and I am posting this.
-
@renluop: The only circumstances in which that message should appear are if the router is disconnected from the PC or the IP address is wrong. Did you perhaps edit the login details?
-
Hi Eric! :) No, and I have just rechecked the revealed password. That, and other details are as before including telnet port. Path for snapshots is (if relevant) C:\Users\..\AppData\Local\dslstats\dslstats32W-4.2\snapshots.
Also see Edit2.
-
Can you check Telnet Data --> Connection Stats and copy the contents here please?
-
'tis as white as my ceiling! :)
-
I'm at a loss to explain this at the moment. I didn't really change anything in the way DSLstats logs in and collects its data in this version, except for one extra check on the connection stats for Technicolor routers. If your stats are blank, then that check isn't the explanation here.
The only other thing I can suggest at this point is that you revert to version 4.12 and make sure that it still works properly. You only need to copy the executable dslstats.exe from the old version to replace the new one. Tomorrow I'll reinstall my TG582n and see if I can find out what's happening, but it will have to wait until the afternoon unfortunately.
-
No sweat, as I am out all day more or less! :)
-
I have some problems with the last versions. ( I'm not a BT user. My provider is GVT in Brazil )
1st
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 9096 Kbps, Downstream rate = 65244 Kbps
Path: 0, Upstream rate = 3971 Kbps, Downstream rate = 37998 Kbps
Discovery Phase (Initial) Band Plan
US: (872,1203) (1972,2779)
DS: (32,867) (1208,1971) (2784,4051)
Medley Phase (Final) Band Plan
US: (872,1203) (1972,2779)
DS: (32,867) (1208,1971) (2784,4051)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 9096 kbps 65244 kbps
Actual Aggregate Tx Power: 5.6 dBm 13.7 dBm
============================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): N/A 36.1 52.6 N/A 17.5 44.5 66.6
Signal Attenuation(dB): N/A 35.8 N/A N/A 17.5 44.5 66.6
SNR Margin(dB): N/A 18.9 0.0 N/A 19.4 19.6 0.0
TX Power(dBm): N/A 5.6 128.0 N/A 12.5 7.5 128.0
#
U4 ???? xdslcmd info pbParams doesn't show this.
2nd
The tones bitloading graph shows all bands in blue. Previous versions shows correctly upstream and downstream. Snapshot attached.
-
1. It looks as though I've tried to be too clever. The new BT firmware does report U4, and I wrongly assumed that it was always there (I don't have a VDSL2 connection to test it on).
I'll have to look at it again.
2. On your connection the U0 band isn't used. Several versions earlier I made a change to deal with this type of connection, but it looks as though something has gone wrong with that part of the code. I'll try to correct it.
-
1. It looks as though I've tried to be too clever. The new BT firmware does report U4, and I wrongly assumed that it was always there (I don't have a VDSL2 connection to test it on).
I'll have to look at it again.
2. On your connection the U0 band isn't used. Several versions earlier I made a change to deal with this type of connection, but it looks as though something has gone wrong with that part of the code. I'll try to correct it.
Thanks for your work in this very useful tool.
U0 is optional depending on the profile, line condition and DSLAM used.
The profiles used here are: (down/up) 27500/2600 , 38000/4000 and 55000/6000 Kb/s.
-
I'm at a loss to explain this at the moment. I didn't really change anything in the way DSLstats logs in and collects its data in this version, except for one extra check on the connection stats for Technicolor routers. If your stats are blank, then that check isn't the explanation here.
The only other thing I can suggest at this point is that you revert to version 4.12 and make sure that it still works properly. You only need to copy the executable dslstats.exe from the old version to replace the new one. Tomorrow I'll reinstall my TG582n and see if I can find out what's happening, but it will have to wait until the afternoon unfortunately.
@renluop: I owe you an apology. I've set up my TG582n and got the "No DSL connection" message (although I didn't get "Router failed to respond to telnet request", and I can think of no reason for that one). I've traced the cause of the problem (it related to a check on non-Technicolor routers which was also being applied to Technicolor routers by mistake). I've fixed it and DSLstats is now running properly with the TG582n.
I do have to go out now, but I'll try to upload fixed versions later.
-
No apology at all is owed me! :)
-
Version 4.21 now uploaded, fixing the issues reported above:
- corrected the cosmetic error on the custom commands page in the Windows version
- corrected formatting of the pbParams display for VDSL2 connections which don't report band U4
- corrected wrongly coloured graphs with VDSL2 connections which don't use band U0 (hopefully)
- corrected "No DSL connection" error with Thomson/Technicolor routers
http://dslstats.plainroad.me.uk
-
Version 4.21 now uploaded, fixing the issues reported above:
- corrected formatting of the pbParams display for VDSL2 connections which don't report band U4
- corrected wrongly coloured graphs with VDSL2 connections which don't use band U0 (hopefully)
Confirmed. Both issues are corrected.
-
:thumbs:
-
Thanks both.
-
Eric not a big issue but when I check for a new version it says I'm up to date ???
Stuart
-
Thanks eric. All seems ok here :)
-
Eric not a big issue but when I check for a new version it says I'm up to date ???
Stuart
Thanks Stuart. I keep a file called VERSION on my website for the purposes of this check, and I hadn't updated it to 4.21. It's corrected now.
Thanks eric. All seems ok here :)
Thanks for confirming it. :)
-
Thanks Eric 4.21 now running and all OK....
Stuart
-
Reporting a minor formatting phoo-bah: "(From start of recording)" (The 64-bit Linux version.) Please see the screen-scrape, below.
-
Thanks Mr Cat. I'll increase the separation a bit next time.
-
Eric,
Just to thank you and report that the updated custom commands work well for me and that no problems have been found in my use.
-
Many thanks Les.
-
Two minor issues:
1) Under Bitswaps per Tone, horizontal compression doesn't "stick" between restarts.
2) Under Stats, attenuation is blank.
-
Two minor issues:
1) Under Bitswaps per Tone, horizontal compression doesn't "stick" between restarts.
2) Under Stats, attenuation is blank.
1) I see that it's saved but not restored after restart. I'll fix it in the next release.
2) What modem/router do you use? If you look at Telnet Data --> Connection Stats, do you see attenuation reported?
-
1) Sorry, I didn't explain properly. :blush:
If horizontal compression is set to 3, on program exit and restart it is still set to 3 but the graph is now displaying as if set to 1. The first pic is after program exit and restart, the second pic is as it should be.
2) Modem is HG612. Attenuation is reported in Telnet Data --> Connection Stats
Down Up
SNR (dB): 6.0 6.0
Attn(dB): 24.1 0.0
Pwr(dBm): 10.8 -0.4
However in Stats, attenuation is blank.
DSLAM/MSAN type: IFTN:0xb203 / v0xb203
DSL mode: VDSL2
Status: Showtime
Uptime: 1 day 2 hours 27 min 17 sec
Downstream Upstream
Attenuation (dB):
Connection speed (kbps): 38649 6877
SNR margin (dB): 6.0 6.0
Power (dBm): 10.8 0.4
Interleave depth: 757 1
INP: 3.00 0
RSCorr/RS (%): 1.7979 0.0347
RSUnCorr/RS (%): 0.1565 0.0000
ES/hour: 2.57 2.99
Actually, that attenuation figure is meaningless anyway?
-
1) Sorry, I didn't explain properly. :blush:
If horizontal compression is set to 3, on program exit and restart it is still set to 3 but the graph is now displaying as if set to 1. The first pic is after program exit and restart, the second pic is as it should be.
That's OK, I did understand. When you restart DSLstats the value in the spinedit box is restored, but this isn't propagated to the graph itself. I've located the reason and it's fixed now.
2) I'm not sure about this at the moment. If the value is reported in the connection stats output, then it should also appear on the Stats page. I use an HG612 myself, but on an ADSL2+ connection, and the attenuation values are copied over as they should be. So something isn't quite right. I don't know if the figures are meaningless, but the upstream value of 0.0 is obviously not correct.
[Later] I've now checked this, and the zero upstream value is the reason the attenuation values aren't being reported in Stats. I left both values blank if one of them was zero. I've now modified this check, so the values are always reported unless both of them are zero.
-
Hello Roseway!
Only just noticed the the categories snapshot save doesn't actually work.
I can not get the the configuration to save automatically (it saves upon start or exit? I've tried stopping as well).
I tried looking for the option in the DSLStats config file and couldn't find the option to enable it either.
[snapshots]
Snapshotdir=C:\Users\Ryan\AppData\Local\dslstats\
Dateorder=1
UseHoursperpage=1
Hourspersnapshot=1
SNRsnapshot=1
Speedsnapshot=1
Bitsnapshot=1
CRCsnapshot=1
FECsnapshot=1
ESsnapshot=0
SNRptsnapshot=0
ExpBitsnapshot=0
Swapsptsnapshot=1
Swapspmsnapshot=1
QLNsnapshot=0
HLogsnapshot=0
ConnectionStatsText=1
SNRText=0
BitloadingText=0
pbParamsText=1
QLNText=0
HLogText=0
AttenuationLogText=0
AverageErrorsText=1
TrafficText=0
EventlogSnapshot=1
CustomCommandsSnapshot=0
SnapOnExit=1
Daily folders=0
LogNumber=47
DeleteOlder=0
Olderthan=7
I don't believe it's there but I might be blind! :D
-
Only just noticed the the categories snapshot save doesn't actually work.
Yes, you're quite right. The option does work if it's enabled, but it isn't saved to the ini file, so you have to re-enable it if you restart DSLstats. Sorry about that. :-[
It will be fixed in the next release.
-
Eric for some time now I'm getting zero byte files created with the following name Custom-2013-11-30-08.28.16.txt, I guess this is because I have my custom commands set to display on the event log, I would have thought that if display on event log was set that either the data would be copied to the file as well or simply not write the file!
Also not everything which is created is being deleted after 7 days (the time I have set). I had hoped that all files older than the time set would be deleted.
Stuart
-
Stuart, I'll take a look at the unwanted custom command files. This isn't an area I've given much attention to, but I'll sort it out. Can I assume that it would be OK simply to not write those files when the event log option is used?
At present, what should happen with the auto-deletion of snapshots is that, if you use the Daily Folders option then the entire folder should be deleted, but if you don't use those folders then only .png files are deleted. The reason is that there may be other files of various kinds in the top level snapshots directory, and sorting out which files to delete and which to leave got rather complicated.
Now that there's another option of category folders it's become more complicated still. I need to give this some proper attention, but at the moment it's not high on the priority list.
-
Stuart, I'll take a look at the unwanted custom command files. This isn't an area I've given much attention to, but I'll sort it out. Can I assume that it would be OK simply to not write those files when the event log option is used?
At present, what should happen with the auto-deletion of snapshots is that, if you use the Daily Folders option then the entire folder should be deleted, but if you don't use those folders then only .png files are deleted. The reason is that there may be other files of various kinds in the top level snapshots directory, and sorting out which files to delete and which to leave got rather complicated.
Now that there's another option of category folders it's become more complicated still. I need to give this some proper attention, but at the moment it's not high on the priority list.
Eric re the custom files yes not writing them if set to use the event log is fine, now I realise I'll untick saving them which will resolve it. I must admit I'd forgotten to do that.
Now I understand how the daily log file folder works I'll use that instead. I've just looked at the docs and it makes it clear there what happens. As to the future I'm not sure what to suggest with categories, although deleting ALL files older than N days in a category should be fine in my view as long as it is documented. These folders are after all DSLStats folders and should only have DSLStats files contained therein.
Stuart
-
Thanks Stuart
Eric re the custom files yes not writing them if set to use the event log is fine, now I realise I'll untick saving them which will resolve it. I must admit I'd forgotten to do that.
Yes, that should deal with it, but in any case for the next release I've disabled the saving of the custom commands text when the event log option is chosen and also greyed-out the option to snapshot that text.
deleting ALL files older than N days in a category should be fine in my view as long as it is documented.
Yes, but the category folders are only created as needed, so I also need to identify which folders have to be searched. Of course it can be done, and I'll do it when time permits.