HowToFixComputers.com




Watched TopicsWatched Topics SearchSearch RegisterRegister Log in to check your private messagesLog in to check your private messages ProfileProfile Log inLog in
SB5120 & Comcast Woes
Goto page Previous  1, 2, 3, 4  Next
 
Post new topic   Reply to topic    Index -> Cable Modems
Author Message
-= Hawk =-
Guest





PostPosted: Thu Dec 21, 2006 10:58 pm    Post subject: Re: SB5120 & Comcast Woes Reply with quote

On Thu, 21 Dec 2006 19:48:48 GMT, "Poul Starz" <Starz@Astromail.com>
scribbled:

Quote:
He's not likely to answer for awhile as the RR news servers have
been down for 5 days of "maintenance" with no estimated-time-
of-completion given. TW has been *ucked up for a couple months
since absorbing Comcast and Adelphia customers in November.

Hey, why dont'cha post the same blather a few more times.

--
'What Profiteth It A Kingdom If The Oxen Be Deflated?'
Riddles II, v3
- T. Pratchett
Back to top
Timothy Daniels
Guest





PostPosted: Fri Dec 22, 2006 8:58 am    Post subject: Re: SB5120 & Comcast Woes Reply with quote

Quote:
groan> The RR news servers have been down for several days.

I have a splitter in the line for analog local stations, now, and the
modem reports 7 dBmV "Downstream", and 49 dBmV on "Upstream".
Access.TimeWarner still reports the same speeds in the mid-1 Mbps
to low 3 Mbps, but speeds measured from SpeakEasy's Los Angeles
server measure from the high 3 Mbps to high 5 Mbps, depending on
the time of day and the alignment of passing meteors. Tracerts still
report intermittent timeouts - most of them occuring within the RR
network. I'd be trying DSL right now if it weren't for the one year
committment.

*TimDaniels*

"Ed Nielsen" wrote:
Quote:
If it were me, Tim, I would pad that down by another 6dB, bringing
the downstream down to +3 and the transmit up to around +53dBmV.
Only, I would have ALL of the padding at the splitter that feeds your
cable modem. If it is a splitter, perhaps change that out for a directional
coupler of comparable value. Many engineers like to see cable modems
run out on the hot side. It helps it to be heard over any noise that
might get on the drop. 53 is perfectly fine. DOCSIS specifies a high
end of 58.

Then again, if you have a DCT(digital cable box), the increase in signal
level a DC would give it could cause it some grief. Might have to throw
in a 3dB pad on the THRU leg of the DC.


CIAO!

Ed N.

Timothy Daniels wrote:
The line technicians were by today, and they said the signal level
on the downstream side (coming into our property) was a bit high,
so they padded it down by 4-5 dB. Now the modem is reporting a
downstram signal level of 9 dBmV and an upstream signal level of
47 dBmV. It had been 15-17 downstream and 50-52 upstream.
I asked the tech who adjusted our amp if those numbers meant
NEGATIVE dB, but he said no (which may still not mean anything).

The bottom line is that the speeds have increased a bit, but it's
not really obvious due to the high variance from test to test. Tracerts
are still showing timeouts, and InternetFrog.com is showing "Quality
of Service" levels ranging between 9% and 50%, i.e. high retransmission
rates, and the VOIP test indicates that there would be lots of dropouts
and pauses. I believe it's due to congestion in the RoadRunner network.

*TimDaniels*

Back to top
$Bill
Guest





PostPosted: Fri Dec 22, 2006 11:13 am    Post subject: Re: SB5120 & Comcast Woes Reply with quote

-= Hawk =- wrote:

Quote:
On Thu, 21 Dec 2006 19:48:48 GMT, "Poul Starz" <Starz@Astromail.com
scribbled:


He's not likely to answer for awhile as the RR news servers have
been down for 5 days of "maintenance" with no estimated-time-
of-completion given. TW has been *ucked up for a couple months
since absorbing Comcast and Adelphia customers in November.


Hey, why dont'cha post the same blather a few more times.

Well, he's partially right - they're all scr**ed up but appear to at least
accept posts.
Back to top
Todd H.
Guest





PostPosted: Fri Dec 22, 2006 12:23 pm    Post subject: Re: SB5120 & Comcast Woes Reply with quote

"Timothy Daniels" <TDaniels@NoSpamDot.com> writes:

Quote:
groan> The RR news servers have been down for several days.

I have a splitter in the line for analog local stations, now, and the
modem reports 7 dBmV "Downstream", and 49 dBmV on "Upstream".
Access.TimeWarner still reports the same speeds in the mid-1 Mbps
to low 3 Mbps, but speeds measured from SpeakEasy's Los Angeles
server measure from the high 3 Mbps to high 5 Mbps, depending on
the time of day and the alignment of passing meteors. Tracerts still
report intermittent timeouts - most of them occuring within the RR
network. I'd be trying DSL right now if it weren't for the one year
committment.

*TimDaniels*

Hi Tim, I think that 49dB on teh transmit side is straining things.
Is this a traditional 2:1 splitter or is it a directional coupler?
Try eliminating the splitter for grins and re-running

ping -t www.yahoo.com

for a good long while to get a feel for your packetloss rate
before/after the elimination of the splitter. Traceroutes aren't a
great measure of packet loss.

If eliminating the splitter helps your situation, and if it's not a
directional coupler/directional tap they have in there for you, call
the cable company and get the tech's back out and nudge them in that
direction. They can slap a directional coupler in there in seconds
and it may give you another 2 or 3 dB of margin on the transmit side
and make your modem happier.

Best Regards,
--
Todd H.
http://www.toddh.net/
Back to top
Timothy Daniels
Guest





PostPosted: Fri Dec 22, 2006 1:50 pm    Post subject: Re: SB5120 & Comcast Woes Reply with quote

"Todd H." wrote:
Quote:
"Timothy Daniels" writes:

I have a splitter in the line for analog local stations, now, and the
modem reports 7 dBmV "Downstream", and 49 dBmV on "Upstream".
Access.TimeWarner still reports the same speeds in the mid-1 Mbps
to low 3 Mbps, but speeds measured from SpeakEasy's Los Angeles
server measure from the high 3 Mbps to high 5 Mbps, depending on
the time of day and the alignment of passing meteors. Tracerts still
report intermittent timeouts - most of them occuring within the RR
network. I'd be trying DSL right now if it weren't for the one year
committment.

*TimDaniels*

Hi Tim, I think that 49dB on teh transmit side is straining things.
Is this a traditional 2:1 splitter or is it a directional coupler?
Try eliminating the splitter for grins and re-running

ping -t www.yahoo.com

for a good long while to get a feel for your packetloss rate
before/after the elimination of the splitter. Traceroutes aren't a
great measure of packet loss.

If eliminating the splitter helps your situation, and if it's not a
directional coupler/directional tap they have in there for you, call
the cable company and get the tech's back out and nudge them in that
direction. They can slap a directional coupler in there in seconds
and it may give you another 2 or 3 dB of margin on the transmit side
and make your modem happier.

Best Regards,
--
Todd H.
http://www.toddh.net/



Without the 2:1 splitter, the downstream signal level rises to 10 dBmv
(from 9 dBmV) and the upstream signal level drops to 47 dBmV (from
49 dBmV). The tracerts show a quadrupling (or more) of timeouts with
the splitter removed. It seems that the lower transmit level hinders the
packets' survival rate, and that the splitter, in reducing the receive level,
causes the modem to drop its transmit level and thus increases the
timeout incidence. Is that right?

BTW, *I* put the splitter between the modem and the RR network
for analog cable TV reception of local stations. Whenever the techs
were here, the splitter had been replaced by a barrel connector
(don't ask). As far as TW is concerned, my only service from them
is RoadRunner. But no instruments measured levels within my condo
unit. The only measurements that they took directly were on the level
from the amp in the vault at the curb and on the output from the building's
amp that resulted from their padding down the signal coming from the
curb amp. The only measurements that they took specific to my modem
were the remote readings reported to them from by cell phone from the
central office. They said that it gave them more information than what
I got from the modem's webpage and, presumably, what they could learn
by tapping into the line between the wall outlet and my modem. So it's
strange that the timeouts are so much less frequent when I put my 2:1
splitter in the line - it is not what they thought the usual configuration was.

*TimDaniels*
Back to top
Fix your Windows Problems - FAST.
FREE Safe Scan Registry Check. Locate & Fix Errors in Minutes!
Ed Nielsen
Guest





PostPosted: Fri Dec 22, 2006 9:25 pm    Post subject: Re: SB5120 & Comcast Woes Reply with quote

Been running out at ~52-54dBmV for about 5 years now with no issues.
I'd much rather run at 52dBmV and be able to shout and be heard above
the noise that inherently makes its way into the line than keep my cable
modem running down around 40dBmV.


CIAO!

Ed N.

Todd H. wrote:
Quote:
Ed Nielsen <egnlsn@comcast.net> writes:

If it were me, Tim, I would pad that down by another 6dB, bringing the
downstream down to +3 and the transmit up to around +53dBmV. Only, I
would have ALL of the padding at the splitter that feeds your cable
modem. If it is a splitter, perhaps change that out for a directional
coupler of comparable value. Many engineers like to see cable modems
run out on the hot side. It helps it to be heard over any noise that
might get on the drop. 53 is perfectly fine. DOCSIS specifies a high
end of 58.

DOCSIS spec or no, in my experience on comcast and wide open west
networks, upstream >50dBmV has always correlated with intermittent
packet loss and frustration like the OP is experiencing. :-)
Back to top
Ed Nielsen
Guest





PostPosted: Fri Dec 22, 2006 9:38 pm    Post subject: Re: SB5120 & Comcast Woes Reply with quote

Lower packet loss with the modem pumping out more suggests that there
may be some noise (impulse, ingress) hopping onto your drop. Where did
they pad your cable? Right at the modem? If you can get to the main
splitter, try padding there. Don't worry about the input -- you have
plenty of room there to do what you want. You can go down to ~-12dBmV
before there would start to be any cause of concern. Heck, I used to
run at ~-12/52 for about 4 years until some plant issues caused me to
alter that. Now, I'm at +7/49, and I hate it. One of these days soon,
I'll get around to swapping out my DC to fix it.


CIAO!

Ed N.

Timothy Daniels wrote:
Quote:
Without the 2:1 splitter, the downstream signal level rises to 10 dBmv
(from 9 dBmV) and the upstream signal level drops to 47 dBmV (from
49 dBmV). The tracerts show a quadrupling (or more) of timeouts with
the splitter removed. It seems that the lower transmit level hinders the
packets' survival rate, and that the splitter, in reducing the receive
level,
causes the modem to drop its transmit level and thus increases the
timeout incidence. Is that right?

BTW, *I* put the splitter between the modem and the RR network
for analog cable TV reception of local stations. Whenever the techs
were here, the splitter had been replaced by a barrel connector
(don't ask). As far as TW is concerned, my only service from them
is RoadRunner. But no instruments measured levels within my condo
unit. The only measurements that they took directly were on the level
from the amp in the vault at the curb and on the output from the building's
amp that resulted from their padding down the signal coming from the
curb amp. The only measurements that they took specific to my modem
were the remote readings reported to them from by cell phone from the
central office. They said that it gave them more information than what
I got from the modem's webpage and, presumably, what they could learn
by tapping into the line between the wall outlet and my modem. So it's
strange that the timeouts are so much less frequent when I put my 2:1
splitter in the line - it is not what they thought the usual
configuration was.

*TimDaniels*
Back to top
Timothy Daniels
Guest





PostPosted: Sat Dec 23, 2006 12:38 am    Post subject: Re: SB5120 & Comcast Woes Reply with quote

I think you got that backwards. First, the modem appears to be
reporting a positive offset - a level *above* some reference level,
not a negative offset from some reference. Thus, with the splitter
in the line, the downstream level drops in magnitude from 10 dBmV
to 9 dBmV (this morning, and during the day yesterday, the downs-
stream level with the splitter in the line is/was 7 dBmV). And the
upstream level rose to 49 dBmV from 47 dBmV with the splitter
(today it's at 50 dBmV with the splitter.)

That's agrees with the model that the Transmit upstream level varies
counter to the downstream Received level, and it also suggests that
the upstream level is a positive value, not a value below a reference
level. Given that, it looks as if the high downstream level was set
too high for there not to be a splitter since the packet loss *increases*
when I substitute a barrel connector for the splitter.

This would make sense if the cable company always assumes that
there would be one or two TVs hung off the same line - a likely
scenario for the average unit in a condo building, but just not the
scenario in my condo unit.

*TimDaniels*


"Ed Nielsen" wrote:
Quote:
Lower packet loss with the modem pumping out more suggests that there
may be some noise (impulse, ingress) hopping onto your drop. Where did
they pad your cable? Right at the modem? If you can get to the main
splitter, try padding there. Don't worry about the input -- you have
plenty of room there to do what you want. You can go down to ~-12dBmV
before there would start to be any cause of concern. Heck, I used to
run at ~-12/52 for about 4 years until some plant issues caused me to
alter that. Now, I'm at +7/49, and I hate it. One of these days soon,
I'll get around to swapping out my DC to fix it.


CIAO!

Ed N.

Timothy Daniels wrote:
Without the 2:1 splitter, the downstream signal level rises to 10 dBmv
(from 9 dBmV) and the upstream signal level drops to 47 dBmV (from
49 dBmV). The tracerts show a quadrupling (or more) of timeouts with
the splitter removed. It seems that the lower transmit level hinders the
packets' survival rate, and that the splitter, in reducing the receive
level,
causes the modem to drop its transmit level and thus increases the
timeout incidence. Is that right?

BTW, *I* put the splitter between the modem and the RR network
for analog cable TV reception of local stations. Whenever the techs
were here, the splitter had been replaced by a barrel connector
(don't ask). As far as TW is concerned, my only service from them
is RoadRunner. But no instruments measured levels within my condo
unit. The only measurements that they took directly were on the level
from the amp in the vault at the curb and on the output from the building's
amp that resulted from their padding down the signal coming from the
curb amp. The only measurements that they took specific to my modem
were the remote readings reported to them from by cell phone from the
central office. They said that it gave them more information than what
I got from the modem's webpage and, presumably, what they could learn
by tapping into the line between the wall outlet and my modem. So it's
strange that the timeouts are so much less frequent when I put my 2:1
splitter in the line - it is not what they thought the usual
configuration was.

*TimDaniels*
Back to top
mediumhappy
Guest





PostPosted: Sat Dec 23, 2006 1:33 am    Post subject: Re: SB5120 & Comcast Woes Reply with quote

Wanted to post a follow-up to my original post.

On the advice of a friend I phoned Comcast's Philadelphia headquarters.
I told them the history, requested that they perform an ingress test at
the pedestal, and told them that my next step, if things couldn't be
resolved, would be to involve the Public Utilities Commission and the
FCC, as well as my legislators.

Within an hour there were three Comcast (not contractors, but Comcast
employees) trucks at my house. The feeds between the house and the
pedestal, the pedestal and the pole, and all the splitters on the
outside of my home, were replaced. There was a bad distribution
amplifier on our block, and all the remaining amplifiers in our
development were "out of alignment" - this was causing noise which was
destabilizing the signal and knocking me (and likely, many others) off
the 'net. They also replaced splitters and feeds inside my home, tested
signal strength at every outlet, and installed a weatherproof enclosure
outside of my home to enclose the splitter. All in all they worked in
and around my home until almost Midnight. The regional manager for
infrastructure gave me his cell number, and told me to call him
directly if there were any other problems. Finally, the folks at
Comcast corporate called me and rolled back my monthly rate to $19.95
for internet access, as a token of good will and as recompense for the
problems I experienced.

I have installed monitoring through dslreports.com (very good
suggestion, thanks!) and will be emailing the results to Comcast after
a week, so that they can see if the downtime correlates to known
outages, or if there are other problems in our area that they have to
fix. They've promised me that they will stay on this problem until I am
satisfied that it's fixed.

All in all I have to say they've gone out of their way to make me
happy. I think there's something to be said for jumping over the local
folks and bringing their corporate management into the equation - they
were able to get the right people focused on the problem, and they made
sure that someone on their end retained accountability and ownership
for my problem - definitely the right step. It should not be necessary
to so to these lengths to get a persistent yet intermittent problem
resolved, but apparently until Comcast revisits their escalation
procedures and does more to ensure customer satisfaction, it IS
necessary.

Thanks to all who commented on my post. Nice to know we're all in a
similar boat.

Pax,
D.

mediumhappy wrote:
Quote:
L&Gs:

I am a Comcast customer in the Atlanta area. My cable modem service is
down more than it's up and I'm on this ridiculous merry-go-round, where
it goes down, I troubleshoot, it's not a problem on my network, I
reboot the modem, problem still exists, I call Comcast, their tech
makes me do everything over, blames my network for a while, then we
determine it's their problem, they reset the modem, it works for a
while then goes down again, I call them back, they set an appointment
for a tech to visit, the tech shows up, tests everything and it's
working fine, then later that day it's dead again and I start the whole
process over.

Before I give up and get DSL, I am wondering if anyone has knowledge of
a utility that will allow my to monitor the availability of the
internet to my computer through the cable modem and log that
availability to a file, so that I can PROVE to them that it's down more
than it's up. I can see that they've disabled my use of SNMP, so
docsdiag won't work, but I want something a little more sophisticated
than a script that will run pings and log the results to a file.
Ideally, something that will grab the logs from the modem itself, save
them (since there appears to be no way to do that from the Surfboard
management page located at http://192.168.100.1/logs.htm), and then
snapshot the power levels upstream and downstream, etc. A Motorola tech
told me that have something that does exactly that but are prohibited
from making it available to the customers even though many of us own
our own cable modems - they claim their agreements with the cable co's
prevent them from empowering us to do anything that concrete to PROVE
how *** their service is, and if Motorola breaks that rule the cable
co's will just switch to other modem vendors who WON'T break it.

So there you go. I'm ot a coder and a pretty lousy scripter, so if
anyone can helpme find something that'll do what I need it to do, I'd
really appreciate it. Peace.
Back to top
Timothy Daniels
Guest





PostPosted: Sat Dec 23, 2006 2:22 am    Post subject: Re: SB5120 & Comcast Woes Reply with quote

It's just amazing what action you can get when you go directly to
the cages that have to be rattled. In my case, I went directly to
the office of the field ops supervisor and got 2 trucks and 3 technicians
out the very next day. I think they reason that if you go that far to get to
them, the next step you'll take is to go to the government offices which
just love to make notes for the next regulatory hearing. It's too bad
that a customer has to so far and expend so much time and energy to
get any real response over "unplug and re-plug in your modem, then
restart your computer".

*TimDaniels*

"mediumhappy" wrote:
Quote:
Wanted to post a follow-up to my original post.

On the advice of a friend I phoned Comcast's Philadelphia headquarters.
I told them the history, requested that they perform an ingress test at
the pedestal, and told them that my next step, if things couldn't be
resolved, would be to involve the Public Utilities Commission and the
FCC, as well as my legislators.

Within an hour there were three Comcast (not contractors, but Comcast
employees) trucks at my house. The feeds between the house and the
pedestal, the pedestal and the pole, and all the splitters on the
outside of my home, were replaced. There was a bad distribution
amplifier on our block, and all the remaining amplifiers in our
development were "out of alignment" - this was causing noise which was
destabilizing the signal and knocking me (and likely, many others) off
the 'net. They also replaced splitters and feeds inside my home, tested
signal strength at every outlet, and installed a weatherproof enclosure
outside of my home to enclose the splitter. All in all they worked in
and around my home until almost Midnight. The regional manager for
infrastructure gave me his cell number, and told me to call him
directly if there were any other problems. Finally, the folks at
Comcast corporate called me and rolled back my monthly rate to $19.95
for internet access, as a token of good will and as recompense for the
problems I experienced.

I have installed monitoring through dslreports.com (very good
suggestion, thanks!) and will be emailing the results to Comcast after
a week, so that they can see if the downtime correlates to known
outages, or if there are other problems in our area that they have to
fix. They've promised me that they will stay on this problem until I am
satisfied that it's fixed.

All in all I have to say they've gone out of their way to make me
happy. I think there's something to be said for jumping over the local
folks and bringing their corporate management into the equation - they
were able to get the right people focused on the problem, and they made
sure that someone on their end retained accountability and ownership
for my problem - definitely the right step. It should not be necessary
to so to these lengths to get a persistent yet intermittent problem
resolved, but apparently until Comcast revisits their escalation
procedures and does more to ensure customer satisfaction, it IS
necessary.

Thanks to all who commented on my post. Nice to know we're all in a
similar boat.

Pax,
D.

mediumhappy wrote:
L&Gs:

I am a Comcast customer in the Atlanta area. My cable modem service is
down more than it's up and I'm on this ridiculous merry-go-round, where
it goes down, I troubleshoot, it's not a problem on my network, I
reboot the modem, problem still exists, I call Comcast, their tech
makes me do everything over, blames my network for a while, then we
determine it's their problem, they reset the modem, it works for a
while then goes down again, I call them back, they set an appointment
for a tech to visit, the tech shows up, tests everything and it's
working fine, then later that day it's dead again and I start the whole
process over.

Before I give up and get DSL, I am wondering if anyone has knowledge of
a utility that will allow my to monitor the availability of the
internet to my computer through the cable modem and log that
availability to a file, so that I can PROVE to them that it's down more
than it's up. I can see that they've disabled my use of SNMP, so
docsdiag won't work, but I want something a little more sophisticated
than a script that will run pings and log the results to a file.
Ideally, something that will grab the logs from the modem itself, save
them (since there appears to be no way to do that from the Surfboard
management page located at http://192.168.100.1/logs.htm), and then
snapshot the power levels upstream and downstream, etc. A Motorola tech
told me that have something that does exactly that but are prohibited
from making it available to the customers even though many of us own
our own cable modems - they claim their agreements with the cable co's
prevent them from empowering us to do anything that concrete to PROVE
how *** their service is, and if Motorola breaks that rule the cable
co's will just switch to other modem vendors who WON'T break it.

So there you go. I'm ot a coder and a pretty lousy scripter, so if
anyone can helpme find something that'll do what I need it to do, I'd
really appreciate it. Peace.
Back to top
Fix your Windows Problems - FAST.
FREE Safe Scan Registry Check. Locate & Fix Errors in Minutes!
Ed Nielsen
Guest





PostPosted: Sat Dec 23, 2006 10:49 pm    Post subject: Re: SB5120 & Comcast Woes Reply with quote

That "reference level" (as you call it), like most numbers that have a
(+) or a (-) before them is 0. DOCSIS says that cable modems have an
input level window of -15 - +15dBmV, which simply means that as long as
the input signal level is within that window, it will work. The output
level window, as dictated by DOCSIS, is +8 - +58dBmV. Again, as long as
the output level of the cable modem is within that window, it will work.

The input level, of course, is determined by the plant/drop system. For
example: There is a line extender (amplifier) at the pedestal that
feeds your house. [Single family home with a white picket fence and a
couple of elm trees in the front yard out in the suburbs. Can't forget
the 2 dogs and a cat, a swing on the front porch, a vegetable garden,
and a few fruit trees out back, etc.] The tap on the output of that
L.E. is a 26 value tap, and the length of your drop is 100', and the
DOCSIS frequency is 600MHz, and it is a QAM256 system. The L.E is
running out at 44dBmV (no slope, the output is flat), which equates to
18dBmV coming out of the tap. 100 feet of RG 6 loses ~5dB@600MHz, so
you a level of 13dBmV at the groundblock. In a QAM256 system, the data
carrier runs at 6dB below the nearest analog channel, so that 13dBmV
becomes 7dBmV. Place a cable modem right at the groundblock, and it
will see an input level of +7dBmV. Say you have a TV set in the family
room and your computer is in a room 25' from the groundblock. A 2-way
splitter loses ~3.9dB at 600MHz and the 25' drop to the cable modem
loses 1.25dB. That 7dBmV at the groundblock then becomes (+7-3.9-1.25=)
1.85dBmV at the input of the cable modem. Suppose you have 4 TV sets.
The input level at your cable modem would then be (7-7.9-1.25=)
-2.15dBmV. Change the attenuation and the input level changes by the
same amount. A 30dB wide input level, cable modems have.

On the output side in the same scenario, the return amp in the L.E.
wants to see ~10dBmV. The pathway from cable modem is the drop and the
tap. Let's say that the upstream frequency is 22MHz. RG 6 loses
~1.25dB/100' at 22MHz. The pathway to that amp has the signal losing
1.25dB (drop) and 26dB (tap). 10 (required input level to the amp) + 26
(tap) + 1.25 (drop) would have the cable modem pumping out 37.25dBmV.
One TV (2-way splitter) and the cable modem 25' from the groundblock
would have it pumping out (10+26+1.253.6+.31=) 41.16. Four TVs would
necessitate that the modem transmit at 44.56dBmV.

The CMTS (Cable Modem Termination System (in the headend)) wants a
signal level of 0dBmV at its input. No wide window like cable modems
have -- it wants 0dBmV. If the attenuation at a cable modem changes,
the CMTS tells the modem to increase or decrease its output level
accordingly. If a cable modem runs so as to hit the CMTS with too hot
of a signal, the CMTS tells it to turn itself down. Too little and it
tells the modem to turn itself up. When you remove the splitter from
your drop, you reduce the attenuation of your drop by 3.5dB, which means
that there is 3.5dBmV more signal hitting the CMTS than previously, so
the CMTS tells the modem to turn itself down. Put it back in and the
modem is told to crank up the power to compensate for the increase in
attenuation. That is why the transmit levels vary when you
remove/insert the splitter.

If noise gets into the line, whether it be in the drop or somewhere in
the plant, the CMTS can't hear the cable modem as well as it needs to,
so it tells the modem to "speak louder," same thing as you do when
conversing with someone on the sidewalk and a loud car drives by. Noise
can be ingress from a local broadcaster or impulse noise such as from a
blow dryer or vacuum cleaner.


CIAO!

Ed N.



Timothy Daniels wrote:
Quote:
I think you got that backwards. First, the modem appears to be
reporting a positive offset - a level *above* some reference level,
not a negative offset from some reference. Thus, with the splitter
in the line, the downstream level drops in magnitude from 10 dBmV
to 9 dBmV (this morning, and during the day yesterday, the downs-
stream level with the splitter in the line is/was 7 dBmV). And the
upstream level rose to 49 dBmV from 47 dBmV with the splitter
(today it's at 50 dBmV with the splitter.)

That's agrees with the model that the Transmit upstream level varies
counter to the downstream Received level, and it also suggests that
the upstream level is a positive value, not a value below a reference
level. Given that, it looks as if the high downstream level was set
too high for there not to be a splitter since the packet loss *increases*
when I substitute a barrel connector for the splitter.

This would make sense if the cable company always assumes that
there would be one or two TVs hung off the same line - a likely
scenario for the average unit in a condo building, but just not the
scenario in my condo unit.

*TimDaniels*


"Ed Nielsen" wrote:
Lower packet loss with the modem pumping out more suggests that there
may be some noise (impulse, ingress) hopping onto your drop. Where
did they pad your cable? Right at the modem? If you can get to the
main splitter, try padding there. Don't worry about the input -- you
have plenty of room there to do what you want. You can go down to
~-12dBmV before there would start to be any cause of concern. Heck, I
used to run at ~-12/52 for about 4 years until some plant issues
caused me to alter that. Now, I'm at +7/49, and I hate it. One of
these days soon, I'll get around to swapping out my DC to fix it.


CIAO!

Ed N.

Timothy Daniels wrote:
Without the 2:1 splitter, the downstream signal level rises to 10 dBmv
(from 9 dBmV) and the upstream signal level drops to 47 dBmV (from
49 dBmV). The tracerts show a quadrupling (or more) of timeouts with
the splitter removed. It seems that the lower transmit level hinders
the
packets' survival rate, and that the splitter, in reducing the
receive level,
causes the modem to drop its transmit level and thus increases the
timeout incidence. Is that right?

BTW, *I* put the splitter between the modem and the RR network
for analog cable TV reception of local stations. Whenever the techs
were here, the splitter had been replaced by a barrel connector
(don't ask). As far as TW is concerned, my only service from them
is RoadRunner. But no instruments measured levels within my condo
unit. The only measurements that they took directly were on the level
from the amp in the vault at the curb and on the output from the
building's
amp that resulted from their padding down the signal coming from the
curb amp. The only measurements that they took specific to my modem
were the remote readings reported to them from by cell phone from the
central office. They said that it gave them more information than what
I got from the modem's webpage and, presumably, what they could learn
by tapping into the line between the wall outlet and my modem. So it's
strange that the timeouts are so much less frequent when I put my 2:1
splitter in the line - it is not what they thought the usual
configuration was.

*TimDaniels*
Back to top
Eric
Guest





PostPosted: Sat Dec 23, 2006 11:42 pm    Post subject: Re: SB5120 & Comcast Woes Reply with quote

Ed Nielsen wrote:
Quote:
Been running out at ~52-54dBmV for about 5 years now with no issues.
I'd much rather run at 52dBmV and be able to shout and be heard above
the noise that inherently makes its way into the line than keep my cable
modem running down around 40dBmV.


CIAO!

Ed N.

Todd H. wrote:
Ed Nielsen <egnlsn@comcast.net> writes:

If it were me, Tim, I would pad that down by another 6dB, bringing the
downstream down to +3 and the transmit up to around +53dBmV. Only, I
would have ALL of the padding at the splitter that feeds your cable
modem. If it is a splitter, perhaps change that out for a directional
coupler of comparable value. Many engineers like to see cable modems
run out on the hot side. It helps it to be heard over any noise that
might get on the drop. 53 is perfectly fine. DOCSIS specifies a high
end of 58.

DOCSIS spec or no, in my experience on comcast and wide open west
networks, upstream >50dBmV has always correlated with intermittent
packet loss and frustration like the OP is experiencing. :-)


If you are in an area fed from poles (aerial), go outside and follow
your drop to the line. You will see a small box called a tap. There
should be a number showing. Subtract that number from your modem
transmit level. Then subtract 3 dB for every 2-way splitter, 7dB for
every 4 way and 11dB for every 8 way in the line between your modem and
the tap. Subtract 1dB for every 100' of coax. The remainder should be
equal to between 15 and 20dB (most systems that were rebuild by AT&T
Broadband should be about 17dB).

Example:
26-4 tap
4 way splitter
150' drop
50' run to outlet
17dB amplifier drive level
modem should transmit at 52dB

Usually, systems are designed to make modems run about 45-50dB. Lower
value taps (further away from an amp) take into account increased cable
loss, splitters, and other devices. The tap in the example above will
be directly connected to an amplifier.
Back to top
Timothy Daniels
Guest





PostPosted: Sun Dec 24, 2006 6:53 am    Post subject: Re: SB5120 & Comcast Woes Reply with quote

Yup, that all sounds right. :-) And it sounds like the cable modem
is receiving and transmitting the right signal levels. But why would
the packet loss increase when the barrel connector is substituted
for the splitter, thus causing the upstream signal level to rise from
+47dBmV to +49 dBmV as a result of the downstream signal level
dropping from +10 dBmv to +7 dBmV? I'd think that the louder
outgoing signal would better the signal-to-noise ratio. as seen by
the network.

*TimDaniels*


"Ed Nielsen" wrote:
Quote:
That "reference level" (as you call it), like most numbers that have a
(+) or a (-) before them is 0. DOCSIS says that cable modems have an
input level window of -15 - +15dBmV, which simply means that as long as
the input signal level is within that window, it will work. The output
level window, as dictated by DOCSIS, is +8 - +58dBmV. Again, as long as
the output level of the cable modem is within that window, it will work.

The input level, of course, is determined by the plant/drop system. For
example: There is a line extender (amplifier) at the pedestal that
feeds your house. [Single family home with a white picket fence and a
couple of elm trees in the front yard out in the suburbs. Can't forget
the 2 dogs and a cat, a swing on the front porch, a vegetable garden,
and a few fruit trees out back, etc.] The tap on the output of that
L.E. is a 26 value tap, and the length of your drop is 100', and the
DOCSIS frequency is 600MHz, and it is a QAM256 system. The L.E is
running out at 44dBmV (no slope, the output is flat), which equates to
18dBmV coming out of the tap. 100 feet of RG 6 loses ~5dB@600MHz, so
you a level of 13dBmV at the groundblock. In a QAM256 system, the data
carrier runs at 6dB below the nearest analog channel, so that 13dBmV
becomes 7dBmV. Place a cable modem right at the groundblock, and it
will see an input level of +7dBmV. Say you have a TV set in the family
room and your computer is in a room 25' from the groundblock. A 2-way
splitter loses ~3.9dB at 600MHz and the 25' drop to the cable modem
loses 1.25dB. That 7dBmV at the groundblock then becomes (+7-3.9-1.25=)
1.85dBmV at the input of the cable modem. Suppose you have 4 TV sets.
The input level at your cable modem would then be (7-7.9-1.25=)
-2.15dBmV. Change the attenuation and the input level changes by the
same amount. A 30dB wide input level, cable modems have.

On the output side in the same scenario, the return amp in the L.E.
wants to see ~10dBmV. The pathway from cable modem is the drop and the
tap. Let's say that the upstream frequency is 22MHz. RG 6 loses
~1.25dB/100' at 22MHz. The pathway to that amp has the signal losing
1.25dB (drop) and 26dB (tap). 10 (required input level to the amp) + 26
(tap) + 1.25 (drop) would have the cable modem pumping out 37.25dBmV.
One TV (2-way splitter) and the cable modem 25' from the groundblock
would have it pumping out (10+26+1.253.6+.31=) 41.16. Four TVs would
necessitate that the modem transmit at 44.56dBmV.

The CMTS (Cable Modem Termination System (in the headend)) wants a
signal level of 0dBmV at its input. No wide window like cable modems
have -- it wants 0dBmV. If the attenuation at a cable modem changes,
the CMTS tells the modem to increase or decrease its output level
accordingly. If a cable modem runs so as to hit the CMTS with too hot
of a signal, the CMTS tells it to turn itself down. Too little and it
tells the modem to turn itself up. When you remove the splitter from
your drop, you reduce the attenuation of your drop by 3.5dB, which means
that there is 3.5dBmV more signal hitting the CMTS than previously, so
the CMTS tells the modem to turn itself down. Put it back in and the
modem is told to crank up the power to compensate for the increase in
attenuation. That is why the transmit levels vary when you
remove/insert the splitter.

If noise gets into the line, whether it be in the drop or somewhere in
the plant, the CMTS can't hear the cable modem as well as it needs to,
so it tells the modem to "speak louder," same thing as you do when
conversing with someone on the sidewalk and a loud car drives by. Noise
can be ingress from a local broadcaster or impulse noise such as from a
blow dryer or vacuum cleaner.


CIAO!

Ed N.



Timothy Daniels wrote:
I think you got that backwards. First, the modem appears to be
reporting a positive offset - a level *above* some reference level,
not a negative offset from some reference. Thus, with the splitter
in the line, the downstream level drops in magnitude from 10 dBmV
to 9 dBmV (this morning, and during the day yesterday, the downs-
stream level with the splitter in the line is/was 7 dBmV). And the
upstream level rose to 49 dBmV from 47 dBmV with the splitter
(today it's at 50 dBmV with the splitter.)

That's agrees with the model that the Transmit upstream level varies
counter to the downstream Received level, and it also suggests that
the upstream level is a positive value, not a value below a reference
level. Given that, it looks as if the high downstream level was set
too high for there not to be a splitter since the packet loss *increases*
when I substitute a barrel connector for the splitter.

This would make sense if the cable company always assumes that
there would be one or two TVs hung off the same line - a likely
scenario for the average unit in a condo building, but just not the
scenario in my condo unit.

*TimDaniels*


"Ed Nielsen" wrote:
Lower packet loss with the modem pumping out more suggests that there
may be some noise (impulse, ingress) hopping onto your drop. Where
did they pad your cable? Right at the modem? If you can get to the
main splitter, try padding there. Don't worry about the input -- you
have plenty of room there to do what you want. You can go down to
~-12dBmV before there would start to be any cause of concern. Heck, I
used to run at ~-12/52 for about 4 years until some plant issues
caused me to alter that. Now, I'm at +7/49, and I hate it. One of
these days soon, I'll get around to swapping out my DC to fix it.


CIAO!

Ed N.

Timothy Daniels wrote:
Without the 2:1 splitter, the downstream signal level rises to 10 dBmv
(from 9 dBmV) and the upstream signal level drops to 47 dBmV (from
49 dBmV). The tracerts show a quadrupling (or more) of timeouts with
the splitter removed. It seems that the lower transmit level hinders
the
packets' survival rate, and that the splitter, in reducing the
receive level,
causes the modem to drop its transmit level and thus increases the
timeout incidence. Is that right?

BTW, *I* put the splitter between the modem and the RR network
for analog cable TV reception of local stations. Whenever the techs
were here, the splitter had been replaced by a barrel connector
(don't ask). As far as TW is concerned, my only service from them
is RoadRunner. But no instruments measured levels within my condo
unit. The only measurements that they took directly were on the level
from the amp in the vault at the curb and on the output from the
building's
amp that resulted from their padding down the signal coming from the
curb amp. The only measurements that they took specific to my modem
were the remote readings reported to them from by cell phone from the
central office. They said that it gave them more information than what
I got from the modem's webpage and, presumably, what they could learn
by tapping into the line between the wall outlet and my modem. So it's
strange that the timeouts are so much less frequent when I put my 2:1
splitter in the line - it is not what they thought the usual
configuration was.

*TimDaniels*
Back to top
Ed Nielsen
Guest





PostPosted: Sun Dec 24, 2006 7:23 am    Post subject: Re: SB5120 & Comcast Woes Reply with quote

It isn't packet loss that causes the modem to pump out more -- nor is it
because the downstream has changed. [You could use a couple of diplex
filters (not the satellite ones but similar in purpose) that separate
the forward path from the return path, pad the downstream down as much
as you want (or even amplify it) and you would see virtually no change
in the transmit level of the cable modem.] It is merely that because of
the reduced attenuation on the drop, the cable modem is hitting the CMTS
too hot, so it is told to turn down.

That suggests to me that there might be something (noise) getting into
the drop between the cable modem and the splitter/barrel location. When
you insert the splitter, you lower the signal level hitting the CMTS, so
it tells the cable modem to increase its transmit level. The signal
level from the splice location back to the lockbox remains pretty much
the same whether the splitter is in there or not -- it is only in the
portion of the drop from that location to the outlet that sees the
increase/decrease in signal level as the modem's transmit level changes.
Could that piece run parallel to some A.C. lines for awhile? There
could be something that is induced onto and is riding on the shield
until it finds a spot where it can leak onto the center conductor. Have
you tried grounding the splitter? If there is something riding on the
shield, that could give it somewhere to go where it will do no harm.


CIAO!

Ed N.

Timothy Daniels wrote:
Quote:
Yup, that all sounds right. :-) And it sounds like the cable modem
is receiving and transmitting the right signal levels. But why would
the packet loss increase when the barrel connector is substituted
for the splitter, thus causing the upstream signal level to rise from
+47dBmV to +49 dBmV as a result of the downstream signal level
dropping from +10 dBmv to +7 dBmV? I'd think that the louder
outgoing signal would better the signal-to-noise ratio. as seen by
the network.

*TimDaniels*


"Ed Nielsen" wrote:
That "reference level" (as you call it), like most numbers that have a
(+) or a (-) before them is 0. DOCSIS says that cable modems have an
input level window of -15 - +15dBmV, which simply means that as long
as the input signal level is within that window, it will work. The
output level window, as dictated by DOCSIS, is +8 - +58dBmV. Again,
as long as the output level of the cable modem is within that window,
it will work.

The input level, of course, is determined by the plant/drop system.
For example: There is a line extender (amplifier) at the pedestal
that feeds your house. [Single family home with a white picket fence
and a couple of elm trees in the front yard out in the suburbs. Can't
forget the 2 dogs and a cat, a swing on the front porch, a vegetable
garden, and a few fruit trees out back, etc.] The tap on the output
of that L.E. is a 26 value tap, and the length of your drop is 100',
and the DOCSIS frequency is 600MHz, and it is a QAM256 system. The
L.E is running out at 44dBmV (no slope, the output is flat), which
equates to 18dBmV coming out of the tap. 100 feet of RG 6 loses
~5dB@600MHz, so you a level of 13dBmV at the groundblock. In a QAM256
system, the data carrier runs at 6dB below the nearest analog channel,
so that 13dBmV becomes 7dBmV. Place a cable modem right at the
groundblock, and it will see an input level of +7dBmV. Say you have a
TV set in the family room and your computer is in a room 25' from the
groundblock. A 2-way splitter loses ~3.9dB at 600MHz and the 25' drop
to the cable modem loses 1.25dB. That 7dBmV at the groundblock then
becomes (+7-3.9-1.25=) 1.85dBmV at the input of the cable modem.
Suppose you have 4 TV sets. The input level at your cable modem would
then be (7-7.9-1.25=) -2.15dBmV. Change the attenuation and the input
level changes by the same amount. A 30dB wide input level, cable
modems have.

On the output side in the same scenario, the return amp in the L.E.
wants to see ~10dBmV. The pathway from cable modem is the drop and
the tap. Let's say that the upstream frequency is 22MHz. RG 6 loses
~1.25dB/100' at 22MHz. The pathway to that amp has the signal losing
1.25dB (drop) and 26dB (tap). 10 (required input level to the amp) +
26 (tap) + 1.25 (drop) would have the cable modem pumping out
37.25dBmV. One TV (2-way splitter) and the cable modem 25' from the
groundblock would have it pumping out (10+26+1.253.6+.31=) 41.16.
Four TVs would necessitate that the modem transmit at 44.56dBmV.

The CMTS (Cable Modem Termination System (in the headend)) wants a
signal level of 0dBmV at its input. No wide window like cable modems
have -- it wants 0dBmV. If the attenuation at a cable modem changes,
the CMTS tells the modem to increase or decrease its output level
accordingly. If a cable modem runs so as to hit the CMTS with too hot
of a signal, the CMTS tells it to turn itself down. Too little and it
tells the modem to turn itself up. When you remove the splitter from
your drop, you reduce the attenuation of your drop by 3.5dB, which
means that there is 3.5dBmV more signal hitting the CMTS than
previously, so the CMTS tells the modem to turn itself down. Put it
back in and the modem is told to crank up the power to compensate for
the increase in attenuation. That is why the transmit levels vary
when you remove/insert the splitter.

If noise gets into the line, whether it be in the drop or somewhere in
the plant, the CMTS can't hear the cable modem as well as it needs to,
so it tells the modem to "speak louder," same thing as you do when
conversing with someone on the sidewalk and a loud car drives by.
Noise can be ingress from a local broadcaster or impulse noise such as
from a blow dryer or vacuum cleaner.


CIAO!

Ed N.



Timothy Daniels wrote:
I think you got that backwards. First, the modem appears to be
reporting a positive offset - a level *above* some reference level,
not a negative offset from some reference. Thus, with the splitter
in the line, the downstream level drops in magnitude from 10 dBmV
to 9 dBmV (this morning, and during the day yesterday, the downs-
stream level with the splitter in the line is/was 7 dBmV). And the
upstream level rose to 49 dBmV from 47 dBmV with the splitter
(today it's at 50 dBmV with the splitter.)

That's agrees with the model that the Transmit upstream level varies
counter to the downstream Received level, and it also suggests that
the upstream level is a positive value, not a value below a reference
level. Given that, it looks as if the high downstream level was set
too high for there not to be a splitter since the packet loss
*increases*
when I substitute a barrel connector for the splitter.

This would make sense if the cable company always assumes that
there would be one or two TVs hung off the same line - a likely
scenario for the average unit in a condo building, but just not the
scenario in my condo unit.

*TimDaniels*


"Ed Nielsen" wrote:
Lower packet loss with the modem pumping out more suggests that
there may be some noise (impulse, ingress) hopping onto your drop.
Where did they pad your cable? Right at the modem? If you can get
to the main splitter, try padding there. Don't worry about the
input -- you have plenty of room there to do what you want. You can
go down to ~-12dBmV before there would start to be any cause of
concern. Heck, I used to run at ~-12/52 for about 4 years until
some plant issues caused me to alter that. Now, I'm at +7/49, and I
hate it. One of these days soon, I'll get around to swapping out my
DC to fix it.


CIAO!

Ed N.

Timothy Daniels wrote:
Without the 2:1 splitter, the downstream signal level rises to 10
dBmv
(from 9 dBmV) and the upstream signal level drops to 47 dBmV (from
49 dBmV). The tracerts show a quadrupling (or more) of timeouts with
the splitter removed. It seems that the lower transmit level
hinders the
packets' survival rate, and that the splitter, in reducing the
receive level,
causes the modem to drop its transmit level and thus increases the
timeout incidence. Is that right?

BTW, *I* put the splitter between the modem and the RR network
for analog cable TV reception of local stations. Whenever the techs
were here, the splitter had been replaced by a barrel connector
(don't ask). As far as TW is concerned, my only service from them
is RoadRunner. But no instruments measured levels within my condo
unit. The only measurements that they took directly were on the level
from the amp in the vault at the curb and on the output from the
building's
amp that resulted from their padding down the signal coming from the
curb amp. The only measurements that they took specific to my modem
were the remote readings reported to them from by cell phone from the
central office. They said that it gave them more information than
what
I got from the modem's webpage and, presumably, what they could learn
by tapping into the line between the wall outlet and my modem. So
it's
strange that the timeouts are so much less frequent when I put my 2:1
splitter in the line - it is not what they thought the usual
configuration was.

*TimDaniels*
Back to top
Warren
Guest





PostPosted: Sun Dec 24, 2006 1:47 pm    Post subject: Re: SB5120 & Comcast Woes Reply with quote

Ed Nielsen <egnlsn@comcast.net> wrote:
Quote:
It isn't packet loss that causes the modem to pump out more --

That's an important thing to keep in mind. TCP/IP packets is just the data
that's carried over an RF signal on the coax. You could have 100% or 0%
packet loss, and it wouldn't have any affect upon how the RF signal levels
are negotiated.

In other words, the railroad tower operator doesn't care if the trains
have people in them or not, as long as they're arriving at and leaving the
stations at the correct time. The railroad tower operator doesn't even
know if the arriving train had any people on it when it left the last
station, so even if it was full when it left station one, if it arrives at
station number two on-time, it's a success even if the train is now empty.

Of course if the train doesn't arrive at all, the passengers can't arrive,
either. So a crappy RF signal could cause packet loss, but packet loss
doesn't have to be related to a crappy RF signal. And packet loss won't
have any affect on the RF signal levels.

--
Warren H.

==========
Disclaimer: My views reflect those of myself, and not my
employer, my friends, nor (as she often tells me) my wife.
Any resemblance to the views of anybody living or dead is
coincidental. No animals were hurt in the writing of this
response -- unless you count my dog who desperately wants
to go outside now.

Shop for networking gear:
http://www.holzemville.com/mall/linksys
http://www.holzemville.com/mall/netgear
Back to top
Display posts from previous:   
Post new topic   Reply to topic    Index -> Cable Modems All times are GMT
Goto page Previous  1, 2, 3, 4  Next
Page 2 of 4

 

 MemberlistMemberlist  UsergroupsUsergroups



Powered by p|-|pBB

Featured Sites: DIY Projects