Mattheww5's profile

Contributor

 • 

28 Messages

Friday, January 15th, 2021 4:00 PM

Closed

Downstream power levels

Are these power levels within range? My downstream levels on some of my channels are ranging from 10.5 to 12. I'm experiencing t3 timeouts and reboots.

Expert

 • 

103.5K Messages

3 years ago

That's high to being out of spec. What do the upstream power levels look like ?

Contributor

 • 

28 Messages

3 years ago

my upstream has 5 channels locked and range from 41 to 45.3. my number 5 channel is at 1280 ksym/sec and mother 4 are at 5120 ksym/sec

Expert

 • 

103.5K Messages

3 years ago

Those aren't current. These are;

 

 

Specification      Min             Max

Downstream Power Level  
Cable Modems-10dBmV+10dBmV
Gateways and EMTAs-7dBmV+7dBmV
Downstream Signal to Noise Ratio35dB-
Upstream Power Level+35dBmV+50dBmV
Upstream Signal to Noise Ratio31dB-
Upstream Receive Power-2dBmV+2dBmV

 

Expert

 • 

103.5K Messages

3 years ago


@Matthewwebster5 wrote:

my upstream has 5 channels locked and range from 41 to 45.3. my number 5 channel is at 1280 ksym/sec and mother 4 are at 5120 ksym/sec


They're o/k. 

Problem Solver

 • 

511 Messages

3 years ago

Copied from another thread; these are the numbers for Comcast.  You may read other sources that cite different numbers, but these are the specs for Comcast:

 

Comcast modem level specs

Begin Quote----------------------------------------------------------------------------

These are the Comcast system / cable plant spec from the troubleshooting tips sticky topic at the top of this board. Again, they are the only ones that really matter;

 

Downstream Power Levels: -8dBmV to  +10dBmV

Downstream Signal to Noise Ratio (SNR):  >35dB 

Upstream Power Level:  +25dBmV to +54dBmV

Upstream Signal to Noise Ratio (uSNR): >31dB  

Upstream Receive Power: -2dBmV to +2dBmV

End Quote-----------------------------------------------------------------------------------------

 

Contributor

 • 

28 Messages

3 years ago

These are ok for a docsis 3.0 modem? My power levels are fluctuating so much now. I just upgraded from 200mbps to 600mbps and I’m not getting the new speed. I’m using a netgear c7000v2 gateway.

Contributor

 • 

28 Messages

3 years ago

I just recently upgraded to the extreme pro 600mbps plan. On the website the plan shows up correctly, while in the my account app it still shows my plan as being the 200mbps plan. When I speed test I only get 200-250mbps and not the 600

Contributor

 • 

28 Messages

3 years ago

i spoke to tech support today and they are sending a tech to check the lines. i am getting a lot of t3 timeout errors and fluctuating signal levels that could verify on their end. i already had the drop replaced about 2-3 months ago because it literally melted inside the box on the side of the box from the pole. 

Contributor

 • 

28 Messages

3 years ago

Contributor

 • 

28 Messages

3 years ago

https://imgur.com/WlsxVId

 

https://imgur.com/J7imhVD

 

as you can see by the linked screenshots it shows im still on the 200mbps plan and not the 600mbps plan. i have a tech coming tomorrow to look at lines so i hope it gets fixed.

Contributor

 • 

28 Messages

3 years ago

a tech is coming out today to hopefully fix the issue.

Expert

 • 

103.5K Messages

3 years ago

The downstream power is still high. Not certain that is the root cause of the problem but you can try inserting a minus 6dB attenuator pad into the coax line at the back of the modem to balance out those power levels and see;

 

https://www.amazon.com/6db-Attenuator-Pad-1-each/dp/B0013L48XA

 

Good luck !

 

 

Expert

 • 

103.5K Messages

3 years ago

Please post back with how things turn out.

Contributor

 • 

28 Messages

3 years ago

tech came out and he said everything looked fine on his end. speed tested via ethernet and got 500mbps which is close to the speeds im paying for, but on my wifi i only get 200mbps. they immediately blamed my gateway after doing a line test and signal test and said everything looks good. i have another company moving in called metronet, i think when i can im just going to switch as im tired of having techs come out and tell me everything is good and blaming my equipment. the gateway is less than a year old. i bought it last year at tax time. he reactivated modem and made sure correct speed provisioning and boot file were loaded as well. he got 700mbps via his tester hooked to ethernet port.

Contributor

 • 

28 Messages

3 years ago

 
 
Apply               Cancel     
Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency
 
Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel405000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnabledBPI+
IP Provisioning ModeHonor MDDhonorMdd(4)
 
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM25642405000000 Hz8.2 dBmV38.7 dB00
2LockedQAM25643411000000 Hz8 dBmV38.1 dB00
3LockedQAM25644417000000 Hz8.3 dBmV38.6 dB00
4LockedQAM25645423000000 Hz8.3 dBmV38.7 dB00
5LockedQAM25638429000000 Hz8.4 dBmV38.8 dB00
6LockedQAM25639435000000 Hz8.5 dBmV38.7 dB00
7LockedQAM25640441000000 Hz8.4 dBmV38.5 dB00
8LockedQAM25641453000000 Hz9 dBmV39.2 dB00
9LockedQAM25625459000000 Hz8.9 dBmV39 dB00
10LockedQAM25630465000000 Hz8.9 dBmV38.8 dB00
11LockedQAM25631471000000 Hz9.2 dBmV39 dB00
12LockedQAM25632477000000 Hz9.4 dBmV39.4 dB00
13LockedQAM2561483000000 Hz9.1 dBmV39.3 dB00
14LockedQAM2562489000000 Hz9.5 dBmV39.5 dB00
15LockedQAM2563495000000 Hz9.3 dBmV39.3 dB00
16LockedQAM2564501000000 Hz9.1 dBmV39.2 dB00
17LockedQAM2565507000000 Hz8.4 dBmV38.6 dB00
18LockedQAM2566513000000 Hz8.4 dBmV38.6 dB00
19LockedQAM2567519000000 Hz8.5 dBmV39 dB00
20LockedQAM2568525000000 Hz8.4 dBmV38.6 dB00
21LockedQAM2569531000000 Hz8.8 dBmV39 dB00
22LockedQAM25610537000000 Hz8.6 dBmV39 dB00
23LockedQAM25611543000000 Hz9.2 dBmV39.4 dB00
24LockedQAM25612549000000 Hz9.1 dBmV39.4 dB00
 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA91280 Ksym/sec39600000 Hz45.3 dBmV
2LockedATDMA15120 Ksym/sec35600000 Hz43.8 dBmV
3LockedATDMA25120 Ksym/sec29200000 Hz42.8 dBmV
4LockedATDMA35120 Ksym/sec22800000 Hz42 dBmV
5LockedATDMA45120 Ksym/sec16400000 Hz41.3 dBmV
6Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
7Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
8Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
 
Extended Upstream Transmit Power
Enable Extended Upstream Transmit Power
 
Current System Time:Mon Jan 25 04:41:58 2021
System Up Time:00:12:59

 

i even just factory reset my gateway. 
 
event log:
TimePriorityDescription
2021-1-25, 04:32:23Notice (6)WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE
1970-1-1, 00:00:49Notice (6)Honoring MDD; IP provisioning mode = IPv6
1970-1-1, 00:00:44Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:01:5c:7e:d2:5b;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:41Notice (6)WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:41Notice (6)WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:38Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2021-1-25, 04:27:10Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:01:5c:7e:d2:5b;CM-QOS=1.0;CM-VER=3.0;
2021-1-25, 04:27:04Critical (3)No UCDs Received - Timeout;;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2021-1-25, 04:26:47Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2021-1-25, 04:26:45Critical (3)No UCDs Received - Timeout;;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:02:07Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:01:5c:7e:d2:5b;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:02:00Critical (3)No UCDs Received - Timeout;;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:43Critical (3)No UCDs Received - Timeout;;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:26Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:14Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:13Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:02Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:01:01Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:53Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:52Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:41Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:39Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=38:94:ed:d9:94:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
forum icon

New to the Community?

Start Here