21CN Training Question

[#1]

There is an exchange 750m away and another 3.5km. I'm on the latter.

[#2]

That's a little unfortunate....does make you wonder why it was done like that I suppose.

[#3]

Thanks for info everyone,  I could now do with some help interpreting my Netgear Debug information.
There are two lines of interest
Status: ShowtimeRetrain Reason: 0
Training Status: Showtime
This is what it has said since I joined the trial and I am now past the first 10 days training, so I was expecting the information to have changed.
Therefore is the line still training or has it never trained in the first place or am I just an idiot misinterpreting the information?
Thanks
Rich

[#4]

I don't think those router messages have anything whatsoever to do with training or the training period in the sense that you mean it. In those messages "training" is to do with syncing with the exchange, negotiating sync speed to match the target SNR Margin set by the exchange and choosing the "best" ADSL protocol (ADSL2+, ADSL2, G.DMT).
"Status: ShowtimeRetrain    Reason: 0" means the router needed to sync and Reason 0 was the cause of this (I'm not sure what 0 signifies (had it just been powered up at sync time - some days ago - cold start?))
"Training Status: Showtime" means the router is now in its normal fully synced operational state"
David

[#5]

Thanks David, so I was being an idiot misinterpreting the info 

[#6]

Just to add an interesting (to me, at least) bit of info on the relationship between MSR and FTR:
When I had my open ticket about my line speed and stability, fault tests were run on several occasions (May-June this year). Here's a selection of data from them
Date    Down sync    BRAS    MSR recalc?  MSR    FTR     Comments
20/5     Not recorded 2500          N                2272    2272
22/5        3068            2500          N                2272    2272    On banded profile
27/5        4148            2250          N                2272    2272    Banding removed
1/6            N.R.            2250          N                2272    2272
5/6           3068            2250          N                2272    2272    Banded
10/6        5152             4500         N                 2272    2272    Banding removed. 4500 isn't a typo!
16/6        3068             2250         N                 2272    2272    Banded
So, on my line FTR is 100% of MSR. And this never gets recalculated.
Is this a bug or a feature?
Graham

[#7]

Sorry about the messy alignment in my contribution above. It looked better than that when I was typing it. Should have used 'preview', I guess.
Graham

[#8]

@grahamt you can use code tags to use a fixed width font so tables like that will look as you want - it's the button with the hash symbol on it on the compose message screen.

test heading | test heading 2 | end
-------------+----------------+----
1            |  4             | 7   
2            |  5             | 8  
3            |  6             | 9   

[#9]

OK - I'll do that in future:

    just
    like
    this

More substantively, do you have an explanation of why my MSR and FTR are the same?
Graham

[#10]

They shouldn't be.  That would be a no
The BT site that gives out those details is being non responsive for me currently, so I'll be happy to check again later on.

[#11]

Did you ever manage to check this, James? No big problem if you didn't - I'm just curious.
Graham

[#12]

I hadn't but have now
Bizarrely - MSR & FTR *were* 2272
However, MSR is now (as of the 17th) 2848Kbps with an FTR of 2278Kbps.

[#13]

Quote from: orbrey

@grahamt you can use code tags to use a fixed width font so tables like that will look as you want - it's the button with the hash symbol on it on the compose message screen. test heading | test heading 2 | end -------------+----------------+---- 1            |  4             | 7    2            |  5             | 8  3            |  6             | 9

Or he could use pre tags (the button immediately to the right of ) if he doesn't want it in a box:

test heading | test heading 2 | end
-------------+----------------+----
1            |  4             | 7   
2            |  5             | 8  
3            |  6             | 9   

[#14]

Thanks to James for getting my MSR recalculated - it's comforting that the maximum stable rate went up rather than the fault threshold rate going down! Those figures now look to be in line with what I'd expect from a line that is capped (by the infamous banded profile) at a top sync speed of 3069.
And thanks to jelv for the extra formatting tip.
Graham

[#15]

I don't know whether when James forced the recalculation of my MSR and FTR the other day it had the side-effect of removing the banding from my line - but yesterday evening (the router hadn't been on during the day) the line was syncing at just over 4500. When I checked, though, it was already dark and, as expected, my SNR was down to 2. It shuffled between 0 and 3 (see picture) until I switched the router off at 10.30pm.
I was hoping that if I turned the line off before it became unusable I could switch on again this morning and still have an unbanded speed. No such luck. Back to the old 3069-777-14dB routine. I guess that there were just too many errors on the line when the higher frequencies were being used.
Graham