With good signal levels and acceptable noise levels, the 3552 will match the 4582 for speeds if you're running gigabit service. If you're running 250/20 or less then they will absolutely be equal. The difference is that the CODA-4582 does not suffer from the high latency that the 3552 or CGN3 series modem do. Those modems are a Puma 6MG modem which has that problem. The 4582 is a Puma 7 modem, which doesn't have the latency issue. However, at the present time as you have noted, there are issues with its introduction into service. So, personal opinion, unless you're having issues with latency in gaming, stick with the 3552 for maybe another month. By then another firmware version or two will have rolled out for the 4582.
@RogersDave Thanks for taking a look at my issue. i have swaped the modem to the modem with black dot
Modem also got the latest .23 pushed.
I have Factory Reset the Modem
Connected Directly to Modem even though its set in Bridge.
My download speed for some reason is not passing 400mbps ( I was constantly getting ~800 with old CODA on pre .19 FW. Issue started happening from .20 on wards ..
Whats going on .. missing my CGN now 😞
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB) 1 645000000 256QAM 0.100 39 38.983 2 363000000 256QAM 0.600 10 38.983 3 369000000 256QAM 0.600 11 38.983 4 375000000 256QAM 0.400 12 38.983 5 381000000 256QAM 0.700 13 38.983 6 387000000 256QAM 0.300 14 38.983 7 393000000 256QAM -0.400 15 38.983 8 399000000 256QAM -2.900 16 37.636 9 405000000 256QAM -2.500 17 37.636 10 411000000 256QAM -0.400 18 38.983 11 417000000 256QAM 0.300 19 38.605 12 423000000 256QAM 0.800 20 38.605 13 429000000 256QAM 0.600 21 38.605 14 435000000 256QAM 1.200 22 38.983 15 441000000 256QAM 1.500 23 38.983 16 447000000 256QAM 1.500 24 38.983 17 555000000 256QAM -0.200 25 38.605 18 561000000 256QAM 0.000 26 38.605 19 567000000 256QAM 0.000 27 38.983 20 573000000 256QAM 0.000 28 38.605 21 579000000 256QAM 0.500 29 38.983 22 585000000 256QAM 0.500 30 38.983 23 591000000 256QAM 0.400 31 38.983 24 597000000 256QAM 0.100 32 38.983 25 603000000 256QAM 0.100 33 38.983 26 609000000 256QAM -0.500 34 38.605 27 615000000 256QAM 0.000 35 38.983 28 621000000 256QAM -0.200 36 38.983 29 633000000 256QAM 0.000 37 38.983 30 639000000 256QAM -0.100 38 38.983 31 357000000 256QAM 0.900 9 38.983 32 651000000 256QAM 0.000 40 38.983OFDM 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 NA NA NO NO NO NAUpstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth 1 30596000 ATDMA - 64QAM 36.000 1 6400000 2 38595824 ATDMA - 64QAM 39.250 3 3200000 3 23700000 ATDMA - 64QAM 36.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
Ok.. So i have narrowed down the issue and found out my speeds are back to 900Mbps down / 40mbps UP between 1.30AM - 8.30AM everyday !!!
So when i run Speed test at 1.30AM - 8.30AM every day, my speeds are back to 900mbps/40mbps up while rest of the hours its stuck at 400Mbps ..
Is this due to Network Congestion ? My area is still on DOCSIS 3.0
That seems like a congestion issue since off peak hours you get good speed. To me that rules out your PC, Gateway, Settings, etc. I would call Tech Support and explain to them how during the day speeds are slow, and off peak hours everything is fast.
Thanks !!! Case Created - C119705438 If any Tech person can expediate this to Network team it will be great please .. Paying 1Gbps but stuck at 400mbps .. still willing to be on beta trail ..
I do have gigabit service. Thanks for your reply. Ill wait another few weeks or a month and then hopefully everything is better.
Is anyone else experiencing random modem reboots (non firmware update) after or around midnight?
it just happened twice within the hour (EST) today. Firmware is on .19
DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=a8:4e:3f:ca:c7:d0;CMTS-MAC=00:17:10:90:e9:24;CM-QOS=1.1;CM-VER=3.1; MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=a8:4e:3f:ca:c7:d0;CMTS-MAC=00:17:10:90:e9:24;CM-QOS=1.1;CM-VER=3.1;
Count me in amongst the multitude of people who have experienced issues with this modem.
On top of it rebooting twice in the last 35 minutes (12:05am EST and 12:35am EST), I experience consistent slow downs at peak hours, to the point where I can't do multiple things with my connection at once.
Despite having a Gigabit connection, when I run speed tests, the most I've ever seen was 850 down and about 30 up. More likely (especially during peak hours), it's in the 400mb down/15 up range.
Even worse, when I run Speedtests on sites not affiliated with Rogers (I don't trust them to provide accurate results) i'm getting numbers below 100mbps.
Running Firmware 184.108.40.206, and the event log is full of "No Ranging Response" errors (among others).
Signal parameters here:
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|Receiver||FFT type||Subcarr 0 Frequency(MHz)||PLC locked||NCP locked||MDC1 locked||PLC power(dBmv)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Bandwidth|
|1||30596000||ATDMA - 64QAM||32.750||1||6400000|
|2||38595766||ATDMA - 64QAM||34.750||3||3200000|
|3||23700000||ATDMA - 64QAM||32.750||2||6400000|
|Channel Index||State||lin Digital Att||Digital Att||BW (sc's*fft)||Report Power||Report Power1_6||FFT Size|
Same thing happened to me. Modem just reboots twice today. A lot of No Ranging Response received - T3 time-out on my logs.
And after disconnections and reboots
MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1 and DHCP RENEW WARNING - Field invalid in response v4 option
Alright so we have multiple users who confirmed that their modems are rebooting randomly (at least once) from 12AM-1AM. The time when the modems reboot also coincides when maintenance is done on the network- not sure if it relates to the modems rebooting, but it is my suspiscion.