Intermittent Connection

**btaber_09** · 07-03-07, 11:24 PM

Alright so I've been having problems with my modem losing a cable lock for some time now and every time I call charter they assure me that it is a hardware issue but with both modems I've had the same problems have arrose. It typically drops out in the middle of the day when the temperature rises to 85 degrees or above. Then during the evening when it cools off it doesn't drop anymore. Any help with this issue would be greatly appreciated.

Here are some logs as of this evening...

Cable Modem History
10:55 PM on July 3rd, 2007
Signal
This page provides important information about the status and quality of the communications
between your cable modem and the cable modem network.

Downstream Channel
The data shown in the table below provides information about the signal coming from the
network to your cable modem.
Lock Status Locked Modulation QAM256
Channel ID 2 Symbol rate 5360537 sym/sec
Downstream Frequency 747000000 Hz Max Bit Rate 5048000 bps
Downstream Power 2.43 dBmV SNR 31 dB

Upstream Channel
The data shown in the table below provides information about the signal being transmitted to
the network from your cable modem.
Lock Status Locked Modulation 16 QAM
Channel ID 3 Symbol rate 2560 ksym/sec
Upstream Frequency 31008126 Hz Max Bit Rate 512000 bps
Upstream Power 48.00 dBmV

And this is the log as of 10:59 PM on July 3rd, 2007… typically during the middle of the day I’ll have a full page of those FEC Lock Errors.

Log
This page provides important information that can be used to resolve problems with your cable modem.

Time Priority Description
2007-07-03 20:46:16 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 20:46:16 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 20:46:03 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 20:46:03 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 20:40:01 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-03 20:32:06 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-03 20:26:27 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 20:26:27 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 19:52:20 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-03 19:43:17 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 19:43:17 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 19:37:48 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 19:37:48 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 19:28:54 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-03 17:35:07 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-03 17:25:13 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 17:25:13 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 16:48:46 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 16:48:46 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 16:34:29 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 16:34:29 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 16:16:18 error ToD request sent - No Response received
2007-07-03 15:26:18 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-03 15:17:51 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:17:51 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:14:55 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:14:55 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:08:25 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:08:25 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:08:23 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:08:23 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:08:22 warning Cable Lost FEC lock
2007-07-03 15:08:21 warning Cable Lost FEC lock
2007-07-03 15:08:09 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:08:09 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:07:20 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-03 15:07:19 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:07:19 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:07:17 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:07:17 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:06:49 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:06:49 information rms a map with the new UCD change count, and changed upstream parms
2007-07-03 15:06:37 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:06:37 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:06:37 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:06:37 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:06:35 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-03 15:06:33 information change count, and changed upstream parms and changed upstream parms
2007-07-03 15:06:33 information Got a map with the new UCD change count, and changed upstream parms
2007-07-03 15:06:22 information Got a map with the new UCD change count, and changed upstream parms

**alex_barringer** · 07-03-07, 11:51 PM

Simple, if your house is air conditioned and your cable modem is in a cool area while operating, at 80 degrees and colder (down to 38 degrees Farenheit) is a good operating temperature for it. Assuming you are not having any power problems either.

Simply put, the problem is not on the inside of your house, this is a common problem that many service providers don't want to fess up to, let alone fix. Works like this, if anywhere on your cable is a bare spot or the grounding shield is loose or exposed to heat and humidity / moisture, you can infact have anomalies as you are encountering.

Sometimes the cable trunk boxes are poorly constructed in that they allow moisture to condense inside of the box, dripping down and wreaking havoc on the signal amplifiers for both the DSL / digital cable service. Even people that have xDSL services have this trouble too.

If somewhere the cable is exposed or pulled out of position (like a large branch fell on it, they took it off but didn't check the connections. Digital cable and communications are very prone to physical connector problems.

Despite what people will tell you is that xDSL and Digital Cable are digital transmissions when they are not at all. The receive and transmission circuits are digital yes, but the differential circuitry in which the signals are sent and received are analog, so the signals have to be converted from digital to analog and back again.

Just so you know, analog signals are prone to thermal noise (noise associated with heat), which in turn can also interfere with your high speed communications end to end (you to your ISP or charter in this case). This is a well know problem in the electronics industry and is nothing new. As far as this affecting your Cable Communication Link Sync signal, also easy to understand, this thermal noise causes too much noise in the signal path for the "clock recovery circuit" in your modem to find or hear the incoming signal so therefore it shuts down. Also heat causes analog signal drift, what this does is when if you have a good connection you may encounter times of the day when the connection gets really slow and sometimes stutters but there is nobody else on the cable connection in your neighborhood or on the ISP trunks, this is what thermal drift does. You still have the DOCSIS center frequency but it drifts off it's normal position, so your modem has to constantly retune / retrain looking for the center frequency to lock onto so it knows when it can send and receive, let alone what speed it can do it at.

Just tell charter to get out there when it is really hot and check the parameters of the line, it's most likely going bad.

**btaber_09** · 07-05-07, 05:53 PM

Charter is coming tomorrow. Anything specific for them to check or just ask them to check the line out?

**btaber_09** · 07-05-07, 10:38 PM

Also would it only supporting DOCSIS 1.0 cause problems?

**steve67535** · 07-06-07, 11:07 PM

I've been having the same thing happen here for about 3 weeks. I'm in southern Wisconsin/Charter cable. At times the modem is fine for hours then all of a sudden it will drop the signal. Charter has come out twice and replaced the modem and a few splitters. The last tech said something about temperature changes and something on the lines needing adjusting to compensate. If you ever figure out what's wrong with your connection let me know. It sounds similiar to what I'm experiencing.

Steve

**trogers** · 07-06-07, 11:14 PM

Not surprising that such are occurring around the US. Hardware and cables were not designed to operate in prolonged three digit temperature (>100F).

**alex_barringer** · 07-07-07, 03:52 AM

How true... Sniff sniff sniff, hmm you know that cable is not firewire you know... something is a burning (just kidding)...

**btaber_09** · 07-07-07, 08:11 PM

The charter technician that showed up was a complete moron as many of them are. I suggested that maybe it was an amplifier problem on the pole and he was like "could be" so he walked through the neighbors yard over to the pole without a ladder... glanced up at it and that was it. Before coming in the house i told him that the modem was only DOCSIS 1.0 compliant and he looked at me like a deer in headlights. So we finally made it in the house and he couldn't distinguish the modem from the router until i told him which i found very sad. He unplugged the coax from the back of the modem and plugged it into his tester and said the levels were perfectly fine. I do believe this because i can check them in the browser. However I told him they fluctuate and he looked at the coax going to the modem and was like well here's the problem these ends to be cut off and replaced with these good ones. The ends weren't high dollar but that was not the problem. He just did this to make me think he knew what he was doing although it was obvious that he did not. He hinted at me getting a new modem if this didn't solve the problem and because i had read in another forum about charter trouble with my befcmu10v2 linksys modem I went ahead and picked up a new motorola surfboard last night. Hooking it up was a pain in the ass. I called them to register the new mac and i got some semi-foreign guy that couldn't speak that well and he told me he got it all hooked up. So i went to internet explorer on the computer and opened it up and there was this charter installation screen looking me in the face. I went through it and it kept saying modem provisioning failed. So i had to call them back a second time and talked to this lady and she was like oh yeah i'll fix it from here. Talk about annoying. Eventually i could connect to the internet and everything was actually faster and there seemed to be no problems. This morning I wake up and my dad alerted me to the fact that it had gone out again this morning. Thinking "oh hell" to myself i started up the computer and started to surf. About a hour later I experienced 2 complete drops within 10 minutes. On one of them i got to the modem signal page before it went off and showed the SNR at 22.7db and the power level downstream at 23.5dbmv. We all know this is very unacceptable but of course Charter will not admit to any problems with their line. I'm just tired of dealing with them. I will call again and raise hell with them about their incompetent technicians and see if i can get somebody else to come actually take a look at the line and pole and amplifier outside to see if i can get it resolved. If they don't I believe i'll be calling the local DSL company and switch from these bozos.

**ridgerunner** · 07-08-07, 10:53 AM

ask the tech if he is a system tech of bbt you need a system/maint tech to check the agc's in the amplifiers

**chpalmer** · 07-08-07, 01:53 PM

Post your log from your new modem.

**btaber_09** · 07-09-07, 12:13 AM

Logs

The Logs Page provides diagnostic messages generated by the Cable Modem. It is intended for use by a qualified technician.

Status
Signal
Addresses
Configuration
Logs
Help

Time Priority Code Description
2007-07-08 16:51:52 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:18 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-07 13:11:11 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-07 13:06:17 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-07-07 11:36:53 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:21 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:16 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-07 11:10:55 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-07 11:10:55 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-07-07 10:38:58 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-07 10:36:43 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:48 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:01:44 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:01:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:16 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:04 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:02 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:02 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:00 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:59 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:58 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:57 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:36 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:35 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:04 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:56 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
1970-01-01 00:02:56 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:25 3-Critical T004.0 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within ti
1970-01-01 00:02:06 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:01:59 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:01:49 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:48 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:47 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:42 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:41 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:37 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:36 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:29 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:29 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:25 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:24 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:24 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:16 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:04 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:03 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:03 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:00 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:59 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:58 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:57 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:36 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:35 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:04 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-07-07 10:22:12 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-07 10:22:12 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-07-07 10:20:52 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-07 10:18:08 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-07-07 09:54:51 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-07-07 09:51:34 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:18 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-07 09:49:17 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-07 09:49:16 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:53 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:46 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:35 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:27 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:27 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:04 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:27 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
1970-01-01 00:04:27 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:03:58 3-Critical T004.0 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within ti
1970-01-01 00:03:58 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:18 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-07-07 09:35:40 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-07 09:35:40 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:31 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:01:26 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:01:17 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:17 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:05 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:01 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:00 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:58 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:58 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:36 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:35 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:05 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-07-07 09:32:08 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-07-07 09:32:08 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-07-07 09:31:42 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:06:46 4-Error D004.3 ToD request sent- No Response received
1970-01-01 00:06:39 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:06:28 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:06:25 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:06:25 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:06:13 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

**chpalmer** · 07-09-07, 12:59 AM

Now you have two separate modem logs with the same problems showing that you can present to them.

By contrast, my modem logs one line every two or three weeks.

Id be looking to get some credits to my service till its fixed.

**btaber_09** · 07-09-07, 09:01 PM

However I have not had any problems with it today. still a cause for concern to call charter?

**chpalmer** · 07-09-07, 11:34 PM

Cause for concern? Yes

Call Charter? Probably not right now until you see it happen again. They may have fixed something on their end. Getting them to admit it could be fun.

Use the H-E-Double Hockey Sticks out of it and watch closely.

Good Luck!

**btaber_09** · 07-30-07, 07:28 PM

Hey guys, just wanted to update and say that the problem has still yet to be resolved. I haven't been home much lately to use it but I've noticed the same drops when it gets really humid outside. However the funny thing is is that when it goes out I can type in 192.168.100.1 and look at the signal levels and they are generally ok but the frequency has been lost. Then when the modem starts scanning for different frequency's it can never find the right one and they have horrible signal levels until it finally gets back to the right one maybe 10 min later. Any ideas?