Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 [2]

Author Topic: Odd behaviour with US SNR levels ,is it a sign of a line fault or not  (Read 5518 times)

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33888
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: Odd behaviour with US SNR levels ,is it a sign of a line fault or not
« Reply #15 on: February 25, 2016, 10:26:10 PM »

Is there any chance that it could have been caused by bad weather or wind making it rub against something ;)

Openreach recently did a fix on a line that I look after for someone.  It was just general wear and tear over the years on the drop wire that came down the side of the house. It was causing audible problems on the voice though.
Also had an engineer repair something here in my BT66 which was basically oxidisation of the copper wires due to weather.     
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

tommy45

  • Reg Member
  • ***
  • Posts: 627
Re: Odd behaviour with US SNR levels ,is it a sign of a line fault or not
« Reply #16 on: February 25, 2016, 11:12:01 PM »

Well as the wire is held to the wall by several cable clips  from the grey bt66 to the DG bay widow where it enters the property(  Straight line of sight to the box, apart from a couple of places where it goes a little lower to run across the porch roof )  It's unlikely down to the weather as the cable doesn't move around even when windy causing the kink 80-90 degree bend in the cable at the point where the nearest cable wall clip is , which has resulted in the outer casing  splitting , the reason it split is probably down to ageing  as the pvc or whatever  the material used is,  down to UV from the sun  too as it turns brittle with ageing, So basically BT have had somewhere near the usable life from this 20+ yr old cable, even if it is better quality when compared to what BT use today
I'm in 2 minds of buying enough quality exterior shielded 2 or 3 pair solid copper cable and cable clips and replacing it myself  i already have some BT issue Gel crimps and know how to do the job,

It's either that or play dumb , report a PTSN fault to my Voice provider and hope their remote tests pick it up ,  there in the past has been some noise (popping) when doing the QLT .
« Last Edit: February 25, 2016, 11:16:26 PM by tommy45 »
Logged

tommy45

  • Reg Member
  • ***
  • Posts: 627
Re: Odd behaviour with US SNR levels ,is it a sign of a line fault or not
« Reply #17 on: March 29, 2016, 05:55:07 PM »

Just a small up date on  my developing line fault , SNR both US & DS has taken a hit, and the attainable rates accordingly

And even making a call has started  causing FEC errors on both us & ds at the same time & also now Error secs and crc's as well , and over the past couple of days  there have been bursts of error secs  at other times  (without phone use)  today is the highest amount of error seconds that i have seen since using MDWS
« Last Edit: March 29, 2016, 05:58:07 PM by tommy45 »
Logged

tommy45

  • Reg Member
  • ***
  • Posts: 627
Re: Odd behaviour with US SNR levels ,is it a sign of a line fault or not
« Reply #18 on: April 01, 2016, 01:28:37 AM »

Code: [Select]
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 28408 Kbps, Downstream rate = 79120 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79998 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 5.7 14.0
Attn(dB): 13.5 0.0
Pwr(dBm): 12.4 1.7
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 42
R: 10 16
S: 0.0971 0.3781
L: 20922 5374
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 63 0
TxQueue: 21 0
G.INP Framing: 18 0
G.INP lookback: 21 0
RRC bits: 0 24
Bearer 1
MSGc: 186 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 5.3333 0.0000
L: 48 0
D: 3 0
I: 32 0
N: 32 0
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 287000
OHFErr: 0 1
RS: 46727232 3458777
RSCorr: 39 6
RSUnCorr: 0 0
Bearer 1
OHF: 70972 0
OHFErr: 0 0
RS: 850926 0
RSCorr: 0 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 1 0
rtx_c: 207762 0
rtx_uc: 48311 0

G.INP Counters
LEFTRS: 1392 0
minEFTR: 79991 0
errFreeBits: 1961791783 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 175341327 0
Data Cells: 6623143 0
Drop Cells: 0
Bit Errors: 0 0

Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0

ES: 15 4255
SES: 11 1
UAS: 524 514
AS: 1140

Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 80080.38 20063.54

Bearer 1
INP: 4.00 0.00
INPRein: 4.00 0.00
delay: 3 0
PER: 16.06 0.01
OR: 95.62 0.01
AgR: 95.62 0.01

Bitswap: 68/68 0/0

Total time = 1 days 1 hours 21 min 0 sec
FEC: 6720344 41890
CRC: 591 4930
ES: 15 4255
SES: 11 1
UAS: 524 514
LOS: 1 0
LOF: 8 0
LOM: 0 0
Latest 15 minutes time = 6 min 0 sec
FEC: 5 5
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 34 1
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 119 119
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 1 hours 21 min 0 sec
FEC: 2858 18
CRC: 536 7
ES: 10 7
SES: 10 0
UAS: 501 491
LOS: 1 0
LOF: 8 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 18143 569
CRC: 0 115
ES: 0 102
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 18 min 59 sec
FEC: 39 6
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0


HELLO HG612
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 28408 Kbps, Downstream rate = 79120 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79998 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Discovery Phase (Initial) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
Medley Phase (Final) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
  VDSL Port Details   Upstream   Downstream
Attainable Net Data Rate:     28408 kbps     79120 kbps
Actual Aggregate Tx Power:        1.7 dBm      12.4 dBm
 =========================================================================================
  VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
  Line Attenuation(dB): 3.2 15.2 21.9   N/A   N/A 8.7 19.2 29.4
Signal Attenuation(dB): 3.2 14.4 21.1   N/A   N/A 11.6 19.1 29.4
SNR Margin(dB): 16.0 14.4 13.8   N/A   N/A 5.7 5.7 5.7
TX Power(dBm): -12.8 -28.5 1.6   N/A   N/A 8.1 7.8 7.0
A few  days further on, and i got a mysterious Re-sync which may have been initiated by DLM , There appears to be a some subtle changes  Such as the amount of interleave  decreasing from 16 to 8, and the DS Snr and Attainable increasing back to somewhere near what it was some 4weeks ago, It doesn't make sense to me why DLM  was lowering SNR attainable, and then partly restores things, as well as a few subtitle changes to the config

Logged

tommy45

  • Reg Member
  • ***
  • Posts: 627
Re: Odd behaviour with US SNR levels ,is it a sign of a line fault or not
« Reply #19 on: June 10, 2016, 03:19:05 PM »

Well i yesterday and today  some strange noise on the voice  service  even over the dial tone, only problem is it seems to stop after a short period  of around 30 secs ,I'm assuming that it may be on the E side pair  or at exchange  as i'm bot seeing and correlation on MDWS such as bursts of errors , unless i make a call , put doing a QLT or pressing a single digit and listening for 15 secs or so doesn't generate errors currently, maybe that dodgy joint is drying out  hence the noise bursts, I rang my voice provider who ran the obligatory line tests which found nothing ,I am getting deja vu of a previous fault that wasn't detectable  until the line failed altogether

Update Some progress at last hopefully, i picked up the handset on my phone earlier today and was greeted with a loud crackling sound over the dial tone which then became intermittent and fizzled out  whilst i was waiting for my voice provider to answer the call, they ran their line tests  and called me back, this time it found a earth type fault, so will progress the fault with BT OR , could this earth fault be at the exchange  ie battery?
« Last Edit: June 20, 2016, 05:56:21 PM by tommy45 »
Logged
Pages: 1 [2]