Interleaving - Plusnet say it is off, router says it is on

[#1]

I asked for interleaving to be set to off and was told that had been action on 7/6  will take 1-5 days so 14/6 by the latest.  16/6 raise a query on this as was told that interleaving is off but that not what my router says:
TP-LINK> w ad ch
near-end interleaved channel bit rate: 7616 kbps
near-end fast channel bit rate: 0 kbps
far-end interleaved channel bit rate: 448 kbps
far-end fast channel bit rate: 0 kbps
And I have power cycled the router.  Do I have to power off for a long time, or overnight or something?  I'd like to try to get 8128 sync.  SNRM is around 8 most of the time.  Why does my router say it is on and Plusnet say it is off?  Plusnet say I should ask in the forum as "Unfortunately this is not something we can offer that level of support on" which seems a odd answer to me.  From where I'm standing it doesn't look like interleaving is switched off, unless there is some trick to activating it.

[#2]

It looks as though there was an error made in the response to your ticket, interleaving *is* turned on for your line. I've placed a manual order for this to be switched off, which is due to complete tomorrow.

[#3]

Thanks.  I'm not going daft then 🙂

[#4]

Checked today and interleaving is now off.  Sync is 8128.  What should I be looking for in SNRM?  And in CRC,FEC,HEC?
What I get is currently
TP-LINK> w ad li f
relative capacity occupation: 54%
noise margin upstream: 20.0 db
output power downstream: 19.5 dbm
attenuation upstream: 10.5 db
carrier load: number of bits per symbol(tone)
tone  0- 31: 00 00 00 00 02 45 66 77 78 88 88 77 77 66 54 20
tone  32- 63: 00 00 00 34 56 78 89 aa ab bd bc cc cc cc cc cc
tone  64- 95: 0c cc cc cc cc cc cc cc cc cc cc cc bc bb cb bb
tone  96-127: bb bb bb bb bb bb bb bb bb bb ba bb bb ab aa aa
tone 128-159: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa
tone 160-191: aa aa aa aa aa aa 9a aa 9a 9a aa 9a 99 99 99 99
tone 192-223: 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99
tone 224-255: 99 99 89 89 99 99 88 99 99 99 99 98 88 88 77 64
TP-LINK> w ad li n
relative capacity occupation: 96%
noise margin downstream: 6.0 db
output power upstream: 12.0 dbm
attenuation downstream: 24.0 db
TP-LINK> w ad li n
relative capacity occupation: 96%
noise margin downstream: 4.5 db
output power upstream: 12.0 dbm
attenuation downstream: 24.0 db
so SNRM max 6dB, dropping down to 2 fairly often. But errors seems to be fixed at 3
TP-LINK> w ad perf
near-end FEC error fast: 0
near-end FEC error interleaved: 0
near-end CRC error fast: 3
near-end CRC error interleaved: 0
near-end HEC error fast: 3
near-end HEC error interleaved: 0
far-end FEC error fast: 0
far-end FEC error interleaved: 0
far-end CRC error fast: 0
far-end CRC error interleaved: 0
far-end HEC error fast: 0
far-end HEC error interleaved: 0
Error second in 15min          : 0
Error second in 24hr            : 1
Error second after power-up    : 3
ADSL uptime    8:20:58
which perhaps was the re-sync to 8128?  Is this anything to worry about?

[#5]

Hi Malcb,
Are you seeing any poor performance from your connection. As 8128 is the maximum sync I wouldn't worry about the SNR. As I've said before, unless you are having performance ssues with your internet then I wouldn't try to analyse router stats because they'll drive you insane!
Jojo

[#6]

Thanks for the reply.  I think performance is ok.  Looking at the errors stats again I think what that is telling me is I have the odd error now and again but nothing to worry about.
At most I seem to to see 1 error second (= in 1 second window had an error)  in 15min, so 1 in 900 error.  I reckon that's acceptable.  Long term it says 58 error seconds since power up 79 hrs ago which is 1 in 4900.

[#7]

Sounds to me like you're still analysing stats

[#8]

lol

[#9]

Quote from: Malcb

Thanks for the reply.  I think performance is ok.  Looking at the errors stats again I think what that is telling me is I have the odd error now and again but nothing to worry about. At most I seem to to see 1 error second (= in 1 second window had an error)  in 15min, so 1 in 900 error.  I reckon that's acceptable.  Long term it says 58 error seconds since power up 79 hrs ago which is 1 in 4900.

When I turned interleaving off to get the 8128 speed, I was getting downstream SNRM that was 7.4-7.9dB most of the time, and ran at around 10 CRC errors per hour. It was no problem whatsoever.

[#10]

Since I fitted a BT i-plate or a BT accelerator as their now called my TX-crc and RX-crc errors are both zero
Puddy