[vdr] Re: DiSEqC support

[Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>]

Oliver Endriss wrote:
> 
> Reinhard Walter Buchner wrote:
> > I tried the new Diseqc system, but it didn't work for me.
> 
> Could you please describe your setup a little bit more in detail?
> Are you using a multi-switch or is the rotor directly connected to your
> DVB-S? How are the devices connected?
> 
> > Here is part of my conf file:
> >
> > S19.2E 11700 V 9750 t v W15 [E1 31 69 40] W3500 W15 t
> > S19.2E 99999 V 10600 t v W15 [E1 31 69 40] W3500 W15 T
> > S19.2E 11700 H 9750 t V W15 [E1 31 69 40] W3500 W15 t
> > S19.2E 99999 H 10600 t V W15 [E1 31 69 40] W3500 W15 T
> >
> > This should tell the motor to move eastwards continiously.
> 
> For the first transmission you should always use command E0.
> E1 is for retransmissions only. You could also try E0 00 69 40
> which would address all devices.

Also make sure you are using the NEWSTRUCT driver and compile VDR with
NEWSTRUCT=1. With the old driver only [E0 ...] commands will work, since
the 0xE0 value is hardcoded in the old driver.

> > S30W 11700 V 9750 t v W15 [E0 30 6B 14] W3500 W15 t
> > S30W 99999 V 10600 t v W15 [E0 30 6B 14] W3500 W15 T
> > S30W 11700 H 9750 t V W15 [E0 30 6B 14] W3500 W15 t
> > S30W 99999 H 10600 t V W15 [E0 30 6B 14] W3500 W15 T

With W3500 I'd say you can leave out the following W15 (just a
cosmetic, whouldn't make much difference).

> > This should tell the motor to move to Satellite position 14
> > (which is Hispasat 30W in my case)
> 
> Just an idea: All values are in hex, so 14 hex = 20 decimal.
> 
> > VDR gives no error messages other than DVB card not syncd
> > on channel 2 (which I used for Via Voice on Hispasat). That
> > is why I upped the Wait time to 3.5 seconds, but it didn't help
> > and the motor doesn`t budge at all.

Are you sure your motor reaches the position within 3.5 seconds?
From any initial position of the antenna?
That's quite a fast move!

Since there are apparently setups with longer wait times, I guess I'll
need to check whether the DiSEqC commands actually need to be executed
when tuning (i.e. whether the actual command string has changed compared to
the previous channel).

> > Can anyone confirm or deny the diseqc motor function? Or does
> > anyone see where I goofed?
> 
> I can confirm that DiSEqC works. I see no reason why motor commands
> should not be transmitted.
> 
> > Using WatchTVPro and Windows the motor works. So I know the
> > card is okay and can supply enough power to the motor to move
> > the dish.
> 
> Can you find out which DiSEqC commands are sent by this program?
> 
> > BTW what does the "99999" stand for?
> 
> It is just a value higher than any transponder frequency which can be
> received. Therfore this entry will apply for all frequencies > 11700
> and < 99999.

I guess I'll have to describe that in vdr.5 - I thought it would be obvious ;-)

Klaus
-- 
_______________________________________________________________

Klaus Schmidinger                       Phone: +49-8635-6989-10
CadSoft Computer GmbH                   Fax:   +49-8635-6989-40
Hofmark 2                               Email:   kls@cadsoft.de
D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de
_______________________________________________________________


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