on 03-03-2022 09:32
Sorry if a duplicate post, but having trouble posting this info.
Similar to others I am having random drop out on both ethernet & wifi.
BQM looks clear. I will post that image as well.
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
10 | 210750000 | 3.200001 | 36.386890 | QAM256 | 10 |
1 | 138750000 | 3.599998 | 36.609653 | QAM256 | 1 |
2 | 146750000 | 3.400002 | 35.779911 | QAM256 | 2 |
3 | 154750000 | 3.400002 | 36.386890 | QAM256 | 3 |
4 | 162750000 | 3.400002 | 36.386890 | QAM256 | 4 |
5 | 170750000 | 3.200001 | 37.355988 | QAM256 | 5 |
6 | 178750000 | 3.200001 | 37.355988 | QAM256 | 6 |
7 | 186750000 | 3.400002 | 37.355988 | QAM256 | 7 |
8 | 194750000 | 3.500000 | 36.386890 | QAM256 | 8 |
9 | 202750000 | 3.500000 | 35.779911 | QAM256 | 9 |
11 | 218750000 | 3.299999 | 37.636276 | QAM256 | 11 |
12 | 226750000 | 3.000000 | 37.355988 | QAM256 | 12 |
13 | 234750000 | 2.900002 | 37.355988 | QAM256 | 13 |
14 | 242750000 | 2.599998 | 37.355988 | QAM256 | 14 |
15 | 250750000 | 2.299999 | 36.609653 | QAM256 | 15 |
16 | 258750000 | 2.500000 | 37.355988 | QAM256 | 16 |
17 | 266750000 | 2.900002 | 37.355988 | QAM256 | 17 |
18 | 274750000 | 3.400002 | 36.386890 | QAM256 | 18 |
19 | 282750000 | 3.599998 | 36.386890 | QAM256 | 19 |
20 | 290750000 | 4.300003 | 37.355988 | QAM256 | 20 |
21 | 298750000 | 5.500000 | 37.355988 | QAM256 | 21 |
22 | 306750000 | 6.400002 | 37.355988 | QAM256 | 22 |
23 | 314750000 | 6.500000 | 37.355988 | QAM256 | 23 |
24 | 322750000 | 6.699997 | 37.355988 | QAM256 | 24 |
25 | 330750000 | 6.400002 | 37.355988 | QAM256 | 25 |
26 | 338750000 | 6.500000 | 38.605377 | QAM256 | 26 |
27 | 346750000 | 6.500000 | 37.636276 | QAM256 | 27 |
28 | 354750000 | 6.199997 | 37.355988 | QAM256 | 28 |
29 | 362750000 | 6.199997 | 36.609653 | QAM256 | 29 |
30 | 370750000 | 5.900002 | 37.355988 | QAM256 | 30 |
31 | 378750000 | 5.800003 | 38.605377 | QAM256 | 31 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
10 | Locked | 36.386890 | 0 | 0 |
1 | Locked | 36.609653 | 6 | 0 |
2 | Locked | 35.779911 | 4 | 0 |
3 | Locked | 36.386890 | 4 | 0 |
4 | Locked | 36.386890 | 0 | 0 |
5 | Locked | 37.355988 | 0 | 0 |
6 | Locked | 37.355988 | 0 | 0 |
7 | Locked | 37.355988 | 0 | 0 |
8 | Locked | 36.386890 | 0 | 0 |
9 | Locked | 35.779911 | 0 | 0 |
11 | Locked | 37.636276 | 0 | 0 |
12 | Locked | 37.355988 | 0 | 0 |
13 | Locked | 37.355988 | 0 | 0 |
14 | Locked | 37.355988 | 0 | 0 |
15 | Locked | 36.609653 | 0 | 0 |
16 | Locked | 37.355988 | 0 | 0 |
17 | Locked | 37.355988 | 0 | 0 |
18 | Locked | 36.386890 | 0 | 0 |
19 | Locked | 36.386890 | 0 | 0 |
20 | Locked | 37.355988 | 0 | 0 |
21 | Locked | 37.355988 | 0 | 0 |
22 | Locked | 37.355988 | 0 | 0 |
23 | Locked | 37.355988 | 0 | 0 |
24 | Locked | 37.355988 | 0 | 0 |
25 | Locked | 37.355988 | 0 | 0 |
26 | Locked | 38.605377 | 0 | 0 |
27 | Locked | 37.636276 | 0 | 0 |
28 | Locked | 37.355988 | 0 | 0 |
29 | Locked | 36.609653 | 0 | 0 |
30 | Locked | 37.355988 | 0 | 0 |
31 | Locked | 38.605377 | 0 | 0 |
33 | 94 | 4K | 1840 | QAM4096 | 424 |
33 | Locked | 41 | 0.9 | 601898773 | 7466 |
on 03-03-2022 09:32
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 32600000 | 43.020599 | 5120 KSym/sec | 64QAM | 3 |
2 | 25800000 | 41.770599 | 5120 KSym/sec | 64QAM | 4 |
3 | 46200000 | 44.770599 | 5120 KSym/sec | 64QAM | 1 |
4 | 39400000 | 44.020599 | 5120 KSym/sec | 64QAM | 2 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | US_TYPE_STDMA | 0 | 0 | 1 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
on 03-03-2022 09:33
Time Priority Description
Wed Jan 26 16:45:33 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 1 00:01:24 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 28 21:21:23 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 28 21:21:33 2022 | 5 | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Jan 28 21:21:55 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 1 00:01:22 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Jan 30 00:24:10 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Jan 30 02:07:33 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Jan 30 13:59:08 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Jan 30 15:29:20 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Jan 31 00:26:34 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Feb 1 14:29:58 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Feb 1 14:58:40 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Feb 4 09:33:40 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Feb 4 10:35:01 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Feb 5 00:25:25 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Feb 5 06:11:06 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 05:20:41 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Feb 8 12:25:26 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Feb 11 10:12:53 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Feb 11 18:37:06 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Feb 11 21:01:50 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Feb 11 23:19:25 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Feb 12 00:25:26 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Feb 12 01:47:55 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Feb 15 12:25:26 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Feb 15 12:34:58 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Feb 19 01:47:33 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Feb 19 08:29:46 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 20 17:12:43 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 20 20:54:33 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Feb 22 13:36:28 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Feb 22 17:53:49 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Feb 24 10:28:01 2022 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Feb 24 10:28:06 2022 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Feb 24 10:29:20 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Feb 24 10:29:31 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Feb 25 07:34:24 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Feb 25 07:49:13 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Feb 25 21:39:27 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 03-03-2022 09:34
https://www.thinkbroadband.com/broadband/monitoring/quality/share/ac41fed14f7ca0bc2814529e35adeed9be79567b-03-03-2022
on 06-03-2022 10:50
Hi @jallaphanti
Welcome back to our community forums and sorry to hear you have been having dropouts on your service.
I can understand the frustration caused and want to best help.
I had a look into your account and everything seems to be in working order. In this case, are you able to give an update on if the issues are ongoing since the last posting?
Thanks,