Return-Path: Received: from rly-me10.mx.aol.com (rly-me10.mail.aol.com [172.20.83.44]) by air-me06.mail.aol.com (v121_r4.4) with ESMTP id MAILINME063-9e04953958dd2; Thu, 25 Dec 2008 09:15:53 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-me10.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINME104-9e04953958dd2; Thu, 25 Dec 2008 09:15:43 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LFqzQ-0003QR-T8 for rs_out_1@blacksheep.org; Thu, 25 Dec 2008 14:15:04 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LFqzP-0003QI-Ob for rsgb_lf_group@blacksheep.org; Thu, 25 Dec 2008 14:15:03 +0000 Received: from qmta09.westchester.pa.mail.comcast.net ([76.96.62.96]) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1LFqzN-0007kv-Mi for rsgb_lf_group@blacksheep.org; Thu, 25 Dec 2008 14:15:03 +0000 Received: from OMTA02.westchester.pa.mail.comcast.net ([76.96.62.19]) by QMTA09.westchester.pa.mail.comcast.net with comcast id vRTD1a0090QuhwU59SEulu; Thu, 25 Dec 2008 14:14:54 +0000 Received: from JAYDELL ([65.96.107.144]) by OMTA02.westchester.pa.mail.comcast.net with comcast id vSEu1a00536xPMd3NSEuY4; Thu, 25 Dec 2008 14:14:54 +0000 Message-ID: <000e01c9669b$28a2ed20$8d01a8c0@JAYDELL> From: To: References: <00ae01c965e5$9a2a4f30$0301a8c0@mal769a60aa920> <000a01c965ee$da266160$6c01a8c0@DELL4> <006301c96681$a8d49c10$0301a8c0@mal769a60aa920> <003601c9668e$fbf22770$8d01a8c0@JAYDELL> <007f01c96692$de3ce180$0301a8c0@mal769a60aa920> Date: Thu, 25 Dec 2008 09:14:54 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.6 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001,NO_REAL_NAME=0.55 Subject: LF: Friday night Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C96671.3F988EB0" 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_40_50,HTML_MESSAGE, NO_REAL_NAME 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 ------=_NextPart_000_000B_01C96671.3F988EB0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Mal Roger the ERP situation.=20 I'll use 508.510 kHz instead of 505.24 kHz since apparently that freq. was c= lear on your end. Jay ----- Original Message -----=20 From: mal hamilton=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Thursday, December 25, 2008 8:15 AM Subject: LF: Re: Re: Re: Re: wspr Jay unfortunately I only have a max of 1w erp this year but hopefully next= year 10w erp then we might do better, your end is not a problem. Will ck you qrg 505.24 although you would be better up the band a bit cos=20= of the EU beacon qrm around 505 khz. 73 de mal/g3kev ----- Original Message -----=20 From: jrusgrove@comcast.net=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Thursday, December 25, 2008 12:47 PM Subject: LF: Re: Re: Re: wspr Merry Christmas to all! Mal Will start looking for your signal at 2200Z Friday night. WE2XGR/2 will=20= be on 505.240 - if that frequency is clear on your end - please advise. I'll= check your frequency but believe it to be clear from previous listening ses= sions.=20 Setup here - WSPR the other night 400 W transmitter power to a 90' top l= oaded vertical. Friday night's transmissions will be at 1 kW. What transmitt= er power will you be using on your end?=20 Jay ----- Original Message -----=20 From: mal hamilton=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Thursday, December 25, 2008 6:12 AM Subject: LF: Re: Re: wspr Tnx Jay I will TX on 502.57 khz starting at 2200 utc Friday night. If any chan= ges let me know. I will be in QSO MODE ie CQ G3KEV QSK. If u hear me send my call to st= art a QSO. I will listen on ur QRG all the time. Pse let me know ur QRG. QRS3 should be ok and if condx good will speed up.=20 73 and Merry Xmas Mal/G3KEV ----- Original Message -----=20 From: jrusgrove@comcast.net=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Wednesday, December 24, 2008 5:41 PM Subject: LF: Re: wspr Mal I was transmitting with WSJT7 in WSPR mode last night. Haven't used=20= it enough to say if it is 'better or worse', however it is designed to be us= ed in QSO mode rather than beacon mode so there are a number of differences. If you're interested in looking, I can transmit QRSS3 on Friday nigh= t for a bit. Jay ----- Original Message -----=20 From: mal hamilton=20 To: rsgb=20 Sent: Wednesday, December 24, 2008 11:35 AM Subject: LF: wspr Has anyone tried WSJT 7.02 in WSPR mode and found it better than t= he wspr 1.01version. Your experience ? mal/g3kev ------------------------------------------------------------------------ No virus found in this incoming message. Checked by AVG - http://www.avg.com=20 Version: 8.0.176 / Virus Database: 270.10.0/1862 - Release Date: 12/= 23/2008 12:08 PM ---------------------------------------------------------------------------- No virus found in this incoming message. Checked by AVG - http://www.avg.com=20 Version: 8.0.176 / Virus Database: 270.10.0/1863 - Release Date: 12/24/2= 008 11:49 AM ------=_NextPart_000_000B_01C96671.3F988EB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Mal
 
Roger the ERP situation.
 
I'll use 508.510 kHz instead of 505.24= kHz=20 since apparently that freq. was clear on your end.
 
Jay
----- Original Message -----
mal= =20 hamilton
Sent: Thursday, December 25, 2008 8= :15=20 AM
Subject: LF: Re: Re: Re: Re: wspr

Jay unfortunately I only have a max of 1w= erp=20 this year but hopefully next year 10w erp then we might do better, your en= d is=20 not a problem.
Will ck you qrg 505.24 although you would= be=20 better up the band a bit cos of the EU beacon qrm around 505 khz.
73 de mal/g3kev
 
----- Original Message -----
Sent: Thursday, December 25, 2008= 12:47=20 PM
Subject: LF: Re: Re: Re: wspr

Merry Christmas to all!
 
Mal
 
Will start looking for your signal at 2= 200Z=20 Friday night. WE2XGR/2 will be on 505.240 - if that frequency is cl= ear=20 on your end - please advise. I'll check your frequency but believe it to= be=20 clear from previous listening sessions. 
 
Setup here - WSPR the other=20 night 400 W transmitter power to a 90' top loaded vertica= l.=20 Friday night's transmissions will be at 1 kW. What transmitter powe= r=20 will you be using on your end? 
 
Jay
 
 
 
----- Original Message -----
From:=20 mal=20 hamilton
Sent: Thursday, December 25, 20= 08=20 6:12 AM
Subject: LF: Re: Re: wspr

Tnx Jay
I will TX on 502.57 khz starting at 2= 200 utc=20 Friday night. If any changes let me know.
I will be in QSO MODE ie CQ G3KEV QSK= . If u=20 hear me send my call to start a QSO. I will listen on ur QRG all the t= ime.=20 Pse let me know ur QRG.
QRS3 should be ok and if condx good w= ill=20 speed up.
73 and Merry Xmas Mal/G3KEV
----- Original Message -----
Sent: Wednesday, December 24,= 2008=20 5:41 PM
Subject: LF: Re: wspr

Mal
 
I was transmitting with WSJT7=20 in WSPR mode last night. Haven't used it enough to say if it is= =20 'better or worse', however it is designed to be used in QSO mode rat= her=20 than beacon mode so there are a number of differences.
 
If you're interested in looking, I=20= can=20 transmit QRSS3 on Friday night for a bit.
 
Jay
 
 
----- Original Message -----
From:=20 mal=20 hamilton
To: rsgb
Sent: Wednesday, December 2= 4,=20 2008 11:35 AM
Subject: LF: wspr

Has anyone tried WSJT 7.02 in WSP= R mode=20 and found it better than the wspr 1.01version.=20 Your experience ?
mal/g3kev
 


No virus found in this incoming message.
Checked by AV= G -=20 http://www.avg.com
Version: 8.0.176 / Virus Database: 270.10.0/1= 862=20 - Release Date: 12/23/2008 12:08 PM


No virus found in this incoming message.
Checked by AVG -=20 http://www.avg.com
Version: 8.0.176 / Virus Database: 270.10.0/1863=20= -=20 Release Date: 12/24/2008 11:49 AM
------=_NextPart_000_000B_01C96671.3F988EB0--