Need opinion on line stats after G.INP enabled

A few days ago G.INP was enabled on my cabinet. Just wanted to see what you guys think.

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 14216 Kbps, Downstream rate = 63592 Kbps
Bearer: 0, Upstream rate = 14216 Kbps, Downstream rate = 63973 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): 6.3 6.3
Attn(dB): 20.9 0.0
Pwr(dBm): 12.6 7.6
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 62
R: 10 16
S: 0.1215 0.5325
L: 16731 3816
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 51 0
TxQueue: 17 0
G.INP Framing: 18 0
G.INP lookback: 17 0
RRC bits: 0 24
Bearer 1
MSGc: 154 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 6.4000 0.0000
L: 40 0
D: 3 0
I: 32 0
N: 32 0
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 6918
OHFErr: 0 0
RS: 1869992 428690
RSCorr: 0 0
RSUnCorr: 0 0
Bearer 1
OHF: 3610 0
OHFErr: 0 0
RS: 35486 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 7507 0
rtx_c: 0 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 0 0
minEFTR: 63970 0
errFreeBits: 56593 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 7102797 0
Data Cells: 118 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: 0 0
SES: 0 0
UAS: 26 26
AS: 59

Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 8.28
OR: 0.01 30.89
AgR: 64039.04 14246.83

Bearer 1
INP: 4.50 0.00
INPRein: 4.50 0.00
delay: 3 0
PER: 16.06 0.01
OR: 79.68 0.01
AgR: 79.68 0.01

Bitswap: 0/0 1/1

Total time = 1 min 25 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 1 min 25 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 0 sec
FEC: 0 0
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 = 1 min 25 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 57 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#

Have you got a copy of your stats before G.INP for comparison?

I do. This was from around a couple of days before G.INP was activated as far as I can tell.

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 14447 Kbps, Downstream rate = 59424 Kbps
Bearer: 0, Upstream rate = 14223 Kbps, Downstream rate = 60532 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): 5.8 6.5
Attn(dB): 20.8 0.0
Pwr(dBm): 12.3 7.6
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 239 237
M: 1 1
T: 64 62
R: 0 16
S: 0.1262 0.5322
L: 15216 3818
D: 1 1
I: 240 127
N: 240 254
Counters
Bearer 0
OHF: 471294384 1905987
OHFErr: 39705 810
RS: 0 1746101
RSCorr: 0 11352
RSUnCorr: 0 0

Bearer 0
HEC: 105158 0
OCD: 3564 0
LCD: 3564 0
Total Cells: 3763593395 0
Data Cells: 1928605206 0
Drop Cells: 0
Bit Errors: 0 0

ES: 13255 739
SES: 24 0
UAS: 26 26
AS: 955241

Bearer 0
INP: 0.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 2.02 8.28
OR: 94.72 30.91
AgR: 60627.17 14254.30

Bitswap: 703335/703335 2854/2854

Total time = 1 days 1 hours 21 min 7 sec
FEC: 0 11352
CRC: 39705 810
ES: 13255 739
SES: 24 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 6 min 7 sec
FEC: 0 1
CRC: 4 0
ES: 3 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: 0 2
CRC: 4 1
ES: 4 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 1 hours 21 min 7 sec
FEC: 0 6
CRC: 38 1
ES: 29 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 0 523
CRC: 1723 62
ES: 1008 60
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 11 days 1 hours 20 min 41 sec
FEC: 0 11352
CRC: 39705 810
ES: 13255 739
SES: 24 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#

Looks pretty good to me then!
What router/modem are you using?

I'm on a BTOR supplied ECI modem (so no line stats) and my line has only slowed over the last year...

Have an OR supplied ECI modem as well but given it was easier to unlock the Huawei HG612. I bought a revision 3B model off a certain auction site and followed some easily found instructions to flash some G.INP compatible firmware that allows me to monitor the stats as well. Router is a DLink 868L.

Thanks. I'm starting to think my ECI modem isn't helping me!
When funds allow (I've been saying that for a while now!) I'm going to buy a Billion 8800nl to see how that behaves.

That's so true if you're on a Huawei cabinet, the ECI modem doesn't support G.Inp

On that note does anyone know of an easy way to unlock an ECI modem that isn't reliant on drilling and soldering? I have the "/r" variant of said modem.

You can perhaps avoid the soldering with a judiciously placed clothes-peg, but drilling is generally required. Not worth the effort really.

I don't think the clothes peg method works on the /r variant due to a more awkward placement of the UART terminals. But would be interested in unlocking an ECI if an easier method is discovered.

Why not get an HG612 for a few quid?

This « Reply #38 on: August 15, 2015, 01:13:27 PM » sounds like it works without soldering http://forum.kitz.co.uk/index.php/topic,15918.msg296...

That's what I though, easier and with a better result.

See the opening post of the Kitz thread, the insert titled "Quote". That seems to refer back to the soldering stuff.

This thread has got tangled.

B4dger has the ECI. The OP has one but is currently using an unlocked HG612.

That and I was just wondering out of curiosity how to unlock an ECI if I had to resort to using one for whatever reason.

Edited by ciday (Sun 11-Oct-15 04:02:10)

I think you need to get access to the circuit board to unlock the ECI. The best way to do this involves drilling the case. You then have to connect to the serial port, again the best way to do this involves drilling and soldering some header pins, although it is possible to hold the header pins in place.

The kitz link above is about flashing replacement firmware into an ECI that has already been unlocked. The "Quote" section I referred to, in the opening post of that thread, contains a link to how to unlock the ECI.

In reply to a post by BatBoy:

That's so true if you're on a Huawei cabinet, the ECI modem doesn't support G.Inp

I didn't realise that - I thought a firmware update (automatically via BT) then this modem was good to go... That explains that!
You would think/hope "BT" would make all their kit compatible...

You would, but instead they bullied Openreach into degrading G.INP to support their broken modems.

?
It's an Openreach modem that's broken, nothing to do with BT Consumer.

Edit - Though the HH 5A is bust as well. That will be because Openreach were asleep at the wheel and didn't spot the problem.

Edited by RobertoS (Sun 11-Oct-15 19:21:17)

Well, the ECI modems should only have been handed out to customers on ECI cabs. The HH5A similarly should only have gone to ECI cabs. However, that didn't happen and BT coerced Openreach into downgrading G.INP rather than replacing the devices that were impacted by Huawei cabs.

You reckon?

It's a possibility, but is it a known fact?