Return-Path: Received: from rly-dc05.mx.aol.com (rly-dc05.mail.aol.com [172.19.136.34]) by air-dc09.mail.aol.com (v126.13) with ESMTP id MAILINDC094-b1f4b3878f3272; Mon, 28 Dec 2009 04:23:10 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-dc05.mx.aol.com (v125.7) with ESMTP id MAILRELAYINDC053-b1f4b3878f3272; Mon, 28 Dec 2009 04:23:00 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1NPBnd-0004VD-Kq for rs_out_1@blacksheep.org; Mon, 28 Dec 2009 09:22:01 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1NPBnd-0004V4-3t for rsgb_lf_group@blacksheep.org; Mon, 28 Dec 2009 09:22:01 +0000 Received: from smtp-out4.blueyonder.co.uk ([195.188.213.7]) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1NPBnb-0001mg-2X for rsgb_lf_group@blacksheep.org; Mon, 28 Dec 2009 09:22:01 +0000 Received: from [172.23.170.138] (helo=anti-virus01-09) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1NPBna-0001OA-2r for rsgb_lf_group@blacksheep.org; Mon, 28 Dec 2009 09:21:58 +0000 Received: from [92.235.33.173] (helo=p4) by asmtp-out6.blueyonder.co.uk with smtp (Exim 4.52) id 1NPBnZ-0008Li-9G for rsgb_lf_group@blacksheep.org; Mon, 28 Dec 2009 09:21:57 +0000 Message-ID: From: "Mark" To: References: <80578.2091.qm@web86505.mail.ird.yahoo.com> <5263798E332240C3BC686B3164057D2F@p4> Date: Mon, 28 Dec 2009 09:21:57 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5843 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Spam-Score: 3.4 (+++) X-Spam-Report: autolearn=disabled,FORGED_MUA_OUTLOOK=3.36,HTML_MESSAGE=0.001 Subject: LF: Re: WD2XSH/17 decoded in GM Content-Type: multipart/alternative; boundary="----=_NextPart_000_0080_01CA879F.33BA5600" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: ** X-Spam-Status: No, hits=2.4 required=5.0 tests=FORGED_MUA_OUTLOOK,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-IP: 193.82.116.20 ------=_NextPart_000_0080_01CA879F.33BA5600 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi All,=20 Must be too early, it seems I missed a bit in the change log about sup= port for compound callsigns in V2 Excellent! Mark GM4ISM ----- Original Message -----=20 From: Mark=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Monday, December 28, 2009 9:03 AM Subject: LF: WD2XSH/17 decoded in GM Hi All,=20 3 instances of decodes of WD2XSH on 503.890KHz last night between 01= :00 and 03:00z all with bad message tagged, and no /17 appended These of course did not upload, sigs were 2 off -28 dB and 1 off -27= dB Several other corrupted calls reported on the same frequency. I was using WSPR1.01, now upgraded to WSPR2 r1714. The change log= does not suggest that 1.01 does not handle the suffixes correctly, bu= t I am hoping that the upgrade will improve things Interestingly the RX noise level indicator says -30dB all the time,= irrespective of the audio level settings, though it displays and deco= des well enough. Soundcard setup is non-standard here, RX is softrock, processed by= Speclab (which also provides the grabber see www.dc2light.co.uk for= a link) Audio Output from Speclab is filtered, frequency shifted and= then passed to the WSPR software. Pleased to copy the WD2XSH/17 on the tiny mag loop antenna, which is= aligned roughly E-W and therfore has a null towards the USA Hopefully future spots will reach the database. Hope all have a happy and prosperous 2010 Mark GM4ISM IO85AR ----------------------------------------------------------------------= -------- No virus found in this incoming message. Checked by AVG - www.avg.com=20 Version: 9.0.722 / Virus Database: 270.14.121/2589 - Release Date:= 12/27/09 09:18:00 ------=_NextPart_000_0080_01CA879F.33BA5600 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
Hi All,
Must be too early, it seems I missed= a bit in the=20 change log about support for compound callsigns in V2
 
Excellent!
Mark GM4ISM
----- Original Message -----
From:=20 Mark
Sent: Monday, December 28, 20= 09 9:03=20 AM
Subject: LF: WD2XSH/17 decode= d in=20 GM

Hi All,
3 instances of decodes of WD2XSH=20 on 503.890KHz last night between 01:00 and 03:00z all with ba= d message=20 tagged, and no /17 appended
These of course did not upload, sig= s were 2 off=20 -28 dB and 1 off -27dB
Several other corrupted calls repor= ted on the=20 same frequency.
 
I was using WSPR1.01, now upgraded= to WSPR2 =20 r1714. The change log does not suggest that 1.01 does not handle the= suffixes=20 correctly, but I am hoping that the upgrade will improve things
 Interestingly the RX noise le= vel indicator=20 says -30dB all the time, irrespective of the audio level settings,= though it=20 displays and decodes well enough.
Soundcard setup is non-standard her= e, RX is=20 softrock, processed by Speclab (which also provides the grabber = ; see www.dc2light.co.uk= for a link) Audio=20 Output from Speclab is filtered, frequency shifted and then passed= to the WSPR=20 software.
 
Pleased to copy the WD2XSH/17= on the tiny=20 mag loop antenna, which is aligned roughly E-W and therfore has a nu= ll towards=20 the USA
Hopefully future spots will reach= the=20 database.
Hope all have a happy and prosperou= s=20 2010
Mark GM4ISM IO85AR


No virus found in this incoming message.
Checked by AV= G -=20 www.avg.com
Version: 9.0.722 / Virus Database: 270.14.121/2589= - Release=20 Date: 12/27/09 09:18:00
------=_NextPart_000_0080_01CA879F.33BA5600--