DrayTek UK Users' Community Forum
Help, Advice and Solutions from DrayTek Users
Draytek Vigor130 issues on BT VDSL2
- leoveo
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 3
- Thank you received: 0
11 Jan 2020 13:53 #1
by leoveo
Draytek Vigor130 issues on BT VDSL2 was created by leoveo
Mid December my BT VDSL2 connection suddenly started playing up. It had gradually dropped down over 2019 from training at about 65 Mbit/s to about 20 Mbit/s but it suddenly couldn't stay connected for more than a few minutes. BT said I had over 800 disconnects a day so they sent an OpenReach engineer.
The engineer measured the connection between the connection box on the front of the house and their cabinet and that was fine on a couple of metrics. He then replaced the master socket to the latest model (with built in filter) and the metre of cable between that new master socket and the connection box on the front of the house. He also reset the DSLAM and speeds went right up. We assumed it was now fixed and he left me with a 70 mbit/s connection that was stable for about 24 hours.
Within days the issue came back and OpenReach sent the same engineer to have another look. He measured no problems on the line but moved our connection to another port on a different board in the cabinet. This hasn't really helped all that much, the connection goes down every six hours or so.
I am starting to believe the problem might be with the Vigor 130. My cabinet seems to be a Huawei one and the connection "Fast" with G.INP support. The cabinet is perhaps 200 metres away, not that far. I am using the 1.8.4 BT firmware from February 2019 in 1483 Bridged IP LLC mode, VPI=0, VCI=38, Modulation=Multimode, MTU=1520. The 'alternative' firmware doesn't sync at all so that's no solution.
Is there anything I should change for the Vigor 130 to work better?
The engineer measured the connection between the connection box on the front of the house and their cabinet and that was fine on a couple of metrics. He then replaced the master socket to the latest model (with built in filter) and the metre of cable between that new master socket and the connection box on the front of the house. He also reset the DSLAM and speeds went right up. We assumed it was now fixed and he left me with a 70 mbit/s connection that was stable for about 24 hours.
Within days the issue came back and OpenReach sent the same engineer to have another look. He measured no problems on the line but moved our connection to another port on a different board in the cabinet. This hasn't really helped all that much, the connection goes down every six hours or so.
I am starting to believe the problem might be with the Vigor 130. My cabinet seems to be a Huawei one and the connection "Fast" with G.INP support. The cabinet is perhaps 200 metres away, not that far. I am using the 1.8.4 BT firmware from February 2019 in 1483 Bridged IP LLC mode, VPI=0, VCI=38, Modulation=Multimode, MTU=1520. The 'alternative' firmware doesn't sync at all so that's no solution.
Is there anything I should change for the Vigor 130 to work better?
Please Log in or Create an account to join the conversation.
- leoveo
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 3
- Thank you received: 0
11 Jan 2020 13:55 #2
by leoveo
Replied by leoveo on topic Re: Draytek Vigor130 issues on BT VDSL2
Here are my stats:
Vigor> vdsl status
ATU-R Info (hw: annex A, f/w: annex A/B/C)
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 66997000 bps US Actual Rate : 18999000 bps
DS Attainable Rate : 77541652 bps US Attainable Rate : 25042000 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 1 US Interleave Depth : 1
NE Current Attenuation : 9 dB Cur SNR Margin : 8 dB
DS actual PSD : -5. 0 dB US actual PSD : 12. 6 dB
NE CRC Count : 90 FE CRC Count : 106442
NE ES Count : 18 FE ES Count : 11145
Xdsl Reset Times : 0 Xdsl Link Times : 148
ITU Version[0] : fe004452 ITU Version[1] : 41590000
VDSL Firmware Version : 05-07-06-0D-01-07 [with Vectoring support]
Power Management Mode : DSL_G997_PMS_L0
Test Mode : DISABLE
ATU-C Info
Far Current Attenuation : 9 dB Far SNR Margin : 9 dB
CO ITU Version[0] : b5004244 CO ITU Version[1] : 434da4a1
DSLAM CHIPSET VENDOR : < BDCM >
Vigor> vdsl status more
ATU-R Info (hw: annex A, f/w: annex A/B/C)
Near End Far End Note
Trellis : 1 1
Bitswap : 1 1
ReTxEnable : 1 1
VirtualNoise : 0 0
20BitSupport : 0 0
LatencyPath : 0 0
LOS : 14 28
LOF : 28 0
LPR : 0 14
LOM : 0 0
SosSuccess : 0 0
NCD : 0 0
LCD : 0 0
FECS : 0 25690 (seconds)
ES : 18 11145 (seconds)
SES : 1 3148 (seconds)
LOSS : 0 0 (seconds)
UAS : 27 53194 (seconds)
HECError : 0 0
CRC : 90 106442
RsCorrection : 0 0
INP : 275 215 (symbols)
InterleaveDelay : 0 19 (1/100 ms)
NFEC : 32 32
RFEC : 16 16
LSYMB : 16 16
INTLVBLOCK : 32 32
AELEM : 0 ----
Please Log in or Create an account to join the conversation.
- jpgrove
- Offline
- Banned
-
Less
More
- Posts: 3
- Thank you received: 0
11 Jan 2020 20:20 #3
by jpgrove
Replied by jpgrove on topic Re: Draytek Vigor130 issues on BT VDSL2
Adjusting your SNR margins may improve stability, but doing so can kick in DLM. I had similar issues, my understanding is that your SNR margin is set at 6db regardless, adjusting mine took my speed from 56 to 72 now stable for 300 plus hours. There is a post on the overclockers forums about how to adjust the margin manually, but you may find the DLM shows no mercy even on a relatively clean line, or you have bad crosstalk which may be local
Please Log in or Create an account to join the conversation.
- leoveo
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 3
- Thank you received: 0
15 Jan 2020 09:51 #4
by leoveo
Replied by leoveo on topic Re: Draytek Vigor130 issues on BT VDSL2
Thanks, I'll look into it.
I have to say that I probably always misunderstood SNR in relation to DSL as I assumed the higher the better. The OpenReach engineer actually said that about 6dB is the sweet spot and the high figures I saw (up to 28 dB at its worst!) are actually a sign of trouble. If the line is poor the devices on both ends of the line agree to raise SNR in the hope of getting a more stable line. Seeing a high SNR is a sign of a poor line.
That said, my line has been stable for about 20 hours now and SNR has crept up to 10 dB so perhaps I just needed a little higher to make the line work.
I have to say that I probably always misunderstood SNR in relation to DSL as I assumed the higher the better. The OpenReach engineer actually said that about 6dB is the sweet spot and the high figures I saw (up to 28 dB at its worst!) are actually a sign of trouble. If the line is poor the devices on both ends of the line agree to raise SNR in the hope of getting a more stable line. Seeing a high SNR is a sign of a poor line.
That said, my line has been stable for about 20 hours now and SNR has crept up to 10 dB so perhaps I just needed a little higher to make the line work.
Please Log in or Create an account to join the conversation.
Moderators: Sami
Copyright © 2024 DrayTek