Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-ma01.r1000.mx.aol.com (Internet Inbound) with ESMTP id F0EE538000083; Sat, 2 Feb 2013 11:06:56 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1U1fSY-0005Uk-IS for rs_out_1@blacksheep.org; Sat, 02 Feb 2013 15:56:54 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1U1fSX-0005Ub-Sn for rsgb_lf_group@blacksheep.org; Sat, 02 Feb 2013 15:56:53 +0000 Received: from out1.ip03ir2.opaltelecom.net ([62.24.128.239]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1U1fSV-0004k1-Hs for rsgb_lf_group@blacksheep.org; Sat, 02 Feb 2013 15:56:52 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlMJAEAeDVFOk8KP/2dsb2JhbABFvjAEgQMXc4IaBQEBBQgBAQNJAiwBAQMFAgEDEQQBAQolFAEEGgYWCAYTCgECAgEBiATCO40rFAwbg2wDiDCFV5hpgnw X-IronPort-AV: E=Sophos;i="4.84,591,1355097600"; d="scan'208,217";a="413095330" Received: from host-78-147-194-143.as13285.net (HELO xphd97xgq27nyf) ([78.147.194.143]) by out1.ip03ir2.opaltelecom.net with SMTP; 02 Feb 2013 15:56:29 +0000 Message-ID: <00ed01ce015d$dc7192a0$0401a8c0@xphd97xgq27nyf> From: "mal hamilton" To: References: <005001ce0131$ba6ddaf0$0401a8c0@xphd97xgq27nyf> <510CF0B7.7060103@psk31.plus.com> <007001ce0139$042377c0$0401a8c0@xphd97xgq27nyf> <510CFB8E.9040706@psk31.plus.com> <008201ce0149$b5f58550$0401a8c0@xphd97xgq27nyf> <009001ce014c$1cfedc90$0401a8c0@xphd97xgq27nyf> <510D1F1B.2050708@psk31.plus.com> <00a401ce0151$70da3350$0401a8c0@xphd97xgq27nyf> <510D27D3.4080608@psk31.plus.com> <00df01ce015d$03c324f0$0401a8c0@xphd97xgq27nyf> Date: Sat, 2 Feb 2013 15:56:27 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Score: 2.3 (++) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Eddie es Co Not doing badly here copy LA6TPA at 1312 Km best distance on the current list of intercepts g3kev ----- Original Message ----- From: mal hamilton To: rsgb_lf_group@blacksheep.org Sent: Saturday, February 02, 2013 3:50 PM Subject: Re: LF: wspr decode [...] Content analysis details: (2.3 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message 2.3 AXB_XMAILER_MIMEOLE_OL_024C2 AXB_XMAILER_MIMEOLE_OL_024C2 X-Scan-Signature: 4999602ae0d888991d6ab5146b3aa278 Subject: Re: LF: wspr decode Content-Type: multipart/alternative; boundary="----=_NextPart_000_00EA_01CE015D.DC0FC390" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.8 required=5.0 tests=HTML_30_40,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-global-disposition: G x-aol-sid: 3039ac1d6009510d39a000fe X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. ------=_NextPart_000_00EA_01CE015D.DC0FC390 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Eddie es Co Not doing badly here copy LA6TPA at 1312 Km best distance on the current = list of intercepts g3kev ----- Original Message -----=20 From: mal hamilton=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Saturday, February 02, 2013 3:50 PM Subject: Re: LF: wspr decode Eddie Now seeing 10 different stns active but not getting that many decodes, = so I am seeing everyone strong es weak but decoding is a different story = that is where QRSS has the advantage because by now I would have full ID = on all 10. A good test would be to follow each WSPR transmission with a QRSS one = for comparison and then we could see who was there but not making a = decode Even the weak ones are good visibility with me and a lot of them are = audible de g3kev ----- Original Message -----=20 From: g3zjo=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Saturday, February 02, 2013 2:50 PM Subject: Re: LF: wspr decode On 02/02/2013 14:27, mal hamilton wrote:=20 Eddie One problem that effects you and your QRP I am beaming E/W and you are to my south in the 40m loop null. I = will switch to the inv L later and maybe see u then. One other thing Yes you did slew your lobes some time ago and saw me. I do not see my callsign on the reports although I have ticked the = Upload box. No you have never uploaded a spot according to the DB. Have you = filled in you details in the Settings box. I depend on time sync via internet. Via a separate time server or Muckysoft? Muckysoft can default to re = setting every month or more which is not enough. Eddie=20 mal/g3kev ----- Original Message -----=20 From: g3zjo=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Saturday, February 02, 2013 2:13 PM Subject: Re: LF: wspr decode Mal I have increased my power by 10dB so you never know. However the = the other morning running this power on QRSS3 I called and called you = precisely on your frequency.. After one call the timing was so right = that I sent you a report over and over but no, you couldn't see me. Temperamental? In no way, it is solid and reliable believe me. = At first I use to measure accurately the 1.6Hz data steps when setting = up a PIC system, now I set it by eye and just look to make sure I get = decoded to -31dB from distant stations, tolerant or what. WSPR copes with frequency drifting TX's some drifting 3 times = the width of the signal, and get decoded. Eddie On 02/02/2013 13:49, mal hamilton wrote:=20 Ps things are improving now decoding DK7FC and M1GEO watch out = you could be next. Seems a temperamental mode g3kev ----- Original Message -----=20 From: mal hamilton=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Saturday, February 02, 2013 1:32 PM Subject: Re: LF: wspr decode Eddie My Logic---If I can decode one then that should apply to all = the others ----- Original Message -----=20 From: g3zjo=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Saturday, February 02, 2013 11:42 AM Subject: Re: LF: wspr decode Simple one, but timing, is your timing OK? Eddie On 02/02/2013 11:32, mal hamilton wrote:=20 I am seeing quite a lot of acty on the waterfall and you = are probably there, 8 visible at present but Decode is a different = story. Like I said if these same stns were on QRSS I would get = an ID and you would probably be there also Most are audible with me and strong enough for a CW qso de g3kev ----- Original Message -----=20 From: g3zjo=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Saturday, February 02, 2013 10:55 AM Subject: Re: LF: wspr decode On 02/02/2013 10:40, mal hamilton wrote:=20 Strangely enough I can only decode GW8MLA and there = are another several stns active at present on WSPR-2. Most are strong = and audible de g3kev Well that will give you a rather distorted view of the = usefulness of the mode then. And you don't see me,=20 Beatles You think you've got everything you want And your bird can sing But you don't see me Do I remember the lyrics right? Eddie ------=_NextPart_000_00EA_01CE015D.DC0FC390 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Eddie es Co
Not doing badly here copy LA6TPA at 1312 Km best = distance=20 on the current list of intercepts
g3kev
 
----- Original Message -----
From:=20 mal=20 hamilton
Sent: Saturday, February 02, = 2013 3:50=20 PM
Subject: Re: LF: wspr = decode

Eddie
Now seeing 10 different stns active but not = getting that=20 many decodes, so I am seeing everyone strong es weak but decoding is a = different story that is where QRSS has the advantage because by now I = would=20 have full ID on all 10.
A good test would be to follow each WSPR = transmission=20 with a QRSS one for comparison and then we could see who was there but = not=20 making a decode
Even the weak ones are good visibility with me = and a lot=20 of them are audible
 
de g3kev
 
----- Original Message -----
From:=20 g3zjo=20
To: rsgb_lf_group@blacksheep.org= =20
Sent: Saturday, February 02, = 2013 2:50=20 PM
Subject: Re: LF: wspr = decode

On 02/02/2013 14:27, mal hamilton wrote:=20
Eddie
One problem that effects you and your=20 QRP
I am beaming E/W and you are to my south = in the 40m=20 loop null. I will switch to the inv L later and maybe see u then. = One=20 other thing
Yes you did slew your lobes = some time=20 ago and saw me.
I do not see my callsign on the reports = although I=20 have ticked the Upload box.
No you have = never=20 uploaded a spot according to the DB. Have you filled in you details = in the=20 Settings box.
I depend on time sync via=20 internet.
Via a separate time server or = Muckysoft?=20 Muckysoft can default to re setting every month or more which is not = enough.

Eddie
mal/g3kev
 
----- Original Message ----- =
From:=20 g3zjo
To: rsgb_lf_group@blacksheep.org
Sent: Saturday, February = 02, 2013=20 2:13 PM
Subject: Re: LF: wspr = decode

Mal

I have increased my power by 10dB so = you never=20 know. However the the other morning running this power on = QRSS3  I=20 called and called you precisely on your frequency.. After one = call the=20 timing was so right that I sent you a report over and over but = no, you=20 couldn't see me.
Temperamental? In no way, it is solid and = reliable=20 believe me. At first I use to measure accurately the 1.6Hz data = steps=20 when setting up a PIC system, now I set it by eye and just look = to make=20 sure I get decoded to -31dB from distant stations, tolerant or=20 what.
WSPR copes with frequency drifting TX's some drifting 3 = times=20 the width of the signal, and get decoded.

Eddie

On = 02/02/2013 13:49, mal hamilton wrote:=20
Ps
things are improving now decoding = DK7FC and=20 M1GEO watch out you could be next. Seems a temperamental=20 mode
g3kev
 
----- Original Message ----- =
From:=20 mal hamilton
To: rsgb_lf_group@blacksheep.org =
Sent: Saturday, = February 02,=20 2013 1:32 PM
Subject: Re: LF: wspr = decode

Eddie
My Logic---If I can decode one then = that=20 should apply to all the others
 
----- Original Message = -----
From:=20 g3zjo
To: rsgb_lf_group@blacksheep.org =
Sent: Saturday, = February 02,=20 2013 11:42 AM
Subject: Re: LF: = wspr=20 decode

Simple one, but timing, is your timing=20 OK?

Eddie

On 02/02/2013 11:32, mal hamilton = wrote:=20
I am seeing quite a lot of acty = on the=20 waterfall and you are probably there, 8 visible at = present but=20 Decode is a different story.
Like I said if these same stns = were on=20 QRSS I would get an ID and you would probably be there=20 also
Most are audible with me and = strong enough=20 for a CW qso
de g3kev
 
----- Original Message = -----=20
From:=20 g3zjo
To: rsgb_lf_group@blacksheep.org
Sent: Saturday, = February=20 02, 2013 10:55 AM
Subject: Re: = LF: wspr=20 decode

On 02/02/2013 10:40, mal hamilton = wrote:=20
Strangely enough I can only = decode=20 GW8MLA and there are another several stns active at = present=20 on WSPR-2. Most are strong and audible
de g3kev
 
Well that will give = you a rather=20 distorted view of the usefulness of the mode = then.

And=20 you don't see me,

Beatles

You think = you've got=20 everything you want
And your bird can sing
But = you don't=20 see me

Do I remember the lyrics=20 = right?

Eddie



------=_NextPart_000_00EA_01CE015D.DC0FC390--