cancel
Showing results for 
Search instead for 
Did you mean: 

Qam wrong?

Viper-t
Fibre optic

Hi can someone tell me if my qam is wrong please?. My upload qam is always 64 as is everyone's I have 1 channel 32qam and 2 at 16qam I think 64 symbols is more data than 16 no? 

Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

14310000041.35120 KSym/sec32QAM2
23010000040.85120 KSym/sec16QAM4
336600000415120 KSym/sec16QAM3
44960000041.55120 KSym/sec64QAM1
523600000405120 KSym/sec64QAM5
353 REPLIES 353

I know we are still going through security questions for the last few weeks but this is my mums current connection which has been terrible for months and months, picture still freezing, if anyone at VIRGIN cares less here are some more stats, post rs errors and net log still terrible as no one has fixed anything 2 engineers been neither has been aloud to do anything, confirmed snr problem from networks will virgin act?

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13310000007.341QAM 25625
2139000000440QAM 2561
31470000004.240QAM 2562
41550000004.240QAM 2563
51630000004.440QAM 2564
61710000004.741QAM 2565
71790000004.941QAM 2566
8187000000541QAM 2567
91950000005.441QAM 2568
102030000005.541QAM 2569
112110000005.941QAM 25610
122190000005.941QAM 25611
132270000006.141QAM 25612
142350000006.241QAM 25613
152430000006.241QAM 25614
162510000006.141QAM 25615
172590000006.141QAM 25616
182670000006.241QAM 25617
192750000006.441QAM 25618
202830000006.741QAM 25619
212910000006.941QAM 25620
222990000006.941QAM 25621
23307000000741QAM 25622
243150000007.241QAM 25623
253230000007.341QAM 25624
263390000007.441QAM 25626
273470000007.541QAM 25627
283550000007.541QAM 25628
293630000007.641QAM 25629
303710000007.541QAM 25630
313790000007.541QAM 25631

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked4100
2Locked40110335
3Locked4000
4Locked40158249
5Locked40206152
6Locked41146171
7Locked41167197
8Locked41199120
9Locked4118782
10Locked4120090
11Locked4195110
12Locked41150123
13Locked4110060
14Locked418219
15Locked413714
16Locked412213
17Locked41240
18Locked41200
19Locked41192
20Locked41120
21Locked4150
22Locked4140
23Locked4110
24Locked4100
25Locked4100
26Locked4100
27Locked4110
28Locked4100
29Locked4100
30Locked4120
31Locked4100
 
04-10-2023 09:20:35noticeREGISTRATION COMPLETE - Waiting for Operational status
04-10-2023 09:20:31noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-10-2023 09:20:25noticeDS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-10-2023 09:20:13warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-10-2023 09:20:11noticeHonoring MDD; IP provisioning mode = IPv4
04-10-2023 09:20:01criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-10-2023 09:19:49criticalCable Modem Reboot via RG reboot command
03-10-2023 15:23:35criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-10-2023 15:23:25criticalCable Modem Reboot via RG reboot command
03-10-2023 10:25:22criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-10-2023 10:25:10criticalCable Modem Reboot via RG reboot command
02-10-2023 10:11:10criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-10-2023 10:10:58criticalCable Modem Reboot via RG reboot command
01-10-2023 10:13:27criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-10-2023 10:13:16criticalCable Modem Reboot via RG reboot command
30-09-2023 10:28:53criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30-09-2023 10:28:42criticalCable Modem Reboot via RG reboot command
29-09-2023 10:39:58criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-09-2023 10:39:46criticalCable Modem Reboot via RG reboot command
28-09-2023 09:06:32criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-09-2023 09:06:20criticalCable Modem Reboot via RG reboot command
27-09-2023 10:08:14criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-09-2023 10:08:02criticalCable Modem Reboot via RG reboot command
26-09-2023 10:08:05criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-09-2023 10:07:54criticalCable Modem Reboot via RG reboot command
25-09-2023 09:40:44criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2023 09:40:32criticalCable Modem Reboot via RG reboot command
24-09-2023 17:27:50criticalNo Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-09-2023 17:27:40criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-09-2023 17:27:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-09-2023 14:33:18critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-09-2023 14:33:18criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
 
513ae56f12c1b5fb03e9accb2605064206300b94-01-10-2023.png

Right so after about a month of no dropped modulations the last few days have been terrible. Started with channel 4 on the upstream dropping to 32QAM like it always used too, the last night when my girlfriend was on the playstation all the upstream dropped to 16QAM and had as high as 25% packet loss on the return path. This shows too on the bqm monitor and netlog and stats. Why is this starting again? I've noticed lately multiple profile changes in a day now obvious upload problems, profile 11 borderline? This is always on the OFDMA 3.1 which must be the problem as it always errors on channel 8 which I simply do not have, so 6 is the highest I presume its the source. Is it just bouncing me between 2 equally congested profile channels?. Just noticed on one of my photos from last night 4 t3 logged quickily on netlog table with all docsis 3.0 dropping to 16qam and even the OFDMA channel dropping to 32QAM evidence as always below. When I read other providers similar problems there techs pull lines actually try to fix the problem externally as senior engineer excluded my home for noise months ago, am I ever getting this resolved? To much traffic? Or to much noise ingress or both? Solutions from vm or some correspondence would be nice? is any work going on like what's happening? This is nearly a year at this point. Do you want me to sue you in small claims do anyone care at all, just tell me and I will happily take you to court with all the biblical amount of evidence for my whole area.

20231006_222006.jpg20231006_221946.jpg20231006_221932.jpg20231006_221926.jpg20231006_221914.jpgcd5435b71483a0e022979b011be3c7fa7bc2d930-07-10-2023.pngcd5435b71483a0e022979b011be3c7fa7bc2d930-06-10-2023.pngcd5435b71483a0e022979b011be3c7fa7bc2d930-03-10-2023.pngScreenshot_20231007_170749_Chrome.jpgScreenshot_20231006_230030_Chrome.jpgScreenshot_20231006_230023_Chrome.jpgScreenshot_20231006_230008_Chrome.jpg

A lot of correcteds too on the active profile whichever one it is.

 

Time Priority Description
Sat Oct
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct
6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct
6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct
4DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Oct
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Oct
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Oct
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Oct
6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct
6SW download Successful - Via Config file
Sun Oct
6SW Download INIT - Via Config file cmreg-vmdg640-bbt076+voc-b.cm
Sun Oct
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
13010000043.0205995120 KSym/sec64QAM4
24310000043.7705995120 KSym/sec64QAM2
34960000043.7705995120 KSym/sec64QAM1
42360000042.5205995120 KSym/sec32QAM5
53660000043.2705995120 KSym/sec64QAM3



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1US_TYPE_ATDMA0000
2US_TYPE_ATDMA0000
3US_TYPE_ATDMA0000
4US_TYPE_ATDMA0000
5US_TYPE_ATDMA0000



3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
610.840.52KQAM128


3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
6OFDMA22053.440
 

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

253310000003.79999940.366287QAM25625
11390000005.19999740.366287QAM2561
21470000005.19999740.366287QAM2562
31550000005.30000340.946209QAM2563
41630000005.09999840.366287QAM2564
51710000004.80000340.366287QAM2565
61790000004.50000040.946209QAM2566
71870000004.80000340.366287QAM2567
81950000004.80000340.366287QAM2568
92030000004.69999740.366287QAM2569
102110000004.69999740.366287QAM25610
112190000004.90000240.366287QAM25611
122270000004.90000240.366287QAM25612
132350000004.80000340.366287QAM25613
142430000004.80000340.946209QAM25614
152510000004.69999740.366287QAM25615
162590000004.90000240.946209QAM25616
172670000004.90000240.366287QAM25617
182750000004.59999840.366287QAM25618
192830000004.40000240.366287QAM25619
202910000004.40000240.946209QAM25620
212990000005.00000040.366287QAM25621
223070000004.50000040.946209QAM25622
233150000003.90000240.946209QAM25623
243230000003.59999840.366287QAM25624
263390000003.59999840.366287QAM25626
273470000003.40000240.366287QAM25627
283550000003.59999840.366287QAM25628
293630000003.40000240.366287QAM25629
303710000003.20000140.366287QAM25630
313790000003.40000240.366287QAM25631



3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

25Locked40.36628700
1Locked40.36628700
2Locked40.36628700
3Locked40.94620900
4Locked40.36628700
5Locked40.36628700
6Locked40.94620900
7Locked40.36628700
8Locked40.36628700
9Locked40.36628700
10Locked40.36628700
11Locked40.36628700
12Locked40.36628700
13Locked40.36628700
14Locked40.94620900
15Locked40.36628700
16Locked40.94620900
17Locked40.36628700
18Locked40.36628700
19Locked40.36628700
20Locked40.94620900
21Locked40.36628700
22Locked40.94620900
23Locked40.94620900
24Locked40.36628700
26Locked40.36628700
27Locked40.36628700
28Locked40.36628700
29Locked40.36628700
30Locked40.36628700
31Locked40.36628700



3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33964K1840QAM4096759


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
33Locked40-3.318723348910

My parents terrible stats today will vm do anything about this do you see a problem with sync failure everyday and reboots?

Time Priority Description
08-10-2023 14:41:12noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-10-2023 14:36:09noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-10-2023 09:45:38noticeREGISTRATION COMPLETE - Waiting for Operational status
08-10-2023 09:45:34noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-10-2023 09:45:29noticeDS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-10-2023 09:45:17warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-10-2023 09:45:14noticeHonoring MDD; IP provisioning mode = IPv4
08-10-2023 09:45:02criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-10-2023 09:44:51criticalCable Modem Reboot via RG reboot command
07-10-2023 09:54:31criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-10-2023 09:54:20criticalCable Modem Reboot via RG reboot command
06-10-2023 10:09:47criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-10-2023 10:09:37criticalCable Modem Reboot via RG reboot command
05-10-2023 09:56:45criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-10-2023 09:56:34criticalCable Modem Reboot via RG reboot command
04-10-2023 09:20:01criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-10-2023 09:19:49criticalCable Modem Reboot via RG reboot command
03-10-2023 15:23:35criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-10-2023 15:23:25criticalCable Modem Reboot via RG reboot command
03-10-2023 10:25:22criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-10-2023 10:25:10criticalCable Modem Reboot via RG reboot command
02-10-2023 10:11:10criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-10-2023 10:10:58criticalCable Modem Reboot via RG reboot command
01-10-2023 10:13:27criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-10-2023 10:13:16criticalCable Modem Reboot via RG reboot command
30-09-2023 10:28:53criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30-09-2023 10:28:42criticalCable Modem Reboot via RG reboot command
29-09-2023 10:39:58criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
29-09-2023 10:39:46criticalCable Modem Reboot via RG reboot command
28-09-2023 09:06:32criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-09-2023 09:06:20criticalCable Modem Reboot via RG reboot command
27-09-2023 10:08:14criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Hi so after connection being good at my home for some weeks, on the 31st of October no less like some horrible joke. My bqm shows lots of packet loss all day. At nearly 1am on the 1st of November my bqm shows no data till nearly 7pm even though Internet was running and ip address says its the same?. Now theres small packet loss but the main problem Is back upstream qams dropping Modulation on multiple channels ever since, now mdd errors oh and t4 and t3 the usual bad stats when you change me to terrible connection. Can someone explain why do overseas vm keep changing my connection from ok connection to terrible? Just leave it alone. Billions of correcteds on the packets. Also missing Channel 1 on my downstream whats that about?.

cd5435b71483a0e022979b011be3c7fa7bc2d930-31-10-2023.pngcd5435b71483a0e022979b011be3c7fa7bc2d930-01-11-2023 (1).png

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

13660000043.5205995120 KSym/sec64QAM3
22360000042.5205995120 KSym/sec32QAM5
33010000043.0205995120 KSym/sec64QAM4
44310000043.7705995120 KSym/sec32QAM2
54960000044.0205995120 KSym/sec32QAM1



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_ATDMA0000
2US_TYPE_ATDMA0000
3US_TYPE_ATDMA0000
4US_TYPE_ATDMA0000
5US_TYPE_ATDMA0000



3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
610.840.52KQAM128


3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
6OFDMA22053.400

 

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

26Locked40.36628700
2Locked40.94620900
3Locked40.36628700
4Locked40.36628700
5Locked40.36628700
6Locked40.36628700
7Locked40.36628700
8Locked40.94620900
9Locked40.94620900
10Locked40.36628700
11Locked40.36628700
12Locked40.94620900
13Locked40.94620900
14Locked40.36628700
15Locked40.36628700
16Locked40.36628700
17Locked40.36628700
18Locked40.36628700
19Locked40.94620900
20Locked40.36628700
21Locked40.36628700
22Locked40.36628700
23Locked40.36628700
24Locked40.36628700
25Locked40.36628700
27Locked40.36628700
28Locked40.36628700
29Locked40.94620900
30Locked40.36628700
31Locked40.94620900
32Locked40.36628700



3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33964K1840QAM4096759


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
33Locked40-2.213282698390

Network Log

Network Log

Time Priority Description

Fri Nov
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Nov
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Nov
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Nov
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Nov
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Nov
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Nov
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Nov
4Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Nov
3Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Nov
5Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Nov
6CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Nov
3SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Oct
30
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Oct
30
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct
29
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct
29
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct
28
4DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct
27
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct
25
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct
25
4DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct
21
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
5ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct
20
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct
20
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct
20
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Oct
19
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Oct
19
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct
15
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct
15
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct
14
4DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct
13
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct
13
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct
13
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct
11
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct
11
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Oct
11
6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Oct
10
4DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Oct
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

263390000003.90000240.366287QAM25626
21470000005.30000340.946209QAM2562
31550000005.50000040.366287QAM2563
41630000005.19999740.366287QAM2564
51710000004.90000240.366287QAM2565
61790000004.69999740.366287QAM2566
71870000005.00000040.366287QAM2567
81950000005.00000040.946209QAM2568
92030000005.00000040.946209QAM2569
102110000005.00000040.366287QAM25610
112190000005.19999740.366287QAM25611
122270000005.09999840.946209QAM25612
132350000005.09999840.946209QAM25613
142430000005.09999840.366287QAM25614
152510000005.00000040.366287QAM25615
162590000005.09999840.366287QAM25616
172670000005.19999740.366287QAM25617
182750000004.80000340.366287QAM25618
192830000004.59999840.946209QAM25619
202910000004.69999740.366287QAM25620
212990000005.30000340.366287QAM25621
223070000004.80000340.366287QAM25622
233150000004.30000340.366287QAM25623
243230000003.90000240.366287QAM25624
253310000004.19999740.366287QAM25625
273470000003.70000140.366287QAM25627
283550000003.90000240.366287QAM25628
293630000003.79999940.946209QAM25629
303710000003.50000040.366287QAM25630
313790000003.59999840.946209QAM25631
323870000003.50000040.366287QAM25632

Sephiroth
Alessandro Volta

I can't say anything about the upstream degradation, and the Forum Team won't tell you anything worthwhile either.  But on your D Channel 1 point, you so have 31x Docsis 3.0 channels.  Someone else will be getting Channel 1 or it's duff and nobody's getting it.  There's a whole pool of channels in the frequency spectrum that can be assigned to the DS.

It's best to log into the GUI so we can see the times for the events recorded in the network log.  But there's no doubt that the upstream has reverted to its bad ways based on the QAM values.

As to the BQM, if you have a red block like that and your internet is working, then it could be at the TBB end.  Maybe your mother had the same?

Seph - ( DEFROCKED - My advice is at your risk)