Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[William Grimsley]

Hi guys,

I think we've taken over too much of daveesh1's thread, or should I say, I have. So, I've made a new thread so we can keep anything else that happens related to one thread. I hope this is ok?

[William Grimsley]

I think DLM's going to intervene again in a minute, it just did but didn't make any changes...

[Chrysalis]

if no changes were made then it probably wasnt a DLM intervention.

Just leave the line alone and wait a couple of days for DLM to do something.

[Ronski]

Changes were made, the  sync  dropped slightly, in fact there have been several small changes after banding was removed. Hopefully g.inp will be applied soon and that will reduce the errors.

[Chrysalis]

What changes ronski?

interleaving, delay and inp all stayed the same.

I see no way to see all the line settings on MDWS.

I see now when hovering over XTR, some extra data is revealed but how do you see the historical data to compare?

Posted in the MDWS thread about this as to not derail this thread, I do see the sync was RDI so suggests is DLM but I dont see any changed parameters.

[William Grimsley]

That's what I'm confused about, to say the line was experiencing a lot of Downstream CRC spikes, I wouldn't have been surprised if it was an LOS.

[Dray]

Looking at your Bitswap/min graph over 2 days, it looks like something comes on at 17.00 and goes off at 9.00 daily which is producing a lot of interference. Is that the central heating?

[William Grimsley]

We have underfloor heating, but it could well be the heat pump... I will have a word with him when he calls me later or his back from holiday on Monday.

[jid]

I'd say DLM will imminently be doing something to the line, the traffic lights are all red now.

[Chrysalis]

popcorn time

[William Grimsley]

Yeah, they've been red for some time now, quite surprised nothing has happened yet!

[kitz]

The Err Secs are weird.   The SNRm is still what I'd class as giving cause for concern for there.   Its still hovering within 1dB range and lines should be able to cope with this.   Bearing in mind line length its going to be more sensitive to noise anyhow and is one of those that would without doubt benefit from g.inp for error stability.

Openreach will not be bothered about such SNRm fluctuations - its too small and considered within normal realms of operating level.
Heck even the other week my own upstream fluctuated between 13.4 and 11.8 and I dont have a clue what it was about.

>> popcorn time

Im afraid not for me.   Last night, I got in.  Sat at the PC, and aside from opening a bottle of wine spend the whole evening sat posting on the forum.  It was only late on I realised I hadnt even cooked or eaten. :/   Its not something I intend to do today as I have lots to do and am out of here.   Its a glorious day and Im not spending it at the PC.   Have a good day everyone   


 

[William Grimsley]

Good plan, kitz. I think we've just got to take some time away from scrutinising the graphs and just take it as it goes from now on. I've already realised that I've spend too much time watching these graphs and need to get doing something else.

Hmm, I wonder when we'll get another resync.

[William Grimsley]

The line is still up after the last DLM resync, quite surprised.

I have no idea why but the Downstream Attainable Rate keeps fluctuating violently!

[NewtronStar]

I am very surprised to see you with all three reds lit up on MDWS DLM error status indicator, did the engineer give you the local loop distance to the cabinet  ?