Ok, I've fixed it what happens next?

Started by Bat, Oct 21, 2007, 14:14:44

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Bat

Hi,
Due to an internal wiring issue my router was indicating a speed of 1.6 meg.  :o
I've just ran in a new cable, speed indicated now 4.8 meg  ;D
However speed tests are still giving me 1.2 meg results.  :(
It is just a case of waiting for it to sort itself out?
Should I reboot my router in a weeks time or something?
Cheers,
Gavin :)

Ann

If you maintain that synch speed then the profile should go up in a few days (3 or 5 I'm not sure which) and then you'll get a higher speed.

The BT test will show your profile and speed.  http://speedtester.bt.com/

cavillas

------
Alf :)

Rik

As Ann says, Gavin, you should find the throughput improves in a few days. If you do the BT speedtest, it will tell you what your profile is, that should increase from the current 1500 figure to somewhere around 4000, maybe 4500 if you're lucky. The profile change does take 3-5 days.
Rik
--------------------

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

Bat

Hi,
Ok, BT says......


Test1 comprises of Best Effort Test:  -provides background information.
    IP profile for your line is - 1250 kbps
    DSL connection rate: 448 kbps(UP-STREAM)  4832 kbps(DOWN-STREAM)
    Actual IP throughput achieved during the test was - 1151 kbps


So do I need to do anything at my end now or just wait and see?
Thanks for the replies so far  :)
Cheers,
Gavin :)



Rik

Just wait, Gavin. Provided your connection remains stable, that profile will increase over the next few days. Your current sync speed should achieve 4500.

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

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

Ann

When Rik says "just wait" what he really means is wait, and get a bit twitchy, and keep doing the BT test just to see.  None of that will do any good but it's in the rules   ;D

Lance

Glad the work has paid of Gavin. As Ann says, time to get twitchy!
Lance
_____

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

Rik

Quote from: tortoise on Oct 21, 2007, 15:55:47
When Rik says "just wait" what he really means is wait, and get a bit twitchy, and keep doing the BT test just to see.  None of that will do any good but it's in the rules   ;D

;D

I didn't add "and don't keep re-booting the router", Ann, which I should have done.
Rik
--------------------

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

Bat

Hi,
I'll just sit back and admire my handy work then  :laugh:
Thanks everyone, I'll post up when I get a change in speed  ;)
Cheers,
Gavin :)

Bat

Hi,
SNR has already dropped by 2 dB to 13  :)
Cheers,
Gavin :)

Lance

Being at 15db shows that you have obviously had a change to your target SNR from 6db to 15db.

I would suggest keep an eye on it over a week, and see what the lowest it drops to is. Once you have done this, I would email support explaining that you had a problem with the internal wiring which is now sorted. Continue to explain that your target SNR has been increased to 15db as a result of the problem but you would like it reduced by BT. It may be, if you see quite a swing downwards, that you only want it adjusted down to 9db (3db movements) as this will continue to give you some extra headroom over the standard target of 6db.

Having a lower target will enable you to have a higher sync.
Lance
_____

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

mrapoc

Which wiring was this? I'm interested lol  :)

Bat

#13
Hi,
It was the telephone extention wiring to the modem upstairs. It was around 20 years old with a joint in it. I've ran the new cable through the loft and airing cupboard to keep it away from mains cables, it's probably twice the length of the original but works alot better already.
EDIT:SNR now 12dB
Cheers,
Gavin :)

mrapoc

ahh right

i have like a 1 metre adsl line straight from the main (and only) socket to my router and a 10metre shielded cat5e cable to my bedroom - still get electrical spikes mind

Lance

The electrical spikes could well be caused further down the line, unfortunately :(
Lance
_____

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

Bat

#16
Hi,
Now got the SNR upto 15.5  :o
I'm gettting a lot of FEC errors, what are they  ???
Pasted for your perusal.............

Uptime: 1 day, 22:42:54 
Bandwidth (Up/Down) [kbps/kbps]: 448 / 4,832
Data Transferred (Sent/Received) [KB/KB]: 0.00 / 0.00  ???

Output Power (Up/Down) [dBm]: 11.5 / 19.5

Line Attenuation (Up/Down) [dB]: 31.5 / 39.0

SN Margin (Up/Down) [dB]: 23.0 / 15.5

Vendor ID (Local/Remote): TMMB / ALCB
Loss of Framing (Local/Remote): 0 / 0 
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): 0
Error Seconds (Local/Remote): 49 / 0
FEC Errors (Up/Down): 318 / 1,268,129
CRC Errors (Up/Down): 0 / 123
HEC Errors (Up/Down): 0 / 116

BT say .....

    IP profile for your line is - 1250 kbps
    DSL connection rate: 448 kbps(UP-STREAM)  4832 kbps(DOWN-STREAM)
    Actual IP throughput achieved during the test was - 1144 kbps


Cheers,
Gavin :)

Rik

Hi Gavin

FEC errors indicate that your line is interleaved, and that the error correction has been working. The number of errors suggests that there's a bit of noise affecting your line still.

From the look of things, your target noise margin has been raised by the BT line management software in order to stabilise things. If you keep a continuous connection for 10-14 days, this should reduce by 3db, repeating at two week intervals. As the noise margin reduces, so your sync speed will increase.

If your line looks stable after your profile adjusts, then you could ask IDNet to get the margin reduced.
Rik
--------------------

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

Bat

#18
Hi,
I think this this getting worse?

Uptime: 6 days, 5:16:15
Modulation: G.992.1 Annex A

Bandwidth (Up/Down) [kbps/kbps]: 352 / 3,392

Data Transferred (Sent/Received) [KB/KB]: 0.00 / 0.00

Output Power (Up/Down) [dBm]: 11.5 / 19.5

Line Attenuation (Up/Down) [dB]: 31.5 / 40.0

SN Margin (Up/Down) [dB]: 4.0 / 16.5

Vendor ID (Local/Remote): TMMB / ALCB
Loss of Framing (Local/Remote): 10 / 0
Loss of Signal (Local/Remote): 2 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): 0
Error Seconds (Local/Remote): 414 / 0
FEC Errors (Up/Down): 718 / 53,924
CRC Errors (Up/Down): 4 / 152
HEC Errors (Up/Down): 4 / 138


BT say...
Test1 comprises of Best Effort Test:  -provides background information.
    IP profile for your line is - 2500 kbps
    DSL connection rate: 352 kbps(UP-STREAM)  3392 kbps(DOWN-STREAM)
    Actual IP throughput achieved during the test was - 2313 kbps


Clearly from the BT test my line is picking up speed, but the router stats don't look good!
Infact it looks to be all over the place, some mentioned on a previous post that my line seems to be going in 2 different directions, I think it's 3 now! :o :o
I've never seen the up bandwidth down graded before....
I've not even thought about this since my last post, let alone done anything with it  ::)
Cheers,
Gavin :)

Rik

Hi Gavin

Give support a ring, there's no way your u/s sync should have dropped like that, they need to get BT to investigate.
Rik
--------------------

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

Bat

Hi,
Rik ... Telephoned, 3 rings as usual ;)
Andrew says he'll check it out.
Cheers,
Gavin :)

Rik

That's great, Gavin. Keep us posted.
Rik
--------------------

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

Bat

Hi,
Andrew has said switch it off over night, then restart in the morning.
Sounds good to me, and I can redo my webserver while the broadband is down :)
Cheers,
Gavin :)

Rik

I'm still curious about that u/s sync, Gavin. Very odd...
Rik
--------------------

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

Bat

#24
Hi,
I only do very odd! Anyone who's met me knows that :D
Andrew said he thinks that as the line has improved that we need to reset, in order to get the improvement to kick in.... Or something like that....
As I've posted up stats and tests on here, I'll switch off later and restart in the morning.
Then I can post up again and monitor it for a few days to see where it goes.
I'm not in any rush as at the moment I have something that works, but it would be nice to be getting the full potential out of it or fix it before it breaks!  :o
Cheers,
Gavin :)

Rik

I'm intrigued now, let me know what your stats are tomorrow will you?
Rik
--------------------

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

Bat

Hi,
Sure. I've got goldfish memory so I'll be lucky if I can remember to switch it off and back on again! :o
Cheers,
Gavin :)

Rik

I can send you a time switch if you like. :)
Rik
--------------------

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

Bat

Hi,
Now there's a good idea! I'd leave it on for a week though! ::)
Cheers,
Gavin :)

Bat

Hi,
Told you I'd forget ::)
Shutdown last night, this morning I'm at:

Uptime: 0 days, 0:05:40
Modulation: G.992.1 Annex A

Bandwidth (Up/Down) [kbps/kbps]: 448 / 4,864

Data Transferred (Sent/Received) [KB/KB]: 0.00 / 0.00

Output Power (Up/Down) [dBm]: 11.5 / 19.5

Line Attenuation (Up/Down) [dB]: 31.5 / 39.0

SN Margin (Up/Down) [dB]: 24.0 / 15.5

Vendor ID (Local/Remote): TMMB / ALCB
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): 0
Error Seconds (Local/Remote): 0 / 0
FEC Errors (Up/Down): 0 / 0
CRC Errors (Up/Down): 0 / 0
HEC Errors (Up/Down): 0 / 0


Speak to you later...
Gavin :)

Rik

Can you do a BT speed test please, Gavin?
Rik
--------------------

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

Bat

Hi,
Tah Dah .....



Test1 comprises of Best Effort Test:  -provides background information.
    IP profile for your line is - 4000 kbps
    DSL connection rate: 448 kbps(UP-STREAM)  4864 kbps(DOWN-STREAM)
    Actual IP throughput achieved during the test was - 3708 kbps


Current router stats ........


Uptime: 0 days, 11:32:00
Modulation: G.992.1 Annex A

Bandwidth (Up/Down) [kbps/kbps]: 448 / 4,864

Data Transferred (Sent/Received) [KB/KB]: 0.00 / 0.00

Output Power (Up/Down) [dBm]: 11.5 / 19.5

Line Attenuation (Up/Down) [dB]: 31.5 / 39.0

SN Margin (Up/Down) [dB]: 24.0 / 13.0

Vendor ID (Local/Remote): TMMB / ALCB
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): 0
Error Seconds (Local/Remote): 4 / 0
FEC Errors (Up/Down): 0 / 3,698
CRC Errors (Up/Down): 0 / 6
HEC Errors (Up/Down): 0 / 5


Cheers,
Gavin :)


Rik

That's fine, Gavin, throughput is good for the profile, profile is right for the sync speed.

If you can manage to keep a stable connection for a couple of weeks, your target noise margin should decrease by 3d, and will repeat until the line becomes unstable. As that happens your sync speed will improve and the profile will follow. It's slow, but we are talking about BT here. :)
Rik
--------------------

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

Bat

Hi,
At least now it's all heading in the same direction :)
Thanks Ric & Andrew :)
Cheers,
Gavin :)

Bat


Rik

It's OK, Gavin, my uncle gets it wrong all the time, and he's known me for a long time! ;)
Rik
--------------------

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