It looks like your firmware update hasn't fully completed.
I would suggest you should try again, ensuring the reset button is held down for 10 to 15 seconds when powering up the modem.
It is easy to accidentally release pressure on it & only achieve a 'partial' firmware update.
This is Wolfy's updated firmware version:-
xdslcmd --version
xdslcmd version 1.0
DSL PHY: AnnexA version - A2pv6C038m.d24j
******* Pass *********
Also your band plan tones haven't changed yet, there are still blue 'shared' tones showing in your bitloading graph.
This is how the pbParams data should look with the updated firmware version:-
Discovery Phase (Initial) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
Medley Phase (Final) Band Plan
US: (7,32) (871,1190)
DS: (33,859) (1216,1852)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 3855 kbps 21412 kbps
Actual Aggregate Tx Power: 6.9 dBm 12.4 dBm
====================================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 8.3 55.7 N/A N/A N/A 22.1 68.4 N/A
Signal Attenuation(dB): 8.3 55.0 N/A N/A N/A 31.4 68.4 N/A
SNR Margin(dB): 6.2 6.2 N/A N/A N/A 6.0 6.0 N/A
TX Power(dBm): 0.8 5.8 N/A N/A N/A 11.3 6.1 N/A
Also, the text shown in red should be present when the firmware has been fully updated:-
xdslcmd info --pbParams
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 3855 Kbps, Downstream rate = 21412 Kbps
Bearer: 0, Upstream rate = 3866 Kbps, Downstream rate = 21698 Kbps
The differences between our connection stats are visually obvious (I'm around 1100m from the cabinet so I'll never see great speeds), but I'll try to explain some of the more relvant stats:-
Discovery Phase (Initial) Band Plan
US: (7,32) (871,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
Medley Phase (Final) Band Plan
US: (7,32) (871,1190)
DS: (33,859) (1216,1852)
My connection 'Discovered' the relevant VDSL2 band plan tones, but due to distance from the cabinet, attenuation & possibly noise/crosstalk are too high for it to actually use all of them at 'Medley' phase.
The 'older' firmware version doesn't identify the current band plan tones correctly & doesn't distinguish between DS Line & Signal attenuation.
The higher Signal attenuation in my D1 band from the updated version indicates a loss of quite a bit of signal due to noise/crosstalk:-
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 8.3 55.7 N/A N/A N/A 22.1 68.4 N/A
Signal Attenuation(dB): 8.3 55.0 N/A N/A N/A 31.4 68.4 N/A
For my connection, that equates to a loss of around 10 Mbps from when it was able to sync at 32Mbps upward.
Minimum Target SNRM for VDSL2 connections is 6dB.
As our connections are in sync at not much above 6dB, it confirms that currently we are unlikely to be able to achieve higher sync speeds.
Users with SNRM of around 9dB or more could potentially achieve higher sync speeds (unless they have intentionally restricted sync speeds or DLM or the ISP has temporarily or permanently capped sync speed).
e.g. I have recently seen a connection with 9.6dB SNRM but sync speed had been capped due to a bridged tap effect at 19998 Kbps, with an attainable rate in excess of 26000 Kbps.
The D: data confirms DS & US Interleaving depth (1 = OFF i.e. fastpath):-
D: 1 1
You have a fairly high DS depth of 863 which will currently be restricting sync speeds.
ISPs have no control over Interleaving depths for VDSL2 connections, so that value will have been determined by DLM based upon error counts, number of resyncs etc. that it has seen.
If your connection was able to regularly sync at higher speeds, it would indicate that either the connection's physical properties have deteriorated or that noise/crosstalk has increased.
With Interleaving applied, Impulse Noise Protection (INP) & delay (Ping times) will have been added at varying levels.
AS my connection is currently operating on fastpath, these values are zero:-
INP: 0.00 0.00
delay: 0 0
When my connection had DS Interleaving set at a low depth of 371, these were applied at the first stage:-
INP: 3.00 0.00
delay: 8 0
As the need for deeper interleaving depth increases, these values will also increase.
I'm nott 100% sure when DLM makes the decision to increase interleaving etc.
Examining your data in the raw xdslcmd info --stats section of a Plink log will confirm at what level yours have been set.
Too high levels of errored seconds, CRC, HEC or RSUnCorr errors or too many resyncs in fairly quick succession will drive DLM to apply interleaving.
Fast path connections do not generally use FEC (Forward Error Connection) a.k.a. RSCorr or since the firmware was updated they sometimes use very low levels.
Interleaving & FEC can be good things as they drastically reduce errors that would mean data has to be retransmitted & can actually speed up actual throughput, despite sync speed being lower.
However, as gamers tend to require very low ping times to avoid being killed in an online game etc.
High levels of delay & INP as applied with interleaving aren't very helpful.
It is often 'better' for gamers to have lower sync speeds & thus lower error counts that tend to maintain fastpath connections.
Here endeth lesson #1.
I can't explain ALL the other stats, but let me know if you have any other queries.
I'll do my best to explain wherever I can.
I think I've seen your name in the Plusnet and/or TBB forums.
WWWombat occasionally visits those forums & he could give you a very detailed technical explanation behind all the stats, but the above might help with a basic understanding for now.
See the attached ongoing montage for how the error counts have changed since my connection reverted to fastpath.
TBH, I expect it won't be too long before interleaving is applied by DLM again.
Author
Topic: VDSL2 Connection Stats (Read 7517 times)