On 06.02.2010 13:26, Ian Bates wrote: > On 6 Feb 2010, at 11:57, Klaus Schmidinger wrote: > >> On 02.02.2010 07:35, Ian Bates wrote: >>> On 1 Feb 2010, at 22:24, abbe normal wrote: >>>> On 2/1/10, VDR User <user....@gmail.com> wrote: >>>>> On Mon, Feb 1, 2010 at 7:12 AM, Halim Sahin <halim.sa...@t-online.de> >>>>> wrote: >>>>>> Hi List and Klaus, >>>>>> >>>>>> It would be really nice if vdr could support diseqc setup directly in >>>>>> vdr. >>>>>> >>>>>> I don't know if this can be done by a plugin but the current solution is >>>>>> difficult for endusers. >>>>>> Setting a diseqc.conf needs some knowledge in diseqc and it's commands. >>>>>> A simple interface for creating a diseqc.conf can improove the >>>>>> usability of vdr! >>>>> Personally I think adding support for multiple diseqc switches is a >>>>> more important feature as I've noticed several users asking how to do >>>>> this in VDR -- which it unfortunately doesn't support. I think this >>>>> is actually one of the reasons some guys fumble around trying to >>>>> cascade their diseqc switches. However, not all switches can be >>>>> cascaded and so they're left stuck. Can't cascade, and no support for >>>>> multiple switches. >>>>> >>>>> >>>> hey guys >>>> >>>> i agree multi cards should be able to use mutli diseqc configs... or >>>> at least be able to assign them to different switches that could be >>>> used... would be nice to add more dishes and lnbs to my setup... would >>>> like to do c and ku band dvb as well as have at least 2 to 3 fixed >>>> dishes with lnbs on them now im limited to 4 max or use a very costly >>>> switch... >>>> >>>> abby >>> Dear all, >>> >>> I have a diseqc-patch I that hacked together a couple of years ago relating >>> to multi-cards/multi-switches that has served my purpose well. It may not >>> be the best way, it may even be the wrong way. I will drag it out of the >>> VDR box for all to see but that will not be for a couple of days. >>> >>> MOTIVATION >>> >>> I have three LNBs (28.2/5, 19.2, 13.0) and two cards, each card attached to >>> a 4-way diseqc switch. Despite the switches being the same model and >>> bought at the same time each one responds to a different set of diseqc >>> commands to change LNB. IIRC one seemed to behave as a cascade of 2-way >>> switches, the other responded to the more usual commands for a 4-way switch. >>> >>> DESCRIPTION >>> >>> Enter my hack. It allows diseqc commands to be defined on a per-card basis >>> (numbered 1, 2, ...). How you determine which number corresponds to which >>> card is left as an exercise for the reader (hint: the margin may not be big >>> enough). These defines are placed in 'diseqc-multi.conf' and start with >>> the card number but are otherwise the same format as those found in >>> 'diseqc.conf'. >>> >>> CONFIGURATION >>> >>> Configuration options within VDR are: >>> >>> - use only the diseqc.conf defines, >>> - use only the diseqc-multi.conf, >>> - use the disqc-multi.conf if a card definition appears otherwise use the >>> diseqc.conf defines. >> I don't like the introduction of a separate diseqc-multi.conf file, >> and also those additional setup options in VDR. >> >> What about simply extending the existing diseqc.conf file to >> accept device numbers, as in: >> >> 1 2 4: >> >> 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 >> >> 3 5: >> >> S13.0E 11700 V 9750 t v W15 [E0 10 38 F4] W15 B W15 t >> S13.0E 99999 V 10600 t v W15 [E0 10 38 F5] W15 B W15 T >> S13.0E 11700 H 9750 t V W15 [E0 10 38 F6] W15 B W15 t >> S13.0E 99999 H 10600 t V W15 [E0 10 38 F7] W15 B W15 T >> >> >> This could mean that devices 1, 2 and 4 can receive S19.2E, >> while devices 3 and 5 can receive S13.0E. >> >> If no device numbers (followed by a ':') are given, a setup >> where every device can receive every satellite is assumed. >> >> Once a line with device numbers (followed by a ':') appears, >> these apply to all following diseqc lines, until the next >> line with device numbers is seen. >> If a diseqc line is parsed without a previous device line, >> that diseqc line applies to all devices. >> >> Klaus > > > Dear Klaus, all, > > That sounds good. Using this proposal I would configure my system with the > following diseqc.conf: > > # diseqc.conf > > S28.2E a1... > S28.2E a2... > S28.2E a3... > S28.2E a4... > > S19.2E b1... > S19.2E b2... > S19.2E b3... > S19.2E b4... > > S13.0E c1... > S13.0E c2... > S13.0E c3... > S13.0E c4... > > 2: > > S28.2E A1... > S28.2E A2... > S28.2E A3... > S28.2E A4... > > S19.2E B1... > S19.2E B2... > S19.2E B3... > S19.2E B4... > > S13.0E B1... > S13.0E B2... > S13.0E B3... > S13.0E B4... > > # EOF > > where [a-cA-C][1-4]... are diseqc command sequences. > > If I understand correctly, with Klaus' proposal my 'normal' switch (card 1) > would use the [a-c][1-4]... commands, and my problem switch (attached to card > 2) would use the [A-C][1-4]... commands. Any additional cards would also use > the [a-c][1-4]... commands.
You would have to put 1: at the beginning of that file, because otherwise everything before the 2: would be applicable to *all* devices, including #2. The first entry that fits will be used. > Unless I have understood incorrectly this gets my vote, if someone implements! Don't worry, I'll do that. Klaus _______________________________________________ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
