![]() |
16QAM & 64QAM Interference
Is it correct that 64QAM is more prone to interference than 16QAM?
|
Re: 16QAM & 64QAM Interference
Quote:
Here is a phaser diagram for QAM16: https://www.cableforum.co.uk/images/local/2015/07/9.gif Each state is well defined with a large guard band, each point can move around quite a bit due to niose, propgation effects etc and still be easy to distinguish. Contrast to QAM64: https://www.cableforum.co.uk/images/...2015/07/10.gif HTH. |
Re: 16QAM & 64QAM Interference
Quote:
However, the extra bandwidth you get from it makes it worthwhile if the network is capable of it. The systems Virgin use mean that if interference rises, it'll drop from QAM64 to QAM16 and even QPSK, reducing overall bandwidth but increasing stability until the issue is fixed. |
Re: 16QAM & 64QAM Interference
although it seems like we have been waiting forever the upstream upgrades and channel bonding, I can see VM have been doing some work on the qt. For as long as I can remember upstream maintenance requests have always been qpsk and when I looked at my power level last week because of the heat, I noticed everything on upstream is now qam16.
Just checked again and very interestingly although I am still on 2 upstreams, one of them is qam64 and it defo wasn't last week. Things are looking up. If they can get 3 bonded upstream channels on qam64 sorted before xmas then we will be in an excellent place for 300/20. |
Re: 16QAM & 64QAM Interference
Quote:
My 2 upstreams are still both QAM16, sadly :( |
Re: 16QAM & 64QAM Interference
the data has been qam16 for yonks but the maintenance requests have always been qpsk. I have just had a quick flick through old threads and I don't think I have ever posted a dump from the upstream burst tab so I cant show you what it used to be like. This is the new one:
|
Re: 16QAM & 64QAM Interference
Could be nothing, could indicate you've been moved from a profile using 16QAM for data and QPSK for maintenance to one using 64QAM for data and 16QAM for maintenance.
There are a few 'interesting' software caveats on one of the CMTS platforms. If you've been resegmented onto one of the new CMTS that'd explain it. ---------- Post added at 13:43 ---------- Previous post was at 13:42 ---------- Quote:
---------- Post added at 13:44 ---------- Previous post was at 13:43 ---------- Quote:
|
Re: 16QAM & 64QAM Interference
cpc24-linc11-2-0-custxxx.12-1.cable.virginm.net
I would have to trawl through previous posts but the linc11-2-0 is defo the same as it was years ago. I'll need to check the cpc24 bit. Edit: just checked and it has been the same since 2012. I found a post for 2010 where I was cpc2 but it hasn't changed since 2012. |
Re: 16QAM & 64QAM Interference
Cisco 10k.
Must be a profile change. |
Re: 16QAM & 64QAM Interference
1 Attachment(s)
It was QPSK now QAM16 for for maintenance too
Attachment 26244 cpc67132-uddi22-2-0-cust***.20-3.cable.virginm.net |
Re: 16QAM & 64QAM Interference
Cheers Martin, must be a network-wide configuration change on the 10ks, probably part of the upgrade to more channels :)
|
Re: 16QAM & 64QAM Interference
Just out of interest, what make is this CMTS?
cpc65166-telf11-2-0-custxxx.16-1.cable.virginm.net Still using QPSK for the maintenance bits. |
Re: 16QAM & 64QAM Interference
Okay yes it's an upstream profile change to allow the fallback mechanisms to work properly.
---------- Post added at 12:36 ---------- Previous post was at 12:35 ---------- Quote:
|
Re: 16QAM & 64QAM Interference
Quote:
|
Re: 16QAM & 64QAM Interference
Quote:
|
| All times are GMT +1. The time now is 22:56. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum