[vdr] diseqc.conf with different lines for each frontend

Teemu Suikki tsuikki at zuik.org
Thu Feb 7 22:36:04 CET 2013


Hi!

I have vdr 1.7.27, from yavdr 0.5.

I have two frontends, one has fixed dish to 1.0W and other is a motorized
dish than can tune any satellite.

I have tried rotorng plugin, but I see that it's entirely possible to let
VDR do the dish control with diseqc.conf.. this is my diseqc.conf file:

1:
S1.0W  11700 V  9750  v t
S1.0W  99999 V 10600  v T
S1.0W  11700 H  9750  V t
S1.0W  99999 H 10600  V T

2:
S1.0W 11700 V  9750  t W15 [E0 31 6B 19] W15 v t
S1.0W 99999 V 10600  t W15 [E0 31 6B 19] W15 v T
S1.0W 11700 H  9750  t W15 [E0 31 6B 19] W15 V t
S1.0W 99999 H 10600  t W15 [E0 31 6B 19] W15 V T

S13.0E 11700 V  9750  t W15 [E0 31 6B 13] W15 v t
S13.0E 99999 V 10600  t W15 [E0 31 6B 13] W15 v T
S13.0E 11700 H  9750  t W15 [E0 31 6B 13] W15 V t
S13.0E 99999 H 10600  t W15 [E0 31 6B 13] W15 V T
(other satellites here too, just two shown)

------------------------------

This works well. VDR moves the dish, works with rotorng disabled.

But the problem is, VDR seems to prefer frontend 2 for some reason. If
frontend 2 is tuned to S13.0E and I switch to channel on S1.0W, I have to
wait for the dish to turn.. Frontend 1 would have been tuned already!

It's worse if there is a timer recording on S1.0W. VDR chooses frontend 2
even if there is only one recording going. Then I can't switch to other
satellites at all, the only moving dish is stuck to S1.0W..

Now, the obvious solution is to remove S1.0W from frontend2 config.. But
then frontend2 can't help if there's duplicate timers on S1.0W.

Is there any way to make frontend1 higher priority, so it would be used
first if it can tune?

-- 
Teemu Suikki
http://www.z-power.fi/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.linuxtv.org/pipermail/vdr/attachments/20130207/dd42fdfe/attachment.html>


More information about the vdr mailing list