Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Fistolution]

Hey everyone.

I'm new to the whole actually-getting-stats-about-your-line game; I know too little to know what's wrong, but just enough to be dangerous.

A few details about my setup:

• I use a HG612 modem (passthrough) connected to an RT-N66U running Tomato.
• It's connected by two cables: one for internet connectivity, the other for stats.
• The modem's IP for stats is 192.168.1.254.
• It runs unlocked firmware version A2pv6C035m.d22g which, if memory serves, came from the HG612 hacking wiki.
• The computer that does the logging is 64-bit Windows 8.1, and is not switched on all of the time.
• The programs (and stats) are synced over Dropbox.
• The full path to the logging directories do not contain spaces, in case it matters (C:\Users\<username_with_no_spaces_honest>\Dropbox\Programs\Information)

I've been using the HG612 stats scripts and GUI v2.0 for a couple of weeks without issue.  A few days ago, when I launched the GUI, I was greeted with an error.  Here's a couple of recent examples from the file:

Code: [Select]

2014-05-17 21:34:03 - Error reading modem log.
2014-05-17 21:34:03 - Error message: String was not recognized as a valid DateTime.
2014-05-17 21:34:03 - Fields in log: 128
2014-05-17 21:34:03 - Array  fields: 17/05/2014, 21:34, 75501, 20000, 6.2, 15.3, 12.4, 6.8, 88164, 24399, PTM, 0, 6, 13185, 9, 0, 0, 833, 0, 0, 42, 0, 0.231, 13185, 9, 42, 590912, 195361, 42615, 0, 6, 0, 151093254, 199250, 10909254, 0, 0, 0, 1477, 1, 0, 4, 0, 0, 0, 0, 0, 0, 14106, 0, 4.2, 21.9, 33.0, 0.0, 12.0, 28.6, 43.9, 4.2, 20.9, 32.2, 0.0, 12.0, 28.6, 43.9, 16.7, 15.3, 15.3, 0.0, 6.3, 6.1, 6.1, -4.0, -19.8, 6.4, 0.0, 8.0, 7.9, 7.0, Showtime, 0, 0, L0, 17a, ON, ON, No, Showtime, 0.0, 0.0, 51, 237, 1, 1, 64, 45, 12, 16, 0.0219, 0.3782, 23364, 5373, 0, 0, 0, 0, 120754703, 0, 255897, 0, 0, 0, 0, 20, 20, 3.00, 0.00, 1.40, 4.25, 8.00, 0.00, 136.89, 60.17, 195, 36, VDSL2, 15, 0, 0
2014-05-17 21:34:03 - Complete  line:  0 20 20 3.00 0.00 1.40 4.25 8.00 0.00 136.89 60.17 180 36 VDSL2 13 0 0
17/05/2014 21:34 75501 20000 6.2 15.3 12.4 6.8 88164 24399 PTM 0 6 13185 9 0 0 833 0 0 42 0 0.231 13185 9 42 590912 195361 42615 0 6 0 151093254 199250 10909254 0 0 0 1477 1 0 4 0 0 0 0 0 0 14106 0 4.2 21.9 33.0 0.0 12.0 28.6 43.9 4.2 20.9 32.2 0.0 12.0 28.6 43.9 16.7 15.3 15.3 0.0 6.3 6.1 6.1 -4.0 -19.8 6.4 0.0 8.0 7.9 7.0 Showtime 0 0 L0 17a ON ON No Showtime 0.0 0.0 51 237 1 1 64 45 12 16 0.0219 0.3782 23364 5373 0 0 0 0 120754703 0 255897 0 0 0 0 20 20 3.00 0.00 1.40 4.25 8.00 0.00 136.89 60.17 195 36 VDSL2 15 0 0

2014-05-17 21:34:03 - Processed line: A 17/05/2014 21:34 75501 20000 6.2 15.3 12.4 6.8 88164 24399 PTM 0 6 13185 9 0 0 833 0 0 42 0 0.231 13185 9 42 590912 195361 42615 0 6 0 151093254 199250 10909254 0 0 0 1477 1 0 4 0 0 0 0 0 0 14106 0 4.2 21.9 33.0 0.0 12.0 28.6 43.9 4.2 20.9 32.2 0.0 12.0 28.6 43.9 16.7 15.3 15.3 0.0 6.3 6.1 6.1 -4.0 -19.8 6.4 0.0 8.0 7.9 7.0 Showtime 0 0 L0 17a ON ON No Showtime 0.0 0.0 51 237 1 1 64 45 12 16 0.0219 0.3782 23364 5373 0 0 0 0 120754703 0 255897 0 0 0 0 20 20 3.00 0.00 1.40 4.25 8.00 0.00 136.89 60.17 195 36 VDSL2 15 0 0
2014-05-17 21:34:03 - Read    length:  600

2014-05-17 21:35:03 - Error reading modem log.
2014-05-17 21:35:03 - Error message: String was not recognized as a valid DateTime.
2014-05-17 21:35:03 - Fields in log: 128
2014-05-17 21:35:03 - Array  fields: 17/05/2014, 21:35, 75501, 20000, 6.2, 15.3, 12.4, 6.8, 88164, 24407, PTM, 0, 6, 14823, 9, 0, 0, 892, 0, 0, 1638, 0, 0.248, 14823, 9, 1638, 633526, 209466, 42614, 0, 6, 0, 162002507, 833810, 10909253, 0, 0, 0, 1477, 1, 0, 4, 0, 0, 0, 0, 0, 634560, 14105, 0, 4.2, 21.9, 33.0, 0.0, 12.0, 28.6, 43.9, 4.2, 20.9, 32.2, 0.0, 12.0, 28.6, 43.9, 16.8, 15.3, 15.3, 0.0, 6.2, 6.1, 6.2, -4.0, -19.8, 6.4, 0.0, 8.0, 7.9, 7.0, Showtime, 0, 0, L0, 17a, ON, ON, No, Showtime, 0.0, 0.0, 51, 237, 1, 1, 64, 45, 12, 16, 0.0219, 0.3782, 23364, 5373, 0, 0, 0, 0, 129465684, 0, 267742, 0, 0, 0, 0, 20, 20, 3.00, 0.00, 1.40, 4.25, 8.00, 0.00, 136.89, 60.17, 210, 38, VDSL2, 15, 2, 0
2014-05-17 21:35:03 - Complete  line: 3.00 0.00 1.40 4.25 8.00 0.00 136.89 60.17 195 36 VDSL2 15 0 0
17/05/2014 21:35 75501 20000 6.2 15.3 12.4 6.8 88164 24407 PTM 0 6 14823 9 0 0 892 0 0 1638 0 0.248 14823 9 1638 633526 209466 42614 0 6 0 162002507 833810 10909253 0 0 0 1477 1 0 4 0 0 0 0 0 634560 14105 0 4.2 21.9 33.0 0.0 12.0 28.6 43.9 4.2 20.9 32.2 0.0 12.0 28.6 43.9 16.8 15.3 15.3 0.0 6.2 6.1 6.2 -4.0 -19.8 6.4 0.0 8.0 7.9 7.0 Showtime 0 0 L0 17a ON ON No Showtime 0.0 0.0 51 237 1 1 64 45 12 16 0.0219 0.3782 23364 5373 0 0 0 0 129465684 0 267742 0 0 0 0 20 20 3.00 0.00 1.40 4.25 8.00 0.00 136.89 60.17 210 38 VDSL2 15 2 0

2014-05-17 21:35:03 - Processed line: A 17/05/2014 21:35 75501 20000 6.2 15.3 12.4 6.8 88164 24407 PTM 0 6 14823 9 0 0 892 0 0 1638 0 0.248 14823 9 1638 633526 209466 42614 0 6 0 162002507 833810 10909253 0 0 0 1477 1 0 4 0 0 0 0 0 634560 14105 0 4.2 21.9 33.0 0.0 12.0 28.6 43.9 4.2 20.9 32.2 0.0 12.0 28.6 43.9 16.8 15.3 15.3 0.0 6.2 6.1 6.2 -4.0 -19.8 6.4 0.0 8.0 7.9 7.0 Showtime 0 0 L0 17a ON ON No Showtime 0.0 0.0 51 237 1 1 64 45 12 16 0.0219 0.3782 23364 5373 0 0 0 0 129465684 0 267742 0 0 0 0 20 20 3.00 0.00 1.40 4.25 8.00 0.00 136.89 60.17 210 38 VDSL2 15 2 0
2014-05-17 21:35:03 - Read    length:  600

I couldn't think of anything I'd changed recently, so I went through the some troubleshooting, both through experience and what I could find on forums:

• Re-creating the scheduled task?  Nope.
• Any left over scheduled tasks that weren't deleted?  Nope.
• Re-unzip v2.0 over the top of the existing files?  Nope.
• Unzip v2.0 in to a new location and start from scratch?  Nope.
• Hey look!  v2.1 just came out!  Perhaps that fixes it?  Nope.
• Re-run through all the steps above for v2.1?  Nope.
• Restart the modem?  Nope.

As you can see, a lot of "Nope"!  The only obvious thing I can think of that I haven't done is re-flash the modem's firmware.  But before I go that crazy, I thought I'd check in with people who might actually know what's going on.

The scripts still appear to be working correctly, as they're updating the log files and new snapshots are still being generated.  I've attached the most recent snapshot.  I suppose while we're here I wouldn't mind knowing if my stats look normal and healthy, but I could probably save that for another thread. 

The GUI's version info states:

Code: [Select]

HG612 Modem logs stats viewer & settings editor V2.1 created 2014-05-13 20:15:44
 Version 2.1.5246.34669 running on Microsoft Windows 8.1 Pro with Media Center
The stats I've seen so far and the things I've had to learn to even vaguely understand them have been very enlightening.  I would be great to continue drawing stats so I can get the big picture of my line's stability over the coming months, and thus why I'd love to get this working again.  But even if I can't get it working again, at least I've learnt a lot on the way.

If you need any more info, ask away and I'll try and get it back to you.  Thanks for reading. 

[Ronski]

Hi Fistolution and welcome to the forums.

Sorry you're having problems, I've seen this problem before and thought I had fixed it. I'm on my phone at the moment, so will take a better look tomorrow. I'm sure your stats are still being recorded and the graphs should still be created.

How big is your modem log file?
Could you post your modem _stats log file or a section of it which includes the 17/05/2014 please. You can see where it's located from the directory paths settings tab.

[Bald_Eagle1]

If you need any more info, ask away and I'll try and get it back to you.  Thanks for reading. 

It looks like you are still using some or maybe all v 2.0's programs (graph version 4.1).

V 2.1 graph version should be 5.0.2.1



With v 2.1 of the package, the first row in the ONGOING_ERROR.LOG_file_ERROR.TXT file should contain the program version No:-

10/05/2014 23:57:00.14 - ONGOING-ISRUNNING-235700-099.TXT - Start of [HG612_stats.exe] - **** Version 2.1 ****


If you are using v 2.1 of the GUI, you also need to use the other programs from v 2.1

[Ronski]

I've used the two lines you've posted from the error log to create a modem log on my system for testing, but it works without a problem, even tried it on a fresh 2.1 installation on Windows 8.1, still works OK.

Only thing I can suggest is posting your modem_stats log or a section of it which had the problems, also post the GUIerror log.

Just seen BE1's post, I wonder if the errors were from an old version of the GUI, although I can see you now have the latest version, do you still have the problem this morning?

I've attached W8 screen shot of the line from your modem, note SES Errors and Error Seconds are not yours, they are from my xlogfile.

[Fistolution]

Thanks for the tips.

@Ronski
I'm afraid despite the GUI updates it's still not working.

As a test, I've deleted the entire Apps directory and every file inside the Scripts directory except HG612_stats.ini.  I then unzipped the latest versions from the release on this page.  It's still not working just yet.

I then let the GUI auto-update:

Code: [Select]

HG612 Modem logs stats viewer & settings editor V2.1 created 2014-05-20 19:36:56
 Version 2.1.5253.9955 running on Microsoft Windows 8.1 Pro with Media Center
My modem_stats.log is 4.5MB, so a bit big to attach.   I've excerpted the data from the 17th until today and attached it.  Please again note that my computer is not on all of the time, so there will be massive holes in the data.

I've also attached GUI Error Log.txt in its entirety.  Finally, I've also attached my configuration (which I didn't delete earlier) in case it should matter.

These are all in FistolutionErrorReadingLogs.zip.

@Bald_Eagle1
I've tried to ensure that all of the graphing programs are now up to date, though it looks like I might have had the correct version (at least of something) already, as I see this in the log:

Code: [Select]

2014-05-17 21:06:10.96 - ONGOING-ISRUNNING-210610-956.TXT - Start of [HG612_stats.exe] - **** Version 2.1 ****
I actually see two ONGOING_ERROR.LOG_file_ERROR.TXT files; one in Event & Error Logs, and one in Ongoing stats.

I'm guessing the Ongoing Stats one seems to only happen on startup, because this is the entire contents of the file:

Code: [Select]

2014-05-19 19:07:10.88 - ONGOING-ISRUNNING-190710-594.TXT - connect() ERROR!!! - Exiting HG612_stats.exe. Status = 1,
2014-05-20 21:55:59.11 - ONGOING-ISRUNNING-215558-028.TXT - connect() ERROR!!! - Exiting HG612_stats.exe. Status = 1,
2014-05-21 18:42:26.83 - ONGOING-ISRUNNING-184226-504.TXT - connect() ERROR!!! - Exiting HG612_stats.exe. Status = 1,
Maybe it tries to connect before the network is established?

The one in the Event & Error Logs directory is much longer, and I've zipped it up for you in the attachments as FistolutionErrorReadingLogs.zip.

[Ronski]

I wonder if it's something to do with Dropbox, perhaps pause syncing or even temporarily move the folders out of Dropbox.

I'll run some tests using your modem log when I get chance over the next few days. I'll basically write a program to read one line at a time from your log, and write it to a modem log file which my GUI is monitoring. This wll simulate HG612 Stats writing to the log and my GUI will read the stats each time the log is written and I can then see if I get any errors.

Edit:Just tried using your modem log and something weird happened, will investigate further later, as the wife and kids are due home any moment.

[Ronski]

Edit:Just tried using your modem log and something weird happened, will investigate further later, as the wife and kids are due home any moment.

What did you use to extract the data from your modem log file as it seems to have altered the structure of the data?

The log file is created with two character codes to signify the end of each line, Chr 13 followed by Chr 10, for some reason in the file you uploaded you only have the Chr 10 code, this stopped the GUI being able to detect the end of each line, but it doesn't cause the error you are seeing. It eventually reads the entire file, until I got an error trying to read before the beginning of the file.

I've just written a little program to read a line from your log file and write it out to another (adding the correct end of line characters), it was able to go through the entire log with no errors from the GUI, so apart from what I mention above I can't find a problem.

I've also tried this on Windows 8, and apart from the laptop struggling to keep as I was updating the modem log file a 100 time a minute, I still didn't have any errors.

My only suggestion's I can think of is to move the files out of dropbox, also make sure dot net is fully updated and see if that sorts the problem out.

When looking at the GUI error file, it states that "String was not recognized as a valid DateTime" but the line that shows the array fields shows the date and time correctly, I wonder if it could be something to do with how you have time/date localisation set in Windows possibly.

Anyway need to get some sleep, early start in the morning.

[Bald_Eagle1]

@Bald_Eagle1
I've tried to ensure that all of the graphing programs are now up to date, though it looks like I might have had the correct version (at least of something) already, as I see this in the log:

Code: [Select]

2014-05-17 21:06:10.96 - ONGOING-ISRUNNING-210610-956.TXT - Start of [HG612_stats.exe] - **** Version 2.1 ****
I actually see two ONGOING_ERROR.LOG_file_ERROR.TXT files; one in Event & Error Logs, and one in Ongoing stats.

I'm guessing the Ongoing Stats one seems to only happen on startup, because this is the entire contents of the file:

Code: [Select]

2014-05-19 19:07:10.88 - ONGOING-ISRUNNING-190710-594.TXT - connect() ERROR!!! - Exiting HG612_stats.exe. Status = 1,
2014-05-20 21:55:59.11 - ONGOING-ISRUNNING-215558-028.TXT - connect() ERROR!!! - Exiting HG612_stats.exe. Status = 1,
2014-05-21 18:42:26.83 - ONGOING-ISRUNNING-184226-504.TXT - connect() ERROR!!! - Exiting HG612_stats.exe. Status = 1,

The one with hardly anything in it (in the Ongoing_Stats folder) is in the wrong folder.

I spotted that issue this morning & amended HG612_stats.exe, ready for a minor update release (v 2.11)

Maybe it tries to connect before the network is established?

The one in the Event & Error Logs directory is much longer, and I've zipped it up for you in the attachments as FistolutionErrorReadingLogs.zip.

The one in the Event & Error Logs directory is the correct one.

The connect() ERROR!!! lines will be in the correct log in the correct directory if you use the attached version of HG612_stats.exe.


I suspect you are correct that a connection attempt is made before the network is established.
So that shouldn't be anything to be concerned about.
Everything else seems O.K.


Even though the modem_stats.log extract does have an issue with line endings as mentioned by RONSKI, it does plot O.K. (apart from all the gaps when you switch the PC off).

The gaps in the data is the cause of the bunching up of the dates/times along the X axis.

I have attached the montage using a 3 hour extract from your log.

[Bald_Eagle1]

From the 3 hour graphs I can see that your DS Attainable rate is quite good, but the high Interleaving depth & low DS SNRM have caused lower sync speeds.

It is difficult to get a full feel for your connection with such limited bursts of logging.
Could you not leave the PC switched on 24/7 for a few days to obtain a 'full' set of daily data as a monitoring baseline?


As you are using an older version of the modem's firmware, it might just be worth giving the updated version a shot.
The updated version does appear to generally provide more stability & given time, your Interleaving depth may reduce (possibly moving on to a fastpath connection) & thus provide higher DS sync speed.
Although a shade over 75 Mbps ain't all that bad is it?

[Ronski]

Fistolution, there is a beta version available, please download and test it- make sure you have the option selected to receive beta updates in the GUI settings tab.

It's just something I thought I would try on the off chance it would cure your problem.

[Fistolution]

Thanks for your time and the detailed replies!

I decided to leave this for a little while (as you can no doubt see!), so I could sort out some (probably) more important things in my life.  More important than an internet connection?  Never. 

First, I apologise about the line endings thing.  I simply cut and paste the relevant part of the logs in to a new file using Notepad++, and I've set that to save using UNIX line endings as default.  My bad!

Anyway, when I came to launch the GUI today...  Everything works.  Hm.  I was still using the latest stable version.

Fistolution, there is a beta version available, please download and test it- make sure you have the option selected to receive beta updates in the GUI settings tab.

It's just something I thought I would try on the off chance it would cure your problem.

I updated, as per Ronski's advice, to the beta version.  No errors!  Gah!

Yes, this is actually good, but I do find it a little annoying when things seem to fix themselves up for no apparent reason.  I guess I should count my blessings.

I noticed that the beta GUI has a program versions tab (very sensible BTW).  My output seems a bit concerning:

Code: [Select]

Graph6 = No version info available.
Graphpd = No version info available.
HG612 Stats Logging GUI = 2.1.5267.38646
HG612_current_stats = No version info available.
HG612_stats = No version info available.
SET_HG612_Date_and_Time = No version info available.

Could you not leave the PC switched on 24/7 for a few days to obtain a 'full' set of daily data as a monitoring baseline?

Is it possible to extract the router info using a Linux machine?  I run a server locally 24/7, and it would be ideal if I can extract the logs using that machine instead.  Naturally I'd be able to transfer them to my Windows PC afterwards for graphing if needed.

Failing that, I'll leave the machine on a few days to get a baseline

As you are using an older version of the modem's firmware, it might just be worth giving the updated version a shot.

I thought I was using the updated one!  Oops.  Do you know where I could find the latest version?  And do I have to worry about BT Agent etc.?

Although a shade over 75 Mbps ain't all that bad is it?

Oh, it's marvellous.  My previous connection was ADSL2+ running at 10 down, 1 up, so I certainly appreciate the difference. 

I just would like to keep track of it over the coming months/years to make sure that things stay good!

Once again, thank you both for all of your time!

[Bald_Eagle1]

I have attached the very latest versions of my programs.

They didn't actually contain the version info until about 1/2 hour ago !!!!


Ronski also updated his GUI this evening.
The version you have might show my program versions (now that I have sussed out how to correctly add the version details to them).

They should now be reported as version 2.1.1.0 as I have been tweaking them & recompiled them all this evening.

They are still classed as beta versions, but they are 99.99% ready for upload to the main download site.


Depending on the content of your current ini file, you may need to delete & recreate the ongoing logging task via the GUI.


burakkucat may be able to point you toward Linux versions, but as far as I am aware they don't include a GUI & may not be fully up to date with additional data that is now included in the Windows graphing versions.





The updated firmware can be obtained here:-

https://mega.co.nz/#F!LdJFDIJL!e_E1twsIg2kTet8mPjrb4w

Use one of the images from the 'Experimental' area.


I use this one as I want my modem to be able to accept any future firmware updates:-

bcm96368MVWG_fs_kernel_HG612V100R001C01B030SP06_unlockedgui

[Ronski]

Well, I was about to reply but had to make a drink for my good wife, and I've come back to find BE1 has replied saving me the trouble.

The latest available beta version should show the version numbers just fine, we hope eventually  to get all programs to update via the GUI, but my time is a bit short at the moment.

I do agree it is strange when something doesn't work, then starts  working for no apparent reason, but let's hope it stays working.