Interpreting HG612 stats return via a telnet session

I have just received my unlocked HG612 in the post and have connected it up to my Netgear router and turned off the BT Home Hub 5 as it consistently rebooting all the time.

I have run the following commands in a telnet session to see what sync speed etc I'm getting with the HG612.

Just wondering if anyone can help me understand them, i.e. with regards to DLM and interleaving.

# xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 6831 Kbps, Downstream rate = 37164 Kbps
Path: 0, Upstream rate = 6874 Kbps, Downstream rate = 24999 Kbps

Discovery Phase (Initial) Band Plan
US: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3971)
Medley Phase (Final) Band Plan
US: (0,95) (868,1207)
DS: (32,859) (1216,1963)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 6831 kbps 37164 kbps
Actual Aggregate Tx Power: 4.2 dBm 12.0 dBm
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 8.4 47.1 N/A N/A 20.1 57.5 86.8

Signal Attenuation(dB): 8.4 46.5 N/A N/A 20.1 57.5 N/A

SNR Margin(dB): 6.2 6.1 N/A N/A 9.4 9.4 N/A

TX Power(dBm): -6.7 3.8 N/A N/A 10.1 7.5 N/A

# xdslcmd info --show
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 6843 Kbps, Downstream rate = 37164 Kbps
Path: 0, Upstream rate = 6874 Kbps, Downstream rate = 24999 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): 9.4 6.2
Attn(dB): 0.0 0.0
Pwr(dBm): 12.0 4.2
VDSL2 framing
Path 0
B: 47 207
M: 1 1
T: 57 40
R: 16 0
S: 0.0610 0.9607
L: 8390 1732
D: 1061 1
I: 64 104
N: 64 208
Counters
Path 0
OHF: 554689 201667
OHFErr: 0 0
RS: 126404985 3769221
RSCorr: 6333 0
RSUnCorr: 0 0

Path 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 92988741 0
Data Cells: 295594 0
Drop Cells: 0
Bit Errors: 0 0

ES: 0 0
SES: 0 0
UAS: 20 20
AS: 1937

Path 0
INP: 8.00 0.00
PER: 3.47 9.60
delay: 16.00 0.00
OR: 73.59 26.64

Bitswap: 12 3


Thanks in advance.

Your Downstream rate suggests that DLM is allocating a lot of bandwidth for FEC (error correction). This is confirmed by looking at the subsequent details. However, your SNR level is above 6, suggesting that you are also on a banded profile.

1. Your actual rate is way below the attainable; 25Mbps vs 37Mbps. The difference would suggest that there is a lot of bandwidth being allocated to FEC error correction. However, my experience is that *if* DLM were turned off, the actual rate would rise by half the difference, and the attainable rate would drop by half the difference - both resulting in around 31Mbps.

2. But the actual speed of 24999 is *so* close to 25Mbps, it suggests that it has been banded by DLM. The fact that SNR values are 9.4dB backs this up.

This suggests your line is having quite a few issues.

But... you mention that your HH5 was constantly rebooting - so it could have been the HH5's behaviour that has caused DLM to intervene.

3. DLM has specified an INP value of 8 symbols and a "delay" of 16ms.
These are both noticeably higher than "standard" DLM settings of 3 symbols and 8ms respectively, again suggesting your line is suffering from quite bad interference.

4. The modems have negotiated FEC settings of R=16 and N=64, so FEC is using about 25% of your line's bandwidth for the error correction work (over 8Mbps), leaving the other 75% for your data (ie the 25Mbps).

Interleaving is turned on with D=1061, I=64 (depth and width).

So... DLM has intervened quite heavily. The question is whether the HH5 is the cause, or the effect.

Best answer is to leave the HG612 connected, and see whether it stays connected, so watch the AS value, and the data returned from the "xdslcmd info --stats" command.

If it stays connected, and you end up seeing very low error rates, then DLM will eventually reduce and/or remove its intervention.

Just ran my first ever # xdslcmd info --stats command (results below).

What does the 'AS' value represent as mine seems quite high (currently 112630)?

# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 6874 Kbps, Downstream rate = 34948 Kbps
Path: 0, Upstream rate = 6874 Kbps, Downstream rate = 24999 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): 8.3 6.2
Attn(dB): 0.0 0.0
Pwr(dBm): 11.6 4.3
VDSL2 framing
Path 0
B: 47 207
M: 1 1
T: 57 40
R: 16 0
S: 0.0610 0.9607
L: 8390 1732
D: 1061 1
I: 64 104
N: 64 208
Counters
Path 0
OHF: 32253013 1245718
OHFErr: 265 124
RS: 3058655512 723112
RSCorr: 1944180 0
RSUnCorr: 7878 0

Path 0
HEC: 1794 0
OCD: 124 0
LCD: 124 0
Total Cells: 1112650078 0
Data Cells: 22960048 0
Drop Cells: 0
Bit Errors: 0 0

ES: 49 92
SES: 0 0
UAS: 20 20
AS: 112630

Path 0
INP: 8.00 0.00
PER: 3.47 9.60
delay: 16.00 0.00
OR: 73.59 26.64

Bitswap: 16039 1573

Total time = 1 days 7 hours 17 min 33 sec
FEC: 1944180 0
CRC: 265 124
ES: 49 92
SES: 0 0
UAS: 20 20
LOS: 0 0
LOF: 0 0
Latest 15 minutes time = 2 min 33 sec
FEC: 3253 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: 8950 0
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 7 hours 17 min 33 sec
FEC: 598553 0
CRC: 85 18
ES: 14 13
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 1345627 0
CRC: 180 106
ES: 35 79
SES: 0 0
UAS: 20 20
LOS: 0 0
LOF: 0 0
Since Link time = 1 days 7 hours 17 min 9 sec
FEC: 1944180 0
CRC: 265 124
ES: 49 92
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
#

AS = "Available seconds"

When you turn it into days+hours+mins, it ought to match the final section of the "--stats" output, "since link time= xxxx". However, there's some form of bug when the connection stays up for more than 49 days, where the "since link time" value stops increasing.

Both AS and the "since link time" go back to zero if the modem resyncs.

UAS="Unavailable seconds"

You can see this in the "total time" section; it shows the value that the modem stays un-synced (such as when negotiating). If it stays at 20, it means you haven't disconnected.

ES="Errored Seconds"
This is the count of how many second-long periods experienced noise.
DLM monitors this to decide whether to intervene more or less.

My HG612 modem has had a stable connection for over a week now. Line was dropping 3+ times a day with the HH5.

I was expecting to see some speed increases from DLM now I have a stable connection for 7+ days, not sure if I'm being impatient or not?

I have run another stats output from the modem and I am concerned with the amount of errors on the download side, not sure it these are in an acceptable range or not. If the errors are not in a normal range could explain why I seemed to have been capped at 25Mb.

Anyone able to comment on the errors shown below:

# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 6791 Kbps, Downstream rate = 34328 Kbps
Path: 0, Upstream rate = 6874 Kbps, Downstream rate = 24999 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): 7.9 6.0
Attn(dB): 0.0 0.0
Pwr(dBm): 12.0 4.2
VDSL2 framing
Path 0
B: 47 207
M: 1 1
T: 57 40
R: 16 0
S: 0.0610 0.9607
L: 8390 1732
D: 1061 1
I: 64 104
N: 64 208
Counters
Path 0
OHF: 183251535 247861
OHFErr: 2802 489
RS: 3126580252 1086567
RSCorr: 8894761 0
RSUnCorr: 54095 0

Path 0
HEC: 12651 0
OCD: 871 0
LCD: 871 0
Total Cells: 659673746 0
Data Cells: 65598699 0
Drop Cells: 0
Bit Errors: 0 0

ES: 257 410
SES: 8 0
UAS: 20 20
AS: 639915

Path 0
INP: 8.00 0.00
PER: 3.47 9.60
delay: 16.00 0.00
OR: 73.59 26.64

Bitswap: 90217 9534

Total time = 1 days 9 hours 45 min 38 sec
FEC: 8894761 0
CRC: 2802 489
ES: 257 410
SES: 8 0
UAS: 20 20
LOS: 0 0
LOF: 0 0
Latest 15 minutes time = 38 sec
FEC: 262 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: 9590 0
CRC: 1 0
ES: 1 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 9 hours 45 min 38 sec
FEC: 814656 0
CRC: 379 22
ES: 18 21
SES: 1 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 1111130 0
CRC: 526 52
ES: 29 48
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Since Link time = 7 days 9 hours 45 min 15 sec
FEC: 8894761 0
CRC: 2802 489
ES: 257 410
SES: 8 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
#

Interleaving on FTTC, unlike on ADSLx, has a very significant effect. In the order of 10Mbps, which is what you are seeing as the difference between actual and Max (attainable). You have quite heavy downstream interleaving applied.

Does it look like my line requires that heavy interleaving?

Out of my depth at that stage sorry, but I think it could be a few more days before the DLM would remove it anyway. And then possibly in steps at shorter intervals.

More up to date stats with attenuation values also:

# xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 6743 Kbps, Downstream rate = 36428 Kbps
Path: 0, Upstream rate = 6874 Kbps, Downstream rate = 24999 Kbps

Discovery Phase (Initial) Band Plan
US: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3971)
Medley Phase (Final) Band Plan
US: (0,95) (868,1207)
DS: (32,859) (1216,1963)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 6743 kbps 36428 kbps
Actual Aggregate Tx Power: 4.2 dBm 12.0 dBm
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 8.4 47.1 N/A N/A 20.1 57.5 86.8

Signal Attenuation(dB): 8.4 46.7 N/A N/A 20.1 57.5 N/A

SNR Margin(dB): 5.9 5.9 N/A N/A 8.4 9.8 N/A

TX Power(dBm): -6.7 3.8 N/A N/A 10.1 7.5 N/A

# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 0
Max: Upstream rate = 6739 Kbps, Downstream rate = 36428 Kbps
Path: 0, Upstream rate = 6874 Kbps, Downstream rate = 24999 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): 9.0 5.9
Attn(dB): 0.0 0.0
Pwr(dBm): 12.0 4.2
VDSL2 framing
Path 0
B: 47 207
M: 1 1
T: 57 40
R: 16 0
S: 0.0610 0.9607
L: 8390 1732
D: 1061 1
I: 64 104
N: 64 208
Counters
Path 0
OHF: 200267502 1194031
OHFErr: 2902 525
RS: 2711253421 3639120
RSCorr: 9195648 0
RSUnCorr: 58400 0

Path 0
HEC: 13603 0
OCD: 933 0
LCD: 933 0
Total Cells: 3512617824 0
Data Cells: 69625196 0
Drop Cells: 0
Bit Errors: 0 0

ES: 281 445
SES: 8 0
UAS: 20 20
AS: 699336

Path 0
INP: 8.00 0.00
PER: 3.47 9.60
delay: 16.00 0.00
OR: 73.59 26.64

Bitswap: 97045 10212

Total time = 1 days 2 hours 15 min 59 sec
FEC: 9195648 0
CRC: 2902 525
ES: 281 445
SES: 8 0
UAS: 20 20
LOS: 0 0
LOF: 0 0
Latest 15 minutes time = 59 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: 4267 0
CRC: 0 8
ES: 0 6
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Latest 1 day time = 2 hours 15 min 59 sec
FEC: 30435 0
CRC: 1 16
ES: 1 14
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 1085108 0
CRC: 478 42
ES: 41 42
SES: 1 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
Since Link time = 8 days 2 hours 15 min 35 sec
FEC: 9195648 0
CRC: 2902 525
ES: 281 445
SES: 8 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
#

Sorry to hi-jack this thread I thought I would just show mine in comparison but I am also wondering if there if someone could tell me if have any issues.

# xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 2
Last initialization procedure status: 0
Max: Upstream rate = 5547 Kbps, Downstream rate = 30244 Kbps
Bearer: 0, Upstream rate = 2000 Kbps, Downstream rate = 26542 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 13.2
Attn(dB): 24.4 0.0
Pwr(dBm): 11.7 5.6
VDSL2 framing
Bearer 0
MSGc: 22 330
B: 51 48
M: 1 1
T: 64 6
R: 12 16
S: 0.0623 0.7651
L: 8216 711
D: 519 1
I: 64 68
N: 64 68
Counters
Bearer 0
OHF: 1123403 279918
OHFErr: 281 0
RS: 287528035 2032446
RSCorr: 174403 1
RSUnCorr: 8185 0

Bearer 0
HEC: 1560 0
OCD: 118 0
LCD: 118 0
Total Cells: 229490658 0
Data Cells: 17043486 0
Drop Cells: 0
Bit Errors: 0 0

ES: 276 1
SES: 13 0
UAS: 56 43
AS: 4498

Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 4.00 16.13
OR: 55.94 166.64
AgR: 26598.10 2166.36

Bitswap: 3640/3640 0/0

Total time = 2 hours 56 min 21 sec
FEC: 398081 5
CRC: 3851 1
ES: 276 1
SES: 13 0
UAS: 56 43
LOS: 0 0
LOF: 13 0
LOM: 10 0
Latest 15 minutes time = 11 min 21 sec
FEC: 40414 0
CRC: 66 0
ES: 25 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: 30404 0
CRC: 61 0
ES: 28 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 2 hours 56 min 21 sec
FEC: 398081 5
CRC: 3851 1
ES: 276 1
SES: 13 0
UAS: 56 43
LOS: 0 0
LOF: 13 0
LOM: 10 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 = 1 hours 14 min 57 sec
FEC: 174403 1
CRC: 281 0
ES: 118 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
Thanks

You are still set at heavy DLM intervention, unchanged from before.

The main input from DLM is seen as INP=8 and delay=16.
The result from the modem shows with FEC overhead of (R=16/N=64), or 25%.

Is this still needed?

The use of FEC is detecting a lot of errors (FEC=9,195,648 over the 8 days), and is correcting the vast majority of them (CRC=2,902 in the same period).

With that level of errors, I would guess that FEC/interleaving is very much needed on your line. It could be true that the settings could be relaxed somewhat, but we (as mere Joe Public) know little about the settings that DLM follows to decide on that.

When I had DLM intervene after a line fault, it took 3 weeks for it to de-intervene. You might need more patience.

You have had intervention from DLM too, but at the "normal" level of INP=3 and delay=8.

Your modem has responded with a FEC overhead of (R=12/N=64), or 18%, so is having less effect than adrian109's.

Your modem is seeing FEC errors (174,000 in 75 minutes) and correcting them.

Comparing the rate of FEC errors between you and @adrian106: you are getting around 38 errors per second, while @adrian106 is getting around 13 errors per second.

Your FEC errors are mostly corrected, but resulted in CRC errors 281 times at a ratio of 630:1. @adrian106 had a ratio of 3200:1.

You are getting more FEC errors per second, but the current FEC settings are letting more become CRC errors per second too.

That suggests that you certainly need FEC/interleaving turned on, and that perhaps your settings need to be made more stringent, or perhaps that @adrian106's can be relaxed.

Hi,

Thanks for comparison, if I should make my settings more stringent please could you point me to which ones?

The four I mentioned are the ones to watch: INP, delay, R and N.

Thanks, I will keep an eye on it.

Why does the DLM decide to turn FEC and interleaving on? I am assuming its to do with telephone wiring but could it also be a power supply like the one fro my HG612 and HG533? As they both are the same power supply and if put an AM radio at the frequency MrSaffron said and it picks up some interference.

It decides on the basis of error counts.

I see, do the errors appear due to interference?

Yes, they can.

Ok thanks, Like I said on an earlier post I think it might be my router and modem AC adaptors. As they seem to put out a lot of noise when using a AM radio to test. I think I will try different adaptors and see how much noise they put out before I switch them.

As I am sure others will tell you, all Switch Mode power supply adaptors generate loads of noise if you put a MW radio near them. Question is, is it causing interference to your broadband? I had 6 months of absolute mayhem on ADSL2+ where something was putting something like a 7dB drop in noise margin causing an immediate disconnect when the SNRM was already low several times a day. After a LOT of investigation found it was a faulty switch mode PSU on a PC monitor three doors away! Once fixed, no sign of it.

You really need to watch/refresh the stats in real time for any effect on the noise margin and play around with moving the PSUs around etc. Best graphically using DSLStats or similar - you'll find a lot of info if you Google this.

Just make sure you keep the PSU bricks and leads away from the (as short as possible) lead from the master socket to the modem/router etc and route the mains leads away from the physical modem if you can. Personally I've never had a faulty or any noticeable interference from a Switch Mode PSU and there are 13 of them in my room plus three APC UPS powering one thing and another.

You can see what was hapening HERE back in 2012.

Hi,

I did a bit of testing yesterday. As you said about power supply's making lots of noise I couldn't find one that has the least amount of noise. I tried moving the PSU's around and moved them about 1ft and half away from master socket and it has reduced errors but not as much I would like.

I have taken you advice about dslstats and I am currently monitoring it.

As for the PSU wires they are bundled with the RJ11 cable fro the telephone not the modem. they do meet somewhere as it all in cable tidy wrap. I will have to do a bit re wiring I think with the power cables, and as for the router power cable is really short while the HG612 is really long so it may be a bit of an issue. When I tested yesterday with a radio the huawei PSU's put out the most noise than all of the other AC adaptors I have spare from previous routers.

My main aim is to reduce the errors either completely so FEC and interleaving turn off so I get a higher sync or reduce them to a small amount so hopefully the DLM will de intervene a bit.

Neat coils of power cables are bad as they create stronger magnetic fields.

Power and signal cables should not run close together and parallel because of the magnetic field round the power one. If they have to cross, best done at right-angles.

Have you tried replacing the filter, or double-filtering the phone line? (You haven't got a Sky box anywhere have you?) Is the phone on a plug-in extension lead?

I see you've lost about 10Mbps against max achievable in the process of adding the interleaving and running error correction. I have lost about the same in the 2 months since FTTC was available - started at an actual of 56Mbps down and now at 46Mbps. The loss now seems to be due to cross talk as more connections got added from my cab - and I'm at about 800m distance with an estimate at only 32 or so so guess more drops to come maybe.

Were you higher originally with a gradual series of drops like mine or was it sudden? I had Errored Seconds counts in the many high 100s per hour originally but now down to about 20 max per hour after the DLM has changed the interleave about 6 times. It tried to reduce the interleaving once but that just pushed the Errored Seconds count back up again. Seems happy when it's below 30.

It's interesting that in the past, when there have been power cuts, as I have all the DSL stuff on a UPS I can see what the line looks like under these conditions. With power off just in the lane (it's fed from a different supply to the rest of the village) I see a jump in available SNR margin of about 4dB. If the whole village goes off its 7-8dB! And there is little industrial activity betwen me and the exchange. Shows just how much ambient noise there is.

Ok I will look at what the best option is like you said probably right angle. Is there anyway of shielding power cables? I had a shielded RJ11 cable but it made my SNR go really low and racked up more errors so I switched it back.

If you mean the VDSL Openraech faceplate I have tried the original I removed but the sync seems to go up and down all the time. For double filtering is that where I would plug one of those dangly filters in or install a VDSL faceplate on top of the one I have? No I don't have anything Sky, and no the phone is directly into the master socket.

When I first got fibre the engineer told me it was synced at 26.2Mbps and said hat would the best you will get at this distance, though I have had 26.5Mbps recently as well so It hasn't really dropped as such.

One thing I have noticed it when it synced higher more errors appear a bit like your if a sync slightly lower less errors appear.


This maybe irrelevant but my friend who lives 3 doors down the road from me and served by same cab and dp as me and has FTTC but he is synced at 15000 so giving him 13.5MBps throughput when does tests. So I think he has it bad but then again his telephone looks to be gaffer taped in areas and has mix of wire that looks to be for speakers and modern drop wire. He like me synced at about 26Mbps at first but his has dropped a considerable amount though he has a lower latency than me which does not make sense.

To double filter your phone plug a dangly into the phone socket with the master and VDSL plate fully assembled.

Ok done it

WWWombat & BatBoy & others
I know this post is a bit old but hopefully the above and others still have an eye on it.
I have a new post going here.............

https://forums.thinkbroadband.com/fibre/4657616-good...

Was there ever a definitive solution to what appears to be heavy DLM intervention which resulted in a low throughput against a higher sync ?.

i.e, was it a copper line fault ?.

In your linked tread you have this line:

Profile Name 0.128M-80M Downstream, Retransmission Low - 0.128M-20M Upstream, Error Protection Off

That suggests that DLM is providing the highest possible connection speed on your line. As do your line stats. It does not control throughput other than by lowering connection speed.



(WWWombat has not posted on these forums since July 2018, and BatBoy passed away during the same year).

RobertoS

Thanks for your comment.
Now I have read the above again, I had taken WWWombat's comments to ......

Adrian109 9th April
Max: Upstream rate = 6843 Kbps, Downstream rate = 37164 Kbps
Path: 0, Upstream rate = 6874 Kbps, Downstream rate = 24999 Kbps

WWWombat 10 April
. The modems have negotiated FEC settings of R=16 and N=64, so FEC is using about 25% of your line's bandwidth for the error correction work (over 8Mbps), leaving the other 75% for your data (ie the 25Mbps).

And made 2 + 2 to equal 5.

It looked like DLM had reduced throughput.

I had missed the difference between the max achievable and actual.

I have another open post here.......
https://forums.thinkbroadband.com/fibre/4657616-good...

Is there anything here that a change of router might help diagnose my issue ?

Thanks

============================================================================
VDSL Training Status: Showtime
Mode: VDSL2 Annex B
VDSL Profile: Profile 17a
Traffic Type: PTM Mode
Link Uptime: 2 days: 21 hours: 14 minutes
============================================================================
VDSL Port Details Upstream Downstream
Line Rate: 20.063 Mbps 79.998 Mbps
Actual Net Data Rate: 19.999 Mbps 79.999 Mbps
Trellis Coding: ON ON
SNR Margin: 15.6 dB 7.7 dB
Actual Delay: 0 ms 0 ms
Transmit Power: - 9.2 dBm 13.9 dBm
Receive Power: -18.7 dBm 6.4 dBm
Actual INP: 0.0 symbols 48.0 symbols
Total Attenuation: 9.3 dB 7.4 dB
Attainable Net Data Rate: 26.359 Mbps 89.238 Mbps
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 2.1 7.4 11.1 N/A 5.0 10.8 16.9
Signal Attenuation(dB): 2.1 7.0 10.3 N/A 5.5 10.7 16.9
SNR Margin(dB): 16.5 15.5 15.5 N/A 7.8 7.7 7.6
Transmit Power(dBm):-22.9 -35.5 - 9.6 N/A 11.3 7.4 7.2
============================================================================

VDSL Counters

Downstream Upstream
Since Link time = 14 min 41 sec
FEC: 32371 15281
CRC: 5 651
ES: 2 493
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 13 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: 1 20
CRC: 0 3
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 21 hours 15 min 13 sec
FEC: 31754 872
CRC: 5 206
ES: 2 159
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 335 6604
CRC: 0 230
ES: 0 170
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Total time = 1 days 21 hours 15 min 13 sec
FEC: 32371 15281
CRC: 5 651
ES: 2 493
SES: 0 0
UAS: 30 30
LOS: 0 0
LOF: 0 0
LOM: 0 0
============================================================================

https://forums.thinkbroadband.com/fibre/t/4657616-go...

Is probably the best thread to continue.

Cross posting about the same issue can confuse people who do not realise and lead to duplication of effort, or people missing salient points.