Warning...FTTC newbie.
I've spent some time reading up about this and my conclusion is that G.INP should have kicked in for me by now. My service started on 12 June, used my own router and ECI modem until 29 June, when I swapped it out for an unlocked Huawei HG612.
I have both an ECI and a Huawei cabinet on my road across from the PCP cabinet, and my DSLstats say I'm connected to the Huawei cabinet. Line attenuation has always been 14.9 and SNR between 6.1 and 6.3. No noise on the telephone line and broadband is working fine, however I've never gone over 66 Mbps (occasional bursts during a speed test...and yes I know this is within the quoted range for Fibre 2).
As you can see from my stats G.INP is not enabled and my question is, will it ever? I thought the whole point of DLM and G.INP was having a stable line and then slowly upping the speed.
Am I banded...or just not getting the whole point of DLM/G.INP?
Any thoughts appreciated.
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 28321 Kbps, Downstream rate = 79992 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 69284 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.2 15.3
Attn(dB): 14.9 0.0
Pwr(dBm): 13.8 6.5
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 51 237
M: 1 1
T: 64 42
R: 12 16
S: 0.0239 0.3781
L: 21440 5374
😧 1355 1
I: 64 127
N: 64 254
Counters
Bearer 0
OHF: 567522581 3808047
OHFErr: 157 49
RS: 3551694781 2396363
RSCorr: 683066 712
RSUnCorr: 7233 0
Bearer 0
HEC: 1772 0
OCD: 46 0
LCD: 46 0
Total Cells: 46064027 0
Data Cells: 2025493224 0
Drop Cells: 0
Bit Errors: 0 0
ES: 35 48
SES: 0 0
UAS: 26 26
AS: 870752
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.53 3.98
OR: 125.13 64.22
AgR: 69408.87 20063.54
Bitswap: 509166/509166 134/134
Total time = 1 days 1 hours 52 min 58 sec
FEC: 683066 712
CRC: 157 49
ES: 35 48
SES: 0 0
UAS: 26 26
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 7 min 58 sec
FEC: 746 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: 1285 1
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 hours 52 min 58 sec
FEC: 7210 2
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: 47242 52
CRC: 23 4
ES: 2 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 10 days 1 hours 52 min 31 sec
FEC: 683066 712
CRC: 157 49
ES: 35 48
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
There's still time for G.INP to kick in.
I have a similar setup where the ECI cab is the initial cab and then expanded with a Huawei cab but not sure how you can tell that you are connected to Huawei cab as dslchecker only shows cab number and both cabs ave same number. If you are assuming Huawei because of when connected then then that is not necessarily correct as you could be connected to a line given up on the ECI cab. The ECI cabs from a recent openreach publication in ISP REVIEW are getting G.INP rolled out but no dates given
It might also possibly depend which version of the unlocked software you have installed on the HG612.
There's SP08 & SP10 being the common ones but it's only SP08 that has the patch for G.INP.
Yep, SP08 firmware (web GUI version) and assuming connected to Huawei cabinet as DSLstats say "DSLAM type / SW version: BDCM:0xa49a (164.154) / v0xa49a", where apparently BCDM is Broadcom = Huawei (at least according to Kitz_co_uk).
Thanks all, I guess I need to give it more time then.
Thought I'd share as made me laugh....
Only ten months in and G.INP finally kicked in, not that I've noticed any difference in download speed, even though connection speed jumped from 69 to 79 (below), it remains steady at 65-ish.
Who knows, in another 10 months it could turn into FTTP 😂
If G.INP was active (though enabled) your downstream SNR would be expected at about 3dB.
Of course G.INP has been activated, in this case in place of interleaving, thus his bump in sync speed and can be seen on the router stats (interleave depth as well as the GINP Enabled on the downstream status).
Sub 6dB SNR targeting only usually starts 2 - 3 days after G.INP is activated, and only if required to achieve higher sync speeds. As the OP is so close to target with just GINP active this may never happen.
Also, the most the OP will see DLM change his target SNR to 5dB which based on the current stats will see an actual SNR of 5.9 - 6.1 with an 80,000 sync and it's probably worth pointing out that this will actually reduce throughput as the sub 6dB profiles DLM applies adds Re-Tx High which will reduce the IP profile of the line and can sometimes persist.
Ipswitch, regarding the lack of change in your speed tests, it could be worth powering down the router for 5 - 10 mins and then powering back up as sometimes the ip profile can get stuck.