Upped to ADSL2+ and still on the dark age

Started by troesma, Jul 09, 2009, 12:19:09

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

troesma

Quote from: Rik on Jul 11, 2009, 19:10:27
It is, I'm afraid. Your profile is correct for your sync speed, throughput is correct for the profile. You need to get that target NM down, and that requires 14 days without a loss of sync. (Unless BT fix a fault and log it, in which case it can be done manually.)

Maybe worth asking James to get BT to do it..? (manually)

Sebby

BT are more often that not willing to do so, but it's always worth a try.

Rik

No clues there, your 21CN date is too far off for work to be going on yet. :(
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

troesma


Rik

You've got it. Your only other option, if things don't settle, would be to try LLU.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

troesma

Guess that's for the folks at IDNET to arrange...

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

troesma

OK, did another detailed run through the house and using a piece of kit that is very sensible to RF interference, found that my alarm clock transformer was emitting a HUGE amount of noise... and was plugged 10 cm away from the router.

Router stats after I removed it from sight...

DSL Driver Version:  AnnexA version - A2pB022g.d20e
DSL VPI/VCI: 0/38
DSL Status: ShowtimeRetrain Reason:   8000
DSL Mode: ADSL2+
DSL Channel: FAST
DSL Upstream Rate: 1047 Kbps
DSL Downstream Rate: 4562 Kbps  :)

(Down/Up)
   
DSL Noise Margin: 15.2 dB   5.9 dB
DSL Attenuation: 44.5 dB   23.3 dB
DSL Transmit Power: 0.0 dBm 13.0 dBm

Cannot do a BT line check yet (within 3 hour window) but let's see how it goes...



Sebby

That's a positive change. :)

Unfortunately, your target SNRM is still set at 15dB. If you hold sync for 14 days, that should drop by 3dB. This should continue in 3dB increments down to the lowest setting of 6dB.

Simon

Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

troesma

Finished work, now to bed... previous BT Speedtest results on SAT at 7 PM

BT test shows now...

Test1 comprises of Best Effort Test:  -provides background information.
   Your DSL connection rate: 3220 kbps(DOWN-STREAM),  1023 kbps(UP-STREAM)
   IP profile for your line is - 2500 kbps
   Actual IP throughput achieved during the test was - 2312 kbps

Now SUN at 3:10 AM

Test1 comprises of Best Effort Test:  -provides background information.
   Your DSL connection rate: 4562 kbps(DOWN-STREAM),  1046 kbps(UP-STREAM)
   IP profile for your line is - 2500 kbps
   Actual IP throughput achieved during the test was - 2305 kbps

Router stats show...

DSL Noise Margin: 12.7 dB  5.5 dB
DSL Attenuation: 44.5 dB  23.3 dB
DSL Transmit Power:  0.0 dBm  13.0 dBm

So it seems it's sorting out, slowly but consistently  ;)

Hope IP profile changes soon...

Rik

3-5 days, probably nearer 5 given the number of re-syncs you've had. :(
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

Quote from: troesma on Jul 12, 2009, 03:17:34
So it seems it's sorting out, slowly but consistently  ;)

Re the SNRM, it's probably only because there's more noise around now. I'd have thought that if you re-sync now, it'll be 15dB again.

rireed3

(Sebby's not telling you to re-sync :eek4:)
It does look like there is still extra noise on your line.  Your sync speed is still the same as you posted at 20:05, but your margin has dropped from 15.2 to 12.7.  I think your target is still at 15 as that won't go down until your line doesn't re-sync for 14 days.

The three pieces of information are all relevant:  noise margin and connection (sync) speed at that margin, and history of sync (how long since the last sync, how many syncs since the router was turned on).  Lleave the router on unless you work on the wiring.

Richard

Rik

You're right, Richard, I'm not - this line needs some stability for a while.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

rireed3

Rik's too fast! Sorry for the mistake (edited). I meant Sebby.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

troesma

Quote from: rireed3 on Jul 12, 2009, 10:48:19
(Sebby's not telling you to re-sync :eek4:)
It does look like there is still extra noise on your line.  Your sync speed is still the same as you posted at 20:05, but your margin has dropped from 15.2 to 12.7.  I think your target is still at 15 as that won't go down until your line doesn't re-sync for 14 days.

The three pieces of information are all relevant:  noise margin and connection (sync) speed at that margin, and history of sync (how long since the last sync, how many syncs since the router was turned on).  Lleave the router on unless you work on the wiring.

Richard


Yup, I'm NOT going to touch anything for a while, but keep monitoring it.

Router says NM back to 14.7db region, so it suggests it's not moving from the 15db target and guess it's going to stay there until the line is stable enough. Luckily, no re-syncs so far but will ask Miriam if she can check on Monday how many re-syncs have taken place during the WE to see what's going on.

From the discussions in other threads, seems BT is making a right mess out of ADSL2 bundling. Just hope IDNet don't get hit hard with customers moving away on behalf of BTs surly service. As the saying goes, it takes a generation to build a reputation, and a second to destroy it.

rireed3

QuoteRouter says NM back to 14.7db region

It's still worthwile trying to find what's causing the fluctuation.  When NM goes down and then back up without re-syncing, it means that momentary noise has affected your line.  2.5 db is a lot for short term variations and is worth investigation.

troesma

Having doing exhaustive checks yesterday, have a strange feeling it's on BT's side of things  >:(

Will try to check today if I missed anything, though.

rireed3

#95
Many of us have been through this search.  Sometimes, but not very often, it's in the exchange.  It was in my case, but it was the devil to prove this and BT's systems and processes did everything to prevent proof, so you'll be much more fortunate if it's under your control.

I realise from one of your previous posts that your noise margin was "solid" at 12.1 before the upgrade, so you believe the fluctuation is due to the upgrade.  The way DLM works makes it unlikely that this was without the presence of noise.  The standard target margin is 6, but this is raised automatically when the line has too many errors/re-syncs.  The target 12 means it was raised in 2 steps of 3 db each.

The only way to really eliminate your house wiring as a source is to turn off the router, unscrew the front of the master socket and plug the router filter into the test socket underneath (others please say if you think this is a good idea for now).  I can't find in your posts where you did this, but if you can do without extensions for a while (pulling away the master face plate disconnects them all), you can check if the 15 db target you appear to be on becomes very steady, only changing slowly, often in the evening.

If you've already found out that using the test socket does not steady your line, for the search in your house and even nearby, it's often helpful to record the noise margin over a long period to see if the fluctuations have a timing you can associate with electrical equipment operation or soaking rain (not thunder - that affects everyone).  I've read posts where a neighbour's treadmill was responsible and was identified this way.  Sometimes the source is further away and more difficult to find or fix.

The treadmill example brings up filtered mains strips.  Tricky to find these in good quality, and brands change, so this would take a little web research.

I thought you mentioned the RouterStats recording program once but in case not, find it here (it's cranky and we can help you use it):
RouterStats

If you ultimately prove that the noise is away from your house, bear in mind that BT don't have to find and fix it.  Your broadband is legally good enough for BT Wholesale/Openreach responsibilities.  Then there are several approaches that IDNet support can help with where appropriate, but consult them with copious details so they can decide what's best.  For example, if you have a bad pair and none of your neighbours do -- if BT won't/can't try a better spare, ask for a second line and number, then ask for your broadband to be switched to it.  This is not the usual approach, but you see how things can develop.  IDNet support are far better than most at figuring these alternatives.

Richard

Rik

The best test of all is to connect a USB-powered modem at the test socket with the house wiring powered off at the consumer unit, that eliminates everything in the house at a stroke. I'd still do the test socket though.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

troesma

Nope, it's not connected to the Test Socket but the external one on BTs Master. Wonder if it's a good idea to force a resync before knowing if it holds its nerve for 48 hrs..?

Just checked and the NM is at 15.1db solid, but the downstream rate has gone UP marginally to 4636 Kbps. Maybe it's the time of the day...  :whistle:

What do you think..?

Rik

Rates will only change on a re-sync so it sounds like you've had one.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

troesma

Despite the increase, not good I guess...  >:(