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
351 REPLIES 351

Sephiroth
Alessandro Volta

The SYNC etc failures at boot time are normal.  At that time, nothing is in sync and the modem can't make sense of the stream of data that is nevertheless hitting it.

 

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

Hmmm it's the all day everyday part that's concerning septh, with the high latency. I find it amazing that no one at vm finds permanently dropped modulations on all 5 channels concerning.... everyday. Not its struggling at certain times of day and drops down a mod but all 5 are dropped all day everyday impacting a variety of things obviously. Everything together netlog bqm and dropped mods speak volumes of there capacity to give a damn about any customers anymore. I'm disgusted at the way there treating us in South bristol and on vm as a whole reading people's bad experiences makes me sick the way they are fobbed off with obvious lies depending on there knowledge and who they speak too, I wish I had the knowledge you do I would be so transparent to them to try to help these poor people, especially in today's climate.

Best regards 

Tom 👍 

Thank you for keeping us updated Viper-t. I would like to investigate this further with yourself. 

I will private message you now to confirm your details. 

^Martin

For heaven’s sake. There’s nothing for you to do other than diligently find out when the area remediation will take place to remove upstream nouse. It’s a big job but poor old Tom is told nothing. 

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

Hi I see I had a sw update by nms on Monday, which others did not receive now I have a new error CMSTATUS:US_Diplexer_Mode_Change: (TLV-9) I've researched what this is but can you tell me why I have this new error please?.

Regards

Sephiroth
Alessandro Volta

What did your research reveal?  Your upstream stats might be useful to see.  I'd be looking for higher frequencies, although they may not have been allocated to your segment.  This message suggests to me that they are working on your area to improve the upstream by adding more channels (up to 85MHz) and so relieving  contention and improving speed.  If the upstream is not in a state of grace when rebooting (as in they're in the process of adding channels), then, according to my understanding, the modem reacts with this error.   It should go away.

The FT won't know what's causing it!

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

Update on my parents connection, t2 timeouts on all return channels 13 t3 errors on channels 4. Sync errors every day 16 consecutive t3 errors while trying to range on upstream channel 8 there is no channel 8? 27 critical errors since last factory reset 6 days ago. There tv continues to freeze yet there still paying there bill on time every time since the 90's. They continue to hope to get there service fixed/resolved.

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13310000007.241QAM 25625
21390000003.940QAM 2561
3147000000440QAM 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.841QAM 25611
13227000000641QAM 25612
142350000006.141QAM 25613
152430000006.141QAM 25614
16251000000641QAM 25615
17259000000641QAM 25616
182670000006.141QAM 25617
192750000006.341QAM 25618
202830000006.641QAM 25619
212910000006.741QAM 25620
222990000006.741QAM 25621
233070000006.941QAM 25622
24315000000741QAM 25623
253230000007.241QAM 25624
263390000007.340QAM 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
12Locked4110
13Locked4100
14Locked4110
15Locked4100
16Locked4110
17Locked4110
18Locked4100
19Locked4100
20Locked4110
21Locked4110
22Locked4110
23Locked4100
24Locked4100
25Locked4110
26Locked4010
27Locked4110
28Locked4100
29Locked4110
30Locked4100
31Locked4010

 

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000049.35120QAM 641
14310000049.35120QAM 642
236600000495120QAM 643
330100000495120QAM 644
42360000049.35120QAM 645

Upstream bonded channels

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

 

Time Priority Description
24-09-2023 17:28:41criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
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;
24-09-2023 14:32:10criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-09-2023 10:42:22noticeREGISTRATION COMPLETE - Waiting for Operational status
24-09-2023 10:42:19noticeUS 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;
24-09-2023 10:42:14noticeDS 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;
24-09-2023 10:42:02warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-09-2023 10:41:59noticeHonoring MDD; IP provisioning mode = IPv4
24-09-2023 10:41:50criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-09-2023 10:41:38criticalCable Modem Reboot via RG reboot command
23-09-2023 16:41:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 16:41:54critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 16:41:54criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 16:40:46criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 09:59:18criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 09:59:06criticalCable Modem Reboot via RG reboot command
22-09-2023 10:14:07criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
22-09-2023 10:13:55criticalCable Modem Reboot via RG reboot command
21-09-2023 18:08:05criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
21-09-2023 18:07:54criticalCable Modem Reboot via RG reboot command
21-09-2023 10:14:54criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
21-09-2023 10:14:43criticalCable Modem Reboot via RG reboot command
20-09-2023 09:48:01criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
20-09-2023 09:47:49criticalCable Modem Reboot via RG reboot command
19-09-2023 10:56:58criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-09-2023 10:56:47criticalCable Modem Reboot via RG reboot command
18-09-2023 10:24:22criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-09-2023 10:24:10criticalCable Modem Reboot via RG reboot command

Hi @Viper-t,

Thank you for expanding. Would you mind clarifying a little further what issues you/your parents are experiencing? I can see you've mentioned the TV service freezing. Is this only happening on specific channels or apps?

Thanks,
 


Zach - Forum Team
New around here? To find out more about the Community Forums, take a look at our FAQs!


Viper-t
Fibre optic

Hi zach, She tells me they do not use apps and it happens on mutiple channels, we have already answered all this and 2 engineers have been already who havent fixed anything, one of which confirmed bad snr after getting off the phone with networks, though that has since disappeared and has been denied (luckily i record all encounters). They just want there tv to stop freezing, as you can see there are big problems with all the data I'm sending, I really don't know what vm want from me you have all the data the engineers haven't fixed it. So some resolution needs to happen moving forward, why does getting any problem fixed with vm take so so long? It's never ending, just give people the service you sell then there is no problem its 2023.

This does not look like a flat power spectrum, there is nearly 4db of tilt on the downstream (3.6), also the last 5 days of bqm shows terrible latency and packet loss, which is ALL the time (everyday) as previous pictures. Last night again picture froze while recording her programme, correctables are now hidden on hub5. Now this is a fault and needs to be fixed if not we will take it higher as we are not here to keep sending data to Virgin Media my parents are customers and I do not work for vm although this last year seems like I do. You will be held accountable. The problem you sent engineers for is not fixed so what is going to be done please?.

513ae56f12c1b5fb03e9accb2605064206300b94-27-09-2023.png513ae56f12c1b5fb03e9accb2605064206300b94-26-09-2023.png513ae56f12c1b5fb03e9accb2605064206300b94-25-09-2023.png513ae56f12c1b5fb03e9accb2605064206300b94-24-09-2023.png513ae56f12c1b5fb03e9accb2605064206300b94-23-09-2023.png

 

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1331000000741QAM 25625
21390000003.740QAM 2561
31470000003.940QAM 2562
41550000003.940QAM 2563
51630000004.140QAM 2564
61710000004.441QAM 2565
71790000004.741QAM 2566
81870000004.841QAM 2567
91950000005.141QAM 2568
102030000005.341QAM 2569
112110000005.741QAM 25610
122190000005.741QAM 25611
132270000005.841QAM 25612
14235000000641QAM 25613
15243000000641QAM 25614
162510000005.841QAM 25615
172590000005.941QAM 25616
18267000000641QAM 25617
192750000006.241QAM 25618
202830000006.441QAM 25619
212910000006.641QAM 25620
222990000006.641QAM 25621
233070000006.741QAM 25622
243150000006.942QAM 25623
25323000000742QAM 25624
263390000007.141QAM 25626
273470000007.241QAM 25627
283550000007.241QAM 25628
293630000007.341QAM 25629
303710000007.241QAM 25630
313790000007.240QAM 25631

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked4100
2Locked4000
3Locked4000
4Locked4000
5Locked4000
6Locked4100
7Locked4110
8Locked4100
9Locked4100
10Locked4100
11Locked4100
12Locked4100
13Locked4100
14Locked4110
15Locked4100
16Locked4110
17Locked4110
18Locked4110
19Locked4100
20Locked4100
21Locked4120
22Locked4100
23Locked4110
24Locked4210
25Locked4220
26Locked4110
27Locked4120
28Locked4120
29Locked4110
30Locked4120
31Locked4020

Hey @Viper-t,

Thanks for coming back to us, I would like to go about looking into this deeper with you, for me to do so I will go about sending you a private message now.

Joe