[vdr] Rotor plugin

["Sameer Khosla" <sameerkhosla@rogers.com>]

Hi all, 

First post to the list, but I've been reading for several months and quietly
playing with my vdr setup here.

The problem I am running into is this - I had a working setup with a 4-port
diseqc aimed at 4 birds.  Everything worked beautifully.

Yesterday I replaced the diseqc switch with an SG2100 rotor.  
I figured out how to configure my diseqc.conf to issue goto stored positions
on the rotor as follows:

S119.0W 99999 V 11250 t v W15 [E0 31 6B 30]
S119.0W 99999 H 11250 t V W15 [E0 31 6B 30]
S91.0W 99999 V 11250 t v W15 [E0 31 6B 31]
S91.0W 99999 H 11250 t V W15 [E0 31 6B 31]
S110.0W 99999 V 11250 t v W15 [E0 31 6B 32]
S110.0W 99999 H 11250 t V W15 [E0 31 6B 32]
S61.5W 99999 V 11250 t v W15 [E0 31 6B 33]
S61.5W 99999 H 11250 t V W15 [E0 31 6B 33]


Indoor testing without dish proves that channel surfing between channels w/
different sources makes the appropriate motor adjustment.

The issue I am running into is this. When trying to aim, the rotor plugin
shows very low signal no matter what.  However if I move the dish to a point
where it should have a view of a particular orbital (so far I have been
successful with S82W/S91W), it still shows no signal..

Unloading the driver, and reloading it, starting vdr it then has signal.  If
I store that position, move away, and then come back to the stored position,
it shows low signal.  Once again, reloading the driver solves the problem.

It appears than any movement away from a signal will cause the receiver to
no longer tune a signal.

I am wondering if maybe I am doing something wrong. 

I am using a Nexus-s 2.2, 2.4.25 kernel, 2003-11-08 driver, vdr-1.2.6,
rotor-0.0.5.

sk.



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.