General Discussion
  >> General Broadband Chatter


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | [2] | 3 | 4 | 5 | 6 | 7 | (show all)   Print Thread
Standard User XRaySpeX
(eat-sleep-adslguide) Sun 20-Nov-11 23:40:21
Print Post

Re: Odd things about BE O2 conections


[re: RobertoS] [link to this post]
 
TSNR = Target SNR Margin!

1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
Standard User deleted
(deleted) Sun 20-Nov-11 23:41:01
Print Post

Re: Odd things about BE O2 conections


[re: XRaySpeX] [link to this post]
 
In reply to a post by XRaySpeX:
TSNR = Target SNR Margin!
TSNRM
Anonymous
(Unregistered)Sun 20-Nov-11 23:42:59
Print Post

Re: Odd things about BE O2 conections


[re: RobertoS] [link to this post]
 
In reply to a post by RobertoS:
Are you talking about the two capped products? I.e.O2 Standard (legacy), and Be Value in both legacy and current versions?

Or something else, such as day-to-day running, where the margin varies as expected.

The 0.5dB immediately after sync I agrre is odd, bur seems to be a differnet, though perhaps related, issue.

What's TSNR? Or am I just having a brain failure? T SNR = target SNR,
I was referring to both the legacy o2 packages and the be unlimited package,
but even if gdmt mode is forced there still is no spare margin visible , and that maxes out at around 12mbit which is a little high


Register (or login) on our website and you will not see this ad.

Anonymous
(Unregistered)Sun 20-Nov-11 23:48:13
Print Post

Re: Odd things about BE O2 conections


[re: Anonymous] [link to this post]
 
In reply to a post by Anonymous:
In reply to a post by RobertoS:
Are you talking about the two capped products? I.e.O2 Standard (legacy), and Be Value in both legacy and current versions?

Or something else, such as day-to-day running, where the margin varies as expected.

The 0.5dB immediately after sync I agrre is odd, bur seems to be a differnet, though perhaps related, issue.
i'll try again, as my post , err well didn't show,???? TSNR =Target snr
the package is irreverent really, but should be more obvious if someone is on the capped @12mbit value product ,if their line can support a higher sync, but truth is only the tsnr is set to shows when is should show a higher (spare snr)
Standard User deleted
(deleted) Sun 20-Nov-11 23:50:49
Print Post

Re: Odd things about BE O2 conections


[re: Anonymous] [link to this post]
 
In reply to a post by Anonymous:
In reply to a post by Anonymous:
In reply to a post by RobertoS:
Are you talking about the two capped products? I.e.O2 Standard (legacy), and Be Value in both legacy and current versions?

Or something else, such as day-to-day running, where the margin varies as expected.

The 0.5dB immediately after sync I agrre is odd, bur seems to be a differnet, though perhaps related, issue.
i'll try again, as my post , err well didn't show,???? TSNR =Target snr
the package is irreverent really, but should be more obvious if someone is on the capped @12mbit value product ,if their line can support a higher sync, but truth is only the tsnr is set to shows when is should show a higher (spare snr)
Why?
Anonymous
(Unregistered)Mon 21-Nov-11 17:22:45
Print Post

Re: Odd things about BE O2 conections


[re: deleted] [link to this post]
 
In reply to a post by BatBoy:
In reply to a post by Anonymous:
In reply to a post by Anonymous:
... nested quotes trimmed ...
i'll try again, as my post , err well didn't show,???? TSNR =Target snr
the package is irreverent really, but should be more obvious if someone is on the capped @12mbit value product ,if their line can support a higher sync, but truth is only the tsnr is set to shows when is should show a higher (spare snr)
Why?
Because it has not been used for the sync and is "spare" and for our info too, so why not ?
Standard User deleted
(deleted) Tue 22-Nov-11 12:41:04
Print Post

Re: Odd things about BE O2 conections


[re: Anonymous] [link to this post]
 
When a line is syncing at the maximum speed on a capped product, and has an unnecessarily high SNR margin, the DSLAM can reduce downstream output power to minimise crosstalk interfering with other peoples lines. This is what appears to have happened with the stats that XRaySpeX has provided.
Standard User XRaySpeX
(eat-sleep-adslguide) Tue 22-Nov-11 15:00:27
Print Post

Re: Odd things about BE O2 conections


[re: deleted] [link to this post]
 
So why the diff. between the Orange & O2 behaviour? They were both LLU ADSL2+.

1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
Administrator MrSaffron
(staff) Tue 22-Nov-11 15:38:35
Print Post

Re: Odd things about BE O2 conections


[re: XRaySpeX] [link to this post]
 
Because how you can configure a DSLAM is very varied

Andrew Ferguson, [email protected]
www.thinkbroadband.com - formerly known as ADSLguide.org.uk
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User epyon
(committed) Tue 22-Nov-11 16:03:22
Print Post

Re: Odd things about BE O2 conections


[re: XRaySpeX] [link to this post]
 
My BE connection is the same there both 3.5 SNR.

BE*Unlimited 17527/1412Kbps
My Broadband Speed TestMy Broadband Speed Test
Pages in this thread: 1 | [2] | 3 | 4 | 5 | 6 | 7 | (show all)   Print Thread

Jump to