Hi,

I am looking for an application to use with my Hauppauge HVR-4000. But I have one problem.
When I scan Hotbird (even using an updated .ini file), I only get the lower half of the channels. My SAT-receiver works fine with the LNBs.

A channel like Euronews France appears at 11034 MHz, but it also appears at 11881 MHz, both vertical pol. But it should not be at 11881. So it is like the program fails to switch to the higher frequencies, and does a second scan at the lower freqs, thinking it is in the high end. I get many channels double as well (because of failure to utilize my universal LNB)

It is probably just a setting somewhere. Can somebody help ?

Settings->diseq->LNB propertes -> lof2

Thanks, but what should I set it for ?

I use Smart Titanium 0.2dB TWIN LNBs

99+% of the European style Universal LNBs are using LOF1 = 9750 MHz and LOF 2 = 10600 MHz, the default values of ProgDVB.

BTW, you wrote "LNBs".
This may be a hint for missing important details...

Now, look at the difference of the true and the virtual transponder, it's exactly the difference between the standard LOFs.
So, your hotbird LNB surely is of this common European Universal type, and it 'just' fails to switch to high band.
But as it is a Twin, you may want to test with cross changing the output ports, as they may differ a little bit in switching signal sensitivity or alike.

Mainly there are four kinds of reasons for such misbehaviour:

- 22kHz signal is used for position switching instead of band switching, wrong switch type set in ProgDVB...
No switch, no such entry.
Switch in fact is DiSEqC *.* or Simple / Toneburst - don't set ProgDVB to believe in an American style 22kHz position switch

- LNB's sensitivity for 22kHz is to low, or cable loss to high, then the receiver may perhaps produce a little more 22kHz signal strength, by this just getting a bit above the treshold, whilst another device might not reach that for even such a little bit of lower control signal amplitude (reaching the LNB). Once again, also try to cross check ports.

- switching problems result from using a loop through of another device, there can only one winner at a time...

- bad shielding contact due to crafting mishap or corrosion, losing quite some DC voltage and / or 22kHz strength by bad contact or (partly) short circuit.


So, do you use any position switching or loop through? Try to test without.
Or anything else you did not mention yet?

I use a 4 port "Maximum" DiSEqC 1.0 switch as well. This works, as I get channels from the correct sats, and it works with my OpenBox X-810 receiver.

I set Switch to 0, as I saw was recommended in some places. Then everything works fine up to 12092 (MCT and friends), and I do not get any doubles. But I am missing the higher freqs.

The specs for my LNB seems to be:
Input Low Band: 10,7 - 11,7GHz
Input High Band: 11.7 - 12,75GHz
Output Low Band: 950 - 1950MHz
Output High Band: 1100 - 2150MHz

I guess this is standard. I have selected LNB power.

More details,

the cable is the 7mm thich version (good quality), about 12 meters long. My Sat Receiver is at the end of a 25+ meter long cable and it works there with no problems, and not many percent dropoff in signal strength. So the cable is fine.

Is this a hardware issue outside the PC-box for sure ? Or could it be a driver problem ?

"I set Switch to 0", that's only making sense in USA (or on C band or similar), where band switching normally is not used.

The switch value is the frequency, above of which the 22kHz (continuous, not (just) DiSEqC pulses resp. bursts) are sent, to set the band switch to HighBand.

So, for Universal LNBs with integrated band switchung, and for European standard multiswitch systems as well, the switch value must be set to be right inside of the bands' overlapping area, between 11550 and 11900 MHz *, to not lose transponders. Default is workng.
Lower or higher values, als long as within that area, may make sense, if an LNB is a bit weaker at upper low or lower high band, or to bypass some interference issues there.
Zero means, no band switching available.

*(depends on the limits of the IF / input tuning range of tuner and software, which is normally from 950 to 2150 MHz)

the solution are the newer beta drivers:

http://www.wintvcd.co.uk/drivers/88x_2_ ... 1_WHQL.zip

it helped me for my nova hd s2. hvr4000 should also ...

install update driver with HcwDriverInstall.exe and reboot pc !

I am using the latest drivers, 2.121.25351.

But on the Hauppauge Forum, it looks like the card has problems wth DiDEqC switches. I will probably get a refund on this "defective" product,