G.INP

[#1]

Found this interesting article, especially the last sentence (today's update).
http://www.ispreview.co.uk/index.php/2015/04/bt-openreach-briefs-uk-fttc-fibre-broadband-isps-on-g-i...

[#2]

no mention of how long the trial will run for, hopefully not to long and something good will come from it so they get to the ECI roll out itself.   

[#3]

Quote from: 11110_110

if this thread is a gold-fish bowl or a little bitch contest

Best post I've seen in this thread. 

[#4]

Quote from: tijara33

Quote this is a weakish argument. No it isn't....................it's a FACT!!

no its pure speculation, you are speculating that if many people are unhappy they would all be posting on the forums, pure speculation.
do you work for the press? as the press love to print speculation as fact.

[#5]

Quote from: npr

Quote from: 11110_110 if this thread is a gold-fish bowl or a little bitch contest Best post I've seen in this thread.

  *giggle*

[tt]
      /^-^\        /^-----^\
      / o o \        V  o o  V
    /  Y  \        |  Y  |
    V \ v / V        \ Q /
      / - \          / - \
      /    |          |    \
(    /    |          |    \    )
===/___) ||          || (___\====
[/tt]
                               

[#6]

Quote from: chrcoluk

no its pure speculation, you are speculating that if many people are unhappy they would all be posting on the forums, pure speculation.

It's not a major issue - otherwise all the large ISPs would be making some kind of service statement. Similarly, the mainstream media would be reporting the issue, if it was seriously impacting the majority of internet users in the UK.
I would be surprised if 10% of FTTC users even know whether they are on Huawei or ECI kit (or even what that means).

[#7]

I'm effected by both this (at least I was until I switch to a different modem, as I did have a BT Home Hub 5A) and the Manchester issue.  The wife is online much more than me at home and doesn't have a clue that there is an issue.  Everything she needs is working ok for her.

[#8]

Quote

I would be surprised if 10% of FTTC users even know whether they are on Huawei or ECI kit (or even what that means).

I was until someone on here enlightened me but that doesn't take away the fact ive got a ECI modem and im on a Huawei Cabinet, and i want to know when BTO are going to upgrade the firmware because i don't see why i have to pay for a different Modem/Router just to get the best out of my Connection.

[#9]

Just about to change over so I’ve put a little info together.




[tt]
==============DNS Response times various========================
Nameserver          Response Time (ms)
                    min/avg/max/stdev/retries
192.168.0.12        1.28/1.35/1.50/0.09/0
192.168.0.15        1.96/2.01/2.06/0.04/0
212.118.241.1      11.36/12.04/12.44/0.37/0
212.118.241.33      11.20/11.46/11.78/0.24/0
83.170.64.2        11.24/11.58/11.98/0.29/0
195.12.4.247        11.81/12.16/12.55/0.26/0
212.159.13.50      15.10/15.48/15.90/0.31/0
192.168.0.254      16.40/16.58/16.87/0.19/0
8.8.8.8            11.62/11.99/12.29/0.23/0
8.8.4.4            11.66/12.21/12.70/0.36/0
4.2.2.1            11.21/11.95/12.35/0.43/0
4.2.2.6            11.95/12.27/12.52/0.22/0
208.67.222.220      11.20/11.60/11.96/0.29/0
208.67.222.222      11.46/11.78/12.14/0.26/0

==============Ping Response times bbc.co.uk======================
                                    Packets              Pings
Host                                Loss%  Snt  Last  Avg  Best  Wrst StDev
1. 192.168.0.254                    0.0%  100    1.0  1.0  0.9  1.2  0.0
2. 195.166.130.164                  0.0%  100  10.5  12.0  9.7  33.8  4.7
3. 84.93.249.81                      0.0%  100  10.4  11.5  9.5  59.6  5.7
4. 195.166.129.0                    0.0%  100  10.9  11.6  10.0  51.0  4.7
5. 212.58.239.6                      0.0%  100  10.8  10.8  9.7  15.4  0.8
6.
7.
8. 132.185.254.109                  0.0%    99  12.8  11.6  10.3  21.6  1.6
9. 132.185.255.149                  0.0%    99  11.2  11.8  10.7  15.1  0.7
10. 212.58.244.20                    0.0%    99  10.1  10.7  10.1  12.0  0.4

===================Modem Profile================================
xdslcmd configure --phyReXmt 3

Stats recorded 28 Apr 2015 09:50:18
DSLAM/MSAN type:        BDCM:0xa41b / v0xa41b
Modem/router firmware:  AnnexA version - A2pv6C038m.d24j
DSL mode:              VDSL2 Profile 17a
Status:                Showtime
Uptime:                1 day 22 hours 1 min 23 sec
Resyncs:                0 (since 28 Apr 2015 09:50:14)

Downstream Upstream
Line attenuation (dB):  24.5 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 43999 6832
SNR margin (dB):        7.7 6.3
Power (dBm):            11.2 1.4
Interleave depth:      16 4
INP:                    47.00 43.00
G.INP:                  Enabled
RSCorr/RS (%):          0.0098 1.3218
RSUnCorr/RS (%):        0.0000 0.0000
ES/hour:                0 0[/tt]

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason:	0
Last initialization procedure status:	0
Max:	Upstream rate = 7037 Kbps, Downstream rate = 47692 Kbps
Bearer:	0, Upstream rate = 6832 Kbps, Downstream rate = 43999 Kbps
Bearer:	1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State:	L0
Mode:			VDSL2 Annex B
VDSL2 Profile:		Profile 17a
TPS-TC:			PTM Mode(0x0)
Trellis:		U:ON /D:ON
Line Status:		No Defect
Training Status:	Showtime
		Down		Up
SNR (dB):	 7.7		 6.3
Attn(dB):	 24.5		 0.0
Pwr(dBm):	 11.2		 1.4
			VDSL2 framing
			Bearer 0
MSGc:		-6		-6
B:		150		211
M:		1		1
T:		0		0
R:		8		10
S:		0.1089		0.9856
L:		11681		1802
D:		16		4
I:		159		222
N:		159		222
Q:		16		4
V:		9		1
RxQueue:		28		12
TxQueue:		14		6
G.INP Framing:		18		18
G.INP lookback:		14		6
RRC bits:		24		24
			Bearer 1
MSGc:		90		58
B:		0		0
M:		2		2
T:		2		2
R:		16		16
S:		10.6667		16.0000
L:		24		16
D:		1		1
I:		32		32
N:		32		32
Q:		0		0
V:		0		0
RxQueue:		0		0
TxQueue:		0		0
G.INP Framing:		0		0
G.INP lookback:		0		0
RRC bits:		0		0
			Counters
			Bearer 0
OHF:		0		0
OHFErr:		0		0
RS:		1775935088		3300798
RSCorr:		173859		30756
RSUnCorr:	0		0
			Bearer 1
OHF:		10329587		933006
OHFErr:		0		2
RS:		61977152		2826054
RSCorr:		34		100
RSUnCorr:	0		0
			Retransmit Counters
rtx_tx:		50777		8129
rtx_c:		41005		8853
rtx_uc:		2744		188
			G.INP Counters
LEFTRS:		653		572
minEFTR:	43998		6827
errFreeBits:	134417208		370046168
			Bearer 0
HEC:		0		0
OCD:		0		0
LCD:		0		0
Total Cells:	1154038671		0
Data Cells:	355828917		0
Drop Cells:	0
Bit Errors:	0		0
			Bearer 1
HEC:		0		0
OCD:		0		0
LCD:		0		0
Total Cells:	0		0
Data Cells:	0		0
Drop Cells:	0
Bit Errors:	0		0
ES:		35		11
SES:		1		0
UAS:		126		126
AS:		165924
			Bearer 0
INP:		47.00		43.00
INPRein:	0.00		0.00
delay:		0		0
PER:		0.00		0.00
OR:		0.01		0.01
AgR:		44200.44	6856.53
			Bearer 1
INP:		2.50		4.00
INPRein:	2.50		4.00
delay:		0		0
PER:		16.06		16.06
OR:		47.81		31.87
AgR:		47.81	31.87
Bitswap:	106982/106982		1095/1095
Total time = 1 days 20 hours 25 min 14 sec
FEC:		2463533		331507
CRC:		97		27
ES:		35		11
SES:		1		0
UAS:		126		126
LOS:		0		0
LOF:		0		0
LOM:		0		0
Latest 15 minutes time = 10 min 14 sec
FEC:		27		0
CRC:		0		0
ES:		0		0
SES:		0		0
UAS:		0		0
LOS:		0		0
LOF:		0		0
LOM:		0		0
Previous 15 minutes time = 15 min 0 sec
FEC:		184		4
CRC:		0		0
ES:		0		0
SES:		0		0
UAS:		0		0
LOS:		0		0
LOF:		0		0
LOM:		0		0
Latest 1 day time = 20 hours 25 min 14 sec
FEC:		45722		13203
CRC:		0		0
ES:		0		0
SES:		0		0
UAS:		0		0
LOS:		0		0
LOF:		0		0
LOM:		0		0
Previous 1 day time = 24 hours 0 sec
FEC:		127265		17547
CRC:		0		0
ES:		0		0
SES:		0		0
UAS:		0		0
LOS:		0		0
LOF:		0		0
LOM:		0		0
Since Link time = 1 days 22 hours 5 min 23 sec
FEC:		173859		30756
CRC:		0		0
ES:		0		0
SES:		0		0
UAS:		0		0
LOS:		0		0
LOF:		0		0
LOM:		0		0
# 

[#10]

That's a good note to continue on.
Everyone in fact agrees that the end of the world is not nigh, I do believe.
That isn't the crux of the matter.
Let's keep it to the tech.

[#11]

Now Running ECI.
I’ll look again tomorrow, same tests.



[tt]
Nameserver           Response Time (ms)
                    min/avg/max/stdev/retries
192.168.0.12         1.30/1.35/1.49/0.07/0
192.168.0.15         1.95/2.02/2.11/0.07/0
212.118.241.1       17.29/17.69/18.08/0.28/0
212.118.241.33       17.35/17.90/18.26/0.31/0
83.170.64.2         17.03/17.33/17.70/0.25/0
195.12.4.247         17.51/17.58/17.69/0.07/0
212.159.13.50       20.39/20.87/21.26/0.34/0
192.168.0.254       21.19/22.83/28.15/2.66/0
8.8.8.8             17.23/17.57/18.09/0.31/0
8.8.4.4             17.20/17.61/17.86/0.25/0
4.2.2.1             17.63/18.56/21.29/1.37/0
4.2.2.6             17.67/18.15/18.60/0.31/0
208.67.222.220       16.94/17.41/17.70/0.26/0
208.67.222.222       16.91/17.17/17.65/0.27/0
                                    Packets               Pings
Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
1. 192.168.0.254                     0.0%   104    1.0   1.0   0.9   1.3   0.0
2. 195.166.128.187                   0.0%   104   17.0  19.6  16.0  75.9   7.9
3. 212.159.2.182                     0.0%   104   16.1  17.1  15.7  59.0   4.6
4. 212.159.0.214                     0.0%   104   16.4  17.9  15.7  57.9   6.6
5. 195.166.129.2                     0.0%   104   17.1  19.5  16.1  67.6   7.9
6. 195.166.129.4                     0.0%   104   56.5  18.2  15.8  56.5   6.9
7. 212.58.239.6                      0.0%   104   16.7  16.6  15.8  21.1   0.7
8.
9.
10. 132.185.254.109                   0.0%   104   17.2  17.2  16.2  24.8   1.5
11. 132.185.255.149                   0.0%   104   17.2  17.5  16.7  22.9   0.7
12. 212.58.244.20                     0.0%   103   16.7  16.5  15.8  17.1   0.3
[/tt]
Edit: I'm on a 40/20 Profile.
I gained 2mbps in upload after G.INP was enabled, I think it's too early to tell as yet, lets see what happens over the next few days.
What I expect to happen is my Downstream to move to around 35.5mbps and for my jitter to decrease.

[#12]

So, in very simple terms, business as usual except (very roughly) ~7ms increase on pings suggesting interleaving in one direction.
Sorry, upload seems to have reduced a little.
Are you on 40/20 @11110_110?  That could 'mask' any change in sync as you were previously over 40Mb/s.
[Edit1] added 40/20 question.
[Edit2] noted slight reduction in measured upload

[#13]

ofcom's reply to me might make it a major issue to the accountants.
In their opinion if this was rolled out to ECI cabs and gave a 8/16ms jump in latency, then all end users can exit their contract penalty free.
I have asked for it in writing, when it comes I can scan it.
The way andyh seems to think a company can change anything and as long as the customer doesnt notice its all ok.

[#14]

Quote from: w23

So, in very simple terms, business as usual except (very roughly) ~7ms increase on pings suggesting interleaving in one direction. Are you on 40/20 @11110_110?  That could 'mask' any change in sync as you were previously over 40Mb/s

I get a marked reduction in sync speed in addition, which is indeed masked by the 40/20 product cap in my case, but is shown in the BT IP profile.

[#15]

I just want to say a thank you for the information in this thread about the Huawei cabinet/ECI Modem issue after G.INP implementation.
My line had dropped from a solid 73Mb/s 9ms Download speed (77Mb/s on the Plusnet site) to 63MB/s 15ms (65Mb/s on the Plusnet site) a few months ago. I put it down to crosstalk at the time, but was somewhat peeved.
After checking the forum recently and reading this thread I decided check my cabinet vendor and then to obtain a Huawei HG612 modem. I install the B030SP08 unlocked firmware and waited.
Nothing changed for 3 days, but I noticed on the 3rd day that the Plusnet site had upped back to 77Mb/s and I disconnected and reconnected at the router.
I am now back to where I was with a 73Mb/s 8ms Download speed.