I've noticed that in the past but not really been able to put my finger on what could be causing it. I might have to get my thinking cap back on and try to find out. Not that I've much chance of being able to do anything about it mind.

I've known for ages that my line is underperforming. It is only 275m long according to OR Engineer's hand held tool but attenuation is always between 19 and 19.2.

IF and it is a big IF, you could sort out why the FECs drop to near zero in the evening you would probably find that G.INP is not invoked and you would see the higher speeds continually.


As for distance, yes, 275m and 19dB attenuation is a little odd. At 400-450m I see 16dB and would expect you to be down at 10-12dB. It could possibly be that the copper feeding you is smaller diameter that standard - BT has used different sizes in the past.

In reply to a post by WelshWArrior:

.... It is only 275m long according to OR Engineer's hand held tool but attenuation is always between 19 and 19.2.

My line is 272m long according to BT engineer and attenuation as measured by my Billion 8800NL is about 17.4dB for some sort of comparison with your figure. According to the OR engineer, some of my line is aluminium (where it goes underground for about 10m). Do you happen to know if some or all of your line is also aluminium? That may account for extra 1.6 to 1.8dB attenuation?

Update on this:

Ran BT speedtest and was prompted to complete TAP3 which failed miserably. Online chat with BT who initially said nothing wrong. I then asked him to check my TAB3 test result which then prompted him to do more tests, confirming 'network issue'. He then raised the fault.

10 mins later, sync drops and immediately reconnects. Attainable is now 70Mbps but actual sync rate is still only 57Mbps i.e hasn't moved. I now notice though that G.INP is now back on.

Is my throughput likely to return to pre-migration levels? Considering I'm now sync'd at 70Mbps (albeit with 220602 FECs a minute!!) I'm hoping so. Guess I'll just have to wait and see what OR engineer finds out.

Edited by WelshWArrior (Tue 26-Apr-16 15:54:49)

Current stats showing the hideous amount of errors latency is also rubbish, averaging 60ms at moment:

adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 17443 Kbps, Downstream rate = 68209 Kbps
Bearer: 0, Upstream rate = 17443 Kbps, Downstream rate = 57676 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 6.3
Attn(dB): 19.2 0.0
Pwr(dBm): 12.7 7.5

VDSL2 framing
Bearer 0
MSGc: 18 20
B: 51 237
M: 1 1
T: 64 64
R: 12 16
S: 0.0287 0.4342
L: 17848 4680
D: 1129 1
I: 64 127
N: 64 254

Counters
Bearer 0
OHF: 10745906 436581
OHFErr: 73 11
RS: 2750814320 2095667
RSCorr: 35931786 35
RSUnCorr: 112 0

Bearer 0
HEC: 20 0
OCD: 0 0
LCD: 0 0
Total Cells: 2196793356 0
Data Cells: 46465947 0
Drop Cells: 0
Bit Errors: 0 0

ES: 16 11
SES: 0 0
UAS: 32 32
AS: 19809

Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.84 6.97
OR: 104.17 29.82
AgR: 57780.29 17472.53

Bitswap: 4782/4782 25/25

Total time = 5 hours 30 min 41 sec
FEC: 35931786 35
CRC: 73 11
ES: 16 11
SES: 0 0
UAS: 32 32
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 41 sec
FEC: 6779 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: 199435 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 = 5 hours 30 min 41 sec
FEC: 35931786 35
CRC: 73 11
ES: 16 11
SES: 0 0
UAS: 32 32
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 = 5 hours 30 min 9 sec
FEC: 35931786 35
CRC: 73 11
ES: 16 11
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
>

It will be better when G.INP is enabled

G.INP is enabled. It got enabled about 10 mins after I rang them today. The sync dropped and reconnected along with G.INP being enabled. This is confirmed if you look at mydslwebstats. I am tenbyboy2

Have a look. It says " G.INP is inactive on this line (has been enabled but is currently turned off)"

I meant ON

I was going to say - an interleaving depth of 1129, and so many FEC errors doesn't look at all like G.INP being active.

Does whatever router he is using show Bearer 1 when active?

Yeah, the Billion 8800 NL does indeed.