MS Scheduling, Procedures and Software (2)
To: rein0zn@ix.netcom.com
From: Steve, KoOU/1
Subject: [METEOR-SCATTER] CQ MS Sked
Date: Wed, 6 Aug 97 15:34:07 EST5EDT
The Perseids are coming: time to get on the radios and make meteor scatter
skeds!
As of last Saturday, I've had to change my CQ MS sked frequency from the
original 144.150 to 144.100 due to a new and as-yet unlocated birdie. I call
CQ on CW during the odd minutes of two separate time periods from central
Massachusetts, FN42dg.
During the first session from 1100 to 1115Z, the antenna is pointed
more-or-less southwest (toward EM84). During the second session from 1130 to
1145Z, the antenna is pointed west-north-west (toward EN34). These
directions should be favoring the areas of highest V/UHF aficianados. After
1145Z, I generally shift to 144.2 or 432.1 and CQ slow speed in any
direction of interest for tropo.
I transmit for one full minute during the Transmit Time Sequences shown
below, and listen for calls during the even minute sequences, including the
first minute of each session. I will match the speed of whoever I hear calling.
Also, if you would like to monitor a high-speed CW sked, you can listen in
on W8WN/EM77 and myself on 144.157 MHz, Monday through Saturday (except most
Thursdays). I call Shel at 1500 lpm (300 WPM) while Shel calls me at 425 lpm
(85 WPM). Ask Shel or myself about getting started with high-speed CW meteor
scatter; Shel's e-mail is W8WN , and
my home e-mail address is shown below.
You can also visit the Meteor Scatter page of Rein Smit, W6/PA0ZN; Rein adds
new stuff almost daily, so check it out:
US MS WEB Information Site
If anybody is interested, I would like to make more CW MS skeds, daily or
one-shot on 144, 222 or 432 MHz. Please respond to my home e-mail address:
Steve, KoOU
73, Steve Ko0U/1
Transmit | Transmit Call: Ko0U Grid: FN42dg
Time Antenna | Time Antenna Freq.: 144.100 Mode: CW
Sequence Direction | Sequence Direction Speed: 200 lpm (40 WPM)
---------------------|---------------------- Home e-mail:
1101-1102 SW | 1131-1132 WNW
1103-1104 " | 1133-1134 " Try listening for W8WN/EM77
1105-1106 " | 1135-1136 " and Ko0U/FN42 on sked from
1107-1108 " | 1137-1138 " 1115Z to 1130Z; W8WN transmits
1109-1110 " | 1139-1140 " "even" minutes at 425 lpm
1111-1112 " | 1141-1142 " (85 WPM), while Ko0U transmits
1113-1114 " | 1143-1144 " "odd" minutes at 1500 lpm
(300 WPM).
Date:Thu, 7 Aug 1997 01:58:13 +0000
From: Shelbi, W8WN
Subject: US HS CW MS Sked
To: MOON-NET@VM.STLAWU.EDU
(We realize that this is the EME reflector. But most of the interest has
been generated by the postings HERE, not on the other VHF reflectors!)
Here is the first listing of approximate CQ times, frequencies, and
procedures for the Perseids for W8WN, EM77, 144 MHz.
Even if you haven't been able to get set up for high-speed CW MS this time
around, make a note of these things. If you can download this, you
probably already have a method - slow and clumsy, but possible - to decode
what you might hear. We would like reception reports, as well as QSOs,
this shower.
Note that CQ times are approximate, and will vary as skeds, sleep, etc
change things.
Fri eve (local) - 0000-0300 UTC 9 Aug
Sat eve (local) - 0000-0200 UTC 10 Aug
Sun eve (local) - 0100-0300 UTC 11 Aug
Mon eve/Tues morn (local) - 0000-1200 UTC 12 Aug (thru probable first peak)
Tues afternoon (local) - 1700-2200 UTC 12 Aug (thru probably second peak)
This will be updated about Monday.
CQs will be transmitted on 144.100. I will listen (then QSY) to 144.106.
I will most likely transmit at 1000 lpm (200 wpm). I will be xmtg on
one-minute periods - 0000-0001, 0002-0003, etc etc - same sequence
regardless of ant heading.
NOTE that I will NOT be listening on 144.100!!! This is the frequency that
will be used by me (and several others) for CALLING CQ! I will LISTEN on
144.106. If I hear and identify you on 144.106, I will then ALSO begin to
transmit on 144.106. So once you have identified me (or some other
station) and are ready to call, you will TRANSMIT AND LISTEN on 144.106, or
whatever frequency the station specifies (see below).
My CQ sequence will most likely be CQF W8WN CQF W8WN etc etc. The "F"
means that I will be receiving UP 6 KHZ. (CQ H would mean that a station
is listening up 8 kHz; CQ N means that the station is listening up 14 kHz;
etc).
Since, if you call me on 144.106, it will be obvious that you are copying
me. So I will continue to xmit at the same speed and sequency, BUT
changing my xmit freq and sending your call & report (K0SM W8WN S2 S2
K0SM....). Then, exchange Rs, etc, as usual. If you can receive but can't
transmit at this speed, use whatever speed you have. Or, call on SSB.
We'll try whatever you have.
If you hear a high speed sig on 144.100, be sure of the ID before calling
me. There will be somewhere between 3 and 6 or more OTHER stations in
North America calling some CQs on 144.100. Since I don't know where they
will be listening (get the letter following the CQ), what times they might
try, which sequence they will use, or how many of them will actually be QRV
by the Perseids peak, I can't give any further info. But if you listen on
144.100, you might have a shot at several different stations, in different
parts of the country.
This information will be stored on the Web page at:
MS WEB Information Site
in case you hear something and can't find this message. So you may want to
note the above URL. And note that this long missive will NOT be repeated -
only a couple of updates on CQ times and a BRIEF summary of the procedure.
Note, too, that the procedure is not exactly the same as that used in
Europe.
At the above Web page you will also find links to other MS pages, including
those that have the HS CW receiving programs. Be advised, also, the 9A4GL
has just released his Beta version 0.40, WHICH WILL BOTH RECEIVE AND
TRANSMIT HS CW! By the time you read this, there should be a v. 0.41 on
his Web page, getting rid of a few of the bugs. His programs can be found
at:
MSDSP ver 0.40 by 9A4GL
If you start hearing HS CW on pings but don't have one of the programs or
devices for receiving it, remember that you can save pings on cassette
tape, record it as a .WAV file, slow this down about 8 times, and, if your
initially-recorded pitch was high enough (it needs to be 1000 Hz or
higher), you can then read it. Slow, but works. Can even use Zoom and
read some off the screen. Won't work for a QSO, but would give you the
ability to find out just what you had received! The Windows 95 version of
CoolEdit even makes it easy, they say.
If you have need to fone me (502)737-8361, be prepared to leave a message
on the (crazy) answering device. When not on the air, I probably won't be
home. And when operating I often don't hear the fone. (The XYL WD8LPN
usually unplugs her fone during meteor showers!) E-mail will be checked
occasionally; but sometimes it is difficult to connect to InfiNet.
Rig is 8877 at about 1 Kw; 4 KLM 16LBX antennas, az-el, @ 15 meters (but in
a small valley); mast-mount preamp, separate receiver. Will most likely be
running V0.4 MS_DSP for both Xmtg and Rcvg. Location is central KY, EM77bq.
We are available for a few skeds (HS CW, CW, SSB) if you need this grid.
But we want to put out a number of CQs to give stations a chance to
practice with their new "toys" on actual pings and bursts (we hope). Watch
for me and several others on 144.100.
73 & good DX, Shelby, W8WN
Shelby, W8WN - EM77bq
w8wn@ne.infi.net
To: "Rein A. Smit"
From: US MS WEB Information Site
in case you hear something and can't find this message. So you may want to
note the above URL. And note that this long missive will NOT be repeated -
only a couple of updates on CQ times and a BRIEF summary of the procedure.
Note, too, that the procedure is not exactly the same as that used in Europe.
At the above Web page you will also find links to other MS pages, including
those that have the HS CW receiving programs. Be advised, also, the 9A4GL
has just released his Beta version 0.40, WHICH WILL BOTH RECEIVE AND
TRANSMIT HS CW! By the time you read this, there should be a v. 0.41 on
his Web page, getting rid of a few of the bugs. His programs can be found
at:
MSDSP ver 0.40 by 9a4GL
If you start hearing HS CW on pings but don't have one of the programs or
devices for receiving it, remember that you can save pings on cassette
tape, record it as a .WAV file, slow this down about 8 times, and, if your
initially-recorded pitch was high enough (it needs to be 1000 Hz or
higher), you can then read it. Slow, but works. Can even use Zoom and
read some off the screen. Won't work for a QSO, but would give you the
ability to find out just what you had received! The Windows 95 version of
CoolEdit even makes it easy, they say.
If you have need to fone me (502)737-8361, be prepared to leave a message
on the (crazy) answering device. When not on the air, I probably won't be
home. And when operating I often don't hear the fone. (The XYL WD8LPN
usually unplugs her fone during meteor showers!) E-mail will be checked
occasionally; but sometimes it is difficult to connect to InfiNet.
Rig is 8877 at about 1 Kw; 4 KLM 16LBX antennas, az-el, @ 15 meters (but in
a small valley); mast-mount preamp, separate receiver. Will most likely be
running V0.4 MS_DSP for both Xmtg and Rcvg. Location is central KY, EM77bq.
We are available for a few skeds (HS CW, CW, SSB) if you need this grid.
But we want to put out a number of CQs to give stations a chance to
practice with their new "toys" on actual pings and bursts (we hope). Watch
for me and several others on 144.100.
73 & good DX, Shelby, W8WN
Shelby, W8WN - EM77bq
w8wn@ne.infi.net
Date: Thu, 07 Aug 1997 18:22:00 +0000
To: Steve Harrison , vhf@w6yx.stanford.edu, wsvhf@qsl.net
From: ,A HREF="mailto:w8wn@ne.infi.net"> Shelby, W8WN
Subject: Re: [WSVHF] MSDSP v0.41 Available Now
New version, 0.41, says it fixed the main buffer retrace problem. Looks good!
W8WN
At 11:12 8/7/97 EST5EDT, Steve Harrison wrote:
Just received the following on the Meteor Scatter reflector. Also, I tried
running version 0.40 as downloaded yesteday and the main buffer would not
retrace to continue recording. David, WD4KPD also reported this; but W8WN
tells me he does not recall seeing this happen on his computer. The older
versions retraced properly for both David and myself. Has anyone else
noticed this? Perhaps the newest version 0.41 fixed it.
73, Steve Ko0U/1
Hi folks,
just came in via EU PacketNetwork :
VHF @WW de:9A4GL 07.08.97 14:09 90 2003 Bytes
!!! MSDSP V0.41 RX/TX MS HS CW !!!
...
From: 9A4GL @ 9A0BBS.HRV.EU (HeTi)
To : VHF @ WW
Hi MS CW workers !
There are MSDSP V0.41.
It fixes some stupied bugs from V0.40.
The program is also available at:
MSDSP ver 0.41
(exact URL of file: MSDSP041.ZIP
Just to remember you what is new: TX part now works (but strange BUG on my
side which swap channels, read documentation for details). Some debuging
stuff added (to find devide error problem). Sample rate is now 6000 (it is
enought) and this enlarge the main buffer to 1min. Also now SB card must be
on DMA 1 (becouse some SB programming problems).
This is the last version before the Persaids. Tomorrow (10.08) I will go to
adriatic coast and will not read email/mails until 20.08, sri. Good luck and
hope there will be no problems.
...
If you want to know when new version is available on my homepage send me
email with your email address, and every time new version is out, you will
recieve email.
...
73 de Tihomir, 9A4GL@9A0BBS.HRV.EU
email: Tihomer, 9A4GL
Home page
(VHF) DK3XT de DB0GE>
73,
Bernie or DK3XT
Home Page
Make More Miles on VHF
To: vhf@w6yx.stanford.edu, wsvhf@qsl.net
From: Steve, Ko0U/1
Subject: MSDSP v0.41 Available Now
Date: Thu, 7 Aug 97 11:12:26 EST5EDT
Just received the following on the Meteor Scatter reflector. Also, I tried
running version 0.40 as downloaded yesteday and the main buffer would not
retrace to continue recording. David, WD4KPD also reported this; but W8WN
tells me he does not recall seeing this happen on his computer. The older
versions retraced properly for both David and myself. Has anyone else
noticed this? Perhaps the newest version 0.41 fixed it.
73, Steve Ko0U/1
Hi folks,
just came in via EU PacketNetwork :
>VHF @WW de:9A4GL 07.08.97 14:09 90 2003 Bytes
>!!! MSDSP V0.41 RX/TX MS HS CW !!!
> ...
From: 9A4GL @ 9A0BBS.HRV.EU (HeTi)
To : VHF @ WW
Hi MS CW workers !
There are MSDSP V0.41.
It fixes some stupied bugs from V0.40.
The program is also available at:
9A4GL
(exact URL of file:
MSDSP041.ZIP
Just to remember you what is new: TX part now works (but strange BUG on my
side which swap channels, read documentation for details). Some debuging
stuff added (to find devide error problem). Sample rate is now 6000 (it is
enought) and this enlarge the main buffer to 1min. Also now SB card must be
on DMA 1 (becouse some SB programming problems).
This is the last version before the Persaids. Tomorrow (10.08) I will go to
adriatic coast and will not read email/mails until 20.08, sri. Good luck and
hope there will be no problems.
> ...
If you want to know when new version is available on my homepage send me
email with your email address, and every time new version is out, you will
recieve email.
> ...
73 de Tihomir, 9A4GL@9A0BBS.HRV.EU
email: Tihomir, 9A4GL
Home Page
(VHF) DK3XT de DB0GE>
To: VHF@w6yx.stanford.edu
Cc: meteor-scatter@qsl.net
From: K0FF
Subject: M/S operating practices: Random VS Skeds
Date: Fri, 08 Aug 97 18:13:03 CDT
Random M/S contacts are very different from trying to work a schedule.
During a sked, you go at it with a single station, back and forth over =
and over, getting bits and pieces and fragments. This is why the S-2/roge=
r S-2/roger-roger/73 thing works there.
On a random contact, I have found the signal levels to be extrodinarily =
high, but usually quite brief. I see no reason to treat such a QSO any =
differently than I would any other plain-language exchange.
To be a valid QSO on any band, you should exchange 2 items of information=
. Call letters =3D the first item, and GRID SQUARE is the second item on =
VHF. (ON HF everyone gives a 59 or 599 regardless of signal strength, whi=
ch to me is kinda phoney)
I think this is quite adequate for 2 meter random QSOs, especially since =
you don't already know the other guy's call letter.
I know that many Old Timers insist on the long "S-2" version, even on ran=
doms, but I submit this is wastefull of time and effort. Anyhow, how are =
you legitimatly exchanging any "information" if you always give an S2? =
Not all burns are 2 seconds long. I have never heard anyone give other =
reports than S2, any more than anyone gave the VK0 operation a 57 or 339 =
on HF! Also don't forget there may be another station waiting to tail-end=
you, so wouldn't it be better, when conditions allow, to make a quick =
clean QSO and then be silent in favor of someone less favored at the mome=
nt?
This is not a discussion, but an explanation of my operating practice in =
this special circumstance.
Skeds will be conducted traditionally.
Hope to work lots of Ya' this time.
73 GEO (K0FF) (573-221-3418 call anytime!)
From: Brian, N5BA
To: k7ja@juno.com
CC: vhf@w6yx.stanford.edu, vhf-dx-discuss@blacksheep.org
Subject: High Speed CW MS
Chip wrote:
Last year, I hear several very, very loud bursts, but activity was poor.
Come on, guys: crank up those keyers and meet me on 144.100 (on your
FT-736R, this means you set it to "144.100.7" MHz).
--------------
OK...If I say I'll meet you on 14.027, on my Yaesu HF rig I tune
to 14.027. On VHF if I say I'll meet you on 144.127 I have to
tune my rig to 144.127.7?????
I understand going to 144.200.7 when I hear a SSB stn who is weak
and I want to get his attention, but if I'm setting up a CW sked,
why do I have to dither the freq????
This is especially important if I am trying European style High
Speed CW...What freq am I supposed to tune in on my FT-736 R on a
CW sked??? 144.100 or 144.100.7???
Answers from both sides of the pond are appreciated.
Brian
N5BA
EL29fx
Date: Sat, 09 Aug 1997 15:39:10 +0100
To: meteor-scatter@qsl.net, wsvhf@qsl.net, vhf@w6yx.stanford.edu
From: Steve, Ko0U
Subject: Wanted: 144/432 MS Skeds
Looking for more 144 and 432 MS skeds; CW or voice on 144, CW only on 432.
I'll sked even if I already have your grid, state, or country; or even if we
worked yesterday, the day before, and every day of the past week. TNX!
Steve, Ko0U/1 FN42dg
Date: Sat, 09 Aug 1997 16:15:59 +0100
To: vhf@w6yx.stanford.edu
From: Steve, Ko0u
Subject: Re: High Speed CW MS
At 02:54 PM 08/09/97 -0700, Brian, N5BA, wrote:
>Chip, K7CA, wrote:
>
>Last year, I hear several very, very loud bursts, but activity was poor.
>Come on, guys: crank up those keyers and meet me on 144.100 (on your
>FT-736R, this means you set it to "144.100.7" MHz).
>--------------
>
>OK...If I say I'll meet you on 14.027, on my Yaesu HF rig I tune
>to 14.027. On VHF if I say I'll meet you on 144.127 I have to
>tune my rig to 144.127.7?????
Here's the problem, Brian: the Yaesu radios "correct" the frequency readout
so it indicates the zero-beat frequency. The Kenwood radios do not. If I
transmit CW on 144.1000 with my TR-9130, my actual zero-beat frequency will
be off by as much as the difference between the CW and USB BFO oscillator
crystal frequencies, which is usually about what the CW sidetone pitch is.
If you tuned your own TR-9130 to 144.1000, you would hear me with about a
800 Hz note.
But if you are using a Yaesu, then you must set your dial about 700 Hz
higher because the radio's frequency display is corrected to the actual
zerobeat frequency, not the frequency at which you will hear my note at
about 700 Hz.
Who knows what the Icoms do...
So, if you tuned your Yaesu to 144.1000 and I have my Kenwood set to
144.1000 also, and I am transmitting CW, then you will not hear me because
your Yaesu will be tuned to my zerobeat frequency. So you have to offset
your tuning to whatever note pitch you want, or 144.1007, if you want to
hear me at 700 Hz pitch.
At least, I THINK this is how it works...Why do they do things different?
Why not? If ALL radios did the same thing all the time, we'd only need ONE
manufacturer of radio and ONE model of radio...and we can't have that now,
can we? And it would likely be the most obnoxious and uncaring manufacturer,
and the absolute worst radio, that would be available, of course. Naturally!
That's how it works!
73, Steve Ko0U/1
HR>
Date: Sat, 09 Aug 1997 11:12:57 -0700
From: Wayne, WB9WLR
To: Steve Harrison
CC: vhf@w6yx.stanford.edu
Subject: Re: High Speed CW MS
Steve Harrison wrote:
Here's the problem, Brian: the Yaesu radios "correct" the frequency
readout so it indicates the zero-beat frequency. The Kenwood radios
do not. If I transmit CW on 144.1000 with my TR-9130, my actual zero
beat frequency will be off by as much as the difference between the
? CW and USB BFO oscillator crystal frequencies, which is usually about
what the CW sidetone pitch is.
If you tuned your own TR-9130 to 144.1000, you would hear me with
about a 800 Hz note.
But if you are using a Yaesu, then you must set your dial about 700 Hz
higher because the radio's frequency display is corrected to the
actual zerobeat frequency, not the frequency at which you will hear
my note at about 700 Hz.
Hiya, Steve.
I would disagree with your frequency setting scheme, for
the following reason. If your sched is on 144.120, and you set a Yazoo
to 144.120.7, you're actually OPERATING on 144.127.7. I would suggest
that the Yazoo provides ACCURATE operating frequency information, the
Kenworth does not. Think about it.
Wanna go for a ride in the Ortega pass??
- 73 -
Wayne
WB6WLR
To: vhf@w6yx.stanford.edu
Subject: Scatter sequence
Date: 9 Aug 97 13:26
From: Russell, K2TXB
Since there seems to be a lot of newer Hams who are going to be
running skeds this year could one of the more experienced hams out there
explain proper sequencing procedures for ALL of us.
A number of years ago the complete procedures were printed up in QST, in
the vhf column. I don't have the reference now, but maybe someone else
knows the issue and can post it.
I'll take a stab at it from memory:
First for schedules (as opposed to random).
1. Calling sequences are 15 seconds, twice a minute. The western most
station transmits on the first and third 15 second segment.
2. Until something is heard, only callsigns are transmitted. Once you
start hearing pings it is acceptable to transmit an S1 report, but
modern practice is to eliminate the S1 report and continue with just
calls. This reduces the likelihood of confusing the other operator.
3. Once you have heard a complete set of calls (both yours and his), you
can start sending an S2 report. Here is where it gets a bit complicated.
If you only heard calls, then you continue to send calls with the S2
report. But, if you also heard an S2 report, you can dispense with the
calls and instead send only RS2 (or roger S2 on ssb).
4. Once you start sending R's the QSO is still not complete until you
also hear R's. Hearing an RS2 means you have heard R's.
5. If you hear R's before you start sending them, it is a good idea to
continue sending your R's for a few sequences to be sure the other
station gets them. If you then hear RRR or 73 from the other station
then you will know he has it all and you are done. But it is not
necessary for you to hear the RRR or 73. As long as the other guy
actually did hear your R's, you are done.
6. Conversely, if you have been sending RS2, and you then hear R's, it
is a good idea to send a sequence or two of 73 or RRR, to let the other
guy know you are done. Again it is not necessary, just polite.
The important thing is not to start sending reports until you have heard
both calls, and not to start sending R's until you have heard both calls
AND the report.
Note that some operators prefer to substitute the grid square for the S2
report. This is OK, but needlessly complicates things for schedules
where the grid is probably known anyway. For random contacts it makes
more sense.
It is not necessary to hear everything in one burst, or even during one
transmission. For instance if I were to hear K2 in one burst and TXB
during another (even previous) burst, I have heard my call. If I hear
S2 before I hear all of the calls, I've still heard the S2, and don't
have to hear it again after I get the calls.
If you hear the other station stop transmitting while a burn is in
progress, it is good to quickly send everything he needs to hear, and
then break, since the burn may still be in progress and you might
complete the qso immediately, If you don't hear anything when you
break, go right back to the normal 15 second sequence. Also, if the
'rocks are running good' you might try a short break at the middle point
of the 15 second transmit sequence to speed up the contact.
For random contacts on or about the calling frequency, the likelihood
that you'll have the frequency to yourself long enough to complete a qso
lasting more than 30 seconds or so, is quite small. Therefore once a
burn starts you try to squeeze everything into it and complete. But you
still have to exchange complete calls, reports (or grid), and rogers to
make it a valid qso.
But in random operation it is still important to maintain the 15 second
sequences when you are not in an actual qso, western stations
maintaining the first and third segment. The reason for this is that
you will reduce the amount of qrm you are causing to other stations who
are also using the frequency for MS. And, of course since they notice
you being polite, they will reciprocate :) I've seen, and heard, some
stations advocating using a 5 second on and off sequence. This may work
fine for that station, but it is a very selfish way to use the calling
frequency. And imagine the mess if everyone did it at once! Try not to
transmit during the listen period. Your neighboor may be getting his
rogers right when you start sending.
Well, I hope this covers all bases. Please excuse me if I rambled a
bit, I'm hurrying because I'm getting ready to go back up to FN02 for
the rest of the summer (and through the September contest), and need to
tear down the computers and ham gear to pack in the car. See you all
via the Perseids, and in September.
73, Russ K2TXB
Russell C. Pillsbury russk2@cyberenet.net
08/09/97 13:26
Running NT 4.0 and NT 3.51 Server
Date: 9 Aug 97 13:26
From: Russell, K2TXB
This is especially important if I am trying European style High
Speed CW...What freq am I supposed to tune in on my FT-736 R on a
CW sked??? 144.100 or 144.100.7???
Answers from both sides of the pond are appreciated. <<
If calling cq on the calling freq I'd use 144.2007 so as to enable guys
who are in ssb mode to hear me. But for cw if a sked is set for 144.1,
that means the carrier freq is 144.1, a freq counter would read 144.1 on
your transmitted signal, etc. So 144.1 is where I'd set the dial.
73, Russ K2TXB
Russell C. Pillsbury russk2@cyberenet.net
08/09/97 13:26
Running NT 4.0 and NT 3.51 Server
From: Jay, K0GU
Subject: High Speed CW MS tests
To: vhf@w6yx.stanford.edu, wsvhf@qsl.net
Date: Sat, 9 Aug 1997 12:39:04 -0700 (MDT)
To those interested in high speed CW Ms testing:
W8WN sent out a message saying he would be QRV this weekend. I also
will be on at about the same times but will transmit on the odd minutes.
I will be on tonight (Sunday UTC) from 01z to 02z and tomorrow night
(Monday UTC) from 01z to 02z on 144.100. I'll be sending at 99 wpm and
using the same CQ format suggested by W8WN (CQ plus letter to indicate
RX frequency). Will beam from NE through SE. I'll be happy to try to the
west (or any other direction) after 02z if I get an indication, in the
next few hours, that someone is listening (Sorry, I won't see any Email
sent after 21z today until Monday). RX reports appreciated.
73, Jay K0GU DN70mq jayk@fc.hp.com 970 568-7813
FT-1000D DEM 144-28 8877
4x17B2 SSB preamp
Date: Sun, 10 Aug 1997 23:06:04 +0100
To: vhf@w6yx.stanford.edu, wsvhf@qsl.net, meteor-scatter@qsl.net
From: Shelbi, W8WN
Comments: Rein, W6/PA0ZN
Top Page
08/06/97