05-31-2016 08:42 AM - last edited on 03-14-2018 04:23 PM by RogersRoland
Hello Community,
We are currently offering our users an exclusive opportunity to participate in an upcoming trial of the new firmware for our Rocket Wi-Fi Modem (CGN3ACR, CGN3AMR and CGN3ACSMR) and Rocket Gigabit Wi-Fi Modem (CGN3552 and CODA-4582). For details of this program, please see this thread.
This thread will be used for feedback regarding the firmware. We've invited @RogersSergio, @RogersSyd & @RogersBob from our Networking team to participate in this thread. Your feedback is very valuable and will be used to enhance the firmware before it is released publicly.
Thank you for your continued feedback and support.
01-12-2021 11:40 PM - edited 01-12-2021 11:41 PM
I would have taken it as a surprise, however no such luck. No longer able to access the login at the usual 192.168.100.1 address. Modem does seem to be continuing to operate unhindered. Pings to common websites continue to be low with gaming and VOIP performing reliably. Download and upload speeds are at the maximum attainable rate for the gigabit plan as they were with previous iteration of firmware. Nothing out of the ordinary to report really. There was a lot of fibre trenching being done in my area by Rogers but I haven't seen any updates to the infrastructure in my building as of yet, so maybe they are still on the way.
01-13-2021 02:17 AM
You on the .35? Haven't had a problem logging in at all. Almost 7days running now too.
01-13-2021 01:58 PM
@gp-se OFDMA is available and functioning on both our CODAs and XB6s where it is enabled on the network.
01-13-2021 04:31 PM
01-13-2021 05:30 PM
Never had any packet loss. And knock on wood haven't had any troubles at all.
01-13-2021 06:18 PM
@RogersIan wrote:
@gp-se OFDMA is available and functioning on both our CODAs and XB6s where it is enabled on the network.
Good to hear, I hope it gets enabled on my Node soon.
01-14-2021 07:54 AM
I am indeed on the .35 variant. I will try a reboot of my hardware today and see when the inability to log in happens again. Which browser are you using when trying to access the login page?
01-14-2021 12:09 PM
Edge Chromium on windows. Still can log in, on the old .33 was lucky if you maybe got 1hr before it became inaccessible. Only way was if it was rebooted, and then you'd still get the limited access.
01-15-2021 05:22 PM
OFDM got turned on in my area!
Hardware Version | 2A |
Software Version | 7.1.1.35 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 591000000 | QAM256 | 3.099 | 7 | 38.983 |
2 | 597000000 | QAM256 | 3.200 | 8 | 40.366 |
3 | 603000000 | QAM256 | 3.599 | 9 | 38.983 |
4 | 849000000 | QAM256 | 1.400 | 2 | 38.605 |
5 | 855000000 | QAM256 | 1.599 | 3 | 37.636 |
6 | 861000000 | QAM256 | 2.700 | 4 | 37.636 |
7 | 579000000 | QAM256 | 2.799 | 5 | 40.366 |
8 | 585000000 | QAM256 | 2.500 | 6 | 38.983 |
9 | 279000000 | QAM256 | -1.700 | 1 | 38.983 |
10 | 609000000 | QAM256 | 3.000 | 10 | 40.366 |
11 | 615000000 | QAM256 | 3.599 | 11 | 40.946 |
12 | 621000000 | QAM256 | 3.700 | 12 | 38.983 |
13 | 633000000 | QAM256 | 3.599 | 13 | 40.366 |
14 | 639000000 | QAM256 | 2.900 | 14 | 38.605 |
15 | 645000000 | QAM256 | 3.400 | 15 | 38.983 |
16 | 651000000 | QAM256 | 3.799 | 16 | 38.983 |
17 | 657000000 | QAM256 | 3.299 | 17 | 38.983 |
18 | 663000000 | QAM256 | 3.500 | 18 | 40.366 |
19 | 669000000 | QAM256 | 3.700 | 19 | 38.983 |
20 | 675000000 | QAM256 | 3.599 | 20 | 38.983 |
21 | 681000000 | QAM256 | 4.000 | 21 | 38.983 |
22 | 687000000 | QAM256 | 3.500 | 22 | 38.983 |
23 | 693000000 | QAM256 | 3.299 | 23 | 38.983 |
24 | 699000000 | QAM256 | 3.500 | 24 | 38.983 |
25 | 705000000 | QAM256 | 3.299 | 25 | 38.983 |
26 | 711000000 | QAM256 | 2.200 | 26 | 38.983 |
27 | 717000000 | QAM256 | 1.400 | 27 | 38.605 |
28 | 723000000 | QAM256 | 1.700 | 28 | 38.605 |
29 | 825000000 | QAM256 | 0.500 | 29 | 38.605 |
30 | 831000000 | QAM256 | 1.200 | 30 | 38.983 |
31 | 837000000 | QAM256 | 1.000 | 31 | 38.605 |
32 | 843000000 | QAM256 | 1.099 | 32 | 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 | 4K | 275600000 | YES | YES | YES | -0.200001 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 25900000 | 64QAM | 47.020 | 2 | 6400000 |
2 | 38700000 | 64QAM | 48.770 | 4 | 6400000 |
3 | 32300000 | 64QAM | 47.270 | 3 | 6400000 |
4 | 21100000 | 64QAM | 46.010 | 1 | 3200000 |
5 | 0 | QAM_NONE | - | --- | 1600000 |
6 | 0 | QAM_NONE | - | --- | 1600000 |
7 | 0 | QAM_NONE | - | --- | 1600000 |
8 | 0 | QAM_NONE | - | --- | 1600000 |
Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
0 | OPERATE | 0.2474 | 9.2213 | 9.6000 | 54.7815 | 47.0000 | 2K |
1 | DISABLED | 0.0000 | 0.0000 | 0.0000 | 0.0000 | 0.0000 | 2K |
© 2021 Hitron Technologies Inc. All rights reserved.
01-15-2021 06:06 PM
I just had to do a hard reset of my Rogers modem, not only was the statistics page not available but there was a hard lockup where the front lights were showing sync and activity but no surf was able to be had. After rebooting the Rogers modem (white Hitron monolith) my RT-AX88U router started processing the magic sand again. I haven't ever had anything like this happen before so I will keep a close eye on it over the weekend and report if anything else is going on.
01-15-2021 06:15 PM
I'm in North Oshawa.
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 591000000 | QAM256 | 3.099 | 7 | 38.983 |
2 | 597000000 | QAM256 | 3.200 | 8 | 39.397 |
3 | 603000000 | QAM256 | 3.599 | 9 | 38.983 |
4 | 849000000 | QAM256 | 1.400 | 2 | 37.636 |
5 | 855000000 | QAM256 | 1.500 | 3 | 37.636 |
6 | 861000000 | QAM256 | 2.700 | 4 | 37.355 |
7 | 579000000 | QAM256 | 2.700 | 5 | 40.366 |
8 | 585000000 | QAM256 | 2.400 | 6 | 38.983 |
9 | 279000000 | QAM256 | -1.700 | 1 | 38.605 |
10 | 609000000 | QAM256 | 2.900 | 10 | 40.366 |
11 | 615000000 | QAM256 | 3.400 | 11 | 40.366 |
12 | 621000000 | QAM256 | 3.599 | 12 | 38.983 |
13 | 633000000 | QAM256 | 3.700 | 13 | 40.366 |
14 | 639000000 | QAM256 | 2.900 | 14 | 38.605 |
15 | 645000000 | QAM256 | 3.299 | 15 | 38.983 |
16 | 651000000 | QAM256 | 3.799 | 16 | 38.983 |
17 | 657000000 | QAM256 | 3.299 | 17 | 38.983 |
18 | 663000000 | QAM256 | 3.400 | 18 | 40.366 |
19 | 669000000 | QAM256 | 3.599 | 19 | 38.983 |
20 | 675000000 | QAM256 | 3.599 | 20 | 38.983 |
21 | 681000000 | QAM256 | 3.900 | 21 | 38.605 |
22 | 687000000 | QAM256 | 3.400 | 22 | 38.605 |
23 | 693000000 | QAM256 | 3.200 | 23 | 38.605 |
24 | 699000000 | QAM256 | 3.400 | 24 | 38.983 |
25 | 705000000 | QAM256 | 3.299 | 25 | 38.983 |
26 | 711000000 | QAM256 | 2.099 | 26 | 38.983 |
27 | 717000000 | QAM256 | 1.400 | 27 | 38.983 |
28 | 723000000 | QAM256 | 1.799 | 28 | 38.605 |
29 | 825000000 | QAM256 | 0.500 | 29 | 38.605 |
30 | 831000000 | QAM256 | 1.200 | 30 | 38.983 |
31 | 837000000 | QAM256 | 0.900 | 31 | 38.983 |
32 | 843000000 | QAM256 | 1.099 | 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.400002 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 25900000 | 64QAM | 47.020 | 2 | 6400000 |
2 | 38700000 | 64QAM | 48.270 | 4 | 6400000 |
3 | 32300000 | 64QAM | 47.020 | 3 | 6400000 |
4 | 21100000 | 64QAM | 46.010 | 1 | 3200000 |
5 | 0 | QAM_NONE | - | --- | 6400000 |
6 | 0 | QAM_NONE | - | --- | 6400000 |
7 | 0 | QAM_NONE | - | --- | 6400000 |
8 | 0 | QAM_NONE | - | --- | 6400000 |
Channel Index | State | lin Digital Att | Digital Att | BW (sc's*fft) | Report Power | Report Power1_6 | FFT Size |
0 | OPERATE | 0.2474 | 9.2213 | 9.6000 | 54.7815 | 47.0000 | 2K |
1 | DISABLED | 0.0000 | 0.0000 | 0.0000 | 0.0000 | 0.0000 | 2K |
01-19-2021 02:10 PM
The only thing I see with this new Firmware is I don't see any DOCSIS Event logs? I rebooted the Modem 3 to 4 times.
01-19-2021 04:33 PM
My modem rebooted this early morning, around 4:00am. I also had intermittent outages this morning around 10:00am and I had to physically unplug the modem and plug it back in. I'm not sure if this is a firmware issue or due to OFDM/OFDMA enabled on my modem and testing is being done. Do you have any insight as to the latter? I know I cannot call Rogers tech support since I am a beta tester but I may need to be removed from the program as my son does online learning and cannot tolerate the outages during the day.
01-19-2021 04:38 PM
Thanks for the feedback on 7.1.1.35 provided so far, keep it coming.
To confirm in 7.1.1.35 we did not implement a fixes for either of:
RogersIan
01-19-2021 04:44 PM
We will be rolling out new code for our CGN3AC trial users over the next couple of days.
The new build 4.5.8.42 has 2 changes which are both geared toward the backend management.
Once you have had some time with the new code please let us know what you think.
Thanks,
RogersIan
01-20-2021 09:00 AM
Hi, looking at my modem AC it's running trial 4.5.8.43. Not sure if you had a typo or my modem will be downgraded?
01-29-2021 12:24 PM
I'm still on 7.1.1.33 is this to be expected?
01-31-2021 12:43 PM - edited 01-31-2021 12:51 PM
02-01-2021 12:29 AM - edited 02-01-2021 12:34 AM
@lethalsniper I don't recall if you have an OFDMA upstream channel running, but I don't believe so. In that case, the upstream channels on both modems are using 6 Mhz wide QAM channels.
The downstream channels are a different story. The CGN3ACSMR will be using twenty four 6 Mhz wide channels. The CODA-4582 will be using the OFDM channel with somewhere under 4096 sub-carriers, don't know the exact number. Using the downstream OFDM channel will result in a greater number of transmit time slots, however, the downstream loads have increased significantly, which counteracts the increase in transmit time slots.
Now, also keep in mind that Rogers may have assigned all of the OFDM capable modems to the OFDM channel, significantly decreasing the load on the QAM channels. I don't know if there is a mixed mode in operation whereby the modems use both OFDM and QAM channels for customer data or if the OFDM channel has the majority load of the customer data, for those customers who are using an OFDM capable modem. That would also explain why customers are see decreasing performance as the overall OFDM load has increased significantly since March 2017.
Looking back on some test data, there is a three to four times increase in the downstream ping times from the CMTS. I'll have to do a little more testing to get a better idea of what that number is, but, there is a significant increase in that CMTS to modem time frame, despite the use of the OFDM channel.
The end goal of the cable operators will be to remove the QAM channels and reassign the frequencies to OFDM channels, significantly increasing the throughput of the CMTS to modem portion of the system. That will take a long time to accomplish, just like removing analogue tv channels took a long time to remove. Its possible to run custom OFDM configurations around the QAM channels but I don't know if any cable operator is actually doing it.
For what its worth, and I've said this in the past, I think your apartment building has a problem with its cable system, and no amount of complaining on the forum will fix that. You need to be speaking with the building management and owners to change out the cabling and basement MDU's. The goal should be to install fibre. The copper cabling could probably be left in place and abandoned instead of paying to remove it. Pull fibre and install fibre ports in all apartments.
02-01-2021 12:58 AM
02-01-2021 01:17 AM
The OFDM channel subcarriers are greatly reduced in signal levels compared to the QAM channels. So, if there is a problem with broadband noise in the buildings cable system across the OFDM band, or significant noise in certain OFDM frequencies, you would probably end up with greater data losses and a need to retransmit data that was lost. That would lead to greater jitter numbers as the ping times would or could be longer depending on what protocol was used, we're talking about ping to ping times which is used in the jitter calculation.
OFDM is very robust in comparison to the QAM channels due to additional error correction, but, I don't think its indestructible. Taking OFDM out of the lab and into the real world probably has its challenges, the greatest probably being system noise.