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

[MsRaye]

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

[chaste]

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

[MsRaye]

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

[chaste]

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.

[WhyIrishMan]

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

Procedure	Status	Comment
Acquire Downstream Channel		Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Configuration File	OK
Security	Enabled	BPI+
DOCSIS Network Access Enabled	Allowed

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Corrected	Uncorrectables
1	Locked	256QAM	23	597.00 MHz	3.80 dBmV	38.98 dB	0	0
2	Locked	256QAM	2	471.00 MHz	5.00 dBmV	40.95 dB	0	0
3	Locked	256QAM	3	477.00 MHz	5.30 dBmV	40.95 dB	0	0
4	Locked	256QAM	4	483.00 MHz	5.20 dBmV	40.95 dB	0	0
5	Locked	256QAM	5	489.00 MHz	4.90 dBmV	40.37 dB	0	0
6	Locked	256QAM	6	495.00 MHz	4.90 dBmV	40.95 dB	0	0
7	Locked	256QAM	7	501.00 MHz	4.80 dBmV	40.37 dB	0	0
8	Locked	256QAM	8	507.00 MHz	5.10 dBmV	40.37 dB	0	0
9	Locked	256QAM	9	513.00 MHz	4.50 dBmV	40.37 dB	0	0
10	Locked	256QAM	10	519.00 MHz	4.90 dBmV	40.95 dB	0	0
11	Locked	256QAM	11	525.00 MHz	4.60 dBmV	40.37 dB	0	0
12	Locked	256QAM	12	531.00 MHz	4.60 dBmV	40.37 dB	0	0
13	Locked	256QAM	13	537.00 MHz	4.70 dBmV	40.37 dB	0	0
14	Locked	256QAM	14	543.00 MHz	4.10 dBmV	40.95 dB	8	0
15	Locked	256QAM	15	549.00 MHz	4.60 dBmV	40.37 dB	3	0
16	Locked	256QAM	16	555.00 MHz	4.00 dBmV	38.98 dB	5	0
17	Locked	256QAM	17	561.00 MHz	4.10 dBmV	38.98 dB	5	0
18	Locked	256QAM	18	567.00 MHz	4.20 dBmV	40.37 dB	7	0
19	Locked	256QAM	19	573.00 MHz	3.90 dBmV	40.37 dB	0	0
20	Locked	256QAM	20	579.00 MHz	4.10 dBmV	40.37 dB	0	0
21	Locked	256QAM	21	585.00 MHz	3.90 dBmV	40.37 dB	0	0
22	Locked	256QAM	22	591.00 MHz	3.70 dBmV	40.37 dB	0	0
23	Locked	256QAM	1	465.00 MHz	5.10 dBmV	40.37 dB	0	0
24	Locked	256QAM	24	603.00 MHz	3.80 dBmV	40.37 dB	0	0

Upstream Bonded Channels

Channel	Lock Status	US Channel Type	Channel ID	Symbol Rate	Frequency	Power
1	Locked	ATDMA	6	5120 kSym/s	24.20 MHz	42.50 dBmV
2	Locked	ATDMA	8	2560 kSym/s	37.00 MHz	42.50 dBmV
3	Locked	ATDMA	7	5120 kSym/s	30.60 MHz	42.50 dBmV
4	Locked	TDMA	5	2560 kSym/s	19.40 MHz	41.25 dBmV

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

Thu Jan 01 00:02:16 1970	3	No 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 2016	5	TCS 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 2016	3	No 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 2016	5	TCS 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 2016	3	No 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 2016	5	TCS 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.

[MsRaye]

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

[WhyIrishMan]

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

Startup Procedure

Procedure	Status	Comment
Acquire Downstream Channel		Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Configuration File	OK
Security	Enabled	BPI+
DOCSIS Network Access Enabled	Allowed

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Corrected	Uncorrectables
1	Locked	256QAM	23	597.00 MHz	3.70 dBmV	38.98 dB	0	0
2	Locked	256QAM	2	471.00 MHz	5.10 dBmV	40.37 dB	0	0
3	Locked	256QAM	3	477.00 MHz	5.30 dBmV	40.95 dB	0	0
4	Locked	256QAM	4	483.00 MHz	5.20 dBmV	40.37 dB	0	0
5	Locked	256QAM	5	489.00 MHz	5.00 dBmV	40.37 dB	0	0
6	Locked	256QAM	6	495.00 MHz	4.90 dBmV	40.95 dB	0	0
7	Locked	256QAM	7	501.00 MHz	4.80 dBmV	40.37 dB	0	0
8	Locked	256QAM	8	507.00 MHz	5.00 dBmV	40.95 dB	0	0
9	Locked	256QAM	9	513.00 MHz	4.50 dBmV	40.95 dB	0	0
10	Locked	256QAM	10	519.00 MHz	4.80 dBmV	40.95 dB	0	0
11	Locked	256QAM	11	525.00 MHz	4.50 dBmV	40.37 dB	0	0
12	Locked	256QAM	12	531.00 MHz	4.60 dBmV	40.37 dB	0	0
13	Locked	256QAM	13	537.00 MHz	4.70 dBmV	40.37 dB	0	0
14	Locked	256QAM	14	543.00 MHz	4.10 dBmV	40.37 dB	8	0
15	Locked	256QAM	15	549.00 MHz	4.60 dBmV	40.95 dB	7	0
16	Locked	256QAM	16	555.00 MHz	4.00 dBmV	38.98 dB	5	0
17	Locked	256QAM	17	561.00 MHz	4.20 dBmV	40.37 dB	5	0
18	Locked	256QAM	18	567.00 MHz	4.20 dBmV	40.37 dB	7	0
19	Locked	256QAM	19	573.00 MHz	3.90 dBmV	40.95 dB	5	0
20	Locked	256QAM	20	579.00 MHz	4.20 dBmV	40.95 dB	9	0
21	Locked	256QAM	21	585.00 MHz	3.80 dBmV	40.37 dB	0	0
22	Locked	256QAM	22	591.00 MHz	3.60 dBmV	40.37 dB	0	0
23	Locked	256QAM	1	465.00 MHz	5.20 dBmV	40.95 dB	0	0
24	Locked	256QAM	24	603.00 MHz	3.70 dBmV	40.37 dB	0	0

Upstream Bonded Channels

Channel	Lock Status	US Channel Type	Channel ID	Symbol Rate	Frequency	Power
1	Locked	ATDMA	6	5120 kSym/s	24.20 MHz	42.50 dBmV
2	Locked	ATDMA	8	2560 kSym/s	37.00 MHz	42.50 dBmV
3	Locked	ATDMA	7	5120 kSym/s	30.60 MHz	42.50 dBmV
4	Locked	TDMA	5	2560 kSym/s	19.40 MHz	41.25 dBmV

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

[WhyIrishMan]

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.

[MsRaye]

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

 But sorry, no bets on if or what was fixed

[WhyIrishMan]

Startup Procedure

Procedure	Status	Comment
Acquire Downstream Channel		Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Configuration File	OK
Security	Enabled	BPI+
DOCSIS Network Access Enabled	Allowed

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Corrected	Uncorrectables
1	Locked	256QAM	15	549.00 MHz	3.90 dBmV	40.95 dB	4	0
2	Locked	256QAM	2	471.00 MHz	4.50 dBmV	40.95 dB	0	0
3	Locked	256QAM	3	477.00 MHz	4.60 dBmV	40.37 dB	0	0
4	Locked	256QAM	4	483.00 MHz	4.50 dBmV	40.37 dB	0	0
5	Locked	256QAM	5	489.00 MHz	4.40 dBmV	40.37 dB	0	0
6	Locked	256QAM	6	495.00 MHz	4.40 dBmV	40.37 dB	0	0
7	Locked	256QAM	7	501.00 MHz	4.10 dBmV	40.37 dB	0	0
8	Locked	256QAM	8	507.00 MHz	4.30 dBmV	40.95 dB	0	0
9	Locked	256QAM	9	513.00 MHz	3.70 dBmV	40.95 dB	0	0
10	Locked	256QAM	10	519.00 MHz	4.10 dBmV	40.37 dB	0	0
11	Locked	256QAM	11	525.00 MHz	3.80 dBmV	40.95 dB	0	0
12	Locked	256QAM	12	531.00 MHz	3.80 dBmV	40.95 dB	0	0
13	Locked	256QAM	13	537.00 MHz	4.00 dBmV	40.37 dB	0	0
14	Locked	256QAM	14	543.00 MHz	3.40 dBmV	40.37 dB	0	0
15	Locked	256QAM	1	465.00 MHz	4.40 dBmV	40.37 dB	0	0
16	Locked	256QAM	16	555.00 MHz	3.40 dBmV	40.37 dB	7	0

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 1970	3	No 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 2016	5	TCS 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 2016	3	No 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 2016	5	TCS 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?