Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: roseway on June 18, 2014, 04:13:22 PM
-
Changes since v4.54.7:
- improved signal attenuation reporting to include more modem/routers
- HG622 override options are now saved
- made some changes to deal with false positives in the HG622 detection
- corrected repeating log event messages when HG622 is detected
- alert triggers for CRC and FEC events can be per-minute or per-sample values
Users of the HG622 will notice that sampling takes an extra two seconds before it's detected as an HG622 type. You can bypass this extra time by setting the override option "Is HG622 type".
Users of the HG612, if you have been running v4.54.7 with the override option "Not HG622 type" set, then please unset that option to check that the auto detection works properly now.
Thank you all.
http://www.s446074245.websitehome.co.uk/downloads.html
-
I am glad to say this version is happy with the HG612 and the issues i had in the last version has been fixed, and auto dectection is working :)
Thanks Eric well done.
-
Eric it seems all OK here. Just one very minor thing, the Email Details and the Triggers boxes you draw on the Alerts config tab are slightly too small height wise on my Windows system. Not checked the Linux version yet.
Stuart
-
Observations from The Cattery --
There is a green camera icon present below the SNR Margin, the Connection Speed, the Tones and the Errors graphs.
There is a burgundy camera icon present below the Stats, the Telnet Data and the Event Log displays. The Stats display also has a burgundy coloured clip-board/notepad icon.
-
It would seem that the green camera saves an image and the burgundy (posh name for dark red ;) ) saves text at least according to the pop up text.
Stuart
-
That's the reason for the difference, yes. (It's actually maroon, by the way. :) )
-
I am glad to say this version is happy with the HG612 and the issues i had in the last version has been fixed, and auto dectection is working :)
Thanks Eric well done.
Many thanks NS.
-
Eric it seems all OK here. Just one very minor thing, the Email Details and the Triggers boxes you draw on the Alerts config tab are slightly too small height wise on my Windows system. Not checked the Linux version yet.
Stuart
I'll check that out, Stuart.
[Later] This turns out to be an odd little difference between Windows and Linux (GTK2) group boxes - the Windows boxes need to be dimensioned a bit larger to accommodate the same content. Fixed for the next release.
-
Was just mucking around in the Tones when I right click to get details on the specific tone the SNR: is always 0 dB, have done this on most of the tones and it still comes up with 0 dB
Image for reference uploaded.
-
Ah, I see that N*Star has done a b*cat! ::)
You need to configure "SNR per Tone" to display on the "Bitloading" graph . . .
I made that very mistake a while back and Eric kindly pointed out my "mishap".
-
Ah, I see that N*Star has done a b*cat! ::)
You need to configure "SNR per Tone" to display on the "Bitloading" graph . . .
I made that very mistake a while back and Eric kindly pointed out my "mishap".
Ah thats right BC I had to remove my configuration file (INI) a few weeks ago and start a fresh.
Thank you BC :blush:
-
Thank you both for your understanding. I should probably explain it a bit better on my website (and maybe put 'N/A' for the value when it's not available).
-
Thank you both for your understanding. I should probably explain it a bit better on my website (and maybe put 'N/A' for the value when it's not available).
I wonder Roseway if you could help me out as I just can't figure out how to turn on the SNR in tones as when I tick (Include with Bitloading) a window pops up and click OK but it unticks itself, I did this before but can't remember how I did it ::)
-
At the moment you have to make the choice - either include SNR per tone with the bitloading graph and don't autosave SNR per tone, or retain SNR per tone as a separate graph so that you can autosave it.
In truth, there's really no reason why you shouldn't be able to have both options at the same time. I'll add that to the todo list.
-
At the moment you have to make the choice - either include SNR per tone with the bitloading graph and don't autosave SNR per tone, or retain SNR per tone as a separate graph so that you can autosave it.
In truth, there's really no reason why you shouldn't be able to have both options at the same time. I'll add that to the todo list.
I now understand :) & Thanks BC & Roseway i've got the SNR displaying again in the Tone details section ;D
-
Excellent! :)
-
Excellent! :)
It still amazes me with DSLstats working away and HG612_Modem_stats working away while watching the World Cup in HD via USB tuner with World of Warplanes in the background with a dozen or so Websites open and no conflicts, it go's to show you that programmers these days are on the ball ;)
PS England 1 Uruguay 2
-
Eric this morning on checking my HG622 event log from overnight I saw:-
20 Jun 2014 03:38:02 *** Second stage login failure. Did you enable the option "Requires command to enter shell" by mistake?
20 Jun 2014 03:38:02 Second stage login failed
It is still running OK and does not seem to have caused any issues. Nothing has changed in the config and all the correct parts are there for an HG622.
Stuart
-
That message would have resulted in a single missing sample, so no other damage should have resulted. I'll make a small tweak to the relevant section of code (an extra 100 ms sleep before sending the second stage command).
-
That message would have resulted in a single missing sample, so no other damage should have resulted. I'll make a small tweak to the relevant section of code (an extra 100 ms sleep before sending the second stage command).
It is quite an old PC which does not run very quickly but at that time in the morning it should not have been doing anything extra, other times of day it does slow down quite a lot but I'd never seen it before that I remember.
Stuart
-
I don't think that the speed of the PC comes into it at this stage. It's more likely to be the speed of response from the modem.
-
One other thing I noticed is that the alerts in the event log still show as per minute rather than per sample but I believe the actual numbers are per sample, at least the one I looked at seemed right according to the graph.
Stuart
-
Yes, sorry, you're right. The alert message always says per minute. I'll fix that before the next release.