Markus Hahn wrote: > Am Mittwoch, 11. Januar 2006 14:43 schrieb Klaus Schmidinger: > >>Oleg wrote: >> >>>S36.0E 00000 V 10750 t v W15 [E0 10 38 FC] W15 A W15 t >>>S36.0E 99999 V 10750 t v W15 [E0 10 38 FD] W15 A W15 T >>>S36.0E 00000 H 10750 t V W15 [E0 10 38 FE] W15 A W15 t >>>S36.0E 99999 H 10750 t V W15 [E0 10 38 FF] W15 A W15 T >> >>VDR also supports L and R for circular polarization. >>See man vdr.5 (sorry, I just saw that I had forgotton to >>add this to the diseqc.conf file as comment. > > > so it should be like this?? > S36.0E 00000 V 10750 t v W15 [E0 10 38 FC] W15 A W15 t > S36.0E 99999 R 10750 t v W15 [E0 10 38 FD] W15 A W15 T > S36.0E 00000 H 10750 t V W15 [E0 10 38 FE] W15 A W15 t > S36.0E 99999 L 10750 t V W15 [E0 10 38 FF] W15 A W15 T I don't think that mixing V/H and R/L on the same satellite is done - or is it? In nit.c the polarization will be set to h, v, r, or l, depending on the data broadcast for a particular transponder. The data in diseqc.conf has to use H/V or R/L correspondingly. > @KLS > > what`s the point with this strange SLOF (Switch Local OszilatorFreqency) > is it possible to calculate it from Hi an Lo LOF? # slof: switch frequency of LNB; the first entry with # an slof greater than the actual transponder # frequency will be used Example: 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 Everything below (and including) 11700 will be considered "low band" and will use the first DiSEqC line. Everything above 11700 will be "high band" and use the second line. There could even be more than two lines, dividing the frequency range into more sections. In the original data above, the 00000 will cause _all_ transponders to use that line, and the 99999 line will never be used. Don't know why he did that. Klaus
