From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: dvbv5-tools update - was: Re: [ANNOUNCE] DVBv5 tools version 0.0.1
Date: Sun, 08 Jan 2012 10:57:47 -0200 [thread overview]
Message-ID: <4F0992CB.6020702@redhat.com> (raw)
In-Reply-To: <4F08F6EB.2030508@redhat.com>
On 07-01-2012 23:52, Mauro Carvalho Chehab wrote:
> I decided to add support for DVB-S, even without signal for testing.
> This probably means that it likely will not work ;) Well, seriously,
> we need testers for it.
>
> The current code should be doing the same that szap does, and should
> work with both dvbv5-zap and dvbv5-scan. The DISEqC code there is very
> simple, and there's no support for dishpro/bandstacking yet. It is
> probably not hard to add support for it.
>
> There are still a few things missing there. For example, the current
> code will only use DISEqC satellite #0, as there's no code to change
> the satellite number yet.
>
> Anyway, testing and patches are welcome!
I decided to rewrite the DISEqC code on it, in order to fix some
bugs, and make the code clearer.
The updates are at the tree:
http://git.linuxtv.org/v4l-utils.git
Basically, additional parameters for satellite delivery systems
are now added to the zap and scan tools:
- l <lnbf>
selects the LNBf type. Using an invalid value like "help" shows
what's currently supported.
- S <sat_number>
Selects satellite number, between 0 to 3. If not specified,
disables DISEqC. This actually changes the DISEqC "option"
and "position" parameter. According with the specs, for
position B, tone should be off, and tone burst should
be miniA.
-W <extra time in ms>
The DISEqC logic will wait for 15 ms. If this parameter is
specified, it will add the extra time to the 15ms delay.
For LNBf devices that use bandstacking (e. g. they use different
LO frequrencies for V and H polarization), the code will
always use 13 Volts and will disable tone/tone burst.
Currently, C-Band multi and DishPro bandstacking LNBf's are
supported.
The code should now work with the following LNBfs:
UNIVERSAL
Europe
10800 to 11800 MHz and 11600 to 12700 MHz
Dual LO, IF = lowband 9750 MHz, highband 10600 MHz
DBS
Expressvu, North America
12200 to 12700 MHz
Single LO, IF = 11250 MHz
STANDARD
Standard
10945 to 11450 MHz
Single LO, IF = 10000 MHz
ENHANCED
Astra
10700 to 11700 MHz
Single LO, IF = 9750 MHz
C-BAND
Big Dish - Monopoint LNBf
3700 to 4200 MHz
Single LO, IF = 5150 MHz
C-MULT
Big Dish - Multipoint LNBf
3700 to 4200 MHz
Dual LO, Bandstacking, LO POL_R 5150 MHZ, LO POL_L 5750 MHz
DISHPRO
DishPro LNBf
12200 to 12700 MHz
Dual LO, Bandstacking, LO POL_R 11250 MHZ, LO POL_L 14350 MHz
Tests are needed!
Regards,
Mauro
next prev parent reply other threads:[~2012-01-08 12:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 12:19 [ANNOUNCE] DVBv5 tools version 0.0.1 Mauro Carvalho Chehab
2012-01-07 17:29 ` Honza Petrouš
2012-01-07 20:05 ` Mauro Carvalho Chehab
2012-01-08 1:52 ` Mauro Carvalho Chehab
2012-01-08 12:57 ` Mauro Carvalho Chehab [this message]
2012-01-10 21:36 ` Antti Palosaari
2012-01-10 22:00 ` Mauro Carvalho Chehab
2012-01-15 18:37 ` Antti Palosaari
2012-01-15 20:03 ` Antti Palosaari
2012-01-15 21:08 ` Mauro Carvalho Chehab
2012-01-15 21:14 ` Antti Palosaari
2012-01-15 21:47 ` Antti Palosaari
2012-01-16 0:16 ` Mauro Carvalho Chehab
2012-01-16 2:57 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F0992CB.6020702@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).