Hello all.

I'm using latest progdvb 4.82.3 and in some transponders e.g. 11097, if I select a channel I have no signal at all. Now I try again selecting it a second, a third, even a fourth or fifth time by double clicking the same channel and the signal is back up to 85%(as it used to be). For as long as I'm watching the channel no problems at all. But If change channel and then select it again I have to make all the double clicks again to get the signal back.

The problem started all of a sudden without any hardware or software change.

SS1, HH120, 1.20m.
The lnb is connected straight to the card.
No dect phone nor some change in the neighborhood as wifi etc.
The transponders lists are correct.
I have used my last working channel lists and with fresh new scanned channels all with correct pids.
I also tried various old versions up to 4.56.
I give up.


Please I'm desperate...
(Just imagine my wife's face if i tell her that she has to click 5-6 times in our htpc and ...maybe... if she is lucky... and god's will........i can't give up.)
Thank you in advance.

Try to find out, if your LNB has a tiny LOF offset on one or both.

Before starting, allow the LNB to stabilize temperature for an hour, set to a horizontal transponder on any band.

For specifying a possibly necessary offset value, try search transponder, check one with that problem.
Then try to modify the transponder frequency manually, in steps of 1 MHz up and down, up to 5 MHz off center.
Click into the stations list area to execute.
Find out the lock / hold range by this.
Normally that range should be symmetrical to nominal frequency, but occasionally it is not.
This way you should be able, to find out, if that transponder comes in a bit to high or low.

Don't store anything.
Write down findings.

Try again on other transponders of the same band.

If you can specify a typical offset value for a band by this procedure, compensate by changing the LOF in use, for the same amount, but into the opposite direction.

One MHz won't mean anything, as that's a matter of transponder list precision and card / tuner specific stepping resolution, but more than one MHz in any direction should be corrected.

Afterwards, do the same on the other band, as those LOFs are independent and may have different factory alignment state....


BTW, don't do that at extreme outside temperature, as then extra offfset might occur, that normally would be handled by automatic fine tuning alone.
So neither at high noon (resp. mid day heat) nor on very early morning hours (coldest period of a day)...

I don't think that my lnb has a small offset because everything was working fine before. But I'm going to try whatever you wrote above just to be sure. If it's not the offset problem do you think that the problem lies in the lnb and I have to buy a new one or is it something else ? Could it be corrupted registry or windows or the problem that I mention has nothing to do with software?

Thank you.

Windows registry ONLY does effect the transponder availability when BDA drivers and devices used.
Means, if it's a Nexus or similar premium card, no trouble with this, as no BDA driver exists.

A bad LNB cable can behave as a sharp multiple notch filter, if causing reflections, f.e. from an occasional hit with the hammer or to sharp bend.
Same can happen, if two lengths of different cable types are used coupled on a single run.

Also a bad output driver stage of the LNB or corroded F connector can cause such.

Perhaps compare with the original or any other DVB application, to perhaps get a clue, if it's software or hardware based trouble, more or less.

Thank you very much Juergen for your efforts.
Problem solved. The lnb was off.
I bought a new one and everything is ok as before.
Thank you again.