public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Ales Jurik <ajurik@quick.cz>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Re : No lock on a particular transponder with TT S2-3200
Date: Thu, 5 Jun 2008 22:52:00 +0200	[thread overview]
Message-ID: <200806052252.00842.ajurik@quick.cz> (raw)
In-Reply-To: <1212695886l.9365l.0l@manu-laptop>

On Thursday 05 of June 2008, manu wrote:
> Well so this would point to a problem involving FEC. But is that a
> problem to get a lock? I mean FEC is just involved after a successful
> tuning, right? So even tuning is a problem IMHO and FEC might be
> another one.
> I hope that someone else can elaborate/confirm or not.
> Bye
> Manu

Well, I've tried to confirm wheather or not some values of FEC disables the 
successful lock. I've found transponder in DVB-S2 which is receivable 
immediately after tuning to with the same FEC (3/4). But I've found that all 
transponders on which I'm not able to get lock have FEC eq to 2/3 or 3/4 and 
modulation of type 8PSK. Transponders with FEC 3/4 and modulation QPSK are 
receivable without problem.

I'll be very glad if someone else could confirm or disagree with my tests as I 
didn't do test tuning on all DVB-S2 channels. 

BR,

Ales

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-06-05 20:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 20:19 [linux-dvb] No lock on a particular transponder with TT S2-3200 manu
2008-06-05 18:47 ` Ales Jurik
2008-06-05 19:58   ` [linux-dvb] Re : " manu
2008-06-05 20:52     ` Ales Jurik [this message]
2008-06-05 20:23 ` [linux-dvb] " Dominik Kuhlen
2008-06-05 22:27   ` [linux-dvb] Re : " manu

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=200806052252.00842.ajurik@quick.cz \
    --to=ajurik@quick.cz \
    --cc=linux-dvb@linuxtv.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