Sharer

29501 seems to be struggling with certain channels... again.

Been having some intermittent rebooting of the modem for a while now... the usual stuff we tend to see as weather warms up here. Will paste a dump of the signal stats at the end of this. Forgive the format and any potential typos... doing this via the not-so-smart phone.

After recovering from tonight's outage (called in b/c it didn't recover after about 20 minutes, outage was reported by the system), downstream list was having a hard time locking on number 17 @ 555Mhz. The DS light kept blinking after coming back online, and that channel wasn't showing a lock for about 10 minutes. Watched it do this through a couple reboots... both soft and hard (haven't done the reset to defaults yet though). There is also the typical slight rise in power on the last upstream channel (#8 @ 36.8Mhz). It is typical behavior here that we have been wrangling with off and on for years now.

This weirdness with the 555Mhz DS channel is a new quirk... the upstream channel has been a problem child for years now. During hotter days or really foul weather and heavier traffic, the power level may start creeping up until it breaks 50, things get dicey, and it starts rebooting several times a day for a while and then clears up again. TWC was never able to truly stomp it out. Always the same symptoms, no matter how many modem swaps and new lines are run trying to rule out anything in the house being at fault. But this 555Mhz downstream lock issue is a new one.

Over the years, SNR has always been just over 39 on the DS side, with 3 to 10 dBmv peak strength during internet only. Occasionally it might go a few points negative strength when we were splitting off a feed for broadcast cable TV... but since going internet only with a dedicated line several years ago, pretty much stays on the positive side. Typically DS stats would be between 40/41 SNR with 3-6 dBmv for each channel in warmer weather. But after tonight's outage it was 42/43 SNR with around 9/10 dbmv.

Perhaps they finally replaced the failing distro box and signal is slightly over-driven now? (During one of the last tech visits, they couldn't move our line to a cleaner port--all potential candidates had MORE noise in the line than the current one).

Any thoughts on this behavior? Should I watch this closer and perhaps look into scheduling a truck roll? Note the errors that have accumulated between snapshots after about an hour of uptime while our network was idle. No reboots between the snapshots, and no new log entries since it recovered and was flooded with SYNCH errors because there was no signal to latch for over 40 minutes.

Procedure Status Comment
Acquire Downstream Channel 645000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode IPv6 Only ipv6Only(1)

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 32 645000000 Hz 9 dBmV 42.7 dB 4 0
2 Locked QAM256 18 561000000 Hz 9 dBmV 43.7 dB 0 0
3 Locked QAM256 19 567000000 Hz 8.6 dBmV 43.5 dB 0 0
4 Locked QAM256 20 573000000 Hz 9 dBmV 43.3 dB 1 0
5 Locked QAM256 21 579000000 Hz 9.8 dBmV 43.8 dB 1 0
6 Locked QAM256 22 585000000 Hz 9.2 dBmV 43.1 dB 4 0
7 Locked QAM256 23 591000000 Hz 9.1 dBmV 43.2 dB 0 0
8 Locked QAM256 24 597000000 Hz 10 dBmV 43.6 dB 0 0
9 Locked QAM256 25 603000000 Hz 9.6 dBmV 43 dB 0 0
10 Locked QAM256 26 609000000 Hz 9.2 dBmV 42.9 dB 2 0
11 Locked QAM256 27 615000000 Hz 9.7 dBmV 42.5 dB 1 0
12 Locked QAM256 28 621000000 Hz 9.8 dBmV 42.9 dB 3 0
13 Locked QAM256 29 627000000 Hz 8.9 dBmV 42.5 dB 1 0
14 Locked QAM256 30 633000000 Hz 9.5 dBmV 42.7 dB 0 0
15 Locked QAM256 31 639000000 Hz 9.5 dBmV 42.7 dB 4 0
16 Locked QAM256 17 555000000 Hz 8.9 dBmV 43.9 dB 0 0

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 6 5120 Ksym/sec 24000000 Hz 43.3 dBmV
2 Locked TDMA 5 2560 Ksym/sec 19200000 Hz 43.3 dBmV
3 Locked ATDMA 7 5120 Ksym/sec 30400000 Hz 43.3 dBmV
4 Locked ATDMA 8 5120 Ksym/sec 36800000 Hz 44.5 dBmV

Procedure Status Comment
Acquire Downstream Channel 645000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode IPv6 Only ipv6Only(1)

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 32 645000000 Hz 8.9 dBmV 42.9 dB 438 679
2 Locked QAM256 18 561000000 Hz 9 dBmV 43.9 dB 469 632
3 Locked QAM256 19 567000000 Hz 8.5 dBmV 43.7 dB 474 709
4 Locked QAM256 20 573000000 Hz 8.9 dBmV 43.5 dB 362 661
5 Locked QAM256 21 579000000 Hz 9.7 dBmV 44 dB 719 771
6 Locked QAM256 22 585000000 Hz 9.1 dBmV 43.3 dB 447 700
7 Locked QAM256 23 591000000 Hz 9.1 dBmV 43.5 dB 346 644
8 Locked QAM256 24 597000000 Hz 10 dBmV 43.8 dB 449 708
9 Locked QAM256 25 603000000 Hz 9.5 dBmV 43.3 dB 426 669
10 Locked QAM256 26 609000000 Hz 9.1 dBmV 43.2 dB 560 757
11 Locked QAM256 27 615000000 Hz 9.6 dBmV 42.6 dB 528 1073
12 Locked QAM256 28 621000000 Hz 9.7 dBmV 43.1 dB 358 681
13 Locked QAM256 29 627000000 Hz 8.9 dBmV 42.8 dB 469 706
14 Locked QAM256 30 633000000 Hz 9.4 dBmV 43 dB 299 680
15 Locked QAM256 31 639000000 Hz 9.4 dBmV 42.9 dB 363 661
16 Locked QAM256 17 555000000 Hz 8.8 dBmV 44 dB 570 875

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 6 5120 Ksym/sec 24000000 Hz 43.3 dBmV
2 Locked TDMA 5 2560 Ksym/sec 19200000 Hz 43.3 dBmV
3 Locked ATDMA 7 5120 Ksym/sec 30400000 Hz 43.3 dBmV
4 Locked ATDMA 8 5120 Ksym/sec 36800000 Hz 44.5 dBmV

Current System Time:Tue Apr 24 00:41:12 2018
4 REPLIES
Highlighted
Proven Sharer

Re: 29501 seems to be struggling with certain channels... again.

You shouldn't be seeing that type of erratic behavior.  If your neighbors are experiencing similar issues, then the problem probably lies in the infrastructure in your neighborhood.  A damange trunk line or faulty equipment is probably the cause.

 

Have you scheduled a field tech visit?  As long as you've made sure your home wiring is in good shape, any problem must lie elsewhere.

Proven Sharer

Re: 29501 seems to be struggling with certain channels... again.

Your numbers look good this time, all are within specs.  However, you should call Spectrum so they can look for errors received on the US at their CMTS server end. 

Like @dstoffa I am suspicious that the bucket truck crew will find an intermittent connection in the overhead plant near your home that wiggles in the wind and shifts the line levels enough to force new autoranging in both directions, or an amp or tap housing that sometimes fills with water.  BT,DT!

Sharer

Re: 29501 seems to be struggling with certain channels... again.

Just had a thought when talking to someone about the streaming plans...

...wonder if the broadcast trap could be impacting things?

IDK the details on the range it filters and whatnot, but remember they came out and put something on the line out in that green box when we cut off broadcast cable (we used the $15 deal for the basic locals for a while before going fully to OTA and streaming only).
Proven Sharer

Re: 29501 seems to be struggling with certain channels... again.


@RAIST5150wrote:
Just had a thought when talking to someone about the streaming plans...

...wonder if the broadcast trap could be impacting things?

IDK the details on the range it filters and whatnot, but remember they came out and put something on the line out in that green box when we cut off broadcast cable (we used the $15 deal for the basic locals for a while before going fully to OTA and streaming only).

That's a good point to remember when the next tech visits:  If Spectrum has switched to fully encrypted 256 QAM digital in your area, the legacy "basic broadcast trap" is no longer needed and should be discarded.  It can cause an intermittent signal loss when it is exposed to water.