[Fwd: LF: Weekend tests]

[Andre' Kesteloot]

Mike Dennison wrote:

> This weekend, there is the greatest opportunity yet to make the
> transatlantic two-way.
>
> I would like to suggest some procedures to maximise that
> opportunity and minimise mutual QRM. Please feel free to point out
> any flaws in my argument.
>
> As far as possible, continuous beaconing should be avoided,
> especially if another station is operating near to you.
>
> Transmission slots to be 15 minutes: VE1ZZ transmits from 00 and
> 30 minutes past the hour, Eu stations transmit from 15 and 45
> minutes past the hour. Send just your own callsign and wait for Jack
> to identify you. If a QSO happens, all other stations to stop
> transmitting.
>
> There is a frequency plan at http:www.lf.thersgb.net/transatlantic.htm
> using the sub-band 135.9-136.0kHz. This includes the Loran
> frequencies for the Canadian end. It is intended for guidance only,
> but it will probably help the chances of success if we make an effort
> to avoid each other. It will also help John/Jack/Larry and the
> AMRAD team to know which frequency to find what station. Please
> e-mail me any updates.
>
> If it helps, I can post telephone numbers on that web page, too (they
> can be removed after the event).
>
> I will post a separate message reminding QRSS novices of
> procedures.
>
> Good luck!
>
> Mike, G3XDV (IO91VT)
> http://www.lf.thersgb.net

X-Mozilla-Status: 00099:49:24 2001
X-Mozilla-Status: 0801
X-Mozilla-Status2: 00000000
FCC: /C|/Program Files/Netscape/Users/akestelo/mail/Sent
BCC: akestelo@bellatlantic.net
Message-ID: <3A5B24F3.223AE5A1@bellatlantic.net>
Date: Tue, 09 Jan 2001 09:49:23 -0500
From: Andre' Kesteloot <akestelo@bellatlantic.net>
Reply-To: andre.kesteloot@ieee.org
X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; uuencode=0; html=0; linewidth=77
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD NSCPCD47  (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: lf-amrad <lf@amrad.org>, AMRAD Tacos <tacos@amrad.org>
Subject: [Fwd: LF: QRSS procedure]
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Mike Dennison wrote:

> QRSS can be confusing for anyone new to it, and any errors can
> be very time-consuming. I have seen people send zero instead of O,
> wasting several minutes, as well as QTH, power level etc. The idea is
> to be as brief as possible whilst keeping the message clear.
>
> Rik, ON7YD has a useful web page showing a typical QSO, and I
> can recommend it to anyone new to QRSS. It is at
> http://www.qsl.net/on7yd/136narro.htm
>
> I suggest for this weekend a slightly shorter format than shown by
> Rik. A QSO could progress as follows:
>
> VE1ZZ: "VE1ZZ VE1ZZ VE1ZZ" etc for 15 minutes.
> G3XDV: "G3XDV G3XDV G3XDV" etc for 15 minutes.
> VE1ZZ: "G3XDV G3XDV M M K"
> G3XDV: "ZZ R O O K"
> VE1ZZ (not copying): "? ? K"
> G3XDV: "ZZ R O O K"
> VE1ZZ: "XDV R R SK"
>
> There is no need to send '73' or 'TU', just 'SK'.
> Don't use 'QRZ' or 'AGN', and certainly not 'PSE RPT' - just '?' will do.
> Don't use full callsigns once the QSO has started, the suffix is
> enough.
> Only use the other station's callsign during the QSO. If you are
> unsure that the DX replied to you, it is permissible to use your own
> suffix as well but without the 'DE' (G3XDV: ZZ XDV O O K).
> Never use RST - the reporting system is:
> 'T' = Seen but not readable.
> 'M' = Readable but not 100%.
> 'O' = 100% of every character seen clearly.
>
> The golden rule is not to send anything that is not needed. A QRSS
> QSO can take 45 minutes. Using this procedure it will reduce to less
> than X-Mozilla-Status: 0009(IO91VT)
> http://www.lf.thersgb.net