ZM4G glow logo
ZL2iFB glow logo
DXing
Home
QTH
Station
Homebrew
Antennas
Elecraft K2 K3
LK550
TS850 mods
LoTW
Logger32
Contesting
DXing
Intruder Watch
HF Challenge
Friends
QBL
Links
QSL!

Quick links

This page covers my main operating interests ... at the moment ....


DXing

I've been licenced since attending after-school 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.  The Radio Amateurs’ Exam was the first public exam I took.  I taught myself CW straight away after a short a break to complete my O-levels and got my CW pass on May 2nd 1979 (yes, more than 3 decades 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 more 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 keep an ear open (just the one) for the 10m beacons most days too.

I’ve caught some good high-band openings including a solid long path run into Europe on 15m that someone kindly recorded and published on YouTube video to show off their fancy instant-reversal Steppir beam (nice!).  And here’s my recording of a 10m long path opening to France.  A 15m QSO with 5T0JL led to a nice chat on email about HF propagation and skeds on the high bands including 12m: Jean runs 90W to a vertical and I was using 100W to a simple wire loop on 12m, so that was clearly a magic path.

Long path signals are quite distinctive, for example here’s a clip of John 9M6XRO on 17m, with an LP echo so strong it can be hard to make out his CW characters.  Using an audio spectrum plot and Audacity’s cursor, I measured the delay at 83 milliseconds: 

LP echo

Travelling at close to 300 million metres per second (speed of light), John’s LP signal must have gone an extra 24,900 km (0.083 x 300,000,000 / 1000) compared to the SP signal.  John is close to 8,000 km away from me, so his SP signal would have taken at least 27 milliseconds to arrive here by the most direct route.  Adding 83 to 27 milliseconds gives the total delay for the LP signal of at least 110 milliseconds, representing a distance of no less than 32,900 km, which is of course 24,900 + 8,000 (phew!).  The earth’s circumference is about 40,000 km, so either my measurements and maths are wrong, or the speed of light or Earth diameter are wrong (!), or more likely the signal took a slightly shorter round-the-world trip than the true long path, especially if we factor-in the likely extra distance between the ground and the ionospheric layers that reflect signals.  It may have cut corners along the grey line but, still, it’s close enough to LP for me.

One Saturday morning in August 2011 I heard my pal Paul ZL4PW CQing on 17/CW.  We worked easily enough on weak groundwaves.  An hour later, I heard him CQing again, but this time with a curious multitone signal.  It sounded like the normal groundwave sig - a normal sine tone - plus a slightly higher frequency signal with a raspy note: an aurora in fact, with a bit of Doppler shift I guess.  10m opened to most of NA shortly afterwards, and just after lunch I was amazed to work ZD8D on 30m.  Even 12m flickered briefly to life a few times.  A fascinating day’s DXing!

One ZL evening in December 2011, I was getting ready for a sked on 12m when I noticed very strong echoes on my transmission.  In fact, I was sure I could hear more than 1 echo, so I turned on the audio recorder and sent a spaced-out string of fast individual dits to check.  This blue audio trace shows one of the roughly 50wpm dits captured by Audacity:

Triple echo QSK

Yes, that’s right, there are 3 echoes!  Presumably the first echo was a reflection from some sort of reflecting surface - a patch of E-layer ionization perhaps - about 9,000 km away from me since it will have gone about 18,000 km in 65 milliseconds.  The second echo delayed by 161 milliseconds had done about 48,000 km, or roughly once around the world.  The third and final echo arrived back here about 300 milliseconds after the dit went out.  Travelling at 300 million meters per second, I calculate it had done a 90,000 km round trip, meaning twice around the globe!  Wow!

For the record, I was using the K3’s fabulous QSK+ setting, with the KPA500 running 500 watts out to a fullwave wire loop antenna.  It probably helps that the loop is more-or-less omnidirectional.

My DXCC records

After ~6 years on the air as ZL2iFB, my QSO totals and DXCC scores are looking quite respectable.  I have worked over 300 DXCC countries, earning mixed-mode, CW, Phone and Data DXCCs, DXCC Challenge and DXCCs for every band from 10m to 80m (including 5 band DXCC).  There’s still a lot of fun and hard work ahead before I reach Honor Roll but here are my all-time DXCC stats as of January 2012:

 

Wkd

QSLd

CW

294

284

Phone

257

196

Data

182

147

Mixed

303

294

The Clublog timeline graph below shows me working more countries each year as the sunspots return:

ZL2iFB clublog annual stats

I make about 5,000 regular DXing QSOs per year as ZL2iFB, plus another few thousand contest QSOs as ZM4G, ZM4T etc., most of them on CW.

This is my DXCC awards table on LoTW:

ZL2iFB LoTW DXCC table

 

Here’s my mixed-mode DXCC breakdown by bands (this one
includes countries confirmed on QSL cards but not yet on LoTW):

Band

10m

12m

15m

17m

20m

30m

40m

80m

160m

ALL

Worked

210

175

256

238

278

260

263

178

34

303

Confirmed

151

123

212

184

246

219

247

152

19

294

 

The WAZ (Worked All CQ Zones) table is filling out nicely, aside from Zone 2 that is:

ZL2iFB WAZ table

 

Lastly, here’s my progress towards WAS (Worked All [US] States).  I’ve worked ‘em all on 10, 15, 20 and 40m.  I have the basic mixed-mode WAS certificate on the wall and enough QSLs to claim the WAS/CW and 40m & 15m awards as well.  There are quite a few gaps left though, especially on the WARC bands and loads on topband.  I’m very pleased to have worked the lot on 10m, especially the QRPers and unfortunate US hams who have to make do with stealth antennas due to the crazy zoning regulations.

ZL2iFB WAS table

 

Back to quick links


HF beacons

I sometimes monitor the beacons on 10m during the ZL daytime while working (one of many benefits of working from home).  No more than once per day, I spot them on DXcluster and occasionally on 10mBeacons.com, and I routinely log them on my online database for all to see:

 www.HFbeacons.info

I’ve heard about two hundred 10m beacons in the past year, most of them running QRP to verticals. 

More comprehensive beacon lists are maintained by G3USF and WJ5O, while DL8WX maintains a database similar to mine detailing when he last heard the beacons (a good sign that they might truly be QRV!). 

It is disappointing that not all beacon keepers mention their beacons on their QRZ.com pages or publish information about their beacons elsewhere on the Internet, even the basics such as the location, power and antenna.  Why they would go to the trouble of maintaining a beacon and yet not publish this information puzzles me.

Beaconbytes

I’ve been recording the 10m beacons to help ID the weak signals we often receive here in NZ.  Aside from the beacon message text, the exact frequency (well, exact according to my K3’s VFO display, calibrated against WWV) and characteristics such as its strength, keying speed, timing, tone of the signal and any anomalies (e.g. does it chirp?) are often enough to ID a beacon reliably without necessarily having to wait to hear its full callsign.  In the case of those annoying beacons that only ID infrequently, it’s a big time saver that lets me log more DX beacons while the band remains open.

When the 10m band is wide open in ZL, there may be more than 50 beacons to ID and log at any one time: that hyperlink pulls up a 13-minute MP3 recording of me systematically tuning through the 10m beacon sub-band from about 28186 (VK5KV) to 28300kHz, (K6FRC/B) in 2010, pausing along the way to ID and log the signals using their callsigns if I catch them or their messages or characteristic signals if not.  Scroll down through my online beacon database while you listen along to figure out where I am and what I’m doing.

Here’s my growing collection of MP3 recordings of beacons (“beaconbytes”), mostly as I received them on 10m but a few were heard on other HF bands or donated by DX friends such as KP3FT:

K7GFH is an interesting example: this 10m beacon uses a converted CB set running just 3 watts to an attic dipole in Oregon, over 11,000 km away from ZL.  Still say 10m is dead?  Well how about EA3TEN, C30P and SV3AQR/B which usually signal long path openings into Southern Europe?  Or TP2CE/B running just 450mW?  And the NCDXF beacons 5Z4B and ZS6DN that indicate an open path on 15m to Southern Africa some ZL evenings around 0600z?  :-)  With so little ham activity prior to the sunspot max, I might never have known about these openings if it weren’t for the beacons.

The NCDXF beacons are not the only timslicers: K4UKB/B and K4FUM/B share 28276kHz, alternating transmissions.

A number of fishing buoys mark drift net positions with beacon transmissions (illegally) within amateur bands.  Some sit rather annoyingly in the beacon sub-bands.  They send a few seconds of carrier (which usually starts up with a chirp), then a short callsign (1-3 characters, chirpy again, chosen by the fishermen), then go silent for a minute or so.  Here’s one on 10m sending C, on sending D and another sending NZ all seemingly due East of NZ - possibly floating around central America or the Caribbean, perhaps even further away.  One or two come up in our afternoons when propagation swings towards VK and JA.  Despite running QRP to CB-type vertical antennas, their saltwater ground plane is enough to launch the RF over thousands of km via skywave, much further than is necessary for the net-hunting fishermen who presumably have a pretty good idea from GPS as to where their nets are and I guess listen on ground wave as they approach for the final few km.

NCDXF beacons

NCDXF logoNew hot The NCDXF beacons are a useful guide to worldwide HF openings on 10 thru 20m, with the benefit that you can monitor a single frequency on each band, ideally using Faros to hear when various long and short paths open, or monitor either all or just a selection of the frequencies automatically over a period to spot the openings (e.g. using Beaconsee). 

The NCDXF beacons are remarkably useful propagation tools.  Like all 24x7 beacons, however, they inevitably suffer occasional outages and glitches, for example OA4B transmitting all its time slots on 18MHz instead of moving band-to-band and VK6RBP having ALC problems.  Find out about planned (and unplanned!) engineering works on the official NCDXF beacon site.

I urge regular users to contribute to the NCDXF to express your support for the beacon ops and help keep the beacons running.  NCDXF is also a major sponsor of DXpeditions.

QRSS beacons

I have previously been unable to copy QRSS beacons for the simple reason that the current version of ARGO (which is the excellent software that almost everyone recommends for QRSS) will only use the default Windows sound device but the sound card I use for radio is not configured as the default on my PC.  But now I have discovered a new open-source program QRSS VD by AJ4VD and at last I can try QRSS reception.

QRSS VD is easy to use: literally within a few minutes of downloading and running the program, I received the KC0TKS QRSS 10m beacon on 28.221.510 sending “TKS” with QRSS30 (30 seconds per dot).  Here’s an image from QRSS VD (click it for a much bigger version):

KC0TKS QRSS30 10m beacon

This grainy image may not look like much to you but I find it amazing, given that the beacon is transmitting just 25 mW and is about 12,000 km from ZL (= 480,000 km per watt )!  It was totally inaudible by ear, of course, but integrated over about 10 minutes the Morse characters are clearly readable.  We can even make out a tiny chirp as the transmitter drifts about 1 Hz HF during each transmission and a short blip after the S character (actually his full callsign sent in normal CW at 13 WPM) which acts as a kind of punctuation mark before the sequence repeats.  At the time this was recorded, 10m was in good shape: I could hear numerous conventional QRP beacons and stations in the USA and central America, even Junior, a mobile Jamaican in the Kingston traffic.  It will be interesting to monitor KC0TKS and other QRSS beacons for signs of life when the band appears to be dead.

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 ZL or a JA, "73" sounds and means the same thing.  CW is more bandwidth -efficient than SSB (approximately 4 Hz per WPM for a well-shaped CW signal, according to K3WWP’s calculations, so less than about 150Hz for normal CW speeds) and much easier to filter out QRM.  Even polar flutter and auroral Doppler shift sound OK on CW.  OK OK so the computer digital modes are even better still but then the computer does all the work, and since I work in IT, typing is not my idea of a fun pastime.

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 sent that way). 

Prosigns

I can’t see much point in learning and using the AC prosign 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.

It’s odd that KN (go ahead named station) and BK (break) are usually sent as prosigns but don’t appear on most ‘official’ lists of Morse prosigns.  Maybe in theory they should be sent normally with letter spaces, but in ham usage they have evolved into prosigns.

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 to help others experiment.  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 screenshot

WSPR measures transmitter power in dBm rather than milliwatts or watts, so here’s a conversion chart to make things easier:

Power to dB conversion chart

 

 

 

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 some fabulous DXpedition DVDs by 9V1YC:

  • 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 rickety 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 continue to 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 the BBC’s “Dr Who”, too scary for kids to see out front.

The vids are well worth watching, whether you just work DXpeditions, dream of joining one or are actually planning one for real.  The 3Y0X video 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

There are many reasons why DXpeditioners enjoy DXpeditioning but top of most people's list, surely, is "To have fun!".  In this context, having fun generally involves:

  • Making QSOs as efficiently, if not necessarily as fast, as humanly possible: accuracy matters more than rate and sometimes conditions or abilities dictate a slower pace
  • Meeting lots of old friends and making new ones (both in the team and in the pileup)
  • Working as many different callsigns as possible, not just filling band-slots for the big guns
  • Working real DX, the rare & surprising stuff, unusual paths, 100w/G5RV brigade and QRPers
  • Using different bands and modes, often including things you wouldn't normally do at home
  • Taming the technology, putting out a good signal and hearing well
  • Dealing effectively with the piles and zoo creatures, getting better at it and at the same time learning to be a better DXer
  • Elmering - teaching novice DXpeditioners the ropes - and learning from peers
  • Getting on the air from exotic far-off places, not just idly dreaming about it (and ideally making time for sightseeing!)
  • Being a pleasure to contact
  • Spreading joy and happiness
  • Staying fit and healthy but getting absolutely exhausted, in a nice way
  • Being a great ambassador for amateur radio
  • Gaining the respect of fellow DXers and DXpeditioners.

Likewise, there are many reasons why DXers enjoy chasing and working DX:

  • Collecting sets and awards - QSLs, DXCC, WAZ, IOTA, stamps, points, what have you
  • Beating rivals, mastering the challenge and earning bragging rights
  • Meeting old friends and making new ones
  • Making connections with exotic, far-off places that non-hams would struggle to even point at on the map
  • Discovering and exploiting different propagation modes and paths
  • Self-improvement - becoming more skilled, competent and accomplished, learning better techniques, getting slicker with every pileup (which includes learning what not to do from the idiots!)
  • Proving and improving the station - the antennas, equipment and operator
  • Enjoying the chase as much as the catch: if it was all too easy, it would no longer be fun
  • Being a pleasure to contact, spreading a little joy
  • Gaining the respect of fellow DXers and DXpeditioners.

To help both DXpeditioners (including DXers living in exotic locations) and DXers have more fun, here are some Hinson tips I originally developed to support the ZL7T DXpedition in 2009.   Absorb my tips to avoid appearing on the piles of fun page ...

 

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. 

Take command of your pile.  Be clear, fair and reasonable.  Lots of DXers will be desperately calling so do your level best to work them as efficiently as possible.  Adopt a consistent rhythm and sensible speed for the conditions.  Ignore the lids - don’t rise to their bait.  Pick out callers that synchronise with your rhythm [hint: they may not be 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 adjustments later if the DX shifts about to avoid the frequency kops.

Learn how to drive your rig and PC before you go on air from an exotic QTH.  Be sure you know how to:

  • operate split (set and check it)
  • lock your TX VFO (use a memory?)
  • adjust your receive filters, notch filter and DSP
  • listen on your TX frequency (quietly, in one ear: if you work anyone there by mistake, you will cause chaos!)
  • log and correct QSOs
  • send standard messages using memories or macros (consistency helps)

DX stations often operate with relatively low power and basic/temporary antennas, so be prepared to work at it.  Find out from propagation prediction tools (such as Club Log) when you are most likely to catch the DX on different bands and plan your move.

Make good use of the propagation.  Listen patiently to see if they are getting stronger.  Turn your beam if appropriate and maybe check the long path.  If you can’t hear them well, you probably won’t get through, especially if they have a pileup. 

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 right 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 only if absolutely necessary work by numbers. Don’t spend too long on any single area or number: cycle through the complete sequence at least once every 10 to 15 minutes.  Keeping the pileup under control is an important job for you.  If you are too slow, the mob will get impatient and tempers will fray.  Be nice. 

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?!

It is considered vaguely rude to ask “What’s your call?” if the DX sends his callsign often, but if you have listened patiently in the pileup for a few minutes and are still not 100% sure, go ahead and ask him to confirm what you have.

Send your own call frequently , ideally during every QSO but if not at least once a minute or so.  If you hear anyone sending QRZ or CL?, that usually means you are not IDing often enough, and it encourages the frequency kops.  Don’t rush it: send your call slowly and carefully every so often.  If it is garbled and gets listed wrongly on DXcluster, some of those calling you will log it wrong.

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 (although slashed-zero fonts help).  On CW and data modes if not SSB, have your 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 new RX frequency and for a while at least enjoy working genuine DXers who are not totally dependent on their DXcluster dripfeed ...

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 s l o w  d o w n 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, create dQRM on the frequency and be somewhat uncomplimentary about you on DXcluster and DX reflectors.

Use all available tools to focus on one caller at a time: notice their tone, rhythm, accent, strength etc. as well as their callsign.  Concentrate.  Use the filters and DSP if they help.  Turn the beam if you can.

Keep your sending speed in check, no matter how big the buzz you are getting, as accuracy comes first.  Use “Farnsworth” extended inter-character gaps on CW for the slower callers, especially if they are evidently having trouble copying you.

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 poor and the path is not good 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, keep notes for yourself and 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 of, and take advantage of, propagation making the best of short greyline openings, long paths, sporadic E, tropo etc.   Listen hard for weak DX callers If you hear or work some DX in a run of routine QSOs, put the pileup on hold for a moment and call specifically for more of the same DX to take advantage of the opportunity which may be just a brief opening. 

Remember: you are in charge.  Avoid turning the pileup into a bun-fight by doing what you say: if you say “Standby Europe” (or “NO EU” on CW and data), studiously ignore any and all Europeans who call until you say “Europe go ahead” (or “EU NW” or “CQ EU”). 

Operate split.  Find the DX station’s listening frequency by listening to his instructions (e.g. “Up five to ten”) and tuning around the pileup to pick out those he is working (“5NN” or “five-niner” reports are a dead giveaway).  Set your transmit VFO near but not on the exact same frequency as previous callers.  Try to find a clear spot in the direction he is tuning.  Even if the DX is working simplex, shift your TX a bit using split or XIT.   Moving as little as 50 to 100Hz up or down will help the DX resolve your signal from the brainless melee of zero-beat callers.

DXing is an art, not a science.  Repeatedly sending your call without any respect for the DX or other callers may get you blacklisted and is wasting everybody’s valuable time.  Think about how your signal will sound at the far end, find yourself a good spot to call and call at precisely the correct moment. 

Use the right  tempo and pace.  Match the DX for speed if you can, otherwise slow down.  Sometimes slowing right down will give you the edge*.

If the pileup is massive, you stand a much better chance of getting through if you simply hunt for a clearer transmit frequency within the range the DX is patrolling, and call there patiently.  If the DX says “up 5 to 10”, go for the 10 not the 5, or even better 7.5kHz up.

Respect the rights of other users of the band, some of whom are not in the pileup.  Be careful not to transmit on top of another QSO.  If you have a dual-RX rig, use the 2nd RX to monitor your TX frequency to make sure it remains clear, and if not move again. 

Repeat after me the DXer’s mantra:
  listen listen listen!

Operate split - always Tell your callers what to do.  Give them a clue about when and when not to call (e.g. be consistent in your use of “thanks” or “TU”).  Help them discover where to call, either by saying something specific like “listening up five” or “listening two-fifty for North America” on SSB or “UP1” on CW, or being a bit more vague if you need to spread the pile out (“UP” or “DN” work fine). 

Be considerate to other users of the band and be extra careful if it is crowded, for example in a busy contest or if other DXpeditions are active at the same time.  Don’t step on someone else’s toes by dumping your pileup on top of them - in other words, listen to your chosen RX frequency before announcing it.  Restrict your pileup’s bandspread by sticking within a defined range of frequencies (e.g. five to ten kHz on SSB or 1-5 kHz on CW). 

Focus on callers who are precisely synchronised with you, as they are evidently hearing you OK.  If their timing is way off, move swiftly along: you’re wasting time.

Use narrow filters to single out specific callers.  Patrol systematically through the receive range when things are quiet but be prepared to move swiftly through the range when the heat is on.  Pointedly 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 you decide to warn them, avoid giving their full callsigns as that confirms you are hearing them and they will just continue.

If you can, monitor your TX frequency on a 2nd RX and if you hear anyone calling you there, send “UP” more often [and do NOT work them!!].

NOTE: even if you have published ‘preferred frequencies’, don’t stick to them slavishly.  DXers will find you wherever you are.  DXpeditions that have unwisely chosen and stuck to low band frequencies permanently masked by QRM in some parts of the world have missed out on QSOs and annoyed DXers unnecessarily.  Clever DXpeditioners shift about to dodge the idiot DQRMers.

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?

Lock your TX VFO to avoid accidentally moving your TX frequency and creating chaos.  If you have published a list of frequencies, have it close to hand.

If you are using an unfamiliar radio, ask someone or take a moment to figure out how to use the VFOs, split and XIT/RIT.  While you transmit, double-check the display.,

[Hint: if you hear an unruly mob of pileup cops on your chosen RX frequency telling your callers to QSY! QSY! UP! UP!, there may well be another DX station on that frequency so it’s probably worth shifting your pileup.  If you hear the cops on your TX frequency, you either need to say “UP” more often, or QSY.]

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 over the top of QSOs in progress.  Ignore tail-enders and, if they are really rude, silently blacklist blind callers and dQRMers, at least for a while.  If the QRM is so horrendous you can only pick out a partial call, send just the partial to encourage that station to try again, hoping that others will wait.

When you call, give your complete callsign just once, 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.  Try to avoid sending question mark - to lids, “?” means “Go ahead”!  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, ignore any unrelated callers: working them ‘to get them out of the way’ trains the pile to ignore your commands.

As a last resort, make up a fictitious full call to complete your partial, have a phantom QSO, and move along.  Don’t log it though!

If you are confident the DX is working you but has made a small mistake with your callsign, do not give him a report but repeat just your callsign, then listen just in case he’s working someone else.  Only give him a report when he has got your whole callsign correctly.   If he once again repeats his mistake, send “NO” followed by your callsign once or twice. 

If you send someone a report but they do not respond, two things are likely: either they cannot hear you (possibly due to QRM on your TX frequency from pileup kops and lids) or you have made a mistake with their callsign.  If the station you are working responds with their callsign but does not send you a report, listen extra carefully to the callsign in case you made a mistake.  Persist with them until you get their correct call and their report (which is a clue that you now have their call OK).

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 your 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.   To cut down on insurance QSOs, update your online log as often as you can, at least daily if you have the facility.

If the DX starts calling for QRPers, exotic DX or first timers, take a short break to allow them their chance.   Go pour yourself a coffee or make a cup of tea.  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.  The DX will return to the pile shortly so rest and be patient.  If you like, spend your time checking propagation predictions to find out when would be your best chance to work them.

Periodically, ask your pileup to QRX while you call specifically for DX callers, QRPers and anyone who hasn’t worked you before on any band/mode .  Listen extra carefully for weak signals and ignore the alligators as best you can.  Turn the beam.  Really make the effort.  If a QRPer, rare DX or first-timer gets through, you will be making someone’s day extra special and perhaps teaching those alligators a lesson in humility and operating technique (some hope!).

If the DX is calling for a specific area but you are not in or near that area, QRX.  The DX will most probably return to the pile shortly but give him a chance to work some real DX. 

If you hear and work some DX (such as long path Africans), ask the pile to wait while you call for more of the same (“EU QRX EU QRX AF AF AF ONLY”).  Give them a few minutes to round up their DX pals and call you.  Some DX openings are very short and the DX that made it through your pile has probably been calling patiently for ages.  Stick to your guns: if after saying AF ONLY you work anyone clearly not in AF, expect to be hounded by yet more rude/ignorant callers.  Ignore callers who only give partial calls - they are usually cheeky queue-jumpers.

Send clearly - not too fast, not too slow - and work on your timing.  You stand a much better chance of getting through if you synchronize with the DX, calling him only when he is listening for new callers. 

Sometimes, delaying your call a bit makes a big difference.

Do not call blindly or out of turn.  Do not send a report unless the DX is calling you and has sent your callsign correctly.  Do not become a pileup kop, shouting at people on the DX station’s transmit frequency. 

Most of all, whatever else happens, stay 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 another cup of tea or walk the dog.   The DX will most likely still be there when you come back, refreshed and ready to play.

There’s more sage advice for pileup kops further below.

Keep your cool! 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 about someone’s callsign, immediately ask the caller to (re)confirm and wait for their response.  Remember, you are in charge. 

Keep to a reasonable, even-tempered speed.

Remain polite and gentlemanly at all times.  Thank the pileup for being patient with you and following your instructions.  Acknowledge them for standing by while you complete a difficult QSO.  Encourage good behaviour (e.g. callers from the correct area if you are working geographically) and ignore the bad (callers from the wrong area).  Never lose your temper on-air.   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 another cup of tea or walk the dog.   The DX will most likely still be there when you come back, refreshed and ready to play.

Remember, everyone, this is only a hobby!

Special pileup tips for digital DXing
in addition to those 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 away 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 and watch the waterfall 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 out too far.  If s