Expert

Re: SB6190 - Austin TX - High uncorrectable codewords on one channel;

Hey, anyone else from Austin care to check their signal page and see if they're getting channels below 501 mHz now?

 

Observer

Re: SB6190 - Austin TX - High uncorrectable codewords on one channel;

I am in Austin and do not have channels below 501 MHz.

 

Downstream channels aside, i do experience something very similar to what is described in this thread.  After several hours of clean signal i get a burst of corrected and uncorrected errors.

 

 

I am also on an SB6190

Expert

Re: SB6190 - Austin TX - High uncorrectable codewords on one channel;

post the signal page without resetting the modem. Are the correcteds on 513 519 525 and 585? If so you have broadcast tv ingress from a loose or corroded connection

or open/ too many plitter ports or a bad connection on one of them.

 could be anywhere from the pole to the modem

 

Observer

Re: SB6190 - Austin TX - High uncorrectable codewords on one channel;

I will post my stuff in a new thread at some point, but for now i am extremely interested in how things progress for WhyIrishMan.  There is nothing remarkable about the errors at the frequencies you mentioned.  In fact if have looked at all of the frequencies at my location from tvfool query and none stand out. 

 

Net of the strange >16 channel bonding that IrishMan is seeing, the described behavior is similar to my issue and as far as i can tell from the other threads different from what others experience.  We are both in Austin, use the SB6190, and see corrected/uncorrected in bursts.  My neighborhood is all buried.  My drop was just laid.  My in house cabling is 2 year old RG6 Quad.  I have a single splitter ahead of the modem, then to a three way that feeds phone modem and two TV.  There are no open ports.  I have traded out the splitters and redid all of the connections to no avail.

 

I now believe that it is upstream, or possibly related to the modem.  But there are a couple of things left to test so i want to do that first.  Unfortunately, i do not have another modem, so I cannot try that option, and its not worth spending $100 just to do that.  But that is the value of having these forums.

 

Based on the Arris HW thread at DSLReports, others have described similar issues on the SB6190.  TW has not provided us with the latest firmware which is a concern, but i have no reason to believe that would suddenly solve my problem (but do wish they would update us).  So IrishMan's comment that changing modems did not change the problem has me leaning toward a problem upstream.

 

But, based on that thread, my next step is a full pin (factory) reset.  I will report back if i see anything remarkable (like 24 channel bonding) for you and WhyIrishMan.

 

If the result of that test leads me away from the problem described in this thread i will start a new one with my stats.

 

Thnks to both of you, this information is very helpful.

 

 

Participant

Re: SB6190 - Austin TX - High uncorrectable codewords on one channel;

Let me clarify, it has stayed at 24 channels since i posted here, indicating to me that soemone on the other end read this; I do however still get the same behavior with a spike in uncorrectables on a random channel

 

Startup Procedure

ProcedureStatusComment
Acquire Downstream Channel Locked
Connectivity StateOKOperational
Boot StateOKOperational
Configuration FileOK 
SecurityEnabledBPI+
DOCSIS Network Access EnabledAllowed 

 

 
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1Locked256QAM23597.00 MHz3.80 dBmV38.98 dB00
2Locked256QAM2471.00 MHz5.00 dBmV40.95 dB00
3Locked256QAM3477.00 MHz5.30 dBmV40.95 dB00
4Locked256QAM4483.00 MHz5.20 dBmV40.95 dB00
5Locked256QAM5489.00 MHz4.90 dBmV40.37 dB00
6Locked256QAM6495.00 MHz4.90 dBmV40.95 dB00
7Locked256QAM7501.00 MHz4.80 dBmV40.37 dB00
8Locked256QAM8507.00 MHz5.10 dBmV40.37 dB00
9Locked256QAM9513.00 MHz4.50 dBmV40.37 dB00
10Locked256QAM10519.00 MHz4.90 dBmV40.95 dB00
11Locked256QAM11525.00 MHz4.60 dBmV40.37 dB00
12Locked256QAM12531.00 MHz4.60 dBmV40.37 dB00
13Locked256QAM13537.00 MHz4.70 dBmV40.37 dB00
14Locked256QAM14543.00 MHz4.10 dBmV40.95 dB80
15Locked256QAM15549.00 MHz4.60 dBmV40.37 dB30
16Locked256QAM16555.00 MHz4.00 dBmV38.98 dB50
17Locked256QAM17561.00 MHz4.10 dBmV38.98 dB50
18Locked256QAM18567.00 MHz4.20 dBmV40.37 dB70
19Locked256QAM19573.00 MHz3.90 dBmV40.37 dB00
20Locked256QAM20579.00 MHz4.10 dBmV40.37 dB00
21Locked256QAM21585.00 MHz3.90 dBmV40.37 dB00
22Locked256QAM22591.00 MHz3.70 dBmV40.37 dB00
23Locked256QAM1465.00 MHz5.10 dBmV40.37 dB00
24Locked256QAM24603.00 MHz3.80 dBmV40.37 dB00

 

 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA65120 kSym/s24.20 MHz42.50 dBmV
2LockedATDMA82560 kSym/s37.00 MHz42.50 dBmV
3LockedATDMA75120 kSym/s30.60 MHz42.50 dBmV
4LockedTDMA52560 kSym/s19.40 MHz41.25 dBmV



 

Current System Time: Tue Jun 28 15:27:50 2016

Thu Jan 01 00:02:16 19703No Ranging Response received - T3 time-out;CM-MAC=d4:0a:a9:00:da:e1;CMTS-MAC=00:17:10:86:5d:1b;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 21 21:49:31 20165TCS Partial Service;CM-MAC=d4:0a:a9:00:da:e1;CMTS-MAC=00:17:10:86:5d:1b;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 21 21:50:33 20163No Ranging Response received - T3 time-out;CM-MAC=d4:0a:a9:00:da:e1;CMTS-MAC=00:17:10:86:5d:1b;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 21 21:53:47 20165TCS Partial Service;CM-MAC=d4:0a:a9:00:da:e1;CMTS-MAC=00:17:10:86:5d:1b;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 22 02:07:36 20163No Ranging Response received - T3 time-out;CM-MAC=d4:0a:a9:00:da:e1;CMTS-MAC=00:17:10:86:5d:1b;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 28 14:59:38 20165TCS Partial Service;CM-MAC=d4:0a:a9:00:da:e1;CMTS-MAC=00:17:10:86:5d:1b;CM-QOS=1.1;CM-VER=3.0;


Power surge forced a reboot about 30 mins ago.

Expert

Re: SB6190 - Austin TX - High uncorrectable codewords on one channel;

I will guess they figured out what they did wrong and fixed it.

 

Participant

Re: SB6190 - Austin TX - High uncorrectable codewords on one channel;

it doesn't feel fixed. But, hopefully the storms stop happening and i can see if 12 hours uptime lasts.

Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel Locked
Connectivity StateOKOperational
Boot StateOKOperational
Configuration FileOK 
SecurityEnabledBPI+
DOCSIS Network Access EnabledAllowed 

 
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1Locked256QAM23597.00 MHz3.70 dBmV38.98 dB00
2Locked256QAM2471.00 MHz5.10 dBmV40.37 dB00
3Locked256QAM3477.00 MHz5.30 dBmV40.95 dB00
4Locked256QAM4483.00 MHz5.20 dBmV40.37 dB00
5Locked256QAM5489.00 MHz5.00 dBmV40.37 dB00
6Locked256QAM6495.00 MHz4.90 dBmV40.95 dB00
7Locked256QAM7501.00 MHz4.80 dBmV40.37 dB00
8Locked256QAM8507.00 MHz5.00 dBmV40.95 dB00
9Locked256QAM9513.00 MHz4.50 dBmV40.95 dB00
10Locked256QAM10519.00 MHz4.80 dBmV40.95 dB00
11Locked256QAM11525.00 MHz4.50 dBmV40.37 dB00
12Locked256QAM12531.00 MHz4.60 dBmV40.37 dB00
13Locked256QAM13537.00 MHz4.70 dBmV40.37 dB00
14Locked256QAM14543.00 MHz4.10 dBmV40.37 dB80
15Locked256QAM15549.00 MHz4.60 dBmV40.95 dB70
16Locked256QAM16555.00 MHz4.00 dBmV38.98 dB50
17Locked256QAM17561.00 MHz4.20 dBmV40.37 dB50
18Locked256QAM18567.00 MHz4.20 dBmV40.37 dB70
19Locked256QAM19573.00 MHz3.90 dBmV40.95 dB50
20Locked256QAM20579.00 MHz4.20 dBmV40.95 dB90
21Locked256QAM21585.00 MHz3.80 dBmV40.37 dB00
22Locked256QAM22591.00 MHz3.60 dBmV40.37 dB00
23Locked256QAM1465.00 MHz5.20 dBmV40.95 dB00
24Locked256QAM24603.00 MHz3.70 dBmV40.37 dB00

 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA65120 kSym/s24.20 MHz42.50 dBmV
2LockedATDMA82560 kSym/s37.00 MHz42.50 dBmV
3LockedATDMA75120 kSym/s30.60 MHz42.50 dBmV
4LockedTDMA52560 kSym/s19.40 MHz41.25 dBmV


 

Current System Time: Tue Jun 28 22:54:27 2016



Highlighted
Participant

Re: SB6190 - Austin TX - High uncorrectable codewords on one channel;

I'm just going to say, it looks like this has been stable for a few days now.

My correctables are in just double digits, and no uncorrectables, staying at 24 downstream channels too.

Power levels look jacked, but that's probably a line issue.

To TWC:

It's pretty backwards for yoru community to have more useful information than yoru tier 3. I'm assuming it's because you don't train them to troubleshoot this sort of issue. I wish whoever fixed this had the decency to own up to what was wrong, because it didn't get fixed until i made a forum post after 3 years of calling you guys complaining and paying $200/mo.

You're failing from a customer service perspective, and you're going to lose the monopoly very soon.

Expert

Re: SB6190 - Austin TX - High uncorrectable codewords on one channel;

Sig levels are fine, error/ s/n is good.

 

 But sorry, no bets on if or what was fixed

Participant

Re: SB6190 - Austin TX - High uncorrectable codewords on one channel;

Startup Procedure

ProcedureStatusComment
Acquire Downstream Channel Locked
Connectivity StateOKOperational
Boot StateOKOperational
Configuration FileOK 
SecurityEnabledBPI+
DOCSIS Network Access EnabledAllowed 

 

 
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1Locked256QAM15549.00 MHz3.90 dBmV40.95 dB40
2Locked256QAM2471.00 MHz4.50 dBmV40.95 dB00
3Locked256QAM3477.00 MHz4.60 dBmV40.37 dB00
4Locked256QAM4483.00 MHz4.50 dBmV40.37 dB00
5Locked256QAM5489.00 MHz4.40 dBmV40.37 dB00
6Locked256QAM6495.00 MHz4.40 dBmV40.37 dB00
7Locked256QAM7501.00 MHz4.10 dBmV40.37 dB00
8Locked256QAM8507.00 MHz4.30 dBmV40.95 dB00
9Locked256QAM9513.00 MHz3.70 dBmV40.95 dB00
10Locked256QAM10519.00 MHz4.10 dBmV40.37 dB00
11Locked256QAM11525.00 MHz3.80 dBmV40.95 dB00
12Locked256QAM12531.00 MHz3.80 dBmV40.95 dB00
13Locked256QAM13537.00 MHz4.00 dBmV40.37 dB00
14Locked256QAM14543.00 MHz3.40 dBmV40.37 dB00
15Locked256QAM1465.00 MHz4.40 dBmV40.37 dB00
16Locked256QAM16555.00 MHz3.40 dBmV40.37 dB70

 

Back to trying to use 16 downstream channels instead of 24.

Even after a pushpin factory default reset;

Time Priority Description
Thu Jan 01 00:02:18 19703No Ranging Response received - T3 time-out;CM-MAC=d4:0a:a9:00:da:e1;CMTS-MAC=00:17:10:86:5d:1b;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 14 03:43:51 20165TCS Partial Service;CM-MAC=d4:0a:a9:00:da:e1;CMTS-MAC=00:17:10:86:5d:1b;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 14 03:44:43 20163No Ranging Response received - T3 time-out;CM-MAC=d4:0a:a9:00:da:e1;CMTS-MAC=00:17:10:86:5d:1b;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 14 22:20:15 20165TCS Partial Service;CM-MAC=d4:0a:a9:00:da:e1;CMTS-MAC=00:17:10:86:5d:1b;CM-QOS=1.1;CM-VER=3.0;


How does the mdoem determine what mode to go into as far as downstream channels? What is making it think 16 today, when it was thinkign 24 last week?