Please may I have an explanation of how the SNR affects broadband delivery?

[#1]

Quote from: Anotherone

On the subject of that drop-wire - any signs, news of when they will be doing the pole replacement. I need to suggest what you want to try and get done.

I think the new poles are a bit of a red herring because the only poles affected are the last two before the one at the edge of the road... i.e. the three poles nearest to our house will not be changed... and the electricity wires will be move before any telephone cables get moved... might not be 'till the new year... according to the contractor...

[#2]

Not exactly a red herring, it would be a case of an Openreach engineer would be around, not to worry, I'll resort to Plan B.
Lets' see what tomorrow brings.

[#3]

The computer rebooted overnight... restarted at at 7:40am... offline between 8:20 and 8:30am... started new router at 1:08pm... stable connection established at 2:05pm...

[#4]

That is looking very much better.I'll post back more in a few minutes.

[#5]

I have now been continuously connected for...
Uptime: 1 day, 1:34:45
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 447 / 1,657
Data Transferred (Sent/Received) [MB/GB]: 815.44 / 3.64
Output Power (Up/Down) [dBm]: 12.0 / 16.7
Line Attenuation (Up/Down) [dB]: 37.7 / 67.5
SN Margin (Up/Down) [dB]: 8.8 / 7.9
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / TSTC
Loss of Framing (Local/Remote): 18 / 0
Loss of Signal (Local/Remote): 2 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 5,629 / 4
FEC Errors (Up/Down): 3,862 / 1,129,536
CRC Errors (Up/Down): 90 / 9,871
HEC Errors (Up/Down): 165 / 10,739
... and I've been impressed with the stability of the service...
Thank you for the support provided in this forum...
KRs... Richard...

[#6]

Well I'm sorry to say that although it's obviously better, there are still some problems. The CRC/ES errors are much too large, and something went on at just after 0300 which although doesn't appear to have caused any loss of sync, speeds still the same as the stats you PM'd me yesterday (and we can ignore the LOS as they were present also, I suspect due to the way you connected) the Upstream SNRM has also dropped a bit.
I'm not convinced RouterStatsLite is setup correctly, certainly the number of Points per page is too long to analyse detail.
I'll post back again about those settings.

[#7]

Quote from: Anotherone

I'm not convinced RouterStatsLite is setup correctly, certainly the number of Points per page is too long to analyse detail.

I've set the chart appended herewith to 5000 data points...
Anotherone... the point is, the connection has recovered from all errors, so far... which is better than ever before... I don't know what happened a 3am... I was asleep... in the past, the router would probably have rebooted... or the SN Margin would have dropped even further...
Is it the router that is 'managing' the connection or are the variations the result of equipment in my local exchange?

[#8]

Uptime: 1 day, 6:15:06
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 447 / 1,657
Data Transferred (Sent/Received) [MB/GB]: 967.27 / 4.20
Output Power (Up/Down) [dBm]: 12.0 / 16.7
Line Attenuation (Up/Down) [dB]: 37.7 / 67.5
SN Margin (Up/Down) [dB]: 10.1 / 8.6
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / TSTC
Loss of Framing (Local/Remote): 18 / 0
Loss of Signal (Local/Remote): 2 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 8,780 / 6
FEC Errors (Up/Down): 4,520 / 1,250,257
CRC Errors (Up/Down): 140 / 13,562
HEC Errors (Up/Down): 252 / 13,725
... graph with 1000 data points...

[#9]

Whilst the 582n may have ensured that the connection has been held with the problems that still remain, all credit to the broadcom chipset, it's not possible to speculate as whether those problems are solely related to interference pickup or an exchange/line issue with out greater detail on the SNRM plots. The line was showing no obvious faults on the last test, although not the best from a performance point of view.
The 582n may be managing things so far, but as I've already mentioned, the errors are high and this will mean a lot of data re-transmits and so reduced performance. Whilst what you see now may be a lot better than you've seen recently, it should still nevertheless be better still.
I want to check that we are definitely looking at all right things, so just want to go through the settings with you.
You selected Thomson TG582n/TG587n from the Router drop down menu?
The URL and Login are straight forward defaults. Now the graphs Tab -
Noise Margin Vertical Axis - leave that set to Adjust axis automatically for now. Tick Plot average value of previous 50 points on the Niose margin, click Apply. You can set the Connection speed to 2500 max, 0 min, no need to plot the Average (pointless). Click Apply.
In the Sample Interval box - sample every 10 seconds 720 points per page. If it's more points per page, the detail gets lost in the captured graph especially if you don't maximise the Window before minimising it to the tray.
On the Capture Tab - tick Noise Margin & Connection speed & Capture part graphs. On the Noise Margin graph itself - right click and select Plot Upstream Noise.
If you are concerned about disk space with the Captured files you can always delete what you don't want to keep after posting them. Delete blank graphs any way.

[#10]

Quote from: Anotherone

The 582n may be managing things so far, but as I've already mentioned, the errors are high and this will mean a lot of data re-transmits and so reduced performance. Whilst what you see now may be a lot better than you've seen recently, it should still nevertheless be better still.

Hello Anotherone... I've setup the RouterStatsLite as you suggest and checked that all other settings are correct... the most recent captured graph is appended...
The most recent stats are:
Uptime: 2 days, 4:14:07
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 447 / 1,657
Data Transferred (Sent/Received) [GB/GB]: 1.00 / 4.53
Output Power (Up/Down) [dBm]: 12.0 / 16.7
Line Attenuation (Up/Down) [dB]: 37.7 / 67.5
SN Margin (Up/Down) [dB]: 8.9 / 7.1
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / TSTC
Loss of Framing (Local/Remote): 18 / 0
Loss of Signal (Local/Remote): 2 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 15,559 / 6
FEC Errors (Up/Down): 7,528 / 2,121,121
CRC Errors (Up/Down): 164 / 23,499
HEC Errors (Up/Down): 283 / 24,519

[#11]

Well done for that. If you can post any other previous graphs since the 582n has been on line that you haven't posted, it will at least mean I can look for general patterns. Especially things like that previous overnight event.

[#12]

Quote from: Anotherone

Especially things like that previous overnight event.

This is what it looked like at 3:06am today...
edit... sorry, this is actually yesterday, 14 Nov... between about 2:30am and 4:30am

[#13]

Graph no. 1: 14 Nov, 4:30-6:30am
Graph no. 2: 14 Nov, 6:30-8:30am
Graph no. 3: 14 Nov, 8:30-10:30am
Graph no. 4: 14 Nov, 10:30-12:30pm
Graph no. 5: 14 Nov, 12:30-2:30pm
Graph no. 6: 14 Nov, 2:30-4:31pm
Graph no. 7: 14 Nov, 4:30-6:30pm
Graph no. 8: 14 Nov, 6:30-8:30pm
Graph no. 9: 14 Nov, 8:30-10:30pm

[#14]

Graph no. 10: 14 Nov, 10:30-00:30am
Graph no. 11: 15 Nov, 00:30-2:30am
Graph no. 12: 15 Nov, 2:30-4:30am
Graph no. 13: 15 Nov, 4:30-6:30am
Graph no. 14: 15 Nov, 6:30-8:30am
Graph no. 15: 15 Nov, 8:30-10:30am
Graph no. 16: 15 Nov, 10:30-12:30pm
Graph no. 17: 15 Nov, 1230-2:30pm
Graph no. 18: 15 Nov, 2:30-4:30pm

[#15]

Graph no. 19: 15 Nov, 4:30-6:30pm