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.
Downstream Bonding Channel Value | 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 | The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading |
| -2 dBmV | -2 dBmV | -2 dBmV | -2 dBmV | -2 dBmV | -2 dBmV | -2 dBmV | -1 dBmV |
Upstream Bonding Channel Value | 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 |
Signal Stats (Codewords)Bonding Channel Value | 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 |
