public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "P. van Gaans" <w3ird_n3rd@gmx.net>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [PATCH] Fix the unc for the frontends tda10021	and stv0297
Date: Mon, 12 May 2008 01:45:33 +0200	[thread overview]
Message-ID: <4827851D.2000104@gmx.net> (raw)
In-Reply-To: <48268EB9.6060000@gmail.com>

On 05/11/2008 08:14 AM, Manu Abraham wrote:
>>> Absolute errors are used very scantily, but have been used to see how
>>> good/bad the whole system is.
>> Except for in safety critical systems (fire suppression system,
>> automobile brakes, etc.), how can a "good/bad" determination based on an
>> error count be separated from a time interval over which that error
>> count occurred?
> 
> 
> It defines whether the FEC engine worked as expected. eg: Just looking
> at a UNC counter counting up with a high BER shows a bad channel.
> looking at a UNC counter going up with a low BER shows a bad error
> correction scheme. looking at a very low BER and a high number of
> uncorrectables imply a bad FEC engine/scheme.

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

Nothing special for the BER levels, just a fairly good signal (need to 
get into tens of thousands before it drops). But there, all of a sudden, 
unc 21 (meaning the picture gets garbled for a moment). I still don't 
know who or what is bullying me with those, but it seems to be caused by 
sparks. I sometimes get it when I flick a light on or off. At night I 
usually don't get these much (or not at all!), in the weekends usually 
have less as well. At day, and especially in the evening though, 
disaster (several each hour or even minute). It's no fault in the shemes 
or FEC engine, I see the standalones hickup as well. So a very short 
error will cause unc, but no higher BER.

P.

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

  parent reply	other threads:[~2008-05-11 23:46 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 [this message]
2008-05-12  6:47               ` e9hack
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=4827851D.2000104@gmx.net \
    --to=w3ird_n3rd@gmx.net \
    --cc=abraham.manu@gmail.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