Kitz Forum

Broadband Related => Broadband Technology => Topic started by: Westie on February 12, 2018, 12:37:37 PM

Title: Struggling to understand G.INP
Post by: Westie on February 12, 2018, 12:37:37 PM
On 30th January I migrated from ADSL to a FTTC line, and apart from four days when I went back to using the ISP-supplied router, have been uploading stats to MDWS both before and after the change.

At 02:24 this morning DLM applied G.INP to the downstream line, and Error Seconds dropped from approx 60/day to almost zero. At the same time the upstream Error Seconds, which were at the same rate as the downstream, have doubled. In consequence the total Error Seconds have remained approximately constant, but are now loaded onto only one stream.

Can anyone please explain why the US has been affected this way? It's probably very simple, but I am completely new to this.  :baby:  :(

I am blessed by having a good line anyway, and on 40/10 I am well within its  capabilities. My DS sync rate has increased from 39970 to 39999, and the US has remained constant at 9999, so it might be argued that this is only an academic exercise.

But I just like to know!   :graduate:

Thanks.
Title: Re: Struggling to understand G.INP
Post by: V_R on February 12, 2018, 01:06:21 PM
Your line is wasted on 40/10!

You Attainable has jumped from a 'measly' 119kbps to a 'not bad' 124kbps.  :D
Title: Re: Struggling to understand G.INP
Post by: tubaman on February 12, 2018, 01:26:48 PM
Your line is wasted on 40/10!

You Attainable has jumped from a 'measly' 119kbps to a 'not bad' 124kbps.  :D

I hope that should say 'Mbps'  :lol:

Seriously though, yes it's all going to be pretty academic when the line can easily support well above your contracted rate.
I'm not sure why your US ES has got worse, but it could be no more than it syncing at a slightly lower S/N ratio than you had before.
MDWS should show you this (I really ought to subscribe  :-[).
 :)
Title: Re: Struggling to understand G.INP
Post by: V_R on February 12, 2018, 01:28:19 PM
Gah, yeah sorry. That'll teach me to not type and work at the same time....
Title: Re: Struggling to understand G.INP
Post by: tubaman on February 12, 2018, 02:15:24 PM
Gah, yeah sorry. That'll teach me to not type and work at the same time....

I sympathise - I too can multi-task as long as you accept that output quality will reduce in proportion to the number of tasks I have.  ;D
Title: Re: Struggling to understand G.INP
Post by: renluop on February 12, 2018, 05:05:20 PM
@tubaman
Could be worse! With me it's proportionate to the square of the number of tasks in hand. ;D
Title: Re: Struggling to understand G.INP
Post by: tiffy on February 12, 2018, 05:15:52 PM
@Westie

Yes, your DLM (RDI) re-synch this morning certainly appears to have applied DS G.Inp as indicated on the main MDWS window and by the DS Interleaving & INP parameters, however, the "data to show" pull down menu is not offering the option to display any of the G.Inp associated parameters which is strange ! (check any other MDWS G.Inp'ed user)

Suppose the first thing to establish is if you now have a "G.INP" tab showing on your DSLStats GUI as should be the case with G.Inp active on your line.

Can't offer an opinion on the US ES rate increase which appears to have coincided with your re-synch / DS G.Inp application other than state this certainly did not occur in my case, however, I do have periodic US "bad noise" days, usually only occur on Saturday's or Sunday's, wait and see if the US ES rate increase is permanant.
Title: Re: Struggling to understand G.INP
Post by: tiffy on February 12, 2018, 07:27:19 PM
@Westie

Ref. G.Inp guidance:

You have likely seen this already, but very good general guidance on G.Inp from the kitz/broadband area:
http://www.kitz.co.uk/adsl/retransmission.htm

Another area which I did not initially find until directed by a forum member:
http://www.kitz.co.uk/adsl/linestats_errors.htm

Gives very good explanations of the G.Inp specific stat's parameters (last paragraph)

Not a definitive answer to your question on increase of US ES rate post G.Inp as such but good general information, I'am sure some of the more knowledgable forum members will be able to offer informed guidance on your original question.

Title: Re: Struggling to understand G.INP
Post by: tiffy on February 12, 2018, 07:50:31 PM
@Westie

Don't know if you have done anything, re-started DSLStats, re-booted your RPi but you are now fully indicating all G.Inp parameters on MDWS "data options" pull down menu, definately not the case this afternoon, I did check a number of times after reading your post.

You also appear to be on retx low profile which is good, approx 97% data throughput ratio as opposed to approx 91% with retx high profile, low profile would certainly be expected on your line.

Edit: Ref to "data options" should be "data to show" pull down menu.
Title: Re: Struggling to understand G.INP
Post by: burakkucat on February 12, 2018, 09:07:28 PM
Don't know if you have done anything, re-started DSLStats, re-booted your RPi but you are now fully indicating all G.Inp parameters on MDWS "data options" pull down menu, definately not the case this afternoon, I did check a number of times after reading your post.

I suspect that the sudden appearance of the data was due to Tony fixing a "mishap" with the MDWS server (http://forum.kitz.co.uk/index.php/topic,14361.msg365020.html#msg365020).  ;)
Title: Re: Struggling to understand G.INP
Post by: kitz on February 12, 2018, 11:39:26 PM
I'd be tempted to give that line a full power down for a short while.

There's some sort of weird jitter.  Look at the downstream SNR/Tone and break down of US Bands. 
May not cure it, but its not unknown on the odd occasion for a line to freak out a bit after a remote resync or power outage.   
Title: Re: Struggling to understand G.INP
Post by: Westie on February 12, 2018, 11:52:51 PM
Thanks for all the comments, folks...

@kitz

Following your suggestion, I'll power off for 30 min and see what happens when I come back on.

Bye for now...
Title: Re: Struggling to understand G.INP
Post by: Westie on February 13, 2018, 08:27:53 AM
I'd be tempted to give that line a full power down for a short while.

Well that worked!  :thumbs: :yay:

Quote
There's some sort of weird jitter.  Look at the downstream SNR/Tone and break down of US Bands.

Hmmm. I noticed that saw-tooth pattern ever since I went FTTC. I have no idea what causes it, but it doesn't seem to consistently affect anything else.

The only other thing that may have been having an effect is a SamKnows Whitebox. I've had one on the line for some years, but it has intermittently and persistently failed to connect properly with this router on FTTC (although it was OK on ADSL). Yesterday I finally decided to switch it off, which I did at about 17:30. Last night's power cycle was the first since G.INP without the Whitebox.

I'm tempted to try the Whitebox again...but not for at least a week!

Thanks everyone for your help. I still don't understand fully what was happening, but "freak out a bit" will suffice for now.  ;D
Title: Re: Struggling to understand G.INP
Post by: Westie on February 15, 2018, 09:59:36 AM
DLM intervened again at 05:10...though I wasn't awake to see it!
Now I have G.INP on both downstream & upstream, and sync at a full 40/10  :yay:

All good things come to those who wait......
Title: Re: Struggling to understand G.INP
Post by: skyeci on February 15, 2018, 10:17:10 AM
very nice. vectoring and g.inp... love the 32.3 snr on the ds... I should imagine your line would go a lot faster than 40/10
Title: Re: Struggling to understand G.INP
Post by: kitz on February 15, 2018, 03:44:03 PM
 :yay:
Title: Re: Struggling to understand G.INP
Post by: Ronski on February 15, 2018, 04:57:32 PM
very nice. vectoring and g.inp... love the 32.3 snr on the ds... I should imagine your line would go a lot faster than 40/10

It certainly would, it has an attainable of 122859Kbps down and 36369kbps up, seems wasted on a 40/10 package  ;) It'd be wasted on a 80/20 package as well, but there is no higher on OR's FTTC network.
Title: Re: Struggling to understand G.INP
Post by: V_R on February 15, 2018, 06:39:36 PM
Thats what I said in the second post, I'd kill for a line like that.  :D