dbirdman
Premium,MVM
join:2003-07-07
Eureka, CA
| reply to caption_nemo
Re: [Installer] Professional Advise to the End User
I'm going to single this out as the most problematical advice:
quote:
The dishes on occasion stop communicating with the modem and the dish requires the modem to know where to point. In this case you have to make sure the modem starts up first when power cycling. I would recommend powering the modem up. Then wait 5 minutes. Power your router up. Wait 2 minutes. Then power the dish up. This will solve your problems. You may have to do this several times. This problem is exponentially increasing among the users I have received calls from.
The current controller from the industry leading MSS company, standard for more than two years has not needed the modem in order to point. The problem is that the modem needs a location update in order to range, and that normally only occurs when there is controller/modem connectivity. Powering up the modem first is one choice, although it is not necessary to wait one second after the modem's LAN light comes on, and that never takes 5 minutes, or even 2. The router is a non-issue. The current controllers also have a startup delay mechanism that you can set. Beyond that, my (free) D3Admin tool has a Generic/Hughes mode that allows the dish to power up immediately, and will take care of the necessary location update.
I use the latter consistently, and simply never have controller/modem problems. The program will also check for modem/controller configuration conflicts, such as happen when Hughes changes a transponder without warning.
--
W2K Server|Toshiba Satellite XP Pro|iDirect 3100 on Datastorm 1.2 meter XF3 with 4-watt BUC|HughesNet IA8/1390/7000s Pro on 2-watt Datastorm G74|1990 Blue Bird Wanderlodge Bus "Blue Thunder" |
