Participant

Re: Reseting modem and router several times per day.

Thank you for your help. Now I understand and can see what are the correct levels. I read the info at the beginning of the forum and saw the 50 db max number, but the tech said it would work as high as 53 db... I also see the 24 download channels are all below 8 db except for 2 which are at 8.8 and 8.2 which are much lower than the 12 to 16 db levels I had before.

Established Sharer

Re: Reseting modem and router several times per day.


sh12313 wrote:

Thank you for your help. Now I understand and can see what are the correct levels. I read the info at the beginning of the forum and saw the 50 db max number, but the tech said it would work as high as 53 db... I also see the 24 download channels are all below 8 db except for 2 which are at 8.8 and 8.2 which are much lower than the 12 to 16 db levels I had before.


The tech is wrong about upstream working OK at +53 dBmV with DOCSIS3 modems.   It used to be that way with slower non-bonded DOCSIS2 TDMA modems from 4 years ago or older. 
As for the "12 to 16 db" download levels you had before, those were all NEGATIVE.  Your numbers are positive now, so the real difference is about 20 dB, which is 100 times more signal than before.

Expert

Re: Reseting modem and router several times per day.

copy and paste the entire level page, let's see what the DS levels are... The corroded connector may have fixed the US levels.

And anything above +52 dBmv will not work with 4 bonded channels...

 To run at +53 it would need to drop multiple channels and probably lock on just one.

While it might work, It's going to be slow and jump around.

 Glad it's fixed.

 

Participant

Re: Reseting modem and router several times per day.

As of this morning:

Status

Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1Locked256QAM32645.00 MHz-9.30 dBmV37.64 dB15161065
2Locked256QAM10513.00 MHz-7.40 dBmV38.61 dB25512237
3Locked256QAM11519.00 MHz-7.20 dBmV38.98 dB23802213
4Locked256QAM12525.00 MHz-8.00 dBmV38.61 dB25391300
5Locked256QAM13531.00 MHz-8.10 dBmV38.61 dB24782198
6Locked256QAM14537.00 MHz-6.30 dBmV40.37 dB2644939
7Locked256QAM15543.00 MHz-7.50 dBmV38.98 dB2141252
8Locked256QAM16549.00 MHz-7.60 dBmV38.98 dB2104192
9Locked256QAM17555.00 MHz-6.80 dBmV38.98 dB1823245
10Locked256QAM18561.00 MHz-7.00 dBmV38.61 dB2061245
11Locked256QAM19567.00 MHz-8.40 dBmV38.98 dB20411195
12Locked256QAM20573.00 MHz-7.40 dBmV38.98 dB1772239
13Locked256QAM21579.00 MHz-6.90 dBmV40.37 dB19612141
14Locked256QAM22585.00 MHz-7.60 dBmV38.61 dB1814209
15Locked256QAM23591.00 MHz-7.30 dBmV38.61 dB1681202
16Locked256QAM24597.00 MHz-6.80 dBmV38.98 dB17601228
17Locked256QAM25603.00 MHz-7.40 dBmV38.98 dB1503122
18Locked256QAM26609.00 MHz-7.40 dBmV38.61 dB1442130
19Locked256QAM27615.00 MHz-6.80 dBmV38.61 dB1436168
20Locked256QAM28621.00 MHz-7.60 dBmV38.61 dB1438104
21Locked256QAM29627.00 MHz-8.40 dBmV38.98 dB149096
22Locked256QAM30633.00 MHz-8.30 dBmV38.61 dB16561081
23Locked256QAM31639.00 MHz-8.90 dBmV38.61 dB1479117
24Locked256QAM9507.00 MHz-8.50 dBmV38.61 dB27414202

 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA35120 kSym/s30.60 MHz42.00 dBmV
2LockedATDMA42560 kSym/s37.00 MHz43.00 dBmV
3LockedTDMA12560 kSym/s19.40 MHz42.25 dBmV
4LockedATDMA25120 kSym/s24.20 MHz42.00 dBmV


 

Current System Time: Wed Mar 08 09:15:41 2017


 The event log has entries again:
Event Log
Time Priority Description
Tue Mar 07 11:22:55 20173No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:23:11 20173Ranging Request Retries exhausted;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:23:11 20173Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:23:22 20173No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:26:01 20173Ranging Request Retries exhausted;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:26:01 20173Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:26:11 20173No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:28:51 20173Ranging Request Retries exhausted;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:28:51 20173Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:29:01 20173No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:31:41 20173Ranging Request Retries exhausted;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:31:41 20173Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:31:51 20173No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:39:27 20175RCS Partial Service;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:56:41 20173No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:56:59 20173Ranging Request Retries exhausted;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:56:59 20173Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Tue Mar 07 11:57:10 20173No Ranging Response received - T3 time-out;CM-MAC=d4:04:cd:18:a3:f1;CMTS-MAC=00:17:10:86:73:89;CM-QOS=1.1;CM-VER=3.0;
Participant

Re: Reseting modem and router several times per day.

I probably left out the negative sign for the 10 to 12 dBmv numbers. I see one or more now at - 9 +
Participant

Re: Reseting modem and router several times per day.

Checked again and lost one upstream channel:

Status

Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA35120 kSym/s30.60 MHz43.50 dBmV
2LockedATDMA42560 kSym/s37.00 MHz42.75 dBmV
4LockedATDMA25120 kSym/s24.20 MHz42.75 dBmV


 

Current System Time: Wed Mar 08 11:41:32 2017

Expert

Re: Reseting modem and router several times per day.

I'd call TWC back out.. the DS levels are too low and at the edge of reliable operation as shown by the hcorrected/ uncorrected hits...

Is the outside line overhead and is it rg 6 or rg11? If thru trees, it's been chewed up and has water in it.

 

Is the house 200' off the street and then there's inhouse wiring?  Really lookls like the hardline tapoff needs to be changed to one that's 3 or 6 db hotter...

 

 Any splitters or old rg 59 in the house? they need to go as well.

?

 

Participant

Re: Reseting modem and router several times per day.

I can say the line from the street to the back of the house is less than a year old and is underground. It does route in a straight line for most of the run and then turns along the back of the house before comming up to the box.  I can't say how old the line is from box into the office room is but there is one connector (wall plate) between box and modem. I just checked and still missing channel 1 up. I will call them out again. Also interested to see if I reset modem and get channel 1 back, is channel one related to the errors. Log has all entries from 3/7 and nothing for 3/8. Anyway, I will call first. Thank you very much for your help.

Participant

Re: Reseting modem and router several times per day.

Another service call scheduled for Friday at 1 pm. They reset modem and channel 1 up is back. Will keep an eye on event log. The cable from box to wall outlet is about 30 feet and could be pretty old. I've been here since 2010 and it pre-dates me for sure. Have no idea when it was installed. I will have him measure loss on it?

Expert

Re: Reseting modem and router several times per day.

lost upstream with good levels usually indicates RF interference from radio transmitters.

 You're losing the 19 mHz channel, might be shortwave radio transmitters or ham radio getting in  That will be around the 15 meter band, anything from 17-13 meters will bother it.  I suspect a bad hardline tapped off, probably running accross the street somewhere in your neighborhood...