I fitted the new VDSL MK3 plate last week, and got some basic stats from the router. I also changed a few settings along the way, and did some tests. Summary : it made a slight difference, but not much. And the TalkTalk DSL3680 (firmware v1.13t) possibly has a reporting bug.
Sync Attn. S/N
Setting Reported UP DOWN UP DOWN UP DOWN
============== ======== === ==== == ==== == ===
Plug in filter G.DMT 896 6560 25 38 7 6
VDSL MK3 G.DMT 896 6528 25 38 7 6.5
Force ADSL2 G.DMT 960 7424 23 37.5 7 6
Force ADSL2+ G.DMT 928 7360 23 38 8 6
auto G.DMT 928 6656 25 37.5 7 6
ADSL2 G.DMT 960 7392 23 37.5 7 6
reboot unchanged G.DMT 928 7328 23 37.5 7 6.5
worst to best results 64 832 2 0.5 1 0.5
1st test was with existing plug in filter into standard NTE5A. I then removed the filter, removed the NTE5A and remade the connections inside (seemed a touch loose) and fitted the VDSL MK3. I also replaced the router cable with a slightly better twisted pair one (original was VERY thin indeed). I squirted all contacts with contact cleaner.
Comparing the 1st and 2nd tests (before and after VDSL) you can see that this didn't really make any difference. Perhaps because I'd not waited long enough for the contact cleaner to dry, as subsequent tests showed a small improvement with the same router settings.
I then changed the ADSL mode from auto to ADSL2, as suggested by burakkucat. After a reboot, the router still reported it was using G.DMT mode - I double checked, I had set it to use ADSL2. And note the curious thing - the attenuation UP consistently drops from 25 to 23 when I've set the router into ADSL2 or 2+ mode, even though it's reporting the connection as G.DMT. When I set it back to auto, the attenuation jumps back to 25 again. So I'm unclear what mode it was actually connecting in! Router reporting bug, or actually choosing to use g.dmt regardless (but then why did the attenuation change consistently?)
So, slightly worth doing, and it looks tidier, but didn't gain much overall.
Thoughts?
Ian