I don't know if the VS works this way, but a couple of the receivers I have make it difficult to search for satellites when connected through a DiseqC switch.
What I found, was that if I had a dish connected say on port 4 of the diseqC switch, that I would put the receiver on a transponder, and start searching for the sat, but what would happen is that after a while, the receiver will start switching switch ports on it's own, apparently looking for the signal. I say apparently, because it might just be caused by a data error, since another feature of all STBs I've used is that if it doesn't lock on a signal, it will send out additional diseqC commands to make sure that the switch is in the right position, and it's possible that a data error puts the switch in the wrong position.
I became aware of the above once when I had 3 different dishes connected to a DiseqC switch, and two were already aimed at the satellite I was trying to aim the 3rd at. I had a TV out at the dish, and also had a meter on the dish I was aiming.
What happened, was that while moving the dish, all of a sudden, the meter went dead, ie loss of lnbf voltage, and at the same time I suddenly got a strong signal indication on the TV. I went to the receiver, and reset the port via the diseqC switch setting, back to the dish I was on, and the meter lit up again, and the TV signal went off. Then, while moving the dish again, the same thing happened, ie signal meter went dead, and the TV came on full signal.
Even though the above behavior is rare, and I've only seen it happen a handfull of times, I've since decided that it is more dependable to bypass a diseqC switch while searching for a satellite. At least if it's going to take a while to find it. My suspicion is that these newer receivers are trying to do things they shouldn't be doing on their own, but as I said, it could be just a situation of data errors.
