Forum Discussion
Is there ANYONE at Cox that understands this? What is causing this dynamic range window violation?
I also wish that we could get some details from Cox, but it seems like they prefer not to go into technical details on the forum. That leaves us to figure things out on our own. I wonder if these DRW violations are even important in DOCSIS 3.1. Take a look at this information:
8.3.3 Dynamic Range Window
The Dynamic Range Window defines a 12dB range of Transmit Power Levels for the CM to use for each of the channels in its Transmit Channel Set. The DRW is controlled by the CMTS and communicated to the CM in the RNG-RSP or in the TCC encodings of the REG-RSP-MP or the DBC-REQ message.
8.3.3.1 Dynamic Range Window When Operating with a DOCSIS 3.1 CMTS
The top of the DRW is defined as P1.6hi – P1.6load_min_set [DOCSIS PHYv3.1]. The CMTS manages the Dynamic Range Window for the modem, ensuring that the CM is not ranged at a value that would result in a violation of the Dynamic Range Window. If the CMTS commands the modem to use a transmit power level P1.6r_n, that would result in a violation of the Dynamic Range Window, the CM performs the commanded adjustment and indicates an error in the Bit 15 or 14 of the SID field of the RNG-REQ Messages.
8.3.3.2 Dynamic Range Window When Operating With a DOCSIS 3.0 CMTS
The top of the DRW is defined as Phi - Pload_min_set [DOCSIS PHYv3.0]. The CMTS manages the Dynamic Range Window for the modem. If the CMTS commands the modem to do something which would result in a violation of the Dynamic Range Window, the CM will reject or ignore the command.
In other words, under DOCSIS 3.0, a DRW violation would actually cause the cable modem to reject the ranging response and who knows what kind of problem that might cause. But with DOCSIS 3.1 the modem makes the adjustment anyway and then sends an information message back to the CMTS. But since it made the adjustment maybe there's no harm done.
In terms of what causes this message in the first place, my guess is a spike of upstream noise. But maybe it's not even that. Maybe it's completely harmless. In any case the DRW violation doesn't prevent the modem from doing what it's been requested to do. So maybe it doesn't matter at all.
- Peterockinit5 years agoNew Contributor III
That's interesting! And I agree. We are ignored because it can't be fixed with a simple reboot.
I don't even know if the dynamic range window is what is causing my issues. But either way my issues are not being fixed. I have thousands of uncorrectables within a day of a fresh reboot and I get intermittent disconnects and gaming is impossible because of the lag and freezing which I assume is from packet loss.
$170 per month for internet and this is what we get. No idea how this monopoly is allowed. It's either crappy"hi speed internet" from cox or 3mbps DSL from CenturyLink