Return-Path: Received: from rly-mh02.mx.aol.com (rly-mh02.mail.aol.com [172.21.166.138]) by air-mh06.mail.aol.com (v121_r5.5) with ESMTP id MAILINMH064-bbb497eff3af2; Tue, 27 Jan 2009 07:34:21 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-mh02.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINMH023-bbb497eff3af2; Tue, 27 Jan 2009 07:34:04 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LRn8X-0001bO-8H for rs_out_1@blacksheep.org; Tue, 27 Jan 2009 12:33:49 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LRn8W-0001bF-ER for rsgb_lf_group@blacksheep.org; Tue, 27 Jan 2009 12:33:48 +0000 Received: from n24.bullet.mail.ukl.yahoo.com ([87.248.110.141]) by relay3.thorcom.net with smtp (Exim 4.63) (envelope-from ) id 1LRn8W-0005iP-Aj for rsgb_lf_group@blacksheep.org; Tue, 27 Jan 2009 12:33:48 +0000 Received: from [217.146.182.179] by n24.bullet.mail.ukl.yahoo.com with NNFMP; 27 Jan 2009 12:33:47 -0000 Received: from [87.248.110.117] by t5.bullet.ukl.yahoo.com with NNFMP; 27 Jan 2009 12:33:41 -0000 Received: from [127.0.0.1] by omp222.mail.ukl.yahoo.com with NNFMP; 27 Jan 2009 12:33:39 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 594085.12244.bm@omp222.mail.ukl.yahoo.com Received: (qmail 58213 invoked by uid 60001); 27 Jan 2009 12:33:41 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=cXS+7AhX0MnikpkzCI5zzv0FOZB2nNdI9nvj6lmtUnu8mu0yxIneW/QxNbgAeGOglbnyAlFhBLL7VcnK/R7WFf+aL9TMbTdmHblwWbrO02dSnuXue6eUtjgkYnt9Ombv6942AbdeCUGp2QAXnPXje0wNPqFzHUfeuL1QDBbWGPY=; X-YMail-OSG: uoqUF_wVM1k2Tg678sK0VYgZahZn9CdfMCu05x9gbIPBk0PTSQnBMAsPwbVOyrdY77bm1dvLgKxA83pdfeHGKSMH0LpM1md65dHuJLSDyDy7X.6f2xNUuudN11gIJGD_pcUlRMjNSyV4YM47cuVUjehIYyNRwutC5.qceOBEX2Ockt0613E.SYrE.GSiAViyu4knQBte1597Fx5Kva0QtYjX4ksRgNv7 Received: from [213.78.182.231] by web24707.mail.ird.yahoo.com via HTTP; Tue, 27 Jan 2009 04:33:40 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Tue, 27 Jan 2009 04:33:40 -0800 (PST) From: brian hodgson To: rsgb_lf_group@blacksheep.org In-Reply-To: <497EE52C.4050808@sighthound.demon.co.uk> MIME-Version: 1.0 Message-ID: <50229.58162.qm@web24707.mail.ird.yahoo.com> DomainKey-Status: good (testing) Subject: Re: LF: G0NBD difficult to decode Content-Type: multipart/alternative; boundary="0-705120698-1233059620=:58162" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=HTML_MESSAGE autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-AOL-IP: 193.82.116.20 --0-705120698-1233059620=:58162 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable For what its worth, I was decoding both M0BMU and G0NBD on alternate lines l= ast night. I'm in Watford (only 17 km from Jim so a VERY big signal !) - G0NBD was inau= dible. Brian (G3YKB) --- On Tue, 27/1/09, John P-G wrote: From: John P-G Subject: Re: LF: G0NBD difficult to decode To: rsgb_lf_group@blacksheep.org Date: Tuesday, 27 January, 2009, 10:42 AM mal hamilton wrote: > Johan > I have mentioned this several times before but noone seems to know why=20 > strong signals or any visible signals do not DECODE. I get some decodes=20 > therefore I know my system is working but not sure whether the problem is at=20 > the TX or RX end. To me wspr seems unreliable given the strength of signals=20 > but producing only marginal decoded output. > 73 de mal/gkev >=20 Mal, LF, In general WSPR is very good at decoding weak signals - that's what it's all about after all - and can give reliable decodes on signals that are inaudible and only faintly visible on the waterfall. Occasionally there seem to be certain strong signals that won't decode, when weaker signals from the same stations are fine. Some discussion has taken place on the WSPR forum over incompatible soundcard sampling rates, others on HF have seem the same "won't decode strong signals" problems too. In the current case, with G0NBD, I guess the problem, whatever it is, is at the sending end, as similarly strong signals from others (M0BMU and G4JNT) decoded fine here, and elsewhere, yet many people had trouble with G0NBD's signal. I see that Chris G3XVL often reports a +13dB s/n ratio for Jim's signal, which shows that strong signals can decode correctly. The question of brevity in passing information (ie "having a QSO") is moot - it's not really intended for that purpose. It's point is to allow monitoring of the path conditions, using low power "weak signals" - WSPR stands for "Weaks Signal Propagation Reporting". If you want a mode for conveying information and exchanging reports then there's a whole gamut - not least among them good old CW. WPSR allows the collection, automatically, of data showing the changes in path conditions over time, with a centralised online database of the results, allowing others to do whatever number crunching they care to on the data. For this the mode is perfectly valid, and given low enough transmit power from the stations involved it shouldn't cause too many problems for other band users. Last night's results showed that, for inter-G (even up to Shetland) the ERPs involved were too high. Gary, with his 5W TX and 2mW ERP is showing the way it should be done - and that wouldn't cause too much QRM for those seeking CW QSOs elsewhere on the band. Using WSPR on 160m recently I discovered that I have a regular opening to N6TTO on the west coast of USA, and I'm often the only Eu station to receive him. Relying on more traditional modes I'd probably never have discovered this. It means that perhaps my location is suitable for 160m, and might be worth some investment in time/effort to get on the band. Without the research using WSPR I'd have not realised that my location was special - although my low noise floor has already proved its worth on 500kHz. Just a few thoughts from here. Cheers, John GM4SLV =20 --0-705120698-1233059620=:58162 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
For what its worth, I was decoding both M0BMU a= nd G0NBD on alternate lines last night.
I'm in Watford (only 17 km from J= im so a VERY big signal !) - G0NBD was inaudible.

Brian (G3YKB)
--- On Tue, 27/1/09, John P-G <gm4slv@sighthound.demon.co.uk><= /i> wrote:
From: John P-G <gm4slv@sighthou= nd.demon.co.uk>
Subject: Re: LF: G0NBD difficult to decode
To: rsgb= _lf_group@blacksheep.org
Date: Tuesday, 27 January, 2009, 10:42 AM
mal hamilton wrote:
> Johan
> I have mentioned this severa= l times before but noone seems to know why
> strong signals or any vi= sible signals do not DECODE. I get some decodes
> therefore I know my= system is working but not sure whether the problem is
at
> the TX or RX end. To me wspr seems unreliable given the strength o= f
signals
> but producing only marginal decoded output.
> 73= de mal/gkev
>


Mal, LF,

In general WSPR is very goo= d at decoding weak signals - that's what
it's
all about after all - an= d can give reliable decodes on signals that are
inaudible and only faintl= y visible on the waterfall. Occasionally there
seem to be certain strong=20= signals that won't decode, when weaker signals
from the same stations are= fine.

Some discussion has taken place on the WSPR forum over incompa= tible
soundcard sampling rates, others on HF have seem the same "won'tdecode
strong signals" problems too.

In the current case, with G0= NBD, I guess the problem, whatever it is, is
at the sending end, as sim= ilarly strong signals from others (M0BMU and
G4JNT) decoded fine here, an= d elsewhere, yet many people had trouble
with G0NBD's signal.

I see that Chris G3XVL often reports a +13dB s/n ratio for J= im's signal,
which shows that strong signals can decode correctly.

The question of brevity in passing information (ie "having a QSO") ismoot - it's not really intended for that purpose. It's point is to
allo= w
monitoring of the path conditions, using low power "weak signals" -
= WSPR
stands for "Weaks Signal Propagation Reporting". If you want a mode<= br>for
conveying information and exchanging reports then there's a whole=20= gamut
- not least among them good old CW.

WPSR allows the collecti= on, automatically, of data showing the changes
in path conditions over ti= me, with a centralised online database of the
results, allowing others to= do whatever number crunching they care to on
the data. For this the mode= is perfectly valid, and given low enough
transmit power from the station= s involved it shouldn't cause too many
problems for other band users. Last night's results showed that, for
inter-G (even up= to Shetland) the ERPs involved were too high. Gary,
with his 5W TX and 2= mW ERP is showing the way it should be done - and
that wouldn't cause too= much QRM for those seeking CW QSOs elsewhere on
the band.

Using W= SPR on 160m recently I discovered that I have a regular opening
to N6TTO=20= on the west coast of USA, and I'm often the only Eu station to
receive hi= m. Relying on more traditional modes I'd probably never have
discovered t= his. It means that perhaps my location is suitable for 160m,
and might be= worth some investment in time/effort to get on the band.
Without the res= earch using WSPR I'd have not realised that my location
was special - alt= hough my low noise floor has already proved its worth
on 500kHz.

J= ust a few thoughts from here.

Cheers,

John
GM4SLV


=20 --0-705120698-1233059620=:58162--