DBSTalk Forum banner
1 - 6 of 6 Posts

· Godfather
Joined
·
355 Posts
Discussion Starter · #1 ·
I have a problem with signal coming and going. My setup is as follows:

4 coax cables from dish to swm16. 1 out to HR34. 1 out to 4 way splitter with 2 lines to an HR20-700 and an HR21.

I have a problem with signal dropping on certain transponders. I know channel 206 ESPN is one of them. I have isolated the problem to one of the coax runs. When I disconnect this line, the channel (206) comes back. I leave it disconnected for 10-15 seconds and then reconnect it. After reconnecting it, all channels will work for 12-48 hours and then it happens again. It's bizarre to me that the channel comes back upon disconnecting but stays on after reconnecting for some time.

I have replaced the coax connectors on the dish side as well as the swm16 side. This made no difference. I've thought about moving the suspect coax to another input on the swm16 but I'm not sure what I would be looking for in this case. I'm not that familiar with how a swm16 works.

My guess is that I have a bad lnb, a bad swm16 or a bad run of coax. How to a narrrow things down to determine the culprit?

Thanks
 

· Registered
Joined
·
5,530 Posts
Maybe none of these. Look at your signal strengths on the 99c, 103ca and 103cb satellites, all transponders. They should all be in the high 80s to mid 90s. If not, and the signals are basically the same on all the receivers, it's probably a dish alignment issue.
 

· Legend
Joined
·
157 Posts
RxMan1 said:
I have a problem with signal coming and going. My setup is as follows:

4 coax cables from dish to swm16. 1 out to HR34. 1 out to 4 way splitter with 2 lines to an HR20-700 and an HR21.

I have a problem with signal dropping on certain transponders. I know channel 206 ESPN is one of them. I have isolated the problem to one of the coax runs. When I disconnect this line, the channel (206) comes back. I leave it disconnected for 10-15 seconds and then reconnect it. After reconnecting it, all channels will work for 12-48 hours and then it happens again. It's bizarre to me that the channel comes back upon disconnecting but stays on after reconnecting for some time.

I have replaced the coax connectors on the dish side as well as the swm16 side. This made no difference. I've thought about moving the suspect coax to another input on the swm16 but I'm not sure what I would be looking for in this case. I'm not that familiar with how a swm16 works.

My guess is that I have a bad lnb, a bad swm16 or a bad run of coax. How to a narrrow things down to determine the culprit?

Thanks
First thing is to determine if the channel losses happen simultaneously on each receiver.

ESPNHD is on the 99(c) satellite, transponder 13. ESPN2HD is on the same bird, same transponder. In theory, when ESPNHD goes SFSS, so should ESPN2HD. Verify that you have acceptable signal levels on the 99c satellite (90s+).

When the issue occurs, you should view the individual signal strengths on each receiver on each tuner. Look first at the 99c satellite. Are all odd xponders registering 0? If so look at the 101 signal strengths, are they also all 0s? If so, that would indicate cable between the LNB and the SWM-16. Swap the first and second cables feeding the SWM-16(101/99 13v/18v). Do the 0s now appear on the EVEN xponders on both the 101 and 99? If so it is definitely that particular cable, or the LNB port connected to that cable. (Swap at the LNB to verify port is good) .

If the 0s are only on the 99c and not also the 101, this would indicate either LNB or SWM-16. You could verify the LNB is good by bypassing the SWM-16 with 2 of the LNB feeds fed directly to the HR20, you said there are 2 lines heading that way anyway. Repeat satellite setup, choosing multiswitch, B-band converters would be needed. Verifying solid signals across all sats/xponders should rule out the LNB as the culprit.

I have attached a spreadsheet with sample signal strengths for a Slimline 3 and a Slimline5 dish.

Good Luck!!
 

· Legend
Joined
·
264 Posts
Rxman, When was this installed? Was ALL equipment installed at the same time? WHo did the install?

You also do not say if this problem is on all recievers or just one, now, brake this whole thing down into little sections, if on all I would try changing the splitter and see if the problem is still there.

If only on one, then I would exchange it for another and see if the problem is with the same reciever or location.

If at location, you have a cable problem, if with reciever, then a reciever problem.

If you still have the problem, then you try the swm16, and work your way to the LNB.

Ya, you may have some money into this, but you just learned how to trouble shoot and get to know your system
 

· Icon
Joined
·
835 Posts
Do NOT rule out a different line as suspect.

You will NOT FIND this in any tech training or updates or other info.

Personal experience. I had same problem as you did, thought it was the one coax line. Each time i removed it from the splitter the rest of the system worked. I replaced it, didnt make any difference.

It ended up being another line that was shorted, but when the opposing good line was connected to the splitter it caused a drop out.

Best to run temp lines to figure out which is bad, or get soem type of cable tester or ohm readings.
 

· Premium Member
Joined
·
41,526 Posts
Jodean said:
Do NOT rule out a different line as suspect.

You will NOT FIND this in any tech training or updates or other info.

Personal experience. I had same problem as you did, thought it was the one coax line. Each time i removed it from the splitter the rest of the system worked. I replaced it, didnt make any difference.

It ended up being another line that was shorted, but when the opposing good line was connected to the splitter it caused a drop out.

Best to run temp lines to figure out which is bad, or get soem type of cable tester or ohm readings.
You've got to love RF. :lol: :lol:
I do follow exactly what was happening, "but" this is on the output of the SWiM, and isn't how the input lines work.
 
1 - 6 of 6 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.
Top