on 02-11-2022 19:20
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?
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 |
Answered! Go to Answer
on 13-11-2022 13:20
Hi Viper-t,
Thanks for posting and sorry to hear you've been having some issues with the connection.
I've had a look at things from our side and it looks like I'll need to arrange another engineer visit.
Before I can do this I'll need to confirm a few details with you, I've popped you over a private message for this (purple envelope, top right hand corner)
Alex_Rm
on 15-11-2022 13:10
Hi can you tell me what you are seeing wrong your end please? QAM is back at 64 for how long I have no idea I'll send error log for more info. Can someone just explain to me what is actually going wrong and with what as im hearing multiple answers depending who I'm speaking with. Engineer didnt know why he was there says my qam settings are done at head office but he didn't know what qam was so had to ring another guy, but your saying I need an engineer can you let me know please for transparency what you think I need an engineer for as the guy who the engineer rang said it was work on the network I cant get a straight or confident answer from anyone which concerns me as I don't want it to get worse and drag out another complaint many thanks kind regards
Time Priority Description
Thu 01/01/1970 00:01:28 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:28 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 10/11/2022 11:43:03 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 10/11/2022 11:54:37 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 10/11/2022 11:54:41 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 10/11/2022 11:55:04 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 10/11/2022 12:17:40 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 10/11/2022 12:17:41 | 6 | CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 10/11/2022 12:17:44 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 10/11/2022 12:19:13 | 3 | Received 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; |
Thu 10/11/2022 12:41:53 | 4 | Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 10/11/2022 12:42:37 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 10/11/2022 12:43:17 | 6 | CM-STATUS message sent. Event Type Code: 16; 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 01/01/1970 00:01:21 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:21 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 10/11/2022 13:14:53 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:22 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:22 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 10/11/2022 13:30:20 | 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 11/11/2022 03:05:45 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/11/2022 17:16:50 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:22 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:22 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 14/11/2022 17:50:53 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 14/11/2022 17:51:04 | 5 | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 14/11/2022 17:51:28 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 15/11/2022 02:13:09 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 16-11-2022 11:51
Can I get a reply on what all these errors are please? We all know T3 time outs but there are so many different ones in a short period of time, there was lots more but a hard reset wiped them.
Regards
on 18-11-2022 19:10
Hi @Viper-t, thanks for getting back to us.
Having made some checks, I would like to book a technician to attend your property. I am going to send you a private message, to confirm some details. Please look out for the purple envelope in the top right of the screen.
Regards
Lee_R
on 19-11-2022 12:20
I've already got one booked Lee thanks, he's on his way now but just phoned me and has no idea why he is coming nor do I as no one will tell me, my qam levels keep dropping from 64 qam to 16, but a previous agent said they seen there's a problem so I would need an engineer. This engineer is the second one to tell me the qam is nothing to do with them thats your end so I think there needs to be communication between head office and engineers as they have no idea why they are coming.
Regards
on 19-11-2022 12:41
The QAM is the resonsibility of Netwoks after the tech has determined the home sote and caninet are OK.
on 21-11-2022 14:08
Hi @Viper-t,
Thank you for coming back to us. Can you tell us how your appointment went? Is there anything else we can do to help?
Please keep us updated on how you got on and what your connection is like.
Thank you.
on 21-11-2022 21:36
This is the last straw tonight my whole family who use your services specifically for gaming, or the Internet wouldn't be a problem, you advertise FOR gaming tonight I haven't seen connection like this since dial up days I'm on 1000/50 mbps tonight my character In game was literally skipping side to side the in game network graph confirms the spikes and continuous stuttering, it was terrible this is the worse I've seen it. Funnily my cisas case was paid today and after All that palaver here we are with a worse than before connection, you can see the packet loss spikes on the graph wgich mirrors the high latency spikes. Again in my apology letter again I was again more or less asked to leave, since the late 90s I've been with virgin before probably alot of new staff so I will not leave, fix my service I pay for. Look at my history I've never made a complaint only since getting the volt package. No one finds it weird I get faster wifi speeds than ethernet cat 6a, ive had 2 engineers who both said they have no clue why they were here and when ringing there are no notes even though it was clearly my qam levels as beginning of this thread and I recieved 3 emails stating you have found a problem your end I would need an engineer when he arrives don't know why he's here? Like what did you find? Also his speed tests were massively different everytime he done it mostly it was around 200 yet wifi 500+ my devices are gigabit capable wired. So he gave me a new hub4 and it was worse like what is going on he then offered a hub 5 but after seeing the threads on here I couldn't accept as ive been at this for months ita stressing us out so much.
on 21-11-2022 21:44
Hi I see now why my gaming is still terrible my QAM levels are still wrong my setup is wrong.
1 | 43100000 | 41.770599 | 5120 KSym/sec | 32QAM | 2 |
2 | 30100000 | 41.270599 | 5120 KSym/sec | 16QAM | 4 |
3 | 36600000 | 41.520599 | 5120 KSym/sec | 16QAM | 3 |
4 | 49600000 | 42.020599 | 5120 KSym/sec | 64QAM | 1 |
5 | 23600000 | 40.520599 | 5120 KSym/sec | 64QAM | 5 |
1 | US_TYPE_STDMA | 0 | 0 | 0 | 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 |
5 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
6 | 10.8 | 38.8 | 2K | QAM8 |
6 | OFDMA | 220 | 53.4 | 0 | 0 |
on 21-11-2022 23:36
Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
6 | 10.8 | 38.8 | 2K | QAM8 |
The channel width doesn't seem right to me. As in not being centred in the upstream spectrum. 10MHz would be centred.
Indeed, if you look in the forum for threads about DOCSIS 3.1 upstream issues, nearly all of them are not centred on 10MHz.
I can't be sure that 10.8 and 10.4 (which I also see in the problem threads) are not within tolerance as I'm still learning D3.1, but the Cablelabs spec does not mention any off-centre tolerance that I could find.
I wonder what the Forum Team will make of what I've suggested and if I'm wrong, I apologise for work others may have to do!