In my case, the fiber only comes to the junction on the street. It's copper
all the way from there. Anything over about 25W in my
case was enough to cause the connection to fail. And we had about half the
annual output of Fairrite's goodies put on every
connection point, run and wire they could find.
Here's the funny part - it was decided by ATT that this was not really a
classic signal overload case here - it was a side effect of
the way the firmware implementation was done.
Apparently the uverse box in the house - when it starts up - scans the band and
excludes communication where it does not have a good
SNR with the mother ship. That's why things like local BC stations don't
affect the box - even though it's baseband signal runs
right through the BC band. Good so far...
However, the modem only does this at excluding action at initialization. If it
encounters an interference after startup (like my CW
or RTTY transmission), the box cycles in a reboot operation in an attempt to
clear the problem. But rather than understanding that
some signals are intermittent - and just excluding and trying the band at some
time later - it continues to cycle in this restart
loop until my signal goes away!
73, Jeff ACØC
From: Peter Laws
Sent: Tuesday, February 15, 2011 3:28 PM
Subject: Re: [RFI] U-Verse problem update
On Tue, Feb 15, 2011 at 15:18, Joe <email@example.com> wrote:
> What bothers me about this is that U-verse in not conducted by copper
> cabling..it is all optical fibre...how is an RF signal getting in and being
> carried by fibre?
Not all U-Verse installs are FTTH - your friend is lucky. Many are
FTTN with copper from there.
Peter Laws | N5UWY | plaws plaws net | Travel by Train!
RFI mailing list
RFI mailing list