Print

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

[Chrysalis]

whilst checking out my data on mydslwebstats I see earlier yesterday 26th approx 6pm what looks like another disturber FTTC line enabled, a sharp instant drop of 10mbit attainable, I still have my current 75mbit sync, but if I resync and its on a 6db target I estimate my new sync speed to be around 58-60mbit/sec, my current snrm is now just 1.4db    Which will be very low based on my historical data for fast path, I have only been that low before when interleaved and during a recognised fault.

I believe the attainable reported by the modem is based on 4db as prior to the change it was reporting attainable equal to my sync speed but now is attainable 64.6 for 4db snrm.  IF the line resyncs at 4db I estimate around 67mbit.  Which is what I was previously getting at 6db, prior to the fault raised at plusnet some months ago.

My point of sale estimate was 73mbit so if I do sync at 60mbit is a 13mbit gap but visiting engineers if past experience is anything to go by will all say thats within operating spec and not even attempt to do any fix.

thoughts?

those with access to mydslwebstats will be able to see this now, attached snr graphs from 26 aug 7am and 27 aug 7am, can see the lower tones battered.

My day1 attainable with fast path was 110mbit, so going down to 60 on fast path is very close to a 50% drop in signal.

[Bald_Eagle1]

Something odd also appears to have happened early this morning regarding US FEC counts

[Chrysalis]

my DS error rate has multiplied a lot, debating now whether or not to manually resync it to get the errors back down.

Obviously I survived this morning no DLM, but today will be a full 24 hours of the lower snrm.

[NewtronStar]

my DS error rate has multiplied a lot, debating now whether or not to manually resync it to get the errors back down.

If you do decide to manually resync the modem (power off) please let 30 minutes pass by before powering up the modem 

[kitz]

I noticed earlier when looking at mine, that your SNRm had taken a nose dive and wondered what could have caused it.   irrc your line had been up and rock steady for ages.

With that loss of SNRm, then it stands to reason your error rates are going to increase..  and yes no doubt the DLM will notice at some point.
So I guess the options are, let the DLM kick in and force a resync, with likely more interleaving and a relative loss of sync speed.   Or do it yourself to try and lessen any DLM effects

[Chrysalis]

the line is messed up. the higher tones D3 are now stronger than the D2 middle and D1 is not much more than D3.  So all the loss of signal since day 1 is on D1 and D2, I will post my snr from dec 2012.  It's D1 and D2 that have regressed.  I think I have a clear crossed pair or something that causes excessive crosstalk but local engineers arent interested.

[kitz]

From a quick look at that bit-loading graph (and without being able to compare before and after graphs) , then your most affected tones are like you say in the D1 region.  - Specifically the area where Id expect to be affected by crosstalk from an adsl2+ line 

[Chrysalis]

the bitloading is probably still similiar as I am still on the 75mbit sync.

[Chrysalis]

ok I left it off for 30+ mins as was a massive error spike earlier, and I overestimated the speed, its down to 58mbit.

[Chrysalis]

waiting game now, plusnet want to send a voice engineer first, so I havent even got a FTTC one booked yet.

[Chrysalis]

guys check my line at 11.22am today, notice something odd?

[burakkucat]

guys check my line at 11.22am today,

Er, excuse the question, but how? 

A link / URL would be helpful. 

[Chrysalis]

mydslwebstats.

basically what happened is my line very briefly got its snr back, but it seems only for 1 minute. at 11.22am the attainable went up to 74.4mbit and snrm recovered, but at 11.23am it was back down again.

[Chrysalis]

here

[NewtronStar]

It looks like the DLM has already seen the high errors and forced a cap on the attainable. so you should see an overall reduction in errors, you know the drill it's to wait 4-5 days and see if it recovers

I take it your fastpath was not effected ?