On 23.01.2011 01:09, VDR User wrote:
> I could be wrong about this but it seems I remember this subject
> coming up some time ago and Klaus mentioning rotor support is on his
> todo list. My apologies if I've got that backwards.
Well, I do have the "gotox" patch on my TODO list, but
I'm afraid it
I had to put the rotor entry in he conf twice with w20 delay between to
make the rotor dependable. And turn off all channel updating.
On 1/24/2011 12:36 PM, Seppo Ingalsuo wrote:
I made this patch because the relationship of vdr diseqc core and rotor
plugin was flaky. Despite of diseqc command
On Sun, 2011-01-23 at 21:38 -0700, Timothy D. Lenz wrote:
> Fixed number would help a little, but would get anoying and be in the
> way a lot of time. Going from one sat to the next is with in 2-3 sec's.
> It's when you need to do a full swing you run into collecting from the
> wrong sat.
Got
Fixed number would help a little, but would get anoying and be in the
way a lot of time. Going from one sat to the next is with in 2-3 sec's.
It's when you need to do a full swing you run into collecting from the
wrong sat.
On 1/23/2011 2:31 PM, Arturo Martinez wrote:
:·)
:·)
I would also
:·)
:·)
I would also like some support for rotors in vdr, I can offer Klaus a
free sat dish and an old rotor if that would motivate him...
Klaus, as a minimum in vdr core we need the ability to specify a ´lapse
value´ between a diseq command being sent (for non rotor users this
would be ze
On 01/23/11 20:37, Timothy D. Lenz wrote:
> btw, here is a collection of pdf's on rotor function:
> http://www.eutelsat.com/satellites/4_5_5.html
>
> On 1/23/2011 9:57 AM, Manuel Reimer wrote:
>> Hello,
>>
>>> I would also love to see native rotor support. The plugin crashes all
>>> the time with
btw, here is a collection of pdf's on rotor function:
http://www.eutelsat.com/satellites/4_5_5.html
On 1/23/2011 9:57 AM, Manuel Reimer wrote:
Hello,
I would also love to see native rotor support. The plugin crashes all
the time with yavdr and is virtually unusable.
IMHO it depends on how th
Actuator control requires a simple interface device for the computer to
control direction and power to a motor. This also requires a driver
which has already been made. Then there is the option to make a diseq
controller box that makes actuators look like rotors. They can be home made:
http://w
Once you have the rotor setup and locations stored in the rotors memory,
you can already control it with with the conf as it is:
S95.0W 9 V 10750 t V W15 [E0 31 6B 0E] W20 [E0 31 6B 0E] W20 [E0 10
38 FC] W5 v
S95.0W 9 H 10750 t V W15 [E0 31 6B 0E] W20 [E0 31 6B 0E] W20 [E0 10
38 FC] W5
Al 23/01/11 09:56, En/na Arthur Konovalov ha escrit:
On 22.01.2011 20:31, Timothy D. Lenz wrote:
VDR being a euro program where FTA sat is far more common should have
really good support built in.
I agree and awaiting too native rotor support in the vdr core.
What I'd like to see is that cor
Hello,
> I would also love to see native rotor support. The plugin crashes all
> the time with yavdr and is virtually unusable.
IMHO it depends on how those rotors are controlled. If they are controlled via
DISEQ and VDR, for whatever reason, fails to send the required DISEQ commands,
then VDR
On Sun, Jan 23, 2011 at 8:56 AM, Arthur Konovalov wrote:
> I agree and awaiting too native rotor support in the vdr core.
I would also love to see native rotor support. The plugin crashes all
the time with yavdr and is virtually unusable.
___
vdr mail
Hi,
Sorry I don't like such requests where the step implementing this would
be the third step before doing the first one.
Afaik rotors are controlled by diseqc commands.
What about a flexible configuration and creation of diseqc.conf directly
in vdr?
Controlling a rotor would be the next step!
Jus
On 22.01.2011 20:31, Timothy D. Lenz wrote:
VDR being a euro program where FTA sat is far more common should have
really good support built in.
I agree and awaiting too native rotor support in the vdr core.
br,
Arthur
___
vdr mailing list
vdr@linuxt
On Sat, Jan 22, 2011 at 10:32 PM, Timothy D. Lenz wrote:
> That would be nice, I thought he said he wasn't interested in doing it
> because of lack of interest. I tried to get the subject going again because
> there are people who would want it, but it seems most of those that would
> use it are n
That would be nice, I thought he said he wasn't interested in doing it
because of lack of interest. I tried to get the subject going again
because there are people who would want it, but it seems most of those
that would use it are not programmers and rely on others to write it.
There are also
I could be wrong about this but it seems I remember this subject
coming up some time ago and Klaus mentioning rotor support is on his
todo list. My apologies if I've got that backwards.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin
Al 22/01/11 19:31, En/na Timothy D. Lenz ha escrit:
I know about that plugin. Won't really help with a rotor. Different
setup. Actuators are for BUD's, Dishes over 1.2m though they have come
out with small dish systems.
Yes, my dish is 1.2m, but I fitted it for an analog receiver, long
before
I know about that plugin. Won't really help with a rotor. Different
setup. Actuators are for BUD's, Dishes over 1.2m though they have come
out with small dish systems. Normally A small dish rotro uses DiSEqC
sent up the cable to control the motor. The rotor plugin is for that,
but current versi
Hi,
What about actuator plugin from Luca http://ventoso.org/luca/vdr/ (wiki page
in German is here http://www.vdr-wiki.de/wiki/index.php/Actuator-plugin ,
use google translate to translate)?
Yarema
2011/1/22 Timothy D. Lenz
> Time to bump this request again
>
> ___
20 matches
Mail list logo
