Qam wrong?

[Viper-t]

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

1	43100000	41.3	5120 KSym/sec	32QAM	2
2	30100000	40.8	5120 KSym/sec	16QAM	4
3	36600000	41	5120 KSym/sec	16QAM	3
4	49600000	41.5	5120 KSym/sec	64QAM	1
5	23600000	40	5120 KSym/sec	64QAM	5

[Sephiroth]

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.

[Viper-t]

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 👍 

[Martin_N]

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

[Sephiroth]

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. 

[Viper-t]

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]

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!

[Viper-t]

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

1	331000000	7.2	41	QAM 256	25
2	139000000	3.9	40	QAM 256	1
3	147000000	4	40	QAM 256	2
4	155000000	4.1	40	QAM 256	3
5	163000000	4.2	40	QAM 256	4
6	171000000	4.6	41	QAM 256	5
7	179000000	4.8	41	QAM 256	6
8	187000000	4.9	41	QAM 256	7
9	195000000	5.3	41	QAM 256	8
10	203000000	5.4	41	QAM 256	9
11	211000000	5.8	41	QAM 256	10
12	219000000	5.8	41	QAM 256	11
13	227000000	6	41	QAM 256	12
14	235000000	6.1	41	QAM 256	13
15	243000000	6.1	41	QAM 256	14
16	251000000	6	41	QAM 256	15
17	259000000	6	41	QAM 256	16
18	267000000	6.1	41	QAM 256	17
19	275000000	6.3	41	QAM 256	18
20	283000000	6.6	41	QAM 256	19
21	291000000	6.7	41	QAM 256	20
22	299000000	6.7	41	QAM 256	21
23	307000000	6.9	41	QAM 256	22
24	315000000	7	41	QAM 256	23
25	323000000	7.2	41	QAM 256	24
26	339000000	7.3	40	QAM 256	26
27	347000000	7.4	41	QAM 256	27
28	355000000	7.4	41	QAM 256	28
29	363000000	7.5	41	QAM 256	29
30	371000000	7.4	41	QAM 256	30
31	379000000	7.4	40	QAM 256	31

Downstream bonded channels

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

1	Locked	41	0	0
2	Locked	40	0	0
3	Locked	40	0	0
4	Locked	40	0	0
5	Locked	40	0	0
6	Locked	41	0	0
7	Locked	41	0	0
8	Locked	41	0	0
9	Locked	41	0	0
10	Locked	41	0	0
11	Locked	41	0	0
12	Locked	41	1	0
13	Locked	41	0	0
14	Locked	41	1	0
15	Locked	41	0	0
16	Locked	41	1	0
17	Locked	41	1	0
18	Locked	41	0	0
19	Locked	41	0	0
20	Locked	41	1	0
21	Locked	41	1	0
22	Locked	41	1	0
23	Locked	41	0	0
24	Locked	41	0	0
25	Locked	41	1	0
26	Locked	40	1	0
27	Locked	41	1	0
28	Locked	41	0	0
29	Locked	41	1	0
30	Locked	41	0	0
31	Locked	40	1	0

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

0	49600000	49.3	5120	QAM 64	1
1	43100000	49.3	5120	QAM 64	2
2	36600000	49	5120	QAM 64	3
3	30100000	49	5120	QAM 64	4
4	23600000	49.3	5120	QAM 64	5

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	1	0	0
1	ATDMA	0	1	0	0
2	ATDMA	0	1	0	0
3	ATDMA	0	1	0	0
4	ATDMA	0	1	13	0

Time Priority Description

24-09-2023 17:28:41	critical	Started 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:50	critical	No 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:40	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-09-2023 17:27:39	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-09-2023 14:33:18	critical	16 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:18	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-09-2023 14:32:10	critical	Started 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:22	notice	REGISTRATION COMPLETE - Waiting for Operational status
24-09-2023 10:42:19	notice	US 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:14	notice	DS 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:02	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-09-2023 10:41:59	notice	Honoring MDD; IP provisioning mode = IPv4
24-09-2023 10:41:50	critical	SYNC 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:38	critical	Cable Modem Reboot via RG reboot command
23-09-2023 16:41:55	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 16:41:54	critical	16 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:54	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
23-09-2023 16:40:46	critical	Started 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:18	critical	SYNC 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:06	critical	Cable Modem Reboot via RG reboot command
22-09-2023 10:14:07	critical	SYNC 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:55	critical	Cable Modem Reboot via RG reboot command
21-09-2023 18:08:05	critical	SYNC 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:54	critical	Cable Modem Reboot via RG reboot command
21-09-2023 10:14:54	critical	SYNC 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:43	critical	Cable Modem Reboot via RG reboot command
20-09-2023 09:48:01	critical	SYNC 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:49	critical	Cable Modem Reboot via RG reboot command
19-09-2023 10:56:58	critical	SYNC 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:47	critical	Cable Modem Reboot via RG reboot command
18-09-2023 10:24:22	critical	SYNC 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:10	critical	Cable Modem Reboot via RG reboot command

[Zach_R]

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,
 

[Viper-t]

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?.

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

1	331000000	7	41	QAM 256	25
2	139000000	3.7	40	QAM 256	1
3	147000000	3.9	40	QAM 256	2
4	155000000	3.9	40	QAM 256	3
5	163000000	4.1	40	QAM 256	4
6	171000000	4.4	41	QAM 256	5
7	179000000	4.7	41	QAM 256	6
8	187000000	4.8	41	QAM 256	7
9	195000000	5.1	41	QAM 256	8
10	203000000	5.3	41	QAM 256	9
11	211000000	5.7	41	QAM 256	10
12	219000000	5.7	41	QAM 256	11
13	227000000	5.8	41	QAM 256	12
14	235000000	6	41	QAM 256	13
15	243000000	6	41	QAM 256	14
16	251000000	5.8	41	QAM 256	15
17	259000000	5.9	41	QAM 256	16
18	267000000	6	41	QAM 256	17
19	275000000	6.2	41	QAM 256	18
20	283000000	6.4	41	QAM 256	19
21	291000000	6.6	41	QAM 256	20
22	299000000	6.6	41	QAM 256	21
23	307000000	6.7	41	QAM 256	22
24	315000000	6.9	42	QAM 256	23
25	323000000	7	42	QAM 256	24
26	339000000	7.1	41	QAM 256	26
27	347000000	7.2	41	QAM 256	27
28	355000000	7.2	41	QAM 256	28
29	363000000	7.3	41	QAM 256	29
30	371000000	7.2	41	QAM 256	30
31	379000000	7.2	40	QAM 256	31

Downstream bonded channels

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

1	Locked	41	0	0
2	Locked	40	0	0
3	Locked	40	0	0
4	Locked	40	0	0
5	Locked	40	0	0
6	Locked	41	0	0
7	Locked	41	1	0
8	Locked	41	0	0
9	Locked	41	0	0
10	Locked	41	0	0
11	Locked	41	0	0
12	Locked	41	0	0
13	Locked	41	0	0
14	Locked	41	1	0
15	Locked	41	0	0
16	Locked	41	1	0
17	Locked	41	1	0
18	Locked	41	1	0
19	Locked	41	0	0
20	Locked	41	0	0
21	Locked	41	2	0
22	Locked	41	0	0
23	Locked	41	1	0
24	Locked	42	1	0
25	Locked	42	2	0
26	Locked	41	1	0
27	Locked	41	2	0
28	Locked	41	2	0
29	Locked	41	1	0
30	Locked	41	2	0
31	Locked	40	2	0

[Joseph_B]

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