Draytek Vigor 130 and FTTC SNR setting increased sync

ChrisD. · 9 Oct 2017 at 11:17

Not sure if this will help anyone else, but I recently tried:

Code:

vdsl snr -50

And my downstream has gone from 55 mbit to near 70 mbit.

It's odd as with the normal BT modem it stays at 55. It's been stable like this for several weeks.

This may help any other 130 users with a long line. The cab is ECI, not sure if this makes a difference.

Code:

> vds sn
Usage:
vdsl snr [delta]
  delta: SNR margin delta. The SNR margin delta should range from -50 to 50.
  delta=1 means 0.1dB.
  Current VDSL SNR Margin is 3 dB.
  Current VDSL SNR Margin delta setting is -50.
> vds sn 0
VDSL SNR update successfully !
Restarting modem ...
>
> vdsl st
  ---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
   Running Mode            :      17A       State                : SHOWTIME
   DS Actual Rate          : 54811000 bps   US Actual Rate       : 18663000 bps
   DS Attainable Rate      : 55041624 bps   US Attainable Rate   : 18739510 bps
   DS Path Mode            :        Fast    US Path Mode         :        Fast
   DS Interleave Depth     :        1       US Interleave Depth  :        1
   NE Current Attenuation  :       16 dB    Cur SNR Margin       :        6  dB
   DS actual PSD           :     6. 7 dB    US actual PSD        :     6. 9  dB
   NE CRC Count            :        0       FE CRC Count         :    23533
   NE ES Count             :        0       FE  ES Count         :    21091
   Xdsl Reset Times        :        0       Xdsl Link  Times     :        2
   ITU Version[0]          : b5004946       ITU Version[1]       : 544e0000
   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 :       17 dB    Far SNR Margin       :        6  dB
   CO ITU Version[0]       : b5004946       CO ITU Version[1]    : 544eb206
   DSLAM CHIPSET VENDOR    : < IFTN >
> vds sn -50
VDSL SNR update successfully !
Restarting modem ...
>
> vd st
  ---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
   Running Mode            :      17A       State                : SHOWTIME
   DS Actual Rate          : 67000000 bps   US Actual Rate       : 18744000 bps
   DS Attainable Rate      : 73047816 bps   US Attainable Rate   : 18823266 bps
   DS Path Mode            :        Fast    US Path Mode         :        Fast
   DS Interleave Depth     :        1       US Interleave Depth  :        1
   NE Current Attenuation  :       16 dB    Cur SNR Margin       :        1  dB
   DS actual PSD           :     6. 7 dB    US actual PSD        :     6. 9  dB
   NE CRC Count            :        0       FE CRC Count         :    23533
   NE ES Count             :        0       FE  ES Count         :    21091
   Xdsl Reset Times        :        0       Xdsl Link  Times     :        3
   ITU Version[0]          : b5004946       ITU Version[1]       : 544e0000
   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 :       17 dB    Far SNR Margin       :        6  dB
   CO ITU Version[0]       : b5004946       CO ITU Version[1]    : 544eb206
   DSLAM CHIPSET VENDOR    : < IFTN >

SupraWez · 9 Oct 2017 at 11:36

Nice info, thanks.

kitfit1 · 14 Oct 2017 at 10:50

Just done the same:

It has made a difference. Will leave it as it is and see how it settles down over a few days.

Caged · 14 Oct 2017 at 13:17

I presume you're both on ECI cabinets? The Huawei ones are negotiating at 3dB by default now (or at least they attempt to).

kitfit1 · 14 Oct 2017 at 14:57

Caged said:
I presume you're both on ECI cabinets? The Huawei ones are negotiating at 3dB by default now (or at least they attempt to).

Yes, i think IFTN indicates an ECI cabinet.

thewanted · 14 Oct 2017 at 16:10

Damn, that's a big improvement @ChrisD. Would you mind posting your attenuation stats since your previous attainable sync rates are almost identical to mine, please?

I need to buy a new router quite desperately, so the Draytek 2860ac is now looking quite tempting (solution price aside).

EDIT: I know nothing about Drayteks. Is "NE Current Attenuation" the stat I'm looking for to compare to my HomeHub 5 below?

Line Attenuation: 33.4 / 23.4

Sparx · 14 Oct 2017 at 16:40

Very interesting, I currently achieve the below... When I first got FTTC about 3 years ago, I achieved the full 80/20 sync. However over time cross talk seemed to batter my sync down.

Do you think if I got one of these and hooked it up with my PN router, it could get me back at full 80/20 or close to?

My house is a new build from mid 2014, the copper was brand new laid 2 days after we moved in, so it's only 3.5 years old. DSL sync has always been brilliant and only seems to drop for any maintenance or the very rare power cut.

Code:

Downstream sync speed:
62.15 Mbps

Upstream sync speed:
16.94 Mbps

Maximum data rate:
61332 / 16938

Noise margin:
3.3 / 6.1

Line attenuation:
19.9

kitfit1 · 14 Oct 2017 at 17:13

Below is my previous modem stats prior to applying ChrisD's -50:

Type ? for command help
> vdsl status

---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 72792000 bps US Actual Rate : 20000000 bps
DS Attainable Rate : 73033112 bps US Attainable Rate : 23646200 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 1 US Interleave Depth : 1
NE Current Attenuation : 15 dB Cur SNR Margin : 6 dB
DS actual PSD : 4. 9 dB US actual PSD : 5. 1 dB
NE CRC Count : 11 FE CRC Count : 11564
NE ES Count : 7 FE ES Count : 10247
Xdsl Reset Times : 0 Xdsl Link Times : 1
ITU Version[0] : b5004946 ITU Version[1] : 544e0000
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 : 16 dB Far SNR Margin : 6 dB
CO ITU Version[0] : b5004946 CO ITU Version[1] : 544eb206
DSLAM CHIPSET VENDOR : < IFTN >

The stats below are my current stats after applying ChrisD's -50:

Type ? for command help
> vdsl status

---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 79995000 bps US Actual Rate : 20000000 bps
DS Attainable Rate : 89633208 bps US Attainable Rate : 22814806 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 1 US Interleave Depth : 1
NE Current Attenuation : 15 dB Cur SNR Margin : 3 dB
DS actual PSD : 5. 7 dB US actual PSD : 5. 8 dB
NE CRC Count : 215 FE CRC Count : 11074
NE ES Count : 156 FE ES Count : 6769
Xdsl Reset Times : 0 Xdsl Link Times : 2
ITU Version[0] : b5004946 ITU Version[1] : 544e0000
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 : 17 dB Far SNR Margin : 6 dB
CO ITU Version[0] : b5004946 CO ITU Version[1] : 544eb206
DSLAM CHIPSET VENDOR : < IFTN >

As you can see, a very significant difference. As i said earlier though, this will need to run for a while to see just how stable it actually is. Because i only applied -50 this morning it hasn't showed up yet in my Zen Portal and probably won't until tomorrow at the earliest.
Considering the short time it has been applied, there seems to be a lot of error counts, as long as this dosn't attract the attention of DLM it's not an issue.

Caged · 14 Oct 2017 at 17:35

Error correction results in a reduced throughput, though. So you'd be better off lifting your target SnR until the errors are not so numerous, since the desired outcome from all of this is a better connection, not just higher numbers on the sync stats.

Sparx: I wouldn't have thought that changing your modem would be able to get your speed back, that's unfortunately what crosstalk does. You'd see an improvement if/when vectoring arrives.

kitfit1 · 14 Oct 2017 at 17:50

Caged said:
Error correction results in a reduced throughput, though. So you'd be better off lifting your target SnR until the errors are not so numerous, since the desired outcome from all of this is a better connection, not just higher numbers on the sync stats

Yes' i know it does, which is why i'll leave it for a few days. I did a download of Ubuntu earlier on and got a constant 8.4Mbps, so it dosn't look as if the error count is causing reduced throughput as of yet.

JasonM · 14 Oct 2017 at 19:20

You can adjust the SNR on Drayteks, however go to low and you get more errors and disconnects. BT reduced it recently from 6db to 3db, but I have used SNR 30 to put it back to 6db as I prefer quality line over peak speeds

SupraWez · 14 Oct 2017 at 19:38

Picked one of these up last week, not tried it yet though.

kitfit1 · 14 Oct 2017 at 20:18

JasonM said:
You can adjust the SNR on Drayteks, however go to low and you get more errors and disconnects. BT reduced it recently from 6db to 3db, but I have used SNR 30 to put it back to 6db as I prefer quality line over peak speeds

I completely agree with what you say @JasonM. To be honest i expect to have to go back as well. But all lines are different, so it's always worth a punt and wait to see what happens.
In the dial up days we all used to do the same thing to gain a bit of extra speed, most of the time it never worked for me lol because of disconnects. As i said though, it's too early for me to make a call as to if this could be a long term setting.

ChrisD. · 15 Oct 2017 at 09:32

The cabinet is ECI, I did put this in my OP.

thewanted said:
Damn, that's a big improvement @ChrisD. Would you mind posting your attenuation stats since your previous attainable sync rates are almost identical to mine, please?

SNR is 3 db.

thewanted · 15 Oct 2017 at 12:11

ChrisD. said:
The cabinet is ECI, I did put this in my OP.

SNR is 3 db.

Thanks, but I meant your line attenuation stats

ChrisD. · 15 Oct 2017 at 12:13

It's all in the OP isn't it?

thewanted · 16 Oct 2017 at 08:07

ChrisD. said:
It's all in the OP isn't it?

I did say that I wasn't sure what I was looking at.

thewanted said:
EDIT: I know nothing about Drayteks. Is "NE Current Attenuation" the stat I'm looking for to compare to my HomeHub 5 below?

kitfit1 · 16 Oct 2017 at 17:57

thewanted said:
Thanks, but I meant your line attenuation stats

You mean this ? :

Type ? for command help
> vdsl status

---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 79995000 bps US Actual Rate : 20000000 bps
DS Attainable Rate : 89525640 bps US Attainable Rate : 22893857 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 1 US Interleave Depth : 1
NE Current Attenuation : 15 dB Cur SNR Margin : 3 dB
DS actual PSD : 5. 7 dB US actual PSD : 5. 8 dB
NE CRC Count : 2950 FE CRC Count : 11226
NE ES Count : 1699 FE ES Count : 6875
Xdsl Reset Times : 0 Xdsl Link Times : 2
ITU Version[0] : b5004946 ITU Version[1] : 544e0000
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 : 17 dB Far SNR Margin : 6 dB
CO ITU Version[0] : b5004946 CO ITU Version[1] : 544eb206
DSLAM CHIPSET VENDOR : < IFTN >
> vdsl snr

Usage:
vdsl snr [delta]
delta: SNR margin delta. The SNR margin delta should range from -50 to 50.
delta=1 means 0.1dB.
Current VDSL SNR Margin is 3 dB.
Current VDSL SNR Margin delta setting is -50.
> 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 : 0 0
VirtualNoise : 0 0
20BitSupport : 0 0
LatencyPath : 0 0
LOS : 0 0
LOF : 0 0
LPR : 0 0
LOM : 0 0
SosSuccess : 0 0
NCD : 0 0
LCD : 0 0
FECS : 154693 118073 (seconds)
ES : 1699 6875 (seconds)
SES : 0 21 (seconds)
LOSS : 0 79 (seconds)
UAS : 40 3041 (seconds)
HECError : 0 0
CRC : 2950 11226
RsCorrection : 0 0
INP : 0 0 (symbols)
InterleaveDelay : 0 0 (1/100 ms)
NFEC : 255 255
RFEC : 16 16
LSYMB : 5410 21451
INTLVBLOCK : 255 255
AELEM : 0 ----
>

ChrisD. · 17 Oct 2017 at 08:28

Code:

> v s 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   :      0               0
 VirtualNoise :      0               0
 20BitSupport :      0               0
 LatencyPath  :      0               0
 LOS          :      0               0
 LOF          :      0               0
 LPR          :      0               0
 LOM          :      0               0
 SosSuccess   :      0               0
 NCD          :      0               0
 LCD          :      0               0
 FECS         :   152087            242079 (seconds)
 ES           :    384            22377 (seconds)
 SES          :      0               0 (seconds)
 LOSS         :      0             110 (seconds)
 UAS          :     40            22377 (seconds)
 HECError     :      0               0
 CRC          :    495            24927
 RsCorrection :      0               0
 INP          :      0               0 (symbols)
 InterleaveDelay :      0               0 (1/100 ms)
 NFEC         :    255             255
 RFEC         :     16              16
 LSYMB        :   5026            17979
 INTLVBLOCK   :    255             255
 AELEM        :      0            ----

Mine.

r7slayer · 8 Dec 2017 at 12:51

I got this modem because my line seems to have been playing up. Was getting packet loss afaik. But it was weird like something randomly changed on my connection i was getting nice low pings. 14ms pings using ookla speed test while getting full sync speeds 80/20 and around 8ms in my team speak server. No packet loss from what i could tell at this time. However then all of a sudden my speed dropped slightly and my pings went from 14 to 20-22 ms using the ookla speed test and from 8ms to 16-17 ms in team speak. I noticed packet loss in team speak and using ping command in cmd prompt i saw odd packets dropped pinging google dns etc.

Only thing i saw change was my SNR which was just over 8SNR but my other half disconnected the plusnet home hub to plug in the hoover and this is when this all started happening. My SNR dropped to 5/6SNR and start experiencing the packet loss.

Saw i was getting errors on the line but since ive changed my SNR to 9 with the Vigor and ive seem to have got rid of the packet loss. However ive kept the higher pings and now my sync speed is around 67 Mbits/s instead of 80. Not sure how all this can have happened from one bloody disconnection of the router. Usually DLM will try to push the SNR up with instability not drop it down. Just glad my line is now stable for now. Got a open ticket with Plusnet but im doubtful they will do anything because im within the acceptable speeds and ive got my line stable my self