Visitor
•
5 Messages
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; |
CCXavier
Official Employee
•
695 Messages
3 years ago
Hello, thank you for reaching out to us. What troubleshooting steps have you taken?
5
0
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)
0
0
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…
0
0
EG
Expert
•
111.5K Messages
3 years ago
FWIW. Their cable modem's downstream power level values are far out of spec.
0
EG
Expert
•
111.5K Messages
3 years ago
@user_8fdac6
Did any of those tips apply ?
0
0
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
0
0