public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Kuhlen <dkuhlen@gmx.net>
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: Sat, 21 Jun 2008 18:40:46 +0200	[thread overview]
Message-ID: <200806211840.47025.dkuhlen@gmx.net> (raw)
In-Reply-To: <200806211552.41278.ajurik@quick.cz>


[-- Attachment #1.1: Type: text/plain, Size: 1720 bytes --]

Hi,

I managed to get access to a 19.2 + 13.0 diseqc dish with a TT-S2 3600 card :)

On Saturday 21 June 2008, Ales Jurik wrote:
> Hi,
> 
> on the frequency you've mentioned I didn't have any problem (never). But at 
> lyngsat it is reported as 11914MHz. I never used freq. shifting (only 
> tested), it was not reasonable for me.
I wanted to show that there's no reason for setting all frequencies +4Mhz or -4MHz.
This is what my patch is all about :)
The request for test tuning with a offset was to confirm the "bug" i found 
in the stb0899 tuning routine

> 
> Problems I have are at transponders with 8PSK modulation. 
Well, I tested: 
19.2 12522 V 8PSK 22000 2/3
  i get 100% (and immediate) lock in the range from: 12512 to 12532
(The frontend always reports 1921MHz (i.e. 12521MHz))
the call looks like:
./simpledvbtune -f 12512 -p v -s 22000 -d 2  -a 1
using '/dev/dvb/adapter1/frontend0' as frontend
frontend fd=3: type=0
ioclt: FE_SET_VOLTAGE : 0
High band
tone: 1
dvbfe setparams :  delsys=4 1912.000MHz / Rate : 22000kSPS
Status: 1b: Signal Carrier Sync Lock
SNR: 0 22 (0x16) (2.2dB)
BER: 0 0 0 0 (0x0)
Signal: 5 170 (0x5aa) 1450 (145.0dBm)
Frontend: if=1921.821 MHz

19.2 12581 V 8PSK 22000 2/3
 works  in the range from 12570 to 12590
frontend reports: 1980 (i.e.12580)

13.0 11996 V 8PSK 27500 2/3
 works from 11986 to 12005
frontend reports: 1395 (i.e. 11995)


The other 13.0 8PSK (11278V and 11449H) are tougher:  they take a few seconds to lock and sometimes they don't lock at all
according to the NIT they use roll-off factor 0.2 (the other channels use 0.35)
This is interesting: I'll check why this takes so much longer


---snip---


Dominik

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

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

  reply	other threads:[~2008-06-21 16:41 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
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 [this message]
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=200806211840.47025.dkuhlen@gmx.net \
    --to=dkuhlen@gmx.net \
    --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