Subject: NET NOTES 14 January 2001
From: K1RQG
Most recent Schedules can be found here
Also submit your sked requests to Joe:
Joe, K1RQG
NET BEGINS
CHECK OUT SKEDS BELOW. GET BACK TO ME WITH ANY CHANGES..
Please note:
There is discussion about the EME procedures. Especially regarding
how to set your xmit freq. See paragraph 5 of G3SEK notes and send your
comments to Ian.. <[email protected]> .. This procedure is of prime
importance to the scheduled stations and newcomers.
I need to know the QRV status of NL7F, WA9FWD, N7AM, GW3XYW ..
Joe
EME schedules, last update 14 Jan 2001, 13:45
(432 MHz listed only)
Skeds for FEB 3
Time 432.040 432.045
0400z KL7HFQ-K5WXN
0430z KL7HFQ-WB0GGM VK4AFL-W1ZX
0500z JH1XUJ-WB0GGM KL7HFQ-K4EME
0530z JA5NNS-WB0GGM AL7OB -K4EME
1715z N1BUG -PA3CSG
2200z WB0GGM-UA6LGH
2230z WB0GGM-OH2DG
2300z WB0GGM-G4ERG
2330z WB0GGM-ON5OF
Skeds for FEB 4
Time 432.045
0530z VK4AFL-W1ZX
EME schedules, last update 14 Jan 2001, 13:45
(1296 MHz listed only)
Skeds for FEB 3
Time 1296.040 1296.050
0000z K9BCT -WA1JOF
0030z WA4OFS-WA1JOF
0100z WA9OUU-WA1JOF
0130z W7BBM -WA1JOF
0200z VE6NA -WA1JOF
0230z VE6TA -WA9OUU
1900z WA1JOF-IK2MMB
1930z WA1JOF-LX1DB
2000z WA1JOF-F5PAU
2030z WA1JOF-I0UGB
2100z WA1JOF-GW3XYW
2130z WA1JOF-EA3UM
2200z WA1JOF-ON5RR VE6TA -HA5SHF
2230z VE6TA -VE6NA
Skeds for FEB 4
Time 1296.050
2100z DJ5MN -WA1JOF
2130z WA8WZG-DJ5MN
2200z WA8WZG-WA1JOF
EME schedules, last update 14 Jan 2001, 13:45
(2304 MHz listed only)
Skeds for FEB 3
Time 2304.050
0200z WA6PY -W5LUA
0230z WA6PY -W7GBI
0500z JA4BLC-WA6PY
0530z JA7BMB-WA6PY
2230z WA6PY -OE9XXI
2300z WA6PY -OE9ERC
2330z WA6PY -LX1DB
Skeds for FEB 4
Time 2304.050
0000z WA6PY -G3LTF
0030z WA6PY -DL6LAU
AA5C: 3cm .. see email report below..
W2UHI: all is well.. a thaw for 4 days.. looking forward to next activity
weekend..
VE1ALQ: nothing new.. just pulled the YL-1050 cavity out of cabinet and
found quite a bit of dust build-up and doing some cleaning.. all
is well..
W5AA: VARO ...
OK1MVD: no e-mail from W5AA for VARO..
K0YW: tnx to W7SZ for QSL card.. any word from F1PYR ?.. any contact
with LU8EDR or PY5ZBU ?... is now using air filter (round 9" dia
by 9" high) used on race cars, M1 tanks etc.. contact Bruce for
more info..
K5JL: suggests Bruce send note to Al for NL for filter info. was not
on last night.. TI2NA working toward 23cm.. TI5KD may be on
on 70cm EME..
WB0GGM: looking for skeds .. UA6LGH, ON5OF, OH2DG, G4ERG, JA5NNS, JH1XUJ,
KL7HFQ.. *******
W7SZ: lot of wind.. minimal EME work.. breaking news.. completed with W7LHL
10' dish 50w on FSK on 23cm EME .. write-up will be in Feb NL.. plans
on working towards 10ghz..
KD4LT: no traffic.. will be on next activity weekend..
K4EME: new QSLs on order.. will be ready for skeds next weekend .. needs
AL7OB & KL7HFQ and others on 70cm EME .. *******
WA1JOF: needs skeds with IK2MMB, LX1DB, F5PAU, I0UGB, GW3XYW, EA3UM, ON5RR,
VE6NA, WA9OUU, WA9FWD, K9ZZH, K9BCT, WA4OFS, (N7AM), W7BBM, NL7F,
*******
W1ZX/M: no traffic..
N2IQ: quiet on 70cm & 23cm this week.. made a partial on 10ghz .. heard
W5LUA "O" copy.. 7' Horn .. (7' apeture and 17' long)
W4RDI: not too much going on .. nothing going on.. clearing out some of
the Palm trees..
NC1I: not much to report.. worked 20+ stations last weekend .. good time..
been a while since real activity.. did get on this weekend.. heard
KL7HFQ on last weekend and this weekend.. pretty quiet on 70cm..
worked DF3RU..
K2DH: not much to report.. went out to work on the dish .. az drive problems
again.. did not make it on last night for this reason.. assuming
Dave can get az drive working , will be on next weekend..
KA0Y: wx terrible.. doing nothing ... looking for NL7F sked ********
K5WXN: was on last night .. not Friday night (High winds).. little
activity.. listened for KL7HFQ.. OE3JPC worked on 70cm for
a new. condx seemed to be good last night, except for very
little activity.. needs KL7HFQ sked ********
WA9OUU: first time on 20 meters.. now hearing echoes on 13cm..
[email protected] @@@@@@
4.4 mtr dish 800w .. needs 15 deg to East .. HB 8x7289 ...
on 13cm 100w to the feed.. GS9B.. ####### only 2320 rcv
available in during next week in the mornings..
currently writing articles for Midwest VHF/UHF group and now
playing with GS15 at 23cm..
VE6TA: needs sked with WA9OUU 23cm .. ******* Was on last night for an
hour or so .. no activty.. working on 4 tube amp now..
W4AD: heard nil from W7QX last night.. cancel any skeds till az rotor
is repaired..
W7QX: heard W4AD "M" copy all the time.. W4AD was on
FOR SALE: EW-90 waveguide, various lengths and some connectors .. N2IQ ..
FOR G3SEK: a discussion about paragraph 5, setting your transmit frequency,
and much discussion as to what to do..
VE4MA: comments about doppler and sked freqs on 10ghz and above..
K1FO: still feels that the old standard of each station xmits on assigned
sked freq is the least confusing and yields the least amount of
freq error..
WA4YGG: getting ready for 23cm .. looking for info on feeds.. Steve..
EM85..
VE7BQH: 10:14 AM 1/14/01
======================================================================
EME OPERATING PROCEDURES FOR 432 AND ABOVE BY G3SEK
1. Why? EME signals are often weak and fading, so we cannot always hear
each other. To help us to make more QSOs, we need some agreed operating
proc.
2. Minimum QSO: The definition of a minimum valid QSO is that both
stations have copied all of the following: 1.Both callsigns from the other
station, 2.Signal report from the other station (or some other previously
unknown piece of information, e.g. the other station's Locator grid), 3. R
from the other station, to acknowledge complete copy of 1 and 2.
3. CW speeds: The recommended sending speed on 432 MHz and above is a
letter speed of 15-20 words/minute, but with extra space between letters
so the word speed is only 12-15 words/minute. This helps to prevent
individual letters of Morse code being broken up by rapid libration
fading. Leave clear pauses between letters, and also between words or
callsigns. Do not change speed. Do not send very slowly - it is harder to
copy!
4. Signal Reports: On EME, do not send a signal report until you have
copied both callsigns completely! Valid signal reports for 432MHz and
above are: T (Not used any more) [Proposed change - T should be removed
from the standard procedure. Almost nobody uses it, and it is too easy to
confuse with M or O.], M Very weak, marginal copy but complete (M is valid
for a QSO on 432MHz and above), O Weak, difficult copy but complete. Leave
clear pauses between letters, so there is no possibility of mistaking M
and O. RST - not the same as on HF. Typical EME RST reports include: 339
Stronger than O but still quite weak and difficult copy; 449 Stronger than
339, almost complete copy; 559 Very strong (for an EME signal), complete
copy. Other combinations are of course possible, for example: 549 Complete
copy but not "S5", 349 "S4" but difficult to copy, etc... Remember that
RST is more difficult to copy than M or O, so using RST can be a risk in
skeds and initial QSOs. Some stations do not like to use RST in contests
because it takes more time.
5. Skeds: 5.1 Skeds Coordination Service - Most beginners start with
skeds, and there is a highly effective world-wide skeds coordination
service to arrange skeds for people who want to work new stations. If you
want skeds, contact one of the skeds coordinators via the 14.345 MHz EME
Net or at the e-mail addresses at the top of every Newsletter. You can of
course arrange your own skeds, but do not use frequencies on or below
432.070 MHz and 1296.070 MHz. Reason: these frequencies are used for
coordinated skeds, and there may be extra skeds that are not in the
Newsletter. 5.2 Frequency - The first-named station in the skeds list
transmits first, exactly on the agreed frequency for the sked. The second-
named station also transmits exactly on the agreed frequency for the sked.
This is the existing procedure. It is simple, and it works well enough.
The only possible error for the transmitting station is in setting the
frequency accurately. The receiving station tunes to compensate for
Doppler shift, and for frequency errors at both stations. Another proposal
is that the transmitting station compensates for Doppler shift by pre-
calculation. This is much more, with the possibility of making mistakes.
This is a big disadvantage for beginners on EME, who are the people who
make most use of skeds. The receiving station still has to tune to
compensate for the frequency errors at both stations, so little is gained.
The increased risks and the extra complication seem to be greater than the
possible advantages.] 5.3 Time periods - Time periods are used for skeds,
because the other station may not be copying at the end of a transmission,
and may not know to change over. For skeds on 432 MHz and above, time
periods are 2.5 minutes for each transmission, synchronized to UTC (+/- 2
sec maximum error). 5.4 Example sked QSO - Skeds list says: 432.045 2300
DL9KR- K2UYH; DL9KR sets his TX frequency to exactly 432.045 (using an
external frequency counter, not the frequency display on the rig). K2UYH
does the same. Initial transmission Exactly at 2300:00 UTC, DL9KR starts
to transmit: K2UYH DE DL9KR (pause) K2UYH DE DL9KR K2UYH... This continues
until 2302:30 ... DE DL9KR K. Further transmissions - procedure depends on
what has been copied. ? Copied nothing at all, or not copied both
callsigns complete then First 2 minutes - transmit both callsigns. Last 30
seconds - do not transmit! ? Copied both callsigns COMPLETE, but no report
then First 2 minutes - transmit both callsigns. Last 30 seconds - transmit
report: M M M = difficult copy, or O O O = easier copy. Do not change
report during a sked period. Do not mix report with callsigns. Do not use
RST reports in initial skeds, unless you are very confident about signal
strengths in both directions. ? Copied both callsigns + report Full 2.5
minutes then transmit only MRMR or OROR ? Copied both callsigns + report
+ R confirmation Full 2.5 minutes then transmit only R R R. ? Copied R R R
If you have copied one R from the R R R... transmission, then the QSO is
now complete. To confirm this to the other station, it is usual to
transmit R R R, 73 TNX GL SK etc. 5.5 Incomplete sked QSOs - Coordinated
skeds are of 30 minutes duration. If the QSO is incomplete at the end of
the 30-minute sked period, you should generally abandon the sked - someone
else will probably need the frequency. 'Private' skeds may continue
longer, but should not be on frequencies used for coordinated skeds.
6. Random QSOs - Most QSOs on 432MHz and 1296MHz are 'random' - not by
skeds. Usually there are no fixed time periods because both stations can
hear when to change from RX to TX. The basic format for a random QSO is
the same as for a sked, except that one station has either called CQ, or
has signed out of a previous QSO on 'his' frequency. Example K1RQG has
called CQ. DL4EBY is going to call him for a random QSO. 6.1 Calling a
station - Frequency If you have set your RX clarifier (RIT) so that your
echoes are at the same audio pitch as K1RQG's signal, then he will hear
you on exactly the same frequency as his own echoes. You may not want to
call exactly on that echo frequency, because it may be the frequency of a
pile-up! Sending callsigns - Send both callsigns - remember that both
stations must copy both callsigns for a valid QSO. However, it may be
useful to give more repeats of your own callsign to help K1RQG to identify
it, e.g: K1RQG DE DL4EBY DL4EBY... The optimum format and length of the
call is a matter of operating skill and judgement. 6.2 Answering a call -
If you copy both callsigns, Reply with both callsigns, with extra repeats
of the calling station, e.g: DL4EBY DL4EBY DE K1RQG... The other station
has almost certainly copied your callsign, but he must copy his own
callsign from you. Then send a report. The rest of the QSO continues as
described in the sked example above. If you have not copied either
callsign for sure Transmit QRZ? QRZ? QRZ? DE... several times. DL4EBY
should reply with both callsigns as above, for 1 minute or more. If K1RQG
replies with QRZ? again, call him for even longer! Note to other stations:
QRZ? is NOT an invitation to break in! If you have copied your own
callsign Often you copy your own callsign easily, but have difficulty in
identifying the unknown callsign. You have two choices: a) Call QRZ? as
above. b) Send Y Y Y Y Y Y Y DE K1RQG... Y Y Y means "I need Your
callsign only. I have already copied my own callsign." DL4EBY should reply
with his own callsign only, for 1 minute or more. After a second Y Y Y,
call for even longer! [YYY is very effective, but it needs more publicity!
Zdenek has proposed to repeat each letter many times, e.g. "OOOOO KKKKK
11111 DDDDD FFFFF CCCCC". When this pattern is repeated, it could be
difficult to understand where the callsign begins and ends. Please
discuss!]
7. ARRL non-EME contest procedure: ARRL VHF/UHF contests use large grid
squares (e.g. FN32) as multipliers, but do not require exchange of a
signal report. On EME, the procedure is the same as described above, but
send your grid square instead of the report. G G G means "I need your grid
square for ARRL contest."
8. Polarization switching / rotation: The EME Directory lists stations
with linear rotatable (rot.) and linear switchable (h/v) polarisation
capability. If only one station can change polarization, he should
optimize polarizations in both periods, and should transmit second in
skeds. If both stations can change polarization, both stations should
transmit horizontal and switch/rotate to receive. [No change above.
Suggest we drop the experimental procedure for polarization ("If you copy
P P P... change your TX polarization back to an earlier setting.") because
there has been no interest.]
9. Breaking the rules! For a newcomer, it often seems that people do not
use these procedures - but this is only partly true. Stations who have
worked each other many times, and have strong signals, may decide to have
a more 'normal' amateur radio QSO without using these special EME
procedures. Even so, the basic QSO format is still there as a framework.
If signals become difficult to read, good EME operators should move back
toward the standard procedures, i.e., Reduce high speeds, send more
clearly, Use M/O reports instead of RST, Do not change frequency or TX
polarization, Change back to standard TX/RX periods synchronized to UTC.
========================================================================
This year the SSB contest starts on 3 Feb at 1100 and continues to 4 Feb at
1200. (The intention is to give everyone one common moon pass.)
Operation is on 1296 only. Scoring will be contact points times number of
Grid Sectors (IO, JM, FN, ...). SSB to SSB contacts will count as 2 points.
SSB to CW (or CW to SSB) 1 point. The exchange is your Grid Sector.
EUROPEAN WORLD-WIDE EME CONTEST 2001
The date for the Eur EME Contest have been set as 31 MARCH/01 APRIL for 432
MHz, 2.3 GHz to 5.7 GHz operation, and 28/29 APRIL for 144
MHz, 1.3 GHz and 10 GHz activity.
========================================================================
Subj: Net Input for Saturday January 13
Date: 1/13/01 9:30:17 AM Eastern Standard Time
From: [email protected] (Greg McIntire)
To: [email protected]
Hi Joe and all on the net. Worked HB9BHU on 3 cm at 0700Z this morning for
a new initial. -O- copy both directions and conditions seemed quite
good. Cold but the weather cooperated enough to keep the TWTA dry this
time. Rain expected today. 73 to all. de Greg, AA5C.
=========================================================================
Subj: N1BUG directory info
Date: 1/13/01 11:15:09 AM Eastern Standard Time
From: [email protected] (Paul Kelley)
Reply-to: [email protected]
To: [email protected]
Hi Joe...
Here is my info for the directory.
N1BUG
FN55mf
432: 1x22, no elevation, 550W
Paul Kelley #########
PO Box 16
Dover-Foxcroft, ME 04426
Phone (207) 943-7484
73,
Paul
============================================================================
To ALL EME stations:
Last year I did a survey of the 2 Meter EME group to determine a consensus
for 2000 ARRL International EME Contest dates. Many EME people other than
the 2M Meter EME group sent me their input which I also included. Joe, K1RQG
ultimately sent me any separate input he had for the 70CM and up group. I
also included this information. I compiled the survey and sent it to Joel,
W5ZN ARRL 1st Vice President. He in turn forwarded it to the ARRL Contest
group for their consideration. The clear consensus from the survey were the
dates chosen by the ARRL Contest group.
After discussion with Ian, G3SEK, Steve, K1FO and Joel, W5ZN, I offered to
do the survey again for 2001.
As is typical, you again will have to consider weather, other contests and
reasonable declination.
The practical dates appear to be:
October 13/14
November 10/11
Other dates that may be considered are October 5/7 and November 3/4 BUT they
are the dates for the European Tropo Contests. Remember, many European
stations will be unable to operate Contest EME on these dates due to the
high QRM from the Tropo contest. Traditionally we have stayed clear of these
dates.
Although the dates are not selected at this time, the Italian EME contest is
always held in September.
You are welcome to submit any two weekends you wish, I will compile and
publish the results on MOON-NET as I did last year as well as forward the
results to Joel, W5ZN.
Please send my your choices NOT LATER than Feb 12,2001
73,
Lionel, VE7BQH
[email protected]
============================================================================
Subj: 3 cm EME QSO
Date: 1/14/01 1:41:26 AM Eastern Standard Time
From: [email protected] (Greg McIntire)
To: [email protected]
Hello Joe and all-I won't be at home during net time but wanted to forward
that I worked OK1UWA on 3 cm this morning. Nice signals both ways although
conditions didn't seem as good as last night. Always looking for new
stations to work on 10 GHz. Best to all. 73, Greg, AA5C
=============================================================================
Subj: Re: NET NOTES JAN 13, 2000
Date: 1/14/01 4:07:44 AM Eastern Standard Time
From: [email protected] (Melum)
To: [email protected]
Hi Joe,
Winds gusting to 60 mph all day. Could not get on at all. I plan to be
very active on 432 for next SW and I am wide open for any sked requests. I
plan to work on optimization for the next 3 weeks. Looking for 1296 HPA
and power supply. Also looking for HPA and preamp for 220.
Tnx & 73
Mike, AL7OB BP51dc http://www.customcpu.com/al7ob
432 EME - FT-736; FT-767; 9.2 Meter; DEM 0.4dB; 700 WATTS
==========================================================================
Subj: Re: NET NOTES JAN 13, 2000
Date: 1/14/01 6:24:06 AM Eastern Standard Time
From: [email protected] (Johannes OE3JPC)
To: [email protected]
Hallo Joe,
hny 2001!
Could you please change my e-mail address in your "net notes"-list?
[email protected] @@@@@@
The address in your list ([email protected]) still works but I often have
problems with that provider.
73 de Johannes OE3JPC
===========================================================================
Subj: stuff for eme notes
Date: 1/14/01 9:43:16 AM Eastern Standard Time
From: [email protected] (Tom Whitted)
To: [email protected]
Good Morning Joe and all, Just to let you know that I have been busy with
the TROPO station trying to get it ready for the Jan. VHF contest. Much
work to do and with winter weather slow progress!! HiHi... I will be on for
next sked weekend and would like a sked with Dj5mn and Wa1jof on 23cm.
Thanks and Happy New year to all of my EME friends.
73's
Tom Whitted
WA8WZG 50Mhz - 47Ghz. From En81OM
http://www.wa8wzg.com
============================================================================
Subj: de ZS6AXT
Date: 1/14/01 12:01:58 PM Eastern Standard Time
From: [email protected] (Ivo Chladek)
To: [email protected] (K1RQG)
Hi Joe,
I was bit amazed with the reported QSB on my signals by MMB; I wonder
: My dish in a stronger winds may move quite a bit despite the
mechanism I have for eliminating it (a counterweight for Azimuth).
However, in stronger winds it is not good enough. I do not have such
experience with Eu stations, in general. Did anybody else observe this
?
73, Ivo
=============================================================================
NET ENDS
Return