12-13-2016 11:54 AM - last edited on 12-14-2016 05:50 PM by RogersMaude
Announced 13-December-2016 by @RogersDave http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/message-id/379...
Credit to @Hybrid_Noodle
Hitron website: http://www.hitron-americas.com/product/coda-4582/
Datasheet: http://www.hitron-americas.com/wp-content/uploads/2016/09/CODA-4582-Datasheet.pdf
60W Power Supply built into unit
Pictures of Hardware Version 1A:
***Added Labels***
02-21-2017 08:27 AM - last edited on 02-21-2017 08:29 AM by RogersCorey
@RogersDave
CommunityHelps asked me to reach out to you directly in case this is a bug. Can you have a look please?
02-21-2017 10:27 AM
@WestPoint wrote:@SeanMM I COMPLETE UNDERSTAND !!!
I as well have a senior citizen living with me, and I have IP devices for her for emergancy response and what not, and they are basically useless if Im not here to litterally watch the network for her...
You dont have her modem set on the firmware trial do you?
02-21-2017 12:47 PM
@markopas no, i didnt join the trial, but I did get them to flash me to .24 trial firmware just because its atleast stable for the most part. Slow speeds, but has only gone down once in the last 2 days...
I thought about it, but I dont want to get some other buggy firmware in the middle of the night and have any mayjor issues.... I just couldnt use v .13 thats comes loaded on the modems, it was failing every 1-4hrs..
02-21-2017 12:58 PM
02-21-2017 01:05 PM
Good to know that a CSR can do it.
02-21-2017 01:09 PM - edited 02-21-2017 01:09 PM
Hello Community,
Just for clarification, while Tier 2 can push the firmware, it will not be permanent. When the network does its regular firmware update push, you will be reverted back to the in production firmware if you are not officially signed up for the Firmware Trial through us here @CommunityHelps.
Regards,
RogersCorey
^ch
02-21-2017 01:19 PM - edited 02-21-2017 01:45 PM
02-21-2017 01:24 PM - edited 02-21-2017 01:25 PM
Thanks for clarifying @RogersCorey,
This was actually a big beef of mine while dealing with Twitter support. It seems rather odd that support isn't able to coordinate with the @CommunityHelps department in order to get people onto the beta firmware if it will potentially fix their issues.
Are there any plans to improve the way internal department communications happen that might allow support to facilitate these things? I'm sure support can gather all the same information (MAC address, etc.) and get someone to verbally agree to any terms (or textually via Twitter support for example).
02-21-2017 10:34 PM
I've been wondering this for quite some time since the move to D3.1 last week, but what is the acceptable range for the OFDM PLC power level?
02-21-2017 11:18 PM
On .24 firmware right now, until 24, I hadn't noticed missing channels. Pulling over 800mbps down and nearly 50mbps up, with fairly low latency, but missing 2 channels:
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 657000000 | 256QAM | 1.800 | 17 | 38.605 |
2 | 561000000 | 256QAM | 2.400 | 2 | 38.983 |
3 | 567000000 | 256QAM | 2.300 | 3 | 38.605 |
4 | 573000000 | 256QAM | 2.300 | 4 | 38.605 |
5 | 579000000 | 256QAM | 2.100 | 5 | 38.983 |
6 | 585000000 | 256QAM | 2.200 | 6 | 38.605 |
7 | 591000000 | 256QAM | 2.200 | 7 | 38.605 |
8 | 597000000 | 256QAM | 2.400 | 8 | 38.983 |
9 | 603000000 | 256QAM | 2.500 | 9 | 38.605 |
10 | 609000000 | 256QAM | 2.100 | 10 | 38.605 |
11 | 615000000 | 256QAM | 2.200 | 11 | 38.983 |
12 | 621000000 | 256QAM | 2.100 | 12 | 38.983 |
13 | 633000000 | 256QAM | 2.100 | 13 | 38.605 |
14 | 639000000 | 256QAM | 2.000 | 14 | 38.605 |
15 | 645000000 | 256QAM | 1.900 | 15 | 38.605 |
16 | 651000000 | 256QAM | 2.100 | 16 | 38.983 |
17 | 555000000 | 256QAM | 2.500 | 1 | 38.605 |
18 | 663000000 | 256QAM | 1.900 | 18 | 38.983 |
19 | 669000000 | 256QAM | 1.800 | 19 | 38.605 |
20 | 675000000 | 256QAM | 1.900 | 20 | 38.605 |
21 | 681000000 | 256QAM | 1.700 | 21 | 38.605 |
24 | 699000000 | 256QAM | 1.700 | 24 | 38.983 |
25 | 705000000 | 256QAM | 1.600 | 25 | 38.605 |
26 | 711000000 | 256QAM | 1.100 | 26 | 37.636 |
27 | 717000000 | 256QAM | 1.300 | 27 | 37.636 |
28 | 723000000 | 256QAM | 0.700 | 28 | 37.636 |
29 | 825000000 | 256QAM | -1.600 | 29 | 36.387 |
30 | 831000000 | 256QAM | -1.900 | 30 | 36.387 |
31 | 837000000 | 256QAM | -1.900 | 31 | 36.387 |
32 | 843000000 | 256QAM | -2.300 | 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 | 3.599998 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 38595766 | ATDMA - 64QAM | 44.000 | 3 | 3200000 |
2 | 30596000 | ATDMA - 64QAM | 40.500 | 1 | 6400000 |
3 | 23700000 | ATDMA - 64QAM | 40.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 |
02-21-2017 11:27 PM - edited 02-21-2017 11:38 PM
@coder_1990 does your modem have a black round sticker on the back of the modem located near the power cord?
02-21-2017 11:53 PM
02-21-2017 11:57 PM - edited 02-21-2017 11:59 PM
Yes, you should swap it out, considering that you have missing channels. Running the 2.4 Ghz by chance? If so, try an experiment: shut down the 2.4 Ghz wifi and then reboot the modem. Check the channels after the reboot to see if all 32 downstream channels are present. You could run a reboot first, with the wifi running, just to check the effects of the reboot, as in, will the reboot result in 32 downstream channels running, even if the wifi is running?
The painful part after the swap will be requesting .24 again and waiting for it to load. In the end you will be better off with all channels available.
02-22-2017 12:26 AM
02-22-2017 12:35 AM
02-22-2017 02:14 PM - edited 02-22-2017 02:22 PM
Hello All,
@CommunityHelps @RogersDave
Last week I upgraded to the new CODA-4582 modem and I have the Rogers Gigabit package. I experienced the exact same issue as everyone else where my downstream was great for about an hour (700Mbps+), and then it would basically decrease to less than 1Mbps, and eventially disconnect completely (Logs indicating many timeouts).
I swapped modems twice.. first one was the 1 black dot, and now have the one with 2 black dots. It made zero difference, so please don't waste time in exchanging the hardware. I am currently on firmware version 2.0.10.19 (which is apparently there production release) but there is zero improvement... ALL 32 downstream channels were still in the negative dBmV values.
I have now contacted Rogers yet again, and they have pushed out the new 2.0.10.24 (this is BETA btw) and I will provide feedback on performance afterwards. Let's all hope this provides a solution to the problem. Because having to reboot your modem every 45 minutes is unacceptable.
02-22-2017 02:24 PM
@CommunityHelps @RogersDave
Just read about users getting reverted back to the .19 firmware. Could you please place my account on the exclusions list for the beta testers, so I can remain on .24
Thanks!
02-22-2017 03:00 PM - edited 02-22-2017 03:19 PM
Send a private message to @CommunityHelps, including your modems MAC address and serial number. Follow that link to the @CommunityHelps public page. Follow the link on the right and side to "send this user a private message". That takes you to the pre-addressed message composition page.
Add in the title: Rogers Rocket Wi-Fi Modem Firmware Trial
Text contents:
1. Modem Model: CODA-4582
2. MAC address:
3. Serial Number:
The MAC address and serial number can be copied from the modem's STATUS page, which is seen when you log into the modem.
Watch for a number overlaid on your avatar in the upper right hand corner of the page when you are logged into the forum. Follow that link down to the message inbox for the reply from the moderators.
Here's a reference post:
If you have .24 loaded on your modem, as seen in the Software version (firmware) on the STATUS page, you should at the very least, restart the modem. Pull the power from the modem, wait for 30 seconds and plug the power cable back in to force a restart. If you have any problems, consider running a factory reset.
Does your modem have a black dot (sticker) on the back of the modem near the power cord? It should.
Edit: add a note to your pm to indicate that you have .24 already loaded, but require the modem to be placed on the exclusion list so that its protected from rolling back to .19 due to the nightly or weekly system check.
Just to note, prior to the creation of the exclusion list or its widespread use, that system check would detect newly installed modems with out of date firmware which are now running on the network and update them accordingly, so that was or is a straight forward process. The addition of test firmware complicates this now by having to protect those modems from the same system check and rolling back to the current production firmware.
02-22-2017 03:26 PM
@Datalink @CommunityHelps @RogersDave
Hi,
I just updated to .24 and performed a full reboot afterwards and regret to inform that it is just as slow as it was previously on .19 I had 500Mbps for about 5 minutes before it dropped back to 2MBps consistently:
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 615000000 | 256QAM | -0.800 | 11 | 38.983 |
2 | 561000000 | 256QAM | -0.600 | 2 | 38.983 |
3 | 567000000 | 256QAM | -1.000 | 3 | 38.605 |
4 | 573000000 | 256QAM | -0.800 | 4 | 38.605 |
5 | 579000000 | 256QAM | -1.000 | 5 | 38.983 |
6 | 585000000 | 256QAM | -0.900 | 6 | 38.983 |
7 | 591000000 | 256QAM | -0.800 | 7 | 38.605 |
8 | 597000000 | 256QAM | -0.900 | 8 | 38.983 |
9 | 603000000 | 256QAM | -1.200 | 9 | 38.605 |
10 | 609000000 | 256QAM | -1.100 | 10 | 38.983 |
11 | 555000000 | 256QAM | -0.900 | 1 | 38.605 |
12 | 621000000 | 256QAM | -1.200 | 12 | 38.983 |
13 | 633000000 | 256QAM | -0.900 | 13 | 38.983 |
14 | 639000000 | 256QAM | -1.000 | 14 | 38.605 |
15 | 645000000 | 256QAM | -0.400 | 15 | 38.605 |
16 | 651000000 | 256QAM | -0.800 | 16 | 38.605 |
17 | 657000000 | 256QAM | -0.400 | 17 | 38.983 |
18 | 663000000 | 256QAM | -0.100 | 18 | 38.983 |
19 | 669000000 | 256QAM | -0.100 | 19 | 40.366 |
20 | 675000000 | 256QAM | -0.600 | 20 | 38.983 |
21 | 681000000 | 256QAM | -0.900 | 21 | 38.983 |
22 | 687000000 | 256QAM | -0.900 | 22 | 38.605 |
23 | 693000000 | 256QAM | -0.700 | 23 | 38.983 |
24 | 699000000 | 256QAM | -0.800 | 24 | 38.605 |
25 | 705000000 | 256QAM | -1.400 | 25 | 38.605 |
26 | 711000000 | 256QAM | -1.100 | 26 | 38.983 |
27 | 717000000 | 256QAM | -1.200 | 27 | 38.605 |
28 | 723000000 | 256QAM | -1.100 | 28 | 38.605 |
29 | 825000000 | 256QAM | -2.000 | 29 | 38.983 |
30 | 831000000 | 256QAM | -2.000 | 30 | 38.983 |
31 | 837000000 | 256QAM | -2.500 | 31 | 38.605 |
32 | 843000000 | 256QAM | -2.600 | 32 | 38.605 |
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 | -0.599998 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 38595805 | ATDMA - 64QAM | 37.500 | 3 | 3200000 |
2 | 30596000 | ATDMA - 64QAM | 35.500 | 1 | 6400000 |
3 | 23700000 | ATDMA - 64QAM | 34.250 | 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 |
02-22-2017 09:19 PM - edited 02-22-2017 10:08 PM
So, still on 0.19 (super glad Twitter Support "expidited" this) and I've been running PingPlotter. The modem just randomly stopped returning times. It's like it randomly decided to start timing out ICMP requests. Obviously that isn't impacting my speeds but it's rather a pain since I've been using PingPlotter to troubleshoot until now and it's worked fine.
It should be noted it was also doing that earlier tonight but a restart of the modem fixed it.
EDIT:
It get's stranger - just noticed that I can't do anything to adjust/turn on our 2.4Ghz wifi
https://i.gyazo.com/e29543a3dd5924bc2847431d0afa63a4.gif
and it has this under status:
Wireless Status
This menu displays the current wireless status
2.4 GHz Wireless Status | |
Wireless Status (2.4 GHz) | OFF |
Wireless Mode (2.4 GHz) | 802.11 b/g/n Mixed |
Wireless Channel (2.4 GHz) | Auto(5) |
5 GHz Wireless Status | |
Wireless Status (5 GHz) | ON |
Wireless Mode (5 GHz) | 802.11 a/n/ac Mixed |
Wireless Channel (5 GHz) | Auto(36) |
SSID Overview | |
TheTeam Down
|
EDIT 2:
Doing a soft reboot of the modem seemed to fix the issue with PingPlotter not getting a response from the modem but it appears 2.4 is still unable to be turned on.
02-22-2017 10:03 PM - last edited on 02-22-2017 10:08 PM by RogersMaude
Just switched to this new modem. The old Rogers Rocket gigabit modem actually was running perfectly fine. In fact i got faster speeds and further range. Now we are all experiencing network issues, low internet, and internet + wifi drop outs constantly.
I do not think there is anyone who is having a good experience with this router (not to mention that it even looks uglier than the old black sleek one).
This is like a cheap plastic box. Can we get our old one back?
I am pretty sure rogers cheated us all and got a cheaper deal from their router vendor so they took our more expensive model...if this is not true Rogers fix my GIGABIT internet!