Return-Path: Received: from rly-mh03.mx.aol.com (rly-mh03.mail.aol.com [172.21.166.139]) by air-mh02.mail.aol.com (v121_r5.5) with ESMTP id MAILINMH023-bc84957e4f7286; Sun, 28 Dec 2008 15:43:56 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-mh03.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINMH038-bc84957e4f7286; Sun, 28 Dec 2008 15:43:38 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LH2Tp-0007JH-FU for rs_out_1@blacksheep.org; Sun, 28 Dec 2008 20:43:21 +0000 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LH2To-0007J8-Qc for rsgb_lf_group@blacksheep.org; Sun, 28 Dec 2008 20:43:20 +0000 Received: from smtp5.freeserve.com ([193.252.22.151] helo=smtp6.freeserve.com) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1LH2Tn-00038j-L6 for rsgb_lf_group@blacksheep.org; Sun, 28 Dec 2008 20:43:20 +0000 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3507.me.freeserve.com (SMTP Server) with ESMTP id 9D8307000084 for ; Sun, 28 Dec 2008 21:43:13 +0100 (CET) Received: from AGB (unknown [91.109.43.175]) by mwinf3507.me.freeserve.com (SMTP Server) with SMTP id 5F23B7000083 for ; Sun, 28 Dec 2008 21:43:13 +0100 (CET) X-ME-UUID: 20081228204313389.5F23B7000083@mwinf3507.me.freeserve.com Message-ID: From: "Graham" To: References: <4956BFEE.19110.2EE6D21@v.d.heide.on-line.de> <001601c968e6$912297e0$4201a8c0@home> <4957D4F8.9000709@telus.net> In-Reply-To: <4957D4F8.9000709@telus.net> Date: Sun, 28 Dec 2008 20:43:12 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.5027.908 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.5027.908 X-Karma: -140: lashback.ubl=-140.0 X-Spam-Score: 0.3 (/) X-Spam-Report: autolearn=disabled,MAILTO_TO_SPAM_ADDR=0.276 Subject: Re: LF: Re: WSPR and CW Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: * X-Spam-Status: No, hits=1.2 required=5.0 tests=MAILTO_TO_SPAM_ADDR, MISSING_OUTLOOK_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 Scott,, JT65 I did a test with jt65 a while ago .. it stopped working about 3 db before the wspr .beacon the K1JT version gave a s/n level about 3 dB better than the multipsk version ....not sure why as they where sent on alternate odd/even slots via the same sound card/tx system The test encountered a little mid band qrm from a mal adjusted cw beacon at the time , but the results are at http://groups.google.com/group/uk500khz/web/jt65-a--jt2-tests G ... -------------------------------------------------- From: "Scott Tilley" Sent: Sunday, December 28, 2008 7:35 PM To: Subject: Re: LF: Re: WSPR and CW > > Hi Jim > > Interesting comments and its pretty much what I experience on WSPR HF. > Another factor to consider with WSPR is the soundcard sampling rate it > uses 12000sps. Some have had issues with this as noted in a recent post > on the WSPRnet blog: > http://wsprnet.org/drupal/node/339 > > This coupled with lack of time sync likely explains the issues > encountered by 'super ham.' > > One thought would be to lengthen the sequence to deal with the 600m fade > period OR allow WSPR to have an averaging function much like JT65. With > careful use of the average function in JT65 I was able to work many very > small stations off the moon that would otherwise be impossible. I bet > the same would hold true for LF/MF and it would make all those not quiet > good even sequences useful. > > Has anyone tried JT65 on 600m??? That should send 'super ham' spinning... > > 73 Scott > VE7TIL > > James Moritz wrote: >> Dear Klaus, Laurence, LF Group, >> >> I have been doing some experiments with WSPR on 2 PCs linked by audio >> cables. I would certainly agree with KL1X about the importance of clock >> accuracy - I found that an error of 5 seconds was enough to completely >> prevent decoding. Fortunately, the clock on my shack PC is accurate >> enough >> that setting it against an MSF-controlled clock once every several hours >> is >> OK. I also found that the "QSO version" of WSPR in WSJT 7 and the WSPR >> 1.01 >> beacon software will correctly decode each other's signals, although in >> either case the QSO mode requires reception of all the overs of the QSO >> in >> order to display the callsigns, due to the format used. When using the >> beacon software for reception, be aware that it may take some minutes for >> the decode to appear after the signal has been received - this seems to >> be >> due to the "off line" nature of the signal processing used. >> >> Recent experience here is that the WSPR mode offers advantages compared >> to >> CW, either manual or QRSS, on the 500kHz band due to the low SNR and the >> fading experienced. Many signals are either always below the audible >> noise, >> or not audible for long enough for aural CW copy without large numbers of >> repeats. With QRSS, and a sufficiently long dot period, one can indeed >> detect very weak signals, but the fading often prevents receiving, for >> example, a complete callsign without losing some symbols and so also >> requiring repeats. QRSS works much better on 136k, where the fading >> period >> is much longer. >> >> WSPR certainly decodes signals that are too weak for aural reception. In >> sensitivity terms, I think it is comparable to QRSS 3. WSPR has the >> advantage over QRSS 3 that the message duration is shorter. The 2 minute >> transmission period of WSPR is a reasonable match to the fading period >> experienced on 500kHz, so there is a good chance of sending the message >> successfully before the signal fades out. I have yet to see any readable >> trans-atlantic CW or QRSS signals at this QTH, while copy of WE2XGR//2 >> using >> WSPR was reasonably consistent, producing a decode for about 25% of the >> transmissions. The redundancy in the data should also make WSPR >> relatively >> resistant to errors caused by QRN impulses, although the QRN level has >> been >> low here recently. For beacon purposes, WSPR also has the huge advantage >> that reception, logging and reporting is automated, so the operator can >> go >> to bed sometimes! >> >> While WSPR does work well, I don't think it is the final word in LF/MF >> digital modes - In particular, the information in a QSO is largely >> restricted to "rubber stamp" exchanges. So I will certainly be interested >> in >> trying other modes, and look forward to see the results of Klaus' work. >> >> Cheers, Jim Moritz >> 73 de M0BMU >> >> >> >> >> >> >> >> > > > > No virus found in this incoming message. > Checked by AVG - http://www.avg.com > Version: 8.0.176 / Virus Database: 270.10.0/1866 - Release Date: > 12/27/2008 20:49 >