From: Rogan Dawes <lists@dawes.za.net>
To: Patrick Boettcher <patrick.boettcher@desy.de>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] DVB-T South Africa
Date: Mon, 12 May 2008 16:53:16 +0200 [thread overview]
Message-ID: <482859DC.6060800@dawes.za.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0805121604170.11078@pub3.ifh.de>
Patrick Boettcher wrote:
> Hi again,
> On Mon, 12 May 2008, Rogan Dawes wrote:
>> I guess this is related to a weak/corrupted signal, although the ber
>> showing up while running tzap seemed reasonable:
>
> A reasonable BER is 0 and (if the demod-driver is supporting) UNC should
> be 0 as well.
>
> BER is the bit-error-rate, not the bitrate.
>
>> I guess I'll need to get a better DVB antenna.
>
> Try to open the window or to put the antenna outside, rotate the
> antenna, check the cables and connector, while having femon running and
> check which position is the best.
>
> Sometimes it helps,
> Patrick.
>
Ok, so I tried unplugging and replugging the antenna, just to make sure
that femon would pick up the crudest of changes, before I tried more
refined ones.
I got the following, but it also crashed my machine :-(
rogan@athena:~$ tzap "eTV(ETV)" > /dev/null &
[1] 5339
rogan@athena:~$ femon
using '/dev/dvb/adapter0/frontend0'
FE: Philips TDA10046H DVB-T (TERRESTRIAL)
status 00 | signal 8b8b | snr 3030 | ber 0001fffe | unc ffffffff |
status 1f | signal 8989 | snr f6f6 | ber 0001a268 | unc ffffffff |
FE_HAS_LOCK
status 1f | signal 8989 | snr 6565 | ber 0001fffe | unc ffffffff |
FE_HAS_LOCK
status 1f | signal 8989 | snr f6f6 | ber 0001b110 | unc ffffffff |
FE_HAS_LOCK
status 1f | signal 8989 | snr ecec | ber 0001ac00 | unc ffffffff |
FE_HAS_LOCK
status 1f | signal 8888 | snr f4f4 | ber 0001a84c | unc ffffffff |
FE_HAS_LOCK
status 01 | signal 8989 | snr 6161 | ber 0001fffe | unc ffffffff |
status 1f | signal 8888 | snr f2f2 | ber 0001b28c | unc ffffffff |
FE_HAS_LOCK
status 00 | signal 8989 | snr 2c2c | ber 0001fffe | unc ffffffff |
status 1f | signal 8989 | snr f3f3 | ber 0001a590 | unc ffffffff |
FE_HAS_LOCK
status 00 | signal 8787 | snr 6d6d | ber 0001fffe | unc ffffffff |
status 1f | signal 8888 | snr f4f4 | ber 0001aeae | unc ffffffff |
FE_HAS_LOCK
status 01 | signal 8989 | snr 8f8f | ber 0001fffe | unc ffffffff |
status 1f | signal 8787 | snr f3f3 | ber 0001e982 | unc ffffffff |
FE_HAS_LOCK
status 00 | signal 8d8d | snr 7171 | ber 0001fffe | unc 00000001 |
status 1f | signal 8c8c | snr f5f5 | ber 00014628 | unc ffffffff |
FE_HAS_LOCK
status 1f | signal 8c8c | snr f8f8 | ber 00016fb0 | unc ffffffff |
FE_HAS_LOCK
status 1f | signal 8b8b | snr f7f7 | ber 00013b8c | unc ffffffff |
FE_HAS_LOCK
status 1f | signal 8b8b | snr f7f7 | ber 000129d4 | unc 0000001e |
FE_HAS_LOCK
status 1f | signal 8888 | snr f6f6 | ber 00017330 | unc ffffffff |
FE_HAS_LOCK
status 00 | signal 0000 | snr e0e0 | ber 0001fffe | unc 00000000 |
status 00 | signal 0000 | snr 3535 | ber 0001fffe | unc 00000000 |
status 00 | signal 0000 | snr 2c2c | ber 0001fffe | unc 00000000 |
status 00 | signal 0000 | snr 3030 | ber 0001fffe | unc 00000000 |
status 00 | signal 0000 | snr e1e1 | ber 0001fffe | unc 00000000 |
status 00 | signal 0000 | snr ffff | ber 0001fffe | unc 00000000 |
status 00 | signal 0000 | snr 3737 | ber 0001fffe | unc 00000000 |
status 00 | signal 0000 | snr 7d7d | ber 0001fffe | unc 00000000 |
status 00 | signal 0000 | snr a9a9 | ber 0001fffe | unc 00000000 |
This would seem to support the notion that I am not getting a good
enough signal, right?
Rogan
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
prev parent reply other threads:[~2008-05-12 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 10:39 [linux-dvb] DVB-T South Africa Rogan Dawes
2008-05-12 10:59 ` Patrick Boettcher
2008-05-12 11:21 ` Rogan Dawes
2008-05-12 12:22 ` Patrick Boettcher
2008-05-12 12:50 ` Rogan Dawes
2008-05-12 14:00 ` Rogan Dawes
2008-05-12 14:08 ` Patrick Boettcher
2008-05-12 14:53 ` Rogan Dawes [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=482859DC.6060800@dawes.za.net \
--to=lists@dawes.za.net \
--cc=linux-dvb@linuxtv.org \
--cc=patrick.boettcher@desy.de \
/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