|
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 sent is the last one, but it’s sent three times. To demonstrate this I have put some trace in cDvbTuner::SetFrontend
within dvbdevice.c which traces the complete diseqc string, the diseqc action,
and for diseqc codes – the actual diseqc code sent. It produces the
following output: Diseqc command list found =
t v [E0 10 38 F4] W500 [E0 31 6B 04] W250 [E0 31 6B 04] W15 T Diseqc action = ""> Diseqc action = ""> Diseqc action = ""> Sending Diseqc command: E0
31 6B 04 < Wrong, should be E0 10 38 F4 > Diseqc action = ""> Sending Diseqc command: E0
31 6B 04 < Wrong, should be E0 31 6B 04 > Diseqc action = ""> Sending Diseqc command: E0
31 6B 04 Diseqc action = ""> The same trace in vdr 1.7.18 shows the correct codes being
sent in the correct sequence. I note that some work was done in this area for 1.7.19 but
my C++ skills are a little weak to diagnose the problem any further. Can anybody throw some more light on what’s going on? Thanks, Mark. Mark Hawes |
_______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
