TV and Internet Problems

My TV hooked up to the cable box will pixel and the internet will drop. I have 2 TVs connected with WIFI boxes and they drop numerous times a day. Comcast says everything is good on their end but I don't believe that to be true. I have a MG8702 modem/router and the power and log say otherwise. Comcast told me to call Motorola for an update but reading online this only comes for the ISP. Is it time to drop Comcast?

Channel	Lock Status	Modulation	Channel ID	Freq. (MHz)	Pwr (dBmV)	SNR (dB)	Corrected	Uncorrected
1	Locked	QAM256	20	543.0	-15.9	37.7	0	0
2	Locked	QAM256	13	501.0	-16.3	37.6	0	0
3	Locked	QAM256	14	507.0	-16.0	37.8	0	0
4	Locked	QAM256	15	513.0	-16.8	37.1	0	0
5	Locked	QAM256	16	519.0	-16.6	37.2	0	0
6	Locked	QAM256	17	525.0	-16.7	37.2	0	0
7	Locked	QAM256	18	531.0	-15.9	37.8	0	0
8	Locked	QAM256	19	537.0	-16.1	37.7	0	0
9	Locked	QAM256	21	549.0	-16.3	37.3	0	0
10	Locked	QAM256	22	555.0	-16.5	37.1	0	0
11	Locked	QAM256	23	561.0	-16.3	37.3	0	0
12	Locked	QAM256	24	567.0	-16.4	37.0	0	0
13	Locked	QAM256	25	573.0	-16.3	37.0	0	0
14	Locked	QAM256	26	579.0	-16.8	36.5	0	0
15	Locked	QAM256	27	585.0	-16.9	36.5	0	0
16	Locked	QAM256	28	591.0	-16.7	36.6	0	0
17	Locked	QAM256	29	597.0	-16.4	36.9	0	0
18	Locked	QAM256	30	603.0	-16.4	36.9	0	0
19	Locked	QAM256	31	609.0	-16.5	36.8	0	0
20	Locked	QAM256	32	615.0	-16.6	36.6	0	0
21	Locked	QAM256	33	621.0	-16.4	36.8	0	0
22	Locked	QAM256	34	627.0	-16.6	36.5	0	0
23	Locked	QAM256	35	633.0	-16.1	37.1	0	0
24	Locked	QAM256	36	639.0	-16.0	37.1	0	0
25	Locked	QAM256	37	645.0	-16.3	36.8	0	0
26	Locked	QAM256	38	651.0	-16.5	36.6	0	0
27	Locked	QAM256	39	657.0	-16.8	36.3	0	0
28	Locked	QAM256	40	663.0	-16.5	36.5	0	0
29	Locked	QAM256	41	669.0	-16.7	36.4	0	0
30	Locked	QAM256	42	675.0	-16.4	36.2	0	0
31	Locked	QAM256	43	681.0	-16.6	36.3	0	0
32	Locked	QAM256	44	687.0	-17.2	35.7	0	0
33	Locked	OFDM PLC	193	957.0	-17.3	34.6	3501410	149991

09:46:53 Tue Sep 13 2022		Critical (3)		Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	09:47:50 Tue Sep 13 2022		Critical (3)		Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	09:48:02 Tue Sep 13 2022		Critical (3)		UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	09:48:22 Tue Sep 13 2022		Critical (3)		UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	09:57:16 Tue Sep 13 2022		Critical (3)		Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	09:58:26 Tue Sep 13 2022		Critical (3)		Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	10:08:41 Tue Sep 13 2022		Critical (3)		Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	10:15:02 Tue Sep 13 2022		Critical (3)		Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	Time Not Established		Critical (3)		SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
	Time Not Established		Critical (3)		UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	14:28:08 Tue Sep 13 2022		Critical (3)		UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	Time Not Established		Critical (3)		SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
	Time Not Established		Critical (3)		UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	Time Not Established		Notice (6)		Honoring MDD; IP provisioning mode = IPv6
	15:06:36 Tue Sep 13 2022		Notice (6)		DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:06:41 Tue Sep 13 2022		Critical (3)		UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:06:49 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:11:24 Tue Sep 13 2022		Warning (5)		MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:11:38 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 4; Chan ID: 28 33 34 36 38 40 41 42 43 44; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:18:50 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:23:35 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:24:11 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:51:37 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:51:43 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:52:49 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:54:00 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:55:54 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:56:11 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:57:21 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	15:57:49 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	16:00:34 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
	16:01:42 Tue Sep 13 2022		Notice (6)		CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;

This conversation is no longer open for comments or replies and is no longer visible to community members.

Responses

CCXavier

Official Employee

•

695 Messages

3 years ago

Hello, thank you for reaching out to us. What troubleshooting steps have you taken?

user_8fdac6

Visitor

•

5 Messages

@XfinityXavier I have checked the connections in the wall and attic for corrosion and tightness. I spoke with Motorola and they determined the event logs and connection parameters provided are not within specifications.

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Freq. (MHz)	Pwr (dBmV)	SNR (dB)	Corrected	Uncorrected
1	Locked	QAM256	12	495.0	-16.3	37.5	67317	23098
2	Locked	QAM256	1	429.0	-16.2	38.0	83782	27817
3	Locked	QAM256	2	435.0	-16.1	37.9	80938	28349
4	Locked	QAM256	3	441.0	-15.5	38.5	71348	26854
5	Locked	QAM256	4	447.0	-15.5	38.5	70651	26449
6	Locked	QAM256	5	453.0	-15.6	38.5	78126	26584
7	Locked	QAM256	6	459.0	-16.0	38.2	67569	22954
8	Locked	QAM256	7	465.0	-15.9	38.2	65295	21503
9	Locked	QAM256	8	471.0	-16.0	38.1	58513	20814
10	Locked	QAM256	9	477.0	-16.4	37.6	65319	21413
11	Locked	QAM256	10	483.0	-16.4	37.7	58572	20384
12	Locked	QAM256	11	489.0	-16.5	37.4	56936	19830
13	Locked	QAM256	13	501.0	-16.3	37.6	56486	19747
14	Locked	QAM256	14	507.0	-16.0	38.0	49692	18889
15	Locked	QAM256	15	513.0	-16.6	37.3	54614	18815
16	Locked	QAM256	16	519.0	-16.5	37.4	50439	22140
17	Locked	QAM256	17	525.0	-16.6	37.4	47921	18054
18	Locked	QAM256	18	531.0	-15.8	37.9	39121	16890
19	Locked	QAM256	19	537.0	-15.9	37.9	38264	17172
20	Locked	QAM256	20	543.0	-15.9	37.9	36022	16968
21	Locked	QAM256	21	549.0	-16.2	37.4	38193	17168
22	Locked	QAM256	22	555.0	-16.4	37.2	38156	21191
23	Locked	QAM256	23	561.0	-16.1	37.4	32056	16850
24	Locked	QAM256	24	567.0	-16.3	37.1	32896	18199
25	Locked	QAM256	25	573.0	-16.2	37.2	31524	17790
26	Locked	QAM256	26	579.0	-16.6	36.8	31781	19733
27	Locked	QAM256	27	585.0	-16.8	36.5	32022	21256
28	Locked	QAM256	28	591.0	-16.6	36.6	29747	20717
29	Locked	QAM256	29	597.0	-16.3	37.1	27395	20063
30	Locked	QAM256	30	603.0	-16.3	37.1	26146	19804
31	Locked	QAM256	31	609.0	-16.4	36.9	25822	19947
32	Locked	QAM256	32	615.0	-16.4	36.8	24473	20363
33	Locked	OFDM PLC	193	957.0	-16.5	35.3	170926235	31773569

Upstream Bonded Channels

Channel	Lock Status	Channel Type	Channel ID	Symb. Rate (Ksym/sec)	Freq. (MHz)	Pwr (dBmV)
1	Locked	SC-QAM	1	5120	35.6	45.8
2	Locked	SC-QAM	2	5120	29.2	45.3
3	Locked	SC-QAM	3	5120	22.8	43.0
4	Locked	SC-QAM	4	5120	16.4	43.8

Log

Time

Priority

Description

06:15:26
Sat Sep 17 2022

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;;CM-QOS=1.1;CM-VER=3.1;

06:15:43
Sat Sep 17 2022

Notice (6)

CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;;CM-QOS=1.1;CM-VER=3.1;

06:15:45
Sat Sep 17 2022

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;;CM-QOS=1.1;CM-VER=3.1;

06:15:47
Sat Sep 17 2022

Critical (3)

No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;

06:15:47
Sat Sep 17 2022

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;-QOS=1.1;CM-VER=3.1;

06:15:48
Sat Sep 17 2022

Notice (6)

CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;;CM-QOS=1.1;CM-VER=3.1;

06:15:53
Sat Sep 17 2022

Critical (3)

No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;

06:15:54
Sat Sep 17 2022

Notice (6)

CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;;CM-QOS=1.1;CM-VER=3.1;

06:15:56
Sat Sep 17 2022

Critical (3)

No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;

06:15:56
Sat Sep 17 2022

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;;CM-QOS=1.1;CM-VER=3.1;

06:16:06
Sat Sep 17 2022

Critical (3)

UCD invalid or channel unusable;;CM-QOS=1.1;CM-VER=3.1;

06:16:08
Sat Sep 17 2022

Critical (3)

No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;

06:16:11
Sat Sep 17 2022

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;

06:16:24
Sat Sep 17 2022

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

06:16:34
Sat Sep 17 2022

Notice (6)

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;

06:16:47
Sat Sep 17 2022

Critical (3)

UCD invalid or channel unusable;;CM-QOS=1.1;CM-VER=3.1;

06:16:55
Sat Sep 17 2022

Notice (6)

CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;;CM-QOS=1.1;CM-VER=3.1;

06:40:46
Sat Sep 17 2022

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;

06:40:50
Sat Sep 17 2022

Critical (3)

UCD invalid or channel unusable;;CM-QOS=1.1;CM-VER=3.1;

06:40:51
Sat Sep 17 2022

Error (4)

DBC-ACK not received;;CM-QOS=1.1;CM-VER=3.1;

06:41:06
Sat Sep 17 2022

Notice (6)

CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;;CM-QOS=1.1;CM-VER=3.1;

06:41:47
Sat Sep 17 2022

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;;CM-QOS=1.1;CM-VER=3.1;

06:41:54
Sat Sep 17 2022

Critical (3)

UCD invalid or channel unusable;;CM-QOS=1.1;CM-VER=3.1;

06:41:56
Sat Sep 17 2022

Critical (3)

No Ranging Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.1;

06:42:06
Sat Sep 17 2022

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

06:42:15
Sat Sep 17 2022

Notice (6)

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;;CM-QOS=1.1;CM-VER=3.1;

06:42:22
Sat Sep 17 2022

Critical (3)

UCD invalid or channel unusable;;CM-QOS=1.1;CM-VER=3.1;

06:49:34
Sat Sep 17 2022

Notice (6)

CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;

06:50:15
Sat Sep 17 2022

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;C


	07:01:11 Sat Sep 17 2022		Notice (6)

CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;;CM-QOS=1.1;CM-VER=3.1;

07:02:34
Sat Sep 17 2022

Notice (6)

CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;;CM-QOS=1.1;CM-VER=3.1;

07:08:17
Sat Sep 17 2022

Notice (6)

CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;;CM-QOS=1.1;CM-VER=3.1;

(edited)

3 years ago

CCDevinC

Contributor

•

473 Messages

@user_8fdac6 Thanks for that!

To get started, and to locate the account, please send our team a direct message with your full name and full address. Thanks!

To send a "Direct Message" message:

Click "Sign In" if necessary
Click the "Direct Messaging" icon at the top of the page (looks like a text bubble)
Click the "New message" (pencil and paper) icon
Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list which appears. The "Xfinity Support" graphic replaces the "To:" line
Type your message in the text area near the bottom of the window

I no longer work for Comcast.

3 years ago

EG

Expert

•

111.5K Messages

@user_8fdac6

Please redact all of the CM MAC and the CMTS MAC addresses in your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".

I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.

Was your question answered? Please mark an Accepted Answer! tick

3 years ago

user_8fdac6

Visitor

•

5 Messages

I will remove the previous images and add new ones

3 years ago

user_8fdac6

Visitor

•

5 Messages

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Freq. (MHz)	Pwr (dBmV)	SNR (dB)	Corrected	Uncorrected
1	Locked	QAM256	20	543.0	-3.3	42.1	0	0
2	Locked	QAM256	1	429.0	-4.2	41.5	0	0
3	Locked	QAM256	2	435.0	-4.1	41.9	0	0
4	Locked	QAM256	3	441.0	-3.4	41.8	0	0
5	Locked	QAM256	4	447.0	-3.4	42.0	0	0
6	Locked	QAM256	5	453.0	-3.4	42.1	0	0
7	Locked	QAM256	6	459.0	-3.7	42.1	0	0
8	Locked	QAM256	7	465.0	-3.6	42.1	0	0
9	Locked	QAM256	8	471.0	-3.8	41.9	0	0
10	Locked	QAM256	9	477.0	-4.2	41.3	0	0
11	Locked	QAM256	10	483.0	-4.1	41.4	0	0
12	Locked	QAM256	11	489.0	-4.2	41.4	0	0
13	Locked	QAM256	12	495.0	-4.0	40.8	0	0
14	Locked	QAM256	13	501.0	-3.9	42.0	0	0
15	Locked	QAM256	14	507.0	-3.6	41.6	0	0
16	Locked	QAM256	15	513.0	-4.2	41.7	0	0
17	Locked	QAM256	16	519.0	-4.1	41.1	0	0
18	Locked	QAM256	17	525.0	-4.1	41.6	0	0
19	Locked	QAM256	18	531.0	-3.4	42.2	0	0
20	Locked	QAM256	19	537.0	-3.5	41.6	0	0
21	Locked	QAM256	21	549.0	-3.6	42.1	0	0
22	Locked	QAM256	22	555.0	-3.8	42.1	0	0
23	Locked	QAM256	23	561.0	-3.5	42.1	0	0
24	Locked	QAM256	24	567.0	-3.7	42.2	0	0
25	Locked	QAM256	25	573.0	-3.7	42.2	0	0
26	Locked	QAM256	26	579.0	-4.1	42.0	0	0
27	Locked	QAM256	27	585.0	-4.3	42.0	0	0
28	Locked	QAM256	28	591.0	-4.0	42.2	0	0
29	Locked	QAM256	29	597.0	-3.6	42.2	0	0
30	Locked	QAM256	30	603.0	-3.6	42.2	0	0
31	Locked	QAM256	31	609.0	-3.5	42.4	0	0
32	Locked	QAM256	32	615.0	-3.5	41.8	0	0
33	Locked	OFDM PLC	193	957.0	-0.9	42.7	63194	0

This is my modem connected directly to the street. Looks like I am running new house wire. Now what do I use for cable, 1 3 way splitter, connectors?

3 years ago

EG

Expert

•

111.5K Messages

3 years ago

@user_8fdac6 I'll provide some tips / "steps"....;

In an effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1000 MHz, bi-directional, and no gold colored garbage from Radio Shack, Home Depot, Target, etc. Splitters should be swapped with known to be good / new ones to test.

Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.

Good luck with it !

(edited)

Jlavaseur

Problem Solver

•

948 Messages

3 years ago

For what’s it’s worth, I had the pixelation and freezes on my cable box/tv , it turned out to be a bad connection on the hdmi cable, I removed it, reinstalled it, walla! No more problems, I have had those cables go bad for no apparent reason…

EG

Expert

•

111.5K Messages

3 years ago

FWIW. Their cable modem's downstream power level values are far out of spec.

EG

Expert

•

111.5K Messages

3 years ago

@user_8fdac6

Did any of those tips apply ?

user_8fdac6

Visitor

•

5 Messages

3 years ago

I swapped a hdmi cable from the bedroom tv that never pixels, but the living room still pixels occasionally. The 2 patio tv have been pixeling but they are wifi boxes so I didn’t swap cables since I have the wifi issue also

Your Home Network

user_8fdac6

TV and Internet Problems

CCXavier

user_8fdac6

CCDevinC

EG

user_8fdac6

user_8fdac6

EG

Jlavaseur

EG

EG

user_8fdac6

New to the Community?