Page 1 of 1
Twin LNB
Posted: Tue Dec 05, 2006 5:30 pm
by Bekkeman
Hello,
I'm new here and I'm Dutch. So my english will sometimes be bad.
I have 2 problems.
First is, that we have a twinLNB with on one side a Philips reciever and on the other side this PC with a ThinHan dvb-s card with CI.
When I want to search for dutch channels on Astra 19.2 the card can't find anything. Only a couple foreign channels like 2M Maroc. When i put de card to another, single LNB, it can find all channels.
How is that possible? There is enough signal on the twin lnb. 87 %
And the LNB does only work when the other reciever on the LNB is turned on. I did select Power to LNB in Progdvb.
Second problem is the CI. It does'nt recognize any CAM. I tried 2. One Official Canaldigital cam module (official in Holland) and a Aston 1.05. I've used the plugin 'CI module' in ProgDVB too. Doesn't make any differance. It just doesn't recognize any cam, I only get a message 'CAM not found..etc'. This i have solved with PMCam. That does work. But it would be better with the original CI and CAM.
That was all

. Maybe a bit much for the first post, but I hope someone can help me!
Greetings,
Harm
Posted: Tue Dec 05, 2006 9:19 pm
by Juergen
First issue, try to cross change the ports of the Twin LNB.
Check the F connectors carefully, water protect them.
Find out, if there's something systematic to be found, on transponders working, like just verticals, or just above 11600 MHz or alike.
If not yet done, have the (dynamic) channel list grouped by transponders, for an easy overview.
Second issue, the CAM menu is not working AFAIK, but CAMs should work, if the DVB card is supported properly.
Posted: Tue Dec 05, 2006 10:05 pm
by Bekkeman
Hello Juergen,
Thanks for the replay.
The weird thing is that, there were first 2 recievers connected to the twin lnb. They both worked good!
When i scan for channels on astra 19.2, progdvb scans 69 transponders. The firts couple of transponders everything works well, horizontal and vertical. Progdvb finds a couple of channels (those foreign channels). The signal quality and level variate, but keep around the 90%! after 4 or 5 transponders the signal quality disappears and signal level gets stuck on 80% and doesn't variate no more, only 80%. And that one (level)dissappears sometimes as well. Then progdvb doesn't find any channels anymore.
Not only Progdvb has this problem, also other programs have it. Also the original of Pinnacle and a couple more. Only on a single lnb, progdvb can find the right channels. I can't find the channels manualy aswel.
_______________________________________________________
EDIT:
I have a channel list that was made on the single LNB with the right dutch channels.
When I connect the dvb-scard on the twin lnb, the signal also fall back to 80% level and no quality when I select such Dutch channel. I'm really confused

Posted: Wed Dec 06, 2006 7:56 pm
by Juergen
Perhaps a small LOF deviation causes this, small enough to be compensated by the STBs' AFC, but too big for DVB software.
Best way to test and quantify may be to (fine) tune a (working) transponder up and down in small steps of 1 MHz manually, to specify a deviation between middle of hold range and nominal frequency. Compensate LOF (in use) for that amount to the opposite direction.
Posted: Thu Dec 07, 2006 11:27 am
by Bekkeman
Wow
That went a bit too fast for me.
STBs' AFC are standard recievers?
Do you mean in other words, that the sattelite dish itself isn't positionised in the wright direction to the Astra?
And how can I fine tune a transponder in Progdvb?
Posted: Thu Dec 07, 2006 10:59 pm
by Juergen
Nope...
STBs are Set Top Boxes, AFC is Automatical Frequency Control.
This is not about dish adjusment but factury alignment and temperature caused tolerances of LNBs' LOFs.
These Local Oscillator Frequencies (the down conversion amount) have to be VERY accurate, plus / minus less than three MHz, to allow tuners to lock on signals. Compared to LOFs in the 10 GHz range, a tolerance of less than 3 MHz means 0,03 % ~ 300ppm.
Now, of course there are difference in the lock and hold tolerance on tuning systems. So, if some device locks, but another does not, their tolerance fields might differ a bit. But the real cause would still be a LOF deviation, that could be compensated by correcting the LOF entry to the real value. Re-tuning an LNB's LOFs would require opening and using a high precision SHF counter, that's not available for the normal user.
So trying to specify a LOF deviation the way I told is the only chance, besides LNB exchange.
However, all I told is just theory, as I cannot come around to test your hardware...
Manual (fine) tuning can be done in menue "Channel List" --> "Scan Transponder"
Posted: Fri Dec 08, 2006 9:20 am
by Bekkeman
Okay, thanks for the explanation again,
But it is a coincidence that now our twin lnb is broken. It happen before I read the replay.
So I didn't do it to buy a new one
I wanted to cross change the cables on the lnb and one broke. Now we have a single.
So I have to get a new one.
On the old one there were a couple of numbers on it:
ALPS
10.7 - 12.75 GHz
LO 1/2 9.75/ 10.6
I don't know the meanig, but does it anything to do with the LOF?
Posted: Fri Dec 08, 2006 6:06 pm
by Juergen
Bekkeman wrote:I don't know the meanig, but does it anything to do with the LOF?
Yes, definitely.
ALPS
brand / manufacturer
10.7 - 12.75 GHz
(input) frequency range
LO 1/2 9.75/ 10.6
LOF1=9750MHz LOF2=10600MHz
Posted: Wed Dec 13, 2006 7:24 pm
by Bekkeman
It Works !! Er functioniert!
Herzilichen dank Juergen!
Den neuen LNB hat der Trick gemacht!