From: e9hack <e9hack@googlemail.com>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH] Fix the unc for the frontends tda10021 and stv0297
Date: Mon, 12 May 2008 08:47:54 +0200 [thread overview]
Message-ID: <4827E81A.1080807@gmail.com> (raw)
In-Reply-To: <4827851D.2000104@gmx.net>
P. van Gaans schrieb:
> Not necessarily. Here some femon output from my Technotrend T-1500:
>
> status SCVYL | signal 54% | snr 99% | ber 188 | unc 0 | FE_HAS_LOCK
> status SCVYL | signal 54% | snr 99% | ber 230 | unc 0 | FE_HAS_LOCK
> status SCVYL | signal 54% | snr 99% | ber 240 | unc 0 | FE_HAS_LOCK
> status SCVYL | signal 54% | snr 99% | ber 234 | unc 0 | FE_HAS_LOCK
> status SCVYL | signal 54% | snr 99% | ber 228 | unc 21 | FE_HAS_LOCK
> status SCVYL | signal 54% | snr 99% | ber 248 | unc 0 | FE_HAS_LOCK
> status SCVYL | signal 54% | snr 99% | ber 280 | unc 0 | FE_HAS_LOCK
> status SCVYL | signal 54% | snr 99% | ber 234 | unc 0 | FE_HAS_LOCK
...
> I see the standalones hickup as well. So a very short
> error will cause unc, but no higher BER.
You may not see a higher BER, because the corrupted signal doesn't hit the BER measuring
period. Femon asks every 1 second for new values. The UNC counting interval is this 1
second, but the BER measuring interval is shorter (50..200ms). For a stv0297, it is 150ms
for QAM256 modulation and 200ms for QAM64. The real measuring interval for the BER is a
fixed number of bits.
-Hartmut
_______________________________________________
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-05-12 6:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-10 8:46 [linux-dvb] [PATCH] Fix the unc for the frontends tda10021 and stv0297 e9hack
2008-05-10 15:17 ` Oliver Endriss
2008-05-10 15:27 ` Oliver Endriss
2008-05-10 15:48 ` Michael Krufky
2008-05-12 13:29 ` Oliver Endriss
2008-05-10 16:02 ` e9hack
2008-05-10 16:39 ` Oliver Endriss
2008-05-10 21:53 ` Andy Walls
2008-05-10 22:16 ` Manu Abraham
2008-05-10 23:44 ` Andy Walls
2008-05-11 6:14 ` Manu Abraham
2008-05-11 18:35 ` Andy Walls
2008-05-11 19:33 ` Manu Abraham
2008-05-11 21:32 ` Andy Walls
2008-05-12 13:16 ` Oliver Endriss
2008-05-12 13:47 ` P. van Gaans
2008-05-12 16:02 ` Oliver Endriss
2008-05-12 17:03 ` P. van Gaans
2008-05-12 22:42 ` Andy Walls
2008-05-11 23:45 ` P. van Gaans
2008-05-12 6:47 ` e9hack [this message]
2008-05-12 14:26 ` Luca Olivetti
2008-05-10 16:12 ` e9hack
2008-05-30 23:46 ` Oliver Endriss
2008-05-31 0:01 ` Manu Abraham
2008-05-31 7:19 ` e9hack
2008-05-31 12:45 ` Oliver Endriss
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=4827E81A.1080807@gmail.com \
--to=e9hack@googlemail.com \
--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