dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
493

sfedrgtyh5r
@75.134.188.x

sfedrgtyh5r

Anon

signal-noise ratio




those are my levels as of a minute ago

i've never seen my downstream SNR lower than 41 dB or higher than 42 dB. as far as i know, these are pretty good numbers

the actual voltages on the other hand are a bit high, i'd like them to be closer to zero... but, ya know. however, this thread is about the SNR

so my questions are:

first of all - what can i do on my end (from the demarcation to my modem) to increase the SNR. i only have internet with the local cable company. the internet modem is connected directly to the splitter (the splitter that shares with my neighbors) on the pole in my backyard. no other splitters are between me and the pole.

AND, how much of a difference (in terms of a good signal) is a SNR of 42:1 dB vs 34:1 dB. obviously higher is better, but is an increase of 8 dB a significant amount?

billaustin
they call me Mr. Bill
MVM
join:2001-10-13
North Las Vegas, NV

billaustin

MVM

There is nothing you can do to increase the SNR. It is a measurement of the difference between the Signal level and the Noise level on the line. The reading of 42 is very good. An increase of 8db is a significant amount.

The power levels are high because there is nothing else connected to the line. Adding splitters and cable (or an attenuator) will reduce the power levels. Cox likes to have them between +10 and -10, but prefers closer to 0.

The upstream power level is set by negotiation between the local node and the modem. Your level is lower because you have a good connection.

bdnhsv
join:2012-01-20
Huntsville, AL

bdnhsv to sfedrgtyh5r

Member

to sfedrgtyh5r
+3 db is double the RF power. -3 db is half the RF power. If you padded your connection to your modem by 10 db then the DS power would be about 0 - +1 and your US power would be about 45 db (which is about perfect in both directions).

Hard Harry7
join:2010-10-19
Narragansett, RI

Hard Harry7 to sfedrgtyh5r

Member

to sfedrgtyh5r
What is the underlying issue? Is your latency and speed good? If so, I say just leave it the way it is. Having a 10dB downstream vs 0dB won't really change much. Having a high downstream also gives you some pillow when the weather gets cold and signal levels usually drop.

Last, is Charter still not bonding upstream? That is probably the thing that is holding your connection back IMO.

koolman2
Premium Member
join:2002-10-01
Anchorage, AK

koolman2 to sfedrgtyh5r

Premium Member

to sfedrgtyh5r
Your SNR readings are amazing. For 256QAM you only need 31.5, but 35 is a considered good. 38 is usually considered very good. Higher SNRs don't gain you anything. Think of it as a conversation: you can hear someone quite well at a normal voice in a quiet room, but in this case the person is talking loudly. You can still hear every word they say and lowering the ambient sound won't help you hear or understand the person any better.

If anything, aquire a 9 dB attentuator to get your signal levels in line.

wsefdrtgyrv
@charter.com

wsefdrtgyrv to Hard Harry7

Anon

to Hard Harry7
said by Hard Harry7:

What is the underlying issue? Is your latency and speed good? If so, I say just leave it the way it is. Having a 10dB downstream vs 0dB won't really change much. Having a high downstream also gives you some pillow when the weather gets cold and signal levels usually drop.

Last, is Charter still not bonding upstream? That is probably the thing that is holding your connection back IMO.

i will never stop leaving things the way they are :P i will always want to mess with it and make it better

the "underlying issue" is i want to have zero jitter and the absolutely lowest latency as possible

latency is what im interested in... because as you can see here:




my download speeds are not holding me back
LittleBill
join:2013-05-24

LittleBill to sfedrgtyh5r

Member

to sfedrgtyh5r
what are your latency ans jitter numbers now? you can't get 0 either impossible nor can you really lower latency

are you going to say for gaming like everyone else for the last month?

koolman2
Premium Member
join:2002-10-01
Anchorage, AK

koolman2 to wsefdrtgyrv

Premium Member

to wsefdrtgyrv
Higher SNR numbers won't help with jitter nor latency. Call your ISP and ask them what your upstream SNR is. If it's above 30 there's no issue.

If you really want to tinker, attentuate that signal.
HELLFIRE
MVM
join:2009-11-25

HELLFIRE to sfedrgtyh5r

MVM

to sfedrgtyh5r
said by wsefdrtgyrv :

the "underlying issue" is i want to have zero jitter and the absolutely lowest latency as possible

2nd LittleBill See Profile , what are your latency and jitter numbers? I'd also add latency / jitter also depends WHERE you're trying
to send / recieve traffic from -- using a traffic analogy, you could have zero traffic in your neighborhood (your ISP) but you hit
the freeway and it's a parking lot (core internet).

...there's also alot more variables to consider as well than simply your SNR values

My 00000010bits

Regards
Tikker_LoS
join:2004-04-29
Regina, SK

Tikker_LoS to sfedrgtyh5r

Member

to sfedrgtyh5r
I read this and it comes across like you're using words that you know how to use, but not what they really mean

you have zero control of latency and/or jitter once you're outside your house

there's virtually nothing you can do to positively affect these things (unless you've got something at your end that's broken)

Hard Harry7
join:2010-10-19
Narragansett, RI

Hard Harry7 to wsefdrtgyrv

Member

to wsefdrtgyrv
said by wsefdrtgyrv :

the "underlying issue" is i want to have zero jitter and the absolutely lowest latency as possible

The only latency you can control is anywhere inside your network to the first hop after the modem. After that, its out of your hands(excluding proxy).

With that said, if your looking to improve the latency you can control, you would want to start with a tracert to the site of your choice, and look for the first public IP. Mine is about 9ms. Alot of it comes down to how close you are to the node.

wfa4sedrcs5
@charter.com

wfa4sedrcs5

Anon

said by Tikker_LoS:

I read this and it comes across like you're using words that you know how to use, but not what they really mean

you have zero control of latency and/or jitter once you're outside your house

there's virtually nothing you can do to positively affect these things (unless you've got something at your end that's broken)

i know quite a bit about how the internet works. i understand that the times you get depend on the route it has to take and the literal geography of it. i will prepare a response below regarding my latency numbers
said by Hard Harry7:

said by wsefdrtgyrv :

the "underlying issue" is i want to have zero jitter and the absolutely lowest latency as possible

The only latency you can control is anywhere inside your network to the first hop after the modem. After that, its out of your hands(excluding proxy).

With that said, if your looking to improve the latency you can control, you would want to start with a tracert to the site of your choice, and look for the first public IP. Mine is about 9ms. Alot of it comes down to how close you are to the node.

every time i tested it in the past, i get an average of 9 ms and sometimes it jumps up to 14 ms randomly even with no bandwidth use

gateway:
$ ping 75.134.188.1
 
PING 75.134.188.1 (75.134.188.1) 56(84) bytes of data.
 
64 bytes from 75.134.188.1: icmp_seq=1 ttl=254 time=7.89 ms
64 bytes from 75.134.188.1: icmp_seq=2 ttl=254 time=10.7 ms //
64 bytes from 75.134.188.1: icmp_seq=3 ttl=254 time=14.8 ms //
64 bytes from 75.134.188.1: icmp_seq=4 ttl=254 time=8.58 ms
64 bytes from 75.134.188.1: icmp_seq=5 ttl=254 time=13.0 ms //
64 bytes from 75.134.188.1: icmp_seq=6 ttl=254 time=17.8 ms //
64 bytes from 75.134.188.1: icmp_seq=7 ttl=254 time=7.57 ms
64 bytes from 75.134.188.1: icmp_seq=8 ttl=254 time=6.91 ms
64 bytes from 75.134.188.1: icmp_seq=9 ttl=254 time=8.53 ms
64 bytes from 75.134.188.1: icmp_seq=10 ttl=254 time=6.99 ms
64 bytes from 75.134.188.1: icmp_seq=11 ttl=254 time=6.45 ms
64 bytes from 75.134.188.1: icmp_seq=12 ttl=254 time=7.38 ms
64 bytes from 75.134.188.1: icmp_seq=13 ttl=254 time=7.27 ms
64 bytes from 75.134.188.1: icmp_seq=14 ttl=254 time=8.95 ms
64 bytes from 75.134.188.1: icmp_seq=15 ttl=254 time=16.0 ms //
64 bytes from 75.134.188.1: icmp_seq=16 ttl=254 time=7.24 ms
64 bytes from 75.134.188.1: icmp_seq=17 ttl=254 time=7.78 ms
64 bytes from 75.134.188.1: icmp_seq=18 ttl=254 time=7.41 ms
64 bytes from 75.134.188.1: icmp_seq=19 ttl=254 time=14.2 ms //
64 bytes from 75.134.188.1: icmp_seq=20 ttl=254 time=7.41 ms
64 bytes from 75.134.188.1: icmp_seq=21 ttl=254 time=7.84 ms
64 bytes from 75.134.188.1: icmp_seq=22 ttl=254 time=7.58 ms
 
--- 75.134.188.1 ping statistics ---
22 packets transmitted, 22 received, 0% packet loss, time 21032ms
rtt min/avg/max/mdev = 6.450/9.478/17.825/3.303 ms
 

gateway test while downloading @ 8 MB/s
$ ping 75.134.188.1
 
PING 75.134.188.1 (75.134.188.1) 56(84) bytes of data.
 
64 bytes from 75.134.188.1: icmp_seq=1 ttl=254 time=10.6 ms
64 bytes from 75.134.188.1: icmp_seq=2 ttl=254 time=9.32 ms
64 bytes from 75.134.188.1: icmp_seq=3 ttl=254 time=7.79 ms
64 bytes from 75.134.188.1: icmp_seq=4 ttl=254 time=17.2 ms
64 bytes from 75.134.188.1: icmp_seq=5 ttl=254 time=9.05 ms
64 bytes from 75.134.188.1: icmp_seq=6 ttl=254 time=7.91 ms
64 bytes from 75.134.188.1: icmp_seq=7 ttl=254 time=10.7 ms
64 bytes from 75.134.188.1: icmp_seq=8 ttl=254 time=6.80 ms
64 bytes from 75.134.188.1: icmp_seq=9 ttl=254 time=8.20 ms
64 bytes from 75.134.188.1: icmp_seq=10 ttl=254 time=8.14 ms
64 bytes from 75.134.188.1: icmp_seq=11 ttl=254 time=8.13 ms
64 bytes from 75.134.188.1: icmp_seq=12 ttl=254 time=12.4 ms
64 bytes from 75.134.188.1: icmp_seq=13 ttl=254 time=19.8 ms
64 bytes from 75.134.188.1: icmp_seq=14 ttl=254 time=8.57 ms
64 bytes from 75.134.188.1: icmp_seq=15 ttl=254 time=6.46 ms
64 bytes from 75.134.188.1: icmp_seq=16 ttl=254 time=7.17 ms
64 bytes from 75.134.188.1: icmp_seq=17 ttl=254 time=9.30 ms
64 bytes from 75.134.188.1: icmp_seq=18 ttl=254 time=11.5 ms
64 bytes from 75.134.188.1: icmp_seq=19 ttl=254 time=9.28 ms
64 bytes from 75.134.188.1: icmp_seq=20 ttl=254 time=24.6 ms // start downloading @ 8 MB/s
64 bytes from 75.134.188.1: icmp_seq=21 ttl=254 time=14.5 ms
64 bytes from 75.134.188.1: icmp_seq=22 ttl=254 time=28.3 ms
64 bytes from 75.134.188.1: icmp_seq=23 ttl=254 time=38.6 ms
64 bytes from 75.134.188.1: icmp_seq=24 ttl=254 time=34.8 ms
64 bytes from 75.134.188.1: icmp_seq=25 ttl=254 time=21.6 ms
64 bytes from 75.134.188.1: icmp_seq=26 ttl=254 time=13.3 ms
64 bytes from 75.134.188.1: icmp_seq=27 ttl=254 time=16.5 ms
64 bytes from 75.134.188.1: icmp_seq=28 ttl=254 time=38.0 ms
64 bytes from 75.134.188.1: icmp_seq=29 ttl=254 time=10.8 ms
64 bytes from 75.134.188.1: icmp_seq=30 ttl=254 time=30.2 ms
64 bytes from 75.134.188.1: icmp_seq=31 ttl=254 time=30.9 ms
64 bytes from 75.134.188.1: icmp_seq=32 ttl=254 time=30.4 ms
64 bytes from 75.134.188.1: icmp_seq=33 ttl=254 time=35.5 ms
64 bytes from 75.134.188.1: icmp_seq=34 ttl=254 time=14.0 ms
64 bytes from 75.134.188.1: icmp_seq=35 ttl=254 time=26.4 ms
64 bytes from 75.134.188.1: icmp_seq=36 ttl=254 time=40.1 ms
64 bytes from 75.134.188.1: icmp_seq=37 ttl=254 time=9.89 ms
64 bytes from 75.134.188.1: icmp_seq=38 ttl=254 time=32.1 ms
64 bytes from 75.134.188.1: icmp_seq=39 ttl=254 time=40.3 ms
64 bytes from 75.134.188.1: icmp_seq=40 ttl=254 time=37.8 ms
64 bytes from 75.134.188.1: icmp_seq=41 ttl=254 time=34.0 ms
64 bytes from 75.134.188.1: icmp_seq=42 ttl=254 time=52.8 ms
64 bytes from 75.134.188.1: icmp_seq=43 ttl=254 time=26.6 ms
64 bytes from 75.134.188.1: icmp_seq=44 ttl=254 time=7.86 ms // end downloading @ 8 MB/s
64 bytes from 75.134.188.1: icmp_seq=45 ttl=254 time=8.65 ms
64 bytes from 75.134.188.1: icmp_seq=46 ttl=254 time=7.17 ms
64 bytes from 75.134.188.1: icmp_seq=47 ttl=254 time=22.6 ms
64 bytes from 75.134.188.1: icmp_seq=48 ttl=254 time=9.98 ms
64 bytes from 75.134.188.1: icmp_seq=49 ttl=254 time=7.75 ms
64 bytes from 75.134.188.1: icmp_seq=50 ttl=254 time=10.0 ms
 
--- 75.134.188.1 ping statistics ---
50 packets transmitted, 50 received, 0% packet loss, time 49039ms
rtt min/avg/max/mdev = 6.462/18.917/52.803/12.159 ms
 

the first hop:
$ ping 96.34.32.210
 
PING 96.34.32.210 (96.34.32.210) 56(84) bytes of data.
 
64 bytes from 96.34.32.210: icmp_seq=1 ttl=253 time=10.2 ms
64 bytes from 96.34.32.210: icmp_seq=2 ttl=253 time=11.9 ms
64 bytes from 96.34.32.210: icmp_seq=3 ttl=253 time=7.36 ms
64 bytes from 96.34.32.210: icmp_seq=4 ttl=253 time=9.12 ms
64 bytes from 96.34.32.210: icmp_seq=5 ttl=253 time=9.19 ms
64 bytes from 96.34.32.210: icmp_seq=6 ttl=253 time=8.33 ms
64 bytes from 96.34.32.210: icmp_seq=7 ttl=253 time=12.8 ms
64 bytes from 96.34.32.210: icmp_seq=8 ttl=253 time=7.46 ms
64 bytes from 96.34.32.210: icmp_seq=9 ttl=253 time=7.85 ms
64 bytes from 96.34.32.210: icmp_seq=10 ttl=253 time=7.67 ms
64 bytes from 96.34.32.210: icmp_seq=11 ttl=253 time=8.69 ms
64 bytes from 96.34.32.210: icmp_seq=12 ttl=253 time=16.1 ms
64 bytes from 96.34.32.210: icmp_seq=13 ttl=253 time=7.61 ms
64 bytes from 96.34.32.210: icmp_seq=14 ttl=253 time=7.57 ms
64 bytes from 96.34.32.210: icmp_seq=15 ttl=253 time=8.04 ms
64 bytes from 96.34.32.210: icmp_seq=16 ttl=253 time=11.5 ms
64 bytes from 96.34.32.210: icmp_seq=17 ttl=253 time=7.66 ms
64 bytes from 96.34.32.210: icmp_seq=18 ttl=253 time=9.62 ms
64 bytes from 96.34.32.210: icmp_seq=19 ttl=253 time=8.99 ms
64 bytes from 96.34.32.210: icmp_seq=20 ttl=253 time=7.61 ms
64 bytes from 96.34.32.210: icmp_seq=21 ttl=253 time=8.81 ms
64 bytes from 96.34.32.210: icmp_seq=22 ttl=253 time=8.24 ms
64 bytes from 96.34.32.210: icmp_seq=23 ttl=253 time=10.7 ms
 
--- 96.34.32.210 ping statistics ---
23 packets transmitted, 23 received, 0% packet loss, time 22033ms
rtt min/avg/max/mdev = 7.360/9.279/16.176/2.114 ms
 

google.com pings:

while downloading linux torrent @ 8 MB/s:

$ ping google.com
 
PING google.com (216.58.216.78) 56(84) bytes of data.
 
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=1 ttl=52 time=20.1 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=2 ttl=52 time=28.7 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=3 ttl=52 time=33.6 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=4 ttl=52 time=46.6 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=5 ttl=52 time=65.9 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=6 ttl=52 time=56.5 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=7 ttl=52 time=45.6 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=8 ttl=52 time=42.0 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=9 ttl=52 time=42.6 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=10 ttl=52 time=47.0 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=11 ttl=52 time=56.9 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=12 ttl=52 time=54.9 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=13 ttl=52 time=38.6 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=14 ttl=52 time=32.6 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=15 ttl=52 time=52.8 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=16 ttl=52 time=38.0 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=17 ttl=52 time=53.3 ms
64 bytes from ord30s21-in-f14.1e100.net (216.58.216.78): icmp_seq=18 ttl=52 time=46.8 ms
 
--- google.com ping statistics ---
18 packets transmitted, 18 received, 0% packet loss, time 17022ms
rtt min/avg/max/mdev = 20.124/44.633/65.999/11.115 ms
 

not downloading
$ ping google.com
 
PING google.com (216.58.216.64) 56(84) bytes of data.
 
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=1 ttl=52 time=23.7 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=2 ttl=52 time=22.3 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=3 ttl=52 time=29.1 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=4 ttl=52 time=24.0 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=5 ttl=52 time=28.1 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=6 ttl=52 time=21.0 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=7 ttl=52 time=36.0 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=8 ttl=52 time=29.2 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=9 ttl=52 time=21.8 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=10 ttl=52 time=23.8 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=11 ttl=52 time=22.7 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=12 ttl=52 time=22.1 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=13 ttl=52 time=27.2 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=14 ttl=52 time=33.7 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=15 ttl=52 time=21.8 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=16 ttl=52 time=24.9 ms
64 bytes from ord30s21-in-f0.1e100.net (216.58.216.64): icmp_seq=17 ttl=52 time=21.6 ms
 
--- google.com ping statistics ---
17 packets transmitted, 17 received, 0% packet loss, time 16022ms
rtt min/avg/max/mdev = 21.048/25.516/36.033/4.303 ms
 

now that you can see my latency numbers. you can tell that during high bandwidth use, the latency spikes. i want to reduce this. i'm pretty sure this is the fault of my modem. (i don't believe my modem is faulty compared to others of the same model, it's just the design of the modem)

and, the other thing is i want to reduce the random spikes of ~15 ms when i'm not downloading or uploading anything. when my connection is idle and all i'm doing is a slow repeating ping test. i want the ping to be within ~1 ms every time. (1 ms jitter)

i can't run a pingtest.net right now because i don't have flash. but in the past when i've did their test, it would usually say i had a ~1-3 ms jitter with 20 ms ping. but we all know how notoriously inaccurate pingtest.net and speedtest.net is
LittleBill
join:2013-05-24

LittleBill

Member

yea you can't fix it, like we said before, but good luck fixing a problem, that is not a problem to begin with

v5b6n87m
@charter.com

v5b6n87m

Anon

i'm currently looking at this: »www.amazon.com/dp/B0013L48XA/

is it worth it? i fail to see how it's gonna help anything. my understanding is that as long as the signal voltages are within the spec of the modem's tuner (which mine are) and the SNR is good - you have a good connection

koolman2
Premium Member
join:2002-10-01
Anchorage, AK

koolman2

Premium Member

The closer to 0 dBmV the better. I doubt it will actually make a difference, but can't tell until you try it.

billaustin
they call me Mr. Bill
MVM
join:2001-10-13
North Las Vegas, NV

billaustin to wfa4sedrcs5

MVM

to wfa4sedrcs5
You are trying to change things you have very little control over. Once the traffic leaves your local network, you are at the mercy of all the carriers in-between you and the destination. A ping test is not the best diagnostic tool, as it is low priority traffic and at the bottom of the resource pool. Pings will spike when there is traffic, that is expected behavior. The spikes you show when downloading the file are minimal and no cause for concern. I would be more concerned about only having one upload channel available.
HELLFIRE
MVM
join:2009-11-25

HELLFIRE to sfedrgtyh5r

MVM

to sfedrgtyh5r
said by wfa4sedrcs5 :

every time i tested it in the past, i get an average of 9 ms and sometimes it jumps up to 14 ms randomly even with no bandwidth use

said by wfa4sedrcs5 :

you can tell that during high bandwidth use, the latency spikes. i want to reduce this. i'm pretty sure this is the fault of my modem.

My general rule of thumb for latency values

- ~1ms for LAN, 10ms is the upper limit, depending on your setup and distance
- ~100ms cross-country (NAmerica)
- ~150ms NAmerica to Europe
- ~300ms NAmerica to APAC

so the question is how far physically is 75.134.188.1 from where you are?

I'll also 2nd that the latency spikes could be due to ANYTHING. If you want to try and isolate this, we're not in a position to stop
you OP, but you could end up spinning your wheels and burning money for a whole lot of nothing.

My 00000010bits

Regards

wsefdrxctgyu
@charter.com

wsefdrxctgyu

Anon

said by HELLFIRE:

so the question is how far physically is 75.134.188.1 from where you are?

i would like to know this as well. but i've searched and searched and i have no way of telling where my charter headend is in monroe michigan

this is the hostname of the first hop i always get:
dtr01monrmi-tge-0-4-0-6.monr.mi.charter.com
 
HELLFIRE
MVM
join:2009-11-25

HELLFIRE to sfedrgtyh5r

MVM

to sfedrgtyh5r
...nor is Charter ever going to tell you -- trade secret and all.

Regards

defiant
Former Charter lackey
join:2013-03-22
Monroe, MI

defiant

Member

I wouldn't say it's a "trade secret", but the location of critical facilities for any industry is typically not published or disclosed without a legitimate reason.
Tikker_LoS
join:2004-04-29
Regina, SK

Tikker_LoS to sfedrgtyh5r

Member

to sfedrgtyh5r
ok, so basically, here's an analogy to what you're asking:

"It's 72 degrees in my house. normally at this time of year, it's 74 degrees outside, but on wednesdays this year it's 65 degrees and windy! if I buy a big furnace and point it out the window, can i get the temp back to 74 and calm?"

it's a ridiculous example, but it's basically what you're asking

esfzg4768
@charter.com

esfzg4768

Anon

said by Tikker_LoS:

ok, so basically, here's an analogy to what you're asking:

"It's 72 degrees in my house. normally at this time of year, it's 74 degrees outside, but on wednesdays this year it's 65 degrees and windy! if I buy a big furnace and point it out the window, can i get the temp back to 74 and calm?"

it's a ridiculous example, but it's basically what you're asking

that makes absolutely no sense and i don't know what you're trying to accomplish

DarkLogix
Texan and Proud
Premium Member
join:2008-10-23
Baytown, TX

DarkLogix to sfedrgtyh5r

Premium Member

to sfedrgtyh5r
Well if you lowered the downstream power it "might" improve the SNR slightly.

Think of it like toning down someone that's yelling in your ear, if they're screaming in your ear it's more likely to get distorted then if they're just talking.

I'd put a 10DB forward path attenuator on there.
DarkLogix

DarkLogix to esfzg4768

Premium Member

to esfzg4768
If you're goal is the best possible signal beyond reasonable measures then you can do the following.

1. get a set of forward path attenuators (I got some off ebay from a UK seller)

2. upgrade your coax from RG6 to RG11

3. make sure the grounding block is properly grounded and is a very good quality (I like to get my stuff from mjsales.net)

4. get a moca filter (to ensure that any neighbor's moco isn't getting into your system.)

I've done the above (only thing left for me is the GB to ped run is still only RG6QS but the GB to CM run is RG11)

Though I'm only ay a SNR of about 40.9

SNR
40.366 dB
40.946 dB
40.366 dB
40.366 dB
40.946 dB
40.366 dB
40.366 dB
40.366 dB

redg6f7tui
@charter.com

redg6f7tui

Anon

i havent been in this field very long so i don't have good contacts nor experience with high quality equipment/parts

charter recently buried a new coax in my backyard going from the pole splitter to my demarcation (box attached to side of my house). it's a nice thick orange cable. the F-type connectors it has look really high quality. compared to the F-type connectors my neighbors have, mine looks far superior. but then again im just using my own judgement based on mere look and feel.

i'm guessing this cable is RG11, it's certainly thicker than 18 AWG.

that orange cable goes into the demarcation box and is connected to a grounding block which is connected to a ground wire running out to the grounding bar that goes into the ground. the ground block has 1 input and 1 output. that output is got to be RG6 (18 AWG) and runs directly to my modem (about a 50 foot run)

the charter tech didn't put a terminal on the wall where the cable enters the house. just ran coax right through the hole. which in my opinion isnt a big deal and it prevents another point of noise introduction/signal loss

i want to upgrade the cable that runs from modem to grounding block outside. i was thinking belden 1694a »www.bluejeanscable.com/p ··· tech.htm

ran to a wall plate terminal like this:


but i dont want to buy a crappy one that is gonna mess with the signal quality. like i said above i have no experience and don't know good brands and such

then on the inside of the house. after the wall plate i want a 90 degree bend block like this:


again, i don't want these parts to affect the signal quality in any bad way

then from the 90 degree bend, a short 3 foot run to the modem. i might add a surge suppressor in there one day too, after i mod my modem (to protect my modded modem from damage)

i want to add capacitors to critical parts of the modem to reduce noise and help with latency

also want to add a better heatsink and fan to keep the chips cool

defiant
Former Charter lackey
join:2013-03-22
Monroe, MI
ARRIS TM1602
Asus RT-AC68
Netgear WNDR3700v4

defiant

Member

Adding a wall-plate is one thing, but everything else is overkill. As long as all coax connectors are installed properly, tightened, and you don't have any unterminated outlets, you're putting in more effort for little gain.

Also, keep in mind, many retail coax surge suppressors can cause more issues than they claim to protect against. If you insist on using one, I believe there's in-line surge-suppressors/protectors - just make sure it's meant for bi-directional cable service, rated 5-1000 Mhz.

DarkLogix
Texan and Proud
Premium Member
join:2008-10-23
Baytown, TX

1 recommendation

DarkLogix

Premium Member

said by defiant:

but everything else is overkill.

He has a SNR of 41 anything to improve it more will be overkill.

To improve the SNR past 41 you'll have to do a lot and will only get a little.

BTW I would double the Ped to GB is RG11 but it could be, but most cable co's only run RG11 to a house if its a really long run.

you'll be able to tell if its RG11 because the connector is a lot bigger (it still comes down to an F type but the rest of the connecter is bigger and it's much less flexible).