All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kovacs Balazs <basq@bitklub.hu>
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] S2API + TT3200 + Amos4w 10.723 S2 problem
Date: Mon, 3 Nov 2008 11:51:16 +0100	[thread overview]
Message-ID: <167586304.20081103115116@bitklub.hu> (raw)

Hi All!

  I tried a few variation, but without any success:

  I try to lock (stable! :)) on our new transponders at Amos 4W:

10,723(V) GHz, DVB-S2/8PSK, SR:30000, FEC:2/3, MPEG-4/Conax
10,759(V) GHz, DVB-S2/8PSK, SR:30000, FEC:2/3, MPEG-4/Conax
10,842(V) GHz, DVB-S2/8PSK, SR:30000, FEC:2/3, MPEG-4/Conax

with a TT3200 card + Debian etch with 2.4.24 etchnhalf kernel + the current V4L-DVB mercurial drivers compiled.

  The drivers recognizes my card, and for example it works good with Premiere's S2 transponders at Astra 19.2E. 

But it won't lock stable on our Amos's transponders.

  FYI: on these TP's there's a pilot signal and rolloff set to 0.20. I tried to push these parameters to scan-s2 and szap-s2, but scan-s2 sometimes lock and sometimes won't on these transponders and also szap-s2 (after a few try to lock with scan-s2 and get the channels.conf from these transponders) sometimes locks, but it's not stable, it lost lock after a few seconds.

  What I recognized also: if i run szap-s2 on our transponders it gives me the status message lines much slower than on other TP's.

it almost always looks like this:

/usr/src/dvb/s2api/szap-s2# ./szap-s2-thome.sh
reading channels from file '/root/.szap/channels.conf'
zapping to 1 '1':
delivery DVB-S2, modulation 8PSK
sat 0, frequency 10723 MHz V, symbolrate 30000000, coderate 2/3, rolloff 0.20
vpid 0x00b3, apid 0x00b1, sid 0x00b4
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 00 | signal 00b1 | snr 0000 | ber 00000000 | unc fffffffe |
status 00 | signal 00b1 | snr 0000 | ber 00000000 | unc fffffffe |
status 00 | signal 00b1 | snr 0000 | ber 00000000 | unc fffffffe |
status 00 | signal 00b1 | snr 0000 | ber 00000000 | unc fffffffe |
status 00 | signal 00b1 | snr 0000 | ber 00000000 | unc fffffffe |
status 00 | signal 00b1 | snr 0000 | ber 00000000 | unc fffffffe |
status 00 | signal 00b1 | snr 0000 | ber 00000000 | unc fffffffe |

but sometimes it can lock, very rare...

please, help me.

thanks,

Basq







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

             reply	other threads:[~2008-11-03 10:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 10:51 Kovacs Balazs [this message]
2008-11-03 12:04 ` [linux-dvb] S2API + TT3200 + Amos4w 10.723 S2 problem Alex Betis
2008-11-03 12:59 ` Goga777
2008-11-04  8:00   ` Kovacs Balazs
2008-11-04  9:08     ` oleg roitburd
2008-11-04  9:31       ` Alex Betis
2008-11-04 12:45         ` Kovacs Balazs
     [not found]       ` <4a5931310811040335i7722125fwc0efefbf01cac93d@mail.gmail.com>
2008-11-04 12:42         ` [linux-dvb] Fwd: " Kovacs Balazs
2008-11-04  9:18     ` [linux-dvb] " Ales Jurik
2008-11-06  8:01       ` Kovacs Balazs
2008-11-06  9:11         ` Ales Jurik
  -- strict thread matches above, loose matches on Subject: below --
2008-11-10 14:47 lucian orasanu
2008-11-11  9:33 Newsy Paper
2008-11-11  9:41 ` Kovacs Balazs
2008-11-11 11:40 Newsy Paper

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=167586304.20081103115116@bitklub.hu \
    --to=basq@bitklub.hu \
    --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 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.