|
|
|
It's been a while since I posted on here, had a relatively stable connection for a quite a few years, until about 3 weeks ago when I started get drop-outs regularly average about 10-20 drops per day, with the occasional drop-free periods of 1 or 2 days then the drops start up again.
Had a BT (Openreach) engineer call and tested the line and he found that a part of my physical line is "grounding" but it is a part that they cannot touch because it has been put behind some external cladding insulation. a solution to that little problem is still being mooted between my Housing association and BT. But, in the mean time I wanted an opinion from someone who has more knowledge of these things about the Line stats from my HH3
Also my line used to be 'FAST' latency but is now 'interleaved'.
ADSL Settings
VPI/VCI: 0/38
Type: PPPoA
Modulation: G.992.5 Annex A
Latency type: Interleaved
Noise margin (Down/Up): 8.9 dB / 5.7 dB
Line attenuation (Down/Up): 33.1 dB / 20.6 dB
Output power (Down/Up): 20.6 dBm / 12.4 dBm
FEC Events (Down/Up): 373327 / 1456
CRC Events (Down/Up): 186 / 316
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): 2382 / 326
Error Seconds (Local/Remote): 7348 / 2494
Thanks
|
|
|
Without actual connection speed data it is hard to say other than the following:
1. Slight mismatch in upstream and downstream attenuations.
2. Interleaving is doing its job and correcting transmission errors
3. Lots of errored secords, but depends on how long ago the count started at zero
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
Ha, thought I'd copied all of it, seems I didn't
Connection Information
Line state: Connected
Connection time: 1 days, 21:46:15
Downstream: 10.43 Mbps
Upstream: 1.085 Mbps
Would the count start at zero from the last reconnect? or when the HH was rebooted?
Edited by deleted (Thu 21-Mar-13 12:25:45)
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
Zero would be 1 day 21 hours ago roughly
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
http://www.coolwebhome.co.uk/calc/calculator.php?par...
Range of expected speeds would be 11500 to 15000 Kbps for the attenuation, so below that. A lower target margin would boost speeds, but that would increase error rates
So yes a clear sign of a problem, with around 1 in 12 seconds creating an error that impacts on throughput.
Solution sounds like remove cladding to fix line, or a new drop wire.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
Cheers Andrew, appreciate the thoughts  I now hope that the powers that be come to some sort of agreement over cabling.
Thanks again
|
|
|
One option if the incoming drop wire contains a spare pair is for BT to swap you over, it may work better - or it may not.
But as a short term way to improve things it is something I would have expected Openreach to have already done, but worth checking that they did as it can be overlooked.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
|
He did try me on the other pair but the noise was much worse so put me back on the original ones.
|
|
|
Zero would be 1 day 21 hours ago roughly Not necessarily!
1d 21h ago is when last re-synced, but errors are usually zeroed only on reboot.
Only way to reliably monitor errors is to hard reboot and then take readings.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC
|