Browser

Re: Constant intermittent DS Partial Service Fallback: MDD Lost errors

I have photos but I can seem to figure out how to post them. I don't see the same screens in the posts that explain how to do it !!!  I get a pop-up with source, image description & dimensions...

Expert

Re: Constant intermittent DS Partial Service Fallback: MDD Lost errors

post them to Imgur then copy the direct link which ends in PNG or JPG

 Paste that link in the photo-URL tab

 

Browser

Re: Constant intermittent DS Partial Service Fallback: MDD Lost errors

http://imgur.com/a/BqcAJ

 

  • One pic of tap
  • Two other pics of underground line and an Amp? - THESE COULD NO LONGER BE IN USE AND OLD BUT SAW THEM AND DECIDED TO TAKE PICTURES
Expert

Re: Constant intermittent DS Partial Service Fallback: MDD Lost errors

Is this a tree root pulling a drop out of the ground or is that a larger 3/4" trunk line.. ?

 

5XWEgRQ

Expert

Re: Constant intermittent DS Partial Service Fallback: MDD Lost errors

This looks cobbled together, left and right hardline "stingers" are of different types... something has been patched together.xv2BdGL

Spectrum Employee

Re: Constant intermittent DS Partial Service Fallback: MDD Lost errors


@mkolinsk wrote:

http://imgur.com/a/BqcAJ

 

  • One pic of tap
  • Two other pics of underground line and an Amp? - THESE COULD NO LONGER BE IN USE AND OLD BUT SAW THEM AND DECIDED TO TAKE PICTURES

source of ingress

Right there where I circled in red, that's going to cause issues for all three customers on that tap.

 

It's hard to tell with the picture quality but it sure looks like metal braids sticking out the back of the fittings (can cause some pretty bad ingress, and egress, basically a signal leak), and the coax looks like it's being crushed with too tight of a turn (causes impedance mismatch)

 

The one nice thing I see is how they seem to be labeled with the house/appartment numbers, and that there's a terminator on the port on the left side to prevent any leak there.

 

I have a feeling the wires are getting bent too much trying to cram into that rather small pedestal, that's probably how it got like that in the first place.

 

My postings on this site are my own, off-the-clock, and don’t necessarily represent TWC’s/Charter's strategies or opinions.
Browser

Re: Constant intermittent DS Partial Service Fallback: MDD Lost errors

When I had opened it up, the extreme bend right where you have circled @agentx5 stuck right out because I thought it is a malpractice to bend coax like that. I went back and looked just now and there are not any braids showing and no apparent cuts in the plastic jacket. I did straighten it out a bit and I also check the connections on that section of coax. It wasn't even finger tight to the tap. I turned it several times by hand and then finished it with about 1/4 or more turn with a 7/16 wrench.

 

With all this being said, does that section of coax need to be replaced or do we just see if the tightening of that connection has any inmpact? Did that tight turn in the coax permanently damage it or might it be okay? 

 

Thanks again @MsRaye and @agentx5 for all the help. I really feel like we are finally getting somewhere now :-) 

Browser

Re: Constant intermittent DS Partial Service Fallback: MDD Lost errors


@MsRaye wrote:

Is this a tree root pulling a drop out of the ground or is that a larger 3/4" trunk line.. ?

 

 


@MsRaye It is a tree root pulling a drop out of the ground. I don't know if that is an active drop or 1 of the first 2 drops that have since been replaced by the existing (3rd) drop. 

Browser

Re: Constant intermittent DS Partial Service Fallback: MDD Lost errors

I restarted my modem and my neighbor's just have a clean slate after tightening that connection and straightening the bend. Here is my signal page for a baseline. 

 

DownstreamBonding Channel Value
Channel ID17 18 19 20 21 22 23 24 
Frequency555000000 Hz 561000000 Hz 567000000 Hz 573000000 Hz 579000000 Hz 585000000 Hz 591000000 Hz 597000000 Hz 
Signal to Noise Ratio38 dB 39 dB 39 dB 39 dB 39 dB 39 dB 38 dB 38 dB 
Downstream ModulationQAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 
Power Level3 dBmV  3 dBmV  3 dBmV  3 dBmV  3 dBmV  3 dBmV  3 dBmV  3 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency37000000 Hz 24200000 Hz 30600000 Hz 19400000 Hz 
Ranging Service ID7772 7772 7772 7772 
Symbol Rate2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level39 dBmV 36 dBmV 37 dBmV 36 dBmV 
Upstream Modulation[3] QPSK
[3] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID17 18 19 20 21 22 23 24 
Total Unerrored Codewords4935265 3889651 3898629 3906463 3883326 3884414 3887524 3915705 
Total Correctable Codewords13 44 14 43 
Total Uncorrectable Codewords1451 1358 556 1351 1521 1475 1569 1510 

 

TimePriorityCodeMessage
Aug 31 2016 22:23:336-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=b0:77:ac:2c:aa:26;CMTS-MAC=00:17:10:8b:6b:12;CM-QOS=1.1;CM-VER=3.0;
Aug 31 2016 22:23:335-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b0:77:ac:2c:aa:26;CMTS-MAC=00:17:10:8b:6b:12;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot from GUI/Configuration page ;CM-MAC=b0:77:ac:2c:aa:26;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 30 2016 22:32:486-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=b0:77:ac:2c:aa:26;CMTS-MAC=00:17:10:8b:6b:12;CM-QOS=1.1;CM-VER=3.0;
Aug 30 2016 22:32:485-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b0:77:ac:2c:aa:26;CMTS-MAC=00:17:10:8b:6b:12;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot from GUI/Configuration page ;CM-MAC=b0:77:ac:2c:aa:26;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 30 2016 21:32:535-WarningT202.0Lost MDD Timeout;CM-MAC=b0:77:ac:2c:aa:26;CMTS-MAC=00:17:10:8b:6b:12;CM-QOS=1.1;CM-VER=3.0;
Aug 30 2016 21:32:535-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b0:77:ac:2c:aa:26;CMTS-MAC=00:17:10:8b:6b:12;CM-QOS=1.1;CM-VER=3.0;
Aug 30 2016 17:54:585-WarningT202.0Lost MDD Timeout;CM-MAC=b0:77:ac:2c:aa:26;CMTS-MAC=00:17:10:8b:6b:12;CM-QOS=1.1;CM-VER=3.0;
Aug 30 2016 17:54:585-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b0:77:ac:2c:aa:26;CMTS-MAC=00:17:10:8b:6b:12;CM-QOS=1.1;CM-VER=3.0;
Aug 30 2016 16:05:246-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=b0:77:ac:2c:aa:26;CMTS-MAC=00:17:10:8b:6b:12;CM-QOS=1.1;CM-VER=3.0;
Aug 30 2016 16:05:245-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b0:77:ac:2c:aa:26;CMTS-MAC=00:17:10:8b:6b:12;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot from GUI/Configuration page ;CM-MAC=b0:77:ac:2c:aa:26;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: Constant intermittent DS Partial Service Fallback: MDD Lost errors

any idea if it was your drop that was 2 turns loose? And was TWC out and didn't tighten it properly? Their techs are supposed to have both a 7/156 and 9/16 torque wrench for the rg6 and rg11 connector nuts. They'r set to click at 11 inch pounds.

1 loose connector can affect all 3 ports, the worst will be the one that's loose