I recently had tons of uncorrected errors, and very high upstream power levels (50+ dBmV). I found a bad splitter and replaced it, which dropped the upstream power to 40 dBmV and got rid of most of the uncorrected errors. But I'm still seeing some, and not sure where to continue chasing this down.
Here's what my modem says for connection stats:
| Acquire Downstream Channel |
531000000 Hz |
Locked |
| Upstream Connection |
OK |
Operational |
| Boot State |
OK |
Operational |
| Configuration File |
OK |
| Security |
Enabled |
BPI+ |
|
|
|
| System Up Time |
2 days 18h:01m:22s |
| Network Access |
Allowed |
|
| Downstream Bonded Channels |
|
| Channel |
Lock Status |
Modulation |
Channel ID |
Freq. (MHz) |
Pwr (dBmV) |
SNR (dB) |
Corrected |
Uncorrected |
| 1 |
Locked |
QAM256 |
20 |
531.0 |
2.1 |
42.6 |
321 |
1 |
| 2 |
Locked |
QAM256 |
13 |
489.0 |
2.3 |
43.4 |
1035 |
204 |
| 3 |
Locked |
QAM256 |
14 |
495.0 |
2.3 |
43.6 |
420 |
99 |
| 4 |
Locked |
QAM256 |
15 |
501.0 |
2.2 |
43.6 |
821 |
56 |
| 5 |
Locked |
QAM256 |
16 |
507.0 |
2.1 |
43.5 |
282 |
0 |
| 6 |
Locked |
QAM256 |
17 |
513.0 |
1.9 |
43.4 |
597 |
21 |
| 7 |
Locked |
QAM256 |
18 |
519.0 |
1.9 |
43.5 |
444 |
24 |
| 8 |
Locked |
QAM256 |
19 |
525.0 |
1.9 |
43.2 |
668 |
55 |
| 9 |
Locked |
QAM256 |
21 |
537.0 |
2.4 |
43.0 |
632 |
9 |
| 10 |
Locked |
QAM256 |
22 |
543.0 |
2.3 |
43.5 |
316 |
26 |
| 11 |
Locked |
QAM256 |
23 |
549.0 |
2.3 |
43.6 |
482 |
8 |
| 12 |
Locked |
QAM256 |
24 |
555.0 |
2.0 |
43.5 |
287 |
0 |
| 13 |
Locked |
QAM256 |
25 |
561.0 |
2.0 |
43.5 |
376 |
0 |
| 14 |
Locked |
QAM256 |
26 |
567.0 |
1.6 |
41.9 |
243 |
1 |
| 15 |
Locked |
QAM256 |
27 |
573.0 |
1.6 |
42.3 |
492 |
9 |
| 16 |
Locked |
QAM256 |
28 |
579.0 |
1.5 |
43.0 |
256 |
0 |
| 17 |
Locked |
QAM256 |
29 |
585.0 |
1.5 |
38.8 |
397 |
6 |
| 18 |
Locked |
QAM256 |
30 |
591.0 |
1.5 |
41.3 |
284 |
0 |
| 19 |
Locked |
QAM256 |
31 |
597.0 |
1.7 |
42.4 |
375 |
0 |
| 20 |
Locked |
QAM256 |
32 |
603.0 |
1.5 |
40.1 |
246 |
0 |
| 21 |
Locked |
QAM256 |
33 |
609.0 |
1.2 |
41.7 |
284 |
0 |
| 22 |
Locked |
QAM256 |
34 |
615.0 |
0.7 |
39.6 |
247 |
0 |
| 23 |
Locked |
QAM256 |
35 |
621.0 |
0.8 |
32.8 |
869 |
0 |
| 24 |
Locked |
QAM256 |
36 |
627.0 |
0.6 |
30.7 |
1667992 |
147733 |
| 25 |
Locked |
QAM256 |
37 |
633.0 |
0.7 |
34.6 |
240 |
0 |
| 26 |
Locked |
QAM256 |
38 |
639.0 |
0.5 |
37.7 |
215 |
0 |
| 27 |
Locked |
QAM256 |
39 |
645.0 |
0.7 |
42.6 |
364 |
0 |
| 28 |
Locked |
QAM256 |
40 |
651.0 |
0.9 |
42.8 |
200 |
0 |
| 29 |
Locked |
QAM256 |
41 |
657.0 |
1.0 |
42.9 |
266 |
0 |
| 30 |
Locked |
QAM256 |
42 |
663.0 |
0.9 |
42.9 |
562 |
111 |
| 31 |
Locked |
QAM256 |
43 |
669.0 |
0.7 |
42.7 |
6464 |
19329 |
| 32 |
Locked |
QAM256 |
44 |
675.0 |
0.2 |
41.9 |
1886 |
3630 |
| 33 |
Locked |
OFDM PLC |
193 |
957.0 |
-7.4 |
37.9 |
-2132881031 |
11094 |
|
|
|
| Channel |
Lock Status |
Channel Type |
Channel ID |
Symb. Rate (Ksym/sec) |
Freq. (MHz) |
Pwr (dBmV) |
| 1 |
Locked |
SC-QAM |
17 |
5120 |
16.4 |
42.0 |
| 2 |
Locked |
SC-QAM |
18 |
5120 |
22.8 |
42.0 |
| 3 |
Locked |
SC-QAM |
19 |
5120 |
29.2 |
42.0 |
| 4 |
Locked |
SC-QAM |
20 |
5120 |
35.6 |
42.3 |
|
So my questions:
- Upstream channels look good now, right?
- Downstream channel 24 has poor SNR and lots of errors, what to look into that would cause just one channel to be bad?
- Downstream channel 31 has good SNR and power but still accumulating errors, what to look into for that?
- Should I worry about the other downstream channels that are only accumulating ones or tens of uncorrected errors per day? I'm not sure why channels with seemingly good SNR and power would be accumulating errors at all.
user_eey3jo
Visitor
•
2 Messages
2 days ago
I'm also still seeing a few critical error logs in the modem per day, though that is down from many per day before I replaced the bad splitter. Specifically I'm seeing 1-2 "Started Unicast Maintenance Ranging - No Response received - T3 time-out" and 1-2 "UCD invalid or channel unusable" per day, and more rarely some warnings like "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW" and "Dynamic Range Window violation".
0
0
XfinityJustinM
Official Employee
•
628 Messages
8 hours ago
Greetings @user_eey3jo, I see you have really put your thinking cap on. Your head is in the right space, but it would be pretty hard to narrow this down. Although you replaced the splitter there could still be some issues with physical line itself, but you've at least taken one huge step forward. We have a few tools that may help us get to the bottom of things. If all else fails we can always have a technician sent out to take a good peak under the hood. If you could send our team a direct message with your full name, the name listed on the account (if different), and the service address associated with your account, I'd be more than happy to look into this for you.
To send a "Direct Message" to Xfinity Support:
Click "Sign In" if necessary
Click the "Direct Messaging" icon
Click the "New message" (pencil and paper) icon
The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there
- As you are typing a drop-down list appears. Select "Xfinity Support" from that list
- An "Xfinity Support" graphic replaces the "To:" line
Type your message in the text area near the bottom of the window
Press Enter to send it.
0
0