@gp-se I'm not sure how to read it but here it is:
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB) 1 609000000 256QAM 5.700 10 38.605 11 615000000 256QAM 6.000 11 38.605 12 621000000 256QAM 6.300 12 38.605 13 633000000 256QAM 5.600 13 38.605 14 639000000 256QAM 5.500 14 38.605 15 645000000 256QAM 5.500 15 38.605 16 651000000 256QAM 5.600 16 38.605 17 657000000 256QAM 5.400 17 38.605 18 663000000 256QAM 5.400 18 38.605 19 669000000 256QAM 5.300 19 38.605 20 675000000 256QAM 5.600 20 38.605 21 681000000 256QAM 5.500 21 38.605 22 687000000 256QAM 5.300 22 38.605 23 693000000 256QAM 5.200 23 37.636 24 699000000 256QAM 4.900 24 37.636 25 705000000 256QAM 4.400 25 37.636 26 711000000 256QAM 4.000 26 37.636 27 717000000 256QAM 3.900 27 37.636 28 723000000 256QAM 3.200 28 37.636 29 825000000 256QAM 6.700 29 38.983 30 831000000 256QAM 6.400 30 37.636 31 837000000 256QAM 6.000 31 37.356OFDM Downstream Overview
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 5.699997Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth 1 38596000 ATDMA - 16QAM 33.250 3 3200000 2 30596000 ATDMA - 16QAM 32.250 1 6400000 3 23700000 ATDMA - 16QAM 32.000 2 6400000OFDM/OFDMA Overview
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
Oh wow, you are missing most of your downstream channels!
I believe this is due to the 2.4 ghz interference issue on the "non-black-dot" units. The black dot units have extra shielding to prevent the 2.4 ghz signals from messing with the modem and causing it to drop channels. Without all your channels you will have terrible speed. I'll bet that when you first reboot, and your speed is good, you have all your channels 1-32, but after time and interference they start dropping. Check your channels when you first reboot, and then once the speeds slows down to compare.
Your signal levels however seem great, and you have docsis 3.1 active in your area.
For now you could try disabling 2.4 ghz radio on the modem, or if you are in bridge mode, you could try moving your wireless router way further away from your modem.
I'm sure you will be told to exchange your modem for the black dot version if you talk to tech support.
I would like to return this faulty CODA modem back.
I'm still having connection dropping issues every few hours, i have to reboot the modem 2-4 times DAILY.
This is unacceptable, and this modem is clearly faulty. It's essential that my connection *never* drops because i'm connecting remotely to my computer at all times.
I do not want to wait until you guys fix all these issues with this modem (if ever).
What are my options of using other modems? Could you please provide a list of supported modems?
I do not need wifi features as I'm bridging it with my own wifi router that works perfectly.
If you plan to return the faulty modem, your options are the CGN3ACSMR or the CGNM-3552. If you're on Gigabit you should get the 3552 as it supports speeds up to 1.2Gbps. The CGN3ASCMR only supports 960Mbps However, given that many people have bricked modems, and are constantly returning to stores to have them replaced, there's a good chance that the modems are out of stock. Before returning the modem, I suggest calling your local Rogers store to see if they have stock of the modems.
@bfanek if that modem doesn't have a black dot near the power cord, then it might make sense to swap it for one that does, as that black dot indicates that the Docsis tuner has additional shielding installed to prevent interference from nearby 2.4 Ghz wifi transmitters.
1. Is that one of the original CODA-4582s without the black dot?
2. If so, try the following experiment if the modem and router (with 2.4 Ghz operating) are close together:
a. separate the two by several feet so that the router can't influence the modem; or
b. shut down the 2.4 Ghz on the router
In both cases, reboot the modem after either one of those actions.
Are you connecting to the computer via VPN? Just curious at this point as I know the CGNM-3552 would crash and reboot after two to three hours of continuous VPN usage. That might be driven entirely upon the type of VPN and protocol used. I don't know if the same applies to this modem as I haven't had the opportunity to look for that scenario.
Depending on your internet plan, you would be eligible for another modem model. The local Rogers store could tell you what model goes with what plan. The one problem in this case is whether or not you're on a gigabit plan. I don't know if there are restrictions in place for that plan to use the CODA-4582 only, or if it will allow the CGNM-3552. Maybe one of the mods can answer that question.
The only problem with swapping modems at the moment is borking of several hundred/thousand (?) modems over the weekend due to some process that Rogers was running. As a result, modems are in high demand and short supply, at least temporarily. So, before you head to a store to swap modems, call first to see if any are in stock.
@gp-se Thanks for the help. I didn't realize that I was missing so many of these channels. A Rogers tech came over about an hour ago to swap out the modem and make sure my signals were okay.
I now have the Black Dot version of the modem from Rogers which seems to have fixed the issue so far. One thing I did notice though is that my firmware is only 126.96.36.199 and has not been updated to the latest firmware it should be on which i believe is 188.8.131.52. Not a huge deal I guess since it's working so far, i'll just wait for it to be pushed to the latest firmware eventually.
The only problem with swapping modems at the moment is borking of several hundred/thousand (?) modems over the weekend due to some process that Rogers was running.
What do you mean by Borking? Like they messed up several hundred/thousand modems over the weekend?
Would this possibly be because of the "IPV6" fix they had planned?