Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: Bald_Eagle1 on May 15, 2014, 09:14:02 PM
-
15/05/2014:
A version 2.1 revision to the HG612 Modem Stats package has now been released.
It is available here:-
http://www.freewarefiles.com/HG612-Modem-Stats_program_84567.html (http://www.freewarefiles.com/HG612-Modem-Stats_program_84567.html)
Click the Blue Download Now! button & choose one of the Download Mirrors.
It is still currently aimed only at VDSL2/FTTC connections for Microsoft Windows users, using a Huawei HG612 modem or a ZyXel VMG8324-B10A combined modem/router.
The package has been fully tested on XP, Vista, Windows 7 & Windows 8/8.1 systems.
What΄s New in version 2.1:
Added the option to record extra debugging information.
Along with Extensive event logging, this option can be turned OFF, with very minimal data stored.
Turning these options OFF speeds up the programs, so it *may* be necessary
to apply a different PC speed setting in the event of failed data harvests
for faster PCs.
Added option to choose the PC speed setting.
FAST actually slows the programs down by adding slight pauses in order
to ensure the modem can keep pace with the PC.
SLOW adds no pauses. This speeds up the programs on slower PCs.
MEDIUM is the middle ground between FAST & SLOW settings.
ONGOING_ISRUNNING files are now always deleted, but a record of
when 2 instances of HG612_stats.exe were running is stored in a log file.
Moved various log files to a new folder named Event & Error Logs to keep them together
Fixed error in modem_stats.log & in Ongoing stats graphs.
US_OHFErr(i.e. US CRC) data was incorrectly being stored as DS_OHFErr
US_OHFErr.png was thus incorrectly plotting DS_OHFErr data
This error was carried into line_stats__FULL_MONTY_P-xxxxxxxx-xxxx.png
Added support for ZyXel VMG8324-B10A combined modem/router.
Not actually tested, but it is believed this option will also
work with other ZyXel modem/router combinations.
Fixed an issue with some user defined folder names that included spaces not beng recognised
Added drop down list of modems in the GUI to select from.
If a modem isn't chosen or if using an older version of the ini file, the programs will default to using the HG612
Added the option to choose/create a different folder for the ongoing modem_stats.log & xlogfile.txt
Added US OHFErr (FEC) errors graph to FULL__MONTY montage of Ongoing Stats.
Added more error checking in get_data() function, forcing a controlled exit if 'stuck' in a loop attempting to obtain data.
Cosmetic graph appearance changes
Added HG612's firmware version to pbParams stats window.
Improved efficiency of snapshot graphing program (GRAPH6.exe)
HG612_current_stats.exe now passes a parameter to GRAPH6.exe to confirm
how the Plink log was generated i.e. via a scheduled or resync event,
manually generated via HG612_current_stats.exe or by dragging & dropping
a Plink log onto the GRAPH6.exe program icon.
Added support for VDSL2 Profile 8a (as used in the Isle of Man)
New users should simply extract the contents of the zip file to Drive C:, ensuring "Expand Folders" or similar setting is selected for a default setup.
Existing users of version 2.0 should extract all the files & subfolders to the relevant existing folders to ensure the slightly different operation of the package is picked up.
Once all the files are in place, existing users should delete the original HG612 Stats Program task & create a new one via the Settings GUI.
By default, Current (snapshot) data will be harvested & plotted every 8 hours, starting at 06:00 & Ongoing data will be harvested every minute, being plotted at 06:00 each day.
These settings can be easily adjusted or logging and/or automated graphing turned off via the Settings GUI.
As always, your feedback, comments & suggestions for further enhancements are welcomed.
-
Fixed error in modem_stats.log & in Ongoing stats graphs.
US_OHFErr(i.e. US CRC) data was incorrectly being stored as US_OHFErr
US_OHFErr.png was thus incorrectly plotting DS_OHFErr data
This error was carried into line_stats__FULL_MONTY_P-xxxxxxxx-xxxx.png
I'm not sure I understand your explanation of the above . . . ???
-
Thank you b*cat.
Now corrected.
It should have read:-
US_OHFErr(i.e. US CRC) data was incorrectly being stored as DS_OHFErr
-
Ah, it now makes sense. Thank you for the fix and the explanation. :)
-
Cheers guys. I think Im already running this if its the same one you sent last week.
Just cant really check anything or change anything atm though.
-
I think I'd already fixed it by then.
If US_OHFErr(i.e. US CRC) & DS_OHFErr are identical, it's the old (incorrect) version.
-
BE see this post here.
http://forum.kitz.co.uk/index.php?topic=13973.msg262824#msg262824
Snapshot graphs broken for me on 2.1
I get a plink file but no graphs.
-
I have responded to the message that you linked to.
-
I can confirm that everything seems to have been running flawlessly since my last report to BaldEagle. Ive had a quick scan through the error logs and I cant see anything glaringly obvious.
For the record, I think its fair to say my PC would be classed as fast
CPU = i7-3770 @ 3.4GHz 3.90 GHz which according to Windows Experience is 7.8
Memory is also 7.8 with Disk transfer rate at 7.9
Im running Windows Pro 7.1
Over the past few weeks I'm happy to report that Ive run HG612 ModemStats under various settings Fast/Medium and with extensive logging on/off without any issues. To also try and identify any issues the graph snapshots have been running at one hour intervals but this also seems ok.
Because Im aware that there have been a couple of major updates over the past week whilst Ive not been able to get to the PC properly and Ive also been getting any updates direct from BE.... I propose to completely start again from scratch just like anyone installing for the first time would, so that I can set my own prefs such as file location and logging times.
Huge thanks to BaldEagle for his time and effort into producing the scripts and Ronski for the updated Zyxel GUI. :thumbs:
--------
ETA
Attached full monty stats for the past 7 days.
-
I propose to completely start again from scratch just like anyone installing for the first time would, so that I can set my own prefs such as file location and logging times.
Houston, I have a problem. No stats are being obtained.
On the first run it created a Current-isrunning log in the scripts folder which didnt clear. This then seemed to cause an issue. I cleared HG612_stats.exe from Task Manager, but the problem just continually re-occurs on each subsequent run
19/05/2014 14:10:00.18 - ONGOING-ISRUNNING-141000-167.TXT - Start of [HG612_stats.exe] - **** Version 2.1 ****
19/05/2014 14:10:00.30 - ONGOING-ISRUNNING-141000-167.TXT - Immediately after ini_parse() - About to determine the OS version. ERROR.LOG status = 0,
19/05/2014 14:10:00.31 - ONGOING-ISRUNNING-141000-167.TXT - *** Windows version = [6.1.7601] ***
19/05/2014 14:10:00.33 - ONGOING-ISRUNNING-141000-167.TXT - In [HG612_stats.exe] - After obtaining the OS version. ERROR.LOG status = 0,
19/05/2014 14:10:00.36 - ONGOING-ISRUNNING-141000-167.TXT - ERROR.LOG successfully opened. Status = 1,
19/05/2014 14:10:00.46 - ONGOING-ISRUNNING-141000-167.TXT - ONGOING-ISRUNNING-141000-167.TXT created. Status = 1,
19/05/2014 14:10:00.60 - ONGOING-ISRUNNING-141000-167.TXT - There are 1 instances of HG612_stats.exe running. Status = 1,
19/05/2014 14:10:00.61 - ONGOING-ISRUNNING-141000-167.TXT - Continuing as there are only 1 instances of HG612_stats.exe running **. Status = 1,
19/05/2014 14:10:00.62 - ONGOING-ISRUNNING-141000-167.TXT - WSAStartup() SUCCESSFUL!!! Status = 1,
19/05/2014 14:10:00.63 - ONGOING-ISRUNNING-141000-167.TXT - getaddrinfo() O.K. Status = 1,
19/05/2014 14:10:00.65 - ONGOING-ISRUNNING-141000-167.TXT - connect() O.K. Status = 1,
19/05/2014 14:10:00.66 - ONGOING-ISRUNNING-141000-167.TXT - *************************************************************************
19/05/2014 14:10:00.67 - ONGOING-ISRUNNING-141000-167.TXT - At start of expect("gin:"), times in loop = 01 *** numbytes = 0
19/05/2014 14:10:00.68 - ONGOING-ISRUNNING-141000-167.TXT - ****** PC_Speed is set as "MEDIUM" in the ini file, times in loop = 01 *** numbytes = 0
19/05/2014 14:10:00.70 - ONGOING-ISRUNNING-141000-167.TXT - At start of expect("gin:"), sleeping for 0.250 seconds *** numbytes = 0
19/05/2014 14:10:00.97 - ONGOING-ISRUNNING-141000-167.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 33
19/05/2014 14:10:00.99 - ONGOING-ISRUNNING-141000-167.TXT - End of expect("gin:")
19/05/2014 14:10:01.01 - ONGOING-ISRUNNING-141000-167.TXT - *************************************************************************
19/05/2014 14:10:01.02 - ONGOING-ISRUNNING-141000-167.TXT - expect("gin:") O.K. Status = 1.
19/05/2014 14:10:01.04 - ONGOING-ISRUNNING-141000-167.TXT - reply(config.Username) O.K. Status = 1.
19/05/2014 14:10:01.05 - ONGOING-ISRUNNING-141000-167.TXT - *************************************************************************
19/05/2014 14:10:01.06 - ONGOING-ISRUNNING-141000-167.TXT - At start of expect("ssword:"), times in loop = 01 *** numbytes = 0
19/05/2014 14:10:01.08 - ONGOING-ISRUNNING-141000-167.TXT - ****** PC_Speed is set as "MEDIUM" in the ini file, times in loop = 01 *** numbytes = 0
19/05/2014 14:10:01.09 - ONGOING-ISRUNNING-141000-167.TXT - At start of expect("ssword:"), sleeping for 0.250 seconds *** numbytes = 0
19/05/2014 14:10:01.36 - ONGOING-ISRUNNING-141000-167.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 17
19/05/2014 14:10:01.38 - ONGOING-ISRUNNING-141000-167.TXT - End of expect("ssword:")
19/05/2014 14:10:01.39 - ONGOING-ISRUNNING-141000-167.TXT - *************************************************************************
19/05/2014 14:10:01.41 - ONGOING-ISRUNNING-141000-167.TXT - expect("ssword:") O.K. Status = 1.
19/05/2014 14:10:01.42 - ONGOING-ISRUNNING-141000-167.TXT - reply(config.Password) O.K. Status = 1.
19/05/2014 14:10:01.43 - ONGOING-ISRUNNING-141000-167.TXT - *************************************************************************
19/05/2014 14:10:01.45 - ONGOING-ISRUNNING-141000-167.TXT - At start of expect("ATP>"), times in loop = 01 *** numbytes = 0
19/05/2014 14:10:01.46 - ONGOING-ISRUNNING-141000-167.TXT - ****** PC_Speed is set as "MEDIUM" in the ini file, times in loop = 01 *** numbytes = 0
19/05/2014 14:10:01.47 - ONGOING-ISRUNNING-141000-167.TXT - At start of expect("ATP>"), sleeping for 0.250 seconds *** numbytes = 0
19/05/2014 14:10:01.74 - ONGOING-ISRUNNING-141000-167.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 5
19/05/2014 14:10:01.76 - ONGOING-ISRUNNING-141000-167.TXT - Still in expect("ATP>") loop, times in loop = 02
Looks like I will have to roll back to HG612 Modem Stats with Spaces.
attached gui settings screenie
-
Just to confirm Im now running 2.1 build 18/05/2014 20:31:50 with the same issue.
-
kitz your first post where everything hunky dory is 2.0 or 2.1?
sorry BE I will probably send lgos tommorow now, got busy and now am out of energy due to weather.
-
Just to confirm Im now running 2.1 build 18/05/2014 20:31:50 with the same issue.
Try directly running HG612 Run.exe from Windows, also the current stats exe as well. Sometimes Windows UAC stops the programs from running and there's an option not to ask again.
-
ry directly running HG612 Run.exe from Windows, also the current stats exe as well.
No still doesnt work. I do get a cmd window which sticks at the following - which i think is the same as in the error log I posted above.
In expect("ATP>") loop, loop_ctr = 1
Sleeping for 0.000 seconds
total_sleep_time = 0.000 seconds
In expect("ATP>"), loop_ctr = 1, numbytes = 2. rxbuf =:-
loop_ctr = 2
Still in expect("ATP>") loop, loop_ctr = 02
In expect("ATP>"), loop_ctr = 2, numbytes = 3. rxbuf =:-
>
loop_ctr = 3
Still in expect("ATP>") loop, loop_ctr = 03
Ive also tried running from the root of c:/ just to make sure theres not any path errors.
The version I have the problem with is the package I downloaded from your site today which was dated 15/05, updating to the beta 18/05 is still broken for me.
kitz your first post where everything hunky dory is 2.0 or 2.1?
V2 build date 09/05/2014
-
Just realised
In expect("ATP>"), loop_ctr = 1, numbytes = 2. rxbuf =:-
That aint ever going to happen in the Zyxel... which will probably be why its getting stuck and not reporting any stats.
Confirmed the Zyxel has been selected in the GUI and the .ini file has the following info
[Modem]
Modem_Type= ZyXel VMG8324-B10A
IP_address = 192.168.1.1
Username = admin
Password = xxxxx
Shell = sh
-
BaldEagle spotted something in my ini
Modem_Type= ZyXel VMG8324-B10A
It should actually be
Modem_type= ZyXel VMG8324-B10A
This causes HG612modem stats to think no Modem_type has been set so it defaults to the HG612
... and this is why I was getting the ATP> errors looping
Ive manually edited my ini file to Modem_type and all is good again. This problem will only affect non HG612 users who use the GUI to amend their modem type.
@ronski
Can you please make the relevant edit for future versions. Thanks :)
-
@ronski
Can you please make the relevant edit for future versions. Thanks :)
Hi Kitz, I'm working on a fix, unfortunately it's not quite as straightforward as editing the values written by my code, as the code that writes/reads the ini file is not case sensitive when it comes to key names. Once Modem_Type exists it will happily read, and write back to that key name without changing it to Modem_type.
I've almost written something (had it working but needed go to work) to process the ini file, and change the case in the Modem_type key name, I should have this updated tonight. This bug will only affect new ini files, or ini files that don't have a Modem_type key, this is why it hasn't affected you before - I'm guessing you've recently deleted your ini file and recreated it.
-
I'm guessing you've recently deleted your ini file and recreated it.
Thanks ronski.
Yes I started again with a fresh download from your site. Theres no hurry as mines working now after a manual edit... and it will only affect those not using a HG612. As long as we are aware in the meantime :)
-
i cant get it to work with my ZyXel VMG8324-B10A , ive put the password in for the telnet, but no stats come up, ive selected zyxel in the modem bit as well, any ideas? i can log in via putty with my details.
-
Balb0wa
Look for the HG612_stats.ini file in the Scripts folder.
Open it in notepad or notepad++
Find
[Modem]
Modem_Type= ZyXel VMG8324-B10A
change it to a small 't'
[Modem]
Modem_type= ZyXel VMG8324-B10A
Save your changes & hopefully it should then work :)
-
worked a treat, thanks :-)
Balb0wa
Look for the HG612_stats.ini file in the Scripts folder.
Open it in notepad or notepad++
Find
[Modem]
Modem_Type= ZyXel VMG8324-B10A
change it to a small 't'
[Modem]
Modem_type= ZyXel VMG8324-B10A
Save your changes & hopefully it should then work :)
-
Ive manually edited my ini file to Modem_type and all is good again. This problem will only affect non HG612 users who use the GUI to amend their modem type.
@ronski
Can you please make the relevant edit for future versions. Thanks :)
I've updated the GUI to modify the ini file, simply running the GUI will check and fix the problem once you've updated to the latest release version, no user intervention is required.
-
That's great RONSKI & I can confirm it does what it says on the tin.
I just edited my ini file to use an upper case 'T' in:-
[Modem]
Modem_Type= HG612
I ran the editor & saw it updating.
The result was indeed a lower case 't' without any manual intervention:-
[Modem]
Modem_type= HG612
-
Thank you Ronski :flower:
-
I have attached updated v 2.11 beta test versions of HG612_stats.exe & HG612_current_stats.exe.
From testing so far, it does appear that these versions now manage things 'better' for faster PCs without too much of a program running time penalty.
Subject to any feedback received (relevant comments along with extracts from CURRENT_ERROR.LOG_file_ERROR.TXT and ONGOING_ERROR.LOG_file_ERROR.TXT), I may be be able to make further speed improvements without compromising program reliability.
The most relevant tests would be to try the various PC Speed settings (SLOW, MEDIUM, FAST) firstly with Extra debugging info logging switched ON & then again with it switched OFF.
In 'normal' & unattended everyday use, Extra debugging info logging will not be needed.
However, for testing purposes, it does need to be switched between ON & OFF to get a full picture of what is happening & whether further improvements can/need to be made.
I have also made some slight improvements to the graphing programs, but those are not relevant for these tests, so I haven't attached them.
-
RE this app, i recently installed it i have a question, Am i supposed to keep getting a windows open file warning pop up From HG612_stats.exe ? When i click ok , my pc speaker beeps and both lan leds on the modem flash briefly is this normal or is something configured incorrectly in my set up
-
I suspect that UAC (User Access Control) on your PC is asking for permission to run HG612_stats.exe each time it runs. Hence the pop up.
Could you post a screenshot of the pop up for us?
If that's the case, depending which version of Windows you are using there should be an option to "always allow" or "don't ask again" (or words to that effect).
If the programs are set up correctly, once you have created the logging task & "always allow" is confirmed, HG612_stats.exe should run invisibly every minute until you turn the logging OFF.
You may also need to "always allow" HG612_Run.exe, HG612_current_stats.exe, GRAPH6.exe & graphpd.exe.
If any of those programs are 'stuck' in Windows Task Manager you will need to end their processes & by manually running them, again, select the "always allow" option.
-
Hi. BE 1 The o/s version is winxpsp3, so none of the UAC bugging ,here is a screen grab
-
O.K.
Just untick the "always ask" box.
That should sort it (providing you feel the publisher is trustworthy, that is :)).
-
That's weird i'm sure i tried that before, now it has stopped the pop up thank's, just got to find a way stopping my pc's internal speaker/buzzer from bleeping 2 or 3 times every few mins or so ,lol
-
I think I had stopped the beeping in the versions attached to the message above:-
http://forum.kitz.co.uk/index.php?topic=13974.msg263365#msg263365
Let me know if you try them & the beeping is still present & I'll post a slightly newer version.
Turning OFF Extra debugging info logging via the GUI should also stop the beeping.
-
I think I had stopped the beeping in the versions attached to the message above:-
Turning OFF Extra debugging info logging via the GUI should also stop the beeping.
worked just fine, thanks BE_1 for your prompt assistance, much appreciated the beep, beep,beeping, every minute or so was starting to annoy me a little,lol
-
Just to officially confirm that so far so good from here. Im running settings at medium and have just turned off logging so will see how that goes over the next few days. A manual run of graphpd and a snapsot worked fine.
The new graph.exe also works good.
Thanks BE :)
-
Thanks for the feedback, Kitz
You're welcome.
I'm just happy to be able to put 'something' back in in return for all the friendly advice & suggestions I've received since registering on this forum.
-
Have been experiencing a critical stop error sound every 1 minute in Windows 8.1 when I toggle off ongoing stats the error sound disappears so this must relate to HG612_Modem_stats running/ harvesting the data every 1 minute.
-
That annoying issue has been fixed in updated version 3.0:-
http://forum.kitz.co.uk/index.php?topic=14118.0
-
That annoying issue has been fixed in updated version 3.0:-
http://forum.kitz.co.uk/index.php?topic=14118.0
AH thanks for the link BE1 I seemed to have overlooked that update.