Re: [vdr] Request for rotor/actuator support integration to vdr

2011-01-23 Thread Arthur Konovalov
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

Re: [vdr] Request for rotor/actuator support integration to vdr

2011-01-23 Thread Halim Sahin
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!

Re: [vdr] Request for rotor/actuator support integration to vdr

2011-01-23 Thread Morfsta
On Sun, Jan 23, 2011 at 8:56 AM, Arthur Konovalov art...@gmail.com 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.

Re: [vdr] Request for rotor/actuator support integration to vdr

2011-01-23 Thread Manuel Reimer
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

Re: [vdr] Request for rotor/actuator support integration to vdr

2011-01-23 Thread Luca Olivetti
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

Re: [vdr] Request for rotor/actuator support integration to vdr

2011-01-23 Thread Timothy D. Lenz
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]

Re: [vdr] Request for rotor/actuator support integration to vdr

2011-01-23 Thread Timothy D. Lenz
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

Re: [vdr] Request for rotor/actuator support integration to vdr

2011-01-23 Thread Ales Jurik
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 yavdr and is

Re: [vdr] Request for rotor/actuator support integration to, vdr

2011-01-23 Thread Arturo Martinez
:·) :·) 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

Re: [vdr] Request for rotor/actuator support integration to, vdr

2011-01-23 Thread Timothy D. Lenz
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