Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on January 31, 2013, 07:02:34 PM
-
This small bugfix version hopefully fixes the login problem with some routers.
http://rsux.plainroad.me.uk
-
Eric this version installed just fine and ran on first click, permissions fine. The other one only failed the first time after correcting permissions.
Stuart
-
Thanks Stuart. In that case I'm fairly certain that the problem was a one-off relating to the upgrade. The program does a bit of conversion of some of its configuration during the first run of this version.
-
Just went to close it as I was turning off the PC tonight and it hung on hitting the red X, was not sampling at the time. After a short while the 'Application not responding' message appeared and was able to close it.
Stuart
-
>>> it hung on hitting the red X
I've got some ideas about this, and I'll probably be changing the way the program closes down.
-
Eric I've had another hang, I left it paused for an hour or more and when I went back to it when I hit start again I got what looked like it might be the small window which shows an exception but there was nothing in it and had to kill it again. I know I should probably have stopped it but I just forgot I left it paused.
Stuart
-
Stuart, this is an issue which I'm aware of, and I haven't got around to dealing with it, so I apologise. I need to find a way of handling long pauses.
-
One other question, should there be an Apply button on each of the config tabs or do you have to go back to the first one to click Apply? There is only the one showing on my version.
Stuart
-
Only the first tab needs Apply. The reason is that the items on the first tab have to be copied elsewhere in the program before they are recognised, whereas the items on the other tabs are read directly by the program as needed. Removing the unnecessary 'Apply' buttons from the other tabs was part of the tidying-up in this version. Sorry if it caused confusion.
-
No problem I just thought I'd seen them before (and I had) I did hit the apply button just in case on the 1st tab ;)
Stuart
-
I noticed that the recording is stopped if a resync occurs. The event log says "Unknown Event" and "No DSL connection" is displayed permanently.
Shouldnt it resume recording as soon as the DSL connection is established?
-
I noticed that the recording is stopped if a resync occurs. The event log says "Unknown Event" and "No DSL connection" is displayed permanently.
Shouldnt it resume recording as soon as the DSL connection is established?
Yes, the present arrangement isn't ideal. I think a better option would be to keep sampling while the connection is down and just record zero values during that time. I'll try to build that into the next version.
-
I noticed that the recording is stopped if a resync occurs. The event log says "Unknown Event" and "No DSL connection" is displayed permanently.
Shouldnt it resume recording as soon as the DSL connection is established?
Yes, the present arrangement isn't ideal. I think a better option would be to keep sampling while the connection is down and just record zero values during that time. I'll try to build that into the next version.
Ah, morphium has raised one of the points I had noticed. I agree that to record zero values would be the best solution for that situation.
My other observations:
- A zero size file called 'test' is created. Possibly generated by the snapshot process?
- When configuring the graph colours, there are more than just colours offered in the option list.
- Although the graphs were configured to have a plain white background, the SNR graph has a distinct pink tinge. Example below.
- The Speed graph does not have a Take snapshot button. Example below.
- WIth the Bitloading graph, right-clicking below the chart does not clear the details. Only right-clicking in the region of the instructions will work. Examples below -- please note the position of my cursor in each example.
-
Thanks for those comments:
1. Yes, the zero-byte file is a test to make sure that the directory is writeable. No doubt there's a more elegant way to check this, but it's a low priority.
2. The items which aren't specific colours are the current system default colours for various parts of the display. The list very possibly includes items which don't exist on every system.
3. Your description of that colour as 'pink' had me puzzled for a moment. :) I must have omitted to apply the changed colours to every graph. Will be fixed.
4. It does have a snapshot button actually, but the positions of the features below the graphs have an annoying habit of drifting around all by themselves. I thought I'd fixed this, but obviously I haven't. Will be fixed.
5. This did work as described at one time, but I agree that it doesn't now. Will be fixed.
-
Thank you, Eric.
- Perhaps it could be named something else other than 'test' -- preferably unique to rs-ux -- and then deleted once the directory status has been verified?
- There are not only just colours in that list . . .
- I don't know how to describe the colour . . . other than 'not white'.
- :)
- :)
-
1. The obvious answer is often the best one - yes I can delete the file after verifying the directory. [Edit - now implemented]
2. I don't know if we're at cross-purposes here. All the items that I see on the list are either colours or specific GUI features, such as 'Desktop', 'Window' and 'Menu', each with a little square of colour displaying the system default colour for that feature.
3. The colour in question is pale yellow - RGB code $FFFFD8. The graphs have always been that colour by default (I just happen to like yellow).
-
2. I don't know if we're at cross-purposes here. All the items that I see on the list are either colours or specific GUI features, such as 'Desktop', 'Window' and 'Menu', each with a little square of colour displaying the system default colour for that feature.
I'm not sure . . . :-\
I've attached two screenshots. In the first you will see that I have defined the 'Graph background' as 'Form' and in the second as 'ScrollBar'. Very peculiar colours for the 'Graph background'; perhaps nonsensical? ???
-
I agree with you that it's a bit inconsistent and rather confusing. I should explain that I'm just using an off-the-shelf colour selector which is part of the Lazarus system, and the names used for the system colours are built into that component. However, having investigated a bit more, I see that I can exclude some sections of the list, to leave out the less relevant parts, so I'll be doing that today. Thanks for helping me towards a small improvement in the program. :)
-
That's great. :thumbs:
But please don't think that you have to rush such enhancements into existence. As long as they are noted in the 'ToDo' list, that will be a good thing. :)
-
I am getting a few times where it just says no data returned and does nothing, on hitting the start button again the little window pops up which I guess might say exception but is blank and on closing this with the X rs-ux terminates. I dont know whether this is related to the 622 as I never saw it with the 612.
One more thought could the event log be auto saved in the graph snapshot folder say every hour or so?
Stuart
-
I've made some changes to the program to deal with the 'No stats' problem more gracefully. What it now does is log the event, record zero values for that sample, and carry on sampling. This seems to work well. I'm finding the same by the way, so I think it's an issue with the HG622 failing to respond from time to time.
I could autosave the event log. I'll put this on the todo list.