http://www.pingtest.net/result/156314187.png
My numbers are gone crazy again:
Downstream Overview
| Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
| 1 | 633000000 | 256QAM | 9.100 | 37 | 40.366 |
| 2 | 609000000 | 256QAM | 9.100 | 34 | 38.983 |
| 3 | 615000000 | 256QAM | 9.400 | 35 | 40.366 |
| 4 | 621000000 | 256QAM | 9.500 | 36 | 38.983 |
| 5 | 603000000 | 256QAM | 8.700 | 33 | 38.983 |
| 6 | 639000000 | 256QAM | 8.100 | 38 | 38.983 |
| 7 | 645000000 | 256QAM | 7.300 | 39 | 38.983 |
| 8 | 651000000 | 256QAM | 7.100 | 40 | 38.983 |
| 9 | 657000000 | 256QAM | 7.700 | 41 | 38.605 |
| 10 | 663000000 | 256QAM | 8.700 | 42 | 38.605 |
| 11 | 669000000 | 256QAM | 9.600 | 43 | 38.605 |
| 12 | 675000000 | 256QAM | 9.800 | 44 | 38.605 |
| 13 | 681000000 | 256QAM | 10.000 | 45 | 38.605 |
| 14 | 687000000 | 256QAM | 9.800 | 46 | 38.605 |
| 15 | 693000000 | 256QAM | 9.900 | 47 | 38.983 |
| 16 | 699000000 | 256QAM | 9.300 | 48 | 37.356 |
| 17 | 705000000 | 256QAM | 9.700 | 49 | 38.983 |
| 18 | 711000000 | 256QAM | 9.900 | 50 | 37.356 |
| 19 | 717000000 | 256QAM | 10.400 | 51 | 37.636 |
| 20 | 723000000 | 256QAM | 10.800 | 52 | 37.636 |
| 21 | 825000000 | 256QAM | 9.600 | 53 | 37.356 |
| 22 | 831000000 | 256QAM | 10.600 | 54 | 37.636 |
| 23 | 837000000 | 256QAM | 10.400 | 55 | 38.605 |
| 24 | 843000000 | 256QAM | 9.700 | 56 | 37.636 |
Upstream Overview
| Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
| 1 | 38596000 | ATDMA - 64QAM | 47.000 | 3 | 3200000 |
| 2 | 30596000 | ATDMA - 64QAM | 46.750 | 1 | 6400000 |
| 3 | 23700000 | ATDMA - 64QAM | 46.750 | 2 | 6400000 |
Seeing a proper ping response from the Windows 7 pc now?
When you run pingplotter, have a look at the upper right hand corner to see if it shows that its running as a Windows service. If so, that means that it collects data in the background. I found that when it was configured that way, I ended up with errors from the router or modem. To cure that situation, rerun the installation again, but don't check the bottom installation option which is to load the background service. Load Pingplotter as a normal application then reboot the pc. Hopefully this will resolve the problem if Pingplotter is loaded as a Windows service.
@Hybrid_Noodle wrote:No worries @RogersDave got to have some fun in this to make sure we all dont go crazy.
Going on complete and utter speculation (and looking at the Hitron residental gateway product line) I would expect it to be either the CGNVM-3580, CODA-4582 or the CODA-4580 based on the new DOCSIS 3.1 standard as I wouldnt expect Rogers to update the modem to another DOCSIS 3.0 standard when they have enough of those out in the wild.
The CGNVM-3580 also uses the Intel Puma 6 chipset so would like to hope that would also not be used as we would be back in the same set of issues as we currently see on the current set of modems.
CODA-4582 has support for MoCA which the CODA-4580 does not so I would hope that we would be looking at the CODA-4582 as the next modem in line for Rogers to validate/test/release into the world.
Excellent job @Hybrid_Noodle on the deduction. I can now confirm that the new gateway is in fact a Hitron CODA-4582 based on Intel Puma 7 chipset. I ran a standard set of latency performance testing (ICMP, ICMPv6, TCP, UDP) and I can say that it is night and day when compared to the previous Intel Puma 6 based modems.
From a technical perspective, there is still a lot of testing going on and some enhancements are already planned to be deployed between not and the end of January. For example, at the moment, this gateway does not have IPv6 enabled but it will get activated in the January release.
I promised @JohnBeaudin a Christmas gift so here it is 🙂 This gateway will be available in stores today and is the new default for Gigabit customers. Ignite 250u and Ignite Gigabit customers should be able to swap their existing gateway without issues. I believe other plans are eligible as well but I need to get confirmation on that.
Every Rogers store should have these gateways available today but it may become a hot commodity quickly. There are new shipments arriving weekly so if you can't get one of these, wait a few days and it should be available.
At the moment and until the end of January, I don't think I'll be able to push trial firmware to these gateways. Because we are working on getting software out as quickly as possible, the gateways are configured to update to a specific version on boot. I will however resume the firmware trial program on these at the end of January 2017.
The firmware trial program on existing gateways will continue along with the work with Intel and Hitron to improve the latency on Puma 6 based chipsets and provide other enhancements. I am hoping to get a new firmware version (4.5.8.28) soon but the Holidays might introduce some delays as well.
In any case, I have been slow at responding to messages from the Community lately because of all the work going on with the new gateway but I am now back in full force and ready to collect your feedback on this new modem.
Dave
@Datalink wrote:Fwiw, I have had previous discussions with @RogersDave regarding this beacon. I'd like to see it removed, but there is apparently a legitimate reason for its existence. So, some compromise will be necessary. Hopefully @RogersDave can provide an update on the progress of this issue.
Also fwiw, this is not a new problem. I'm not sure when it was first seen, .19, or .20 or perhaps even sooner. I don't use the modem's wifi so I wasn't keeping track of it.
The issue of the hidden SSID being broadcasted on the 2.4 GHz is high on my priority list to it requires some rework to be done on our side. I had a few meetings in the last couple of days explaining the impact of this hidden SSID and why it should be removed.
I can't say for sure if and when it will be removed but I'm working on it. Also, the new gateway doesn't broadcast this additional SSID.
Dave
@ValentynL wrote:How long, on average, does it take for the firmware to be pushed on the modem?
I was told 7 business days.
@ValentynL, normally yes. I usually push all the updates on Monday morning but work on the new gateway took a lot of my time.
I will be processing the pending firmware upgrade requests throughout the day today.
Dave
@lethalsniper wrote:
New modem ? Does it fix the latency higher pings? Is the fix coming in January ?
As I said, this new modem has MUCH better performance in terms of latency for ICMP, ICMPv6, TCP and UDP. These improvements are available today.
There are a few open items on this CODA-4582 that are being addressed with likely 2 firmware upgrades between now and the end of January. I'm sure the community here will provide a lot of feedback so we might have to make adjustments to this schedule.
On existing modems, work is in progress with Intel and Hitron. I heard that there should be a new Intel base code available this week. After that it will require Hitron to integrate and test the firmware before it's available to us. I'm hoping to have a firmware available before Christmas but it may wait until January.
Dave
@VivienM wrote:
I'm tempted to go pick one up, but one question: when you say IPv6 is not enabled, is that only in gateway mode? Or is there also no IPv6 in bridge mode?
That is an excellent question and I don't have the answer. I will ask the question and get back to you.
IPv6 will be fully enabled with software version 2.0.10.16 scheduled for deployment in January.
In theory you should see better ping times. In terms of IPV6, that depends if you play on an XBox One or not. If you use an XBox One, then it will use IPV6 if its available. If you play on anything else, and IPV6 is not required for the game, then there won't be any issues running the new modem.
@lethalsniper wrote:
So with this new modem will I see better pings when gaming even though IPv6 is not fully avail or would I still be better off with my older modem
Based on my own testing, you are far better off with the new modem. But if you prefer, you can also wait a couple of days, I'm sure there will be lots of reports posted here on the improvements.
Dave
-
937670 views
-
669 Likes
-
-
