I been in contact with Support again this morning. They are reluctant to carry out a reset on my line in case it gets 'tagged' by BT. They believe that the DLM will pick up the fact that my line is now stable - quote Changes are normally made providing the line will support that change over 14 days unquote.

This was the thrust of my initial post as a number of ISP-run forums suggest that a downstream SNR of 15 is a BT 'fixed' setting which requires human intervention to change.

My particular router is now on release in Australia. Broadband customers are recording ADSL2+ download speeds in excess of 20Mbps with a router SNR of 3.

After a small fault on my line last week my snr moved from 6 to 9
yesterday it dropped back to 6 with only a small amount of line errors and no disconnections.
I think its all to do with line errors on how fast your snr will come back down

This will be seen as instability by the BT profiling system used by IDNET and will damage your profile.

Looks like a statement of fact by me, do you accept that this is not the case.

I am tired of your trolling, sometimes helpful, but like misinformed call centre staff you can do more harm than good at times.

resyncs and level of errors is taken into account.

This is why some likes appear stable at 9dB for example but are never lowered to 6dB, because the errors detected in the background point towards things not being perfect.

In reply to a post by MrSaffron:

This will be seen as instability by the BT profiling system used by IDNET and will damage your profile.

Looks like a statement of fact by me, do you accept that this is not the case.

I am tired of your trolling, sometimes helpful, but like misinformed call centre staff you can do more harm than good at times.

Do you know why the SNR is 13 to 14 then?

Probably set as a target noise margin of around 12dB.

Why it is set to that one cannot answer, but seen as I've talked to the people behind the BT DLM system, then a single resync per day is not taken as an unstable line.

There are cases where some modems have resync'd without logging it in their internal GUI and a myriad of other possibilities, but is guess work by and large as to what is happening.

from what i was told from BT
Its all to do with loss of connection to the exchange and how many errors your line shows
So say i did 5 reconnection's every day for a week with little line errors and my snr should not change.
But say you did the same but had lots of line errors, then the DLM would take that into account and action a raise in SNR
Please do kick me if i got what they said wrong

Edited by deleted (Mon 28-Mar-11 15:10:16)

As a general rule under old IPStream Max you needed 10 or more disconnects in an hour to trigger the DLM to raise target noise margin.

With WBC I don't think it is vastly more sensistive, since one or two disconnects a day is to be expected from consumer hardware, i.e. people switching off over night, power outages, and the occassional bit of noise.

The tracking of errors and decisions are generally talked about with respect as to whether the target noise margin can be lowered.

Well i can confirm from my own experience that Errors are also tracked for raising your snr aswell
I was told the threshold for this target snr to be raised due to line errors but forget what it was
My line had no disconnections for 2 weeks but loads of errors
After a manual reboot of the router my snr was raised
loads of things now determine how your snr is played with by the dlm

Can't beat a manual set system, as you can have a line that produces errors that have little or no impact on the throughput or other factors, in such cases that should not mean dlm cripples that connection by raising snr like it always has,