06-06-2019 10:39 AM
@Camael1 @Geezup can both of you log into your modem, navigate to the STATUS .... DOCSIS WAN tab and copy the signal level table starting at the "Downstream Overview" and going all the way to the bottom right hand corner of the OFDMA section at the bottom of the table. Ignore the data that sits above the "Downstream Overview". That table will copy just like any other table in a document, select or highlight that entire section and right click .... copy. Then you can paste that into a post. Hopefully that will shed some light on the problems that both of you are experiencing. Its possible however that very short interruptions won't be captured in that data. If the external cable and/or connectors are old and starting to fail, that will cause short interruptions in service that will increase in frequency until the cable or connectors finally fail. While the service is up and running, the signal levels will appear normal. Additionally, the modem reboot will return the service back to its normal operating mode, but, the reboot won't resolve the underlying cause of the failures.
06-06-2019 10:50 AM
06-06-2019 10:51 AM
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 591000000 | 256QAM | -7.700 | 7 | 35.084 |
2 | 855000000 | 256QAM | -11.300 | 3 | 33.377 |
3 | 861000000 | 256QAM | -11.600 | 4 | 33.487 |
4 | 579000000 | 256QAM | -7.000 | 5 | 35.084 |
5 | 585000000 | 256QAM | -7.000 | 6 | 35.595 |
6 | 849000000 | 256QAM | -10.200 | 2 | 34.346 |
7 | 597000000 | 256QAM | -7.600 | 8 | 35.084 |
8 | 603000000 | 256QAM | -8.000 | 9 | 34.926 |
9 | 609000000 | 256QAM | -9.100 | 10 | 34.346 |
10 | 615000000 | 256QAM | -8.300 | 11 | 34.484 |
11 | 621000000 | 256QAM | -7.900 | 12 | 34.926 |
12 | 633000000 | 256QAM | -8.600 | 13 | 34.346 |
13 | 639000000 | 256QAM | -8.100 | 14 | 34.926 |
14 | 645000000 | 256QAM | -9.100 | 15 | 33.834 |
15 | 651000000 | 256QAM | -8.900 | 16 | 33.957 |
16 | 657000000 | 256QAM | -8.300 | 17 | 34.926 |
17 | 663000000 | 256QAM | -8.900 | 18 | 34.346 |
18 | 669000000 | 256QAM | -9.100 | 19 | 33.834 |
19 | 675000000 | 256QAM | -8.300 | 20 | 34.484 |
20 | 681000000 | 256QAM | -8.800 | 21 | 34.484 |
21 | 687000000 | 256QAM | -9.100 | 22 | 34.484 |
22 | 693000000 | 256QAM | -8.100 | 23 | 35.084 |
23 | 699000000 | 256QAM | -8.200 | 24 | 35.084 |
24 | 705000000 | 256QAM | -9.400 | 25 | 34.346 |
25 | 711000000 | 256QAM | -9.500 | 26 | 34.346 |
26 | 717000000 | 256QAM | -9.900 | 27 | 33.487 |
27 | 723000000 | 256QAM | -10.600 | 28 | 32.585 |
28 | 825000000 | 256QAM | -10.000 | 29 | 34.926 |
29 | 831000000 | 256QAM | -10.100 | 30 | 34.484 |
30 | 837000000 | 256QAM | -10.800 | 31 | 34.346 |
31 | 843000000 | 256QAM | -10.200 | 32 | 34.484 |
32 | 279000000 | 256QAM | -3.100 | 1 | 35.595 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | 4K | 275600000 | YES | YES | YES | -2.299999 |
1 | NA | NA | NO | NO | NO | NA |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 38596000 | ATDMA - 64QAM | 38.250 | 6 | 3200000 |
2 | 30596000 | ATDMA - 64QAM | 35.500 | 4 | 6400000 |
3 | 23700000 | ATDMA - 64QAM | 34.250 | 5 | 6400000 |
Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
0 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
1 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
06-06-2019 10:54 AM
06-06-2019 10:55 AM
@Camael1 you have some channel signal levels below -10 dBmV, which is Rogers cut off point to send a tech. Call tech support and ask the Customer Service Rep to run a signal check on your modem. It should fail automatically. Also advise the CSR that you're experiencing service drop outs. The signal check failure should result in the CSR arranging for a tech visit at your convenience. When that is done, please repost the signal levels. Sometimes this takes more than one visit, and perhaps the issue is beyond the local external cable, further upstream towards the Cable Modem Termination System, which the modem is connected to for modem control and data services.
06-10-2019 07:41 AM
I have been having disconnect issues the last few weeks - can you please take a look at the information below and let me know if you notice something? The event log shows a lot of activity (my internet dropped out last night around 11 PM).
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 603000000 | 256QAM | 6.400 | 9 | 40.366 |
2 | 849000000 | 256QAM | 8.400 | 2 | 40.366 |
3 | 855000000 | 256QAM | 8.500 | 3 | 38.983 |
4 | 861000000 | 256QAM | 9.100 | 4 | 38.983 |
5 | 579000000 | 256QAM | 6.500 | 5 | 40.366 |
6 | 585000000 | 256QAM | 6.700 | 6 | 40.366 |
7 | 591000000 | 256QAM | 6.700 | 7 | 40.366 |
8 | 597000000 | 256QAM | 6.600 | 8 | 40.946 |
9 | 279000000 | 256QAM | 3.900 | 1 | 40.946 |
10 | 609000000 | 256QAM | 6.500 | 10 | 40.366 |
11 | 615000000 | 256QAM | 6.400 | 11 | 40.946 |
12 | 621000000 | 256QAM | 6.200 | 12 | 40.366 |
13 | 633000000 | 256QAM | 6.100 | 13 | 38.983 |
14 | 639000000 | 256QAM | 6.100 | 14 | 40.366 |
15 | 645000000 | 256QAM | 6.400 | 15 | 40.946 |
16 | 651000000 | 256QAM | 6.500 | 16 | 40.366 |
17 | 657000000 | 256QAM | 6.900 | 17 | 40.946 |
18 | 663000000 | 256QAM | 7.000 | 18 | 40.366 |
19 | 669000000 | 256QAM | 7.300 | 19 | 40.366 |
20 | 675000000 | 256QAM | 7.300 | 20 | 40.366 |
21 | 681000000 | 256QAM | 7.300 | 21 | 40.946 |
22 | 687000000 | 256QAM | 7.600 | 22 | 40.946 |
23 | 693000000 | 256QAM | 7.700 | 23 | 40.366 |
24 | 699000000 | 256QAM | 8.000 | 24 | 40.366 |
25 | 705000000 | 256QAM | 8.100 | 25 | 40.366 |
26 | 711000000 | 256QAM | 7.900 | 26 | 40.366 |
27 | 717000000 | 256QAM | 7.800 | 27 | 40.366 |
28 | 723000000 | 256QAM | 7.800 | 28 | 40.946 |
29 | 825000000 | 256QAM | 8.300 | 29 | 40.366 |
30 | 831000000 | 256QAM | 8.400 | 30 | 40.366 |
31 | 837000000 | 256QAM | 8.600 | 31 | 40.946 |
32 | 843000000 | 256QAM | 8.600 | 32 | 40.366 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | NA | NA | NO | NO | NO | NA |
1 | 4K | 275600000 | YES | YES | YES | 4.599998 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 36996000 | ATDMA - 64QAM | 33.250 | 4 | 6400000 |
2 | 22100000 | ATDMA - 64QAM | 36.500 | 1 | 3200000 |
3 | 30596000 | ATDMA - 64QAM | 33.500 | 3 | 6400000 |
4 | 25300000 | ATDMA - 64QAM | 37.250 | 2 | 3200000 |
Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
0 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
1 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
06-10-2019 09:13 PM
DOCSIS Logs
The DOCSIS event logs is shown here
No.
Time
Type
Priority
Event
1
06/10/2019 04:28:28
85010200
warning
TCS Partial Service;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
2
06/10/2019 04:28:44
82000500
critical
Started Unicast Maintenance Ranging - No Response received - T3 time-out;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
3
06/10/2019 04:28:45
82000300
critical
Ranging Request Retries exhausted;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
4
06/10/2019 04:28:45
82000600
critical
Unicast Maintenance Ranging attempted - No response - Retries exhausted;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
5
06/10/2019 04:29:01
82000500
critical
Started Unicast Maintenance Ranging - No Response received - T3 time-out;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
6
06/10/2019 04:29:02
82000400
critical
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
7
06/10/2019 04:29:02
82000300
critical
Ranging Request Retries exhausted;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
8
06/10/2019 04:29:02
82000600
critical
Unicast Maintenance Ranging attempted - No response - Retries exhausted;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
9
06/10/2019 04:29:05
82000500
critical
Started Unicast Maintenance Ranging - No Response received - T3 time-out;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
10
06/10/2019 04:29:06
82000400
critical
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
11
06/10/2019 04:29:18
82000500
critical
Started Unicast Maintenance Ranging - No Response received - T3 time-out;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
12
06/10/2019 04:29:19
82000300
critical
Ranging Request Retries exhausted;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
13
06/10/2019 04:29:19
82000600
critical
Unicast Maintenance Ranging attempted - No response - Retries exhausted;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
14
06/10/2019 04:29:21
82000500
critical
Started Unicast Maintenance Ranging - No Response received - T3 time-out;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
15
06/10/2019 05:28:06
82000400
critical
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
16
06/10/2019 05:28:17
85010200
warning
TCS Partial Service;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
17
06/10/2019 05:28:21
82000400
critical
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
18
06/10/2019 05:28:48
85010200
warning
TCS Partial Service;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
19
06/10/2019 11:13:51
82000400
critical
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
20
06/10/2019 11:15:50
90000000
warning
MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;MAC - Removed from post;CM-QOS=1.1;CM-VER=3.1;
06-11-2019 09:04 AM
Hello, @ASimkins.
Thank you for posting your concern in the Community. The downstream levels are a little high, but within the specs and it should not cause disconnections. Did you notice the modem rebooting when the Internet drops?
We can run a few tests on your connection to determine the root cause of the issue. Please send us a private message at @CommunityHelps. You can find details about our private messaging in this blog.
Cheers,
RogersMoin
06-11-2019 02:12 PM - edited 06-11-2019 03:52 PM
I wanna say my Hitron has been dropping internet for about 2 months now. I just ran a Twitch Bandwidth test, and it went out within a few seconds of starting the test. Not sure if that caused it or not. Also, at this point, I'm unsure whether it's the modem or not.
I'd also like to point out the modem doesn't seem to restart when it happens. As in, I'm still able to access the modem in my browser immediately after the internet goes down.
Speeds are good for the most part. Signal levels are within spec and pretty much always have been in the duration I've had these issues. I still have packet loss issues as well where I will spike to like 50% or near 100% and not have a disconnect so I feel like it's not the modem.. but a lot of people are reporting drops with their Hitrons. I just had my CODA-4582U replaced about 4 or 5 months ago. Back then I was getting pretty terrible packet loss spikes. It wouldn't fully disconnect but was more like up to 50% packet loss for 10-15 seconds every now and then.
But later on, I started experiencing full disconnects. I was in contact with customer service for these disconnects and the last thing I was told, about a month ago, was that it was an issue with either a power supply on Roger's end or the city's electrical grid causing these disconnects. I figure if that was truly the case it would've been fixed by now. However, I've asked for a follow-up a couple of times and so far, no news.
If someone is able to explain the event log a bit more to me I would greatly appreciate that. I edited out the MAC addresses:
10 | 06/11/2019 18:40:07 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
11 | 06/11/2019 18:40:07 | 82000300 | critical | Ranging Request Retries exhausted;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
12 | 06/11/2019 18:40:07 | 82000600 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
13 | 06/11/2019 18:40:10 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=xCMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
14 | 06/11/2019 18:40:11 | 82000300 | critical | Ranging Request Retries exhausted;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
15 | 06/11/2019 18:40:11 | 82000600 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
16 | 06/11/2019 18:40:41 | 82000400 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
17 | 06/11/2019 18:41:14 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
18 | 06/11/2019 18:41:19 | 84000500 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
19 | 06/11/2019 18:41:33 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
20 | 06/11/2019 18:41:48 | 84020200 | warning | Lost MDD Timeout;CM-MAC=xx;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.1; |
Signal levels for reference. I also have an amplifier I can put on to get closer to 0 dBmV:
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 633000000 | 256QAM | -0.700 | 13 | 38.605 |
2 | 849000000 | 256QAM | -5.400 | 2 | 36.610 |
3 | 855000000 | 256QAM | -4.200 | 3 | 37.356 |
4 | 861000000 | 256QAM | -2.900 | 4 | 37.636 |
5 | 579000000 | 256QAM | -1.900 | 5 | 38.983 |
6 | 585000000 | 256QAM | -1.300 | 6 | 38.983 |
7 | 591000000 | 256QAM | -1.400 | 7 | 38.605 |
8 | 597000000 | 256QAM | -1.200 | 8 | 38.983 |
9 | 603000000 | 256QAM | -0.300 | 9 | 38.983 |
10 | 609000000 | 256QAM | 0.400 | 10 | 40.366 |
11 | 615000000 | 256QAM | 0.700 | 11 | 38.605 |
12 | 621000000 | 256QAM | 0.200 | 12 | 40.366 |
13 | 303000000 | 256QAM | -1.600 | 1 | 38.983 |
14 | 639000000 | 256QAM | -1.000 | 14 | 38.983 |
15 | 645000000 | 256QAM | -1.700 | 15 | 38.605 |
16 | 651000000 | 256QAM | -2.400 | 16 | 38.983 |
17 | 657000000 | 256QAM | -3.000 | 17 | 38.605 |
18 | 663000000 | 256QAM | -3.200 | 18 | 38.605 |
19 | 669000000 | 256QAM | -3.300 | 19 | 38.605 |
20 | 675000000 | 256QAM | -3.200 | 20 | 38.983 |
21 | 681000000 | 256QAM | -2.900 | 21 | 38.605 |
22 | 687000000 | 256QAM | -2.600 | 22 | 38.605 |
23 | 693000000 | 256QAM | -2.200 | 23 | 38.983 |
24 | 699000000 | 256QAM | -1.600 | 24 | 38.983 |
25 | 705000000 | 256QAM | -1.100 | 25 | 38.605 |
26 | 711000000 | 256QAM | -1.800 | 26 | 37.636 |
27 | 717000000 | 256QAM | -3.700 | 27 | 37.356 |
28 | 723000000 | 256QAM | -5.100 | 28 | 37.356 |
29 | 825000000 | 256QAM | -6.200 | 29 | 36.387 |
30 | 831000000 | 256QAM | -6.500 | 30 | 36.610 |
31 | 837000000 | 256QAM | -6.300 | 31 | 36.610 |
32 | 843000000 | 256QAM | -5.900 | 32 | 36.387 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | NA | NA | NO | NO | NO | NA |
1 | 4K | 290600000 | YES | YES | YES | 0.700001 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 38596234 | ATDMA - 64QAM | 39.250 | 3 | 3200000 |
2 | 30596000 | ATDMA - 64QAM | 36.500 | 1 | 6400000 |
3 | 23700000 | ATDMA - 64QAM | 39.000 | 2 | 6400000 |
Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
0 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
1 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
Edit: just ran another 3 Twitch bandwidth test and lost internet again within 10 seconds of starting each of them. I gave my modem a reboot before the last one and still, it disconnected. Is my modem faulty? Here is what the DOCSIS WAN page looks like when it happens:
Network Access | Process... |
IP Address | 0.0.0.0 |
Subnet Mask | |
Gateway IP Address | |
DHCP Lease Time | 😧 -- H: -- M: -- S: -- |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 591000000 | 256QAM | -0.500 | 7 | 38.983 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | NA | NA | NO | NO | NO | NA |
1 | NA | NA | NO | NO | NO | NA |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
0 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
1 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
edit2: also every CODA I've used so far sometimes does this thing where on a reboot I only have like 3-5mbps download. I feel as if it's not establishing downstream connections properly or something. Most times it seems to eventually fix itself or I can just reboot a few more times to get it back up. Anyone else with this CODA-4582 issue?
edit3: factory reset the modem. This helped get my downspeed back up to 300+ and so far, no disconnect when doing a Twitch Bandwidth test. Still getting some packet loss and dropped frames when I test stream, however. Definitely makes me think these disconnects were a result of the modem.
06-11-2019 06:29 PM
@Datalink Thanks you so much for the help. The Rogers technician came today to check the situation. This is how the DOCSIS WAN looks like.
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 657000000 | 256QAM | -3.400 | 17 | 37.356 |
2 | 849000000 | 256QAM | -7.600 | 2 | 35.780 |
3 | 855000000 | 256QAM | -8.100 | 3 | 35.084 |
4 | 861000000 | 256QAM | -9.000 | 4 | 34.484 |
5 | 579000000 | 256QAM | -2.000 | 5 | 37.356 |
6 | 585000000 | 256QAM | -1.700 | 6 | 37.356 |
7 | 591000000 | 256QAM | -1.600 | 7 | 37.636 |
8 | 597000000 | 256QAM | -2.100 | 8 | 37.636 |
9 | 603000000 | 256QAM | -2.300 | 9 | 37.356 |
10 | 609000000 | 256QAM | -2.800 | 10 | 37.356 |
11 | 615000000 | 256QAM | -3.000 | 11 | 37.356 |
12 | 621000000 | 256QAM | -3.000 | 12 | 37.356 |
13 | 633000000 | 256QAM | -3.400 | 13 | 36.610 |
14 | 639000000 | 256QAM | -3.500 | 14 | 37.356 |
15 | 645000000 | 256QAM | -3.400 | 15 | 37.356 |
16 | 651000000 | 256QAM | -3.200 | 16 | 37.356 |
17 | 279000000 | 256QAM | 2.200 | 1 | 37.356 |
18 | 663000000 | 256QAM | -3.400 | 18 | 37.356 |
19 | 669000000 | 256QAM | -3.600 | 19 | 37.636 |
20 | 675000000 | 256QAM | -3.600 | 20 | 36.610 |
21 | 681000000 | 256QAM | -3.600 | 21 | 37.356 |
22 | 687000000 | 256QAM | -3.700 | 22 | 37.356 |
23 | 693000000 | 256QAM | -3.500 | 23 | 37.636 |
24 | 699000000 | 256QAM | -3.400 | 24 | 37.356 |
25 | 705000000 | 256QAM | -3.700 | 25 | 37.356 |
26 | 711000000 | 256QAM | -4.200 | 26 | 36.610 |
27 | 717000000 | 256QAM | -4.700 | 27 | 36.610 |
28 | 723000000 | 256QAM | -4.900 | 28 | 36.610 |
29 | 825000000 | 256QAM | -7.000 | 29 | 36.387 |
30 | 831000000 | 256QAM | -6.900 | 30 | 36.387 |
31 | 837000000 | 256QAM | -7.100 | 31 | 36.387 |
32 | 843000000 | 256QAM | -7.400 | 32 | 35.780 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | NA | NA | NO | NO | NO | NA |
1 | 4K | 275600000 | YES | YES | YES | 2.400002 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 23700000 | ATDMA - 64QAM | 35.750 | 5 | 6400000 |
2 | 38596000 | ATDMA - 64QAM | 40.750 | 6 | 3200000 |
3 | 30596000 | ATDMA - 64QAM | 37.000 | 4 | 6400000 |
Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
0 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |
1 | DISABLED | 0.5000 | 0.0000 | 0.0000 | -inf | -1.0000 | 4K |