General Discussion
  >> Fibre Broadband


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


Pages in this thread: 1 | 2 | [3] | (show all)   Print Thread
Standard User RobertoS
(elder) Sat 08-Oct-16 16:54:00
Print Post

Re: Can someone explain this high line attenuation please?


[re: deleted] [link to this post]
 
(Edit - typed while MrSaffron and you exchanged posts about it).

The blue and blue/white wires are a pair twisted together. That helps cancel our randon noise attacking them as they both get the attack which self-cancels. A bit like (audible) noise-cancelling headphones.

The blue should go to 2, the blue/white to 5. Similarly with the orange and orange/white.

That picture shows that two pairs have been split.

When wired correctly noise is picked up by (say blue) T2 at one end to T2 at the other, and the same noise is picked up by the blue/white wire from T5-T5. Because they are wound round each other, it largely cancels out.

In the picture T2 will pick up noise on the blue and T5 noise on the orange, but they aren't wound round each other so don't cancel out. Similarly with the blue/white and orange/white. Both pairs as wired there will get additive noise instead of largely cancelling noise.

To us it seems a bit minor as they are in the same outer casing so getting similar noise exposure, but in practice the exposure is different enough to mess up the connection.

Kindness isn't going to cure the world of all its awfulness but it's a good place to begin. Daisy Ridley.
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 57825/13835kbps @ 600m. - BQM

Edited by RobertoS (Sat 08-Oct-16 16:55:12)

Standard User deleted
(deleted) Sat 08-Oct-16 17:01:58
Print Post

Re: Can someone explain this high line attenuation please?


[re: RobertoS] [link to this post]
 
As posted previously, this is not the case with my wiring. I am using the blue and blue/white wires from the same pair (Pair 1).
Standard User RobertoS
(elder) Sat 08-Oct-16 17:17:34
Print Post

Re: Can someone explain this high line attenuation please?


[re: deleted] [link to this post]
 
Yes, I saw that. Hence my edit at the top of my post smile. I thought it worth leaving the post there rather than deleting it though.

Kindness isn't going to cure the world of all its awfulness but it's a good place to begin. Daisy Ridley.
My broadband basic info/help site - www.robertos.me.uk. Domains, site and mail hosting - Tsohost.
Connection - AAISP Home::1 80/20. Sync 57825/13835kbps @ 600m. - BQM


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

Standard User deleted
(deleted) Sat 08-Oct-16 17:40:59
Print Post

Re: Can someone explain this high line attenuation please?


[re: deleted] [link to this post]
 
Is your CAT5 wiring solid copper, or is it stranded or copper-coated-magnesium, etc?
Standard User deleted
(deleted) Sat 08-Oct-16 18:00:47
Print Post

Re: Can someone explain this high line attenuation please?


[re: deleted] [link to this post]
 
Proper solid copper. The same stuff used for commercial structured cabling.

I do not beleive the Cat5e is at fault as I get exactly the same results are the NTE5 test socket with everything else disconnected.
Standard User deleted
(deleted) Sat 08-Oct-16 18:33:31
Print Post

Re: Can someone explain this high line attenuation please?


[re: deleted] [link to this post]
 
Be wary when estimating line length.

On a logical basis, my line would be about 50 Metres long, plenty of ducting available on a green-field site in 1967 - but is in fact at least 250 Metres, as it does not follow the "obvious" route, going about 125 Metres away from my house, before returning by about another 125 Metres.

Basically all is underground, compounded by the main ducting with the E-side from the Exchange, goes past my house about 2 metres away, to reach the PCP, 50 metres away.

The excess length came to light in the 1980s, when assisting a PO/BT engineer clear a fault on it.
Pages in this thread: 1 | 2 | [3] | (show all)   Print Thread

Jump to