[mythtv-commits] Ticket #5703: MythTV unable to use disecq (Only first disecq switch works)
MythTV
mythtv at cvs.mythtv.org
Fri Jul 3 07:30:29 UTC 2009
#5703: MythTV unable to use disecq (Only first disecq switch works)
--------------------------------+-------------------------------------------
Reporter: skerit at kipdola.com | Owner: danielk
Type: defect | Status: closed
Priority: minor | Milestone: 0.21.1
Component: mythtv | Version: 0.21-fixes
Severity: medium | Resolution: invalid
Mlocked: 0 |
--------------------------------+-------------------------------------------
Comment(by anonymous):
Hello,
I can confirm the issue with the multytenne dish.
The problem is, I think, in the repeated DiSeqC command.
The first command itself is correct.
Mythtv debugging only logs the first command sent, not the repeats, so I
can not confirm if the repeated commands are correct.
The UI of Mythtv-setup requires to send at least 1 repeat.
I don't think this is needed as per DiSeqC specifications.
Repeats are only for cascading multiple switches.
A fix would be to allow in mythtv-setup to specify "0" (zero) as a valid
number of repeats.
When changing the "cmd_repeat" column in the DiSeqC_tree table of the
database manualy to "0", the multytenne dish works perfectly.
This is more or less what the patch tried to do: not sending a repeated
command.
I didn't do any testing, but I think this is one or 2 things:
- A timing issue where the repeated command is simply sent to quickly for
the multytenne (The DiSeqC specification says "at least" 15ms between
DiSeqC messages, mythtv does exactly 15ms.)
- Or the repeated commands are wrong. (There is a lot of DiSeqC equipment
that simply ignore repeated commands...)
Would it be possible to change the user interface of mythtv-setup to make
it possible to send 0 repeats?
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5703#comment:9>
MythTV <http://www.mythtv.org/>
MythTV
More information about the mythtv-commits
mailing list