Print

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

[Black Sheep]

50 meters sounds fine to me my telegraph pole with the dropwire is 43 meters to the house as for the OR cost for re-siting your current feed to a dropwire you will need to ask BlackSheep

I've covered this elsewhere regarding practicalities etc ....... but costings are not my 'thang' I'm afraid. 

[burakkucat]

I'm guessing that the correct method would be to contact the ISP/CP and request that they make arrangements for an Openreach planning visit, in respect of replacing the current underground service feed with an aerial drop.

[burakkucat]

I've only just seen the QLN plot and that is also a horror story . . .

[MaximusPrime]

@burakkucat,

I've been disconnected since 20:30, back on BT Home Hub 5A, what do you mean horror story?

@NewtronStar,

"Retrain Reason : 200000" - what does it mean?

[MaximusPrime]

Guys what do the Traffic Lights mean on MDWS?

[burakkucat]

Guys what do the Traffic Lights mean on MDWS?

If you left-click on the traffic lights, a window will open and show all the current relevant data for your circuit. See the attachment, below --

[MaximusPrime]

Thanks @burakkucat,

my noise margin is up so my speed is down at the moment.

I don't think I'll see CRC errors again until my speed is increased & noise margin lowered

[MaximusPrime]

Guys,

I had a disconnect today with CRC's recorded on my DSL Stats but not on MDWS. Is this a bug?

It happened 2 nights ago too.

Edit: but strange CRC's on the G.INP graph - why?

[tbailey2]

Hi

Those two graphs are for different stats - the DSLstats one is for Bearer 0 while that for MDWS is for Bearer 1.

You may not see stats for all minutes in MDWS on the 24 hours graph as, in your case, the graph is 680 pixels wide but there are 1440 minutes in a day so over half get discarded for that plot.

But I've checked in the raw database and there were no CRC errors at all uploaded to MDWS within the period that is shown on the DSLstats graph, certainly not between 12:38 and 12:48 .


 

[MaximusPrime]

@tbailey2,

I would guess my line gets disconnected due to a very quick spike in CRC's. I get a new connection & the stats are recorded on my machine. By the time I get a connection to MDWS the CRC's are gone & are not recorded?

Edit 1: the end points of these graphs seem to coincide?

Edit 2: Actually the same thing happened yesterday morning too, image attached

[NewtronStar]

You will definitely notice when a resync has occurred when you see a spike of severely errored seconds when monitoring stats don't how or why this happens but it's become the norm and I just just discount those error's

[MaximusPrime]

@NewtronStar,

the solid line in your graph indicated that there was no disconnection I believe?

My graphs show a disconnection (dashed line) followed by a decreasing number of CRC's - that would indicate to me there was a large spike of errors which caused the disconnections abruptly, when the connection was reestablished the number of CRC's decreased quickly

[NewtronStar]

@NewtronStar,

the solid line in your graph indicated that there was no disconnection I believe?

It was a DLM resync with no CRC errors before or during the event just a spike of SES's

[MaximusPrime]

@NewtronStar,

sorry, I see what you are saying now, I thought your graphs were CRC graphs.

MDWS doesn't show that I had any Error Seconds today but MyDSL stats does; attached

[tbailey2]

A bit early in the morning to be looking through the database records but you had a resync at the time those 11 ES occurred yesterday (12:45)  and were recorded locally on DSLstats. That dropped the connection and so you missed the upload at 12:45 while it reconnected - that upload would have had the data for those ES in so MDWS never saw it. They are recorded by DSLstats as delta values. i.e. the difference between the previous value and the current one so it goes back to zero again if there are no further ES.

Similarly you missed an upload at 0248 this morning due to a resync.