From: Klaus Schmidinger <Klaus.Schmidinger@tvdr.de>
To: linux-media@vger.kernel.org
Subject: Re: [linux-media] stb0899: no lock on dvb-s2 transponders in SCR environment
Date: Sat, 27 Apr 2013 16:51:26 +0200 [thread overview]
Message-ID: <517BE5EE.6050004@tvdr.de> (raw)
In-Reply-To: <517BC11E.50105@gmx.de>
On 27.04.2013 14:14, Reinhard Nissl wrote:
> Hi,
>
> my stb0899 card works properly on dvb-s and dvb-s2 transponders when using a direct port on my sat multiswitch.
>
> When using a SCR port on that multiswitch and changing VDR's config files accordingly, it only locks on dvb-s transponders.
>
> A SCR converts the selected transponder's frequency after the LNB (IF1) to a fixed frequency (for example 1076 MHz) by mixing the signal with a local oscialator frequency above IF1 so that the lower sideband of the mixing product appears at 1076 MHz.
>
> The lower sideband's spectrum is mirrored compared to the upper sideband, which is identical to the original spectrum on the original IF1.
>
> Could that be the reason why the stb0899 cannot lock on dvb-s2 transponders in an SCR environment?
>
> Any ideas on how to get a lock on dvb-s2 transponders?
Just wanted to let you know that I can confirm the problem with
the stb0899. On my TT S2-6400 I can receive DVB-S and DVB-S2 just
fine with SCR. During development of SCR support for VDR I guess
I did all tests with the 6400, so I didn't come across this problem.
However, as a reaction to your posting I explicitly tested it with
my budget cards, and there I indeed can only tune to DVB-S transponders.
No idea how to solve this, though...
Klaus
next prev parent reply other threads:[~2013-04-27 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 12:14 stb0899: no lock on dvb-s2 transponders in SCR environment Reinhard Nissl
2013-04-27 14:51 ` Klaus Schmidinger [this message]
2013-05-05 11:21 ` [linux-media] Re: [linux-media] " Reinhard Nissl
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=517BE5EE.6050004@tvdr.de \
--to=klaus.schmidinger@tvdr.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.