DLM on my line or?

[#1]

The modem doesn't indicate whether G.INP is enabled unless you get information via telnet (command line)  from it...

[#2]

Do i ask for anther reset or am i wasting my time?, i have 6 months left on the contract with plusnet although if i want another 12 cheaper line rental then i renew that in may, the other option is to come out of the contract with whats left and go elsewhere.

[#3]

Quote from: darklight

@mlmclaren i managed to get my laptop connecting to the modem got the web interface on, didn't both changing ip on the modem. Had a look around, but don't know what i'm looking for to see if G.INP is enabled just to make sure.

Use DSLstats v5 it can be found here: http://www.s446074245.websitehome.co.uk/
Download the 32bit Windows v5.4, once downloading extract the .zip folder and then double click dslstats to open the program
Then in the top of the program navigate to configuration, Login and then make sure the IP field is correct (using the one you just assigned the modem), select HG612 from the drop down menu, make sure username and password are both admin unless you changed them.
Then finally make sure that shell command box has "sh" entred in it and that the CLI command prefix is set to xdslcmd..
Once done navigate to stats tab along top of aprogram and then click the green play button in the corner.. all being well the stats will show, Copy and paste this into a post and I will see how your connection is looking..

[#4]

Just got told by PN after a retest that a fail is on the line and that's with nothing plugged in the master socket so it's going back to BT.

[#5]

Quote from: nigel1971

Just got told by PN after a retest that a fail is on the line and that's with nothing plugged in the master socket so it's going back to BT.

Hey nigel, you must have been unlucky that possibly you were hit with G.INP then you had a genuine line fail. Once the line issues are sorted you will have the right firmware/modem to connect with. As a response to your earlier post, even if you moved isp theres a chance the issue would travel with you, so best to chase it with plusnet to get it resolved.

[#6]

I thought as much, I hope Openreach can get this sorted ASAP...

[#7]

Quote from: ericgripp

Hey nigel, you must have been unlucky that possibly you were hit with G.INP then you had a genuine line fail. Once the line issues are sorted you will have the right firmware/modem to connect with. As a response to your earlier post, even if you moved isp theres a chance the issue would travel with you, so best to chase it with plusnet to get it resolved.

Can you please explain why you believe G.INP was actually enabled on this users line and if it was why would it be removed as it is actually a more advance error protection meaning that it would be in affect if the line had issues...
Also the user already has G.INP capable hardware, but seems that they are connected to a non G.INP activated DSLAM (ECI)

[#8]

@mlmclaren what you think, got all the results from my modem here they are, by the looks of it i was right G.INP is enabled.
whats that Interleave depth like is that bad or good?
Stats recorded 10 Apr 2015 10:01:01
DSLAM/MSAN type:         BDCM:0xa44f / v0xa44f
Modem/router firmware:   AnnexA version - A2pv6C038m.d24j
DSL mode:               VDSL2 Profile 17a
Status:                 Showtime
Uptime:                 1 day 22 hours 47 min 3 sec
Resyncs:                 0 (since 10 Apr 2015 10:00:28)

Downstream Upstream
Line attenuation (dB):   9.8 0.0
Signal attenuation (dB): Not monitored
Connection speed (kbps): 79999 20000
SNR margin (dB):         13.9 19.7
Power (dBm):             13.5 5.5
Interleave depth:       16 8
INP:                     46.00 47.00
G.INP:                   Enabled
RSCorr/RS (%):           0.0018 0.0202
RSUnCorr/RS (%):         0.0000 0.0000
ES/hour:                 0 0

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 40924 Kbps, Downstream rate = 109184 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79999 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): 13.9 19.7
Attn(dB): 9.8 0.0
Pwr(dBm): 13.5 -5.5
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 130 97
M: 1 1
T: 0 0
R: 8 8
S: 0.0518 0.1554
L: 21468 5457
D: 16 8
I: 139 106
N: 139 106
Q: 16 8
V: 14 2
RxQueue: 57 39
TxQueue: 19 13
G.INP Framing: 18 18
G.INP lookback: 19 13
RRC bits: 24 24
Bearer 1
MSGc: 186 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 5.3333 16.0000
L: 48 16
D: 3 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: 77238896 3902875
RSCorr: 1248 322
RSUnCorr: 0 0
Bearer 1
OHF: 10490894 46303
OHFErr: 0 0
RS: 125889992 3473546
RSCorr: 0 111
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 17058 212
rtx_c: 403 212
rtx_uc: 0 0
G.INP Counters
LEFTRS: 5 0
minEFTR: 79999 19997
errFreeBits: 205608963 51394863
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 154577821 0
Data Cells: 696828538 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: 25 25
AS: 168513
Bearer 0
INP: 46.00 47.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 80614.82 20102.08
Bearer 1
INP: 4.00 4.00
INPRein: 4.00 4.00
delay: 3 0
PER: 16.06 16.06
OR: 95.62 31.87
AgR: 95.62 31.87
Bitswap: 81464/81464 3355/3355
Total time = 1 days 22 hours 48 min 58 sec
FEC: 1248 322
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 25 25
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 3 min 58 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
Previous 15 minutes time = 15 min 0 sec
FEC: 16 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 = 22 hours 48 min 58 sec
FEC: 507 116
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: 741 206
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 25 25
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 1 days 22 hours 48 min 33 sec
FEC: 1248 322
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#

[#9]

Quote from: darklight

whats that Interleave depth like is that bad or good?

I'm not sure how the Interleaving depths with G.INP work.. they might be the same as before but regardless, my interleave depths are 8 for downstream and upstream (they used to be very low or nothing) but with all the messing with the modem and the line sitting in a fault state for a while when you wasn't compatible with G.INP it might just require DLM to reduce them... I would just leave it connected for a while and it will probably fix itself over time.
Do you have a link to your BQM (if you have one that is)

[#10]

@Darklight Your SNR is stupidly high on both 

[#11]

Yes because he is already at maximum speed and don't require the SNR to be any lower...
The higher the SNR the more stable the connection...
SNR will only be an issue for those who are over 200m from the cabinet and want every bit of speed possible.
As you will see in the stats above... @darklights modem syncs at full speed, and can attain over 100mbps

[#12]

So in the future if and when BT decides to push the limit up i could get above 80Mpbs.
what about the Interleave depth?

[#13]

If BT were to release a 100/30 service on FTTC then you would be able to get it "all remaining well of course"
When BT do the G.Fast rollout you should be capable of around 500mbps "according to some reports" but it's all a case of wait and see.. I wouldn't mind if BT increased the upload from 20 to 25 mbps on my line as it seems capable..
Bare in mind that even though a line might sync at 80mbps you will only get around 77mbps due to overheads, my line syncs at 66mbps but I only see 62-63 throughput on it.
As far as Interleaving goes, you will need to just wait for a while while the DLM settles and it should at some point try to reduce it... unfortunately as G.INP is very new and very few bit of information about to inform about how the profiles work and if Interleaving means anything anymore...
G.INP is supposed to be a new form of error correct that replaces Interleaving... it's supposed to do the same job but have less impact of speeds and latency, which it does seem to do well as Interleaving depth of 8 before G.INP would of surely seen my latency somewhat higher than the 9/10ms it is now.