Return-Path: Received: from mtain-dh07.r1000.mx.aol.com (mtain-dh07.r1000.mx.aol.com [172.29.65.27]) by air-de02.mail.aol.com (v126.13) with ESMTP id MAILINDE023-5ea84b437a469e; Tue, 05 Jan 2010 12:43:34 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by mtain-dh07.r1000.mx.aol.com (Internet Inbound) with ESMTP id 5D9F7380001B3; Tue, 5 Jan 2010 12:43:32 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1NSDPo-00044p-UO for rs_out_1@blacksheep.org; Tue, 05 Jan 2010 17:41:56 +0000 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1NSDPo-00044g-E2 for rsgb_lf_group@blacksheep.org; Tue, 05 Jan 2010 17:41:56 +0000 Received: from mail-bw0-f221.google.com ([209.85.218.221]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1NSDPl-0002Wm-Ll for rsgb_lf_group@blacksheep.org; Tue, 05 Jan 2010 17:41:56 +0000 Received: by bwz21 with SMTP id 21so10554717bwz.4 for ; Tue, 05 Jan 2010 09:41:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=lsCFCxIUkDBmQQKEawwvsP0p6oqytNqqQmAerFV3aRI=; b=soioxmOCJw8tDZyDWZSo7E/Mk8lV9TKZk0Fd1Cb51hiOtJWI3cwJ4mCn5bakvP7j08 WINThFUDRTwU/EWtTV0ROrLKa7p36DV7D6lhzbDmY9k5zdM/8pKeUN8//o2dkesuFvaY rkaklIOxfCgQaNnI9yfDiUX1NVafZK6BFHfcI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=wdi6Hxr0yn0LDxGpUeJE8b2yxcUBUOKMptD4rfLZbqTHkXaFqaHV3lvNFC0KuED95v 6Ig1SW3X1U16kV+jkeUS4VUv359FtWnSHAzhd98Sxpq5CRqSSxIETC0jy/wWVVzDjWLO AWOOw71b9R44XxJ0PY9PviXQnh0szssS9+mgc= MIME-Version: 1.0 Received: by 10.204.4.215 with SMTP id 23mr3361494bks.160.1262713306555; Tue, 05 Jan 2010 09:41:46 -0800 (PST) In-Reply-To: <007501ca8d6e$86e3de80$0401a8c0@xphd97xgq27nyf> References: <1569989546@web.de> <007501ca8d6e$86e3de80$0401a8c0@xphd97xgq27nyf> Date: Tue, 5 Jan 2010 17:41:45 +0000 Message-ID: <9afca2641001050941v40248a15o4e08eb8f77b074f3@mail.gmail.com> From: Roger Lapthorn To: rsgb_lf_group@blacksheep.org X-Karma: unknown: DomainKey-Status: good (testing) X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: Re: LF: Callsigns Content-Type: multipart/alternative; boundary=0015174c1caa172569047c6e5a79 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_20_30,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: 3039ac1d411b4b437a442c86 X-AOL-IP: 193.82.116.20 X-Mailer: Unknown (No Version) --0015174c1caa172569047c6e5a79 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mal, So you've no strong views on slow QRS modes. That's good.. 73s Roger 2010/1/4 mal hamilton > Chris > QRS 3 is manageable for a full call but when it gets to QRS 60, 120, 240 > and > 480 it is pathetic and unnecessary because on LF/MF when QSB hits the > whole dots/dashes are broken up and meaningless.ie gibberish > Still some insist so what can one do ???????????????? > I ignore anything slower than QRS 10 even if it comes from outer Mongoli= a > !! > G3KEV > > > ----- Original Message ----- > From: "Chris" > To: > Sent: Monday, January 04, 2010 6:10 PM > Subject: Re: LF: Callsigns > > > > Hi Horst, > > I don't agree. If a station is beaconing in QRSS3, time surely is hard= ly > a > > problem. Why they can't send a full callsign , say, every fifth time > beats > > me. Anyway, isn't the prefix of more interest to listeners who may not= be > on > > this site? > > Chris, G4AYT. > > ----- Original Message ----- > > From: "Horst St=F6cker" > > To: > > Sent: Monday, January 04, 2010 5:25 PM > > Subject: Re: LF: Callsigns > > > > > > Hello Chris, in standard CW this will be no problem. But in QRSS3, for > > example, it sometimes just takes too long. While testing in QRSS3 or > other > > "slow" modes, I send CW ID for local operators. As the S/N ratio is wo= rse > > not everyone who can read my QRSS3 is able to read my standard CW. Tha= ts > > part of the game . . . > > Horst > > > > .> -----Urspr=FCngliche Nachricht----- > > > Von: "Chris" > > > Gesendet: 04.01.10 17:19:13 > > > An: "RSGB LF Group" > > > Betreff: LF: Callsigns > > > > >I wish beaconing stations would send a full callsign, even every so > > > often, in the same mode as they are transmitting. I can undertsand > > > not doing so during a QSO once contact has been established (to save > > > time). > > > > > > Chris, G4AYT. > > > > > > ___________________________________________________________ > > Preisknaller: WEB.DE DSL Flatrate f=FCr nur 16,99 Euro/mtl.! > > http://produkte.web.de/go/02/ > > > > > > > > > --=20 ------------------------------------------------------------- http://g3xbm-qrp.blogspot.com/ http://www.g3xbm.co.uk G3XBM GQRP 1678 ISWL G11088 --0015174c1caa172569047c6e5a79 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mal,

So you've no strong views on slow QRS modes. That's go= od..

73s
Roger

2010/1/4 mal= hamilton <g= 3kevmal@talktalk.net>
Chris
QRS 3 is manageable for a full call but when it gets to QRS 60, 120, 240= and
480 it is pathetic and unnecessary because on LF/MF =A0when =A0QSB hits th= e
whole dots/dashes are broken up and meaningless.ie gibberish
Still some insist so what can one do ????????????????
I ignore anything slower than QRS 10 even if it comes from outer Mongolia= !!
G3KEV


----- Original Message -----
From: "Chris" <c= .ashby435@btinternet.com>
To: <rsgb_lf_group@blac= ksheep.org>
Sent: Monday, January 04, 2010 6:1= 0 PM
Subject: Re: LF: Callsigns


> Hi Horst,
> I don't agree. If a station is beaconing in QRSS3, time surely is= hardly a
> problem. Why they can't send a full callsign , say, every fifth= time beats
> me. Anyway, isn't the prefix of more interest to listeners who ma= y not be
on
> this site?
> Chris, G4AYT.
> ----- Original Message -----
> From: "Horst St=F6cker" <horst.stoecker@web.de>
> To: <rsgb_lf_group= @blacksheep.org>
> Sent: Monday, January 04, 2010 5:25 PM
> Subject: Re: LF: Callsigns
>
>
> Hello Chris, in standard CW this will be no problem. But in QRSS3, fo= r
> example, it sometimes just takes too long. While testing in QRSS3 or= other
> "slow" modes, I send CW ID for local operators. As the S/N= ratio is worse
> not everyone who can read my QRSS3 is able to read my standard CW. Th= ats
> part of the game . . .
> Horst
>
> .> -----Urspr=FCngliche Nachricht-----
> > Von: "Chris" <c.ashby435@btinternet.com>
> > Gesendet: 04.01.10 17:19:13
> > An: "RSGB LF Group" <rsgb_lf_group@blacksheep.org>
> > Betreff: LF: Callsigns
>
> >I wish beaconing stations would send a full callsign, even every= so
> > often, in the same mode as they are transmitting. I can undertsa= nd
> > not doing so during a QSO once contact has been established (to= save
> > time).
> >
> > Chris, G4AYT.
>
>
> ___________________________________________________________
> Preisknaller: WEB.DE= DSL Flatrate f=FCr nur 16,99 Euro/mtl.!
> http://pr= odukte.web.de/go/02/
>
>
>





--
----------= ---------------------------------------------------
http://g3xbm-qrp.blogspot.com/
http://www.g3xbm.co.uk
G3XBM =A0 =A0GQRP 1678 =A0 =A0 =A0ISWL G11088
--0015174c1caa172569047c6e5a79--