Andrew de Quincey wrote: > > > When I compiled the latest VDR developer version with the dvb-kernel > > header files, everything compiled just fine - so I would assume that there > > was no change in the API (besides, it has always been emphasized that the > > API did not change between DVB and dvb-kernel). > > > > Sendeing DiSEqC codes in VDR is done via the > > > > ioctl(fd_frontend, FE_DISEQC_SEND_MASTER_CMD, &cmd)); > > > > call - is this no longer the way to go? > > According to the DISEQC spec you're supposed to do the following for max. > compatability: > ioctl(fd, FE_SET_TONE, SEC_TONE_OFF); > ioctl(fd, FE_SET_VOLTAGE, voltage); > usleep(15000); > ioctl(fd, FE_DISEQC_SEND_MASTER_CMD, &dCmd); > usleep(15000); > ioctl(fd, FE_DISEQC_SEND_BURST, miniCmd); > usleep(15000); > ioctl(fd, FE_SET_TONE, tone); > usleep(15000);
That's what VDR does with its default DiSEqC setup: S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W15 A W15 t S19.2E 99999 V 10600 t v W15 [E0 10 38 F1] W15 A W15 T S19.2E 11700 H 9750 t V W15 [E0 10 38 F2] W15 A W15 t S19.2E 99999 H 10600 t V W15 [E0 10 38 F3] W15 A W15 T However, if I have equipment where I know that just plain hex commands work, I don't see the need for doing tone and voltage handling. Turning on the LNB voltage at all is something I believe the driver should do when the frontend is opened. Klaus -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
