Hi BE, thanks for the reply
The best way would be to compare the raw telnet stats from xdslcmd info --stats & also xdslcmd info --pbParams.
I can only really give these from after the upgrade. Since the line got rock stable after the D-side pair switch I gave up monitoring after a few months until the recent firware upgrade (im on a huawei cab so fingers crossed for vectoring). The telnet data seems to concur with the web GUI (im on linux so run dslstats as well as a custom perl collector and RRDTool, too much hassle to fire up a windows VM and run the HG612 modem stats scripts unfortunately!)
Down Up
SNR (dB): 6.2 15.0
Attn(dB): 11.5 0.0
Pwr(dBm): 12.6 -1.6
old pbParams (form a year ago) are here
http://forum.kitz.co.uk/index.php?topic=12979.msg245243#msg245243, showing 7.1
New pbParams:
Max: Upstream rate = 22959 Kbps, Downstream rate = 72876 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 73107 Kbps
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,1205) (1972,2782)
DS: (33,859) (1216,1961) (2793,3970)
VDSL Port Details Upstream Downstream
Attainable Net Data Rate: 22959 kbps 72876 kbps
Actual Aggregate Tx Power: - 1.6 dBm 12.6 dBm
====================================================================================
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 2.8 12.7 19.2 N/A N/A 7.1 14.6 22.6
Signal Attenuation(dB): 2.8 11.8 18.3 N/A N/A 8.3 14.4 22.6
SNR Margin(dB): 15.2 15.0 15.0 N/A N/A 6.2 6.2 6.1
TX Power(dBm): -15.8 -30.9 -1.7 N/A N/A 8.7 7.8 7.0
Perhaps line conditions have improved, a distuber pair has been disconnected or the updated firmware reports things more accurately?
Im inclined to think the latter. Unless somehow the line significantly improved in the space of power down->firmware update->power up, but im guessing the probabilities of that happening are rather minimal
The web interface stats I posted in my previous post were copied right before the upgrade and right after.
so maybe the newer firmware makes more efficient use of all available tones?
c'est possible.
I'm slightly surprised that US SNRM is so high though as I would normally have expected US attainable rate to increase.
Me too, but it was right there in black and white - US SNRM doubled, and sync stayed the same (Though my line has always been a bit weird, you may notice my DS 'max rate' is always lower than the 'bearer' generally. no idea why, it stays stable at 72-73mbps usually.
I take it you are actually achieving the full 20 Mbps US sync speed?
80/20 and yes, its 19999 on the U path. Though I max out at 17mbps throughput, which is a bit less than the 10% I would expect. wireshark tells me its due to TCP re-xmits a-la TCPs normal throttling - only when under max use - they go away if i throttle the TCP stream manually own to say 14mbps. My guess is my U path has quite a bit of errors when at full chat (side note; my U path is the only one that generates FEC and CRC / ES nowadays)
I do still see those massive dips in SNRM (only on upstream) that I mentioned in my post from last year, when the phone is off the hook. They still reduce the SNRM by up to 7db sometimes, but now with this new 15dB margin that still leaves bags of room. Before the firmware upgrade, when we were on the phone my upload throughput would go down drastically (about 8 to 10 meg max upload when phone was off hook, 17 max when on hook), but since the firmware change the dips still happen, but throughput remains solid 17's even when off hook.
Please see the 2014-09-02 upstream SNRM graph attached for current SNRM (and an example of the 'off hook dip'). Ive also attached a US SNRM graph from october '13 and current bitloading. To be fair today's bitloading on the US doesnt look overly different from before the D-side switch in Oct13 (though you can see the improvement in the D paths the D-side pair switch made!). Old bitloading from Oct 13 is here
http://forum.kitz.co.uk/index.php?topic=12979.msg245197#msg245197Im thinking that your theory about more efficient use may be the winner here? Is the binary blob in this firmware release different to Asbokids release from Sept last year?