You you tried unplugging all receivers and the PI for the SWM to reset everything including the SWM module?
HR20-700 problem or SWMLine problem?
I am planning to call D* today to request a replacement unit for my HR20-700, but I wanted to check here to verify that my problem is with the HR20 and not a SWMLine problem. I'll try to explain my setup and problem briefly but with enough detail to give the relevant facts.
I've got an HR20-700 in my bedroom, and I've also got an HR20-100 in the living room and an H20 in my study. I installed a SWMLine LNB about 2 months ago, and everything worked great initially. Both tuners on the HR20s had good signals from the SWMLine, and the SWM signal strengths were actually higher than they had been before on all three receivers. The PI is installed "behind" my HR20-700 in the bedroom, and all of the distance requirements are well within range.
About 2 or 3 weeks ago, I started noticing a few things on the HR20-700. One problem was apparent signal loss, which I first noticed through random pixellating when watching one of the "new" HD channels from D10 (like ESPN-HD on channel 206). I could tune to ESPN-HD on channel 73 or one of the "older" non-HD channels and the problem was not there. Then, I started getting the "Searching for Signal on Tuner 1" from time to time. Sure enough, I would go to the setup menu to check my Tuner 1 signal strength, and there were zeroes for all sats and all transponders on Tuner 1 (Tuner 2 was receiving signals, although they were lower than they had been previously). I do a Red Button Reset, and after the setup is finished, both Tuners have strong signals on all sats and the appropriate transponders. However, this usually lasts a day or two, and then the same problem happens again. RBR always fixes it again.
In addition to these problems, the HR20-700 has become sluggish in response to commands from the remote control (this includes all commands). And last night, another issue started. I have Entourage set to record every week on the HR20-700. When I went to play last night's episode, the screen turned gray for about 5 or 6 seconds (like it was "loading" the episode) and then it gave me the "Would you like to delete this episode" message with the YES or NO options (like I had already watched the whole recording and was at the end of it). I said NO, exited all the way out to Live TV, and retried several times to view this episode, and got the same result every time. This also happened with the True Blood episode that was supposed to record last night.
So, is this a problem with the HR20-700, or is it a possible SWMLine problem? Like I said, the RBR fixes these problems, but they always come back. On top of that, I don't have any of these problems on either of my other receivers. I am planning to call D* for a replacement today for the HR20-700, but I wanted to verify my suspicions before I called.
Thanks in advance for any help!
I've got an HR20-700 in my bedroom, and I've also got an HR20-100 in the living room and an H20 in my study. I installed a SWMLine LNB about 2 months ago, and everything worked great initially. Both tuners on the HR20s had good signals from the SWMLine, and the SWM signal strengths were actually higher than they had been before on all three receivers. The PI is installed "behind" my HR20-700 in the bedroom, and all of the distance requirements are well within range.
About 2 or 3 weeks ago, I started noticing a few things on the HR20-700. One problem was apparent signal loss, which I first noticed through random pixellating when watching one of the "new" HD channels from D10 (like ESPN-HD on channel 206). I could tune to ESPN-HD on channel 73 or one of the "older" non-HD channels and the problem was not there. Then, I started getting the "Searching for Signal on Tuner 1" from time to time. Sure enough, I would go to the setup menu to check my Tuner 1 signal strength, and there were zeroes for all sats and all transponders on Tuner 1 (Tuner 2 was receiving signals, although they were lower than they had been previously). I do a Red Button Reset, and after the setup is finished, both Tuners have strong signals on all sats and the appropriate transponders. However, this usually lasts a day or two, and then the same problem happens again. RBR always fixes it again.
In addition to these problems, the HR20-700 has become sluggish in response to commands from the remote control (this includes all commands). And last night, another issue started. I have Entourage set to record every week on the HR20-700. When I went to play last night's episode, the screen turned gray for about 5 or 6 seconds (like it was "loading" the episode) and then it gave me the "Would you like to delete this episode" message with the YES or NO options (like I had already watched the whole recording and was at the end of it). I said NO, exited all the way out to Live TV, and retried several times to view this episode, and got the same result every time. This also happened with the True Blood episode that was supposed to record last night.
So, is this a problem with the HR20-700, or is it a possible SWMLine problem? Like I said, the RBR fixes these problems, but they always come back. On top of that, I don't have any of these problems on either of my other receivers. I am planning to call D* for a replacement today for the HR20-700, but I wanted to verify my suspicions before I called.
Thanks in advance for any help!
1 - 12 of 12 Posts
I have not tried that yet. I was wondering if that would fix anything, since my problem was localized with the HR20-700 (and because of a little laziness on my part :lol: ). If I understand it correctly, unplug everything and then reconnect the power starting with the PI and then each receiver?Grentz said:You you tried unplugging all receivers and the PI for the SWM to reset everything including the SWM module?
I noticed you said that you installed the SWMLine. I take that to mean that DirecTV did not do it for you. If that's correct, what type of splitter are you using? I had similar problems when I installed my own.
If the resets that Grentz recommended don't help (or only help for a couple days), try a better splitter. My problems disappeared after I changed to a Perfect Vision PV23-303.
By the way, when doing the power resets, power the PI back up before the receivers.
If the resets that Grentz recommended don't help (or only help for a couple days), try a better splitter. My problems disappeared after I changed to a Perfect Vision PV23-303.
By the way, when doing the power resets, power the PI back up before the receivers.
You are correct...I did the install myself. I'm using the SW4 splitter (I think that is the correct model number) that came as part of a package deal with the LNB. I've got 3 outputs used, and the 4th unused output is terminated.bakers12 said:I noticed you said that you installed the SWMLine. I take that to mean that DirecTV did not do it for you. If that's correct, what type of splitter are you using? I had similar problems when I installed my own.
If the resets that Grentz recommended don't help (or only help for a couple days), try a better splitter. My problems disappeared after I changed to a Perfect Vision PV23-303.
By the way, when doing the power resets, power the PI back up before the receivers.
Were your problems isolated to one receiver also?
might try swapping reciever locations if you can, and see if the problem follows the location or the reciever..
That's a good idea that I had not thought of yet.houskamp said:might try swapping reciever locations if you can, and see if the problem follows the location or the reciever..
How long is it recommended to leave the power disconnected if I am trying to reset the PI and receivers by unplugging them? 1 minute, 5 minutes, 30 minutes??
15 minutes seems to be the ideal time..Eddie L. said:That's a good idea that I had not thought of yet.
How long is it recommended to leave the power disconnected if I am trying to reset the PI and receivers by unplugging them? 1 minute, 5 minutes, 30 minutes??
Two of the four ports had a problem in my setup. One of the bad ports was terminated so only one of my receivers had the issue. DirecTV recommends a SWS-4 (shown here) which is probably the best you can get.Eddie L. said:You are correct...I did the install myself. I'm using the SW4 splitter (I think that is the correct model number) that came as part of a package deal with the LNB. I've got 3 outputs used, and the 4th unused output is terminated.
Were your problems isolated to one receiver also?
That's the one that I've got (the SWS-4). I didn't think about the port being bad. If nothing else works, I will try changing the ports (I've got one that is terminated and unused).bakers12 said:Two of the four ports had a problem in my setup. One of the bad ports was terminated so only one of my receivers had the issue. DirecTV recommends a SWS-4 (shown here) which is probably the best you can get.
Were you using the SWS-4 originally or something else?
I used something else. I think it's labeled MCR, but I don't know the model number. If you're using a SWS-4, count on this being something else. I would do the resets that Grentz outlined.Eddie L. said:Were you using the SWS-4 originally or something else?
I was having a problem with my HR20 and SWM8 with some of the same things that you have mentioned, and some weird things like channels skipping from MSNBC to Disney or FSSW. One day it was getting particularly bad and upon checking my signals to the SWM8, they would sometimes be in the 90's or drop to 0's. The cabling appeared fine, swapped the splitter for the one recommended here with no change.
Then I tried something out of the blue: I disconnected my eSata (750GB WD) and booted back to the internal. The problems disappeared. SWM8 was solid in the 90's.
Conjecture: Due to bad sectors or reads from the regular HD, the system was getting bogged down causing these issues.
I swapped out the WD for a Seagate DB35.3 750GB drive using the copy method listed elsewhere, here. Only took 5 hours...
. But since then, I haven't seen those issues crop up again. The DB35 series is tuned for DVR use (skipping past bad reads instead or retrying).
So it may be possible that you have a bad drive, be it internal or external.
Keith
Then I tried something out of the blue: I disconnected my eSata (750GB WD) and booted back to the internal. The problems disappeared. SWM8 was solid in the 90's.
Conjecture: Due to bad sectors or reads from the regular HD, the system was getting bogged down causing these issues.
I swapped out the WD for a Seagate DB35.3 750GB drive using the copy method listed elsewhere, here. Only took 5 hours...
. But since then, I haven't seen those issues crop up again. The DB35 series is tuned for DVR use (skipping past bad reads instead or retrying).So it may be possible that you have a bad drive, be it internal or external.
Keith
1 - 12 of 12 Posts
- This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
DBSTalk Forum
A forum community dedicated to digital bit streaming enthusiasts. Come join the discussion about programming, content, and reception, home theaters, displays, models, styles, satellites, reviews, accessories, classifieds, and more!
Full Forum Listing
Recommended Communities
