FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
I Plan to Stick Around
Posts: 315

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial


@JohnBeaudin wrote:

I am really looking forward to OFDMA , is there other people that now have 4 upstream channel? 

 

mine is still only 3.


Still 3 here:

 

Upstream Overview

Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandwidth
130596000ATDMA - 64QAM38.25016400000
238596000ATDMA - 64QAM42.25033200000
323700000ATDMA - 64QAM38.75026400000
Microsoft® MVP Windows Insider - Windows Security
I'm a Reliable Contributor
Posts: 617

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

Are we getting close to the new beta firmware? 

Product Manager
Product Manager
Posts: 26

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

 

@mcsandy @RyzenFX .37T2 has been scrapped. It was our initial Band Steering build, but we found issues with the code which prevented its release.

 

The new code currently in test will be our next release.

 

@JohnBeaudin No release date I apologize. The code brings a few big changes so we are taking our time with testing.

@Datalink  Good news the Guest network issue where clients attempting to connect receive an error on the first try looks to be resolved. 

 

 

Resident Expert
Resident Expert
Posts: 6,222

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

@RogersIan does this next release also bring in the frequency extension up to 1.2 Ghz?  



I'm a Reliable Contributor
Posts: 617

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

Not much activity for the past 2 weeks, Let's hope for more action in March! 

Fingers crossed for the new firmware.

I Plan to Stick Around
Posts: 21

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

I wish to be removed from the firmware trials.  Thank you.

 

aube

 
Highlighted
Moderator
Moderator
Posts: 1,542

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

Hello, @aube.

 

We appreciate your participation in the firmware trial. We can assist in excluding your modem from the trial; please send us a PM at @CommunityHelps

 

Cheers,

RogersMoin

I'm a Reliable Contributor
Posts: 617

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

@RogersIan

 

It's been almost 5 weeks since your last post, are we getting closer to deploying the firmware to beta users?

I Plan to Stick Around
Posts: 11

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

This still happens, TX/RX, SNR is all good, the fact it seems to happen to the CMTS gateway interface im connected to seems to be it's not my signal or cabling here...

 

Since this modem runs Linux I'd be saddened for any issues with the kernel version.

 

That said, I doubt its any signal issues.

 

Software/firmware build: 2.0.10.36T6


$ ping 99.228.0.1  
PING 99.228.0.1 (99.228.0.1) 56(84) bytes of data.
64 bytes from 99.228.0.1: icmp_seq=1 ttl=63 time=14.3 ms
64 bytes from 99.228.0.1: icmp_seq=2 ttl=63 time=9.22 ms
64 bytes from 99.228.0.1: icmp_seq=3 ttl=63 time=7.73 ms
64 bytes from 99.228.0.1: icmp_seq=4 ttl=63 time=16.3 ms
64 bytes from 99.228.0.1: icmp_seq=5 ttl=63 time=9.95 ms
64 bytes from 99.228.0.1: icmp_seq=6 ttl=63 time=8.90 ms
64 bytes from 99.228.0.1: icmp_seq=7 ttl=63 time=9.94 ms
64 bytes from 99.228.0.1: icmp_seq=8 ttl=63 time=9.10 ms
64 bytes from 99.228.0.1: icmp_seq=9 ttl=63 time=8.24 ms
64 bytes from 99.228.0.1: icmp_seq=10 ttl=63 time=9.64 ms
64 bytes from 99.228.0.1: icmp_seq=11 ttl=63 time=9.65 ms
64 bytes from 99.228.0.1: icmp_seq=12 ttl=63 time=9.89 ms
64 bytes from 99.228.0.1: icmp_seq=13 ttl=63 time=74.4 ms
64 bytes from 99.228.0.1: icmp_seq=14 ttl=63 time=17.4 ms
64 bytes from 99.228.0.1: icmp_seq=15 ttl=63 time=7.91 ms
64 bytes from 99.228.0.1: icmp_seq=16 ttl=63 time=9.69 ms
64 bytes from 99.228.0.1: icmp_seq=17 ttl=63 time=11.1 ms
64 bytes from 99.228.0.1: icmp_seq=18 ttl=63 time=10.6 ms
64 bytes from 99.228.0.1: icmp_seq=19 ttl=63 time=8.84 ms
64 bytes from 99.228.0.1: icmp_seq=20 ttl=63 time=9.30 ms
64 bytes from 99.228.0.1: icmp_seq=21 ttl=63 time=8.84 ms
64 bytes from 99.228.0.1: icmp_seq=22 ttl=63 time=31.8 ms
64 bytes from 99.228.0.1: icmp_seq=23 ttl=63 time=16.10 ms
64 bytes from 99.228.0.1: icmp_seq=24 ttl=63 time=9.81 ms
64 bytes from 99.228.0.1: icmp_seq=25 ttl=63 time=9.86 ms
64 bytes from 99.228.0.1: icmp_seq=26 ttl=63 time=8.84 ms
64 bytes from 99.228.0.1: icmp_seq=27 ttl=63 time=8.97 ms
64 bytes from 99.228.0.1: icmp_seq=28 ttl=63 time=8.79 ms
64 bytes from 99.228.0.1: icmp_seq=29 ttl=63 time=10.7 ms
64 bytes from 99.228.0.1: icmp_seq=30 ttl=63 time=10.4 ms
64 bytes from 99.228.0.1: icmp_seq=31 ttl=63 time=7.01 ms
64 bytes from 99.228.0.1: icmp_seq=32 ttl=63 time=8.85 ms
64 bytes from 99.228.0.1: icmp_seq=33 ttl=63 time=7.79 ms
64 bytes from 99.228.0.1: icmp_seq=34 ttl=63 time=10.8 ms
64 bytes from 99.228.0.1: icmp_seq=35 ttl=63 time=8.81 ms
64 bytes from 99.228.0.1: icmp_seq=36 ttl=63 time=8.88 ms
64 bytes from 99.228.0.1: icmp_seq=37 ttl=63 time=10.7 ms
64 bytes from 99.228.0.1: icmp_seq=38 ttl=63 time=18.10 ms
64 bytes from 99.228.0.1: icmp_seq=39 ttl=63 time=41.10 ms
64 bytes from 99.228.0.1: icmp_seq=40 ttl=63 time=7.87 ms
64 bytes from 99.228.0.1: icmp_seq=41 ttl=63 time=10.9 ms
64 bytes from 99.228.0.1: icmp_seq=42 ttl=63 time=9.93 ms
64 bytes from 99.228.0.1: icmp_seq=43 ttl=63 time=13.0 ms
64 bytes from 99.228.0.1: icmp_seq=44 ttl=63 time=11.7 ms
64 bytes from 99.228.0.1: icmp_seq=45 ttl=63 time=11.7 ms
64 bytes from 99.228.0.1: icmp_seq=46 ttl=63 time=9.56 ms
64 bytes from 99.228.0.1: icmp_seq=47 ttl=63 time=8.00 ms
64 bytes from 99.228.0.1: icmp_seq=48 ttl=63 time=29.8 ms
64 bytes from 99.228.0.1: icmp_seq=49 ttl=63 time=16.6 ms
64 bytes from 99.228.0.1: icmp_seq=50 ttl=63 time=11.5 ms
^C
--- 99.228.0.1 ping statistics ---
50 packets transmitted, 50 received, 0% packet loss, time 114ms
rtt min/avg/max/mdev = 7.005/13.226/74.403/10.836 ms

The times are great, nothing unusual here

Product Manager
Product Manager
Posts: 26

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

 

 

We are still testing the CODA firmware. We have a reported issue where some devices experiece the 5GHz band freezing. Any type of roll out is on hold until we find out what is causing this.

 

@DatalinkUnfortunately extending the frequency range is not solely a firmware upgrade and would require additional changes to support

 

In regards to modems showing 4 upstream channels. The number of channels seen on devices is driven by what our network is able to support in that area. Since every area is different it's sometimes difficult to provide the same support in all areas all at once but as support is available we make sure to enable it as quickly as possible so our customers benefit from the improvements.

RogersIan