I've done some further investigation and as far as I can tell the
problem appears to be with the value returned by cDiseqc::Codes in
diseqc.c.
The return value changed from 'uchar' to 'const uchar' between 1.7.18
and 1.7.19 and the returned value now always points to the last diseqc
code in the
Am 25.07.2011 13:12, schrieb Hawes, Mark:
I’ve done some further investigation and as far as I can tell the
problem appears to be with the value returned by cDiseqc::Codes in
diseqc.c.
The following trace from 1.7.19 shows the problem:
Received from diseqc-Codes(n) a pointer 137345509
Thanks Udo, that seems to have done the trick.
I guess Klaus will pick this up as a matter of course ...
Regards,
Mark.
-Original Message-
From: Udo Richter [mailto:udo_rich...@gmx.de]
Sent: Tuesday, 26 July 2011 5:19 AM
To: VDR Mailing List
Subject: Re: [vdr] Diseqc problems
Hi,
Since upgrading to VDR 1.7.19 I have experienced problems with Diseqc.
My diseqc configuration uses command strings which contain 3 code sets:
a diseqc switch command, a diseqc go to command, and a repeat goto
command.
Since upgrading to VDR 1.7.19 it appears that the only code set
Just looked at the trace I sent in my initial post and realised that I
had selected a Diseqc command that I had modified while trying to
diagnose the situation so my annotations were a bit misleading.
The following should be less confusing:
Diseqc command list found = t v [E0 10 38 F4] W500
