In reply to a post by Zarjaz:

So we reckon REIN then ?

To non-engineer brains, at least mine which was only a "Certified" engineer's LOL, REIN means some big noise source external to the premises. Thinking about it now, an obvious misconception .

In reply to a post by greenglide:

I would imagin that a VPN is used to carry the traffic from the BT WIFI AP.

One thing is certain - there is no way that it can have any impact on the sync rate as there can only be one data stream over the DSL link.

Correct - it is a VPN and it just borrows a proportion of the bandwidth which depends on the sync rate to a max of 2Mb upstream and if it s not required that is available for the owner.

A couple of years back I tried running speedtests on a line synced at just under 19 Mbps. From memory, with no-one on the WiFi I achieved around 18.2Mbps. I then started some large downloads on the WiFi connection and tried speedtests again and results varied between 16.2 and 16.4 Mbps so 1.8 to 2 Mbps was given to the VPN for the WiFI service. .

In reply to a post by TomPoolHD:

The line was disconnecting every time the phone rang , He did something at the exchange and said it was fixed i heard nothing after that. This line is at my grandparents and i don't want to hassle them to stay in to wait for a engineer that not really a option.

Is the line stable now? Do your grandparents need every last drop of speed? Consumer-level modems might as well put a Lib Dem Manifesto in table form under the error stats, for how trustworthy they are. Swap it with 10 others you'll get 10 sets of very different results.

It ain't optimal but if it ain't broke...?

Seems stable now . Il give it a restart at 11am and see how it goes.
Will the noise margin go back to 6db? Or will i have to ring BT?

Edited by deleted (Wed 29-Jan-14 07:46:02)

Ok 5 days later and im here with the results. Could any one tell me how i could get a better speed now that you have these stats:

Connection Information

Line state: Connected
Connection time: 5 days, 14:24:05
Downstream: 14 Mbps
Upstream: 1.198 Mbps

ADSL Settings

VPI/VCI: 0/38
Type: PPPoA
Modulation: G.992.5 Annex A
Latency type: Interleaved
Noise margin (Down/Up): 9.9 dB / 5.8 dB
Line attenuation (Down/Up): 23.5 dB / 12.4 dB
Output power (Down/Up): 18.3 dBm / 12.6 dBm
FEC Events (Down/Up): 243443 / 1510
CRC Events (Down/Up): 722 / 437
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): 4773 / 733
Error Seconds (Local/Remote): 501 / 177

http://www.coolwebhome.co.uk/calc/index.php?param=RG...

Lower the target noise margin to a more standard 6dB could see you get 16 Mbps, but looks likely that this may mean more errors i.e. line does not look totally clean.

Also for posting link data, a resync so the results are seen as soon after the modem has synced will help. It maybe you have a 12 dB target margin and actual margin has dropped lower now as the sun is just setting (yes once the sun has set does have an effect on ADSL)

Here you go MrSaffron re sync in test socket:

ADSL Line Status

Connection Information

Line state: Connected
Connection time: 0 days, 00:00:51
Downstream: 14 Mbps
Upstream: 1.17 Mbps

ADSL Settings

VPI/VCI: 0/38
Type: PPPoA
Modulation: G.992.5 Annex A
Latency type: Interleaved
Noise margin (Down/Up): 8.3 dB / 6.3 dB
Line attenuation (Down/Up): 23.4 dB / 12.3 dB
Output power (Down/Up): 18.3 dBm / 12.4 dBm
FEC Events (Down/Up): 39 / 120
CRC Events (Down/Up): 1 / 21
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): 3 / 10
Error Seconds (Local/Remote): 301 / 130

Ok no change in advice, lower target noise margin will give more speed, but even with 51 seconds run time there is evidence of errors, so they might get worse.

So how do i go about lowering the target noise margin? Ring BT or contact them on the BT forum?

If it's stable, the DLM may lower the (sync-time) margin to 6dB itself. It normally takes 10-14 days after the cause of the instability is removed. That would mean in another 5 days or so.

BT could reset it earlier, but the errors then may cause DLM to raise it again. That's what it's for, to balance between speed and stability.

I would think the forum route, as first-line on the phone may not know what you are talking about, and probably haven't the authority anyway.

Edited by RobertoS (Tue 04-Feb-14 18:38:39)