Tony, I'm really liking the updated vectoring display, much nicer than the old one . Just as a suggestion, presuming it fits would it not be more descriptive to have "Vectoring Upload Not Supported" rather than "Vectoring Not Supported" when an uploader is using HG612 Stats?

Tony, I'm really liking the updated vectoring display, much nicer than the old one . Just as a suggestion, presuming it fits would it not be more descriptive to have "Vectoring Upload Not Supported" rather than "Vectoring Not Supported" when an uploader is using HG612 Stats?

Tried originally and doesn't fit in various ways but you obviously understand what the short version means. The hover tells the full story. Both roseway and I have tried to contact BE1 but he's not been around for at least a year.

Tried originally and doesn't fit in various ways but you obviously understand what the short version means. The hover tells the full story. Both roseway and I have tried to contact BE1 but he's not been around for at least a year.

I will monitor and see if that swapping reduces in frequency over the coming days or indeed stops

I don't think it will stop as explained earlier in this thread by Chrysalis:

Quote

Vectoring has 2 operating modes.

One of the modes makes it so a modem can transmit vectoring compatible signals so it wont crosstalk to fully enabled vectored lines, the other mode is full vectoring where not only does it transmit compatible signals but it can also utilise other vectored signals to kill crosstalk. I believe the 1 state is fully vectoring, the 3 state is vectoring compatible signal but no active crosstalk mitigation

Unfortunately the sampling rate at one minute intervals is probably too slow to see how long it actually stays in each state. You'd need to run a copy of DSLStats sampling as fast as possible and keep an watch on the state but you can't do that with an upload to MDWS...

One of the modes makes it so a modem can transmit vectoring compatible signals so it wont crosstalk to fully enabled vectored lines, the other mode is full vectoring where not only does it transmit compatible signals but it can also utilise other vectored signals to kill crosstalk. I believe the 1 state is fully vectoring, the 3 state is vectoring compatible signal but no active crosstalk mitigation.

This explanation for the different states is clearly wrong. There are different levels of vectoring support, either G.993.5 "full" vectoring giving you crosstalk cancellation and a speed boost, or the vectoring friendly modes described in G.993.2 where only other lines benefit. I don't think it's even possible for your line to alternate between full vectoring and vectoring friendly while remaining connected. If it were possible, it would make little sense to be cancelling the crosstalk for your line much for the time, but then occasionally stop doing that at intervals. Therefore I don't think the vectoring state refers to full vectoring vs. vectoring friendly.

I think state 3 VECT_RUNNING probably indicates that the modem is currently doing something (perhaps sending the error samples) at the particular moment you're checking the state.

Not sure just how useful this be be, but I'll post anyway to show a little of what I've observed with vectoring.

What I did was collect the output of xdslctl info --vectoring at 5-second intervals over a ~four [hour] period between 19:50 and midnight, and log key output including the vectoring state, the packets sent or discarded, and the status sent or discarded.

The following is a summary count of each of the states observed during that time:

I think state 3 VECT_RUNNING probably indicates that the modem is currently doing something (perhaps sending the error samples) at the particular moment you're checking the state.

I agree with ejs based on what I saw. When in state 1 the packets sent value does not change. When in state 2 or 3 the packet and status counts increase. For example the following shows the transition from state 1 to 3 and back to 1: