G.INP affecting certain eci modems,resulting in a drop in sync rate and other issues

[MarkG33]

My understanding is they disable the upstream transmission of G.INP and enable fastpath again.
I noticed changes on the 10th May. And this has been consistent on both my HH5A and ECI modem. I still want to try out the .11 update for the HH5A. I'm curious to see how it performs by itself with the update. 😄
Mark.

[GeekOfBroadband]

How to Fix the ECI modem with G.INP!

Step 1: Place modem on a solid base.           http://prntscr.com/7eid9w

Step 2: Hammer 8 nails in the top.            http://prntscr.com/7eidx3

Step 3: Write with a highlighter G.INP on the front.     http://prntscr.com/7eiedw

Step 4: Take a saw and cut half way down the modem.      http://prntscr.com/7eieiq

Step 5: Take a hammer a smash the top until the lid comes apart.       http://prntscr.com/7eiey6

Step 6: Completely remove the lid so you can see the chipset.       http://prntscr.com/7eif9l

Final Step Optional. Recycle.      http://prntscr.com/7eig53

[ewanb75]

Roflmao Geek, haha.  

That is roughly how I am feeling, but I think I would have added fire into themix.. 😉

[fingerbob69]

@GeekOfBroadband

That is just too funny.

@BT When people feel moved to this sort of (v.funny) posting then you know your reputation is taking a pasting on the issue.

[McGrath1982]

I'm in stitches reading them 😂😂



-------------------------------
Sent from my iPhone 6

[Barry57]

Hehe

What was the eci/r replaced with ?

A fancy all in one or back on the unlocked hg612 3b GeekOfBroadband ?

[GeekOfBroadband]

Probably a Billion 8800AXL 

[N0STIE]

Is ECI modem affected with HH5 Type B? I am on ECI cab, actually getting max speed my line supports but high ping though. Is it worth to give ECI modem a go?

[burnside]

The HH5 Version B has a G.inp compatible chipset (broadcom) so would work fine, in fact they did work fine as did the Huawie HG 612 modems with the latest firmware if you were on a huawei FTTC cab until they rolled out the  so called "fix"

Which was in fact no more than a botch up, they simply disabled G.inp on the upstream so the upstream is now fast path with FEC

 they did this so those who where supplied with an incompatible  device by BT ie HH5 version A and the ECI modem would see an improvement to latency, but due to the increased FEC (foward error correction) overheads on the upstream many are not seeing their previous upstream sync rates re appear again, So a fail by BT

What they should of done is recall all the incompatible devices that they supplied  and replaced them with compatible ones

As for those on ECI FTTC cabs G.inp has so far not been rolled out on those , as those too are incompatible with G.inp

This is an issue due to incompetance why wasn't this picked up during testing of the HH5 vA and ECI modems? The so called experts surely would have know they wouldnt work properly with G.inp  and my bet would be they wouldn't be vector compatible either

[x5gb]

I thought the update was only been uploaded to lines which are affected not the whole network in which case it shouldn't affect people who were using HH5B and HG612 modems. Is this not the case as that would be a right **bleep** up on Openreach's part.