Reply to thread

Message: <blockquote data-quote="clarkebelt" data-source="post: 1090451" data-attributes="member: 148422">Well here is where things take a turn into crazytown...In looking at the screenshot I posted above I realized that something is wrong.  To explain, please understand that at present I am only using the first three ports on the DiSEqC switches - port D or BB (depending on how the software designates it) is unconnected and unused - and of the three that are connected, only the third port (port C or BA) has a tone switch on it, and that tone switch is the only thing that has a Ku-band LNB connected to it.  The first two inputs have C-band LNB's directly connected, as does the "off" side of the tone switch.  And just in case you start to think I may have them physically miswired, I will just mention that the DiSEqC switches are inside the house, while the 22 kHz tone switches are out at one of the poles.  It would therefore be physically impossible to accidentally connect a 22 kHz tone switch between the tuner and the DiSEqC switch.Yet when I scanned DiSEqC A above, it found the Ku-band LNB and showed the signals from it.  Same thing happens if I select DiSEqC B or C (the correct one) - it shows the same signals on roughly the same frequencies.  Here is a comparison of what it shows on DiSEqC A (which has NO Ku LNB or tone switch) and DiSEqC C (note that some signals apparently dropped between the two scans, which would be expected on this satellite because it is used for news uplinks and other wild feeds, but you can see the similarities):[ATTACH=full]152512[/ATTACH][ATTACH=full]152513[/ATTACH]But the next weird part is that while these signals also show up on DiSEqC B, on DiSEqC D (the unconnected one) this does NOT happen:[ATTACH=full]152514[/ATTACH]Now I wondered if a similar bleedover between DiSEqC's happens with C-band signals, and it does not.  Scanning C-band shows only the signals that should be there on each DiSEqC switch position.  I want to emphasize that there is no way the Ku band signals can actually be appearing on all three DiSEqC inputs, so I am at a loss to explain the above.  Also it happens on both of the in-use tuners which are connected to separate DiSEqC switches, so I doubt it's a DiSEqC issue (also we never saw anything like this with an actual satellite receiver connected).  I am totally at a loss to explain why the TBS scan program would report a Ku satellite on a DiSEqC position other than the one it's actually connected to, but be that as it may, here is the information you asked for.  This is with the tone switch on, and it did NOT fail as you expected:[ATTACH=full]152515[/ATTACH]There is no "auto" setting for the tone switch, there is HIGH/ON, LOW/OFF, and ALL.  Setting it to ALL showed the next screwy thing - even though I had set the lower frequency to 11700, it found both C-band AND Ku-band signals (the two screenshots below are from the same scan but with the slider moved):[ATTACH=full]152517[/ATTACH][ATTACH=full]152518[/ATTACH]At this point I got to thinking, this stupid scan program is going to find that Ku LNB no matter what I set it to.  So as a test, I set it back to circular but turned the tone switch off.  Take a wild guess what happened:[ATTACH=full]152519[/ATTACH]My theory is that either this scan program has a bug in it that is not allowing it to work correctly with this particular tuner, or there is something going on in the driver that is allowing the Ku signals from one DiSEqC port to appear on others.  Or something like that.  Actually this is so weird to me that I can't think of any logical explanation.  If the DiSEqC switch were faulty and were allowing signals to bleed over between ports then port D should also be affected, and C-band should also be affected, and neither of those is true (and also I find it hard to believe that two different DiSEqC's would be similarly affected, and that I never saw this issue when it was connected to a receiver).  As I noted, it would be physically impossible for me to have miswired it so that the tone switch is between the tuner and the DiSEqC switch. And nothing explains why this program still sees the signals from the Ku LNB when the tone switch is set to off.So anyway, there is the information you asked for, but I don't know if it can be trusted at all, since this scan program apparently wants to find that Ku LNB no matter what I set it to, as long as it's not C-band. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused    :confused:" loading="lazy" data-shortname=":confused:" /></blockquote>

Verification