Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on January 01, 2015, 11:30:45 AM
-
Several small improvements. Changes since v5.3:
- corrected small cosmetic error on Snapshots page in Windows version
- when the average error values are reset, the SES values are now included
- when the MDWS options "SNR per tone" and "Bitloading" are enabled, the corresponding
options in "Items to monitor" cannot now be disabled
- when the option "SNR per tone" is disabled in "Items to monitor", its sub-items "Show as
separate graph" and "Include with bitloading" are also disabled
- empty text files of error averages are no longer autosaved
- eliminated false positives in detecting resync events
- added option to select the font used in the graphs
- the configured modem/router model is noted in the event log on startup and after changing
- with modems which don't report FECs directly, DSLstats now falls back to RSCorr for FECs
- uploads to MDWS from locales which use a comma as the decimal divider are now converted
to the UK format before uploading
- modified the telnet login function slightly to accommodate modems which apply extra formatting
to the login prompt
http://www.s446074245.websitehome.co.uk/downloads.html (http://www.s446074245.websitehome.co.uk/downloads.html)
Edit - added last item to list of changes
-
Downloaded to The Cattery. :)
Unfortunately there is no graphical output when it is started . . . Just like it was with v5.3 :(
[Duo2 dslstats64L-5.3.1]$ ls
bitloading.html connspeed.html fec.html README ses.html snrmpbup.html upload12.l64
CHANGELOG crc.html fullstatstemplate.html routers.dat snrm.html specialrouters.dat
combined.template dslstats LICENCE routertraffic.csv snrmpbdown.html statstemplate.html
[Duo2 dslstats64L-5.3.1]$ ./dslstats
TLResourceList.Sort 57 DUPLICATE RESOURCE FOUND: TBitchart:PNG
TLResourceList.Sort 58 DUPLICATE RESOURCE FOUND: TBitchart:PNG
TLResourceList.Sort 59 DUPLICATE RESOURCE FOUND: TBitchart:PNG
TLResourceList.Sort 60 DUPLICATE RESOURCE FOUND: TBitchart:PNG
TLResourceList.Sort 65 DUPLICATE RESOURCE FOUND: TLinechart:PNG
TLResourceList.Sort 66 DUPLICATE RESOURCE FOUND: TLinechart:PNG
TLResourceList.Sort 67 DUPLICATE RESOURCE FOUND: TLinechart:PNG
TLResourceList.Sort 68 DUPLICATE RESOURCE FOUND: TLinechart:PNG
TLResourceList.Sort 70 DUPLICATE RESOURCE FOUND: TLinediagchart:PNG
TLResourceList.Sort 71 DUPLICATE RESOURCE FOUND: TLinediagchart:PNG
TLResourceList.Sort 72 DUPLICATE RESOURCE FOUND: TLinediagchart:PNG
TLResourceList.Sort 73 DUPLICATE RESOURCE FOUND: TLinediagchart:PNG
TLResourceList.Sort 82 DUPLICATE RESOURCE FOUND: TSNRMperband:PNG
TLResourceList.Sort 83 DUPLICATE RESOURCE FOUND: TSNRMperband:PNG
TLResourceList.Sort 84 DUPLICATE RESOURCE FOUND: TSNRMperband:PNG
TLResourceList.Sort 85 DUPLICATE RESOURCE FOUND: TSNRMperband:PNG
TLResourceList.Sort 108 DUPLICATE RESOURCE FOUND: TTraffic:PNG
TLResourceList.Sort 109 DUPLICATE RESOURCE FOUND: TTraffic:PNG
TLResourceList.Sort 110 DUPLICATE RESOURCE FOUND: TTraffic:PNG
TLResourceList.Sort 111 DUPLICATE RESOURCE FOUND: TTraffic:PNG
^C
[Duo2 dslstats64L-5.3.1]$
-
Thanks for trying. You've got all the correct files in place, and the DUPLICATE RESOURCE responses are quite normal. I'll now have to apply myself to producing a diagnostic version for you to try, to get to the bottom of this.
-
For completeness I should mention that I removed the ~/.dslstats/ directory before attempting to start the utility.
-
Yes, thanks, that means it was a completely clean start.
-
Windows 32bit working fine here and the improvements are as it says on the tin, the only thing that sticks out in Version 5.3.1 is the CPU usage on every sample has gone up from 10% to 30% just wondering if others see this to if not then i'll need to optimize the OS.
-
Both, linux and windows versions are running fine here.
I don't have higher CPU usage than before. If you want to reduce it you may want to disable "bitloading" and "SNR per tone" monitoring.
-
Both, linux and windows versions are running fine here.
I don't have higher CPU usage than before. If you want to reduce it you may want to disable "bitloading" and "SNR per tone" monitoring.
Thanks morphium i'll do as you suggested.
EDIT: did as you said and the CPU usage has gone down to 9% on each sample
cheers :)
Just another edit it seems the SNR per tone monitoring is the cause of higher CPU usage and while disabled and with bitloading activated the CPU usage is 1%
-
Several small improvements. Changes since v5.3:
- corrected small cosmetic error on Snapshots page in Windows version
- when the average error values are reset, the SES values are now included
- when the MDWS options "SNR per tone" and "Bitloading" are enabled, the corresponding
options in "Items to monitor" cannot now be disabled
- when the option "SNR per tone" is disabled in "Items to monitor", its sub-items "Show as
separate graph" and "Include with bitloading" are also disabled
- empty text files of error averages are no longer autosaved
- eliminated false positives in detecting resync events
- added option to select the font used in the graphs
- the configured modem/router model is noted in the event log on startup and after changing
- with modems which don't report FECs directly, DSLstats now falls back to RSCorr for FECs
- uploads to MDWS from locales which use a comma as the decimal divider are now converted
to the UK format before uploading
http://www.s446074245.websitehome.co.uk/downloads.html
Eric, thanks a lot. Didn't see in the changelog the fix you made for the telnet prompt, does this include it? :)
In order to update, can I simply unzip and overwrite all files? I have a portable config, I configured it to write everything in the same dir.
Thank you. :)
-
In windows your config settings are held in C:Users\username\Appdata\local so even if you delete/remove the old DSLstats folder and unzipp DSLstats your current settings will survive and be used on Version 5.3.1
-
In windows your config settings are held in C:Users\username\Appdata\local so even if you delete/remove the old DSLstats folder and unzipp DSLstats your current settings will survive and be used on Version 5.3.1
Nope: on windows you can configure DSLstats to write config files in the application directory (portable mode), that's what I did. Hence my request.
In the zip file I notice there's no .ini file so overwriting should be safe, but I preferred to ask. :)
Thanks for your comment.
-
In windows your config settings are held in C:Users\username\Appdata\local so even if you delete/remove the old DSLstats folder and unzipp DSLstats your current settings will survive and be used on Version 5.3.1
Nope: on windows you can configure DSLstats to write config files in the application directory (portable mode), that's what I did. Hence my request.
In the zip file I notice there's no .ini file so overwriting should be safe, but I preferred to ask. :)
Thanks for your comment.
yes it will work but don't delete the DSLstats folder or you will lose the config file thats why I find it's better to let DSLstats send the config/ini file to the appdata folder by default it cause's less hassel when updateing to a new version of DSLstats.
-
What NS says is true, but yes, you can just copy all the files in the download, overwriting the earlier versions. The configuration and saved data will be preserved if you do this.
-
Eric, thanks a lot. Didn't see in the changelog the fix you made for the telnet prompt, does this include it?
Yes, that fix is included, but I forgot to include it in the changelog. I'll correct that.
-
Both, linux and windows versions are running fine here.
I don't have higher CPU usage than before. If you want to reduce it you may want to disable "bitloading" and "SNR per tone" monitoring.
I think this probably relates to the changes I made to deal with MDWS uploads from locales which use the comma as the decimal divider. So it should only affect the MDWS uploads of those two items, and they could be disabled in the MDWS section but left enabled for DSLstats' own graphing.
For the next release I'll modify that section of code so that the comma replacement only occurs on systems which actually need it.
-
In windows your config settings are held in C:Users\username\Appdata\local so even if you delete/remove the old DSLstats folder and unzipp DSLstats your current settings will survive and be used on Version 5.3.1
Nope: on windows you can configure DSLstats to write config files in the application directory (portable mode), that's what I did. Hence my request.
In the zip file I notice there's no .ini file so overwriting should be safe, but I preferred to ask. :)
Thanks for your comment.
yes it will work but don't delete the DSLstats folder or you will lose the config file thats why I find it's better to let DSLstats send the config/ini file to the appdata folder by default it cause's less hassel when updateing to a new version of DSLstats.
There's no hassle when you update, no matter the location of the config files, because Eric (wisely) doesn't put any config files in the zip, so you don't overwrite anything (proper behaviour for portable apps).
If you change the option right after first installation (first run), you don't lose anything, at first save configuration is created from the start in the exe folder, and that's good.
If you change the option after some time, config files are in win appdata, what I did in my case was copy them to exe folder, run the program, select the option to save them in the exe folder and close. Then deleted win appdata folder after I was sure that config was read from the exe folder.
It would be good if the program would take care automatically of the migration when you change the option, and I would also suggest using a subdirectory for config files to ease config migration/backup. I use many portable apps, so I'm used to these kind of manual processes and it's not a big problem for me.
Thanks for the comments. :)
-
Eric, thanks a lot. Didn't see in the changelog the fix you made for the telnet prompt, does this include it?
Yes, that fix is included, but I forgot to include it in the changelog. I'll correct that.
No problem Eric. You should have at least 2-3 new italian users thanks to that update. It wasn't working but I posted the link to 5.3.1 exe telling people that it now the telnet issue was fixed. ;)
I also noticed that you solved the issue of the locale for MDWS uploads, that's great too, thank you.
-
Windows 32bit working fine here and the improvements are as it says on the tin, the only thing that sticks out in Version 5.3.1 is the CPU usage on every sample has gone up from 10% to 30% just wondering if others see this to if not then i'll need to optimize the OS.
Further to the comments earlier, I've remembered that you use a Raspberry Pi, and I guess it's not too surprising that the extra processing in v5.3.1 puts a bit of a strain on the CPU. As I said above, I'll seek to minimise this in the next release.
-
Seems to be working ok and reporting FEC errors from my DG834DT.
Is there a way to save a graph that been running for some time say 7 days and not the 24hrs max per graph. ?
-
Not in a very convenient form. You can save the accumulated data for some of the graphs as XML files (Configuration --> Advanced --> Save/Restore XML) and load this data back into the program to view it at some later time. I don't know if anyone actually uses this feature, and it really needs updating, but I won't be able to do that for some time.
-
Seems to be working ok and reporting FEC errors from my DG834DT.
Is there a way to save a graph that been running for some time say 7 days and not the 24hrs max per graph. ?
That's what MyDSLWebStats was created to achieve ;)
-
Good point :)
-
Not in a very convenient form. You can save the accumulated data for some of the graphs as XML files (Configuration --> Advanced --> Save/Restore XML) and load this data back into the program to view it at some later time. I don't know if anyone actually uses this feature, and it really needs updating, but I won't be able to do that for some time.
I used to... before MDWS.
-
Ah yes, I remember now. :)
-
I was thinking about using it on the forum :o
-
Thats why I run both HG612_modem stats and DSLstats. Both are great programs but have different uses.
DSLstats is the best for showing real time monitoring whilst HG612_modem stats is excellent for providing long term graphs.
They both work in different ways:-
Erics program takes the info and plots it straight to a visual graph which you can see things as they happen.
BE's program collects the raw data then you run graphpd to output the graph for the period you want.
.. and now we have Tony's MDWS which nicely brings them together by collecting the data from either prog and maintaining historical visual data.
I used to use the xml files for DSLstats but when I started running HG612_modem stats I tended to use that more for historical data.
I must admit that I quite often delay updating DSLstats purely because I dont want to lose the current running graph. However have a look at Tony's My DSL WebStats (http://www.mydslwebstats.co.uk/) and see if it fits the bill for what you want to do.