I believe the Thomson TG585v7 is known to misreport output power - i tend to see the figure at 0 or 25.5db for the downstream output power.
In a way thats a shame, as it could have explained the drop in attenuation. Output power is a measurement of power transmitted from the MSAN, which affects the strength of the adsl signal and can also make the line more vulnerable to fluctuations in SNR if its too low.
Leaving the router off overnight wont make any difference to the figure, but I have known some routers mis-report, which is why I asked if you can recall if it ever seemed to record properly when on BE.
For adsl2+ it should be 18/19/20dBm, and the DSLAM can ramp the power up a bit if theres lots of bit-swap. Anything less and you are unlikely to get full bitloading, its seldom you ever see it at more than 20dBm.
If you see 0, then yes its false reporting, because the line just would not work if that figure was true
Have had DSLstats running for over 24h now
Thank you. At first glance of the graph it is showing symptoms of REIN.
Closer inspection of the SNRm shows some odd upstream spikes at circa 18:05, 19:20 and 20:05 which we sometimes see if there is a line fault and the telephone rings. However, I note you say that the phone wasnt in use, so taken with the downstream variance, it could possibly be
SHINE.
Just for the sake of completeness, can you advise if the line lost sync at those times? The 'Connection Speed' tab may show this as its unlikely to have retrained at exactly the same sync speed. Whilst at the Connection speed tab, it may be interesting to tick the 2 check boxes to also record the max attainable values.
REIN and SHINE do sometimes go together. From the graphs its possible that your upstream is affected by SHINE when 'something' is first switched on and shows a spike, whilst the downstream is affected for the period of time the cause remains switched on.
Your CRCs during this period are going crazy. From the graphs, it looks like the figures are clipped at 30, but in reality are much more (You can change the clipping value and/or turn it off, but the graph shows the effects either way).
Your bit loading graph, shows that you possibly do have a small amount of crosstalk. If your SNR per tone follows the same pattern, then its centered around tone 225 which is the 7/8Mb speeds.. and is exactly where Id expect a short line to see the most effects, so all looks normalish as far as crosstalk is concerned.
Whether its the state of your internal wiring that is causing the connection to be more sensitive to REIN I dont know.
The bell wire is the usual culprit for acting as an antennae for REIN.There are many causes of REIN, it doesn't necessarily have to be in your own house, weve seen many cases where its neighbours equipment that has been the culprit.
if I got this plate fitted would it cause problems with that in future?
I'll leave the other guys to discuss the internal wiring & face plates as they are already on it... but personally speaking if you can get it normalised to an SSFP, then no it wont affect VDSL. In fact BToR Engineers will normally fit an SSFP Mk3 as part of a managed FTTC install. I had previously installed my own SSFP several years before getting FTTC. No BT wont scold you for removing the bell/ring wire.
Im not too sure if its a good idea to get FFTC yet though whilst the line is in its current state. (noted that its ready but not available). I had a fault develop literally the day after I ordered FTTC. (FTTC and the Sky takeover of the BE MSANs happened at the same time here). Its going to be much harder when on FTTC to prove that your line isnt performing as it was.
I dont know the exact location of your cab, but based on the similarity of your BE adsl2+ stats to my own, then Id anticipate you should easily get 80Mpbs plus on vdsl. What was a very obvious fault on adsl2+, became much harder to prove on vdsl, because you should get lots of 'spare' SNRm for such a short line. This can mask SNRm variances and errors, that wont really affect the line until VDSL crosstalk also starts to kick in. By which time it will just all be lumped together and you will be told nothing they can do for crosstalk.