public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Will <nico@youplala.net>
To: linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] script to automatically get signal strength and BER
Date: Mon, 04 Feb 2008 16:11:57 +0000	[thread overview]
Message-ID: <1202141517.6826.47.camel@acropora> (raw)
In-Reply-To: <47A735A0.2040801@rogers.com>


On Mon, 2008-02-04 at 10:56 -0500, CityK wrote:
> Nicolas Will wrote:
> > On Fri, 2008-02-01 at 14:43 +0000, Nicolas Will wrote:
> >   
> >> Hi all,
> >>
> >> Before I try to make one, did anyone write a script that goes
> through
> >> a
> >> channels.conf file and outputs human readable signal strength, BER
> and
> >> such for all channels?
> >>     
> >
> > I received 2 scripts by pers. email.
> >
> > Thanks guys !
> >
> > I have created a wiki page containing the scripts"
> >
> > http://linuxtv.org/wiki/index.php/Testing_reception_quality
> >
> > Hope this helps.
> >
> > Nico
> Also see femon (part of the dvb-apps)
> "femon -h" for help
> "femon -H" for what you want

Ah.

My femon (dvb-utils on my Gutsy Mythbuntu) does not have the -H option.
It's probably too old.

I shall look at the hg sources.

The first script created a nice baseline and comparaison tool for the
before and after masthead amp installation.

A 26-dB masthead amp + associated in-line power supply gave me 20-25%
better signal strength, and most importantly brough all the BER to zero.

http://www.youplala.net/~will/htpc/signaltest/

I'm happy :o)

Nico


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

      reply	other threads:[~2008-02-04 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1201877013.6796.5.camel@acropora>
     [not found] ` <1201955576.935.23.camel@youkaida>
2008-02-04 15:56   ` [linux-dvb] script to automatically get signal strength and BER CityK
2008-02-04 16:11     ` Nicolas Will [this message]

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=1202141517.6826.47.camel@acropora \
    --to=nico@youplala.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