|
Quick links
This page covers my main operating interests ... at the moment ....
DXing
I've been licenced since I was at school thanks to the electronics club run by physics teacher
Graham G4AVV and his student Colin G4CWH, among others. Graham and Colin taught a few of
us the theory, and in turn when they left we taught boys in the years below us. I taught myself
CW straight away with a bit of a break to complete my O-levels and got my pass on May 2nd 1979
(more than 30 years ago!). My call G4iFB came through shortly after. Colin, if you're reading this,
thanks for threatening to do nasty things to my insides if I got a Class B VHF licence. You were
right. HF is for grown ups and CW is definitely the civilised mode!
Outside of contests, I enjoy HF DXing whenever I have time for radio. Mostly that means around
ZL dawn (sometimes) and dusk (most evenings) on the low bands (30-40-80m, with no antenna
for 160m at the moment) and occasionally the odd spare hour in the middle of the day on HF since
my home office is my shack, conveniently enough. I’ve caught the odd high-band opening
including a solid long path run into Europe on 15m in May 2009 that someone kindly recorded and
published on YouTube video to show off their fancy instant-reversal Steppir beam (nice!).
After ~4 years on the air as ZL2iFB, my QSO totals and DXCC scores are creeping up and I have
been awarded the basic mixed mode and CW DXCCs, plus single band DXCCs for 20, 30 and 40m
with 80m just one LoTW confirmation away (I’m already there with some to spare if I count QSL
cards). There’s still a lot of fun and hard work ahead before I reach Honor Roll but here are my
DXCC counts as of February 10th including QSL cards and LoTW confirmations received:
|
|
Wkd
|
QSLd
|
|
CW
|
265
|
238
|
|
SSB
|
148
|
85
|
|
Data
|
61
|
30
|
|
Mixed
|
270
|
242
|
|
I’m making about 4-5,000 regular DXing QSOs per year as ZL2iFB, plus another couple of
thousand contest QSOs as ZM4G, ZM2M etc., with 89% of them on CW.
This is my DXCC awards table on LoTW (ignoring those additional QSL cards):
Here’s my mixed-mode DXCC breakdown by bands:
|
Band
|
160m
|
80m
|
40m
|
30m
|
20m
|
17m
|
15m
|
12m
|
10m
|
ALL
|
|
Worked
|
33
|
154
|
225
|
197
|
233
|
163
|
150
|
35
|
59
|
270
|
|
Confirmed
|
17
|
118
|
200
|
140
|
152
|
99
|
99
|
22
|
35
|
242
|
|
A lovely chat on 30m with Ron WA2EKW in Mountain, North Dakota, meant I have worked all the
states in USA from NZ. Under the official WAS rules, however, QSOs made from my previous
QTHs in ZL don’t count any more so I’m hunting once more for QSOs with all US states from
Hawkes Bay ...
Back to quick links
HF beacons
I often monitor the beacons on 10m during the ZL daytime while working (one of many benefits of
working from home). Despite the dearth of sunspots, I’ve heard over sixty 10m beacons in the
past year, most of them running QRP to verticals. That link takes you to my online beacon
log/database, courtesy of Google Docs: here’s a static screenprint from the database:
More comprehensive beacon lists are maintained by G3USF and WJ5O. I’m disappointed that not
all beacon keepers publish information about their beacons on the Internet, even the basics such as
location, power and antenna. Why they would go to the trouble of maintaining a beacon and yet
not publish this information puzzles me.
The NCDXF beacons are a useful guide to worldwide openings on 10 thru 20m, with the benefit
that you can monitor a single frequency on each band to hear when various DX paths open/close.
Individual beacons in the chain occasionally drop offline but, on the whole, they have been
remarkably reliable. I urge regular users to donate to the NCDXF beacon fund.
Beaconbytes
: here’s my growing collection of MP3 soundbytes of the 10m beacons:
I’ve been experimenting with FreqPad, a Logger32 add-on to memorise and recall 10m beacon
frequencies. The K3’s memories are probably more useful on the whole (e.g. it’s easier to step
through the beacon frequencies for a quick listen) although it would be helpful if the memory
channel text field was long enough for the entire callsign (longer text would just have to scroll
horizontally, like the boot/welcome message).
Back to quick links
CW
I have been using CW almost exclusively since I was first licensed in 1979 and discovered that 100
watts or less goes much further on the key than on the mic. Even with QRO I still love CW,
perhaps because CW is a more universal language than SSB. Nearly everything gets abbreviated -
whether you're a G or a JA, "73" sounds much the same on the key though it's quite different in
English and Japanese! It's much more bandwidth efficient than SSB and much easier to filter out
QRM. OK OK so the digital modes are even better but then the computer does all the work, and
my hobby is not (just) about operating computer keyboards.
If, like me, you thought Morse Code was invented by Samuel Morse, check out what the History
Channel has to say about it.
International Morse Code, plus various procedural aspects of sending and receiving telegrams, are
specified by ITU-R recommendation M.1677. If you care about CW, please pay attention to the
prosigns (such as ...-.- “end of work”) that should be run together as
one continuous character
,
not separate letters (...-.- might be remembered and written as SK or VA but should not be that
way). Same applies to -...-.- “break” .-.-. “end of message” -.--. “go ahead named station
only” -...- “hyphen or break” and so on. By the way, I can’t see much point in learning and using
the new Morse character for the @ symbol in email addresses when “at” works perfectly well and
is universally understood. Likewise “dotcom” or “dotnet” or whatever are self-evident whereas the
dot or fullstop character is not so commonly used by hams.
Back to quick links
WSPRnet
WSPRnet (“Weak Signal Propagation Reporting Network”) is an HF propagation monitoring system
on WSPR, an experimental weak-signal data mode that uses digital audio processing on PC
soundcards to encode and decode narrowband (just 6 Hz!) QRP data transmissions. Each
transmission takes 2 minutes to transmit the station’s callsign, locator and power. QRP and QRPp
signals are routinely received over thousands of kilometers when the bands are open. IN the best
amateur tradition, the software was written and released free-of-charge by K1JT. The really neat
thing about it is that the program automatically uploads details of transmitters and receivers to a website where the information is listed and mapped in near-real-time, so you can see at a glance
where in the world your QRP signals are currently being heard on whatever band you are using.
Here’s a screenshot (with some notes for new WSPR users since the help file is rather basic):

WSPR measures transmitter power in dBm rather than milliwatts or watts, so here’s a conversion
chart to make things easier:
The chart is a simple Excel
spreadsheet. By all means
download it if you want to print
it for the shack wall or calculate
different equivalents.
A similar project is running on PSK31 mode - see PropNET.org.
Back to quick links
DXpeditioning
In 2001, I was lucky enough to be invited to join the Voodudes DXpedition to Ouagadougou,
Burkina Faso for the XT2DX operation in CQ WW CW. We transported the entire multi-multi station
from Ghana to Burkina overland in a hired minibus and set it up on the roof of an hotel. It was a
real blast - although I have plenty of contest experience, it was my first real experience of being at
the DX end of a pileup. I’m planning to join the boys again in West Africa this November ...
I was part of the Oceania DX Group’s VI9NI team in 2006 for CQ WPX CW. The contest was a bit
of a flop but the trip was fun.
The opposite happened with a short break to Rarotonga, operating as E51iFB from a fabulous
holiday QTH that just didn’t work out on the radio somehow. I could hear OK but evidently
couldn’t be heard, and to cap it all my laptop’s hard drive expired taking the whole E51iFB log with
it. :-( It’s a good thing I didn’t make many QSOs really.
I'd love to do more DXpeditions, in particular I want to visit the Galapagos Islands HC8 to combine
amateur radio and following Charles Darwin's exploration of the exotic fauna and flora that has
evolved there (takes me back to my genetics training). Perhaps one day I’ll get to meet Trey at
HC8N, the Galapagos beacon in all the major contests ...
Lee ZL2AL lent me the fabulous DVDs by 9V1YC of various DXpeditions:
-
ZL9CI to Campbell Island in 1999 (in which Lee participated);
-
VP8THU to Southern Thule, one of the South Sandwich Islands in 2002;
-
3Y0X to Peter 1st Island in Antarctica in 2006;
-
BS7H to Scarborough Reef in 2007.
The icy conditions in South Sandwich and Peter 1st really don’t appeal to me. It’s clear from the
DXpedition leader’s reaction that getting the last few members of the 3Y0X team plus the
remaining gear off Peter 1st by helicopter was a tremendous relief.
The BS7H story is amazing - to see 4 self-contained stations perched on wooden platforms on
rocks about the size of a rug, the largest remaining bits of a dead reef still above water at high tide,
in a war zone in the South China Sea is almost incredible. They were fortunate to have such good
weather as I’m sure the slightest of squalls would have been catastrophic. The “discussions” about
whether DXCC rules should permit such an entity rumble on.
VP8THU was a “micro-light DXpedition” using small barefoot transceivers. Given that they must
have spent a fortune getting the team there, it seems odd that they would skimp on equipment
and settle for poorer signals, but still they made a respectable number of QSOs. Watching them
ferry people and equipment from a dinghy up an icy rock face, and back again at the end, is best
done from behind the settee - a bit like watching the BBC’s “Dr Who” as a child.
The vids are well worth watching, whether you just work DXpeditions, dream of joining one or are
planning one for real. The 3Y0X one shows a little of the organization and logistics arrangements
necessary for a major DXpedition. It’s a shame James 9V1YC doesn’t at least make a guest
appearance in front of the lens though: I guess either he’s not keen on letting someone else hold
his expensive camera or he’s camera shy!
Back to quick links
Pileup tips
Here are some Hinson tips for DXers working DX in pileups to maximize their chances of success
and hence fun, plus the corollary - tips for DX stations to maximize their rates and fun. These tips
were first developed and published for the ZL7T DXpedition in March 2009.
|
Pileup-beating advice for DXers
|
Pileup
management
advice for
DX
stations
|
|
Listen listen
listen!
If
you
hear
a
pileup
or
see
something
juicy
spotted
on
DXcluster,
please
don’t
just
jump
straight
in.
You
will
not
be
able
to
work
the
DX if
you
can’t
even
hear
the
DX,
so
first
find
the
DX
stn’s
TX
frequency
and
set
up
your
transceiver
and
antenna
properly
while
you
listen
to
his
rhythm
and
hopefully
find
out
his
preferred
RX
frequency.
|
Aim to be efficient, fair and reasonable.
You
know
lots
of
DXers
will
be
desperately
calling
so do
your
level
best
to
work
the
pileups
as
efficiently
as
possible.
Try
to
adopt
a
consistent
rhythm
and
sensible
speed
for
the
conditions,
and
be
prepared
to
slow
down
a bit
(or
use
“Farnsworth”
extended
inter-character
gaps
at
least)
for
the
slower
callers
who
appear
to be
having
trouble
copying
you.
Ignore
the
lids
-
don’t
rise
to
the
bait.
Pick
out
the
polite
stations
with
good
quality
signals
(hint:
they
are
seldom
the
loudest!).
|
|
Configure your rig correctly.
Use
the
appropriate
filter
settings,
RF
gain
or
attenuation
and
so
forth
to
have
the
best
possible
chance
of
completing
a
QSO.
You
might
like
to
lock
your
receive
VFO
or
pop
it
into
a
memory
once
it is
set
correctly,
though
you
may
need
to
make
minor
adjustments
later.
Turn
your
beam
if
appropriate
and
if
necessary
check
the
long
path.
DX
stations
often
operate
with
relatively
low
power
and
basic
temporary
antennas,
so be
prepared
to
work
at it.
|
Take maximum advantage of your QTH.
If
you
are
on a
desert
island,
find
a
suitable
location
right
on
the
beach
if
you
can,
as
close
as
you
dare
get
to
the
sea
(simple
vertical
antennas
work
extremely
well
at
the
water’s
edge
or
even
better
on a
short
pole
in
the
water
- you
simply
can’t
get a
better
ground
plane).
Next
best
would
be a
high
cliff-top
site
with
excellent
take-off
over
the
sea
in
the
main
directions
of
interest.
Mountain
tops,
hill
tops
and
even
hotel
roofs
make
good
locations
too.
Don’t
forget
to
order
good
propagation
before
you
leave
home
....
|
|
Spend
a
moment
listening
to
the
DX in
order
to
pick
up
his
pattern
and
style
of
operation.
Is he working all comers or calling specific call areas/continents, working by numbers, or whatever? Is this a contest-style quick fire operation working snappy callers who only call once, or is the DX taking the time to chat to callers and work the slower ones?
|
If
the
pileups
get
too
unruly,
consider
calling
and
working
specific
areas/continents
and
if
absolutely
necessary
work
by
numbers.
Don’t spend too long
on
any
single
area
or
number:
cycle
through
the
complete
number
sequence
or
listen
elsewhere
every
10-15
minutes
or
so.
Keeping
the
pileup
under
control
is an
important
job
for
you.
|
|
Double-check the DX stn’s callsign.
DXcluster spots from over-excited DXers often list broken (incorrect or incomplete) calls. Some are obviously broken but others look OK at first glance, until you notice an Oh instead of a zero, an L instead of a one, or a 5 instead of an S ...
Do
not
call
until
you
are
certain
who
you
are
calling
and
make
sure
you
log
the
DX
correctly.
You would not want all this hard work to go to waste, would you?!
|
Send your own call frequently
,
ideally
during
every
QSO
but
if
not
at
least
once
every
minute
or
two.
If
you
hear
callers
sending
QRZ
or
CL?,
that
usually
means
you
are
not
identifying
often
enough.
Take
extra
care
logging
when
you
are
either
tired
or
working
flat-out.
Simple
typos
(such
as
entering
an oh
instead
of a
zero)
are
hard
to
spot
by
eye.
On CW
and
data
modes
if
not
SSB,
have
the
computer
send
the
logged
call
as
part
of
the
exchange,
as a
sanity
check.
And
if
the
pileup
gets
too
monstrous,
just
move
to a
clear
frequency
and
for a
while
at
least
enjoy
working
genuine
DXers
who
are
not
totally
dependent
on
their
DXcluster
drips
...
|
|
Give
your
callsign
in
full
but
only
once,
then
listen
for a
bit.
On
CW,
use
QSK
if
possible
to
hear
instantly
when
the
DX
comes
back.
On
phone,
use
recognised
phonetics.
Never
give
“last
two”
(unless
the
DX is
explicitly
asking
for
it).
If
the
path
is
open
and
the
pileup
is
huge,
giving
your
callsign
more
than
once
without
listening
just
creates
QRM
and
slows
the
DXer’s
rate
down.
If
the
DX
responds
with
part
of
your
callsign
missing
or
incorrect,
give
your
callsign
again,
in
full,
once
and
listen
carefully
in
case
you
are
doubling
with
another
DXer
with
a
similar
callsign
to
yours.
If he
still
can’t
get
your
callsign
correctly,
give
it
twice
and
listen.
Sometimes
it
helps
to
slow
down
a
little
-
savour
the
moment,
you
are
working
DX!
|
Repeat
at
least
the
corrected
part,
if
not
the
entire
call,
of
anyone
whose
call
you
did
not
send
correctly
the
first
time.
Failing
to do
this
leaves
the
DXer
uncertain
whether
the
QSO
was
completed
and
leads
to
additional
but
unnecessary
“insurance”
QSOs.
Get
this
right
and
the
callers
will
love
you.
Get
it
wrong
and
they
will
challenge
your
parenthood,
send
“LID”
or
just
cause
QRM
on
the
frequency
and
be
somewhat
uncomplimentary
on
DXcluster.
Use
all
available
tools
to
focus
on
one
caller
at a
time:
notice
their
tone,
rhythm,
accent,
strength
etc.
as
well
as
their
callsigns.
Use
filters
if it
helps.
Turn
the
beam
if
that
helps.
|
|
Choose the best times to call the DX.
Be
aware
of
propagation.
Check
the
solar
figures
and
propagation
predictions
(more
advice
further
below).
If
conditions
are
clearly
poor
to
your
part
of
the
world
right
now,
hold
on
until
they
improve
and/or
choose
another
band.
Check
any
pre-announced
preferred
frequencies,
or
use
previous
spots
as a
clue.
Meanwhile,
look
for
other
DX to
work
-
tune
around
because
rare
DX
stations
often
come
up to
work
DXpeditions
and
some
look
around
the
bands
while
they
are
on.
Remember
it’s
always
best
to
work
and
then
spot
DX
than
to
see
them
spotted
and
join
the
pileups!
|
Be
aware
and
take
advantage
of
propagation
,
making
the
best
of
short
greyline
openings,
long
paths,
sporadic
E/tropospheric
modes
on
the
high
bands
and
so
forth.
Listen
for
weak
DX
callers.
If
you
hear
or
work
some
exotic
DX in
a run
of
routine
QSOs,
put
the
pileup
on
hold
for a
moment
and
call
for
more
DX to
take
advantage
of
the
opportunity.
Remember: you are
in
charge.
To
avoid
the
pileup
turning
into
a
bun-fight,
do
what
you
say.
If
you
say
“Standby
Europe”
(or
“NO
EU”
on
CW),
studiously
ignore
any
and
all
Europeans
who
call
until
you
say
“Europe
go
ahead”
(or
“EU
GA”).
Don’t
bother
with
“IZ1QRM,
you
are
in
Europe,
please
QRX”
as
lids
who
don’t
know
where
they
live
are
not
worth
the
air
time.
|
|
Operate split - always!
Find
the
DX
stn’s
listening
frequency
by
listening
to
his
instructions
(e.g. “Up five to ten”) and tuning around the pileup to pick out people they are working (the “5NN” or “five-niner” reports from callers are often a giveaway). Set your transmit VFO near but not on the exact same frequency, please. Even if the DX is working simplex, shift your TX a few Hz. Moving as little as 50 to 100Hz up or
down
will
help
the
DX
resolve
your
signal
from
all
the
other
zero-beat
callers.
If
the
pileup
is
massive,
you
stand
a
much
better
chance
of
getting
through
if
you
hunt
for a
clearer
transmit
frequency
within
the
range
the
DX is
using
but
be
careful
not
to
transmit
on
top
of
another
QSO.
If
you
have
a
dual-RX
rig
such
as
the
K3 of
FT1000,
use
the
2nd
RX to
listen
on
your
TX
frequency
and
make
sure
it is
clear.
Respect
the
rights
of
other
users
of
the
band
who
may
not
be in
the
pileup
-
remember:
Listen listen
listen!
|
Patrol
systematically
through
the
receive
range
when
things
are
quiet
but
be
prepared
to
move
swiftly
through
the
range
when
the
heat
is
on.
Use
narrow
filters.
However,
try
to
restrict
the
bandwidth
consumed
by
the
pileup
by
not
listening
too
far
up
the
band,
in
other
words
stick
to a
restricted
range
of
receive
frequencies
(e.g.
five
to
ten
up on
SSB
or up
1-2
on
CW),
looking
for
callers
who
are
clear
enough
to
copy
and
polite.
Studiously
ignore
the
alligators,
callers
who
interrupt
QSOs
or
call
blindly
as
they
are
certainly
rude
and
are
probably
not
hearing
you
well
enough
to
make
a QSO
efficiently
anyway.
If
possible
listen
on
your
own
frequency
with
a 2nd
RX
and
if
you
hear
anyone
calling
you
there,
send
“UP”
more
often
[do
NOT
work
them!!].
Be
very
careful
in a
crowded
band
(for
example
in a
busy
contest)
not
to
step
on
someone
else’s
toes
by
dumping
your
pileup
on
them
- in
other
words,
listen
to
your
chosen
RX
frequency
before
announcing
it.
|
|
Double
check
your
rig’s
frequency
display
and
VFO
settings
while
you
transmit
to
make
sure
you
are
actually
operating
split.
Accidentally
or
even
worse
deliberately
transmitting
on
the
DX
stn’s
frequency
is a
no-no,
creates
QRM,
interrupts
his
rhythm
and
raises
everyone’s
blood
pressure.
Don’t
be a
frequency
cop.
Also,
please
try
to
contain
your
enthusiasm:
do
not
shout
and
overdrive
your
rig
as
that
will
make
your
signal
difficult
or
impossible
to
copy
and
will
create
QRM.
Keep
checking
your
ALC
and
compression
meters
and
reset
the
mic
gain
where
necessary!
Listen
carefully
for
other
stations
the
DX is
working
and
try
to
figure
out
his
pattern,
for
instance
is he
working
people
mostly
around
one
specific
frequency,
over
a
small
range,
or
“randomly”
across
the
entire
pileup?
|
Always operate “split”
,
in
other
words
listen
up to
a few
kHz
away
from
where
you
are
transmitting
so
everyone
can
still
hear
you
no
matter
how
many
callers
are
calling.
Give
callers
at
least
a
clue
to
where
to
tune
their
TX
both
when
you
first
go
split
and
periodically
thereafter
by
saying
something
specific
like
“listening
up
five”
or
“listening
two-fifty”
on
SSB
or
“UP1”
on
CW,
otherwise
it’s
OK to
be
more
vague
if
you
need
to
spread
the
pileup
(“UP”
or
“DN”
work
fine).
Restrict
the
range
of
your
pileup,
and
by
all
means
use
your
narrow
filters
to
help
single
out
specific
callers
(good
DXers
will
often
call
very
close
to
previous
callers).
If
possible,
lock
your
TX
VFO
or
save
it in
- and
transmit
from
- a
memory.
This
helps
avoid
accidentally
moving
your
TX
frequency
and
so
walking
the
entire
pileup
gradually
across
the
band!
|
|
Wait for the right moment to transmit.
Please
do
not
tail-end
other
QSOs
or
call
continuously,
but
wait
for
your
cue
which
is
usually
when
the
DX
says
UP. [Hot
DX
tip:
it
often
helps
to
wait
just
a
second
or
three
longer
if
the
DX is
tuning
around
the
pileup.
Don’t
be
too
hasty
to
call
at exactly the same instant as everyone else!]
|
Maintain a consistent rhythm
to
avoid
encouraging
other
callers
to
call
in
while
a QSO
is
still
in
progress.
Ignore
tail-enders
and,
if
they
are
really
rude,
blacklist
blind
callers,
at
least
for a
while.
If
the
QRM
is so
horrendous
you
can
only
pick
out a
partial
call,
send
the
partial
with
a
question
mark
to
encourage
that
station
to
try
again
and
others
to
wait.
|
|
When
you
call,
give
your
complete
callsign
just
once
or at
most
twice,
then
listen
for a
moment
and,
if
the
DX
has
not
come
back
to
someone,
call
again
in
the
same
way.
Everyone
should
be
listening
far
more
than
they
transmit.
|
Listen at least as much as you transmit.
Use your filters etc.
to
the
best
effect
and
make
a
special
effort
to
pick
out
weak
callers,
whether
DX or
QRPers
(ideally
both!).
|
|
Listen carefully to what the DX is sending.
Always send your full call.
If the DX sends X? and your call does not contain an X, then just stand by for a moment: they are almost
certainly not
talking
to
you.
If
the
DX
sends
W3X?
(especially
if
they
repeat
it),
they
are almost certainly not calling K5Xsomething, and certainly not something totally unrelated such as UA9ABC or I5ABC. If you keep on transmitting regardless, you will only prolong the agony for everyone and you may be blacklisted.
Be nice, people. We all want to play.
|
Repeat
whatever
characters
of a
partial
call
you
are
reasonably
certain
about,
with
a
question
mark
to
invite
that
station
to
try
again
and
signal
other
callers to
wait.
Focus
on
the
specific
tone
and
rhythm
of
the
caller,
and
persist
doggedly
until
you
get
his
complete
call.
If you make a genuine mistake and nobody returns to your first or second offer, say something like “No copy, QRZ” (or “NIL QRZ” on CW) and return to normal calling. If you are reasonably certain the caller had, say, “W3X” in his call, studiously ignore any unrelated callers, as to cave in to such demands them invites utter chaos.
|
|
If
you
are
uncertain
that
you
completed
a
QSO,
call
again
straight
away.
If you can’t get through to confirm, check the online log if available. Avoid unnecessary duplicate QSOs on the same band and mode, unless you are really not sure that you made the QSO first time around (“insurance QSOs”). Also, do not repeat your callsign if the DX has just sent it correctly, as this sounds like you are making a correction.
|
If
you
hear
someone
you
have
just
worked
immediately
or
soon
after
calling
you
again,
check
the
log
carefully,
repeat
their
call
back
to
them
and
say
something
like
“QSL”
or
“You’re
in
the
log”
to
confirm
and
complete
the
QSO
unambiguously
for
them.
If
you
made
a
mistake
in
the
log,
correct
it,
apologise
and
patiently
confirm
their
full
call
on
air.
Update
your
online
log
as
often
as
you
can
or at
least
daily
if
you
have
the
facility
to
cut
down
on
“insurance
QSOs”.
|
|
Take
a
short
break
on
the
hour
to
allow
QRP
and
genuine
DX
stations
to
have
a go.
At
the
very
least,
turn
off
your
amplifier
and
turn
down
the
wick.
By
all
means
sign
/QRP
if
your
license
allows
this
but
only
if
you
are
running
5
watts
or
less!
Play
the
game.
|
On
the
hour
every
hour,
please
put
the
pileup
on
hold
and
listen
out
specifically
for
DX
callers
and
QRPers
.
Listen
extra
carefully
for
weak
signals
and
ignore
the
alligators
as
best
you
can.
Turn
the
beam
(where
applicable)
and
really
make
the
effort.
If
they
get
through,
you
will
be
making
someone’s
day extra special.
|
|
Do
not
call
blindly
or
out
of
turn.
Do
not
become
a
“pileup
cop”
,
shouting
on
the
DX
station’s
transmit
frequency.
Most
of
all,
whatever
happens,
always keep your cool
.
If
you
lose
your
temper
and
start
disrupting
the
pileup
or
chastising
other
callers,
you
will
only
inflame
things
and
slow
down
the
rate
for
us
all.
If it
all
gets
too
much
for
you,
take
a
break
to
cool
off.
Go
make
a cup
of
tea
or
take
a
walk.
The
DX
will
most
likely
still
be
there
when
you
come
back,
refreshed
and
ready
to
play.
There’s more sage advice for pileup cops further below.
|
Keep your cool too!
For
example,
if
you
get a
partial
callsign
or
suspect
you
might
have
made
an
error, persist doggedly until you are confident enough to complete and finally log the QSO.
Always
be as
clear
as
possible
in
what
you
are
sending
(e.g.
send
“<call>
KN KN
KN”
or
”<call>
ONLY!”
to
indicate
that
other
callers
apart
from
the
person
you
are
working
should
stand
by),
and
stick
to
your
guns
.
Make
every
effort
to
confirm
full
callsigns,
or at
the
very
least
repeat
the
corrected
suffix
or
prefix.
If
there
is any doubt
immediately
ask
the
caller
to
confirm.
Remain
polite
and
gentlemanly
at
all
times
as
this
encourages
good
behaviour. Studiously
ignore
the
rudest
lids:
let
them
stew
in
their
own
juices!
|
|
Remember, everyone, this is only a hobby!
|
Special advice for digital modes (e.g. RTTY & PSK) in addition to that above
|
|
Lock
your
RX
frequency
on
the
DX
and
turn
off
all
automatic
tuning
(e.g. AFC and NET in MMTTY). Manually select your TX frequency, lock it or pop it in the memory and for sure don’t touch that VFO if the DX calls you! Keep to a sensible range but look for a quiet spot away from the DX stn’s TX frequency (up to 1 kHz on PSK, probably more on RTTY) and stay put for a while. If the DX seems to drift off frequency, use the RIT on your rig to keep them in tune rather than moving your VFO or adjusting the receive frequency in software. Don’t forget to listen on your chosen TX frequency from time to time to make sure it’s still clear.
|
Stick
to
the
preferred
band
segments
for
each
mode,
especially
if
this
is a
condition
of
your
licence.
Avoid
the
beacon
frequencies
and,
of
course,
listen
first
to
find
a
clear
spot.
Always split.
Never operate simplex. Avoid listening too close to your own TX frequency.
Turn
off
all
automatic
tuning
and
lock
your
TX
frequency
to avoid wandering across the band. Use suitable filters to pick out individual callers. Remember your responsibility to tune within a limited range to avoid spreading the pileup too far. If stations are clearly not hearing you well, double check that your TX frequency remains clear and don’t forget to send “UP” or “QSX 14085-6” or similar.
|
|
Setup
your
digital
mode
software
and
macros
appropriately
.
When
calling,
give
your
own
call
two
or
three
times.
It is
not
normally
necessary
to
include
the
DX
callsign
in
your
macro,
unless
there
are
co-channel
operations
and
possible
confusion.
HINT:
you
can
do
this before you
join
the
pileup!
Take
a
moment
to
get
it
right
before
you
start
transmitting,
and
make
absolutely
sure
you
can
actually
copy
the
DX
properly
and
have
his
call
correct
(DXcluster
is a
reliable
source
of
busted
calls!).
|
The
worst
thing
for
callers
is
not
knowing
who
got
called.
Repeat
callers’
callsigns
at
least
twice
,
usually
three
times
or
more (e.g.
include
it at
the
start and end of your ‘send report’ macro, and yet again in your ‘thank you’ macro).
Give
your
own
callsign
frequently
too,
ideally
ending every QSO with your callsign and finally “CQ UP” or similar.
|
|
Do not overdrive your transmitter.
Apart from perhaps overheating and damaging it, your signal will probably become unreadable and create QRM for others. This is especially important if you are using AFSK with tones generated by a PC audio card. Use your rig’s transmit monitor function for a simple but crude quality check. If you have a separate receiver or a monitor scope, listen to/monitor your own data transmissions to check the levels. If not, find a local ham who is willing to help you conduct some tests. If you have trouble contacting reasonably strong stations normally, and especially if you receive reports indicating poor quality signals, check those settings again.
|
Look
out
especially
for
well
modulated
signals,
even
the
weak
ones
and
make
certain
your
own
signal
is
clean.
Do
not
overdrive
your
transmitter
and be careful not to knock the microphone or PC level controls once set. It pays to keep a written note of the correct settings: you should really have figured those out before you left home but small adjustments may be needed in the field: ask a local to check the quality and width of your data signal when you first set up.
|
|
Here is an illustration of some of the techniques in use: along with several other ZL DXers, I had
been calling K4M (the DXpedition on Midway Island) on 40m/CW for several minutes one ZL
evening but was getting nowhere in a huge pileup, so I consciously changed tactics. First, I
stopped transmitting for a while to LISTEN to their pileup for the stations he was working, trying to
figure out his listening pattern. He seemed to be working several stations at a time on or near one
frequency, then spinning the dial: this meant it was worth me finding someone he was working and
calling him on or near that frequency rather than, say, looking for a quiet spot in the pileup. With
him on the main receiver in my left ear, I tuned through the pileup on the sub-receiver in my right
ear, listening hard for the tell-tale “5NN” of someone actually working him and trying to pick up his
rhythm. After a couple of failed attempts, I caught a JA sending him a report and set my TX
frequency right there. My next tactic was to turn down my CW sending speed to try to catch his
attention. As soon as he finished with the JA, I gave my call just once and listened. He came right
back with a partial call (no QRZ, no question marks, just part of my call) and I immediately resent
my call once more and listened again. This time he came straight back with my full call and report,
so I sent him 5NN TU, he sent TU K4M UP back real quick and that was that. The whole QSO
including the repeats took just a few seconds but that’s another DXCC band-slot filled thanks very
much.
Listen to this MP3 soundbyte of the QSO to hear how it played out on air.
If you appreciate this advice and want more of the same, I recommend these excellent guides:
DXpeditioning Basics by Wayne Mills N7NG for ARRL
Ethics and Operating Procedures for the Radio Amateur
by John Delvodere ON4UN and Mark Demeuleneere ON4WW for the IARU
So you want to be a DXer? DXing tips from Jim AA0MZ
DX Etiquette, an Op-Ed piece in QST by Randy Johnson W6SJ (forthcoming!)
DXpeditioning Behind the Scenes for Radio Amateurs Worldwide:
A Manual for DXpeditioners and DXers
edited by Neville Cheadle G3NUG and Steve Telenius-Lowe G4JVG
[Unfortunately this appears to be out-of-print, so ask around at the radio club!]
Back to quick links
Advice to pileup cops
Finally, here’s a desperate plea to all you pileup cops and spleet poleece Out There. You are not
the only one listening to someone making a fool of himself on the DX station’s TX frequency. Most
of us in the pileup can probably hear him too. Almost all of us choose to ignore the fool,
remember that we got it wrong once ourselves, and hope he will soon spot the error of his VFOs.
We turn our antennas and use our filters and notches to good effect, and mostly carry on calling
the DX when he invites further calls (and not before!). If the fool persists, a few of us may decide
to Do Something Positive About It, such as sending him a private TALK message (NOT an
ANNOUNCE/ALL or a pseudo spot!) on the DXcluster network to point out the error of his ways,
politely of course. Those of you who decide to become pileup cops and start transmitting “UP UP
UP” on the DX station’s TX frequency have just become
part of the problem, not the solution
.
Sending “UP YOU IDIOT” or “SPLEEEEEET” and further QRM breaks the terms of your amateur
license, for a start, indicates that YOU are the idiot and no doubt proves the small size of your
delicate anatomy. It merely encourages other pileup cops and lids to start railing at YOU for
transmitting on top of the DX.
DON’T DO IT!
Bite your knuckle. Shout at the Morse key. Send
the fool an email if you like, telling him he’s busted. But whatever else you do,
DO NOT
TRANSMIT ON THE DX STATION’S TX FREQUENCY
. EVER.
Not even if you turn your
amplifier off and whisper quietly to him. You wouldn’t want to see your own call on the split police
hall of shame, now, would you?
Back to quick links
JCC Japanese Cities Club award
JARL, the Japanese national radio society, runs an award scheme based around working Japanese
cities. I stumbled across this after noticing yet another JA special event station with a weird callsign
sending its JCC number to strings of JA callers on 40m. Google found the JARL page listing those
JCC numbers and with a bit of digging and guesswork (to get around some broken links on the
JARL website), I found this brief page about the JCC award. The basic award requires QSLs from
at least 100 of the nearly 800 current cities, ignoring the deleted cities (which I hardly like to ask
about).
There is a similar JCG award for working at least 100 of the 396 current guns ... not, not that kind
of gun, a Japanese gun is evidently a “regional congregation of towns and districts”, not unlike the
districts or parishes of G-land I guess, making this award vaguely similar to the Worked All Britain award.
JARL’s main English page for all its awards is here.
Back to quick links
HF propagation
On the topband reflector, N7DF noted that changes of the direction in which the interplanetary
magnetic field impinges on earth's magnetic field (known as Bz, apparently) affect propagation on
all the SW bands. The 7-day magnetic data from NOAA did indeed show a correlation between Bz
(the yellow plot) and the outstanding 10m conditions I experienced over the previous weekend:
Notice the Bz (and Theta and Phi) dips to the negative region on the 13th and again on the 14th
and 16th: these were the very periods when 10m conditions peaked for me. According to N7DF,
the periods of change between Bz+ and Bz- correlate with enhanced LF conditions, while the stable
Bz- periods correlate with enhanced HF conditions.
... Unfortunately, this is yet another lagging indicator that doesn’t help predict when conditions will
peak. But still, it’s an interesting aside.
During the 2010 FOC Marathon, I was watching the graphs to see if I could spot 10m
openings, and managed a whopping four 10m QSOs when the Phi value went “off the top of the
chart” (evidently it wraps around and reappears at the bottom of the axis). Listening around and
calling CQ on 10m at other times yielded no further QSOs so there might be a correlation there,
but it’s far from certain as this is hardly a scientific study. Anyway, speculating on this was an
interesting way to spend the time waiting while the memory keyer made my CQ calls. With
N1MM’s screen layout carefully adjusted, I could monitor the previous couple of hours’ Phi and
Theta values using the NOAA 24 hour graph on a browser screen, auto-updating every minute in
real time and viewable in a convenient gap between the N1MM windows:
[I made that screenshot after the Marathon while listening on 17m: like all other contests, the
Marathon does not include the WARC bands, making them a peaceful haven for non-contesters.]
Towards the end of the FOC Marathon at 21:00z on Feb 7th 2010 and for a good few hours
afterwards, I noticed the background noise coming up in waves to about S6 on 10m: the noise
would peak for a minute or two, then subside for a few mins, then come back. I recorded some of
the peaks - here’s one recorded on 28020 (left channel) and 28200 (right channel) at about
01:00z on Feb 8th UTC. According to fellow Kiwi DXers and SpaceWeather.com, it turns out I was
hearing C-class solar flares sending huge bursts of wideband radiation our way. The sun is finally
waking up after its prolonged snooze the past few years.
Back to quick links
DX Magazine’s annual DX Marathon
CQ Magazine's DX Marathon is a DXers’ competition to work the most DXCC countries (plus a few
CQ mag specials such as the Shetland Islands) and CQ zones in the calendar year - any mode.
Here's how I entered, step-by-step:
-
Extracted and saved my log from Logger32 as an ADIF file.
- Downloaded the DX Marathon scoring utility by AD1C.
-
Installed the DX Marathon utility.
-
Ran the DX Marathon utility.
-
Pointed it at the ADIF log from step 1, selected 2009, watched it write a CSV file.
-
Opened the CSV file in Excel.
-
Opened the official DX Marathon entry form also in Excel.
-
Cut-n-pasted the QSO info from the CSV file into the entry form, in 2 halves: first the country
info, then the zones info.
-
Checked the info for any glaring errors, then saved it somewhere handy.
-
Sent the saved file as an email attachment to Scores@Dxmarathon.com
-
Checked my inbox for a confirmation email that the entry had been received.
-
Double-checked that my entry is shown on the list of entrants.
The 2010 event is already under way, so if you are DX, don’t be surprised if I call you on several
bands having already worked you in 2009! Likewise, I’m happy for others to call me at least once
per band/mode per year, well as often as you like really.
Back to quick links
Configuring VE7CC’s Cluster User to use a different DXcluster
Using VE7CC's Cluster User program to connect to your favourite DXcluster beats just connecting
directly for several good reasons, such as:
-
Auto-reconnect - if the link drops, it logs you back in
-
Easier filtering - point-n-click configuration of the DXcluster filters for bands etc.
-
Ready access to spots sorted by band, frequency etc.
-
Read access to announcements, cluster mail etc.
-
Ability to merge spots from two DXclusters (more on this below)
The default list of DXClusters in Cluster User does not include the CDXC cluster, amongst others.
Here are the instructions to configure Cluster User to connect to an unlisted cluster:
-
On the top line menu, select
Configuration
-->
Cluster (telnet)
-
Into the (normally empty) node box, type
CDXC, then click
Add
[Note: it is also possible to
add another DXcluster address to the default node data file, but if you later select the 'Update
node list' option on this screen, your changes will be overwritten when the software re
-downloads the default node data file from the WWW. So basically, don't bother.]
-
Into the address field, type
cluster.cdxc.org.uk
(or the Telnet address for another cluster)
-
Into the port field, type
7300
(the most common port, although some use 7373 etc.)
- Click
Apply
to tell the software you intend to connect to the CDXC cluster
- Click
Exit
-
On the top line menu, select
Configuration
--> User info
-
Enter your CDXC
cluster login ID and password
(obtained from CDXC) and optionally
complete the rest of this panel with the appropriate info for your location, home node etc.
- Click
OK to save it
-
If you are currently connected to another cluster node, click the
Disconnect
box next to the
node name at the top of the screen
- Click
Connect
to tell Cluster User to make a Telnet connection to the address entered in
steps 3 & 4 and then submit your username and password entered in step 8 to log you in,
and that should have you connected to the CDXC cluster.
-
Optionally set up the cluster info, band filters etc. using the
Settings, Bands
and other tabs in
the VE7CC program
I have just figured out how to connect to two clusters using two instances of the Cluster User
software (in other words, I run it twice but with the ‘link’ option set), so that I can get both the
members-only spots from the closed CDXC cluster and global spots while being able to send global
spots by default using a different cluster: the info needed to do this is in the VE7CC help, which is
entirely online. Connecting simultaneously to two clusters (with different callsigns e.g. ZL2IFB and
ZL2IFB-16) is handy in case the primary cluster goes down for maintenance, falls over, drops off
the Interwebnet or whatever.
Back to quick links
|