G.INP off on Huawei cabs now??

It's now been 2 weeks since my migration from Plusnet to BT and G.INP still hasn't been re-enabled despite huge errors on the line - over 500,000 FEC/sec at some times of day.

Has G.INP been turned off on Huawei cabs now too? I hope not as my attainable is 69Mbps but I'm only sync'd at 58Mbps. When it was enabled before, I re-sync'd at 68Mbps ish.

I have G.INP just like many others.

Hmm is it normal then for mine still to have not been turned back on after 2 weeks? I haven't rebooted router for about 10 days - will rebooting help?

I remember when G.INP was enabled last summer, it was only after the power to the house had been off whilst I did some electrical work. When I turned it back on, it was enabled.

Looks like they have stopped tuning G.INP back on if it's been disabled by a DLM reset. This may be until they fix G.INP on ECI cabs.

AIUI at very high error levels G.INP simply isn't effective, as it only reserves a tiny amount of bandwidth to do the retransmission so can't cope at such levels. So DLM just turns it off and relies on good ol' interleaving.

I'd say 500,000 FECs per second is way too high and you have some sort of fault condition. However, I would have rebooted long ago.

Edited by RobertoS (Mon 09-May-16 09:11:08)

What's wrong with it on ECI cabs? It's enabled on mine and working perfectly.

The problem is it's not working perfectly for everyone, so it's being removed on some lines.

I had a BT engineer out last Tuesday (even though I'd cancelled him the day before!) but he couldn't find any fault on the line - he did say it should be faster though as he said the line is just over 200m long!

I wonder why G.INP was on before then? The only difference here is that I changed from Plusnet to BT. This has cost me nearly 10Mbps.

In reply to a post by Icaras:

What's wrong with it on ECI cabs? It's enabled on mine and working perfectly.

Downstream only, so not perfectly.

Well you said your 500,000 FECs/sec is intermittent. If it wasn't happening when he was there he wouldn't hang around waiting for it, would he. Therefore no fault found.

That's 500 per millisecond. Quite apart from any other error types. Keeping your modem busy, and quite hot I expect.