From: Georg Acher <acher@in.tum.de>
To: Linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] [RFC] SNR units in tuners
Date: Sun, 19 Oct 2008 23:52:26 +0200 [thread overview]
Message-ID: <20081019215225.GA11678@braindead1.acher> (raw)
In-Reply-To: <19262.1224449033@kewl.org>
On Sun, Oct 19, 2008 at 09:43:53PM +0100, Darron Broad wrote:
> >The docs for the 24116 say that the snr is measured in 0.1dB steps. The
> >absolute range of registers a3:d5 is 0 to 300, so full scale is 30dB. I
> >doubt we will see the 30dB in a real-world setup...
>
> Okay, so we know the step size of 0.1 per bit and that's measured
> within a range of 0 to 300 but that doesn't actually say what it's
> value is? Ie, is 50=5dB or something else?
I guess so.
> All the graphs I see for QPSK and 8PSK in use in the real-world
> suggest the theoretical limit of esn0 is a lot less than that available
> range. I don't know what is the accepted error rate to set this limit.
> Perhaps someone who has authority on this subject can chime in?
>
> On the cx24116 testing observed that a register max of 160 from QPSK
> gave good approximation to that given by regular sat-kit sitting
> around 100%. If that really means 16dB then it doesn't look right
> compared to the graphs I see, what's wrong here?
I've looked at the IF output of the frontend (it should be always a CX24118)
with spectrum analyzer. The input was from Astra 19.2 with a 80cm dish. The
slope top above the noise floor indicates also a SNR of 16, maybe 18dB, but
not more. It's really that low...
--
Georg Acher, acher@in.tum.de
http://www.lrr.in.tum.de/~acher
"Oh no, not again !" The bowl of petunias
_______________________________________________
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-10-19 21:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 18:04 [linux-dvb] [RFC] SNR units in tuners Devin Heitmueller
2008-10-17 18:13 ` Steven Toth
2008-10-17 19:55 ` Darron Broad
2008-10-17 20:06 ` Devin Heitmueller
2008-10-18 5:42 ` Darron Broad
2008-10-19 19:54 ` Georg Acher
2008-10-19 20:43 ` Darron Broad
2008-10-19 21:52 ` Georg Acher [this message]
2008-10-19 23:40 ` Darron Broad
2008-10-20 0:01 ` Darron Broad
2008-10-18 18:56 ` Richard Scobie
2008-10-17 22:01 ` Patrick Boettcher
2008-10-18 18:36 ` Trent Piepho
2008-10-18 19:38 ` Matthias Schwarzott
2008-10-19 11:46 ` Andreas Oberritter
2008-10-25 14:59 ` wk
2008-10-27 10:37 ` Morgan Tørvolt
2008-10-27 14:03 ` Georg Acher
2008-10-27 15:54 ` Andy Walls
2008-10-27 16:16 ` Morgan Tørvolt
2008-10-27 16:25 ` Georg Acher
2008-10-27 16:40 ` Manu Abraham
2009-08-07 7:04 ` VDR User
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=20081019215225.GA11678@braindead1.acher \
--to=acher@in.tum.de \
--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