CODA-4582 - Open Issues for Investigation

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
Highlighted
I'm an Advisor
Posts: 931

Re: CODA-4582 - Open Issues for Investigation


@rjmaxim wrote:

Just my 2cts of ignorance...isn't the interference only when you are running Coda in Gateway and also attach a router, when both units are broadcasting WiFi frequencies.....I cannot see how the Coda in Bridge mode can be affected by the WiFi frequencies of a router to slow it down. I am not a DataCom guru and would like to understand. Cheers...     

No, this is much lower level radio interference. Let me try to explain in a fairly non-technical way (I don't have the engineering background for a technical explanation)

 

Fundamentally, a cable network is essentially a collection of radio waves at different frequencies up to 860MHz packaged onto a piece of coax. Other things outside the cable network (e.g. TV broadcasters, cellular providers, etc.) also broadcast radio waves at the same frequency. One thing that's important with cable networks is that you shouldn't leave any coax sitting there not connected to anything because that piece of coax will act as an antenna for the radio waves around it - this is why, for example, you shouldn't have a 3-way splitter if you only have 2 devices, or why you shouldn't have an outlet connected if there's no device there.

 

The problem with the non-black dot modems (and I am not fundamentally sure that the black dot modems completely fully fix this) is that signals from 'outside' the coax are able to interfere with the signals on the coax before they reach the cable tuner. Those outside signals can come from... anywhere, i.e. including any neighbours' wifi, your own separate router in bridge mode, etc... and some part of the CODA between the coax cable and the tuner effectively acts as an antenna for them.

Highlighted
I've Been Around
Posts: 1

Re: CODA-4582 - Open Issues for Investigation

I just got the modem yesterday. Initially I though it was my pfsense firewall going all wonky on me. But after investigating, appears that the new CODA 4582 modem keeps on dropping the connection for which the remedy is to reboot the modem.

 

I suppose I'll also need to have the modem upgraded to the latest firmware. Anybody see improvements with the new firmware?

 

 

Highlighted
I Plan to Stick Around
Posts: 17

Re: CODA-4582 - Open Issues for Investigation

I'm 90% sure I've figured out a big part of the speed degredation problem:

 

The CODA-4582 modem is overheating

 

Even with firmware .24, speedtests during OFF PEAK hours would vary around 7-800Mbps, but would shoot back to over 900Mbps after a fresh reboot before degrading again shortly after. The results were never consistent when degraded, back to back tests could vary by as much as 50Mbps even though I was using the Rogers server on speedtest.net.

 

Ever since day one, I've felt a lot of heat radiating off the top of the modem. Yes I removed all the plastic wrap before plugging it in. I never gave much thought about the heat at first but considering how inconsistent the performance is, I wanted to experiment.

 

I placed a standard 120mm case fan on the top of the unit blowing down and shrouded the upper half of the modem on the sides to force the air to exhaust out the bottom half. Did a fresh reboot and now I'm getting consistent ~930Mbps downstream speedtests back to back during off peak hours. I've never been able to get such consistent speedtest results before and I've had the modem since December. On peak hours from ~9pm to 1am are still varying from 600-800Mbps since my node is oversaturated. 

Highlighted
I Plan to Stick Around
Posts: 207

Re: CODA-4582 - Open Issues for Investigation


@rjmaxim wrote:

@Jeffj wrote:

@Hwaiting wrote:

@Jeffj wrote:

@RogersDave wrote:

@gp-se wrote:

@RogersDave got .24 a few hours ago, network is SLOW, so I checked my DOCSIS Logs: 


@gp-se, I just ran a remote test on your modem and can clearly see signs of interference at 591 MHz and possibly at 597 MHz.

 

For the geeks out there, this is really close to a quarter wavelength of WiFi channel 1 (2401-2423 MHz).

 

My best recommendation is to swap this modem whenever you have a chance.

 

Dave


Just to explain to the non geek a little further and to geek out a bit my self lol

 

Cable operates between 100MHz to 1000MHZ  area. so much ofthat range is with in a quarter to half wave legnth of the 2.4ghz spectrum.  The fact that most consumer routers sue quarter wave, quarter wave di pole or half wave antennas due to the form factor they need to achieve. this probably has a signifigant factor in the interference as well. 

 

Also the antenna placement on these access points is not optimal, again due totheformfactor they have to achieve so they actually generate some noise in the spectrum them selves, but typically this doesnt matter because it can still cover the average household so no one notices or cares untill something like interfering with your CM happens. 

 

Back a few yeats ago, i did an experiment and shielded a TPlink WR-1040D antennas from them selves so they dont cross talk, and essentially doubled the range of the unit, but it changed it from a omni directional unit to a directional due to the shielding. I was also able to reduce the transmit power by almost 60% and still gain better range and thus reducing noise signifigantly. 

 

Wireless is a cruel mistress sometimes. 


So in the case where the modem is experiencing interference, is it experiencing the interference from it's own radio antennas?  And if we are using it in bridge mode with our own routers, does separation from the modem and router make much of a difference if the waves are omnidirectional?  Is there a minimal distance we should have them separated by?  Thanks.


As long at the modem is the black dot with the proper shielding distance *shouldnt* matter and it shouldnt interfear with its self. Otherwise Rogers recommended having your wireless 2.4 turnedo ff on the Coda if its not a black dot and have your router 6 feet minimum away. 


Just my 2cts of ignorance...isn't the interference only when you are running Coda in Gateway and also attach a router, when both units are broadcasting WiFi frequencies.....I cannot see how the Coda in Bridge mode can be affected by the WiFi frequencies of a router to slow it down. I am not a DataCom guru and would like to understand. Cheers...     


No, If your CODA modem suffers from interference, it does not matter the source of the 2.4 GHZ interference, Be its self or a seperate AP. This is why they recommend you to get a Black dot modem if you have issues and keep your seperate AP at minimum 6 feet away from the CM.  If you suffer from the interfernce using the built in 2.4 GHz will be unusable and you will notice issues. 

Highlighted
I'm an Enthusiast
Posts: 945

Re: CODA-4582 - Open Issues for Investigation

HI @RogersDave seems like my modem has rebooted on its own last night around 4am I have been on .24 since Thursday wondering was there any work being done or does my modem suffer from interference
Highlighted
Resident Expert
Resident Expert
Posts: 1,117

Re: CODA-4582 - Open Issues for Investigation

@lethalsniper

if you have interference issues you'll notice "sync errors" in the DOCSIS logs.

 



Highlighted
I'm a Senior Contributor
Posts: 641

Re: CODA-4582 - Open Issues for Investigation

My DOCSIS log is loaded with errors but no synch error at least.

 

Some people on D3.1 mention that they have no more errors in their log since 3.1 , looks like D3.1 is the answer to many issues.

Highlighted
I'm an Enthusiast
Posts: 945

Re: CODA-4582 - Open Issues for Investigation

I have had those error messages before and I'm on 3.1 and was on .23
Highlighted
I Plan to Stick Around
Posts: 103

Re: CODA-4582 - Open Issues for Investigation


@gp-se wrote:

@lethalsniper

if you have interference issues you'll notice "sync errors" in the DOCSIS logs.

 


@gp-se Thx ...Good to know. My Blk Dot .24....and Signal strength on 13 channels between 0 and -6.0

and Log over last 3 days showing one synch error. Does this mean I have some interference. Maybe the  Blkdot 4582 Diplexer is not shielded enough.....I am running in bridge mode but if the 4582 is not sufficiently shielded it could get interference from my router 2.4Ghz . Will test by turning this frequency off on the router. Also note the date on the first message....1970? Maybe some other mysterious force is at play... LOL.  

 

 

No.

Time

Type

Priority

Event

1

01/01/1970 00:01:05

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC= xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

2

02/16/2017 22:51:28

90000000

warning

MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC= xx:xx:xx:xx:xx:xx;CMTS-MAC= xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

3

02/17/2017 05:35:49

84000500

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC= xx:xx:xx:xx:xx:xx:c0;CMTS-MAC= xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

4

02/17/2017 17:58:26

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC= xx:xx:xx:xx:xx:xx;CMTS-MAC= xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

5

02/17/2017 18:21:45

90000000

warning

MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC= xx:xx:xx:xx:xx:xx;CMTS-MAC= xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

6

02/18/2017 03:58:08

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC= xx:xx:xx:xx:xx:xx;CMTS-MAC= xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

Highlighted
I Plan to Stick Around
Posts: 85

Re: CODA-4582 - Open Issues for Investigation

@gp-sewhat about this? I am on Docsis3.1

 

 

No.

Time

Type

Priority

Event

1

02/17/2017 16:36:01

82000400

critical

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

2

02/17/2017 16:36:30

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

3

02/17/2017 16:36:45

90000000

warning

MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

4

02/17/2017 16:36:46

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

5

02/17/2017 16:44:28

84000500

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

6

02/17/2017 16:44:34

84020200

warning

Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

7

02/17/2017 16:45:23

82000400

critical

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

8

02/17/2017 16:45:51

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

9

01/01/1970 00:00:02

68000401

warning

ToD request sent - No Response received;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

10

02/17/2017 16:46:09

90000000

warning

MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

11

02/17/2017 16:46:28

82000500

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

12

02/17/2017 16:49:41

84000500

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

13

02/17/2017 16:49:46

84020200

warning

Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

14

02/17/2017 16:50:37

82000400

critical

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

15

02/17/2017 16:51:06

82000200

critical

No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

16

02/17/2017 16:51:16

68000401

warning

ToD request sent - No Response received;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

17

02/17/2017 16:51:20

90000000

warning

MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

18

02/17/2017 17:07:17

68010300

error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

19

02/17/2017 17:18:31

90000000

warning

MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

20

02/18/2017 17:18:50

84020200

warning

Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;