Interleaving increasing daily and low speeds.

Hi.

I thought I would post my question here as there seem to be a lot of knowledgeable folk around.

Apologies for the poor title. I couldn't think of anything suitable so please feel free to edit it.

I recently had BT infinity installed and I am seeing a few things that concern me. It looks like there is quite a bit of noise on the line according to the HG612 stats, and as a result I am seeing a high level of interleaving applied to the line.

For the first week or so my speed was hovering around 76Mb, and 20Mb upload. The connection itself was functioning completely fine. I did notice on day one that there were quite a few CRC errors appearing. I think it was on day 2 that interleaving was applied to the line, which remains on the line to this day. The level of interleaving seems to have increased a lot since then. The speeds are now a lot less, and the level of interleaving is now at:. Delay: Downstream:9, Upstream:6. D: Downstream: 1723, Upload: 551.

The number of FEC's don't seem to have really reduced though in this time, although interleaving has been increasing progressively.

When the engineer came around recently and plugged in his JDSU, he advised that the max rate that my is was capable of was showing as about 74Mb , and that my actual rate was around 60Mb. This made me wonder, as according to the HG612 stats, the max rate that the line should be capable of is displayed as 93Mb.

1) Is there any reason for the difference between the maximum rate reading on the JDSU compared to the max rate figure on the HG612?

For the first day, the line seemed stable enough with no disconnections (and was fine for daily use anyway); and as I didn't have any additional latency on the line, everything felt a little snappier I think. For the first week or so, the actual speed still remained at about 74/75Mb. It was only the last few days that the speed seems to have also dropped dramatically also.

2) I would much prefer to have a slower downstream speed, and for there to be no interleaving on the line, but this doesn't seem to be possible. It seems that instead, a heavy level of interleaving is being applied by the DLM, coupled with a reduction in line speeds, but with no noticeable difference in the number errors being reported. Is there any chance of DLM noticing that the caps on speeds and interleaving aren't actually reducing the number of errors, and so will relent, and restore original speed with interleaving off?

Also..

3) Does anyone know why there is such a big difference between the max rate figure in the HG612 stats and my actual sync speed. Max rate in HG612 stats: 93564. Actual: 48703. Surely if my line is (theoretically) capable of much higher speeds, shouldn't I be seeing a much higher actual speed than I am?

Hope I have explained myself well enough. The errors don't seem to be coming in ever second, but maybe every so many minutes a whole load of errors will appear. All Openreach line tests come back as OK.

Here are the HG612 stats:

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 2
Max: Upstream rate = 27164 Kbps, Downstream rate = 93564 Kbps
Path: 0, Upstream rate = 14996 Kbps, Downstream rate = 48703 Kbps

Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 13.6 10.9
Attn(dB): 0.0 0.0
Pwr(dBm): 13.6 6.8
VDSL2 framing
Path 0
B: 31 21
M: 1 1
T: 64 64
R: 16 10
S: 0.0209 0.0466
L: 18371 5498
D: 1723 551
I: 48 32
N: 48 32
Counters
Path 0
OHF: 34510549 1275770
OHFErr: 5 0
RS: 2453252362 3087014
RSCorr: 128896 26406
RSUnCorr: 137 0

Path 0
HEC: 26 0
OCD: 0 0
LCD: 0 0
Total Cells: 1127578080 0
Data Cells: 15721732 0
Drop Cells: 0
Bit Errors: 0 0

ES: 7 0
SES: 5 0
UAS: 39 39
AS: 57932

Path 0
INP: 6.00 4.00
PER: 1.67 5.95
delay: 9.00 6.00
OR: 95.68 64.42

Bitswap: 168 49

Total time = 22 hours 30 min 19 sec
FEC: 228061 42165
CRC: 3464 0
ES: 7 0
SES: 5 0
UAS: 39 39
LOS: 5 0
LOF: 5 0
Latest 15 minutes time = 19 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 2987 2
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 22 hours 30 min 19 sec
FEC: 228061 42165
CRC: 3464 0
ES: 7 0
SES: 5 0
UAS: 39 39
LOS: 5 0
LOF: 5 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
Since Link time = 16 hours 5 min 31 sec
FEC: 128896 26406
CRC: 5 0
ES: 1 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
#

Edited by deleted (Fri 14-Jun-13 21:10:21)

Time to turn off as much electrical lit in house and use test socket for modem or at least not have it on an extension.

Fttc can get interference from a different range of kit to adsl so worth trying find out if an issue in home

On will it turn interleave off doubt it.

Hi.

Apologies. I didn't mention the house setup. There are no extensions active in the house, they are all disconnected. The HG612 is connected directly to the master socket. However, I have still tried connecting the HG612 directly to the test socket.

There aren't really many electrical appliances to turn off.

In the living room (where the HG612 is), there is only the sky box, panasonic plasma, blu-ray player, and router. There are no cordless devices, and lighting is also off currently.

Outside the living room, there is really only the fridge and boiler.

Edited by deleted (Fri 14-Jun-13 21:23:39)

Both the Sky box and the plasma TV can be death to it.

In reply to a post by RobertoS:

Both the Sky box and the plasma TV can be death to it.

That's interesting. I will try turning them off tomorrow and see if it makes any difference over 24 hours.

I have monitored the HG612 previously though when the TV has been turned off, and I didn't see any difference, but I haven't tried unplugging the sky box yet.

I have just tried plugging the HG612 into a power socket in a different part of the house, as where the HG612 is normally plugged in is on the same electrical circuit as the burglar alarm (when I flip one of the trip switches in the fuse box the HG612 and the burglar alarm both go off). The different power socket which I have just tried plugging the HG612 into is also situated well away from the plasma TV and the sky box.

This hasn't seemed to make any difference to the frequency of number of errors being reported, in the first 15 minutes anyway.

Since Link time = 14 min 23 sec
FEC: 3498 0
CRC: 0 0
ES: 0 0

Edited by deleted (Fri 14-Jun-13 22:17:56)

Is the burglar alarm connected to the phone line?

In reply to a post by MrSaffron:

Is the burglar alarm connected to the phone line?

No. The BT cable arrives outside the house behind the grey box, and then goes through the wall straight into the master socket. There are no other cables connected there.

I'd check out the Sky box first. Are you moving the HG612 to different rooms?

Edited by RobertoS (Fri 14-Jun-13 22:47:57)

In reply to a post by RobertoS:

I'd check out the Sky box first. Are you moving the HG612 to different rooms?

My wife is watching a film at the moment unfortunately, otherwise I would happily turn the box off.

I actually left the HG612 in the same location and just ran an extension cable from another room which I knew was on a different electrical circuit. I do remember that when we previously had an extension socket in a room upstairs that I would still see a similar number of errors when the HG612 was connected to that socket as well.

There do seem to be a lot of FEC errors appearing in a short amount of time, but they seem to come in large short bursts. Nothing for a few minutes, and then thousands suddenly appear, then nothing from another few minutes or more etc.

Since Link time = 10 min 45 sec
FEC: 2324 555

Since Link time = 15 min 15 sec
FEC: 2324 555
CRC: 0 0

I have reconnected the HG612 to the original power socket again for now, and will leave it turned on and connected for the next week or so. Don't want DLM applying even more interleaving because I'm turning the HG612 on and off too often.

Edited by deleted (Fri 14-Jun-13 23:10:42)