TG582 on 20CN

[#1]

I'm not going to comment on what is being tried as I think it would be more appropriate for Plusnet to make a statement if it is successful (we are trying more than one thing).
I think it would be helpful if anyone else is seeing the same as me could post because that would allow further testing if we find something that works for me.
If something we try is not successful I will post so people know what doesn't work.

[#2]

Re RSL, 'Cos that was an either or question really and  Lite would have been quicker to setup, if you hadn't already done RouterStats which I do know runs with the 582n    What do you think I have on my Desktop    Well you could change the sample rate to 10 seconds. I assume that both the Sync speed and Noise Margin go to zero, and I still say it broken if it syncs at 8192 on 20CN as that's 64kbps more than 20CN can supposedly do 

[#3]

Just double checked - I was seeing what I expected.
It's actually syncing at 8128 which ties up with the BT speed test reporting it as 8.13Mbps

PS Had anyone noticed that at the bottom of the front page of http://www.speedtester.bt.com/ it says:

Quote

Note : Have you tried our new BT Wholesale speed test website -www.speedtest.btwholesale.com.

[#4]

Anyone any comments to make on these stats, particularly the number of errors in relation to the connection time?
Uptime: 1 day, 17:39:30
DSL Type: ITU-T G.992.1
Bandwidth (Up/Down) [kbps/kbps]: 832 / 8.128
Data Transferred (Sent/Received) [MB/GB]: 145,14 / 1,00
Output Power (Up/Down) [dBm]: 12,3 / 20,0
Line Attenuation (Up/Down) [dB]: 9,0 / 18,0
SN Margin (Up/Down) [dB]: 14,0 / 9,6
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / TSTC
Loss of Framing (Local/Remote): 0 / -
Loss of Signal (Local/Remote): 0 / -
Loss of Power (Local/Remote): 0 / -
Loss of Link (Remote): -
Error Seconds (Local/Remote): 49 / -
FEC Errors (Up/Down): 37 / 12.930
CRC Errors (Up/Down): 7 / 63
HEC Errors (Up/Down): - / 256

[#5]

I'd say the numbers of CRC and HEC errors are trivial for over a day connected. Also the FEC errors though in my experience and what I've seen posted Thomson routers seem to count these up for something to do. My ADSL2+ connection with TG585v8 runs up around 2000 CRC errors per day. That rate doesn't appear to bother the DLM. It's set minimum depth interleaving on my line just short of turning it off. It did turn it off when my target SNRM was 3dB higher.
I wonder if the dash values are actually negative where the TG585 used to report 4 trillion. If this applies the telnet interface (or the Routerstats stats page) show the number with a minus sign. (Negative values are obviously nonsense - presumably result from storage not being properly reset.)
You should get good speeds when you are moved to ADSL2+.

[#6]

With a 9db SNR I'm not sure I would have expected quite that number of errors.
What does the SNR drop to at night ?
I would also have expected a better SNR with that attenuation, I used to get 9db on 20CN on a 28db line when synched at 8128k.

[#7]

I've set RouterStats to plot the FEC errors. I wish I knew what happened just after 10:35!

[#8]

@MisterW
SNR drops very little at night, maybe 0.5db (it's all underground which I guess helps).
The SNR I'm getting is very, very close to what I was getting from the Netgear before I swapped over.

[#9]

Quote

I wish I knew what happened just after 10:35!

Wow, that's a big burst of errors ???.
That could explain the high total. Other than the burst at 10:35, the rest of the time it looks fine.
Is that the only burst during the day, and I don't suppose it's every day is it ?

[#10]

I only started graphing the FEC errors last night when I saw they had gone up by quite a lot from when I last looked. I'll be watching this closely from now on.

[#11]

The FEC errors indicate Interleaving is on, that's about all you can say about them 

Quote from: spraxyt

...... the FEC errors though in my experience and what I've seen posted Thomson routers seem to count these up for something to do.

Pretty much my observation
However, it would be nice to know how/when they change, so monitoring them could prove interesting. But I'd monitor the HEC errors as well and see if they change as the same time. I was a little surprised to see the HEC errors higher than the trivial level of CRC errors though. No noise on your line? You might consider a filter swap if things get interesting. See if phone usage has any effect.

[#12]

On my connection (20CN at the time) the CRC and HEC error counts with a TG585v7 were of equal magnitude. When I changed to a TG585v8 the CRC error count was similar but the HEC error count increased 10-20 times. The DLM didn't appear to bother about that.
That discrepancy continued on migration to 21CN ADSL2+. Currently with 25 days 1 hr uptime CRC error count is 51,916, HEC error count 1,020,459 (FEC errors 60,585,756 for the record).

[#13]

Time has come to comment on what fixed this problem: upgrading the router firmware to 10.2.2.9.
Following the router firmware upgrade I didn't have a single further drop of sync on 20CN.
Not long after my exchange was upgraded to 21CN. Since then I've been monitoring the stats closely. I was also sent a second TG582 which has the standard 8.4.4.J firmware (in case my original problem was a hardware fault).
I'm finding the router with the 10.2.2.9 firmware will hold a higher sync rate.

[#14]

Does that 10.2.2.9 have the Demo watermark I've seen mentioned elsewhere?

[#15]

Yes