From: Ales Jurik <ajurik@quick.cz>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Re : Re : No lock possible at some DVB-S2 channels with TT S2-3200/linux
Date: Sun, 15 Jun 2008 19:20:30 +0200 [thread overview]
Message-ID: <200806151920.30719.ajurik@quick.cz> (raw)
In-Reply-To: <200806151147.19451.dkuhlen@gmx.net>
On Sunday 15 of June 2008, Dominik Kuhlen wrote:
> Hi,
>
> On Thursday 22 May 2008, Ales Jurik wrote:
> > Hi,
> >
> > my friend told me that he is sometimes able to get lock by decreasing
> > (not increasing) the frequency. Yesterday I've tested it and it seems to
> > me he was right. So I'm able to get (not very stable, for few minutes)
> > lock as well as by increasing and by decreasing frequency of the same
> > channel (EurosportHD).
>
> The derotator code in the stb0899 seems to be setting the initial frequency
> to the lowest search range and never changes this (as it should increase
> steadily to find a lock)
>
> > It was also detected (not by me, I don't have riser card) that when the
> > card is connected not directly into PCI slot but with some riser card,
> > the needed difference for getting lock is higher (up to 10MHz). So also
> > some noise from PC is going into calculations.
> >
> > I don't think the problem is in computation of frequency but in for
> > example not stable signal amplitude at input of demodulator or in not
> > fluently changing the gain and bandwith of tuner within the band. As I
> > see in the code some parameters are changing in steps and maybe 3 steps
> > for whole band is not enough? Especially in real conditions (not in lab)?
>
> Could you please try the attached patch if this fixes the problem with
> nominal frequency/symbolrate settings?
>
Many thanks, but I don't see any improvement. Minimum time after I've lock is
150s.
The only improvement was done 2weeks ago when Manu Abraham fixed some headers
with register addresses. From that time it is possible to get lock also at
problematic channels but very unstable.
But I've found that all channels with lock problems are DVB-S2, 8PSK, FEC 3/4.
So all channels broadcasted in QPSK is possible to tune without problems and
also channels broadcasted in DVB-S2, 8PSK, FEC 2/3 are possible to tune to
without problems. Channels in DVB-S2, 8PSK with different FEC (to 2/3 and
3/4) I was not able to test.
Do you think that info could be useful?
BR,
Ales
> > But under Windows no problems were detected, so it seems that all that
> > problems are solveable by driver (software).
> >
> > BR,
> >
> > Ales
> >
> >
> >
> > _______________________________________________
> > linux-dvb mailing list
> > linux-dvb@linuxtv.org
> > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
> Dominik
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-06-15 17:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 18:42 [linux-dvb] No lock possible at some DVB-S2 channels with TT S2-3200/linux Ales Jurik
2008-05-13 17:58 ` [linux-dvb] Re : " manu
2008-05-13 21:26 ` Ales Jurik
2008-05-13 22:01 ` [linux-dvb] Re : " manu
2008-05-22 8:13 ` Ales Jurik
2008-05-22 9:34 ` [linux-dvb] Re : Re : No lock possible at some DVB-S2 channelswith " Igor
2008-06-15 9:47 ` [linux-dvb] Re : Re : No lock possible at some DVB-S2 channels with " Dominik Kuhlen
2008-06-15 17:20 ` Ales Jurik [this message]
2008-06-16 2:21 ` [linux-dvb] Re : " manu
2008-06-16 8:20 ` Ales Jurik
2008-06-16 19:14 ` joep
2008-06-16 20:26 ` ChaosMedia > WebDev
2008-06-16 20:45 ` Ales Jurik
2008-06-20 13:18 ` Daniel
2008-06-20 13:47 ` Ales Jurik
2008-06-20 14:33 ` Daniel
2008-06-20 15:32 ` psofa
2008-06-20 15:45 ` joep
2008-06-21 12:36 ` [linux-dvb] " Dominik Kuhlen
2008-06-21 13:52 ` Ales Jurik
2008-06-21 16:40 ` Dominik Kuhlen
2008-06-21 17:20 ` Ales Jurik
2008-06-22 18:19 ` psofa
2008-06-26 19:58 ` Goga777
-- strict thread matches above, loose matches on Subject: below --
2008-06-15 19:31 psofa
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=200806151920.30719.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