Billy was in the neighborhood Friday all day, I spoke to him when he was working on the next pole downstream from me. A neighbor two doors up was showing only one upstream channel locked. He found a bad connection somewhere at the pole and something that looked burnt, which he replaced, then remotely rebooted their modem and it locked 4 upstream channels. He checked from pole to pole for issues all day through the neighborhood on my node.
During the morning while he was working, I did see a series of T3 and T4 timeouts in the span of a few minutes, which I assumed was due to Billy disconnecting things, so we eventually rebooted the modem to get our home network working again, about 10:30 AM that morning.
Interestingly, from that point on, the modem held the same original consecutive 8 DS channels with no switching to other channels and no lost DS channels, for 36 hours, with only one T3 Timeout about 3 AM early Saturday morn. Then Saturday night about 10:30 PM, we had the same Lost MDD/Loss of Sync/T3/T4-Timeouts/T4-Reboot we have been getting mostly at that same time period each night.
So that auto-reboot from T4 was last night at 10:30 PM.... now 12 hours later we still have the original consecutive DS channels. So something was fixed it seems, as far as the DS channel switching issues..... but we still are seeing the T4 reboots. Hmmm...
Billy did say, and this may be important, that they "switched out" or "changed out the node," which i took to mean they replaced the node hardware, a couple of weeks or a few weeks ago. They found at the headend that where the some cable or cables go INTO the fiber optic there, that the nut that attaches them was stripped and so it is kind of jury-rigged on. He said the headend folks were scheduled to replace that this Tuesday during 3rd shift while most users are asleep. I'm hoping that has a positive effect on the T4 reboot issue. We will see.
This is what my signal looks like now at 10:30 AM Sunday, 12 hours after the auto reboot from T4 Timeout last night (12 hours ago). This is the same as what it looked like for 36 hours after Billy was on the pole up the street as well, prior to that T4 reboot last night.
Channel ID | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | |
Frequency | 507000000 Hz | 513000000 Hz | 519000000 Hz | 525000000 Hz | 531000000 Hz | 537000000 Hz | 543000000 Hz | 549000000 Hz | |
Signal to Noise Ratio | 37 dB | 38 dB | 38 dB | 38 dB | 38 dB | 38 dB | 39 dB | 38 dB | |
Downstream Modulation | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | |
Power Level
| -2 dBmV | -2 dBmV | -2 dBmV | -2 dBmV | -2 dBmV | -2 dBmV | -2 dBmV | -1 dBmV |
Channel ID | 2 | 4 | 3 | 1 |
Frequency | 24200000 Hz | 37000000 Hz | 30600000 Hz | 19400000 Hz |
Ranging Service ID | 5217 | 5217 | 5217 | 5217 |
Symbol Rate | 5.120 Msym/sec | 2.560 Msym/sec | 5.120 Msym/sec | 2.560 Msym/sec |
Power Level | 46 dBmV | 48 dBmV | 46 dBmV | 44 dBmV |
Upstream Modulation | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [3] 16QAM | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [2] 16QAM |
Ranging Status | Success | Success | Success | Success |
Channel ID | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 |
Total Unerrored Codewords | 1970267542 | 1969459266 | 1969467889 | 1969476516 | 1969452587 | 1969448813 | 1969452432 | 1969451116 |
Total Correctable Codewords | 1 | 0 | 1 | 0 | 16 | 11 | 11 | 19 |
Total Uncorrectable Codewords | 596 | 546 | 556 | 1486 | 640 | 1459 | 633 | 1507 |
Oh well..... now it's switched out 525 MHz for 609 MHz. Still have 8 channels but no longer consecutive.
Channel ID | 9 | 10 | 11 | 13 | 14 | 15 | 16 | 26 | |
Frequency | 507000000 Hz | 513000000 Hz | 519000000 Hz | 531000000 Hz | 537000000 Hz | 543000000 Hz | 549000000 Hz | 609000000 Hz | |
Signal to Noise Ratio | 38 dB | 38 dB | 38 dB | 38 dB | 38 dB | 38 dB | 38 dB | 39 dB | |
Downstream Modulation | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | |
Power Level
| -3 dBmV | -3 dBmV | -3 dBmV | -3 dBmV | -2 dBmV | -2 dBmV | -2 dBmV | 0 dBmV |
Channel ID | 2 | 4 | 3 | 1 |
Frequency | 24200000 Hz | 37000000 Hz | 30600000 Hz | 19400000 Hz |
Ranging Service ID | 5217 | 5217 | 5217 | 5217 |
Symbol Rate | 5.120 Msym/sec | 2.560 Msym/sec | 5.120 Msym/sec | 2.560 Msym/sec |
Power Level | 46 dBmV | 48 dBmV | 46 dBmV | 44 dBmV |
Upstream Modulation | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [3] 16QAM | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [2] 16QAM |
Ranging Status | Success | Success | Success | Success |
Channel ID | 9 | 10 | 11 | 13 | 14 | 15 | 16 | 26 |
Total Unerrored Codewords | 2189988376 | 2189180102 | 2189188716 | 2153961810 | 2153926676 | 2153917631 | 2153911438 | 2153970805 |
Total Correctable Codewords | 3 | 0 | 9 | 20 | 33 | 23 | 27 | 33 |
Total Uncorrectable Codewords | 596 | 546 | 556 | 2942 | 1216 | 2871 | 2177 | 2966 |
Firber optics won't cause RF ingress issues, they sure could cause any sort of T1-T6 errors and resets.
Did you ask him why there are #6 solid copper wires jumping around all the neighborhood amplifiers?It's VERY unusual to see that.... and it starts creating noise junctions and rf rectification for yet more dissimilar metals on the poles.
The next issue is why the CMTS jumping your modems channels all the way up to CH 26 rather than CH 17?
That spread is outside the modems published 96 mHz acceptance bandwidth.
I suspect the skipped channels have extremely high levels of ingress on them which modems don't tolerate well.
Latest design 24-32ch "full bandwidth" 108-1004 mHz designs will be more resilient to what's on skipped channels
I dunno why the channels switch up so high, but I also don't know if there is a way for them to control that. Do you know?
I forgot to ask about the copper jumper wires. I'll try asking next week.
I will eventually have to buy a newer modem regardless. I'm wondering if a 16-channel is going to be useful once Spectrum moves this area to 24 or 32 channels. I think we may be up to 24 already.
As you can see, the modem continues to drop 519 and 525 MHz:
Channel ID | 9 | 10 | 13 | 14 | 15 | 16 | 29 | 30 | |
Frequency | 507000000 Hz | 513000000 Hz | 531000000 Hz | 537000000 Hz | 543000000 Hz | 549000000 Hz | 627000000 Hz | 633000000 Hz | |
Signal to Noise Ratio | 38 dB | 39 dB | 39 dB | 39 dB | 38 dB | 38 dB | 39 dB | 39 dB | |
Downstream Modulation | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | |
Power Level
| -2 dBmV | -1 dBmV | -1 dBmV | -1 dBmV | -1 dBmV | 0 dBmV | 0 dBmV | 0 dBmV |
Channel ID | 2 | 4 | 3 | 1 |
Frequency | 24200000 Hz | 37000000 Hz | 30600000 Hz | 19400000 Hz |
Ranging Service ID | 5217 | 5217 | 5217 | 5217 |
Symbol Rate | 5.120 Msym/sec | 2.560 Msym/sec | 5.120 Msym/sec | 2.560 Msym/sec |
Power Level | 46 dBmV | 48 dBmV | 47 dBmV | 44 dBmV |
Upstream Modulation | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [3] 16QAM | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [2] 16QAM |
Ranging Status | Success | Success | Success | Success |
Channel ID | 9 | 10 | 13 | 14 | 15 | 16 | 29 | 30 |
Total Unerrored Codewords | 4059940039 | 4059131766 | 4042665059 | 4007453328 | 4007392876 | 4007375164 | 4007370210 | 3941412733 |
Total Correctable Codewords | 3 | 0 | 26 | 37 | 45 | 28 | 94 | 114 |
Total Uncorrectable Codewords | 596 | 546 | 1231 | 4486 | 1820 | 3525 | 2799 | 5940 |
You're sitting on 32 channels right norw and ch 14 &30 have ingress looking at the uncorrected counts...
It's also operating well outside MFG's acceptance bandwidth of 96 mhz
That CMTS is wrong as well, if anything is should be doing a pair of 4 channel banks. This is a tier 4 issue complicated by the ingress
If you've got friends on this node, see what their channel lineups look like, that may help narrow it down to see how widespread the ingress is.
I only have one neighbor up the street whose modem I can look at, but her's is a leased 16-channel wi-fi gateway which isn't having any issues, unlike my 8-channel modem.
The late night repair work must have been done overnight, as the logs show maintenance-type interruption about 4:30 AM. Sadly, it didn't fix anything for me. Around 9:30 PM I had another spell of Lost MDD/Lossof Sync/T3-T4-Timeout-reboot, as I have been getting. Tonight the T4 reboot left me with no Internet access and I had to do a power reset on top of it. Just aggravated now....
TimePriorityCodeMessage
Aug 10 2017 20:23:55 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Aug 10 2017 20:23:55 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:17 | 6-Notice | N/A | Cable Modem Reboot due to power reset ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
Aug 10 2017 20:20:44 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Aug 10 2017 20:20:44 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:17 | 6-Notice | N/A | Cable Modem Reboot due to T4 timeout ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
Aug 10 2017 20:19:53 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Aug 10 2017 20:19:48 | 5-Warning | T202.0 | Lost MDD Timeout;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Aug 10 2017 20:19:44 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Aug 10 2017 20:19:24 | 3-Critical | T05.0 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Aug 10 2017 20:05:19 | 5-Warning | T202.0 | Lost MDD Timeout;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Aug 10 2017 20:05:19 | 5-Warning | N/A | DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Aug 09 2017 04:31:04 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Aug 09 2017 04:31:04 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:22:50 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:17 | 6-Notice | N/A | Cable Modem Reboot due to T4 timeout ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
Aug 09 2017 04:07:41 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Aug 09 2017 04:07:39 | 5-Warning | T202.0 | Lost MDD Timeout;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Aug 09 2017 04:07:38 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
Aug 09 2017 04:07:37 | 5-Warning | T202.0 | Lost MDD Timeout;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0; |
....and while I have been holding the original consecutive 8 channels for a while recently, now, after only 2 hours after reboot, I've already skipped off 519 MHz again.
Channel ID | 9 | 10 | 12 | 13 | 14 | 15 | 16 | 17 | |
Frequency | 507000000 Hz | 513000000 Hz | 525000000 Hz | 531000000 Hz | 537000000 Hz | 543000000 Hz | 549000000 Hz | 555000000 Hz | |
Signal to Noise Ratio | 38 dB | 38 dB | 39 dB | 38 dB | 38 dB | 38 dB | 38 dB | 39 dB | |
Downstream Modulation | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | |
Power Level
| -1 dBmV | -1 dBmV | -1 dBmV | -1 dBmV | 0 dBmV | 0 dBmV | 0 dBmV | 0 dBmV |
Channel ID | 2 | 4 | 3 | 1 |
Frequency | 24200000 Hz | 37000000 Hz | 30600000 Hz | 19400000 Hz |
Ranging Service ID | 4731 | 4731 | 4731 | 4731 |
Symbol Rate | 5.120 Msym/sec | 2.560 Msym/sec | 5.120 Msym/sec | 2.560 Msym/sec |
Power Level | 46 dBmV | 48 dBmV | 47 dBmV | 46 dBmV |
Upstream Modulation | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [3] 16QAM | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [2] 16QAM |
Ranging Status | Success | Success | Success | Success |
Channel ID | 9 | 10 | 12 | 13 | 14 | 15 | 16 | 17 |
Total Unerrored Codewords | 431544762 | 430705860 | 326892893 | 326922861 | 326912634 | 326872308 | 326869972 | 326900692 |
Total Correctable Codewords | 0 | 2 | 14 | 20 | 30 | 27 | 34 | 31 |
Total Uncorrectable Codewords | 516 | 1454 | 1162 | 3024 | 1268 | 2222 | 2177 | 2164 |
You're internet only, no cable tv, right?
Do a channel scan on an ATSC tv with no antenna and see if it gets anything.. Then try a 2" piece of wire (center of rg6 or 59) in the connector...
There is no ch 21-22-23 listed for your area, let's see what channels are strong there or if the database is wrong.
Nearest 22 is 38 miles away and extremely weak.
I have "Starter TV" and 60/6 internet.
Signal tonight after 26 hours uptime on modem:
Channel ID | 9 | 10 | 13 | 17 | 27 | 28 | 30 | 31 | |
Frequency | 507000000 Hz | 513000000 Hz | 531000000 Hz | 555000000 Hz | 615000000 Hz | 621000000 Hz | 633000000 Hz | 639000000 Hz | |
Signal to Noise Ratio | 38 dB | 38 dB | 39 dB | 39 dB | 38 dB | 38 dB | 38 dB | 39 dB | |
Downstream Modulation | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | |
Power Level
| -1 dBmV | -1 dBmV | -1 dBmV | -1 dBmV | 0 dBmV | 0 dBmV | 0 dBmV | 0 dBmV |
Channel ID | 2 | 4 | 3 | 1 |
Frequency | 24200000 Hz | 37000000 Hz | 30600000 Hz | 19400000 Hz |
Ranging Service ID | 4731 | 4731 | 4731 | 4731 |
Symbol Rate | 5.120 Msym/sec | 2.560 Msym/sec | 5.120 Msym/sec | 2.560 Msym/sec |
Power Level | 46 dBmV | 48 dBmV | 47 dBmV | 46 dBmV |
Upstream Modulation | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [3] 16QAM | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [2] 16QAM |
Ranging Status | Success | Success | Success | Success |
Channel ID | 9 | 10 | 13 | 17 | 27 | 28 | 30 | 31 |
Total Unerrored Codewords | 4288101822 | 4287262921 | 4112209963 | 4103545471 | 4103513123 | 4035714384 | 4035840231 | 4035844081 |
Total Correctable Codewords | 2 | 4 | 38 | 45 | 62 | 241 | 6135 | 1504 |
Total Uncorrectable Codewords | 516 | 1454 | 2672 | 6437 | 3516 | 8231 | 6432 | 7391 |
Your tv is connected to the cable box by HDMI cable, not coax, correct?
Nothing is on the antenna connector, set the setup for an antenna connection to see if there are really strong channels that get in with nothing connected. Then try a 2" piece of wire like a bent open paperclip.Then try a 5" wire. You'll probably need to compare them with what's listed on tvfool to find the actual channels rather than the aliases that some are still using... Need to see if yo u pick up a 22 or 23 which are on 519 and 525 mHz