* Symbol rate limit for TT 3200
@ 2009-03-05 18:04 Manu
2009-09-23 14:36 ` Lou Otway
0 siblings, 1 reply; 3+ messages in thread
From: Manu @ 2009-03-05 18:04 UTC (permalink / raw)
To: linux-media@vger.kernel.org, Manu Abraham
Hi all,
I have been struggling for quite a while to lock on a DVB-S2
transponder. And recently I got some information that they changed the
symbol rate to 45MS/s which looks borderline to me. Can someone confirm
that the TT 3200 can do that?
I also attach a log that I obtained when trying to lock on this
transponder with the following parameters:
QPSK, FEC= 5/6, 45MS/s
The driver I used was Igor's (very recent) one with szap-s2. The status
oscillates between 00 and 0b, it can take long to attain 0b which
suggests long and unreliable lock (never got VITERBI, just demod lock
+sync).
Thx for any help
Bye
Emmanuel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Symbol rate limit for TT 3200
@ 2009-03-05 18:06 Manu
0 siblings, 0 replies; 3+ messages in thread
From: Manu @ 2009-03-05 18:06 UTC (permalink / raw)
To: linux-media@vger.kernel.org, Manu Abraham
[-- Attachment #1: Type: text/plain, Size: 79 bytes --]
I know I know I forgot to attach the log ;-)
Here you go...
Bye
Emmanuel
[-- Attachment #2: TP-45000-SR-FEC-56-Lock-SYNC-but-No-VITERBI.txt.bz2 --]
[-- Type: application/x-bzip, Size: 7794 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Symbol rate limit for TT 3200
2009-03-05 18:04 Symbol rate limit for TT 3200 Manu
@ 2009-09-23 14:36 ` Lou Otway
0 siblings, 0 replies; 3+ messages in thread
From: Lou Otway @ 2009-09-23 14:36 UTC (permalink / raw)
To: Manu; +Cc: linux-media@vger.kernel.org, Manu Abraham
Manu wrote:
> Hi all,
> I have been struggling for quite a while to lock on a DVB-S2
> transponder. And recently I got some information that they changed the
> symbol rate to 45MS/s which looks borderline to me. Can someone confirm
> that the TT 3200 can do that?
> I also attach a log that I obtained when trying to lock on this
> transponder with the following parameters:
> QPSK, FEC= 5/6, 45MS/s
> The driver I used was Igor's (very recent) one with szap-s2. The status
> oscillates between 00 and 0b, it can take long to attain 0b which
> suggests long and unreliable lock (never got VITERBI, just demod lock
> +sync).
> Thx for any help
> Bye
> Emmanuel
> --
>
I've been having a similar problem and have tried using the patch from
Igor Liplianin.
http://marc.info/?l=linux-dvb&m=122730082915638&w=2
Unfortunately this patch didn't work for my device until I reduced
hi_clk to 110MHz.
I'm concious that Manu Abraham (to avoid confusion with the OP, also
called Manu) doesn't recommend a frequency higher than 99MHz.
Is this a device limitation? What are the chances of damaging the device
by setting a clock frequency higher than 99MHz?
Many thanks,
Lou
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-09-23 14:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-05 18:04 Symbol rate limit for TT 3200 Manu
2009-09-23 14:36 ` Lou Otway
-- strict thread matches above, loose matches on Subject: below --
2009-03-05 18:06 Manu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox