Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on September 19, 2012, 10:51:22 AM
-
Mainly a bugfixing and tidying-up release.
- program is now multithreaded, so responsiveness isn't degraded during sampling
- added 'System uptime' figure and option to use AS or SF for DSL uptime
- corrected wrong positioning of some buttons
- changed layout of QLN/HLog pages so that resizing doesn't cause components to overlap
- increased minimum size of window so that resizing doesn't cause display problems
- corrected scaling of SNR per tone graph
- corrected issue when pausing in the middle of a sampling period
- 'Sampling' is now displayed during the initial sampling period (although not really necessary any more)
- corrected issue which gave error message "The internet connection may have been dropped"
- sorted out enabling/disabling of the Start/Pause/Stop buttons to reflect status
- changed code which detects VDSL2 band plans, to take account of systems which don't use band U0
https://docs.google.com/folder/d/0BxbUtOYVZ_SCZ1BnY3RKYnN2b1U/edit
-
Eric the uptime is still screwed on my system. Using AS gives give 114+ daaays for noth Uptie and DSL uptime, however the DSL time changes to 123+days when using the SF option! So neither give the corret DSL uptime for me.
Stuart
-
Something doesn't look quite right on my VDSL2 connection.
SNR in the bitloading graph looks slightly out of kilter & bitloading is all the same colour.
-
The 1st time I started rsw I had one of those moments when there was a message box complaining about a priviledged instruction. Fortunately this hasn't happened since.
Have had rsw freeze once, after running for 2hrs, during the sampling process with the application failing to recover. Besides this single event the data presented appears to be accurate and reliable.
Have a question on the CRC graph it says "CRC per min", is it this or CRC per sample?
The AS vs SF value is down to the conversion factor, despite the spec saying superframes should be 17ms on my 834GT they work out to be approx every 16.25ms. (Answers on a postcard for other routers).
SF: 27098975 25922363
AS(Uptime): 440679
-
Downloaded to The Cattery for testing. ;)
-
Eric the uptime is still screwed on my system. Using AS gives give 114+ daaays for noth Uptie and DSL uptime, however the DSL time changes to 123+days when using the SF option! So neither give the corret DSL uptime for me.
Stuart
Sorry Stuart, I'm guilty of unintentional misrepresentation here. I should label that second uptime figure differently. I've found no way to get the DSL uptime from the telnet interface for your router (and probably several others).
-
Something doesn't look quite right on my VDSL2 connection.
SNR in the bitloading graph looks slightly out of kilter & bitloading is all the same colour.
Sorry, that does look a bit of a mess. I'll try to sort it out.
-
The 1st time I started rsw I had one of those moments when there was a message box complaining about a priviledged instruction. Fortunately this hasn't happened since.
Have had rsw freeze once, after running for 2hrs, during the sampling process with the application failing to recover. Besides this single event the data presented appears to be accurate and reliable.
I suspect that these two things are from the same cause, and maybe related to the Windows version only. I'll try to find out what's happening.
Have a question on the CRC graph it says "CRC per min", is it this or CRC per sample?
No, it is CRC per minute. I get the data from the total CRC figure - I subtract the value in the previous sample from the value in the present sample, and convert it to a 'per minute' value using the sampling rate.
The AS vs SF value is down to the conversion factor, despite the spec saying superframes should be 17ms on my 834GT they work out to be approx every 16.25ms. (Answers on a postcard for other routers).
SF: 27098975 25922363
AS(Uptime): 440679
It doesn't tie up accurately with the 17 ms standard on my HG612 either. I'm wondering if the SF value has any real use in calculating uptime.