Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on April 05, 2013, 11:12:31 AM
-
This is a bugfix release. The two main improvements are:
- The issue which resulted in an unrecoverable error when autosnapshots were enabled, and the program was minimised to the system tray, has been corrected.
- The handling of OS standby or hibernation has been changed, and the program now resumes properly when the system is restored. You may still see a red error message in the toolbar, but it will apply only to the first sample after resuming.
Full list of changes since v2.71:
- fixed bug whereby tweaking didn't work when using special login
- increased maximum clipping level for CRC graph
- fixed issue with resuming after a long pause
- fixed bug which caused floating point error with some configurations when minimised to the system tray
- fixed issue of lockup when emerging from standby
- improved reporting of login errors
- added option to pause after login error
http://rsux.plainroad.me.uk
-
Eric it's up and running.
I also noticed that my AS uptime now shows and is incrementing just fine ;)
Stuart
-
Thanks Stuart. I forgot to mention that little change.
(I don't expect that many people see uptimes greater than 49 days :) )
-
Nice to see a new release.
-
Eric what is the new max clipping level for CRCs now?
Stuart
-
The highest level you can set it to is now 500/min. There's no fundamental limit, so I suppose on reflection I could have made it a lot higher, or perhaps offer the option of a logarithmic scale.
-
The highest level you can set it to is now 500/min. There's no fundamental limit, so I suppose on reflection I could have made it a lot higher, or perhaps offer the option of a logarithmic scale.
I was just wondering, mainly because on my screen the small space for the numbers is not large enough to fully show all the figures so it's difficult to see them properly. I lose half of the right most digit.
Stuart
-
I'll make a note to increase the size of the spinedit boxes.
-
Thanks for the new release.
I think this is a little cosmetic bug: The SNR graph on the combined SNR/bitloading page is invisible if the line is horizontal.
Look at the D3 band:
(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fwww.abload.de%2Fthumb%2Fbitloading-2013-04-05jzpe9.png&hash=c5c5393e7544ba56f4c188b05cf12cfebe9305c6) (http://www.abload.de/img/bitloading-2013-04-05jzpe9.png)(https://forum.kitz.co.uk/proxy.php?request=http%3A%2F%2Fwww.abload.de%2Fthumb%2Fsnr-2013-04-05-21.32u8kpx.png&hash=002557a626545bfcebb64affac42bf06cb74920d) (http://www.abload.de/img/snr-2013-04-05-21.32u8kpx.png)
-
That's a strange one. I'll check it out.
[Edit] I've located the bug, and it will be fixed in the next version.
-
Eric I was wondering if you can create options which allows the program to login and start recording on program start, and another to start minimised?
Stuart
-
Stuart, those options were added in v2.7. Just add the words 'mimimise' and/or 'startrecording' to the command line which runs the program, e.g.:
rsux startrecording minimised
-
Stuart, those options were added in v2.7. Just add the words 'mimimise' and/or 'startrecording' to the command line which runs the program, e.g.:
rsux startrecording minimised
:-[ :-[ :-[ :-[ :-[
Stuart
-
;D
-
Me too :-[ In windows I am starting it with a command file since these posts.
cd C:\.... \rs-w32-2.73
start "rsw" rsw startrecording minimised
Are any other options available on the command line? I did not notice this advice anywhere but I am not one to read the instructions!
-
Someone requested these two command line options a few weeks ago, and there aren't any others at present. But if there are others you'd like to have, feel free to ask.
-
Eric
Might it be possible to disregard errors when the time interval is more than the sample time (or divide by the sample interval in minutes). You will see that currently with standby all the graphs are nice except for the errors. Bits swaps per minutes must be worked out differently as they come out with no jumps.
Yours hopefully!
-
Yes, I thought I'd covered that issue, but clearly there's a bit more to do.
[Edit] Fixed in next version