Kitz Forum

Broadband Related => Router Monitoring Software => Topic started by: Ronski on February 24, 2015, 07:31:11 AM

Title: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on February 24, 2015, 07:31:11 AM
Today we have released version 5, for existing users you can update all programs from within the graphic user interface, in due course I will also upload version 5 to Freeware files.

I have found from time to time that certain anti virus programs complain, or block some parts of our programs, if in doubt you can use www.virustotal.com to scan any file. Please report any false positives to your anti virus provider.

Change log.

Quote
5.0.5533.12916   24-02-2015

      Version 5 release
      Added G.INP indicator to main stats tab under connection up time.
      
4.0.5419.17215   2-11-2014

      Altered task priority code, it's now stored as the actual value used, this allows the editor.ini to be edited to used non standard values (0 to 10)

4.0.5356.15443   31-08-2014

      Fixed bug which meant settings modified flag was always set after opening GUI if not using My DSL WebStats
      Alteration of labels on My DSL WebStats setting tab.
      
4.0.5356.14100 31-08-2014

      Beta release of version 4
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on February 24, 2015, 08:52:38 AM
thanks ronski.

also glad you kept the priority stuff intact.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on February 24, 2015, 09:03:31 AM
gui on first startup had a red box saying log error, but that box has dissapeared now.

There is a issue bald eagle side of things, will put in a new thread.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on February 24, 2015, 10:06:03 AM
I had the same issue when I updated here at work, seems to be an issue reading the modem log whilst updating the programs.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bowdon on February 24, 2015, 10:35:13 AM
Thanks for the update mate.

I had to lower my avast shields for 10 minutes while it updated. With the shields up it blocks one of the files and the update doesn't happen. But lowering them for 10 minutes and attempting the update works. Avast did scan one of the files (i forget which) when I put the shields up again after. But it OK'ed it, so all is good.

Avast is slowly becoming annoying for the false positives.

Anyways, good update :)
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on February 24, 2015, 10:42:15 AM
I use Avast, and it blocked upload.exe, but if you scan the file it pronounces it as safe, very odd that it comes up with two different results. Please report it as a false positive.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bowdon on February 24, 2015, 11:45:26 AM
I ended up having an argument on the avast free forum 2 weeks ago about another .exe file. Sadly the moderators on there seemed to take a stone wall opinion of false positives. It's worth a try I suppose, if it becomes an issue. So far now its working correctly.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on February 24, 2015, 01:27:03 PM
ahh so uploading is now a seperate exe, I need to run another update to get it.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bowdon on February 24, 2015, 03:19:53 PM
I've noticed Avast seems to want to scan every .exe file. But they all come out good. It only does it the once.

Btw, I like the G.INP enabled information. Does this come from the modem, or is it relaying information back from the cabinet about the line?

The reason I ask is I still havent updated the modem firmware yet, so I'm wondering is it saying No, because its not seen on the modem, and could still be on the line (but the modem isn't using it)?

Sorry if that question sounds a bit confusing.. nearly confused myself too lol
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on February 24, 2015, 03:38:49 PM
It's comes from  the modem data, BE1 can tell you more about as that's all his handy work, I just lookup the relevant field in the log file generated by his program.

We are only aware of one person that currently has G.INP enabled,  BT have only just started rolling it out.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on February 24, 2015, 06:49:53 PM
If G.INP hasn't yet been enabled (whether it's due to an old modem firmware version or the cabinet's DSLAM not yet using it), somewhere in each row of the ongoing modem_stats.log should be the text "NO_G.INP".

When it is enabled, each row should contain the text "G.INP"



Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tbailey2 on February 24, 2015, 08:04:32 PM
G.INP is now also flagged up in MDWS as soon as it's detected on a line by using this new data from both upload programs (latest versions only).

On the large page (only, not the small one) of All User Stats it now colours the background in Lime Green of the DSLAM last column when present. Same colour as we were using the for the test detection idea which is now defunct.  No colour shown there if it's not present.

On individual user stats graphs, the status bar above the graph now shows an additional column at far left with same colour background that says G.INP if it's enabled. If not there's nothing there.

Attached shows both.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on February 26, 2015, 08:23:44 AM
who is the user? I dont see anyone.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on February 26, 2015, 11:38:54 AM
who is the user? I dont see anyone.

I do  ;)

On the large page (only, not the small one) of All User Stats it now colours the background in Lime Green of the DSLAM last column when present.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on February 26, 2015, 11:51:52 AM
and the user is?

I dont know how to get to the large page from the normal pages.

site seems dead now, nothing loading.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: NewtronStar on February 26, 2015, 12:38:34 PM
and the user is?

I dont know how to get to the large page from the normal pages.

site seems dead now, nothing loading.

here is how to get large page (full page)

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on February 26, 2015, 01:05:49 PM
it's danbl.

When you have all user stats listed, just above the Update button, it states A Full Page version is HERE with more data, simply click the HERE.

Edit. Had noticed NS post on a new page.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on February 26, 2015, 01:52:45 PM
ahh ok thanks guys.

danbl isnt on the list I can see O_o

I found him in the normal page, but dont see him on the full user list.

ok found him on the all users page now, so its a green box over the cabinet name.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bowdon on March 07, 2015, 11:00:03 AM
I updated to the latest version of avast today and when it reboots it did a pop-up saying that it had blocked the hg612 stats program from starting.

It didnt give me an option to say it was safe. Only to fill out a form to say its a false positive, which apparently just tells them to fix it in the next update. A fat lot of good that is for me now. I'm going to try and see if I can find the block in avast to unblock it.

I'm really losing my patience with Avast these days. Its aragont attitude of some of the mods on their forum, its overblocking actions, and I can't even remember when was the last time a pop up came about updated virus definitions. These days its all advertisements and news!

Anyone recommend a good anti virus program? I've had avg in the past.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on March 07, 2015, 11:19:21 AM
You need to find the Virus Chest, and from there right click on the appropriate entry and choose restore and add to exclusions. I've added the chest to the four shortcuts which appear when you open the main Avast interface, as it's such a pain to find otherwise. Simply right click on the short cut and choose the option you want, in this case Virus Chest.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bowdon on March 07, 2015, 11:24:02 AM
Thanks mate.

I did that then had to restart its logging task and now its back working.

I've been on the Avast forum asking why don't they add a 'file is safe' option on the pop up, especially when they have an option for submitting a false positive report (which I did). Part of that is saying I trust the program. Hopefully they will correct it by the next update.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on April 01, 2015, 12:32:23 PM
ronski seems I Cannot update, error below.

Code: [Select]
A backup of GRAPH6.exe has been made.
A backup of Graphpd.exe has been made.
A backup of HG612 Stats logging GUI.exe has been made.
For some strange reason we had an error backing up HG612_current_stats.exe
Error: Access to the path 'F:\Drivers\HG612\HG612_Modem_Stats_Programs-CURRENT\Scripts\HG612_current_stats.exe.BAK' is denied.
Update abandoned.

If I untick the "backup old programs" box, the same error still appears so still tries and fails to make the backup when I disable backups as well.

ok the .bak file was read only, updated now.

However I dont have the latest g.inp fixed binary, its 5.0.0.1 not 5.0.0.2
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on April 01, 2015, 01:22:09 PM
I guess your reply above answers my question in the other thread.

When the updates are carried out there are two types of backups, one is optional. This one will copy the files to a folder and they are date/time stamped.
 
The other, which yours is failing on is a temporary backup, which should be deleted after successfully installing the updates.

Can you check and make sure that no .bak files exists in your scripts folder, also check that the path shown is the correct path.

Did the other programs update ok?

Oh, just read the bit stating it was read only, don't know why. You should have version 5.0.0.3.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on April 01, 2015, 03:57:07 PM
sorry one file is 5.0.0.3, current stats, rest are older. is that correct?
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on April 01, 2015, 08:04:10 PM
It's advisable to disable you're anti virus whilst performing updates, especially Avast.

Latest versions numbers attached
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: NewtronStar on April 17, 2015, 10:36:07 PM
I liked HG612 in the early days think it was version 3.00 it was nice an simple it's has just gone over my head on later versions to much info puts me sleep an Openreach Engineer would just run away from all that info  :D

Sorry BE1 it's just my view all i look at these days in order are SNRM CRC's FEC's ES's and Bitloading tones though rtx_tx and RSCorr Bearer1 is becoming useful with G.INP.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on April 17, 2015, 10:42:29 PM
I have split the topic as I had accidentally posted in Ronski's thread.

The graph posts are now here:-

http://forum.kitz.co.uk/index.php/topic,15346.0.html


The problem is that ALL the data is now relevant, but there's just such a lot of it that I couldn't decide which parts were the MOST relevant.

Maybe as Kitz mentioned, a simpler montage showing the most vital data (perhaps something like I have posted in the new thread) could lead to needing to see all the other data?


Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 22, 2015, 10:04:26 PM
As of tonight it's stopped uploading to MDWS for some reason unless i run the HG612_Run.exe process manually, it then updates  the GUI and uploads to the MDWS for a short time before stopping again , the program GUI it's self isn't working as it is not updating stats from the modem
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 22, 2015, 11:12:17 PM
As of tonight it's stopped uploading to MDWS for some reason unless i run the HG612_Run.exe process manually, it then updates  the GUI and uploads to the MDWS for a short time before stopping again


Have your programs all been updated to the latest versions (see attached).

I'm running Windows 7 here & I didn't experience this issue at all during my quite extensive testing prior to the v 5.1 release.

Is there anything in the ONGOING_ERROR.LOG_file_ERROR.TXT log that might indicate when/why it ceased working properly?


What's your MDWS username?



Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 22, 2015, 11:22:50 PM
Yes updated to latest version and has been working fine until tonight, my MDWS user name is Tom34 the time on the gui is also stuck at 22:06
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 22, 2015, 11:25:46 PM
See if there is a 'stuck' instance of HG612_Run.exe and/or HG612_stats.exe in Windows Task Manager.
If so, end its process & see if that kickstarts the auto-logging again.

Is your GUI the same version/date as the one in my screenshot?

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 22, 2015, 11:31:22 PM
Another user had the same issue:-

https://community.plus.net/forum/index.php/topic,139651.0.html

Just checking again, it looks as though he is using a slightly older version of the GUI than mine.

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 22, 2015, 11:48:27 PM
I have got it going again after deleting all exceptions in my Av firewall and deleting the  scheduled task it creates,
Then i got the pop up asking to open the file every 2mins or so, so i un selected the warn me every time the file wants to open so far so good, the ongoing error log was too big for notepad ,so i deleted it since, as it be pointless having a log file that you can't read, imo  BTW all the versions are the same builds as in your SS BE, thanks for you speedy support, i think in my case something got corrupted  somehow ,
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 22, 2015, 11:53:58 PM
To keep the log files to a minimum size, you could disable the 'extra' logging (until there appears to be a program error):-

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 22, 2015, 11:57:07 PM
I have got it going again after deleting all exceptions in my Av firewall


Which AV/Firewall do you use?


Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 23, 2015, 12:13:45 AM
Eset SS v7 Just noticed that it had stopped harvesting stats again, this time i was able to the the HG612 stats.exe process in task manager stuck as you mentioned earlier, i simply killed the process and it started  running again
What would cause it to hang?
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 23, 2015, 08:23:11 AM
If you ever have to kill its process, depending how far it got before it got stuck, a file named something like ONGOING-ISRUNNING-072713-194.TXT should be left behind in the Scripts folder.

If you haven't already deleted any of those files, could you please post the most recent one for me to look at?
It should contain a list of all the processes running at the time HG612_stats.exe started running.



Strictly speaking, if something goes wrong, HG612_stats.exe should record the problem in ONGOING_ERROR.LOG_file_ERROR.TXT & exit gracefully.

Could you please post that file for me to examine?
You may need to compress it first for it to fit within the forum's attachment file size limit.


My suspicion is that either some other program is blocking or causing HG612_stats.exe and/or HG612_Run.exe to hang or that something else is accessing the modem at the same time which would corrupt the modem's responses to HG612_stats.exe's stats data requests at an unexpected stage.


Whenever more than 1 instance of HG612_stats.exe attempt to run at the same time, possibly if the first instance has been slowed down by something else hogging all the PC's resources etc, one or both of the instances should be exited & a record of it logged in the EXIT_2_INSTANCES.LOG file.


Here are a couple of examples from when my resource hungry AV program (AVG 2015) slowed my PC down when running its daily scan:-

23/02/2015  4:09:08.66 - ONGOING-ISRUNNING-040900-398.TXT - ** Exiting as there are 2 instances of [HG612_stats.exe] running. Status = 1,
23/02/2015  4:09:08.66 - ONGOING-ISRUNNING-040800-587.TXT - ** Exiting as there are 2 instances of [HG612_stats.exe] running. Status = 1,
23/02/2015  4:09:08.71 - ONGOING-ISRUNNING-040800-587.TXT - ** ONGOING-ISRUNNING-040800-587.TXT DELETED - Status = 1,
23/02/2015  4:09:08.71 - ONGOING-ISRUNNING-040900-398.TXT - ** ONGOING-ISRUNNING-040900-398.TXT DELETED - Status = 1,

That tells me that the instance of HG612_stats.exe from 04:08 was still running at the time the 04:09 instance started.
Both instances needed to exit to avoid any of them hanging.
 


23/02/2015  4:33:28.83 - ONGOING-ISRUNNING-043300-298.TXT - ** Exiting as there are 2 instances of [HG612_stats.exe] running. Status = 1,
23/02/2015  4:33:28.90 - ONGOING-ISRUNNING-043300-298.TXT - ** ONGOING-ISRUNNING-043300-298.TXT DELETED - Status = 1,

That tells me that the instance from 04:32 must have still been running when the 04:33 instance started, but this time, only the instance from 04:33 needed to exit.


Could you also post your EXIT_2_INSTANCES.LOG file so I can see what was happening at around the problematic times?


Once we can confirm what causes the issue, I can build in some code to deal with it.



EDIT:

I see that your most recent upload to MDWS was timed at 05:59 this morning so it seems the problem is still present, unless you intentionally stopped the uploads or that you PC or ROUTER went into sleep mode etc.




Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 23, 2015, 01:05:29 PM
Ok i uploaded  all 3 files you requested, and yes it appears to be hanging the process for some reason , the ONGOING_ERROR.LOG_file_ERROR.TXT .zip had to be renamed from the.rar extension because we can't upload files with a .rar extension, so you may have to rename it so it becomes a .rar again
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 23, 2015, 02:04:28 PM
This MIGHT be the problem:-

23/05/2015  6:00:07.56 - ONGOING-ISRUNNING-060000-109.TXT - *** Scheduled snapshot logging IS due, running [HG612_current_stats.exe].

That should go on to record this:-

23/05/2015  6:00:05.84 - ONGOING-ISRUNNING-060000-088.TXT - Normal End of [HG612_stats.exe]
23/05/2015  6:00:07.77 - ONGOING-ISRUNNING-060000-088.TXT - Start of [Upload.exe] - **** Version 5.1.0.0 16/05/2015 ****
23/05/2015  6:00:08.18 - ONGOING-ISRUNNING-060000-088.TXT - Now exiting [Upload.exe]. Status = 1,
 
23/05/2015  6:00:08.29 - ONGOING-ISRUNNING-060000-088.TXT - End of [HG612_stats.exe] AFTER WebStats stuff



Being as the rest of the 06:00 log was missing, I suspect that HG612_current_stats.exe was 'blocked' & therefore it didn't complete.
In turn, that could have stopped HG612_stats.exe from 06:00 from completing (i.e. hanging), meaning that it was still running when the next instance was due at 06:01:-


23/05/2015  6:01:00.15 - ONGOING-ISRUNNING-060100-109.TXT - Start of [HG612_stats.exe] - **** Version 5.1.0.0 16/05/2015 ****
23/05/2015  6:01:00.82 - ONGOING-ISRUNNING-060100-109.TXT - ** About to exit as there are 2 instances of HG612_stats.exe running. Status = 1,
23/05/2015  6:01:00.93 - ONGOING-ISRUNNING-060100-109.TXT - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1,
23/05/2015  6:01:00.95 - ONGOING-ISRUNNING-060100-109.TXT - About to close(sockfd). Status = 1,
23/05/2015  6:01:00.98 - ONGOING-ISRUNNING-060100-109.TXT - About to freeadddrinfo(res). Status = 1,
23/05/2015  6:01:01.03 - ONGOING-ISRUNNING-060100-109.TXT - ERROR.LOG successfully closed. Status = 0,
23/05/2015  6:01:01.04 - ONGOING-ISRUNNING-060100-109.TXT - *** End of [HG612_stats.exe] - 2 OR MORE INSTANCES WERE RUNNING. Status = 0,


There may well also be a 'stuck' instance of HG612_current_stats.exe that needs its process ending via Task Manager.


You could try running HG612_current_stats.exe manually, to see if Windows or your AV/Firewall asks if it should always be allowed or not.

If you are asked the question, select the option that always allows it or doesn't ask again.

You MAY also need to allow it via your AV/Firewall program to (hopefully) ensure this issue doesn't crop up again.


To test this out, after you are able to confirm that HG612_current_stats.exe runs all the way through to normal to completion when run manually, could you temporarily adjust the schedule interval in the GUI to 1 hour rather than the (probably) 8 hours default setting?

See the attached screenshot for where that setting is located.

It should then auto-run at the next hour & every hour following that.


Please let me know whether that resolves the issue or not in case I need to look somewhere else.





EDIT:

Some typos corrected

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 23, 2015, 02:43:10 PM
The processes are all allowed  to run and have rules in the AV firewall , so nothing obvious, i have  just deleated all the fw rules and all the Hips rules that the program creates in order to run, i have also run the HG STATS.exe  manually and it appeared to run without error, no pop up prompts from my AV
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 23, 2015, 02:47:17 PM
i have also run the HG STATS.exe  manually and it appeared to run without error, no pop up prompts from my AV


Does HG612_current_stats.exe run O.K. when run manually though & are any of the programs in the Scripts folder 'stuck' in Task Manager?

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 23, 2015, 03:36:36 PM
It hung again, in task manager the only process related that was stuck/hung was the HG612_stats.exe process i did notice just before i killed it what i think was another instance of the  HG612_stats.exe that disappeared abruptly

As for the HG612_stats.exe running as intended or not without being able to save the data in the cmd prompt window that it opens  when i run it manually i can't say for sure, even then  if it didn't generate an error  i would be none the wiser , but the window closes quickly , the process doesn't stay in the list of processes for long afterwards

When the HG612_stats.exe  is run it also runs AcroRd32.exe which is adobe reader i'm a little puzzled as to why this is associated with HG612_stats.exe ?
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 23, 2015, 04:22:44 PM
From MDWS, it looks as though the 14:59 instance ran O.K., but the 15:00 instance didn't.

If you had indeed set the snapshot schedule to run every hour, it 'appears' that running HG612_current_stats.exe from HG612_stats.exe is the problem.


What is in CURRENT_ERROR.LOG_file_ERROR.TXT from when the problem first reared its head?

It should look something like this:-

23/05/2015  0:00:05.39 - CURRENT-ISRUNNING-000005-287 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
23/05/2015  0:00:06.11 - CURRENT-ISRUNNING-000005-287 - From IsRunningVB.exe, there are 1 instances of HG612_stats.exe running. Status = 1,
23/05/2015  0:00:10.75 - CURRENT-ISRUNNING-000005-287 - Normal End of [HG612_current_stats.exe] - Status = 0,


23/05/2015  6:00:07.60 - CURRENT-ISRUNNING-060005-907 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
23/05/2015  6:00:08.09 - CURRENT-ISRUNNING-060005-907 - From IsRunningVB.exe, there are 1 instances of HG612_stats.exe running. Status = 1,
23/05/2015  6:00:08.46 - CURRENT-ISRUNNING-060005-907 - [HG612_stats.exe] is still running
23/05/2015  6:00:12.81 - CURRENT-ISRUNNING-060005-907 - Normal End of [HG612_current_stats.exe] - Status = 0,


In my example from 00:00, HG612_stats.exe will have completed quite soon after HG612_current_stats.exe started


In the example form 06:00, when my PC was also busy doing other things, HG612_stats.exe didn't complete so quickly & HG612_current_stats.exe waited for it to complete before continuing:-

23/05/2015  6:00:08.46 - CURRENT-ISRUNNING-060005-907 - [HG612_stats.exe] is still running


It might just be that HG612_current_stats.exe waits too long on your setup?
Your CURRENT_ERROR.LOG_file_ERROR.TXT log might confirm that one way or the other

I have just noticed from MDWS that the same thing appears to have happened at 16:00, so it at least appears that we're getting close to working out what needs changing.


Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 23, 2015, 04:25:57 PM
When the HG612_stats.exe  is run it also runs AcroRd32.exe which is adobe reader i'm a little puzzled as to why this is associated with HG612_stats.exe ?


Does AcroRd32.exe  run EVERY time HG612_stats.exe runs?

They are not associated, so that's another mystery for me to look into.

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 23, 2015, 04:38:57 PM
Quote
CURRENT_ERROR.LOG_file_ERROR.TXT


19/05/2015 21:00:07.82 - CURRENT-ISRUNNING-210007-732 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
19/05/2015 21:00:29.27 - CURRENT-ISRUNNING-210007-732 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015  0:00:08.09 - CURRENT-ISRUNNING-000007-967 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015  0:00:24.59 - CURRENT-ISRUNNING-000007-967 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015  3:00:07.90 - CURRENT-ISRUNNING-030007-826 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015  3:00:24.65 - CURRENT-ISRUNNING-030007-826 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015  6:00:08.27 - CURRENT-ISRUNNING-060008-201 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015  6:00:25.13 - CURRENT-ISRUNNING-060008-201 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015  9:00:07.85 - CURRENT-ISRUNNING-090007-779 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015  9:00:24.71 - CURRENT-ISRUNNING-090007-779 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015 12:00:07.85 - CURRENT-ISRUNNING-120007-779 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015 12:00:24.79 - CURRENT-ISRUNNING-120007-779 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015 15:00:08.40 - CURRENT-ISRUNNING-150008-264 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015 15:00:27.26 - CURRENT-ISRUNNING-150008-264 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015 18:00:09.01 - CURRENT-ISRUNNING-180008-889 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015 18:00:25.88 - CURRENT-ISRUNNING-180008-889 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015 21:00:10.26 - CURRENT-ISRUNNING-210009-982 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015 21:00:29.45 - CURRENT-ISRUNNING-210009-982 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015  0:00:08.24 - CURRENT-ISRUNNING-000008-107 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015  0:00:24.95 - CURRENT-ISRUNNING-000008-107 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015  3:00:09.65 - CURRENT-ISRUNNING-030009-467 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015  3:00:27.88 - CURRENT-ISRUNNING-030009-467 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015  6:00:08.26 - CURRENT-ISRUNNING-060008-154 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015  6:00:25.26 - CURRENT-ISRUNNING-060008-154 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015  9:00:08.04 - CURRENT-ISRUNNING-090007-967 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015  9:00:24.79 - CURRENT-ISRUNNING-090007-967 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015 12:00:08.15 - CURRENT-ISRUNNING-120008-061 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015 12:00:24.57 - CURRENT-ISRUNNING-120008-061 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015 15:00:09.09 - CURRENT-ISRUNNING-150008-951 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015 15:00:26.51 - CURRENT-ISRUNNING-150008-951 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015 18:00:08.10 - CURRENT-ISRUNNING-180007-967 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015 18:00:25.02 - CURRENT-ISRUNNING-180007-967 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015 21:00:08.26 - CURRENT-ISRUNNING-210008-154 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015 21:00:25.24 - CURRENT-ISRUNNING-210008-154 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015  0:00:07.95 - CURRENT-ISRUNNING-000007-873 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015  0:00:24.76 - CURRENT-ISRUNNING-000007-873 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015  3:00:07.99 - CURRENT-ISRUNNING-030007-896 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015  3:00:25.00 - CURRENT-ISRUNNING-030007-896 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015  6:00:07.80 - CURRENT-ISRUNNING-060007-723 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015  6:00:24.81 - CURRENT-ISRUNNING-060007-723 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015  9:00:07.78 - CURRENT-ISRUNNING-090007-706 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015  9:00:24.72 - CURRENT-ISRUNNING-090007-706 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015 12:00:08.53 - CURRENT-ISRUNNING-120008-346 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015 12:00:25.61 - CURRENT-ISRUNNING-120008-346 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015 15:00:07.86 - CURRENT-ISRUNNING-150007-786 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015 15:00:24.70 - CURRENT-ISRUNNING-150007-786 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015 18:00:07.97 - CURRENT-ISRUNNING-180007-879 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015 18:00:24.83 - CURRENT-ISRUNNING-180007-879 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015 21:09:37.46 - CURRENT-ISRUNNING-210937-359 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***


22/05/2015 22:40:49.17 - CURRENT-ISRUNNING-224049-078 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015 22:41:01.79 - CURRENT-ISRUNNING-224049-078 - Normal End of [HG612_current_stats.exe] - Status = 0,


23/05/2015 16:15:43.92 - CURRENT-ISRUNNING-161543-843 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
23/05/2015 16:15:57.87 - CURRENT-ISRUNNING-161543-843 - Normal End of [HG612_current_stats.exe] - Status = 0,

No the adobe process doesn't appear to run every time, just sometimes when i run it manually  It also maybe related to the snapshot data logging as i have set it to 1 time every 24hrs and it so far hasn't got stuck
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 23, 2015, 07:11:20 PM
No the adobe process doesn't appear to run every time, just sometimes when i run it manually  It also maybe related to the snapshot data logging as i have set it to 1 time every 24hrs and it so far hasn't got stuck



I'm getting a little confused now by which program 'it' relates to.

There are 3 references to 'it' in your quote, so could you please clarify which 'it' each one refers to?

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 23, 2015, 08:58:06 PM
Sorry i assumed you would know which i was talking about HG612_stats.exe was the process that i ran manually aka (it)
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 24, 2015, 01:37:30 AM
So, to summarise:-

While the snapshot logging (HG612_current_stats.exe) doesn't attempt to run at the turn of an hour, it appears that HG612_stats.exe runs without a hitch (so far)?

HG612_current_stats.exe runs O.K. when manually run?

You seem to be using a version of XP for the logging.
If so is it Pro or Home & is it Service Pack 3?

This issue only started happening after you updated to v 5.1?



Is all the above a correct summary?


I've attempted to reproduce the issue at this end to no avail (yet).

I'm still looking into it though.

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 24, 2015, 03:08:20 AM
So, to summarise:-

While the snapshot logging (HG612_current_stats.exe) doesn't attempt to run at the turn of an hour, it appears that HG612_stats.exe runs without a hitch (so far)?

HG612_current_stats.exe runs O.K. when manually run?
yes to both

You seem to be using a version of XP for the logging.
If so is it Pro or Home & is it Service Pack 3?

This issue only started happening after you updated to v 5.1?


Is all the above a correct summary?


I've attempted to reproduce the issue at this end to no avail (yet).

I'm still looking into it though.
Yes  the o/s is WIN XP SP3 pro, and the issue only started  following updating to the latest build /version 5.1





Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 24, 2015, 10:07:02 AM
O.K.

I can see from MDWS that apart from when it was down for maintenance, it appears that data was being uploaded as intended.

Now that you have set the snapshot logging schedule to just once every 24 hours, what time is it due?



I have attached a test version of HG612_current_stats.exe with a couple of very minor tweaks for you to try out.
Could you please use this version in the Scripts folder instead of the original one?


Rather than having to wait until the next scheduled snapshot time, I have also attached a test version of HG612_stats - TEST.exe.
You don't need to replace the original version of HG612_stats.exe.


Could you firstly run the new HG612_current_stats.exe MANUALLY at say 30 seconds past the minute, PC system time?
As it's an update from the original version, you may need to allow it in Windows and also your AV/Firewall.


It should produce this output in CURRENT_ERROR.LOG_file_ERROR.TXT:-

24/05/2015  9:27:32.85 - CURRENT-ISRUNNING-092732-767 - Start of [HG612_current_stats.exe] *** Version 5.1.0.1 - 24/05/2015 ***
24/05/2015  9:27:32.97 - CURRENT-ISRUNNING-092732-767 - Parameter passed to [HG612_current_stats.exe] = (null) -  i.e. ** MANUALLY ** initiated
24/05/2015  9:27:33.02 - CURRENT-ISRUNNING-092732-767 - delay from ini file is 0
24/05/2015  9:27:33.50 - CURRENT-ISRUNNING-092732-767 - Creating subfolder C:\HG612 Modem Stats with Spaces\Current Stats\Current_Stats_20150524-0927
24/05/2015  9:27:33.53 - CURRENT-ISRUNNING-092732-767 - Modem_type = HG612
24/05/2015  9:27:34.53 - CURRENT-ISRUNNING-092732-767 - Logged in to modem O.K.
24/05/2015  9:27:38.12 - CURRENT-ISRUNNING-092732-767 - Logged out of modem O.K. Status = 1,
24/05/2015  9:27:38.15 - CURRENT-ISRUNNING-092732-767 - Data has veen harvested, Status = 1
24/05/2015  9:27:38.25 - CURRENT-ISRUNNING-092732-767 - Normal End of [HG612_current_stats.exe] - Status = 0,




Secondly, at say 30 seconds past the next minute, could you MANUALLY run HG612_stats - TEST.exe?
Again, you may need to allow it in Windows and your AV/Firewall program.

It should simulate a scheduled snapshot event without locking up your main HG612_stats.exe program & produce this output in CURRENT_ERROR.LOG_file_ERROR.TXT:-

24/05/2015  9:28:48.45 - CURRENT-ISRUNNING-092848-319 - Start of [HG612_current_stats.exe] *** Version 5.1.0.1 - 24/05/2015 ***
24/05/2015  9:28:48.61 - CURRENT-ISRUNNING-092848-319 - Parameter passed to [HG612_current_stats.exe] = SCHEDULED - i.e. ** AUTOMATICALLY ** initiated
24/05/2015  9:28:48.67 - CURRENT-ISRUNNING-092848-319 - delay from ini file is 0
24/05/2015  9:28:48.14 - CURRENT-ISRUNNING-092848-319 - Creating subfolder C:\HG612 Modem Stats with Spaces\Current Stats\Current_Stats_20150524-0928-SCHEDULED
24/05/2015  9:28:48.17 - CURRENT-ISRUNNING-092848-319 - Modem_type = HG612
24/05/2015  9:28:49.19 - CURRENT-ISRUNNING-092848-319 - Logged in to modem O.K.
24/05/2015  9:28:52.88 - CURRENT-ISRUNNING-092848-319 - Logged out of modem O.K. Status = 1,
24/05/2015  9:28:52.90 - CURRENT-ISRUNNING-092848-319 - Data has veen harvested, Status = 1
24/05/2015  9:28:52.99 - CURRENT-ISRUNNING-092848-319 - Normal End of [HG612_current_stats.exe] - Status = 0,



After carrying out those tests, could you please post the output from CURRENT_ERROR.LOG_file_ERROR.TXT & confirm whether or not the test version of HG612_stats - TEST.exe ended up 'stuck' in Task Manager & needed its process to be ended?


Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 24, 2015, 12:59:23 PM
Well it was due to run at 6am,& it appears to of ran without issues this time  see 6am log output, no multiple instances , i will post back on the results from the files you have attached
_____________________________________________________

Ok i replaced the original HG612_current_stats.exe file with the one that you attached and ran it as per your instructions the attached txt file ( CURRENT_ERROR_LOG_file .txt) shows the output from running that file

The second HG612_stats - TEST.exe results are in  the error log test 2  output.txt  file

Not seeing the exe files getting stuck when i  ran them

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 24, 2015, 01:41:20 PM
It looks like you are still running the original version of HG612_current_stats.exe:-

24/05/2015 13:05:33.07 - CURRENT-ISRUNNING-130533-000 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***



The one I attached should be Version 5.0.0.1 & it should have today's date:-

24/05/2015  9:27:32.85 - CURRENT-ISRUNNING-092732-767 - Start of [HG612_current_stats.exe] *** Version 5.1.0.1 - 24/05/2015 ***


Also, enabling all the extra debugging/error logging has the effect of slowing program flow down.

I would prefer the tests to be conducted initially with the extra debugging data disabled.

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 24, 2015, 02:25:54 PM
I for some reason copied the file from the unzipped  downloaded  full  installation  folder,

re done with the extra logging turned off    tests in same order as before , no process hanging so far
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 24, 2015, 03:43:36 PM
O.K. So far, so good (apart from my typo in the log message)  :-[

The real test will be when HG612_stats.exe is very busy on the hour.

i.e. it will be gathering snapshot and ongoing data for the files that are uploaded, the actual upload itself & when scheduled snapshot and/or daily graphing is due.

06:00 is the default time that it will be at its busiest & that's the likeliest time for something to go wrong.

In the meantime, as we have missed the 15:00 opportunity, could you please reset scheduled snapshot logging to every hour?
That way, we will be able to see how it copes at 16:00 & every hour (for a while).


If you are around at 16:00, or whenever the scheduled snapshot logging is due, could you please post these logs from a few minutes before, during & a few minutes after the hourly schedule?:-

ONGOING_ERROR.LOG_file_ERROR.TXT

CURRENT_ERROR.LOG_file_ERROR.TXT



If things fail again, it would also be worth posting these logs from before, during & after the hourly schedule:-

EXIT_2_INSTANCES.LOG

Login_events.TXT


Please keep the test version (HG612_stats - TEST.exe) for now, just in case any other tests are needed.


Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 24, 2015, 04:15:04 PM
Here is the output from the ONGOING_ERROR.LOG_file_ERROR.TXT & CURRENT_ERROR.LOG_file_ERROR.TXT files  after the scheduled harvest of stats


Current error log file

Code: [Select]
24/05/2015 16:00:07.67 - CURRENT-ISRUNNING-160007-593 - Start of [HG612_current_stats.exe] *** Version 5.1.0.1 - 24/05/2015 ***
24/05/2015 16:00:07.82 - CURRENT-ISRUNNING-160007-593 - Parameter passed to [HG612_current_stats.exe] = SCHEDULED - i.e. ** AUTOMATICALLY ** initiated
24/05/2015 16:00:07.87 - CURRENT-ISRUNNING-160007-593 - delay from ini file is 6
24/05/2015 16:00:14.28 - CURRENT-ISRUNNING-160007-593 - Creating subfolder C:\HG612_Modem_Stats\Current_Stats\Current_Stats_20150524-1600-SCHEDULED
24/05/2015 16:00:14.31 - CURRENT-ISRUNNING-160007-593 - Modem_type = HG612
24/05/2015 16:00:15.25 - CURRENT-ISRUNNING-160007-593 - Logged in to modem O.K.
24/05/2015 16:00:19.17 - CURRENT-ISRUNNING-160007-593 - Logged out of modem O.K. Status = 1,
24/05/2015 16:00:19.20 - CURRENT-ISRUNNING-160007-593 - Data has veen harvested, Status = 1
24/05/2015 16:00:19.34 - CURRENT-ISRUNNING-160007-593 - Normal End of [HG612_current_sta[b][/b][b][/b][b][/b]ts.exe] - Status = 0,
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 24, 2015, 05:11:38 PM
That all looks correct now.

Let's see how it goes overnight & critically at 06:00 tomorrow morning.


Did you add all these in the middle of the word 'stats' or has my program done it?:-

Code: [Select]
[b][/b][b][/b][b][/b]
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 24, 2015, 05:28:00 PM
That all looks correct now.

Let's see how it goes overnight & critically at 06:00 tomorrow morning.


Did you add all these in the middle of the word 'stats' or has my program done it?:-

Code: [Select]
[b][/b][b][/b][b][/b]
Those [/b] where generated by this forum i think ,maybe because i used code,or has something to do with me underlining and using bold before the code? as they are not in the log.txt
file  the schedule is set to do a snapshot every hour  as you requested ,so no need to wait until 6am any-more unless you where meaning the daily graphing? in which case that is set to graph at 23.58 tonight 

Quote
24/05/2015 16:00:07.67 - CURRENT-ISRUNNING-160007-593 - Start of [HG612_current_stats.exe] *** Version 5.1.0.1 - 24/05/2015 ***
24/05/2015 16:00:07.82 - CURRENT-ISRUNNING-160007-593 - Parameter passed to [HG612_current_stats.exe] = SCHEDULED - i.e. ** AUTOMATICALLY ** initiated
24/05/2015 16:00:07.87 - CURRENT-ISRUNNING-160007-593 - delay from ini file is 6
24/05/2015 16:00:14.28 - CURRENT-ISRUNNING-160007-593 - Creating subfolder C:\HG612_Modem_Stats\Current_Stats\Current_Stats_20150524-1600-SCHEDULED
24/05/2015 16:00:14.31 - CURRENT-ISRUNNING-160007-593 - Modem_type = HG612
24/05/2015 16:00:15.25 - CURRENT-ISRUNNING-160007-593 - Logged in to modem O.K.
24/05/2015 16:00:19.17 - CURRENT-ISRUNNING-160007-593 - Logged out of modem O.K. Status = 1,
24/05/2015 16:00:19.20 - CURRENT-ISRUNNING-160007-593 - Data has veen harvested, Status = 1
24/05/2015 16:00:19.34 - CURRENT-ISRUNNING-160007-593 - Normal End of [HG612_current_stats.exe] - Status = 0,
with no added [/b] s
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 24, 2015, 05:37:30 PM
Those [/b] where generated by this forum i think ,maybe because i used code, as they are not in the log.txt
file  the schedule is set to do a snapshot every hour  as you requested ,so no need to wait until 6am any-more

Ack regarding the [/b] etc.

I mentioned 06:00 as that's when everything is done by default, including the daily graphing which can be quite intensive, PC resource-wise.

It won't do any harm to let the snapshot schedule run every hour for now though, to give it a good testing.

As I didn't really change much in HG612_current_stats.exe, I think the issue MIGHT have been program permissions all along (Windows & your AV/Firewall).

The other user (buseng12) seems to believe sorting things out properly with his McAfee AV program has now resolved the issues he was seeing.
It's rather hard to be certain though as he doesn't log stats 24/7 & it always appears (wrongly?) from his MDWS graphs that he has been experiencing some problems.


Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 24, 2015, 06:31:27 PM
Quote
It's rather hard to be certain though as he doesn't log stats 24/7 & it always appears (wrongly?) from his MDWS graphs that he has been experiencing some problems.
Very strange

Also i didn't know about the 6am harvesting regardless of how the EU sets it up
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 24, 2015, 08:14:08 PM
Also i didn't know about the 6am harvesting regardless of how the EU sets it up



6am is the default setting.
This can be changed by users via the GUI or by manually editing the ini file though:-

Code: [Select]
[Graphing]

Pause_after_obtaining_snapshot_data=     NO
Auto_graph_Snapshot_data=                YES
Pause_after_snapshot_graphs_plotted=     NO
Pause_after_ongoing_graphs_plotted=      NO
Plot_area_background_colour=             31
Daily_Graphing=                          NO
Daily_Graphing_Time=                     06:00

[Logging]

Ongoing_Logging=                         YES
Current_Stats=                           NO
Current_Stats_Interval=                  8
Current_Stats_Datum=                     06



Looking back at one of your ONGOING_ERROR.LOG_file_ERROR.TXT files, it appears you haven't actually set Daily graphing of ongoing stats to run:-

23/05/2015  2:16:24.43 - ONGOING-ISRUNNING-021605-343.TXT - *** Scheduled Daily graphing is NOT switched on.


Have you been creating the ongoing graphs manually then or just relying on MDWS?

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on May 25, 2015, 12:58:53 AM
In the folder where the graphs are stored i have this as my latest  in the current stats folder  Current_Stats_20150525-0000-SCHEDULED ,and this is the latest  in the ongoing stats folder Ongoing_Stats_20150524-2358-1Day before that same time the day before  So other than these i don't know how or what else there is to set up graphing
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 25, 2015, 08:36:08 AM
It seems like you now have daily graphing set to run at 23:58 each day.

Having it run 2 minutes before the hour is probably not a bad thing as it will reduce PC resource demand when other things are done on the hour, especially if your XP machine isn't a particularly high spec.

23/05/2015  2:24:01.39 - ONGOING-ISRUNNING-022400-125.TXT - ****** PC_Speed is set as "FAST" in the ini file, times in loop = 01 *** numbytes = 0
23/05/2015  2:24:01.40 - ONGOING-ISRUNNING-022400-125.TXT - At start of expect("gin:"), sleeping for 0.500 seconds *** numbytes = 0 

:
:
:
23/05/2015  2:24:06.70 - ONGOING-ISRUNNING-022400-125.TXT - total_sleep_time = 2.600 seconds




One last thing you may wish to try now that everything seems O.K. is to change the PC's Speed settings via the GUI.

The FAST setting is for high spec PCs that try to process the raw stats quicker than the modem can actually provide them.
This setting actually adds a few 0.5 second pauses in my programs when needed, to avoid them getting ahead of the modem.

The MEDIUM setting adds 0.25 second program pauses when needed.

My Windows 7 PC isn't particularly high spec, so I use the SLOW setting, which doesn't introduce any program pauses.


From memory, I think Ronski added the 23:58 timing for using the programs on his server which was sometimes very busy at midnight, slowing everything down etc. & it was occasionally missing the daily graphing when the timing was set for midnight.




Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: GigabitEthernet on May 31, 2015, 08:59:01 PM
Hi all,

I've this afternoon downloaded these fantastic utilities.

I've set everything up as the instructions say and everything seems to be working but the only thing that isn't is that the GUI is supposed to show the current stats, right? This is not the case on my system (see attachment).

It's been running for two hours now and the UI doesn't show anything. What am I doing wrong?

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on May 31, 2015, 09:24:09 PM
Is the modem_stats.log file in the Ongoing_Stats folder being updated every minute?

It's possible that you need to 'allow' the programs that are stored in the Scripts folder in your AV program/firewall.
One or more of them may be 'stuck' in Task Manager if something is blocking them.

It may help to temporarily disable the logging, end any remaining instances of the programs in Task Manager & try to manually run each program to see if Windows asks if you wish to always allow them.


The programs that mainly seem to be affected by permissions are HG612_Run.exe and HG612_stats.exe.


Check the Event & Error Logs folder for the logs that might indicate what is/isn't happening.

Don't leave any of the logs open in Windows Notepad though as that can effectively cause the programs to wait until you close them in Notepad again.


I have read that some AV programs simply quarantine some programs without even asking if they are safe to run or not.

Are the Directory paths as shown in the Settings tab in the GUI correct?
They will be highlighted in yellow if any of them are incorrect.

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: GigabitEthernet on May 31, 2015, 09:34:44 PM
Ahh that's working now, thank you :) Windows 10 wasn't letting all of the processes run.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on May 31, 2015, 10:55:14 PM
By the way I looked into the avast issues.

Avast has a hardened mode.  If hardened mode is enabled and set to agressive it requires the exe to be whitelisted on their servers.

This type of malware protection is the future as whitelisting is vastly superior to blacklisting but obviously if its a program with hardly any users like our's it will not be whitelisted.

If hardened mode is turned off then there should be no issue with avast, I am not sure if moderate hardened mode is enabled, that doesnt use the whitelist system but will block things it cannot clearly determine as safe.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: npr on July 16, 2015, 06:19:39 PM
Just a heads up, the file has disappeared from the link.
http://www.freewarefiles.com/HG612-Modem-Stats_program_84567.html
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on July 16, 2015, 08:23:36 PM
Thanks npr, I've tried contacting Freeware Files and also resubmitting it but I've heard nothing.

Here's a direct link (http://www.ronski.me.uk/downloads/HG612_Modem_Stats_Programs-r5.1.zip) if you need it.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on July 16, 2015, 09:07:46 PM
can I share the direct link on other forums, or do I tell people to wait?
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on July 17, 2015, 06:45:44 AM
I'm quite happy for you to host the file on your server and then share that link.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: GigabitEthernet on July 29, 2015, 09:49:47 PM
I've got my TalkTalk-supplied Huawei HG635 telnet enabled and I wish to use your scripts with it.

How would I edit the password as the Billion 8800NL uses a different syntax - the Huawei uses xdslcmd.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on July 29, 2015, 10:01:17 PM
How do you get into a telnet session to obtain the stats?

Does it require you to type "sh" or "shell" as per the HG612?

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: GigabitEthernet on July 29, 2015, 10:04:22 PM
Yes it does, it requires sh:

Code: [Select]
Login: !!Huawei
Password:
ATP>sh


BusyBox vv1.9.1 () built-in shell (ash)
Enter 'help' for a list of built-in commands.

$ xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 8817 Kbps, Downstream rate = 41667 Kbps
Path: 0, Upstream rate = 8599 Kbps, Downstream rate = 41053 Kbps
Path: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on July 29, 2015, 10:22:06 PM
You could try manually editing the HG612_stats.ini file for now:-

[Login]
IP_address=                              192.168.1.1
Username=                                admin - change this to !!Huawei if admin isn't the name you need to use
Password=                                admin - change this to whatever password is needed
Shell=                                   sh

[Locations]
Main_folder=                             C:\HG612 Modem Stats with Spaces
Scripts_and_Programs=                    C:\HG612 Modem Stats with Spaces\Scripts
Apps_folder=                             C:\HG612 Modem Stats with Spaces\Apps
Current_Stats_folder=                    C:\HG612 Modem Stats with Spaces\Current Stats
Ongoing_Stats_folder=                    C:\HG612 Modem Stats with Spaces\Ongoing Stats
Modem_Log=                               C:\HG612 Modem Stats with Spaces\Ongoing Stats

[Mode]
Mode=                                    extensive

[Graphing]
Pause_after_obtaining_snapshot_data=     NO
Auto_graph_Snapshot_data=                NO
Pause_after_snapshot_graphs_plotted=     NO
Pause_after_ongoing_graphs_plotted=      NO
Plot_area_background_colour=             31
Daily_Graphing=                          YES
Daily_Graphing_Time=                     06:01

[Delays]
Delay_snapshot_data_harvest_seconds=     0
Delay_ongoing_data_harvest_seconds=      0

[Logging]
Ongoing_Logging=                         YES
Current_Stats=                           YES
Current_Stats_Interval=                  4       
Current_Stats_Datum=                     02

[Event/Error_logging]
Extensive_event_logging=                 YES
Extra_debugging_info=                    YES

[Modem]
Modem_type=                              HG612 - change this to HG622 if HG612 doesn't work


I have not tested the programs with a HG635, so please let me know how you get on in case I need to amend the program code at all.

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: GigabitEthernet on July 29, 2015, 10:28:58 PM
It's not working with either modem selected :(

I think it is perhaps because:
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on July 29, 2015, 10:46:35 PM
Is the "$" the prompt? It is "#" for the HG612/HG622.


With Extra debugging info logging enabled, could you post the latest instance entry from the ONGOING_ERROR.LOG_file_ERROR.TXT file?


This is mine:-

29/07/2015 22:40:46.54 - ONGOING-ISRUNNING-224046-479.TXT - Start of [HG612_stats.exe] - **** Version 5.1.0.2 28/05/2015 ****
29/07/2015 22:40:46.74 - ONGOING-ISRUNNING-224046-479.TXT - Immediately after ini_parse() - About to determine the OS version. ERROR.LOG status = 0,
29/07/2015 22:40:46.75 - ONGOING-ISRUNNING-224046-479.TXT - *** Windows version = [6.1.7601] ***
29/07/2015 22:40:46.79 - ONGOING-ISRUNNING-224046-479.TXT - In [HG612_stats.exe] - After obtaining the OS version. ERROR.LOG status = 0,
29/07/2015 22:40:46.83 - ONGOING-ISRUNNING-224046-479.TXT - From ini file, Modem_type = HG612. Status = 0,
29/07/2015 22:40:46.90 - ONGOING-ISRUNNING-224046-479.TXT - ERROR.LOG successfully opened. Status = 1,
29/07/2015 22:40:47.04 - ONGOING-ISRUNNING-224046-479.TXT - **** From IsRunningVB.exe, dslstatssampling.exe is *NOT* running
29/07/2015 22:40:47.16 - ONGOING-ISRUNNING-224046-479.TXT - ONGOING-ISRUNNING-224046-479.TXT created. Status = 1,
29/07/2015 22:40:47.46 - ONGOING-ISRUNNING-224046-479.TXT - There are 1 instances of HG612_stats.exe running. Status = 1,
29/07/2015 22:40:47.50 - ONGOING-ISRUNNING-224046-479.TXT - Continuing as there are only 1 instances of HG612_stats.exe running **. Status = 1,
29/07/2015 22:40:47.57 - ONGOING-ISRUNNING-224046-479.TXT - WSAStartup() SUCCESSFUL!!! Status = 1,
29/07/2015 22:40:47.60 - ONGOING-ISRUNNING-224046-479.TXT - hg612ip = 192.168.1.1, HG612PORT = 23. Status = 1,
29/07/2015 22:40:47.64 - ONGOING-ISRUNNING-224046-479.TXT - getaddrinfo() O.K. Status = 1,
29/07/2015 22:40:47.68 - ONGOING-ISRUNNING-224046-479.TXT - socket() O.K. Status = 1,
29/07/2015 22:40:47.72 - ONGOING-ISRUNNING-224046-479.TXT - sockfd = 152, "res->ai_addrlen" = 16 connect() ERROR CODE = 0. Status = 1,
29/07/2015 22:40:47.75 - ONGOING-ISRUNNING-224046-479.TXT - connect() O.K. Status = 1,
29/07/2015 22:40:47.78 - ONGOING-ISRUNNING-224046-479.TXT - *************************************************************************
29/07/2015 22:40:47.80 - ONGOING-ISRUNNING-224046-479.TXT - At start of expect("gin:"), times in loop = 01 *** numbytes = 0
29/07/2015 22:40:47.82 - ONGOING-ISRUNNING-224046-479.TXT - ****** PC_Speed is set as "SLOW" in the ini file, times in loop = 01 *** numbytes = 0
29/07/2015 22:40:47.85 - ONGOING-ISRUNNING-224046-479.TXT - At start of expect("gin:"), sleeping for 0.000 seconds *** numbytes = 0
29/07/2015 22:40:47.86 - ONGOING-ISRUNNING-224046-479.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 9
29/07/2015 22:40:47.89 - ONGOING-ISRUNNING-224046-479.TXT - Still in expect("gin:") loop, times in loop = 02
29/07/2015 22:40:47.92 - ONGOING-ISRUNNING-224046-479.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 91
29/07/2015 22:40:47.94 - ONGOING-ISRUNNING-224046-479.TXT - End of expect("gin:")
29/07/2015 22:40:47.97 - ONGOING-ISRUNNING-224046-479.TXT - *************************************************************************
29/07/2015 22:40:47.99 - ONGOING-ISRUNNING-224046-479.TXT - expect("gin:") O.K. Status = 1.
29/07/2015 22:40:48.02 - ONGOING-ISRUNNING-224046-479.TXT - reply(config.Username) O.K. Status = 1.
29/07/2015 22:40:48.05 - ONGOING-ISRUNNING-224046-479.TXT - Username from HG612_stats.ini = "admin". Status = 1.
29/07/2015 22:40:48.08 - ONGOING-ISRUNNING-224046-479.TXT - *************************************************************************
29/07/2015 22:40:48.10 - ONGOING-ISRUNNING-224046-479.TXT - At start of expect("ssword:"), times in loop = 01 *** numbytes = 0
29/07/2015 22:40:48.13 - ONGOING-ISRUNNING-224046-479.TXT - ****** PC_Speed is set as "SLOW" in the ini file, times in loop = 01 *** numbytes = 0
29/07/2015 22:40:48.16 - ONGOING-ISRUNNING-224046-479.TXT - At start of expect("ssword:"), sleeping for 0.000 seconds *** numbytes = 0
29/07/2015 22:40:48.17 - ONGOING-ISRUNNING-224046-479.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 1
29/07/2015 22:40:48.21 - ONGOING-ISRUNNING-224046-479.TXT - Still in expect("ssword:") loop, times in loop = 02
29/07/2015 22:40:48.25 - ONGOING-ISRUNNING-224046-479.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 15
29/07/2015 22:40:48.28 - ONGOING-ISRUNNING-224046-479.TXT - End of expect("ssword:")
29/07/2015 22:40:48.30 - ONGOING-ISRUNNING-224046-479.TXT - *************************************************************************
29/07/2015 22:40:48.33 - ONGOING-ISRUNNING-224046-479.TXT - expect("ssword:") O.K. Status = 1.
29/07/2015 22:40:48.36 - ONGOING-ISRUNNING-224046-479.TXT - reply(config.Password) O.K. Status = 1.
29/07/2015 22:40:48.38 - ONGOING-ISRUNNING-224046-479.TXT - Password from HG612_stats.ini = "admin". Status = 1.
29/07/2015 22:40:48.41 - ONGOING-ISRUNNING-224046-479.TXT - *************************************************************************
29/07/2015 22:40:48.44 - ONGOING-ISRUNNING-224046-479.TXT - At start of expect("ATP>"), times in loop = 01 *** numbytes = 0
29/07/2015 22:40:48.46 - ONGOING-ISRUNNING-224046-479.TXT - ****** PC_Speed is set as "SLOW" in the ini file, times in loop = 01 *** numbytes = 0
29/07/2015 22:40:48.49 - ONGOING-ISRUNNING-224046-479.TXT - At start of expect("ATP>"), sleeping for 0.000 seconds *** numbytes = 0
29/07/2015 22:40:48.50 - ONGOING-ISRUNNING-224046-479.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 1
29/07/2015 22:40:48.53 - ONGOING-ISRUNNING-224046-479.TXT - Still in expect("ATP>") loop, times in loop = 02
29/07/2015 22:40:48.58 - ONGOING-ISRUNNING-224046-479.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 6
29/07/2015 22:40:48.61 - ONGOING-ISRUNNING-224046-479.TXT - End of expect("ATP>")
29/07/2015 22:40:48.64 - ONGOING-ISRUNNING-224046-479.TXT - *************************************************************************
29/07/2015 22:40:48.66 - ONGOING-ISRUNNING-224046-479.TXT - expect("ATP>") O.K. Status = 1.
29/07/2015 22:40:48.94 - ONGOING-ISRUNNING-224046-479.TXT - **** reply(config.Shell) O.K. Status = 1.
29/07/2015 22:40:48.95 - ONGOING-ISRUNNING-224046-479.TXT - *************************************************************************
29/07/2015 22:40:48.99 - ONGOING-ISRUNNING-224046-479.TXT - At start of expect("# "), times in loop = 01 *** numbytes = 0
29/07/2015 22:40:49.00 - ONGOING-ISRUNNING-224046-479.TXT - ****** PC_Speed is set as "SLOW" in the ini file, times in loop = 01 *** numbytes = 0
29/07/2015 22:40:49.03 - ONGOING-ISRUNNING-224046-479.TXT - At start of expect("# "), sleeping for 0.000 seconds *** numbytes = 0
29/07/2015 22:40:49.05 - ONGOING-ISRUNNING-224046-479.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 1
29/07/2015 22:40:49.08 - ONGOING-ISRUNNING-224046-479.TXT - Still in expect("# ") loop, times in loop = 02
29/07/2015 22:40:49.14 - ONGOING-ISRUNNING-224046-479.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 121
29/07/2015 22:40:49.16 - ONGOING-ISRUNNING-224046-479.TXT - End of expect("# ")
29/07/2015 22:40:49.19 - ONGOING-ISRUNNING-224046-479.TXT - *************************************************************************
29/07/2015 22:40:49.24 - ONGOING-ISRUNNING-224046-479.TXT - The prompt "# " *WAS* received. Sleeping for 0.100 seconds. Status = 1,
29/07/2015 22:40:49.38 - ONGOING-ISRUNNING-224046-479.TXT - Reaching this point means logging in to the modem was successful. Status = 1,
29/07/2015 22:40:49.39 - ONGOING-ISRUNNING-224046-479.TXT - reply(xdslcmd info --stats) O.K. Status = 1, return value = 0
29/07/2015 22:40:49.42 - ONGOING-ISRUNNING-224046-479.TXT - **** At start of get_data("xdslcmd info --stats")
29/07/2015 22:40:49.47 - ONGOING-ISRUNNING-224046-479.TXT - In get_data(#01). *** This was included in data received:- xdslcmd info --stats - (numbyes = 1516, index = 1516)
29/07/2015 22:40:49.66 - ONGOING-ISRUNNING-224046-479.TXT - In get_data(#02). *** This was included in data received:- xdslcmd info --stats - (numbyes = 1436, index = 2952)
29/07/2015 22:40:49.69 - ONGOING-ISRUNNING-224046-479.TXT - In get_data(#02). *** This was included in data received:-  # - (numbytes = 1436, index = 2952)
29/07/2015 22:40:49.72 - ONGOING-ISRUNNING-224046-479.TXT - get_data() for xdslcmd info --stats O.K. Status = 1, times in get_data() loop was 02
29/07/2015 22:40:49.80 - ONGOING-ISRUNNING-224046-479.TXT - After xdslcmd info --stats, ERROR.LOG status = 1
29/07/2015 22:40:49.83 - ONGOING-ISRUNNING-224046-479.TXT - **** At start of get_data("xdslcmd info --pbParams")
29/07/2015 22:40:49.84 - ONGOING-ISRUNNING-224046-479.TXT - In get_data(#01). *** This was included in data received:- xdslcmd info --pbParams - (numbyes = 25, index = 25)
29/07/2015 22:40:50.08 - ONGOING-ISRUNNING-224046-479.TXT - In get_data(#02). *** This was included in data received:- xdslcmd info --pbParams - (numbyes = 1080, index = 1105)
29/07/2015 22:40:50.11 - ONGOING-ISRUNNING-224046-479.TXT - In get_data(#02). *** This was included in data received:-  # - (numbytes = 1080, index = 1105)
29/07/2015 22:40:50.14 - ONGOING-ISRUNNING-224046-479.TXT - get_data() for xdslcmd info --pbParams O.K. Status = 1, times in get_data() loop was 02
29/07/2015 22:40:50.19 - ONGOING-ISRUNNING-224046-479.TXT - After xdslcmd info --pbParams, ERROR.LOG status = 1
29/07/2015 22:40:50.20 - ONGOING-ISRUNNING-224046-479.TXT - *************************************************************************
29/07/2015 22:40:50.23 - ONGOING-ISRUNNING-224046-479.TXT - **** At start of get_data("xdslcmd --version")
29/07/2015 22:40:50.26 - ONGOING-ISRUNNING-224046-479.TXT - In get_data(#01). *** This was included in data received:- xdslcmd --version - (numbyes = 109, index = 109)
29/07/2015 22:40:50.30 - ONGOING-ISRUNNING-224046-479.TXT - In get_data(#01). *** This was included in data received:-  # - (numbytes = 109, index = 109)
29/07/2015 22:40:50.31 - ONGOING-ISRUNNING-224046-479.TXT - reply(xdslcmd --version) O.K. Status = 1, times in get_data() loop was 01
29/07/2015 22:40:50.34 - ONGOING-ISRUNNING-224046-479.TXT - get_data() for xdslcmd --version O.K..Status = 1, times in get_data() loop was 01
29/07/2015 22:40:50.37 - ONGOING-ISRUNNING-224046-479.TXT - After xdslcmd --version, ERROR.LOG status = 1
29/07/2015 22:40:50.39 - ONGOING-ISRUNNING-224046-479.TXT - *************************************************************************
29/07/2015 22:40:50.42 - ONGOING-ISRUNNING-224046-479.TXT - **** At start of get_data("equipcmd swversion display")
29/07/2015 22:40:50.45 - ONGOING-ISRUNNING-224046-479.TXT - In get_data(#01). *** This was included in data received:- equipcmd swversion display - (numbyes = 28, index = 28)
29/07/2015 22:40:50.67 - ONGOING-ISRUNNING-224046-479.TXT - In get_data(#02). *** This was included in data received:- equipcmd swversion display - (numbyes = 157, index = 185)
29/07/2015 22:40:50.69 - ONGOING-ISRUNNING-224046-479.TXT - In get_data(#02). *** This was included in data received:-  # - (numbytes = 157, index = 185)
29/07/2015 22:40:50.72 - ONGOING-ISRUNNING-224046-479.TXT - get_data() for (equipcmd swversion display)       O.K. Status = 1, times in get_data() loop was 002
29/07/2015 22:40:50.73 - ONGOING-ISRUNNING-224046-479.TXT - *************************************************************************
29/07/2015 22:40:50.76 - ONGOING-ISRUNNING-224046-479.TXT - After xdslcmd --swversion(), ERROR.LOG status = 1
29/07/2015 22:40:50.78 - ONGOING-ISRUNNING-224046-479.TXT - Minutes past the hour = 40
29/07/2015 22:40:50.81 - ONGOING-ISRUNNING-224046-479.TXT - 40 Mod 60 = 40. Therefore Snapshot uploading *IS NOT* due yet.
29/07/2015 22:40:50.83 - ONGOING-ISRUNNING-224046-479.TXT - *** reply("exit") after "equipcmd swversion display" O.K. Status = 1,
29/07/2015 22:40:50.86 - ONGOING-ISRUNNING-224046-479.TXT - *************************************************************************
29/07/2015 22:40:50.87 - ONGOING-ISRUNNING-224046-479.TXT - At start of expect("ATP>"), times in loop = 01 *** numbytes = 0
29/07/2015 22:40:50.89 - ONGOING-ISRUNNING-224046-479.TXT - ****** PC_Speed is set as "SLOW" in the ini file, times in loop = 01 *** numbytes = 0
29/07/2015 22:40:50.92 - ONGOING-ISRUNNING-224046-479.TXT - At start of expect("ATP>"), sleeping for 0.000 seconds *** numbytes = 0
29/07/2015 22:40:50.94 - ONGOING-ISRUNNING-224046-479.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 6
29/07/2015 22:40:50.95 - ONGOING-ISRUNNING-224046-479.TXT - Still in expect("ATP>") loop, times in loop = 02
29/07/2015 22:40:51.08 - ONGOING-ISRUNNING-224046-479.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 6
29/07/2015 22:40:51.09 - ONGOING-ISRUNNING-224046-479.TXT - End of expect("ATP>")
29/07/2015 22:40:51.12 - ONGOING-ISRUNNING-224046-479.TXT - *************************************************************************
29/07/2015 22:40:51.15 - ONGOING-ISRUNNING-224046-479.TXT - *** reply("exit") from "ATP>" O.K. Status = 1,
29/07/2015 22:40:51.17 - ONGOING-ISRUNNING-224046-479.TXT - Logged out of modem O.K. Status = 1,
29/07/2015 22:40:51.20 - ONGOING-ISRUNNING-224046-479.TXT - The next bit is the dtp- stuff. Status = 1,
29/07/2015 22:40:51.22 - ONGOING-ISRUNNING-224046-479.TXT - The next bit is 'displaying' the stats. Status = 1,
29/07/2015 22:40:51.25 - ONGOING-ISRUNNING-224046-479.TXT - The next bit gets the local time and calculates seconds past the epoch. Status = 1,
29/07/2015 22:40:51.28 - ONGOING-ISRUNNING-224046-479.TXT - AFTER  calculating seconds past the epoch. Status = 1,
29/07/2015 22:40:51.29 - ONGOING-ISRUNNING-224046-479.TXT - The next bit gets the data from the previous row of data from modem_stats.log. Status = 1,
29/07/2015 22:40:51.47 - ONGOING-ISRUNNING-224046-479.TXT - Now in exit. Status = 1,
29/07/2015 22:40:51.48 - ONGOING-ISRUNNING-224046-479.TXT - *** WSACleanup has completed.
29/07/2015 22:40:51.51 - ONGOING-ISRUNNING-224046-479.TXT - *** About to free(txbuf).
29/07/2015 22:40:51.53 - ONGOING-ISRUNNING-224046-479.TXT - *** txbuf has been freed.
29/07/2015 22:40:51.56 - ONGOING-ISRUNNING-224046-479.TXT - *** About to free(rxbuf).
29/07/2015 22:40:51.58 - ONGOING-ISRUNNING-224046-479.TXT - *** rxbuf has been freed.
29/07/2015 22:40:51.59 - ONGOING-ISRUNNING-224046-479.TXT - *** Now checking for resyncs - There are 1 instances of HG612_stats.exe running.
29/07/2015 22:40:51.62 - ONGOING-ISRUNNING-224046-479.TXT - *** Resync *NOT* detected.
29/07/2015 22:40:51.67 - ONGOING-ISRUNNING-224046-479.TXT - ONGOING-ISRUNNING-224046-479.TXT DELETED - Status = 1,
29/07/2015 22:40:51.68 - ONGOING-ISRUNNING-224046-479.TXT - *** Scheduled snapshot logging is *NOT* switched ON.
29/07/2015 22:40:51.72 - ONGOING-ISRUNNING-224046-479.TXT - *** Scheduled Daily graphing is switched ON.
29/07/2015 22:40:51.73 - ONGOING-ISRUNNING-224046-479.TXT - *** Scheduled Daily graphing is NOT due.
29/07/2015 22:40:51.75 - ONGOING-ISRUNNING-224046-479.TXT - End of [HG612_stats.exe], Closing ERROR.LOG. Status = 1,
29/07/2015 22:40:51.78 - ONGOING-ISRUNNING-224046-479.TXT - ERROR.LOG successfully closed. Status = 0,
29/07/2015 22:40:51.79 - ONGOING-ISRUNNING-224046-479.TXT - total_sleep_time = 0.100 seconds
29/07/2015 22:40:51.81 - ONGOING-ISRUNNING-224046-479.TXT - Normal End of [HG612_stats.exe]
29/07/2015 22:40:51.89 - ONGOING-ISRUNNING-224046-479.TXT - Web_stats are enabled, Username = BaldEagle1
29/07/2015 22:40:51.90 - ONGOING-ISRUNNING-224046-479.TXT - ************** Collating ongoing data for MDWS **************
29/07/2015 22:40:51.93 - ONGOING-ISRUNNING-224046-479.TXT - temp log "C:\HG612 Modem Stats with Spaces\Ongoing Stats\temp_BaldEagle1_live_modem_stats.log" opened O.K.
29/07/2015 22:40:51.95 - ONGOING-ISRUNNING-224046-479.TXT - ************** G.INP is active **************
29/07/2015 22:40:51.97 - ONGOING-ISRUNNING-224046-479.TXT - ************** Collating ongoing data for MDWS completed **************
29/07/2015 22:40:52.00 - ONGOING-ISRUNNING-224046-479.TXT -  Closing "C:\HG612 Modem Stats with Spaces\Ongoing Stats\temp_BaldEagle1_live_modem_stats.log"
29/07/2015 22:40:52.01 - ONGOING-ISRUNNING-224046-479.TXT -          "C:\HG612 Modem Stats with Spaces\Ongoing Stats\temp_BaldEagle1_live_modem_stats.log" closed O.K.
29/07/2015 22:40:52.07 - ONGOING-ISRUNNING-224046-479.TXT - Ongoing log looks VALID, so it CAN be uploaded.
29/07/2015 22:40:52.25 - ONGOING-ISRUNNING-224046-479.TXT - Start of [Upload.exe] - **** Version 5.1.0.1 02/06/2015 ****
29/07/2015 22:40:52.31 - ONGOING-ISRUNNING-224046-479.TXT - Now exiting [Upload.exe]. Status = 1,
29/07/2015 22:40:52.34 - ONGOING-ISRUNNING-224046-479.TXT - Closing [Upload.exe's] access to ONGOING_ERROR.LOG
 
29/07/2015 22:40:52.40 - ONGOING-ISRUNNING-224046-479.TXT - End of [HG612_stats.exe] AFTER WebStats stuff

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: GigabitEthernet on July 29, 2015, 10:56:27 PM
Here you are :)

Code: [Select]
29/07/2015 22:54:00.79 - ONGOING-ISRUNNING-225400-052.TXT - WSAStartup() SUCCESSFUL!!! Status = 1,
29/07/2015 22:54:00.81 - ONGOING-ISRUNNING-225400-052.TXT - hg612ip = 192.168.3.254, HG612PORT = 23. Status = 1,
29/07/2015 22:54:00.84 - ONGOING-ISRUNNING-225400-052.TXT - getaddrinfo() O.K. Status = 1,
29/07/2015 22:54:00.87 - ONGOING-ISRUNNING-225400-052.TXT - socket() O.K. Status = 1,
29/07/2015 22:54:00.90 - ONGOING-ISRUNNING-225400-052.TXT - sockfd = 120, "res->ai_addrlen" = 16 connect() ERROR CODE = 0. Status = 1,
29/07/2015 22:54:00.92 - ONGOING-ISRUNNING-225400-052.TXT - connect() O.K. Status = 1,
29/07/2015 22:54:00.95 - ONGOING-ISRUNNING-225400-052.TXT - *************************************************************************
29/07/2015 22:54:00.97 - ONGOING-ISRUNNING-225400-052.TXT - At start of expect("gin:"), times in loop = 01 *** numbytes = 0
29/07/2015 22:54:00.99 - ONGOING-ISRUNNING-225400-052.TXT - ****** PC_Speed is set as "FAST" in the ini file, times in loop = 01 *** numbytes = 0
29/07/2015 22:54:01.01 - ONGOING-ISRUNNING-225400-052.TXT - At start of expect("gin:"), sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 22:54:01.53 - ONGOING-ISRUNNING-225400-052.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 9
29/07/2015 22:54:01.55 - ONGOING-ISRUNNING-225400-052.TXT - Still in expect("gin:") loop, times in loop = 02
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on July 29, 2015, 10:58:37 PM
I'd need to see everything that is shown in my example (or a copy of the file itself).

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: GigabitEthernet on July 29, 2015, 11:02:12 PM
This is everything I have stored for that minute:

Code: [Select]
29/07/2015 22:54:00.09 - ONGOING-ISRUNNING-225400-052.TXT - Start of [HG612_stats.exe] - **** Version 5.1.0.0 16/05/2015 ****
29/07/2015 22:54:00.32 - ONGOING-ISRUNNING-225400-052.TXT - Immediately after ini_parse() - About to determine the OS version. ERROR.LOG status = 0,
29/07/2015 22:54:00.34 - ONGOING-ISRUNNING-225400-052.TXT - *** Windows version = [5.1.2600] ***
29/07/2015 22:54:00.37 - ONGOING-ISRUNNING-225400-052.TXT - In [HG612_stats.exe] - After obtaining the OS version. ERROR.LOG status = 0,
29/07/2015 22:54:00.39 - ONGOING-ISRUNNING-225400-052.TXT - From ini file, Modem_type = HG622. Status = 0,
29/07/2015 22:54:00.44 - ONGOING-ISRUNNING-225400-052.TXT - ERROR.LOG successfully opened. Status = 1,
29/07/2015 22:54:00.52 - ONGOING-ISRUNNING-225400-052.TXT - **** From IsRunningVB.exe, dslstatssampling.exe is *NOT* running
29/07/2015 22:54:00.58 - ONGOING-ISRUNNING-225400-052.TXT - ONGOING-ISRUNNING-225400-052.TXT created. Status = 1,
29/07/2015 22:54:00.72 - ONGOING-ISRUNNING-225400-052.TXT - There are 1 instances of HG612_stats.exe running. Status = 1,
29/07/2015 22:54:00.76 - ONGOING-ISRUNNING-225400-052.TXT - Continuing as there are only 1 instances of HG612_stats.exe running **. Status = 1,
29/07/2015 22:54:00.79 - ONGOING-ISRUNNING-225400-052.TXT - WSAStartup() SUCCESSFUL!!! Status = 1,
29/07/2015 22:54:00.81 - ONGOING-ISRUNNING-225400-052.TXT - hg612ip = 192.168.3.254, HG612PORT = 23. Status = 1,
29/07/2015 22:54:00.84 - ONGOING-ISRUNNING-225400-052.TXT - getaddrinfo() O.K. Status = 1,
29/07/2015 22:54:00.87 - ONGOING-ISRUNNING-225400-052.TXT - socket() O.K. Status = 1,
29/07/2015 22:54:00.90 - ONGOING-ISRUNNING-225400-052.TXT - sockfd = 120, "res->ai_addrlen" = 16 connect() ERROR CODE = 0. Status = 1,
29/07/2015 22:54:00.92 - ONGOING-ISRUNNING-225400-052.TXT - connect() O.K. Status = 1,
29/07/2015 22:54:00.95 - ONGOING-ISRUNNING-225400-052.TXT - *************************************************************************
29/07/2015 22:54:00.97 - ONGOING-ISRUNNING-225400-052.TXT - At start of expect("gin:"), times in loop = 01 *** numbytes = 0
29/07/2015 22:54:00.99 - ONGOING-ISRUNNING-225400-052.TXT - ****** PC_Speed is set as "FAST" in the ini file, times in loop = 01 *** numbytes = 0
29/07/2015 22:54:01.01 - ONGOING-ISRUNNING-225400-052.TXT - At start of expect("gin:"), sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 22:54:01.53 - ONGOING-ISRUNNING-225400-052.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 9
29/07/2015 22:54:01.55 - ONGOING-ISRUNNING-225400-052.TXT - Still in expect("gin:") loop, times in loop = 02
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: GigabitEthernet on July 29, 2015, 11:09:38 PM
Nevermind, try this:

Code: [Select]
29/07/2015 23:08:06.49 - ONGOING-ISRUNNING-230806-459.TXT - Start of [HG612_stats.exe] - **** Version 5.1.0.0 16/05/2015 ****
29/07/2015 23:08:06.68 - ONGOING-ISRUNNING-230806-459.TXT - Immediately after ini_parse() - About to determine the OS version. ERROR.LOG status = 0,
29/07/2015 23:08:06.70 - ONGOING-ISRUNNING-230806-459.TXT - *** Windows version = [5.1.2600] ***
29/07/2015 23:08:06.72 - ONGOING-ISRUNNING-230806-459.TXT - In [HG612_stats.exe] - After obtaining the OS version. ERROR.LOG status = 0,
29/07/2015 23:08:06.73 - ONGOING-ISRUNNING-230806-459.TXT - From ini file, Modem_type = HG622. Status = 0,
29/07/2015 23:08:06.77 - ONGOING-ISRUNNING-230806-459.TXT - ERROR.LOG successfully opened. Status = 1,
29/07/2015 23:08:06.84 - ONGOING-ISRUNNING-230806-459.TXT - **** From IsRunningVB.exe, dslstatssampling.exe is *NOT* running
29/07/2015 23:08:06.92 - ONGOING-ISRUNNING-230806-459.TXT - ONGOING-ISRUNNING-230806-459.TXT created. Status = 1,
29/07/2015 23:08:07.05 - ONGOING-ISRUNNING-230806-459.TXT - There are 1 instances of HG612_stats.exe running. Status = 1,
29/07/2015 23:08:07.07 - ONGOING-ISRUNNING-230806-459.TXT - Continuing as there are only 1 instances of HG612_stats.exe running **. Status = 1,
29/07/2015 23:08:07.09 - ONGOING-ISRUNNING-230806-459.TXT - WSAStartup() SUCCESSFUL!!! Status = 1,
29/07/2015 23:08:07.12 - ONGOING-ISRUNNING-230806-459.TXT - hg612ip = 192.168.3.254, HG612PORT = 23. Status = 1,
29/07/2015 23:08:07.14 - ONGOING-ISRUNNING-230806-459.TXT - getaddrinfo() O.K. Status = 1,
29/07/2015 23:08:07.17 - ONGOING-ISRUNNING-230806-459.TXT - socket() O.K. Status = 1,
29/07/2015 23:08:07.20 - ONGOING-ISRUNNING-230806-459.TXT - sockfd = 120, "res->ai_addrlen" = 16 connect() ERROR CODE = 0. Status = 1,
29/07/2015 23:08:07.22 - ONGOING-ISRUNNING-230806-459.TXT - connect() O.K. Status = 1,
29/07/2015 23:08:07.24 - ONGOING-ISRUNNING-230806-459.TXT - *************************************************************************
29/07/2015 23:08:07.26 - ONGOING-ISRUNNING-230806-459.TXT - At start of expect("gin:"), times in loop = 01 *** numbytes = 0
29/07/2015 23:08:07.28 - ONGOING-ISRUNNING-230806-459.TXT - ****** PC_Speed is set as "FAST" in the ini file, times in loop = 01 *** numbytes = 0
29/07/2015 23:08:07.30 - ONGOING-ISRUNNING-230806-459.TXT - At start of expect("gin:"), sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:07.82 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 9
29/07/2015 23:08:07.83 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("gin:") loop, times in loop = 02
29/07/2015 23:08:27.25 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:27.28 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("gin:") loop, times in loop = 03
29/07/2015 23:08:27.30 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:27.32 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("gin:") loop, times in loop = 04
29/07/2015 23:08:27.35 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:27.37 - ONGOING-ISRUNNING-230806-459.TXT - In expect("gin:"). Because times in loop = 5, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:27.91 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("gin:") loop, times in loop = 05
29/07/2015 23:08:27.93 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:27.96 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("gin:") loop, times in loop = 06
29/07/2015 23:08:27.98 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:28.00 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("gin:") loop, times in loop = 07
29/07/2015 23:08:28.02 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:28.04 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("gin:") loop, times in loop = 08
29/07/2015 23:08:28.07 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:28.09 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("gin:") loop, times in loop = 09
29/07/2015 23:08:28.11 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:28.13 - ONGOING-ISRUNNING-230806-459.TXT - End of expect("gin:")
29/07/2015 23:08:28.15 - ONGOING-ISRUNNING-230806-459.TXT - *************************************************************************
29/07/2015 23:08:28.17 - ONGOING-ISRUNNING-230806-459.TXT - expect("gin:") O.K. Status = 1.
29/07/2015 23:08:28.20 - ONGOING-ISRUNNING-230806-459.TXT - reply(config.Username) O.K. Status = 1.
29/07/2015 23:08:28.22 - ONGOING-ISRUNNING-230806-459.TXT - Username from HG612_stats.ini = "!!Huawei". Status = 1.
29/07/2015 23:08:28.24 - ONGOING-ISRUNNING-230806-459.TXT - *************************************************************************
29/07/2015 23:08:28.26 - ONGOING-ISRUNNING-230806-459.TXT - At start of expect("ssword:"), times in loop = 01 *** numbytes = 0
29/07/2015 23:08:28.29 - ONGOING-ISRUNNING-230806-459.TXT - ****** PC_Speed is set as "FAST" in the ini file, times in loop = 01 *** numbytes = 0
29/07/2015 23:08:28.31 - ONGOING-ISRUNNING-230806-459.TXT - At start of expect("ssword:"), sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:28.83 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:28.85 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ssword:") loop, times in loop = 02
29/07/2015 23:08:28.87 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:28.90 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ssword:") loop, times in loop = 03
29/07/2015 23:08:28.94 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:28.96 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ssword:") loop, times in loop = 04
29/07/2015 23:08:28.99 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:29.01 - ONGOING-ISRUNNING-230806-459.TXT - In expect("ssword:"). Because times in loop = 5, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:29.53 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ssword:") loop, times in loop = 05
29/07/2015 23:08:29.56 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:29.58 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ssword:") loop, times in loop = 06
29/07/2015 23:08:29.61 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:29.63 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ssword:") loop, times in loop = 07
29/07/2015 23:08:29.66 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:29.68 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ssword:") loop, times in loop = 08
29/07/2015 23:08:29.70 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:29.72 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ssword:") loop, times in loop = 09
29/07/2015 23:08:29.75 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:29.77 - ONGOING-ISRUNNING-230806-459.TXT - End of expect("ssword:")
29/07/2015 23:08:29.80 - ONGOING-ISRUNNING-230806-459.TXT - *************************************************************************
29/07/2015 23:08:29.82 - ONGOING-ISRUNNING-230806-459.TXT - expect("ssword:") O.K. Status = 1.
29/07/2015 23:08:29.84 - ONGOING-ISRUNNING-230806-459.TXT - reply(config.Password) O.K. Status = 1.
29/07/2015 23:08:29.86 - ONGOING-ISRUNNING-230806-459.TXT - Password from HG612_stats.ini = "zgj019283". Status = 1.
29/07/2015 23:08:29.88 - ONGOING-ISRUNNING-230806-459.TXT - *************************************************************************
29/07/2015 23:08:29.90 - ONGOING-ISRUNNING-230806-459.TXT - At start of expect("ATP>"), times in loop = 01 *** numbytes = 0
29/07/2015 23:08:29.93 - ONGOING-ISRUNNING-230806-459.TXT - ****** PC_Speed is set as "FAST" in the ini file, times in loop = 01 *** numbytes = 0
29/07/2015 23:08:29.96 - ONGOING-ISRUNNING-230806-459.TXT - At start of expect("ATP>"), sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:30.49 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:30.51 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ATP>") loop, times in loop = 02
29/07/2015 23:08:30.53 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:30.55 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ATP>") loop, times in loop = 03
29/07/2015 23:08:30.57 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:30.60 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ATP>") loop, times in loop = 04
29/07/2015 23:08:30.62 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:30.64 - ONGOING-ISRUNNING-230806-459.TXT - In expect("ATP>"). Because times in loop = 5, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:31.16 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ATP>") loop, times in loop = 05
29/07/2015 23:08:31.18 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:31.20 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ATP>") loop, times in loop = 06
29/07/2015 23:08:31.22 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:31.25 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ATP>") loop, times in loop = 07
29/07/2015 23:08:31.27 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:31.29 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ATP>") loop, times in loop = 08
29/07/2015 23:08:31.31 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:31.34 - ONGOING-ISRUNNING-230806-459.TXT - Still in expect("ATP>") loop, times in loop = 09
29/07/2015 23:08:31.36 - ONGOING-ISRUNNING-230806-459.TXT - numbytes received from recv(sockfd, rxbuf, RXBUFSIZE-1, 0) = 0
29/07/2015 23:08:31.38 - ONGOING-ISRUNNING-230806-459.TXT - End of expect("ATP>")
29/07/2015 23:08:31.40 - ONGOING-ISRUNNING-230806-459.TXT - *************************************************************************
29/07/2015 23:08:31.42 - ONGOING-ISRUNNING-230806-459.TXT - expect("ATP>") O.K. Status = 1.
29/07/2015 23:08:31.45 - ONGOING-ISRUNNING-230806-459.TXT - Reaching this point means logging in to the modem was successful. Status = 1,
29/07/2015 23:08:31.47 - ONGOING-ISRUNNING-230806-459.TXT - reply(xdslcmd info --stats) O.K. Status = 1, return value = 0
29/07/2015 23:08:31.49 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #025, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:32.02 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #050, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:32.54 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #075, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:33.07 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #100, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:33.59 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #125, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:34.11 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #150, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:34.63 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #175, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:35.16 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #200, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:35.68 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #225, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:36.20 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #250, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:36.72 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #275, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:37.24 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #300, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:37.76 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #325, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:38.30 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #350, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:38.88 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #375, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:39.45 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #400, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:40.02 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #425, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:40.59 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #450, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:41.17 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #475, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:41.74 - ONGOING-ISRUNNING-230806-459.TXT - **** Because this is attempt #500, sleeping for 0.500 seconds *** numbytes = 0
29/07/2015 23:08:42.31 - ONGOING-ISRUNNING-230806-459.TXT - *** ERROR!!! - Now in get_data_exit as times_in_loop was 500. Status = 1,
29/07/2015 23:08:42.35 - ONGOING-ISRUNNING-230806-459.TXT - Temp File ONGOING_GET_DATA_ERROR-230842-317.TXT was created. Status = 1,
29/07/2015 23:08:42.48 - ONGOING-ISRUNNING-230806-459.TXT - About to close(sockfd). Status = 1,
29/07/2015 23:08:42.51 - ONGOING-ISRUNNING-230806-459.TXT - *** WSACleanup has completed.
29/07/2015 23:08:42.54 - ONGOING-ISRUNNING-230806-459.TXT - *** About to free(txbuf).
29/07/2015 23:08:42.59 - ONGOING-ISRUNNING-230806-459.TXT - *** txbuf has been freed.
29/07/2015 23:08:42.62 - ONGOING-ISRUNNING-230806-459.TXT - *** About to free(rxbuf).
29/07/2015 23:08:42.68 - ONGOING-ISRUNNING-230806-459.TXT - *** rxbuf has been freed.
29/07/2015 23:08:42.74 - ONGOING-ISRUNNING-230806-459.TXT - ONGOING-ISRUNNING-230806-459.TXT DELETED - Status = 1,
29/07/2015 23:08:42.82 - ONGOING-ISRUNNING-230806-459.TXT - ERROR.LOG successfully closed. Status = 0,
29/07/2015 23:08:42.86 - ONGOING-ISRUNNING-230806-459.TXT - Abnormal End of [HG612_stats.exe]
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on July 30, 2015, 01:12:16 AM
I think I know where it might be failing, so I'll have a look at it tomorrow night.

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on July 30, 2015, 09:32:09 PM
I see you are now uploading to MDWS via DSLStats.

However, could you please try manually running the attached version of HG612_stats.exe between DSLStats data harvests & post the resulting data from ONGOING_ERROR.LOG_file_ERROR.TXT?

Please change the modem type in the HG612_stats.ini file to HG635 though as I have now added some specific code for that modem (mainly to deal with the "$" prompt).


Also, disable uploading to MDWS via my program if you continue to upload via DSLStats


I'm not sure whether it needs the additional code as per the HG622 or not in order to login via my program, but it is included in the attached version of HG612_stats.exe

Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on October 16, 2015, 07:41:53 PM
I've released an update to the the GUI, unfortunately it's the removal of MyDSLWebstats  :(

Quote
5.1.5767.32891   16-10-2015

      Remove MyDSLWebstats and turned off data upload - website no longer running. (The code is still there but hidden should it be required again)
      Corrected issue with resync time calculation when spanning day light saving changes
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Bald_Eagle1 on October 16, 2015, 08:08:34 PM
Discussion regarding using HG635 has been moved to here:-

http://forum.kitz.co.uk/index.php/topic,16327.0.html
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on October 17, 2015, 06:57:40 AM
guys if tony doesnt like my proposals I am willing to start a new solution with your cooperation if ok, but waiting for tony to reply first.

My solution will likely use already existing tools for graphs and we can work together to get data compatible with the graphing templates.  I will be in it for the long haul, and will be a 100% free service.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on October 27, 2015, 07:56:36 PM
Just a quick update to reinstate MyDSL WebStats fuctionality, note this will not automatically enable stats upload, you'll need to check to ensure it's enabled after installing the update.

Quote
5.1.5778.35529   27-10-2015

      Reinstate MyDSL WebStats functionality
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: kitz on November 01, 2015, 12:39:32 AM
Thanks ronski for your continued support in making it work with MDWS.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on April 13, 2016, 10:10:21 PM
Minor update to the GUI

Quote
5.1.5947.37706   13-04-2016

      Added following values to the stats tab
      
         Upstream CRC errors (delta)
         Upstream HEC errors (delta)
         Upstream FEC errors (delta)
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on April 14, 2016, 02:12:38 PM
thanks, updated successfully.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on May 07, 2016, 01:27:12 PM
a tip for those running this on mechanical drives like myself, ntfs compression works wonders for the files, I had 37gig usage from the daily snapshot graphs, after ntfs compression it was down to 7 gig, also file access times are significantly improved on my system since modern processors can compress and decompress way faster than old i/o can process. 

You dont need to compress the entire drive, just the folder.

With that said now a feature request :)

Ronski can you please add a once a week and once a month option to the auto snapshot function?

--note--

I had to set PC speed to 'fast' again after this change ;) big speedup.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on May 08, 2016, 08:15:06 AM
With that said now a feature request :)

Ronski can you please add a once a week and once a month option to the auto snapshot function?


It would probably be easiest to give a day of the week option  to run, but  BE1 would need to add support in HG612 stats first.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: matt12321 on June 28, 2016, 10:48:30 PM
Just installed this onto a Windows Server 2008r2 machine - I can force it to look up the stats and retrieve them from the log folder but nothing is appearing in the GUI (all N/A).

The scheduling etc is all green.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on June 29, 2016, 06:09:12 AM
If N/A is showing in all the connection stats then this means a modem_stats.log has not been created.

As all the four boxes on the right are green then I'm going to presume that your scheduled task is created and enabled, so we have some things that we need to check.

1. That the scheduled task is created properly, and set to run HG612_Run.exe located in the same folder as the GUI program.
2. That nothing is blocking (IE Antivirus/security settings) the following three programs, also all located in the same folder. HG612_Run.exe, HG612_stats.exe & HG612_current_stats.exe. You could try running these manually one at a time and see what happens.
3. That your firewall is not blocking telnet access to the modem.
4. Your modem IP address and details are set correctly on the modems settings tab.

Hopefully one of the above will solve the problem.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: skyeci on June 29, 2016, 07:04:02 AM
Also worth checking the task password is correct. If in doubt delete the current task and create a new task with your admin password.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: matt12321 on June 29, 2016, 07:25:27 AM
I ran the programs and deselected the UAC "ask me every time for this program" - so hopefully that will fix it!
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Dray on June 29, 2016, 07:29:27 AM
You have to schedule a task to run the programs every minute or so, 24*7

Or use DSLStats which is simpler.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: skyeci on June 29, 2016, 08:27:02 AM
Looks like it has started to upload now.let it run 24/7
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on October 02, 2016, 05:05:00 PM
After my old PC failing  mobo it think as it won't read the hdd  just lots of bzbz instead of it's correct name, anyway i want to instal and run the modem stats on a different drive to C as my c drive is a SSD and the modem stats is write intensive  is there a way to run it from my other hdd ?
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on October 02, 2016, 05:33:31 PM
Yes, just copy it to where you want to run it, open the GUI program and from the settings/directories tab tell it where the directories are. If you change the main directory location first it will ask to update the others automatically.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Chrysalis on October 02, 2016, 06:18:20 PM
ronski any news on the new version with adjusted service checks?
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: tommy45 on October 02, 2016, 06:26:43 PM
Yes, just copy it to where you want to run it, open the GUI program and from the settings/directories tab tell it where the directories are. If you change the main directory location first it will ask to update the others automatically.
many thank's all working now, just got to sort e-mail client and my TS3 server out
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on December 05, 2016, 08:48:25 PM
I've released a minor update to the GUI.

Quote
5.1.6143.36645   26-10-2016

      Changed timer interval for checking scheduled task - reduces CPU load
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on December 05, 2016, 10:08:20 PM
Not sure why, but my works system stopped uploading stats after I allowed an automated update, the upload stats option was unchecked on the MyDSL Stats tab.

If this happens to anyone please report here and I'll look into it.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: pooclah on December 11, 2016, 07:54:28 PM
Hi Ronski

Just updated mine and box still ticked - everything working as normal.

Thank you
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on December 11, 2016, 08:33:58 PM
Thanks pooclah, I had been testing the new version on my works PC, but rolled it back to an earlier version to check the update went OK, I think it was the earlier version that caused it.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on December 22, 2016, 08:57:09 PM
MS seem to have altered something in Windows 10, and this is affecting parts of the program which delete the task and also disable/enable the task when turning off both stats logging options.

If you run into these problems to work-a-round the issue run the GUI with elevated privileges  (Right click - rus as administrator)

You can also edit the programs properties and on the compatibility tab tick the checkbox to "Run this program as an administrator", and then clip apply. Each time you run the program you will get a UAC window pop up though (there are ways around this without turning off UAC).

Note: This only so far seems to affect Windows 10, W7 & W8.1 and also Windows Home Server 2011 seem to work as they should.

I will try to pursue a proper fix in due course.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on May 07, 2017, 10:28:02 AM
I've released a minor update to handle the change in URL for the TBB ping monitor graphs, since they updated the website the URL has changed, old URLs still work though.

Quote
5.1.6336.18537   07-05-2017

      Updated TBB Ping monitor validation for new URL format
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on March 11, 2018, 05:42:14 PM
I've released a minor update to the graphic user interface, this removes and turns off My DSL Webstats uploads as the service is closing down.

The code is still in there, but hidden, so should the service come back I can reactivate it, BUT it relies on everything else being the same as I have no access to the code that actually uploads the data - Baldeagle1 has not been on the forum for over a year now.

Quote
5.1.6641.36791   08-03-2017

      Removed My DSL WebStats - service closing down on 12 March
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on April 28, 2018, 05:29:51 PM
Just a quick note to say that I've changed broadband suppliers, so the update check will fail as I've yet to fathom why my home hosted website is not reachable.
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: kitz on May 06, 2018, 07:47:50 PM
Thanks for letting us know :)
Title: Re: HG612 Modem Stats Editor & GUI v5 released
Post by: Ronski on May 06, 2018, 10:57:28 PM
Thanks, it's all fixed now, meant to post back, but forgot.