View Full Version : STRANGE Problem with E*
eggemon
09-20-03, 11:47 AM
I am having a VERY STRANGE problem with my Dish Network setup. I have been a subscriber for a long time. My setup here has not changed materially for several months, and until just over a week ago, it worked fine.
I have 3 receivers, 6000u (8VSB/8PSK), 4000, 2700; SW64, and a Dish 500 (no 3rd sat right now).
The problem: the 6000 is great, but the other 2 receivers think the switch is bad, i.e., they do not see all 4 LNB inputs (119 odd/even & 110 odd/even). At different times, the problem receivers see 2 or 3 of the 4.
I have moved receivers to different input cables, and the situation stays the same -- the same receivers get the same result.
I came up with a 2nd SW64, and that made no difference. I had an extra LNB, so I swapped one, and no difference.
All connections have been checked and rechecked. All receivers have the latest code releases. Signal is great (100+ on both sats).
I have *no clue* why it started doing this; the *only thing* that changed recently (up to my troubleshooting efforts) was that I added the new HD package (which works fine).
Anyone have a suggestion for what might be going on here, or what to do about it??? I am completely confused and beginning to question the veracity of logic :( Any (constructive) suggestions welcomed...
First D* refers to Directv not DISH ECHOSTAR is abbreviated E*. Try the 2700 or 4000 connected to the cable that goes to the 6000. If the check switch is good try the 6000 at one of the other cables. If it is bad your problem is cabling.
eggemon
09-20-03, 12:53 PM
(Yes, I know I meant E* -- finger slipped and I didn't catch it...)
I have already tried swapping receivers around. The problem stayed with the receiver, not the cable. I have also run an entirely new cable between switch and receiver, and that made no difference.
I appreciate the suggestion...
Try this: Disconnect the SAT inputs to the 2 old rcvrs & run the Switch Test. This will "clear the matrix" on both. Then reconnect & Switch Test them one at a time.
Sometimes when a rcvr has a switch problem this is the only fix.
eggemon
09-20-03, 06:16 PM
Try this: Disconnect the SAT inputs to the 2 old rcvrs & run the Switch Test. This will "clear the matrix" on both. Then reconnect & Switch Test them one at a time.
Sometimes when a rcvr has a switch problem this is the only fix.
Thx HTGuy, but that didn't work, either...
If you have a friend or relative that subscribes to DISH try connecting one of the old receivers to their system. It sounds like you have 2 bad receivers.
Deguelo
10-28-03, 07:32 PM
You do not specify if your LNB is a DishPro or a Legacy. If you are trying to use a DP LNB on Legacy receivers, you will need to have a DP adapter in place on your receivers.
valand_krisban
10-30-03, 07:29 PM
I have 3 receivers, 6000u (8VSB/8PSK), 4000, 2700; SW64, and a Dish 500 (no 3rd sat right now).
I came up with a 2nd SW64, and that made no difference. I had an extra LNB, so I swapped one, and no difference.
Are you powering the SW-64? Maybe the cable runs are too long to signal the switching.
eggemon
10-31-03, 07:29 PM
Are you powering the SW-64? Maybe the cable runs are too long to signal the switching.
Yes, I am powering the SW-64 -- I have tried it without power, and it does not work at all. I have tried inserting power on two different cable runs, both shorter than one that worked fine in my previous home, without success.
As an update, I have virtually proven that the problem is associated directly with the SW-64. I dropped back to two receivers utilizing SW-21s. With any pair of my receivers in play, everything is wonderful. So, it is not the cable, the LNBFs, or the receivers... It has to be related to the SW-64s (and both I have tried exhibit the problem). I plan to try one more test -- changing my grounding setup. If that doesn't solve it, I will punt.
To the previous question, I do not have DishPro -- it's all legacy.
Thanks for the input...
SouthernSky
11-01-03, 08:50 PM
Maybe you've tried this, but have you run the 2 older receivers through the SW64 with the 6000 disconnected from the SW64, then rerun the switch test?
If they work fine now, then re-add the 6000 and see what you get running a switch test. What are the connection results you get on 119, 110 or SW64? Is the SW64 being recognized and are you getting both, one or neither transponders?
eggemon
11-02-03, 05:01 PM
Maybe you've tried this, but have you run the 2 older receivers through the SW64 with the 6000 disconnected from the SW64, then rerun the switch test?
I could not recall trying just the two old receivers, so I tried it, and...
Good> the switch test was perfect
Bad> but some channels fail on one receiver (but not the other)
If they work fine now, then re-add the 6000 and see what you get running a switch test. What are the connection results you get on 119, 110 or SW64? Is the SW64 being recognized and are you getting both, one or neither transponders?
Adding the 6000 back, no change from above -- switch tests good, still bad channels on one receiver.
I could easily believe I have a bad receiver, but with the SW64 out of the picture, it worked fine. Plus, the other receivers have had problems at other times...
I am officially tired of this mess now :mad:
At the moment, with all three recievers again connected, I have two that get virtually everything, and one (the least-used one) getting most things, so I will learn to live with it (until it gets worse again...)
Thanks again to all who have shared ideas on this vexing issue.
vBulletin® v3.7.6, Copyright ©2000-2012, Jelsoft Enterprises Ltd.