posted
Although I don't see how it's related, my problem began the same day I upgraded my DS2 to firmware version 3.6.4. On February 14, 2005, I successfully upgraded my D2 and performed a NVCLEAR. Starting that same day, and everyday since, I sporadically loose a good receive signal quality on the my DW6000. The D2 can find the satellite and I usually have a signal quality of 82 or higher. Sometimes passing cross-pol or getting ranging may take awhile, but I eventually get on and can transmit. It takes from 5 to 30 minutes to get operational after moving.
Although this is sometimes frustrating to wait, my main problem is loosing the receive signal. After the system is fully operational, I'll suddenly loose the receive signal, hence loosing transmit. The receive quality will drop from 82+ to <5. Sometimes it takes an hour or more, then all is restored to normal. Sometimes, the receive signal comes back after only a minute or two. Other times, the receive signal will be good for hours, then drop for a few minutes, then come back, then drop, then come back, then drop. This may last for a couple hours. There hasn't been any repeated method to the problem, other than it happens everyday at some point. Sometimes in the morning, noon, evening, or late at night. Sometimes more than once a day. We have been moving a couple hundred miles every few days. Weather has been clear to stormy. But even when stormy, I get a good receive signal before it is lost then eventually restored.
posted
I would start with the cables. Make sure the cables are tight on the back of the 6000 and also that the fittings aren't loose. Give the cables a gentle tug and see if the fitting comes loose from the cable. I know that once the D-2 finds and locks on to the signal, it shouldn't have to move the dish unless it is peaking for cross-pol. I don't think that the upgrade is the problem unless the 6000 is telling the D-2 that it isn't done finding the satellite and to keep peaking.
Posts: 70 | From: So. Cal | Registered: Apr 2004
| IP: Logged |
posted
Checked the cables, all seems like a tight connection. I'm sure it's not trying to peak the signal anymore as the search is completed. I can be on for hours before signal just drops, and may or may not return immediately.
-------------------- HughesNet l Xplornet [Canadian] VAR l F1 D2 91/985 l Windows 7 Posts: 188 | From: Mission, BC Canada | Registered: Oct 2003
| IP: Logged |
posted
Every time I have had trouble getting or holding a signal I found it was in the connection. I have had to change ends because of corrosion and the nuts being threaded too deep to tighten down properly. (The nut was tight but the cable loose inside) Some 90Degree fitting I bough as well as the ones originally installed on the cable were defective and didn’t show up till 4 months after installation. Good luck
posted
Larry, Just out of curiosity, do you have a Public IP address or Dynamic (192.168.0.1) what ports are the D-2 and the modem plugged into on the router and are you wireless or hardwired to your computer?
-------------------- Bill Adams Winegard Company Posts: 15691 | From: Traveling the Western US | Registered: May 2003
| IP: Logged |
posted
It could be the connections. The system was installed only 6 months ago. But I think the cable feels a little loose inside the connectors.
Bill - my DW600 is NAT enabled, with a public IP address. Since it's a NAT system, I'm not using the WAN port on my WAP router. The D2 and DW6000 are just plugged into regular switched LAN ports. The WAN port is empty. I'm wireless with my PC's. I do have a Cat5 cable on the switch I used when I uploaded the new firmware.
A local MotoSAT installer is supposed to be in this RV park tomorrow to help another user and stop by my rig.
[ March 03, 2005, 12:28 PM: Message edited by: The Happy Wanderers ]
posted
Larry, Just as a note, you are either NAT enabled or you have a Public IP. I will assume that you are dynamic (Nat'd). If you go to 192.168.0.1 in your browser you can click on System Info and it should show your IP Address as 192.168.0.1. Assuming we are correct on all of those points your setup is correct.
-------------------- Bill Adams Winegard Company Posts: 15691 | From: Traveling the Western US | Registered: May 2003
| IP: Logged |
posted
Thanks Bill for the clarification. I saw the NAT IP address, and assumed that was the Public IP. Sysem info does show at 192.168.0.1. D2 is at 192.168.0.2.
The system worked fine for 5 months with no problems. My sporadic loss of signal just started a few weeks ago and happens randomly everyday. The signal was just lost for over 20 hours. Of course, the MotoSAT installer is expected to be here soon and the system just came back online. I'm hoping it goes down soon again so he'll have a failed system to work with.
posted
Larry, While he is there, have him update the D-2 to 3.6.4 and be sure that he leaves the local address to the (new) correct local address of 192.168.0.250 (instead of 0.2).
-------------------- Bill Adams Winegard Company Posts: 15691 | From: Traveling the Western US | Registered: May 2003
| IP: Logged |
posted
Well, the installer did what he could, but never found an exact cause of my problem. I had already upgraded to 3.6.4 and he did change the D-2 IP to *.250. He changed the DW6000 power supply which looked promising. He packed up and was about to leave when I lost signal again. He tried new cables and a new modem, but that didn't change anything. He did find that I accidently put in a bogus net mask on the D-2 after the NVCLEAR. I was back online and all looked good for awhile. This time, he did pack up and leave. About 5 monutes after he left, it went down again. I called him and he returned. This time, he changed the LNB. He's gone again, and we'll see (and hope) that fixed the problem.
But this problem has been so sporadic, I won't feel like the problem is solved until the system stays up for over 24 hours straight.
UBBFriend: Email this page to someone!
Printer-friendly view of this topic
