On WBC 3dB is the default Target NM with Fast Path on stable lines.

EDIT: That's what it aims at but will approach it gradually as not all lines are stable and it is learning your line.

Edited by XRaySpeX (Tue 26-Mar-13 23:28:47)

Ummm.

The default, i.e. the value at which it is set on initial connection, is still 6dB. What has changed is that as well as being able to increase it on unstable lines it can now also lower it on stable ones. Seemingly after a much shorter period than its recovery period from disturbance of 10-14 days.

So, a bit of a mystery as to why it is at 7db on mine, maybe the DLM trying out various settings?

If your target SNR is 7 it would have to be manually set, the DLM will only change it to 3 or 9 in extremely rare cases (from what I've seen).

Is your SNR 7 or do you mean target of 7SNR?

Edited by deleted (Wed 27-Mar-13 08:30:34)

It goes up and down continually over 24 hours. It only gets set at the time you connect, and BT systems use 3, 6, 9, 12, and 15dB. 18dB used to be available as a manual setting on ADSL Max but I don't know if that is still the case on all products.

Due to the variations in SNRM during a period of connection we always request the OP to supply his reported SNRM at the moment of a re-sync (sync time)

Well, at about 4 this morning, unless there was some weird power outage, it looks like the DLM decided to do a re-sync, here are my new stats as of the time of posting this:

Line state: Connected
Connection time: 0 days, 08:20:17
Downstream: 16.08 Mbps
Upstream: 888.9 Kbps

ADSL Settings

VPI/VCI: 0/38
Type: PPPoA
Modulation: G.992.5 Annex A
Latency type: Interleaved
Noise margin (Down/Up): 8.9 dB / 13.3 dB
Line attenuation (Down/Up): 6.2 dB / 3.3 dB
Output power (Down/Up): 20.0 dBm / 12.1 dBm
FEC Events (Down/Up): 68 / 121
CRC Events (Down/Up): 0 / 32
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
HEC Events (Down/Up): 0 / 11
Error Seconds (Local/Remote): 0 / 0

And here are the stats from the logs:

03:57:28, 27 Mar. ( 100.560000) DSL is up
03:57:26, 27 Mar. ( 98.240000) DSL noise margin: 13.20 dB upstream, 9.00 dB downstream
03:57:24, 27 Mar. ( 97.160000) DSL line rate: 888 Kbps upstream, 16461 Kbps downstream

Weird that not much has changed

Edited by deleted (Wed 27-Mar-13 12:28:04)

Looking closer at the log it seems the whole hub was rebooted by an engineer remotely logging in, at 4am

<<<<<<<<<<<<<<<<<<<< Limit of uservisible log >>>>>>>>>>>>>>>>>>>>
03:56:14, 27 Mar. ( 26.520000) Booting firmware 4.7.5.1.83.8.94.1.11 (Type A)
03:55:31, 27 Mar. (127613.420000) DSL is down after 577 minutes uptime
03:55:30, 27 Mar. (127612.080000) PPPoA is down after 577 minutes uptime
03:55:23, 27 Mar. (127605.260000) Server URL: https://pbthdm.bt.motive.com; Connecting as user: ACS username
03:55:21, 27 Mar. (127603.510000) Initializing transaction for event code 6 CONNECTION REQUEST

Rien n'a chang� then.

The 7dB NM you chucked in was just an intermediate night-time non-sync time value.

The HomeHub 3 is remotely managed in terms of logging in and checking firmware versions etc.

With 6 million customers it will NOT be someone logging in individually to your home hub.