03-01-2017 08:43 PM
Can't test CODA limits. Don't have Gigabit account 😉
03-02-2017 09:46 AM
@User1445713 wrote:If the CODA modem is rated 1 Gigabit and beyond then I don't see why we couldn't see 1 gigabit download speed. The modem should be the last bottleneck on the larger scale network.As far as computer every one is different but new modern low power thin notebooks don't have problems with Gigabit speeds. I have 2017 Dell XPS 13" 3360, low power i7 2-core (15 Watts) CPU with solid state hard drive M.2 PCIe connection type. I can easily get 1Gb/s consistent speeds on internal network downloading file from NAS drive (107 megabytes per second on the Windows file copy chart) 35% CPU load. This is using LAN Gigabit Dell adapter to USB 3.1 Type C (Thunderbolt) as well as using Ebay inexpensive USB 3.0 to Gigabit adapter. I'm getting 200 Mb/s speeds using the same test on wireless. Laptop AC card is rated 866.7 Mbps and CODA 1733 Mbps.Laptop can typically run all day on battery without even turning the fan on similar to tablets and phones.
Can't test CODA limits. Don't have Gigabit account 😉
I would invite you over but ever since I got bumped from .19 to .23 and then .24 shortly after my speeds went from 925-950 down to 750 down just because of the firmware upgrade. I would be more than happy to stick with .19 if issue wasnt for it no working with DLINK hardware in bridge mode.
03-02-2017 11:40 AM
@CommunityHelps @RogersDave
Ok. So everyone getting all those strange errors, Im telling you, TRY a factory reset, by unplugging all your devices from the LAN connections, and press the reset button on the bank with a paper clip for about 30secs then release.
leave all you connections un plugged, let the modem boot, it will eventually stating flashing your download and upload lights green, and it will redownload the v.24 firmware and reboot again.
Then try plugging in 1 device, a laptop or desktop to the wired LAN if you can, and do the inital modem setup with only that device connected, and then check your speeds using; https://speedcheck.rogers.com/en
ALSO NOTE, cat5 cables may not provide gigabit connections, even on short length, to guaruntee you are getting gigabit connection, use only cat6 cables and check your ethernet card when connected for either 100mbps connection or 1.0gbps.
If your using cat6 and all this doesnt work, try replacing the modem again to the new dual black dot modems, which I did myself, and then boot up the same way, only with one device and test.
My connection seems to be pretty good since i did this, I only went down once so far, and im still wokring on that with Rogers, as it seems any long-term connection sustained, seems to slow over time and then fail. My IP phone wont make more than about a 2 min call with hanging up, and my Xbox One S tried to download and install Star Wars Battlefront, approx. 42gb file, and it started at about 220mbps, but within 1 min, it dropped to 150mbps, then 75mpbs, then about 20mbps, then less than 1mpbs, litterally downloading at kbps for about 15secs, then it stopped, paused the download/install, and all my devices lost internet, but not IP adresses, and I was forced to do a manual reboot.
It seems, for the most part, they have stabilized the connections, as long as there isnt a sustained connection, lol, which is hilarous and just great for all us gamers and people with home offices and seniors with IP lifeProtect devices... *sarcasm*
Anyways, I hope that helps some people get to where they can be stable for the most part until Rogers can determine what the issue is....
03-03-2017 03:35 AM
03-03-2017 08:16 AM - edited 03-03-2017 08:17 AM
For those looking for an overall service experience rather than determining their local speed to Rogers' infrastructure, I would advise to run tests from this site: here.
03-03-2017 09:37 AM
@blues_clues wrote:For those looking for an overall service experience rather than determining their local speed to Rogers' infrastructure, I would advise to run tests from this site: here.
Just tried this and it gave me less than stellar results (which I know are way below avg.) here at work and only completed 2 out of the 4 tests.
03-03-2017 10:54 AM
I tried the sourceforge.net/speedtest on 250/20 with the original Coda Modem
Latency: 65ms
Download Speed: 363 mbs
Upload Speed: 30.8 mbs
Packet loss: 0%
The test rated my connection 4.4/5
On speedtest.net I usually get 330 down and 22 up..
03-03-2017 12:10 PM - edited 03-03-2017 12:14 PM
Sooooo it took around 36 hours but Rogers finally fixed their provissioning servers and got my new double-black-dot CODA-4582 up and running. I see it is on firmware 2.0.10.24. I never requested a trial firmware so I guess .24 is the latest firmware being pushed out to both regular users and trial firmware users? If thats the case, I guess there is no point in me asking to be added to the CODA trial firmware program right now, eh?
Here are my signal readings:
Downstream Overview Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB) 1 621000000 256QAM 2.900 12 36.610 2 561000000 256QAM 3.700 2 36.387 3 567000000 256QAM 4.000 3 36.387 4 573000000 256QAM 4.400 4 36.387 5 579000000 256QAM 4.100 5 36.610 6 585000000 256QAM 3.900 6 36.387 7 591000000 256QAM 4.000 7 36.387 8 597000000 256QAM 4.100 8 36.387 9 603000000 256QAM 4.400 9 36.610 10 609000000 256QAM 4.100 10 36.610 11 615000000 256QAM 3.600 11 36.610 12 555000000 256QAM 3.700 1 36.610 13 633000000 256QAM 2.900 13 35.780 14 639000000 256QAM 2.400 14 35.780 15 645000000 256QAM 2.000 15 35.780 16 651000000 256QAM 1.700 16 35.780 17 657000000 256QAM 2.300 17 35.780 18 663000000 256QAM 2.600 18 36.610 19 669000000 256QAM 2.800 19 36.610 20 675000000 256QAM 2.800 20 36.610 21 681000000 256QAM 3.000 21 36.387 22 687000000 256QAM 3.200 22 36.610 23 693000000 256QAM 3.200 23 36.387 24 699000000 256QAM 3.100 24 36.387 25 705000000 256QAM 2.100 25 35.780 26 711000000 256QAM 2.000 26 35.780 27 717000000 256QAM 1.700 27 35.084 28 723000000 256QAM 1.600 28 34.926 29 825000000 256QAM 0.500 29 32.321 30 831000000 256QAM 0.200 30 31.994 31 837000000 256QAM 0.300 31 31.915 32 843000000 256QAM 0.100 32 31.915 OFDM Downstream Overview 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 5.500000 Upstream Overview Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth 1 30596000 ATDMA - 16QAM 27.250 1 6400000 2 38595824 ATDMA - 16QAM 29.250 3 3200000 3 23700000 ATDMA - 16QAM 26.250 2 6400000 OFDM/OFDMA Overview 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
I should mention I took out the "3db SAT4203 5-42MHz return path attenuator" because WITH it I was getting around 12-15mbit upload speeds (albiet the signal was showing around 30-32 dBmV for port ID 1 through 3) but WITHOUT it I am getting a solid 18-20mbit upload speed pretty much all the time. Strange... you'd figure the higher signal level would lead to better speeds (I assume the higher signal the better for upstream?)
My upload/download LED lights on the CODA modem are blue still, so that means I'm on DOCSIS 3.0, right? They'll turn purple when it's 3.1? Will the OFDM/OFDMA Overview above change the "State" from DISABLED to ENABLED also when I'm on DOCSIS 3.1? Just want to learn so I can recognize why my speeds start getting bad since I see so many issues with 3.1 over in the "CODA-4582 - Open Issues for Investigation" thread lol...
03-03-2017 12:56 PM
Odd thing just happened right now with my Coda modem. After losing internet on the work laptop, I went down to see the modem and all green lights with up/down flashing green. Thought it was a firmware update so waited. After more than 10 mins, logged back into the modem and same version .24 but lots of errors in the log file:
5 03/03/2017 12:41:33 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 6 03/03/2017 12:41:34 82000300 critical Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 7 03/03/2017 12:41:34 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 8 03/03/2017 12:41:34 82000300 critical Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 9 03/03/2017 12:41:34 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 10 03/03/2017 12:41:34 82000300 critical Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 11 03/03/2017 12:41:34 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 12 03/03/2017 12:43:31 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 13 03/03/2017 12:43:37 82000900 warning B-INIT-RNG Failure - Retries exceeded;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 14 03/03/2017 12:45:02 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 15 03/03/2017 12:45:10 82000900 warning B-INIT-RNG Failure - Retries exceeded;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 16 03/03/2017 12:46:39 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 17 03/03/2017 12:46:42 82000900 warning B-INIT-RNG Failure - Retries exceeded;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 18 03/03/2017 12:48:03 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 19 03/03/2017 12:48:27 90000000 warning MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1; 20 03/03/2017 12:48:34 84000700 warning RCS Partial Service;CM-MAC=;CMTS-MAC=00:17:10:91:66:82;CM-QOS=1.1;CM-VER=3.1;
Seems ok now after this incident. First time this happened while I was using the internet since the upgrade to .24. Was it some maintenence on the network?
03-03-2017 06:46 PM
@trafsta your upload signals are very low, with the new CODA modems upload signals are generally lower than the old CGN 3 Modems, but they still should be above 30. I would call tech support and see what they say. They can check the upload SNR levels, which we cannot see when we login to the modem.