Post deleted by witchunt

You misunderstand how this works and how it's deployed.
Vdsl2 has its own vectoring
G.Fast has its own vectoring.
Neither work with each other. They are completely different technologies run from separate cabinets.
The G.Fast pod is bolted to the PCP, not to the fibre cabinet.
They don't talk to each other and only share a power supply.

A G.Fast pod with vectoring being added to your PCP will not randomly give vectoring to the FTTC cabinet, or any of its users.
Vectoring is entirely optional on VDSL2/FTTC
It is mandatory on G.Fast.

edit: a little more on the technology.

Vectoring units are integrated with their DSLAMs. It receives information from all the modems connected to the DSLAM measuring the crosstalk/noise/interference each line receives. It then performs a massive amount of computer processing and fancy algorithms to work out how best to reduce this. It seems "anti-phase signals" to cancel out the crosstalk signals. This results in almost no noise on a line. This allows more bits/tones to be used which increases sync.

As the G.Fast DSLAM and the VDSL2 DSLAM are completely independent there's no way for some form of cross-vectoring to work. It might not even be technically possible as they are 2 very different forms of DSL.
VDSL2 (along with all its ADSL predecessors) use something called Frequency Division Duplex.
G.Fast uses Time Division Duplex.

Edited by j0hn83 (Fri 26-Jan-18 16:10:49)

In reply to a post by j0hn83:

You misunderstand how this works and how it's deployed.
Vdsl2 has its own vectoring
G.Fast has its own vectoring.
Neither work with each other. They are completely different technologies run from separate cabinets.
The G.Fast pod is bolted to the PCP, not to the fibre cabinet.

The last line is the only bit I forgot about - I understood the rest, I was agreeing with you all. I don't see how it could have been interpreted differently. I was trying to clear up the confusion that someone else had about G.Fast adding vectoring to the rest of their DSLAM (and like I said, I made the mistake of thinking that the G.Fast pod was connected to the DSLAM in that post... which probably led to all the confusion actually, sorry).

Ironically, the original post was about an AIO cab!

Edited by deleted (Sat 27-Jan-18 22:57:49)

Thanks to a faulty slow cooker, we had a couple of power cuts over the weekend. I checked DSLStats this evening to see if that had caused problems with DLM and the opposite seems to have occurred.

Sync has returned to 79987/19999 with an attainable rate of 98632/22206, which considering the 400m line length is pretty respectable. As you might expect with those speeds, vectoring is also showing as 1 (VECT_FULL) again.

So no idea what caused it to switch off initially, but it must still be activated at the cabinet anyway and a re-sync has enabled it on the line again.

In reply to a post by j0hn83:

Vectoring units are integrated with their DSLAMs. It receives information from all the modems connected to the DSLAM measuring the crosstalk/noise/interference each line receives. It then performs a massive amount of computer processing and fancy algorithms to work out how best to reduce this. It seems "anti-phase signals" to cancel out the crosstalk signals. This results in almost no noise on a line. This allows more bits/tones to be used which increases sync.

Correct, and this is why it takes longer for modems to resync with the cabinet.

In reply to a post by Toonshorty:

So no idea what caused it to switch off initially, but it must still be activated at the cabinet anyway and a re-sync has enabled it on the line again.

Sounds like the router was at fault then. It is highly unlikely that vectoring would�ve been turned off, normally once it�s activated, it is for good.

Edited by deleted (Mon 05-Feb-18 21:49:22)