In reply to a post by StephenTodd:

Going right back to the original post

The graphs were taken as part of a general investigation. While my modem was reporting a tatic 72Mb/s my laptop and another machine were reporting a variable 20Mb/s to 30Mb/s. If interference was causing the issue then we have to ask why the modem remained connected at 72Mb/s throughout.

Edited by Andrue (Sat 29-Dec-12 12:00:17)

Sorry, yes you are right. You'd clearly stated actual sync speed of 72 and corresponding profile but I somehow missed it ~ too early in the morning?

In reply to a post by StephenTodd:

Sorry, yes you are right. You'd clearly stated actual sync speed of 72 and corresponding profile but I somehow missed it ~ too early in the morning?

Could be. Plus it's the holiday. I've given my brain permission to go on slow time until Wedensday

In reply to a post by Andrue:

Plus it's the holiday. I've given my brain permission to go on slow time until Wedensday

I thought it already had permanent permission ....

When is Wedensday?

Maybe that's another problem. He gave it the same instruction a few years ago, and it's never been reached.

In reply to a post by RobertoS:

In reply to a post by Andrue:

Plus it's the holiday. I've given my brain permission to go on slow time until Wedensday

I thought it already had permanent permission ....

No - it just doesn't always follow the rules

In reply to a post by RobertoS:

It might be useful if we could have the modem stats, (both --pbParams and --show, or even --stats instead of --show as that gives the error stats), for when it is bad, for comparison. That might help analyse things a little better.

I remember reading your earlier post about the exact 2-monthly occurrences. I've no brainwaves at the moment I'm afraid .

FYI:

http://i50.tinypic.com/359bw2p.png

(Thanks to BaldEagle for the monitoring)

IDNet actually seemed to do a reasonable job this time. They contacted BT and got a response. Unfortunately the BT response wasn't all that helpful and we're back to getting an engineer sent out which I think will be an expensive waste of time.

BT response:
"Remote diagnostics have been carried out and currently all tests pass. No
over-utilisation of the cab is indicated. I have discussed the issues you
have stated (ie issues occur regualrly every 60). The FTTC network team
have stated no profile changes have taken place or any limitations on your
customer circuit.

Next course of action recommended/to be taken: As current remote checks do
not indicate any issue, if you require any further investigation and have
fully eliminated any possible cause of issues with your customer
equipment/set up/sources of interferance, in order to instigate an
Openreach engineerfor further checks"

So it seems I'm stuck :-/

Edited by Andrue (Thu 21-Feb-13 18:59:09)

Andrue wow so not just my line having it rough.

You got pretty bad QLN like me, you have a stronger hlog graph yet your sync imo is poor for the attenuation like mine.

Your D0 bitloading should be hogging 15bits per tone in my view, but is battered by QLN and you also have one of the unfavourable adsl bitmasking masks thats affecting a lot of D0 tones as well.

Interesting that their remote tests seem to be inadequate as they not picking up the high levels of QLN. Or maybe they are but BT accept that amount of QLN.

In reply to a post by Chrysalis:

You got pretty bad QLN

With a reasonably repeatable 60 day pattern it sounds more like QRM to me...