4 Messages
Nighthawk CAX80 - Downstream power too low
Since getting this service two years ago my downstream power has always reported low, it wasn't until recently I've been experiencing outages intermittently and really poor connectivity.
Modem is a Nighthawk CAX80 with the latest firmware. Its in a spot in my office with good airflow.
I don't have any splitters and I have only one connection directly to the demarc outside my house connected via a coax coupler. I have checked the coupler that was installed at the house by the tech and I have even tried replacing with multiple new couplers and the results are the same.
I have contacted for support in the past and the technician wasn't helpful when I mentioned the low downstream power. I have scheduled for another tech to come out but short of replacing all the cables and couples I feel like this is on the ISP side. Not sure what else to do.
Here's an output of the latest logs from my modem:
Cable Diagnostic
Status: Poor
Action:
[Partial Service]
If the Partial Service mode does not go away within a few hours (Click the Refresh button after each step):
1) Make sure the coaxial cable is tightly connected.
2) Remove any unnecessary splitters.
3) Replace any required ones.
4) Contact your service provider for troubleshooting help.
[Downstream Power Level]
Try these actions (Click the Refresh button after each step):
1) Make sure the coaxial cable is tightly connected.
2) Remove any unnecessary splitters.
3) Replace any required splitters.
4) Contact your service provider for troubleshooting help.
Internet Access: Good
Downstream Status: Bad
Partial Service: Poor
Cable modem is in partial service mode. Your service provider might be under maintenance. Most of the time it won't affect your traffic and will automatically clear when work is complete.
Downstream Power Level: Bad
Downstream power is poor (-17.0dBmV). The recommended level is between -10dBmV to 10dBmV.
Downstream SNR: Good
Upstream Status: Poor
Partial Service: Poor
Cable modem is in partial service mode. Your service provider might be under maintenance. Most of the time it won't affect your traffic and will automatically clear when work is complete.
Upstream Power Level: Good
Current time: Sun Jan 26 20:03:10 2025
Startup Procedure
Acquire Downstream Channel: 543 MHz Locked
Connectivity State: OK Operational
Boot State: OK Operational
Security: Enabled BPI+
Downstream Bonded Channels (Partial Service)
Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
1 Locked 256 QAM 17 543000000 Hz -9.1 dBmV 40.9 dB 0 0
2 Locked 256 QAM 1 441000000 Hz -7 dBmV 41.1 dB 0 0
3 Locked 256 QAM 2 453000000 Hz -7.9 dBmV 40.9 dB 0 0
4 Locked 256 QAM 3 459000000 Hz -10.8 dBmV 40 dB 0 0
5 Locked 256 QAM 4 465000000 Hz -10.5 dBmV 40.1 dB 0 0
6 Locked 256 QAM 5 471000000 Hz -10.3 dBmV 40.2 dB 0 0
7 Locked 256 QAM 6 477000000 Hz -7.6 dBmV 41.2 dB 0 0
8 Locked 256 QAM 7 483000000 Hz -6.9 dBmV 41.5 dB 0 0
9 Locked 256 QAM 8 489000000 Hz -7.6 dBmV 41.4 dB 0 0
10 Locked 256 QAM 9 495000000 Hz -10.5 dBmV 40.2 dB 0 0
11 Locked 256 QAM 10 501000000 Hz -13 dBmV 39.1 dB 0 0
12 Locked 256 QAM 11 507000000 Hz -14.6 dBmV 38 dB 0 0
13 Locked 256 QAM 12 513000000 Hz -14.2 dBmV 38.3 dB 0 0
14 Locked 256 QAM 13 519000000 Hz -11.7 dBmV 39.8 dB 0 0
15 Locked 256 QAM 14 525000000 Hz -9.1 dBmV 40.9 dB 0 0
16 Locked 256 QAM 15 531000000 Hz -6.6 dBmV 41.8 dB 0 0
17 Locked 256 QAM 16 537000000 Hz -7.5 dBmV 41.6 dB 0 0
18 Locked 256 QAM 18 549000000 Hz -11.5 dBmV 39.8 dB 0 0
19 Locked 256 QAM 19 561000000 Hz -11.4 dBmV 39.9 dB 0 0
20 Locked 256 QAM 20 567000000 Hz -9.8 dBmV 40.7 dB 0 0
21 Locked 256 QAM 21 573000000 Hz -9.8 dBmV 40.6 dB 0 0
22 Locked 256 QAM 22 579000000 Hz -11.3 dBmV 39.9 dB 0 0
23 Locked 256 QAM 23 585000000 Hz -15.7 dBmV 37 dB 0 0
24 Locked 256 QAM 24 591000000 Hz -16.9 dBmV 36.1 dB 0 0
25 Locked 256 QAM 25 597000000 Hz -17 dBmV 36.1 dB 0 0
26 Locked 256 QAM 26 603000000 Hz -15.6 dBmV 37.1 dB 0 0
27 Locked 256 QAM 27 609000000 Hz -12.1 dBmV 39.4 dB 0 0
28 Locked 256 QAM 28 615000000 Hz -8.8 dBmV 40.3 dB 0 0
29 Locked 256 QAM 29 621000000 Hz -6.6 dBmV 41.7 dB 0 0
30 Locked 256 QAM 30 627000000 Hz -8.3 dBmV 41.2 dB 0 0
31 Locked 256 QAM 31 633000000 Hz -10.4 dBmV 40.1 dB 0 0
32 Not Locked Unknown 0 0 Hz 0.0 0.0 0 0
Upstream Bonded Channels (Partial Service)
Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
1 Locked ATDMA 2 5120 Ksym/sec 22800000 Hz 53.0 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 16300000 Hz 53.0 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 29200000 Hz 53.0 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 35600000 Hz 53.0 dBmV
5 Not Locked Unknown 0 0 0 0.0
6 Not Locked Unknown 0 0 0 0.0
7 Not Locked Unknown 0 0 0 0.0
8 Not Locked Unknown 0 0 0 0.0
Downstream OFDM Channels
Channel LockedStatus ProfileID ChannelID Frequency Power SNR/MER ActiveSubcarrier Unerror Correctable Uncorrectable
1 Locked 0 ,1 ,2 ,3 37 693000000 Hz -12.92 dBmV 35.6 dB 1108 ~ 2987 26878593 23647117 1461798
2 Not Locked 0 0 0 Hz 0 dBmV 0 dB 0 ~ 4095 0 0 0
Upstream OFDMA Channels
Channel LockedStatus ProfileID ChannelID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV
Event Log
Time Priority Description
Sun Jan 26 20:02:47 2025 Notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 20:02:44 2025 Notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 20:02:24 2025 Notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 20:01:43 2025 Notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 20:00:31 2025 Notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:59:59 2025 Notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:59:39 2025 Notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:58:18 2025 Notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:56:17 2025 Notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:56:02 2025 Notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:55:22 2025 Notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:54:21 2025 Notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:53:46 2025 Notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:52:54 2025 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:44:59 2025 Critical No Ranging Response received - T3 time-out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:44:58 2025 Notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:44:56 2025 Critical No Ranging Response received - T3 time-out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:43:47 2025 Notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:43:46 2025 Notice TLV-11 - unrecognized OID;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:35 1970 Notice Honoring MDD; IP provisioning mode = IPv6
Thu Jan 1 00:00:31 1970 Critical No Ranging Response received - T3 time-out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:26 1970 Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REMOVED;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:41:53 2025 Critical Resetting the cable modem due to docsDevResetNow
Sun Jan 26 19:39:44 2025 Critical No Ranging Response received - T3 time-out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:39:35 2025 Critical No Ranging Response received - T3 time-out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:03:47 1970 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:02:30 1970 Critical No Ranging Response received - T3 time-out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:02:25 1970 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:28 1970 Critical No Ranging Response received - T3 time-out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:23 1970 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:30 1970 Critical No Ranging Response received - T3 time-out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:30 1970 Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REMOVED;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:24:38 2025 Critical Resetting the cable modem due to docsDevResetNow
Sun Jan 26 19:23:44 2025 Critical No Ranging Response received - T3 time-out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:23:37 2025 Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:05:47 2025 Critical No Ranging Response received - T3 time-out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:05:46 2025 Critical No Ranging Response received - T3 time-out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:04:21 2025 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Sun Jan 26 19:02:23 2025 Critical No Ranging Response received - T3 time-out;CM-MAC=REMOVED;CMTS-MAC=REMOVED;CM-QOS=1.1;CM-VER=3.1;
Accepted Solution
EG
Expert
•
109.8K Messages
3 months ago
The upstream power is out of spec as well ! Bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it up to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.
Insist that the tech escalates this issue ! Good luck !
1
EG
Expert
•
109.8K Messages
2 months ago
@roccog
Out of curiosity, would you please post what the signal status values look like now ?
1
EG
Expert
•
109.8K Messages
2 months ago
Thanks for the update. Looks good ! You should be golden ! Hope things hold up for you ! Good luck !
0