Return-Path: Received: from mtain-md12.r1000.mx.aol.com (mtain-md12.r1000.mx.aol.com [172.29.96.96]) by air-mb05.mail.aol.com (v126.13) with ESMTP id MAILINMB052-a3844b4383bf71; Tue, 05 Jan 2010 13:24:00 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by mtain-md12.r1000.mx.aol.com (Internet Inbound) with ESMTP id 3D21E38000532; Tue, 5 Jan 2010 13:23:57 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1NSE3A-0004Dk-SQ for rs_out_1@blacksheep.org; Tue, 05 Jan 2010 18:22:36 +0000 Received: from [83.244.159.144] (helo=relay3.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1NSE3A-0004Db-5j for rsgb_lf_group@blacksheep.org; Tue, 05 Jan 2010 18:22:36 +0000 Received: from out1.ip05ir2.opaltelecom.net ([62.24.128.241]) by relay3.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1NSE37-0007Up-C0 for rsgb_lf_group@blacksheep.org; Tue, 05 Jan 2010 18:22:36 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtMEANwRQ0tZ8qiZ/2dsb2JhbACNRgbGOoQwBA X-IronPort-AV: E=Sophos;i="4.47,507,1257120000"; d="scan'208,217";a="261606055" Received: from unknown (HELO xphd97xgq27nyf) ([89.242.168.153]) by out1.ip05ir2.opaltelecom.net with SMTP; 05 Jan 2010 18:22:05 +0000 Message-ID: <000d01ca8e33$fb097de0$0401a8c0@xphd97xgq27nyf> From: "mal hamilton" To: References: <1569989546@web.de> <007501ca8d6e$86e3de80$0401a8c0@xphd97xgq27nyf> <9afca2641001050941v40248a15o4e08eb8f77b074f3@mail.gmail.com> Date: Tue, 5 Jan 2010 18:22:03 -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: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: Re: LF: Callsigns Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01CA8E33.FAC45E90" 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: 3039ac1d60604b4383bd22f5 X-AOL-IP: 193.82.116.20 ------=_NextPart_000_000A_01CA8E33.FAC45E90 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Anything slower than QRS 3 leads to problems in QSB, some of the dashe= s break up and we get gibberish QRS10 is about the limit. Some use QRS 120 and 240 ie take 240 sec dot that is 4 minute dot and= 12minute dash, this is a long time and when QSB hits the whole dot/da= sh train gets chopped and appears as irregular traces and garbled, thi= s leads to guesswork by the RX station, especially when someone has in= dicated a frequency that they will use. It has all been discussed in the past so the above information is a co= nsensus of opinion by experienced LF/MF operators. also, QRS is a real time mode with immediate exchange of information= between two or more stations and Attended by operators at each end. I hope you are satisfied by this observation G3KEV =20 ----- Original Message -----=20 From: Roger Lapthorn=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Tuesday, January 05, 2010 5:41 PM Subject: Re: LF: Callsigns Mal, So you've no strong views on slow QRS modes. That's good..=20 73s Roger 2010/1/4 mal hamilton Chris QRS 3 is manageable for a full call but when it gets to QRS 60, 12= 0, 240 and 480 it is pathetic and unnecessary because on LF/MF when QSB hit= s 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= Mongolia !! 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 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= 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 QRSS= 3, for > example, it sometimes just takes too long. While testing in QRSS= 3 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. Thats > 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 ever= y so > > often, in the same mode as they are transmitting. I can undert= sand > > not doing so during a QSO once contact has been established (t= o 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 ------=_NextPart_000_000A_01CA8E33.FAC45E90 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Anything slower than QRS 3 leads to= problems in=20 QSB, some of the dashes break up and we get gibberish QRS10 is about= the=20 limit.
Some use QRS 120 and 240 ie take= 240 sec dot=20 that is 4 minute dot and 12minute dash, this is a long time and when= QSB hits=20 the whole dot/dash train gets chopped and appears as irregular traces= and=20 garbled, this leads to guesswork by the RX station, especially when so= meone has=20 indicated a frequency that they will use.
It has all been discussed in the past= so the above=20 information is a consensus of opinion by experienced LF/MF=20 operators.
also, QRS is a real time mode with im= mediate=20 exchange of information between two or more stations and Attended by= operators=20 at each end.
I hope you are satisfied by this=20 observation
 
G3KEV
 
 
 
 
----- Original Message -----
Sent: Tuesday, January 05, 20= 10 5:41=20 PM
Subject: Re: LF: Callsigns

Mal,

So you've no strong views on slow QRS mod= es. That's=20 good..

73s
Roger

2010/1/4 mal hamilton <<= A href=3D"mailto:g3kevmal@talktalk.net">g3kevmal@talktalk.net&= gt;
Chris<= BR>QRS=20 3 is manageable for a full call but when it gets to QRS 60, 120,= 240=20 and
480 it is pathetic and unnecessary because on LF/MF  w= hen=20  QSB hits the
whole dots/dashes are broken up and meaningless.ie= =20 gibberish
Still some insist so what can one do ????????????????=
I=20 ignore anything slower than QRS 10 even if it comes from outer Mon= golia=20 !!
G3KEV


----- Original Message -----
From: "Chr= is" <c.ashby435@= btinternet.com>
To:=20 <rsgb_lf_= group@blacksheep.org>
Sent: Monday, January 04, 2010 6:10 PM
Subject:= Re: LF:=20 Callsigns


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




--=20
-------------------------------------------------------------http://g3xbm-qrp.blogs= pot.com/
http://www.g3xb= m.co.uk
G3XBM  =20  GQRP 1678      ISWL G11088
------=_NextPart_000_000A_01CA8E33.FAC45E90--