Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1] 2 3

Author Topic: HG612 Modem Stats - G.INP Graphs  (Read 10919 times)

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
HG612 Modem Stats - G.INP Graphs
« on: April 17, 2015, 08:32:27 PM »

Just a quick note...................


I have recently been tweaking and updating the programs.

These updates will shortly be released for updating via the GUI.

In the meantime, please see the attached G.INP montage in its proposed layout from the latest 30 days of stats from my connection (including the switch over from non-G.INP to G.INP active.

I have attempted to combine all the relevant Bearer 0, Bearer 1 & G.INP related stats into a single montage.

If G.INP is not yet activated, the usual Bearer 0 only data montage will be generated.


Green graph borders = Always present data
Grey graph borders   = Bearer 0 data
Yellow graph borders = Bearer 1 data
Blue graph borders    = non-specific Bearer data.


Comments/feedback regarding the proposed layout would be very much appreciated.

Just for information purposes, I have also attached the montage for a 24 hour period.

« Last Edit: April 17, 2015, 10:32:43 PM by Bald_Eagle1 »
Logged

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 32216
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: HG612 Modem Stats - G.INP GRaphs
« Reply #1 on: April 17, 2015, 08:54:22 PM »

Well done BE1.  Nice work. :thumbs:


There's quite a lot of data now to show.   
A thought just occured as I stretched the browser window across both dual monitors, that there is a lot of info there and for those of us that read line stats, I wondered about perhaps a cutdown version of the more important graphs that we use most of the time.

Still have the full monty, but say another version that is forum friendly and contains say just the US and DS SNRm graph, the combined output power,  combined DS&Us bitwaps etc etc.   If we suspect a problem with say the DS SNRm we could always ask for the full monty.

Its just a suggestion, no worries if its a PITA to do, but it would be interesting to see what others who read stats think too, and if it would make things easier to just be presented with the vital info first.
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 27726
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: HG612 Modem Stats - G.INP GRaphs
« Reply #2 on: April 17, 2015, 08:57:12 PM »

Hmm . . . There is just so much information that it is rather overwhelming to try and take it all in. Also the physical size of the montages have become too large for easy viewing. Not only do I have to vertical scroll but horizontal scrolling is also required.  :-\

The phrase "over-egging the pudding" comes to mind.  :-X

[Edit: I see kitz was faster at her keyboard and a little more tactful than the perpetually grumpy kuro-neko!]
« Last Edit: April 17, 2015, 08:59:25 PM by burakkucat »
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 Modem Stats - G.INP GRaphs
« Reply #3 on: April 17, 2015, 10:26:01 PM »

How's about these:-

6 days of VITAL_STATS & FULL_MONTY from a different G.INP active connection.


Logged

NewtronStar

  • Kitizen
  • ****
  • Posts: 4838
Re: HG612 Modem Stats - G.INP Graphs
« Reply #4 on: April 17, 2015, 10:43:39 PM »

Who is going to interpret/explain all those extra graphs to a new member which is having a line issue ?

At the moment a rtx_tx per min above 90 will give me 1 errored second on DSLstats.
« Last Edit: April 17, 2015, 11:13:59 PM by NewtronStar »
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 Modem Stats - G.INP Graphs
« Reply #5 on: April 17, 2015, 11:16:49 PM »

Now, that IS a tough question.

I thought that I had a reasonably good understanding of the differences between good & poor connections before G.INP was implemented & could immediately spot problem areas.

It immediately became much harder to do that as soon as G.INP was introduced, not least due to the masses of new data to consider.

What I have seen though is that G.INP seems to do a pretty good job of stabilising 'problematic' connections that would have previously taken significant speed hits & quite large increases in delay etc.


It seems that there is now a buffer to receive data where a pre-determined number of attempts are made to correct it via rtx_c etc.
Only if that still fails, are errors converted to CRCs etc. that need full retransmission.

The overhead used for G.INP seems to be far lower than the previous method of automatically applying high interleaving depths, delay & reduced sync speeds to deal with reasonably infrequent bursts of interference.


Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 Modem Stats - G.INP Graphs
« Reply #6 on: April 17, 2015, 11:37:14 PM »

Who is going to interpret/explain all those extra graphs to a new member which is having a line issue ?

At the moment a rtx_tx per min above 90 will give me 1 errored second on DSLstats.

& what about rtx_c & rtx_uc?

I THINK it will be the rtx_uc that causes one or more CRCs, which trigger the ES (but I'm not sure).

« Last Edit: April 17, 2015, 11:57:09 PM by Bald_Eagle1 »
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 Modem Stats - G.INP Graphs
« Reply #7 on: April 17, 2015, 11:55:14 PM »

Here's the Bearer 0 OHFerr/CRC to go with the other graphs
Logged

NewtronStar

  • Kitizen
  • ****
  • Posts: 4838
Re: HG612 Modem Stats - G.INP Graphs
« Reply #8 on: April 17, 2015, 11:59:25 PM »

& what about rtx_c & rtx_uc?
I THINK it will be the rtx_uc that causes a CRC, which triggers the ES (but I'm not sure).

Look BE1 you have given us excellent insight into our stats over the years with your program and your knowledge just keep going  ;) the weird part about G.INP is as you have pointed out it helps problematic lines and the goodside of that is we don't need to monitor are broadband lines so often which then has a downside the developers don't feel there is any need to expand on their projects.

Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 Modem Stats - G.INP Graphs
« Reply #9 on: April 18, 2015, 12:08:07 AM »

Another question to mull over..............

How the hell will we now be able to report a genuine fault to our ISPs with any real confidence, especially as 'real' line issues as shown in the other user's 6 day stats don't always result in clobbered sync speeds like they used to?

He & I believe he has been experiencing an intermittent HR/dodgy joint issue.
That would have been really easy to spot & provide hard evidence not too long ago, but now...............???


Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 Modem Stats - G.INP GRaphs
« Reply #10 on: April 18, 2015, 12:15:02 AM »

 :lol:

[Edit: I see kitz was faster at her keyboard and a little more tactful than the perpetually grumpy kuro-neko!]

That's probably because she's a M$ Windows user  ;) :baby:  :lol:

Personally, I open graphical forum attachments directly into my M$ Windows provided Photo Viewer program rather than directly in the forum page.
That way I can very easily use the mouse wheel to zoom in & out & also drag the picture up/down left/right to the area of particular interest.

Logged

NewtronStar

  • Kitizen
  • ****
  • Posts: 4838
Re: HG612 Modem Stats - G.INP Graphs
« Reply #11 on: April 18, 2015, 12:58:37 AM »

Warning

HG612_modem_stats is having a hissy fit the reason must be a HG612 firmware update

Software version = N/A
Software last change detected at 18/04/2015 at 00:53

Firmware version = N/A
Firmware last change detected at 18/04/2015 at 00:53

CPU version = N/A
CPU last change detected at 18/04/2015 at 00:53

CFE version = N/A
CFE last change detected at 18/04/2015 at 00:53


Software version = V100R001C01B030SP08
Software last change detected at 18/04/2015 at 00:56

Firmware version = A2pv6C038m.d24j
Firmware last change detected at 18/04/2015 at 00:56

CPU version = BCM6368
CPU last change detected at 18/04/2015 at 00:56

CFE version = 1.0.37-102.6
CFE last change detected at 18/04/2015 at 00:56
« Last Edit: April 18, 2015, 01:02:24 AM by NewtronStar »
Logged

NewtronStar

  • Kitizen
  • ****
  • Posts: 4838
Re: HG612 Modem Stats - G.INP Graphs
« Reply #12 on: April 18, 2015, 01:29:48 AM »

And this for the logs

24/01/2015 at 01:56 - Firmware version change detected, changed to A2pv6C038m.d24j from N/A
24/01/2015 at 01:56 - Software version change detected, changed to V100R001C01B030SP08 from N/A
24/01/2015 at 01:56 - CPU version change detected, changed to BCM6368 from N/A
24/01/2015 at 01:56 - CFE version change detected, changed to 1.0.37-102.6 from N/A
25/02/2015 at 22:24 - Firmware version change detected, changed to N/A from A2pv6C038m.d24j
25/02/2015 at 22:24 - Software version change detected, changed to N/A from V100R001C01B030SP08
25/02/2015 at 22:24 - CPU version change detected, changed to N/A from BCM6368
25/02/2015 at 22:24 - CFE version change detected, changed to N/A from 1.0.37-102.6
25/02/2015 at 22:24 - Firmware version change detected, changed to A2pv6C038m.d24j from N/A
25/02/2015 at 22:24 - Software version change detected, changed to V100R001C01B030SP08 from N/A
25/02/2015 at 22:24 - CPU version change detected, changed to BCM6368 from N/A
25/02/2015 at 22:24 - CFE version change detected, changed to 1.0.37-102.6 from N/A
03/04/2015 at 00:51 - Firmware version change detected, changed to A2pv6C038m.d24j from N/A
03/04/2015 at 00:51 - Software version change detected, changed to V100R001C01B030SP08 from N/A
03/04/2015 at 00:51 - CPU version change detected, changed to BCM6368 from N/A
03/04/2015 at 00:51 - CFE version change detected, changed to 1.0.37-102.6 from N/A
18/04/2015 at 00:53 - Firmware version change detected, changed to N/A from A2pv6C038m.d24j
18/04/2015 at 00:53 - Software version change detected, changed to N/A from V100R001C01B030SP08
18/04/2015 at 00:53 - CPU version change detected, changed to N/A from BCM6368
18/04/2015 at 00:53 - CFE version change detected, changed to N/A from 1.0.37-102.6
18/04/2015 at 00:56 - Firmware version change detected, changed to A2pv6C038m.d24j from N/A
18/04/2015 at 00:56 - Software version change detected, changed to V100R001C01B030SP08 from N/A
18/04/2015 at 00:56 - CPU version change detected, changed to BCM6368 from N/A
18/04/2015 at 00:56 - CFE version change detected, changed to 1.0.37-102.6 from N/A
Logged

NewtronStar

  • Kitizen
  • ****
  • Posts: 4838
Re: HG612 Modem Stats - G.INP Graphs
« Reply #13 on: April 18, 2015, 01:31:38 AM »

HG612_modem_stats has crashed 3 times HELP
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 Modem Stats - G.INP Graphs
« Reply #14 on: April 18, 2015, 07:45:53 AM »

HG612_modem_stats has crashed 3 times HELP


If it was HG612_stats.exe itself that crashed, could you post or email me the full details from ONGOING_ERROR.LOG_file_ERROR.TXT.?
Please include a continuous period from a few minutes before it crashed to a few minutes afterward.

If it was only the GUI that crashed, you'd be better asking Ronski in his thread:-

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



« Last Edit: April 18, 2015, 08:00:24 AM by Bald_Eagle1 »
Logged
Pages: [1] 2 3