DLM reset request (ADSL2+)

[#1]

Long power outage yesterday.

A Billion 7800DXL always handled cuts superbly before but this time it was killed possibly by the switch on surge.

Am using an old PN Technicolor582. It does the basics but is very slow. Stats say bandwidth is 16.1 but Ookla over wi-fi on an iPad gives 3 maximum. SNRM is shown as c.12. This was OK with the Billion as it gave a rock solid connection of 16+ and 13+ over wi-fi/iPad.

Can PN reset the DLM to 6?

TIA.

[#2]

@Mardler 

Have you confirmed that you do not also have a fault on your line?

For example, if you still have a telephone service, do you have dial tone?

It is quite possible, (I have experienced it myself), for one leg of the telephone pair to be broken, which will prevent the telephone from working, but for the broadband to still work - albeit at greatly reduced speed.

.

[#3]

@Mardler 

Your message is a bit confusing.

Are you saying that you previously got with the Billion a download of 16Mbps with a SNR of 12dB and with the 582 you are receiving the same 16 Mbps with the same SNR. The only difference being that now the wireless performance is much slower?

If so, then this is a wireless problem and nothing to do with your ADSL connection.

Why not either ask Plusnet for a new hub or buy a replacement for the Billion.

At 16Mbps you are getting nearly the full speed available from ADSL so I doubt that a reset would make a significant difference anyway. I would guess that your wired speed exceeds the guaranteed minimum. The line doesn't need a low SNR and in these circumstances it's advantageous to have it higher.

[#4]

Mr P: the phone line is fine.

[#5]

Baldrick: thanks and yes, that is exactly what I mean. I am also aware of the lousy wi-fi performance of the 582 hence buying the Billion 7 years ago. The Billion gives both a maximum possible (bandwidth) and actual connection, the 582 gives only the former so connection is probably going to be 80% of that at best. Last night late streaming YT stuff was very blotchy thus confirming 3 devices showing 2 or 3 Mbps d/l over wi-fi (another device gave 11+ which was odd) all using Ookla.

The Billion SNR tweaking initially allowed a solid 20Mbps but shoddy work at the exchange caused all kinds of problems for those relying on it. Eventually the SNR started to rise until its current level so I didn't tweak it instead opting for a medium d/l speed and better resilience and it's worked perfectly until now.

I just bought a replacement 7800DXL from a guy who seems honest and helpful. 

I will post again if I manage to get the replacement working.

[#6]

SNRM of 12dB suggests that there is an (or has been an) issue on line.  Suggest that raising a fault report can do not harm.

What is the line attenuation figure?  With 16mbps at 12dB on ADSL2+ this sounds like a very short line ... which might do lots better.

WiFi is though going to be limiting here.

[#7]

An update.

The DLM request was when using the Technicolor router.

A replacement Billion 7800DXL arrived yesterday. I first tried the supplied psu with my 7800 and it worked perfectly.

It too connected with a high SNRM. The router target SNRM was 4 (which has given a rock solid connection with a high actual SNRM of 11+ and a lowish rate (which I left) so I reset it to 6.

The 6 setting gave a rate of 20379 with 17.1 measured over wi-fi. Stable all afternoon and evening.

Overnight the disconnects started. Very similar to several occasions last year (then the connection was mostly up for 2 or 3 months before a spell of hourly disconnects).

Last year, although Openreach wouldn't admit it, there was a fault at the exchange subsequently corrected.

Is it worth asking PN to run a check on my line?

[#8]

While typing my update comment there was another disconnect, "ADSL link down" as usual.

Simultaneously a mains monitor disconnected from the sender in the outside meter box.

Interference?

[#9]

TM, here are the stats:-

Target SNRM set at 4 at 16:46 yesterday:-

SNRM: 6.4, attenuation 16db, d/l rate (sync): 20379 (17.1Mbps over wi-fi).

Target SNRM set at 6 at 01:30 today:-

SNRM: 9.1, attenuation 16, sync 18603 

Currently:- 8/17/13507*

We're about 0.7 of a mile from the exchange.

*The drop in sync rate coincided with the disconnects.

Wi-fi is pretty good.

[#10]

I highly recommend that (at least whilst there are issues) you do not “game” the SNRM. All that does is to mask issues … and artificially keep the speed above the minimum guaranteed.

There is no harm in raising a fault … but only when the line management is not being fudged.

0.7km should deliver an attenuation around 12dB … which ought to sync at 24mbps (IP profile around 21mbps). So remove the fudge factor and get the underlying issue investigated, as it would appear that the line cannot sustain a 4dB margin.

[#11]

Read my notes again, TM.

There no fudge. The SNRM target is now set to 6. Apart from these odd spells the line easily sustains a 4db SNRM for months on end (e.g. 77 days, 90 days etc) in fact it has worked perfectly at 2. That's down to the router.

I also showed the attenuation at 16/17db (the Techicolor router was identical) which is way more than 12. 

As for sync, I have never seen anywhere near 24mbps, 21+ is the best which is what I expect from a good line with the IP profile; 21220 held yesterday afternoon at 4db target SNRM until the early hours today when the disconnects started and I reset to 6 for greater stability but it made no difference. 

Currently it's SNRM 8.1, attenuation 17, attainable rate 11520, sync 10467 - last disconnected 1h 30m ago. Not good!

Last year there were 3 or 4 spells of identical behaviour all due to an exchange issue.

Disconnects every hour or so are unacceptable.

We can soldier on a little longer before switching to FTTP. And there's the dilemma: who with?!

[#12]

I have been looking at the SNRM settings. Even at a target of 3 sync is 11900 (on 12980 attainable with actual SNR 6) which is crazy. Yesterday it was 20379 at 4 (21220 attainable, actual SNR 6.4). Resetting to 6 gives SNR 9+ and sync c.9. Attenuation is increasing, now 17.

This is near identical to 2023 and previous years when exchange faults were detected.

It doesn't explain why a mains monitor lost sync with its outdoors transmitter at exactly the same time as the internet connection once again became iffy. Maybe coincidence, or interference.

[#13]

@Mardler 

Are you in a particularly rural location?

I'm just wondering if there is an issue with your incoming mains supply. Possibly an occasional spike that is affecting your mains monitor, and also either your router or inducing interference on to your telephone line?

.

[#14]

Mr_P, thanks: locale is fairly rural and only 0.7 of a mile from the exchange. A mains transformer is very close to the house. So we should do better and were on Wednesday afternoon and evening up to just gone midnight.

I will try resyncing mid afternoon with the target SNRM set as before.

FWIW, the incessant disconnects started 10 or more years ago. A number of serious copper line faults were rectified with some improvement. The PN router was ditched for a top Netgear and that was a bit better especially wi-fi. Eventually I became fed up with often near dialup speeds and in 2017 bought the Billion. Instant success: we had an excellent speed and a 100% stable connection even using a somewhat dubious SNRM tweak (actual SNR of 3 or even 2). I used a more realistic SNRM long term and apart from bouts of disconnects like this the connection stays up for months. 

Of course, we currently have strong solar activity so that might have an impact somewhere. Oh and I might wander round the locality listening for AM interference at c.512m which is roughly the frequency at which interference will affect the copper line and SNR.

[#15]

I had read carefully your previous posts and your last one confirmed what I said before - you gaming the SNRM masks the issue. If your line is 0.7km it should do much better than it is doing without fudging things. If the line is fine, is fine the DLM will find its own way to 3dB without your “assistance”.

SNRM is only elevated to address stability issues, due to a fault. Your best course of action is to stop trying to bend light and raise a fault report. Confirming the line attenuation figure (which is more accurate than suggesting a line length) would help to affirm the assessment.