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

Sephiroth
Alessandro Volta

Upstream is right on the edge, Viper - as I'm sure you know.  It's taking 50+ dBmv power for the CMTS to be able to read at 16QAM.  Right on the edge.  

With regard to the BQM graphs, they may be doing area work at night that they can't be bothered to tell you about.

 

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

No they are not doing any work mate as its been like this since I started the bqm when she first rang about her tv always freezing, infact it's usually worse I've uploaded some. When I got time after the end of the week I'm going to contact which and ofcom as our treatment has been diabolical, and the lack of knowledge from the people involved is unreal. They should hire people like you who don't need the best part of a year to find a simple and obvious problem. I've gave them so many chances and they spit in our faces time and time again, just trying to waste time and hope it magically fixes itself. They need to be held accountable for there terrible treatment of customers.

Regards

Hey @Viper-t,

Thanks for getting back to us, sorry that this is still ongoing for you. 

After checking into our systems I see no issues which would be directly affecting you, with regards to the BQM graph, can you confirm if you have had any texts as of late confirming work being done in your area?

Joe

I'll tell you shall I what's wrong our end as your end is in a book/script. My parents TV freezes all the time so you sent an engineer who rang networks and confirmed on AUDIO TAPE as always, as VIRGIN MEDIA are now all the time LYING TO CUSTOMERS. confirmed area snr problem South bristol since then they have done squat, did not start a ticket and did not catch up with my elderly parents. Then you send another engineer a more useless one who installed a hub 5 even though they are on m125 fair enough, he also confirmed as bristol cables are all in trenches they are to old and fail. I wonder if that might be our problem? The router is not in spec all upstream modulations are maxed out power wise and all qams are 16qam and the netlog is filled with the most serious critical error SYNC Timing Synchronization failure - Loss of Sync which mean it can't talk to the cmts every 20ms so not synchronised so  can lose connection and has to restart/renegotiate again, the amount EVERYDAY. tv continues to freeze lag pixelates. Others of us locally continue to have noise problems, I had another dropout last night but that's why I'm now suing your a€€ and reporting you to which as you just refuse to do anything.

10-09-2023 09:56:28noticeREGISTRATION COMPLETE - Waiting for Operational status
10-09-2023 09:56:24noticeUS 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;
10-09-2023 09:56:19noticeDS 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;
10-09-2023 09:56:06warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-09-2023 09:56:04noticeHonoring MDD; IP provisioning mode = IPv4
10-09-2023 09:55:52criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-09-2023 09:55:41criticalCable Modem Reboot via RG reboot command
09-09-2023 09:53:30criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2023 09:53:19criticalCable Modem Reboot via RG reboot command
08-09-2023 10:01:55criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-09-2023 10:01:43criticalCable Modem Reboot via RG reboot command
07-09-2023 10:26:42criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-09-2023 10:26:31criticalCable Modem Reboot via RG reboot command
06-09-2023 10:08:33criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-09-2023 10:08:21criticalCable Modem Reboot via RG reboot command
03-09-2023 09:56:55criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-09-2023 09:56:44criticalCable Modem Reboot via RG reboot command
02-09-2023 10:44:29criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-09-2023 10:44:18criticalCable Modem Reboot via RG reboot command
01-09-2023 09:24:25criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-09-2023 09:24:13criticalCable Modem Reboot via RG reboot command
31-08-2023 01:38:18criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
31-08-2023 01:38:18critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
31-08-2023 01:37:11criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30-08-2023 23:07:49criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30-08-2023 23:07:38criticalCable Modem Reboot via RG reboot command
30-08-2023 23:05:41criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30-08-2023 15:34:53criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30-08-2023 15:34:41criticalCable Modem Reboot due to SW Upgrade
30-08-2023 15:29:41criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
30-08-2023 15:29:29criticalCable Modem Reboot via RG reboot command
30-08-2023 15:27:17criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
 
 

 

Also why is the t4 (16 consecutive t3 timeouts) error while trying to range upstream channel 8? There isnt a channel 8 only 4 on docsis 3.0. The modem has power and Ranging issues as well as daily dropped connections. My parents need the engineer to set this up correctly as its still not fixed the reason they were there to fix the TV from cutting out and freezing. Which hub 5 will not do. Todays, in the day latency below showing the area problem noise as always.

513ae56f12c1b5fb03e9accb2605064206300b94-10-09-2023.png

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000049.85120QAM 161
14310000049.85120QAM 162
23660000049.85120QAM 163
33010000049.55120QAM 164
42360000049.85120QAM 165

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

Will you fix my parents tv/connection? 

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000049.55120QAM 161
14310000049.35120QAM 162
23660000049.35120QAM 163
33010000049.35120QAM 164
42360000049.35120QAM 165

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0010
4-09-2023 17:25:49criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-09-2023 09:18:19noticeREGISTRATION COMPLETE - Waiting for Operational status
14-09-2023 09:18:16noticeUS 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;
14-09-2023 09:18:11noticeDS 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;
14-09-2023 09:17:59warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-09-2023 09:17:56noticeHonoring MDD; IP provisioning mode = IPv4
14-09-2023 09:17:46criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
14-09-2023 09:17:35criticalCable Modem Reboot via RG reboot command
13-09-2023 09:12:35criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-09-2023 09:12:23criticalCable Modem Reboot via RG reboot command
12-09-2023 10:13:06criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-09-2023 10:12:55criticalCable Modem Reboot via RG reboot command
11-09-2023 09:45:44criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11-09-2023 09:45:33criticalCable Modem Reboot via RG reboot command
10-09-2023 09:55:52criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
10-09-2023 09:55:41criticalCable Modem Reboot via RG reboot command
09-09-2023 09:53:30criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-09-2023 09:53:19criticalCable Modem Reboot via RG reboot command
08-09-2023 10:01:55criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-09-2023 10:01:43criticalCable Modem Reboot via RG reboot command
07-09-2023 10:26:42criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
07-09-2023 10:26:31criticalCable Modem Reboot via RG reboot command
06-09-2023 10:08:33criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
06-09-2023 10:08:21criticalCable Modem Reboot via RG reboot command
03-09-2023 09:56:55criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-09-2023 09:56:44criticalCable Modem Reboot via RG reboot command
02-09-2023 10:44:29criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-09-2023 10:44:18criticalCable Modem Reboot via RG reboot command
01-09-2023 09:24:25criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-09-2023 09:24:13criticalCable Modem Reboot via RG reboot command
31-08-2023 01:38:18critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
31-08-2023 01:38:18criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

All these critical errors are a serious problem, all upstream modulations have dropped and stay at 16 qam as the network is TOO NOISY causing there tv to lose picture pixelate freeze, power is maxed on upstream. Bqm shows terrible latency causing these problems hub 5 is worse than there hub3 why does virgin media make problems worse? Is this retaliation for complaining? As there is so many times across your forum where this is the case, can someone do there job as there to old for this stress or I will add there case to mine and will be a way bigger problem than it needs to be. As this terrible service has gone on to long. Just read your forums or ofcom who ever do not care is making a once great company terrible, what a waste.

513ae56f12c1b5fb03e9accb2605064206300b94-02-09-2023 (1).png513ae56f12c1b5fb03e9accb2605064206300b94-01-09-2023.png513ae56f12c1b5fb03e9accb2605064206300b94-03-09-2023 (2).png513ae56f12c1b5fb03e9accb2605064206300b94-05-09-2023 (1).png513ae56f12c1b5fb03e9accb2605064206300b94-06-09-2023 (1).png513ae56f12c1b5fb03e9accb2605064206300b94-07-09-2023.png513ae56f12c1b5fb03e9accb2605064206300b94-10-09-2023 (1).png513ae56f12c1b5fb03e9accb2605064206300b94-11-09-2023.png513ae56f12c1b5fb03e9accb2605064206300b94-13-09-2023.png513ae56f12c1b5fb03e9accb2605064206300b94-14-09-2023.png

Thanks for your reply, I have checked our system and can see there were some connection drops over the past few days. But they look like they have been resolved now.

How are things looking at your end? If you are still seeing issues, please reboot the Hub. If the issues continue after the reboot, please let us know. We're always happy to assist.

Regards

Nathan

The do's and don'ts. Keep the community welcoming for all. Follow the house rules


Hi Nathan, Done a reset think it updated firmware but the problem persists, netlog filled straight away 2 loss of syncs with cmts, failed to aquire modulation timing, and reboots like the pages before. I've looked in the forums a lot of people with a hub 5 upgrade/downgrade is having problems. My parents problem and other's locally have an area problem I told the engineer a hub 5 will do nothing to fix the noise or hide it. I also mentioned it would probably make it worse, but he was adamant it would improve there tv freezing crashing. Its the same problem as the thread hub 5 dropping docsis connection. There tv froze again last night she tells me around 9pm looking at the bqm chart which I've showed vm is full of latency everyday, upstream has dropped modulations 24 hours a day since the hub 5 was added before it was a few channels dropped now all of them this problem needs an engineer to fix but actually fix this time not make it worse. Upstream power maxed at dropped modulation. I'm shocked at what is happening at vm right now to all long term customers from the 90s unreal.

For transparency the drop at 310pm is from the reboot done as requested by vm.

513ae56f12c1b5fb03e9accb2605064206300b94-17-09-2023 (1).png

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000049.35120QAM 321
143100000495120QAM 322
236600000495120QAM 323
330100000495120QAM 324
423600000495120QAM 325

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
 

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13310000007.241QAM 25625
21390000003.940QAM 2561
31470000004.140QAM 2562
41550000004.140QAM 2563
51630000004.240QAM 2564
61710000004.641QAM 2565
71790000004.841QAM 2566
81870000004.941QAM 2567
91950000005.341QAM 2568
102030000005.441QAM 2569
112110000005.841QAM 25610
122190000005.941QAM 25611
13227000000641QAM 25612
142350000006.241QAM 25613
152430000006.141QAM 25614
16251000000641QAM 25615
17259000000641QAM 25616
182670000006.141QAM 25617
192750000006.341QAM 25618
202830000006.641QAM 25619
212910000006.841QAM 25620
222990000006.841QAM 25621
233070000006.941QAM 25622
243150000007.141QAM 25623
253230000007.241QAM 25624
263390000007.341QAM 25626
273470000007.441QAM 25627
283550000007.441QAM 25628
293630000007.541QAM 25629
303710000007.441QAM 25630
313790000007.440QAM 25631

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked4100
2Locked4000
3Locked4000
4Locked4000
5Locked4000
6Locked4100
7Locked4100
8Locked4100
9Locked4100
10Locked4100
11Locked4100
12Locked4100
13Locked4100
14Locked4100
15Locked4100
16Locked4100
17Locked4100
18Locked4100
19Locked4100
20Locked4100
21Locked4100
22Locked4100
23Locked4100
24Locked4100
25Locked4100
26Locked4100
27Locked4100
28Locked4100
29Locked4100
30Locked4100
31Locked4000
Time Priority Description
17-09-2023 17:16:49noticeREGISTRATION COMPLETE - Waiting for Operational status
17-09-2023 17:16:45noticeUS 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;
17-09-2023 17:16:40noticeDS 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;
17-09-2023 17:16:27warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-09-2023 17:16:25noticeHonoring MDD; IP provisioning mode = IPv4
17-09-2023 17:16:02criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-09-2023 17:15:50criticalCable Modem Reboot via RG reboot command
17-09-2023 17:13:02criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-09-2023 17:12:50criticalCable Modem reset to Factory Default via reset button

 

By the way the netlog time is wrong when logged in properly it's still wrong, obviously can't get real time from cmts?