10-12-2019 01:27 PM - last edited on 10-15-2019 02:04 PM by RogersMoin
i haven't been able to speed test higher than 500mbps with a wired connection, I am on a gigabit connection.
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 591000000 | 256QAM | 4.200 | 7 | 38.983 |
2 | 855000000 | 256QAM | 0.600 | 3 | 38.605 |
3 | 861000000 | 256QAM | 1.000 | 4 | 38.605 |
4 | 579000000 | 256QAM | 4.600 | 5 | 38.983 |
5 | 585000000 | 256QAM | 4.900 | 6 | 38.605 |
6 | 849000000 | 256QAM | 0.300 | 2 | 38.983 |
7 | 597000000 | 256QAM | 3.600 | 8 | 40.366 |
8 | 603000000 | 256QAM | 3.800 | 9 | 38.605 |
9 | 609000000 | 256QAM | 3.300 | 10 | 38.983 |
10 | 615000000 | 256QAM | 3.500 | 11 | 38.983 |
11 | 621000000 | 256QAM | 3.400 | 12 | 38.983 |
12 | 633000000 | 256QAM | 3.700 | 13 | 38.605 |
13 | 639000000 | 256QAM | 3.100 | 14 | 38.983 |
14 | 645000000 | 256QAM | 3.100 | 15 | 38.983 |
15 | 651000000 | 256QAM | 2.700 | 16 | 38.605 |
16 | 657000000 | 256QAM | 2.200 | 17 | 38.605 |
17 | 663000000 | 256QAM | 2.200 | 18 | 38.983 |
18 | 669000000 | 256QAM | 2.900 | 19 | 38.983 |
19 | 675000000 | 256QAM | 3.200 | 20 | 38.983 |
20 | 681000000 | 256QAM | 3.400 | 21 | 38.983 |
21 | 687000000 | 256QAM | 4.300 | 22 | 38.983 |
22 | 693000000 | 256QAM | 3.600 | 23 | 38.983 |
23 | 699000000 | 256QAM | 4.500 | 24 | 38.983 |
24 | 705000000 | 256QAM | 3.700 | 25 | 38.983 |
25 | 711000000 | 256QAM | 4.000 | 26 | 38.983 |
26 | 717000000 | 256QAM | 3.500 | 27 | 38.983 |
27 | 723000000 | 256QAM | 3.100 | 28 | 38.983 |
28 | 825000000 | 256QAM | 1.700 | 29 | 38.605 |
29 | 831000000 | 256QAM | 0.800 | 30 | 38.983 |
30 | 837000000 | 256QAM | 0.500 | 31 | 38.605 |
31 | 843000000 | 256QAM | 0.100 | 32 | 38.605 |
32 | 279000000 | 256QAM | -0.300 | 1 | 37.356 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | 4K | 275600000 | YES | YES | YES | 1.500000 |
1 | NA | NA | NO | NO | NO | NA |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 25300000 | ATDMA - 64QAM | 39.250 | 6 | 3200000 |
2 | 36996000 | ATDMA - 64QAM | 35.250 | 8 | 6400000 |
3 | 22100000 | ATDMA - 64QAM | 38.000 | 5 | 3200000 |
4 | 30596000 | ATDMA - 64QAM | 35.250 | 7 | 6400000 |
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 |
*Added Labels*
Solved! Solved! Go to Solution.
11-10-2019 12:20 PM - last edited on 11-10-2019 12:29 PM by RogersCorey
My speeds are slow I’m on gigabit getting 600mbps I think my docsis signals aren’t good plz check and fix
*Link removed for privacy reasons*
11-10-2019 02:08 PM
https://www.flickr.com/photos/185437315@N02/?
Docsis signals are shown
11-10-2019 03:55 PM
11-11-2019 09:46 AM
11-11-2019 11:16 AM
@AzaanKamran the top DOCSIS 3.0 channels (1 to 32) are fine. I wouldn't expect any issues with those, but, the modem isn't using the DOCSIS 3.0 downstream channels at the moment.
The DOCSIS 3.1 OFDM channel is the download channel in use. There isn't enough data presented in the user interface to know of that channel is operating within spec. That would require a call to tech support to determine.
The DOCSIS 3.0 upstream channels are all low, lower than normal for this modem which usually runs in the 30 to 32 dBmV range. That might not be a problem however, depending on the signal levels when they arrive at the neighbourhood node. They might still be well within spec.
Call tech support and ask the Customer Service Rep to run a signal check on the modem. Ask if the Downstream OFDM channel is operating within specification and ask if the upstream signal levels are within spec at the neighbourhood node.
I'm assuming that your in a house, which is connected to a neighbourhood node. If you live in an apartment/condo/highrise, then your building could have its own Multiple Dwelling Unit, or several of them, to service the apartments in the building. That might explain the low upstream levels. If that is the case, then the question of the upstream levels becomes, "are they acceptable when they arrive at the MDU?"
One last question at this point, how are you measuring the data rate, via ethernet or wifi. If its via wifi, then you need to run a speedtest via ethernet with a pc/laptop which will run download rates in the order of 930/940 Mb/s.
If you're testing to this point has been with wifi, don't call tech support until you've had a chance to run a test via ethernet.
11-11-2019 11:44 AM
11-11-2019 11:46 AM - edited 11-11-2019 11:49 AM
Yes, but, is that via ethernet or via wifi?
Can you have a look at the following post and if you're running a Windows pc or laptop, check the current TCP Receive Window setting. You could set that to "Experimental", reboot the pc or laptop and then rerun the speedtest to see if that makes a difference in the results.
https://support.microsoft.com/en-us/help/4494445/tcp-receive-auto-tuning-level-feature-in-windows
11-11-2019 11:49 AM
11-11-2019 11:52 AM
11-11-2019 11:53 AM - edited 11-11-2019 11:56 AM
Ok, understand, you're using the wifi app to run a speedtest within the modem. Do you happen to have any ethernet connected devices that can be used to run a speedtest, and that will support 930/940 Mb/s?
I'd call tech support and ask the CSR to run a signal check to see what turns up. My personal opinion is that the upstream levels are too low, but, its a question of whether or not they are acceptable at the neighbourhood node.
Are you running any other Rogers services such as Cable TV or Home Phone, and if so, would you happen to know if there is an amplifier connected to the cable system where the cable enters the home?
Are you in a house, or apartment/condo/highrise building?
Edit: Ok, so a tech is arriving today. Hopefully he or she will be able to see what the problem is. Nope, I'm not a technician, just a Forum volunteer, so I and the other volunteers don't have access to any of Rogers systems.
11-11-2019 11:55 AM
11-11-2019 11:57 AM
11-11-2019 11:57 AM
11-11-2019 12:00 PM - edited 11-11-2019 12:01 PM
Ok, understand. Normally the Cable Modem Termination System (CMTS) would issue a command to the modem to increase the transmit signal level out of the modem if the received signal level at the neighbourhood node was too low, which I suspect it is. So, the fact that the modem is still running at a low output power level is very odd. That's not a normal occurrence. Have you already swapped modems by any chance?
11-11-2019 12:01 PM
11-11-2019 12:02 PM
11-11-2019 12:15 PM
Thats hard to say. I'd suspect the modem is at fault, but, swapping with another modem will prove or disprove that theory. The tech support comments on "SNR and tx power" runs in both directions, firstly from the neighbourhood node to the modem, using the downstream DOCSIS 3.1 OFDM channel, and secondly, from the modem to the neighbourhood node using the four DOCSIS 3.0 upstream channels.
If the downstream OFDM channel wasn't running correctly, that would or could cause slow data rates. As I indicated above, the user interface doesn't present all of the data required to assess the OFDM channel, so, that requires tech support or a field tech to look at the parameters to see if there is a problem with the OFDM channel.
If the upstream channels are not arriving at the neighbourhood node with adequate signal levels or signal to noise ratios, then that could affect the downstream rates as the upstream responses might not be received and would have to be retransmitted by the modem. That retransmission could result in slower downstream rates.
So, the field tech will have to asses what the problem is and come up with the correct solution.
11-14-2019 03:41 PM - last edited on 11-14-2019 04:16 PM by RogersMaude
I recently upgrade my 150 unlimited Ignite internet to Rogers Ignite Gigabit, and receive a big disappointment. My Wi-Fi download speed now is :
1- Asus laptop - 34mbps
2- Samsung 7s edge - 64 mbps
3- Cubot power - 54 mbps
4- ipad 5th generation - 150 mbps
5- PC with AORUS Z2370 gaming 5 Motherboard - 180 mbps (Wi-Fi), 530 mbps (Ethernet).
So only the direct line Ethernet is somewhat approaching hi- speed while all WIFI devices got very low speed.
Rogers service came twice to look at the problem and said that was normal ! I said this was the worst sale ever for a Rogers service.
I need to mention that in Jan. 2018, I had also bought a Rogers Ignite Gigabit UNLTD plan and used it for over a year with much better results (Wifi consistently over 500 mbps on all devices above), before going back to 150 Ignite Internet for a few months.
So my question is : What has happened to Rogers Wifi download speed ?
11-15-2019 03:43 PM
Hello, @vocao
Welcome to the Rogers Community Forums! 😃
It certainly is strange that you are experience such a huge difference in speeds from Ethernet to Wi-Fi. Ethernet is definitely faster but from the results that you've provided, it seems like your devices are connecting to the 2.4GHz band and not the 5GHz band.
Do you know if you have Band Steering enabled on the Gateway? If yes, it can be difficult to determine which band you are connected to. For testing purposes, please disable Band Steering and connect to the Network designated -5G. You may need to edit the network name after disabling Band Steering.
Let us know if the speeds are still low via Wi-Fi after trying this.
RogersTony
11-17-2019 08:23 PM
I'm also on Gigabit connection, can't get above 200 Mbps on cat6 wired.
Can anyone of Rogers tech here tell me if anything's wrong with my connection ?
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 609000000 | 256QAM | -1.300 | 10 | 38.983 |
2 | 849000000 | 256QAM | 0.700 | 2 | 40.366 |
3 | 855000000 | 256QAM | 0.800 | 3 | 40.946 |
4 | 861000000 | 256QAM | 1.200 | 4 | 40.946 |
5 | 579000000 | 256QAM | -1.900 | 5 | 38.605 |
6 | 585000000 | 256QAM | -1.400 | 6 | 38.983 |
7 | 591000000 | 256QAM | -1.000 | 7 | 38.983 |
8 | 597000000 | 256QAM | -1.000 | 8 | 38.983 |
9 | 603000000 | 256QAM | -1.000 | 9 | 38.983 |
10 | 279000000 | 256QAM | -2.500 | 1 | 38.983 |
11 | 615000000 | 256QAM | -1.300 | 11 | 38.983 |
12 | 621000000 | 256QAM | -1.500 | 12 | 40.366 |
13 | 633000000 | 256QAM | -1.400 | 13 | 38.983 |
14 | 639000000 | 256QAM | -1.500 | 14 | 38.983 |
15 | 645000000 | 256QAM | -1.200 | 15 | 38.983 |
16 | 651000000 | 256QAM | -1.200 | 16 | 38.605 |
17 | 657000000 | 256QAM | -1.300 | 17 | 38.605 |
18 | 663000000 | 256QAM | -1.500 | 18 | 40.366 |
19 | 669000000 | 256QAM | -1.500 | 19 | 38.983 |
20 | 675000000 | 256QAM | -1.300 | 20 | 38.983 |
21 | 681000000 | 256QAM | -1.000 | 21 | 38.983 |
22 | 687000000 | 256QAM | -0.800 | 22 | 40.366 |
23 | 693000000 | 256QAM | -1.100 | 23 | 38.983 |
24 | 699000000 | 256QAM | -1.200 | 24 | 38.983 |
25 | 705000000 | 256QAM | -2.100 | 25 | 38.983 |
26 | 711000000 | 256QAM | -2.200 | 26 | 38.983 |
27 | 717000000 | 256QAM | -2.000 | 27 | 38.983 |
28 | 723000000 | 256QAM | -1.400 | 28 | 38.983 |
29 | 825000000 | 256QAM | 0.500 | 29 | 40.366 |
30 | 831000000 | 256QAM | 0.400 | 30 | 40.946 |
31 | 837000000 | 256QAM | 0.300 | 31 | 40.946 |
32 | 843000000 | 256QAM | 0.200 | 32 | 40.366 |
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 | -1.099998 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 38596000 | ATDMA - 64QAM | 36.000 | 3 | 3200000 |
2 | 30596000 | ATDMA - 64QAM | 32.250 | 1 | 6400000 |
3 | 23700000 | ATDMA - 64QAM | 32.000 | 2 | 6400000 |
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 |
11-17-2019 09:32 PM - edited 11-17-2019 10:27 PM
@osh168 there's nothing that stands out as being an issue, however, your modem is using a DOCSIS 3.1 OFDM channel for the downstream data and the user interface doesn't present all of the data for that OFDM channel. Call tech support and ask the Customer Service Rep to run a signal check on your modem. Ask specifically if the OFDM channel parameters are within spec and what the QAM number is for the QAM channel. It should be running at 1024.
Also, have a look at the following Microsoft support page regarding the Windows TCP Receive Window Auto-tuning:
https://support.microsoft.com/en-ca/help/4494445/tcp-receive-auto-tuning-level-feature-in-windows
I had to set this to experimental recently to get the data rate for one pc back to where it should be. Here's another user's results with this as well:
I think that Windows 10 has been causing issues with this setting, so, its worth having a look at.
Is your computer connected directly to the modem or does the data path run through any switches or house cabling?
Edit: What Software (firmware) version is loaded on your modem, as indicated on the STATUS page of the modem? That is displayed when you log into the modem.