My numbers are gone crazy again:
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|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|
I belive it's an ICMP test? 'Engine' settings says 'ICMP using Windows DLL (default)'
Thanks for the help, btw. 🙂
@NBomb thats the same as running a ping using a ping command. Either one, pinging the modem, should give you 1 ms return times with an occasional high ping time. You can't rule out a possible bad modem 😞
Thanks for that comment, actually!
It made me think, and I decided to also try vanilla ping, and it's entirely timing out.
Pinging the modem from this computer (Windows 7, wired) is always timing out. Pinging from my macbook via wifi (through the router to the modem) shows behaviour as you described.
Update: Tried a bunch of things that had no effect, but a reboot of the modem seems to have cured that particular issue. Hmmm.
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.
Can anyone let me know if these modem stats look good?
Downstream Overview Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB) 1 693000000 256QAM -5.400 47 38.605 2 363000000 256QAM -3.800 10 38.983 3 369000000 256QAM -2.800 11 38.983 4 375000000 256QAM -2.700 12 38.983 5 381000000 256QAM -4.100 13 40.366 6 387000000 256QAM -2.300 14 40.366 7 393000000 256QAM -3.800 15 38.983 8 399000000 256QAM -3.600 16 38.605 9 405000000 256QAM -1.900 17 40.366 10 411000000 256QAM -3.400 18 38.983 11 417000000 256QAM -2.400 19 38.983 12 423000000 256QAM -1.200 20 40.366 13 429000000 256QAM -2.800 21 40.366 14 435000000 256QAM -1.600 22 40.946 15 441000000 256QAM -2.000 23 38.983 16 447000000 256QAM -2.700 24 40.366 17 555000000 256QAM -5.500 25 38.605 18 561000000 256QAM -5.300 26 38.605 19 567000000 256QAM -4.200 27 39.855 20 573000000 256QAM -5.500 28 38.983 21 579000000 256QAM -3.800 29 40.946 22 585000000 256QAM -3.100 30 40.366 23 591000000 256QAM -2.900 31 38.983 24 597000000 256QAM -2.500 32 40.946 25 603000000 256QAM -2.900 33 39.900 26 609000000 256QAM -2.700 34 39.500 27 615000000 256QAM -3.200 35 39.500 28 621000000 256QAM -4.300 36 39.500 29 681000000 256QAM -5.900 45 38.200 30 687000000 256QAM -6.600 46 38.200 31 357000000 256QAM -2.300 9 39.500 32 699000000 256QAM -7.700 48 37.900 Upstream Overview Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth 1 23700000 ATDMA - 64QAM 39.750 2 6400000 2 38596000 ATDMA - 64QAM 41.250 3 3200000 3 30596000 ATDMA - 64QAM 40.000 1 6400000
Yep, I remember messing with that in the past, but at the moment it's running in 'application' mode.
I'll look into this again in the future. 🙂
How long, on average, does it take for the firmware to be pushed on the modem?
I was told 7 business days.
It seems with the .27 firmware I'm getting LAN port disconnections until I restart the modem.
I'm using the CGN3ACR in bridge mode with a Portal router (https://portalwifi.com/) connected.
I've tried with my other router (TP-Link Archer c8) and see the same kind of issues.
Has anyone else seen this behaviour?
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 (22.214.171.124) 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.