collected wisdom and lessons learned for the little pistol dan zeitlin, k2ywe (k3au) revised january...

Collected Wisdom and Lessons LearnedCollected Wisdom and Lessons Learnedfor thefor the

Little PistolLittle Pistol

Collected Wisdom and Lessons LearnedCollected Wisdom and Lessons Learnedfor thefor the

Little PistolLittle PistolDan Zeitlin, K2YWE (K3AU)Dan Zeitlin, K2YWE (K3AU)

Revised January 2012Revised January 2012

Dan Zeitlin, K2YWE (K3AU)Dan Zeitlin, K2YWE (K3AU)

Revised January 2012Revised January 2012

Copyright 2006, 2007,2012All rights reservedDan Zeitlin, Annapolis, MDFree use with prior permission

K2YWE Little Pistol 01-2011 - p2

Agenda

• What’s this about?• Who is K2YWE?• Elements of Success• Preparation• Contest Basics (refresher)• Strategy• Station Considerations• Antennas• Software• My favorite Software Features• Operating Tips and “Best Practices”• SO2R• Resources• Summary• Appendix A - Best Practices Collection• Appendix B – Interfaces and Accessories • Appendix C – Selected Contest Loggers


What’s a Little Pistol?

A Little Pistol in this context is

• Low Power

• Single Op

• Modest Antennas Wires, maybe a low Beam NOT big towers and/or stacks


What’s this about?

Objective

• Improved Scores for Little Pistols (LP)

Intended Audience

• Modest low power HF stations

• Parts may apply to VHF/UHF+

How?

• Make the most with what you have

• Adopt successful operating practices


About Dan

• Licensed in 1956 (KN2YWE) Mostly CW. Mixed rag chewing and DXing

• Limited casual contest background Occasional FD and Sweepstakes

• 1996 FD with dyed-in-the-wool contesters Nibbled the bait. Fell in with a bad crowd.

• Little part of “Big Gun” team for a few years Same crowd. Set the hook and reeled me in.

• Little Pistol home station 100W, wires and later a small low tribandersmall low tribander Occasional guest Op elsewhere Encouraging Results

• CARA/PVRC FD team Mostly 80 CW

Boom Mic & FootswitchBoom Mic & FootswitchBoom Mic & FootswitchBoom Mic & Footswitch


Elements of Little Pistol Success

• The Right Frame of Mind

• Preparation

• Practice

• Attention to Detail

• Perseverance

• Learning from Others

My observations are relevant to most successful endeavors


The Right Frame of Mind

QRL!

Don’t forget it is a competition““it's a jungle out there” it's a jungle out there” . . . . . . dede N6TR N6TR

You will not be alone““. . . contesting skill includes the ability to tolerate high . . . contesting skill includes the ability to tolerate high levels of QRM, and if you can't do that, you might as well levels of QRM, and if you can't do that, you might as well hang it up.“ hang it up.“ . . . . . . dede K3ZO K3ZO

Think Big““If you think and act like you’re a big dog, If you think and act like you’re a big dog, you will convince most of the pack that you will convince most of the pack that you are, although you may get bitten you are, although you may get bitten once in a while.” once in a while.” . . . . . . dede K2YWE K2YWE

Don’t forget it is a competition““it's a jungle out there” it's a jungle out there” . . . . . . dede N6TR N6TR

You will not be alone““. . . contesting skill includes the ability to tolerate high . . . contesting skill includes the ability to tolerate high levels of QRM, and if you can't do that, you might as well levels of QRM, and if you can't do that, you might as well hang it up.“ hang it up.“ . . . . . . dede K3ZO K3ZO

Think Big““If you think and act like you’re a big dog, If you think and act like you’re a big dog, you will convince most of the pack that you will convince most of the pack that you are, although you may get bitten you are, although you may get bitten once in a while.” once in a while.” . . . . . . dede K2YWE K2YWE


Preparation

• Have a strategy – write it downProvides baseline guidance Try to optimize within your constraints

Modify as needed in “battle”

• Reassess your strategy during the contest Expect to change the details

Take radical departures only if you have good reason to, like one or more of your baseline assumptions was wrong

“Now the general who wins a battle makes many calculations in his temple ere the battle is fought. The general who loses a battle makes but few calculations beforehand.” . . . Sun Tzu


INSERT key seems to stick!

PreparationGet your act in order before the performance

• Check your set-up well before the start Antennas, Hardware, Software, support files

Set appropriate software defaults

Provide enough time for fixing any problems

• Be well rested for the contest

• Listen day(s) before to get a feel for Condx

• Have a simple means to restart software What did I call this file . . .?

Re-use the same name for the currentcontest files. Rename after the contest.

Skip Next -Contest Basics

Jump to “Strategy”


• Rules are published well in advance

• Valid contacts exchange two-way information Contest rules define the specific information

• Final score is composed of two pieces QSO points – Based on number of valid contacts

• Points per contact may vary

Multipliers – Based on a unique characteristic• Usually location - State, Country, Zone, Grid

Total Score is QSO points times the MultipliersTotal Score = “Q pts” x “Mults”

Same stations may provide multiple Qs or Mults• Contacts on different bands or modes may each count

Contest Basics

31 W6IXB 59 59 SCV32 W5AFX 59 59 STX

31 W6IXB 59 59 SCV32 W5AFX 59 59 STX

Individual contest rules spell everything out, including scoring

Skip Contest BasicsJump to “Strategy”


Scoring Example

Pts/QSO may differ within some contests Might be different by mode, or by local or “DX” QTH

Band QSOsPoints/

QSOQSO

PointsMults

160 2 3 6 280 15 3 45 840 25 3 75 1020 35 3 105 2515 5 3 15 410 2 3 6 2

252 X 51 = 12,852 Total Score

Simple Multi-band contest



Sample Exchange (CQ WW HF Contest)

• “CQ TEST PA0LOU” PA0LOU calling CQ contest

• “K3AU” K3AU responds

• “K3AU 599 14” PA0LOU sends the callsign he is responding to, then exchange of RST and Zone

• “599 5” K3AU sends his exchange

• “TU PA0LOU” Thanks K3AU and waits for next station to call

Results in one “Q” for each station, and a multiplier if the other station’s zone or country has not yet been worked on this band (CQ WW)

Stations try to exchange required info as efficiently as possible



• More Q’s are key to producing higher scores Q’s and Mults are both important but . . .

Q’s fuel the engine, Mults provide the turbo boost

• Operating Time is fixed, so Rate must go up!

• Thus, Concentrate on achieving Higher Rates

• Rate Drivers

• Successful Running is a proven rate generator

Being Heard and Hearing others• At fixed power level, this mainly means better Antennas

Efficiency - Less wasted time in and between QSO’s• Look to Operating Practices and Shack Arrangement

Attracting the other stations• Operating Practices

High Level Thoughts . . .Some reasoning to frame the problem


Strategy

• Class Selection Band(s), modes, assistance, number of Ops, … Leverage your strengths

• Bands and Modes Which, when?

• Propagation What’s best for Q’s and Mults

• ON/OFF times selection Time limits Meals, sleep, “real life” periods

• Operation CQ vs. S&P Rates, Speeds and Timing

Having a game plan pays off during the contest

SOA, MUF,S&P,

rates, snacks . .

.

Q’s, Mults, Bones . . .


• Focus on making the most Q’s Block out expected S&P and Run times, ground rules

Balance with occasional short checks for Mults

• Base primarily on expected Propagation Range of prediction tools are available

• QST or CQ tables – simplest

• Models – most complex, better

• “Rules of Thumb”

Temper predictions with your own observations Gray Line info can help real-time, especially on 160m and 80m

• Allow for time-of-day considerations What’s going on elsewhere in the world

StrategyRemember that maximizing Q’s is primary to success


• Choose OFF times at lowest expected Q rates Base on your own or other stations’ history

Don’t forget minimum OFF time rules

• Try to ensure using your full time allotment

• Allow possibility you may want a late slot Don’t get caught short of time at the end

I usually leave a late half-hour insurance slot

It’s tricky, considering the bullet above

• Sync with your personal needs (duhh)

ON/OFF TimesMake the best use of your time


• Set an average rate you want to achieve (Total Q’s) / (Operating Hrs)

• Set minimum rates you’ll accept Acceptable rate will vary over the contest period

• Include minimum rates in your Strategy

• Make a change if you drop below the Rate Change Freq, Band, Mode

Swap Running and S&P

Chase some Mults Change your shirt

Rates RulesSetting Rate Rules helps you achieve QSO goals

1,000/24 =4000-04z 6004-08z 4508-12z 30 12-16z 4016-20z 5020-24z 25

1,000/24 =4000-04z 6004-08z 4508-12z 30 12-16z 4016-20z 5020-24z 25

Change Something !


• Be thoroughly familiar with your software A contest is not the time for first trial

Gain familiarity in day-to-day use

Exploit helpful features

Use practice programs and modes

Modify settings to suit your style

• Be comfortable with Run techniques Practice with a simulator

Try to operate “run style” (5NN MD DAN BK . . . TU)Pick a day with a good conditions on your best band

Use the Best Practices mentioned later in this presentation

Contest Hound Practices with CT

PracticeIt may not make you perfect, but it will make you better!


Station Improvements

• Assess Station Strengths and Weaknesses Take band by band inventory based on performance history

• Attack Weaknesses with biggest payoffs first Incrementally fill in the holes

Expect Antennas to rank high

Don’t forget to pick “low hanging fruit”

• Assess your Operating Practices Bounce your operation against the Best Practices (later)

Adjust accordingly

• Improved Antennas & Running payoff most But every improvement counts – they all add up

Put method behind your madness


My Experience

• Operation Better exploited software features (Bandmap, SCP, …)

Discovered and incrementally adopted “Best Practices”

Biggest single payoff in Operation was Running

• Started Running – Had assumed not possible for an LP

• My running rates improved with experience and trials

• Station Improved antennas – eventually migrated to monobanders

• None exotic – Delta loop, bent dipole, and lazy U wires

• Eventual addition of small Yagi made a big difference

Made shack changes for better” operating efficiency” . . .

Performance improved with incremental changes


“Better Operating Efficiency”

Boom Mic & Footswitch

Life is

Good!

Footswitch & Prop

Mic Prop

No Help!

Ugh!


Station Improvements at K2YWE

• Footswitch Frees hands for undisrupted keyboard use CW - Quick T-R transition without listening to QSK noise

• Boom or Headset Mic Less fatigue, freedom to move, respond to local “QRM” . . .

• Antenna Switching Quick band changes. Replaced connector swaps.

• Added or Improved Antennas More chance to sustain Run, snag S&P Q’s with less calls Make more “second” tier QSOs

• “Sensible Rearrangement” of Equipmentuipment More efficient, less effort to operate . . .

Improvements aimed at higher rates


Antenna Improvements

• What assets exist to hang antennas on?

• Use all the property lines to full advantage

• Try to design a system using monobanders

• Add/change antenna to help your weakest band

• Consider fixed antenna with gain to EU or West

• Enable a new band, like 160m for New Mults and more Q’s during slow times

• Put up even a minimal Yagi if possible

Be innovative within your constraints


Multi-band270 ft Horiz Loop

Two 40m Deltas Two 40m Deltas and160/80m Vertical(s)

vg vg vggd gd gdok ok okp p pvp vp vp

160 80 40 20 15 10 160 80 40 20 15 10 160 80 40 20 15 10

40m Delta, 80m Dipole, 40m Delta, 80m Dipole160m Lazy-U 160m Lazy-U, C3SS

vg vggd gdok okp pvp vp

160 80 40 20 15 10 160 80 40 20 15 10

Antenna Growth at K2YWEBegan with Multi-band loop with uneven performance and a lot of tuning.Made incremental improvements to fix deficiencies

Current Systemwith mono-banders gives better and more balanced performance


K2YWE Antenna FarmetteSqueezed in three wire monobanders and a 12’ boom tribander

You can sure cram a lot in 1/5th acre, XYL willing!

80m Droopy-End Dipole

125’

75’

40m

In

v D

elt

a

160m “U”

Force 12 C3SS

(12’ boom 24ft max element)

40m Delta serves as 160-80m Rx only and Aux Ant for 20-15-10m Small tri-bander

on a 45’ AB-577 “rocket launcher”


Software (S/W)

• Use your Radio and Keying interfaces Build or buy and integrate them if you haven’t already (Appendix A) It’s very hard to make and sustain high rates without them

• Recommended S/W Setup (CT keywords SHOWN)

WORKDUPES - BANDMAP & ANNOUNCE Windows CORRECT call signs - RATE Window Super Check Partial - SCP Window Stop on auto CQ - SCORE Window

• Spotting Network? View as a strategic decision Can be a valuable asset, especially in S&P Remember caveats about wasting time chasing Mults Does not alleviate you from confirming all entries

Use a contest-oriented program and set it up to facilitate high rates


Software FeaturesMost Useful to Me

Skip All butBandmap

Skip all AllDetail- Jump to

Best Practics


Dupe Alert (CT screen)

Check for duplicate entries is automatic upon callsign entry

TI3TLS

Alert as DUPE with time & date of previous QSO

TI3TLS

Skip All butBandmap


Matches callsign fragments against database created from recent contest logs and current logged contacts . . . anywhere in the callsign

Check Partial Call (CT screen)

Call fragments yield possible known contester callsigns

Skip All butBandmap


the Bandmap (CT and N1MM screens shown)

• Tells you who is on what frequency, if worked before, and if needed as QSO or multiplier

• Data is entered by hand or

automatically from spots

• Map updates periodically

to expunge stale data

• Own frequency can

be ‘centered’ or scrolled

The bandmap saves time in Search & Pounce mode

Skip BandmapJump to

SO2R


the Bandmap - CT

21:24:48

Current TransceiverFrequency

NeededMult in White

NeededQSO in Blue

AlreadyWorkedin Black

FrequencyTime Entered into BandmapCall

Radio tuned to N4CWNo # or on black bar indicates Worked beforeGoing to tune up to K2YWE, a needed QSO

Radio tuned to N4CWNo # or on black bar indicates Worked beforeGoing to tune up to K2YWE, a needed QSO

*


Radio tuned up to K2YWE and blue indicates Needed QSOIntend to work K2YWE

Radio tuned up to K2YWE and blue indicates Needed QSOIntend to work K2YWE*

the Bandmap - CT

21:25:03


NeededMult in White

FrequencyTime Entered into BandmapCall

NeededQSO



21:25:15Worked and logged K2YWEStatus changed to ‘Worked’ and time updatedIntend to next work WA6AQQ, a needed Mult

Worked and logged K2YWEStatus changed to ‘Worked’ and time updatedIntend to next work WA6AQQ, a needed Mult

the Bandmap - CTFrequency

Time Entered into BandmapCall

Updated Time & Status

NeededMult in White

AlreadyWorkedin BlackCurrent

TransceiverFrequency


21:25:38

the Bandmap - CT

Radio tuned up to WA6AQQ# and red bar indicates Needed Mult

Radio tuned up to WA6AQQ# and red bar indicates Needed Mult


Frequency Call

NeededMult


Next NeededQSO in Blue

Time Entered into Bandmap


Tips and Best Practices

“Best Practices” are what successful competitors say works for them.


Some CW Tips* - CW

• Do not be intimidated by stations too fast for you to copy.

Start with the slower stations higher in the band.

Don't worry if you have to hear a call several times to get it.

As the contest goes on your will improve!

• Call CQ high in the band at a speed comfortable for you.

• Don’t be shy about sending QRS.

Most stations will slow down to your speed.

• Try moving frequency a bit if you can’t seem to be heard.

Often receiver bandwidths in a crowded band are set very narrow.

Don’t let your code speed keep you from enjoying CW contests

*Some tips are courtesy of the 1999 YCC “Cookbook”


Some Phone Tips

• Use conventional or unmistakable phonetics “Duck Soup” are poor phonetics for “D S”

Use Standard or “Common Use” phonetics (countries, cities . ..)

• Maintain a “friendly sense of urgency” in your QSOs

Chattiness will slow your rate and lose you contacts.

• Do not be intimidated by stations talking fast or unintelligibly.

Firmly ask until you get all the exchange info. Use “again?”

It is usually better to ask for one piece of missing info at a time.

• Listen to what is on your frequency when working split.

If you can hear it, you can better time your call or defer until later.

Apply these basic Phone tips for starters


• Every point counts! There’s no such thing as “not worthwhile” When things are slow, call for “anybody”

• A rule of thumb strategy Work bands that may close first. Move with propagation. This often means 10-15-20 in a.m. then 40-80-160 later on. Try running rather than chasing spots when high bands are open. Go after the Mults when 20 has slowed, but 40 hasn't opened yet.

• Keep multipliers in mind “Move” Multipliers if you can do so efficiently Have frequencies on each band set up for quick jaunt Balance the effect on rate and total score when chasing Mults

Best Practices Basics* - OverallOverall

*Some of these tips are courtesy of the 1999 YCC “Cookbook”


The Master Callsign Data Base is not the Bible

Verify the callsign of the station you're working BV6U and 5C8N are not real callsigns (6V6U and HC8N).

Don't log them that way.

Always HEAR the call that the station is signing and log it correctly.

Best Practices Basics* - OverallOverall - continued

*Some of these tips are courtesy of the 1999 YCC “Cookbook”

You mean that’s a busted call?


“ “fresh meat”fresh meat”• S&P rates can be very high early in the contest

Everyone is fofor you. You can quickly hop fromquickly hop from station to station with little fear of Dupes. You are usually safe to callsafe to call first and fill-in the call at the QSO end.

• Use early S&P to find a spot to CQ You can maintain a high rate while searching for a clear spot. It beats the alternative of establishing a frequency before the Test

• Be sure to try CQing late in the contest You will be “fresh meat” to many that have been CQing all along. They will be seeking to squeeze out the last few QSOs.

• Repeat only what is missing when asked for a fill Repeating known parts wastes time and possible “clear times.”

• QRL? . . .

Best Practices Basics - OverallOverall - continued


Do you really want to ask QRL?

“Can anyone honestly believe that there is a single KHz anywhere in the relevant portion of the 20 meter band that is NOT in use somewhere in the world during the CQWW?” . . . de K3ZO

One Approach . . . Pick a “clear” spot and CQ without “QRL?” You will only invite others to take the frequency by asking.You’ll find out quickly enough if the Freq is in use by calling CQ.This is very controversial. Many hams feel that not asking is rude. You Decide. Use “QRL?” if you have any doubts or are thin-skinned!


Best PracticesGeneral

• Use K3ZO's "Rule of TWICE" – modify “twice” as sensible

If you can't get a station after calling TWICE, move on

If he doesn't ID after transmitting TWICE, move on

• Don’t waste time repeatedly calling DX that has moderate Sigs when the band is otherwise quiet from their part of the world

They are probably “opening the band” with lots of ERP

• Enable and use the band map in your logging software

• Insist on fills until you get all the info. Use “Again?” on phone

Don’t log the QSO without complete info. “Sorry, No QSO”

• Keep the width of an SSB signal in mind Be sure you are away enough from strong stations running not to

be covered by a pileup you can’t hear


Running

• Use the widest IF bandwidth you can stand Less chance to miss off-freq callers, especially on CW

• Don’t break a run to pull one station through Your rate will suffer if you take too long

You will drive away impatient waiting stations

• Use only a quick ‘Thanks’ if stations are waiting They know your call. Don’t waste time on it.

Throw in your call every few Q’s for the uninitiated

• Send complete exchange with a partial call Nearly all Ops will correct you, good ones without a missing a beat

Fix the call during his transmission

more Best Practices . . .


more Best Practices . . .Running - continued

• Call CQ when bands are dead for the day or worked out

• Call CQ when the band is active if you are able to find a frequency and hold it

• Always work Dupes ("WORKDUPE" in CT) You might not be in his log

• If you can't drag a station's call through after trying TWICE, ignore him and start calling CQ again. This is part of K3ZO's "Rule of TWICE." Modify "TWICE" to suit

your station capabilities and contest circumstances.

• Enable call sign correction in your software. This will send the corrected call as part of your goodbye message ("CORRECT" in CT)



• Speed up if your run is being sustainedThis is especially true in contests like SS where the exchange includes your call sign. Slow back down appropriately

• Hit the SEND key as soon as the call is in your head. Finish typing in the log during the automated response or while talking

Some programs can do this automatically after n characters

• Move Multipliers to other bands if you have the time Pick frequencies in advance



• If another station calls CQ on your frequency, try "QRL" or "Frequency in use, QSY"

• Don't engage in extended frequency fights

If QRL/QSY fails, it almost always pays to move

Sometimes you can move up or down a bit in order to lessen the QRM and still hang on to "your" frequency

• NEVER NEVER NEVER acknowledge a "jammer". NEVER. Just keep your pace, and don't change your tone of voice on phone or even synchronize your calls to his QRM.

Often throwing in a few fake Q’s will discourage the jammer

The Complete Best Practices CollectionAppears in Appendix B

The Complete Best Practices CollectionAppears in Appendix B


A Word About Single Op 2 RadioEveryone has their own idea of an efficient SO2R layout . . .

K1PT S02R Setuptwo radios, two computers “Special” contest switch at

DF0WA

S02Rone computerAn earlier two radio

setup(no PC)


• It’s easy for SO2R to be a distraction

• KISS (Keep It Simple Stupid) is key Start with a simple setup Use SO2R only when things are slow

• CQ #1, S&P #2 or Alternate CQs• Modify your setup operation with experience

• Many top Ops swear by it (i.e. N6TR) Has potential to add significantly to your score

• Some don’t use it at all (i.e. K3ZO)

p.s. I’m at stage one – few or no SO2R Q’s per contest - dbz

SO2RSave SO2R until you have nearly exhausted other improvements


• If the IF is being "pumped" by stations nearby (and in the AGC bandpass) trying running with

your AGC OFF”. . . de K3RA

• Noise limiters can cause noise or clicks when “pinged” by strong adjacent signals. Turn off

unless you have no choice.*

Miscellaneous Receiver TricksHints and Kinks that you may not have considered

*On the Yaesu 1000MP, turn the adjustment knob full CCW, even when both NLs are off.


Local PVRC ResourcesThere is ample opportunity and willing help available locally

• Multi-Op Station Opportunities WX3B in Frederick - Jim Nitzburg

• Help (order not significant!) K3RA – Rol Anders KE3Q – Rich Boyd KD4D – Mark Bailey K2YWE – Dan Zeitlin K3ZO – Fred Laun W3LPL – Frank Donovan ND3F - Brian, VHF+

• Single Op Opportunities Often “unused” stations are available Post a query on the PVRC reflector


Internet Links

“includes non-contest loggers

Contest Organizations, Calendars, Info, and Sponsors Potomac Valley Radio Club (PVRC) pvrc.org Contesting.Com contesting.com Frankford Radio Club (FRC) frc-contest.org CQ Magazine (CQWW, WPX, and others) cq-amateur-radio.com National Contest Journal – NCJ (QSO parties, Sprints, more) ncjweb.com ARRL (Sweepstakes, Field Day, DX, UHF/VHF, more) arrl.org/contests SM3CER Calendar sk3bg.se/contest WA7BNM Calendar hornucopia.com/contestca

Contest Logging Programs CT & CTWin k1ea.com TR Log, TR4W tr4w.com Win-Test win-

test.com Writelog writelog.com N1MM pages.cthome.net/n1mm\


• Prepare and pay attention to detailPrepare and pay attention to detail Remember Sun Tzu Remember Sun Tzu

• Adopt proven Best PracticesAdopt proven Best Practices Don’t be afraid to experiment. Keep what works for you.Don’t be afraid to experiment. Keep what works for you.

• Run, big dog, runRun, big dog, run Try to Run if at all possibleTry to Run if at all possible

• Start now making incremental changesStart now making incremental changes Make an improvement list and work it downMake an improvement list and work it down

• Strategies are importantStrategies are important Pick and plan the contests. Use the plan for guidance.Pick and plan the contests. Use the plan for guidance.

• There are lots of resources to help youThere are lots of resources to help you Just askJust ask

“ “ It’s not the size of your station, it’s how you use it! ”It’s not the size of your station, it’s how you use it! ”

Little Pistols Little Pistols cancan successfully compete successfully compete

You You cancan do well with a modest station do well with a modest station


Appendix A - Best Practices Collection

Appendix B – Interfaces and Accessories Appendix C – Selected Contest Loggers

Appendices


Best Practices Collection

Appendix A


Best Practices Collection

BEST PRACTI CE RATI ONALEGeneral Operating1 Assume a Big Dog attitude. • If you act like a big dog, most will believe you.

If they bite back painfully, you can find other turf.2 Maintain a “friendly sense of urgency” in your

QSOs• Chattiness will slow your rate and lose you contacts.

3 Always work Dupes (in CT “WORKDUPE”) • You may not be in their log • It usually takes more time to rebuff than work.

4 Enable and use the bandmap feature of your logging software.The Bandmap allows you to mark stations on the fly.

• If you need to check back later, the bandmap will have the call sign and frequency noted for you. • You’ll waste less time waiting for stations to ID or on calling Dupes.

5 In general, use K3ZO's "Rule of TWICE." Modify "TWICE" to suit your station capabilities and contest circumstances:• If you can't get a station after calling TWICE, move on. • If he doesn't ID after transmitting TWICE, move on.

• Your time can be better spent increasing your rate. • A Multiplier is usually not be worth the lost Q's spent trying. • You can put him in the bandmap to check back later.

BEST PRACTI CE RATI ONALEGeneral Operating1 Assume a Big Dog attitude. • If you act like a big dog, most will believe you.

If they bite back painfully, you can find other turf.2 Maintain a “friendly sense of urgency” in your

QSOs• Chattiness will slow your rate and lose you contacts.

3 Always work Dupes (in CT “WORKDUPE”) • You may not be in their log • It usually takes more time to rebuff than work.

4 Enable and use the bandmap feature of your logging software.The Bandmap allows you to mark stations on the fly.

• If you need to check back later, the bandmap will have the call sign and frequency noted for you. • You’ll waste less time waiting for stations to ID or on calling Dupes.

5 In general, use K3ZO's "Rule of TWICE." Modify "TWICE" to suit your station capabilities and contest circumstances:• If you can't get a station after calling TWICE, move on. • If he doesn't ID after transmitting TWICE, move on.

• Your time can be better spent increasing your rate. • A Multiplier is usually not be worth the lost Q's spent trying. • You can put him in the bandmap to check back later.

BEST PRACTI CE RATI ONALEGeneral Operating


Best Practices Collection (con’d)

BEST PRACTI CE RATI ONALEGeneral Operating - continued6 Do not waste time repeatedly calling DX stations

that have moderate signals when the band is otherwise quiet from their part of the world. This is likely to happen when big guns are just “opening the band” or “keeping it open.” Try another time.

• Many stations running high power will be heard when propagation is poor, but will not hear you despite elaborate antennas.• Remember that 1.5kW vs. 100W is about the difference between S-7 and S-3.

7 Try moving frequency a bit if you can’t seem to be heard.

• Often receiver bandwidths in a crowded band are set very narrow.

8 Move Multipliers if you have the time. • Pick frequencies in advance.

• Quick way to gain Multipliers • Many Ops will go with you.

9 Try sending only the missing or wrong part when correcting your call or exchange (“Fill”). • The response to K3A? should be “ABC” (several times if necessary) since the K3 wasn’t in question. • Similarly, in SS if the query is for your Check, avoid sending the entire exchange

• The time you spend sending known info is wasted. • You may squander a clear interval or QSB peak on resending known information.

BEST PRACTI CE RATI ONALEGeneral Operating - continued6 Do not waste time repeatedly calling DX stations

that have moderate signals when the band is otherwise quiet from their part of the world. This is likely to happen when big guns are just “opening the band” or “keeping it open.” Try another time.

• Many stations running high power will be heard when propagation is poor, but will not hear you despite elaborate antennas.• Remember that 1.5kW vs. 100W is about the difference between S-7 and S-3.

7 Try moving frequency a bit if you can’t seem to be heard.

• Often receiver bandwidths in a crowded band are set very narrow.

8 Move Multipliers if you have the time. • Pick frequencies in advance.

• Quick way to gain Multipliers • Many Ops will go with you.

9 Try sending only the missing or wrong part when correcting your call or exchange (“Fill”). • The response to K3A? should be “ABC” (several times if necessary) since the K3 wasn’t in question. • Similarly, in SS if the query is for your Check, avoid sending the entire exchange

• The time you spend sending known info is wasted. • You may squander a clear interval or QSB peak on resending known information.




BEST PRACTI CE RATI ONALEGeneral Operating - continued10 Listen to what is on your frequency when

working split. • If you can hear it, you can better time your call or defer until later.

11 Call CQ when the band is active if you are able to find a frequency and hold it.

• You will usually beat your S&P rate without difficulty. • An exception is the start of the contest when everyone is new for you, and your S&P rate can be very high.

12 Call CQ when the bands are dead for the day or worked out near the end of the contest.

• That’s when the stations that have been CQing will S&P for “fresh meat.”

13 Do not inquire if the frequency is busy before CQing. • You’ll find out soon enough if it is.

• QRL? announces to others that it’s clear at your end.• Someone else may well jump in and CQ.

BEST PRACTI CE RATI ONALEGeneral Operating - continued10 Listen to what is on your frequency when

working split. • If you can hear it, you can better time your call or defer until later.

11 Call CQ when the band is active if you are able to find a frequency and hold it.

• You will usually beat your S&P rate without difficulty. • An exception is the start of the contest when everyone is new for you, and your S&P rate can be very high.

12 Call CQ when the bands are dead for the day or worked out near the end of the contest.

• That’s when the stations that have been CQing will S&P for “fresh meat.”

13 Do not inquire if the frequency is busy before CQing. • You’ll find out soon enough if it is.

• QRL? announces to others that it’s clear at your end.• Someone else may well jump in and CQ.




BEST PRACTI CE RATI ONALEGeneral Operating - Phone14 Use conventional or unmistakable phonetics.

• “Duck Soup” are poor phonetics for “D U”• The whole idea of phoenetics is to eliminate ambiguity by standardization. • Non-native english speakers may not understand a "home made" alphabet.

15 Do not be intimidated by stations talking fast or unintelligibly. • Firmly ask until you get all the exchange info. Use “again?” • It is usually better to ask for one piece of missing info at a time.

• The QSO is not worth anything to you if it's wrong (busted).• "Again" is quick and universally understood.

BEST PRACTI CE RATI ONALEGeneral Operating - Phone14 Use conventional or unmistakable phonetics.

• “Duck Soup” are poor phonetics for “D U”• The whole idea of phoenetics is to eliminate ambiguity by standardization. • Non-native english speakers may not understand a "home made" alphabet.

15 Do not be intimidated by stations talking fast or unintelligibly. • Firmly ask until you get all the exchange info. Use “again?” • It is usually better to ask for one piece of missing info at a time.

• The QSO is not worth anything to you if it's wrong (busted).• "Again" is quick and universally understood.


S



BEST PRACTI CE RATI ONALERunning16 Use the widest IF bandwidth you can stand • Less chance to miss off-freq callers, especially

on CW 17 If another station calls CQ on your frequency

and fails to respond to your QRL-QSY message, carry on for a while to see if he leaves. But, don’t do this for very long.

• Even though he is not hearing you, if you are being heard by others he may not get many responses and may give up after a few minutes. No one likes to waste time.

18 Don’t engage in extended frequency fights • Try “QRL” or “Frequency in use, QSY.” If that fails, it almost always pays to move. • Sometimes you can move up or down a bit in order to lessen the QRM and still hang on to “your” frequency.

• It costs you QSO time. • You may be in QRM at the other end.

19 Don’t break a run to pull one station through • Your rate will suffer if you take too long • You will drive away impatient waiting stations

20 If you can't drag a station's call through after trying TWICE, ignore him and start calling CQ again. • This is part of K3ZO's "Rule of TWICE." Again, modify "TWICE " to suit your station capabilities and contest circumstances.

• Running has to do with how fast you can accurately pull a call and get it into the log. You don’t want your rate to slow down or other callers to lose interest. • Equally important, on a crowded band you have to transmit a lot to keep "your" frequency clear.

BEST PRACTI CE RATI ONALERunning16 Use the widest IF bandwidth you can stand • Less chance to miss off-freq callers, especially

on CW 17 If another station calls CQ on your frequency

and fails to respond to your QRL-QSY message, carry on for a while to see if he leaves. But, don’t do this for very long.

• Even though he is not hearing you, if you are being heard by others he may not get many responses and may give up after a few minutes. No one likes to waste time.

18 Don’t engage in extended frequency fights • Try “QRL” or “Frequency in use, QSY.” If that fails, it almost always pays to move. • Sometimes you can move up or down a bit in order to lessen the QRM and still hang on to “your” frequency.

• It costs you QSO time. • You may be in QRM at the other end.

19 Don’t break a run to pull one station through • Your rate will suffer if you take too long • You will drive away impatient waiting stations

20 If you can't drag a station's call through after trying TWICE, ignore him and start calling CQ again. • This is part of K3ZO's "Rule of TWICE." Again, modify "TWICE " to suit your station capabilities and contest circumstances.

• Running has to do with how fast you can accurately pull a call and get it into the log. You don’t want your rate to slow down or other callers to lose interest. • Equally important, on a crowded band you have to transmit a lot to keep "your" frequency clear.




BEST PRACTI CE RATI ONALERunning - continued21 Use only a quick "Thanks" or "TU" without your

call sign or QRZ if stations are waiting to work you (You heard multiple callers). • Throw in your call once every few Q’s for the uninitiated. • Keep it up until there are no more responses, then build back to your “full” QRZ message and CQ. • If you get no response after working the first station this way, try sending your call and TEST” before resuming to a full CQ.

• Most waiting stations will know your call. Don’t waste time on it.• Minimizing the time stations have to wait for you will help to keep the impatient ones hanging around and will increase your QSO rate.

• Less experienced contesters may not realize you are waiting for them. “TEST” will alert them you are ready for another station to call.

22 When the call sign of a responder is questionable, send a complete exchange using the questionable call. Then correctit during his exchange transmission.• You can use SCP to help guess incomplete calls first round. • Make sure you have it right before you let him go.

• Nearly all stations will correct you on their transmission, good Ops without a missing a beat. • It saves the time of an extra exchange devoted only to getting the call sign right. • You can always revert to “normal” means if this practice fails.

BEST PRACTI CE RATI ONALERunning - continued21 Use only a quick "Thanks" or "TU" without your

call sign or QRZ if stations are waiting to work you (You heard multiple callers). • Throw in your call once every few Q’s for the uninitiated. • Keep it up until there are no more responses, then build back to your “full” QRZ message and CQ. • If you get no response after working the first station this way, try sending your call and TEST” before resuming to a full CQ.

• Most waiting stations will know your call. Don’t waste time on it.• Minimizing the time stations have to wait for you will help to keep the impatient ones hanging around and will increase your QSO rate.

• Less experienced contesters may not realize you are waiting for them. “TEST” will alert them you are ready for another station to call.

22 When the call sign of a responder is questionable, send a complete exchange using the questionable call. Then correctit during his exchange transmission.• You can use SCP to help guess incomplete calls first round. • Make sure you have it right before you let him go.

• Nearly all stations will correct you on their transmission, good Ops without a missing a beat. • It saves the time of an extra exchange devoted only to getting the call sign right. • You can always revert to “normal” means if this practice fails.




Got More?

BEST PRACTI CE RATI ONALERunning - continued23 Enable call sign correction in your software

(“CORRECT” in CT) . This will send the corrected call as part of your goodbye message.

• Stations want assurance you have logged them correctly. This will keep them from asking QSL?

24 Speed up if your run is being sustained. This is especially true in contests like SS where the exchange includes your call sign. Slow back down appropriately.

• Stations waiting will usually know your info. • More stations will be inclined to wait for shorter times.• Your rate will go up with speed (duh).

25 Hit the SEND key as soon as the call is in your head, and finish typing it into the log during the automated response or while talking.

• If your fingers are like mine, they slightly lag my brain so that I am still typing when the other station stops sending. • This Best Practice reduces the lag between when the other station finishes calling and when you respond. The typing and SENDing overlap increases rate.

26 When running, NEVER NEVER NEVER acknowledge a "jammer". NEVER. Just keep your pace, and don't change your tone of voice on phone or even synchronize your calls to his QRM.

• With no response, he can't be sure he is even bothering you, and it isn't any "fun" for him if he doesn't get a reaction.

BEST PRACTI CE RATI ONALERunning - continued23 Enable call sign correction in your software

(“CORRECT” in CT) . This will send the corrected call as part of your goodbye message.

• Stations want assurance you have logged them correctly. This will keep them from asking QSL?

24 Speed up if your run is being sustained. This is especially true in contests like SS where the exchange includes your call sign. Slow back down appropriately.

• Stations waiting will usually know your info. • More stations will be inclined to wait for shorter times.• Your rate will go up with speed (duh).

25 Hit the SEND key as soon as the call is in your head, and finish typing it into the log during the automated response or while talking.

• If your fingers are like mine, they slightly lag my brain so that I am still typing when the other station stops sending. • This Best Practice reduces the lag between when the other station finishes calling and when you respond. The typing and SENDing overlap increases rate.

26 When running, NEVER NEVER NEVER acknowledge a "jammer". NEVER. Just keep your pace, and don't change your tone of voice on phone or even synchronize your calls to his QRM.

• With no response, he can't be sure he is even bothering you, and it isn't any "fun" for him if he doesn't get a reaction.



Interfaces and Accessories

Appendix B


Can be from rig or computer. RS-232, parallel, or discretes

Switch Relays and Point Rotors

Antenna & Rotor

TNC or Internet using RS-232 cable or no H/W at all (Telnet, etc)

Annunciate and track needed Mults and QSOs

Spots

Varies with DVP type, but interface itself is not complicated

Send CQ and Exchanges with DVP or card

Voice “Keying”

Simple interface, usually to parallel port

Send CQ, Exchanges, keyboard CW, paddle CW

CW Keying

Varies from RS-232 cable alone, to simple electronic interfaces

Track & control Freq and Mode, maintain Bandmap

Radio

ComplexityFunctionalityInterface

Hardware InterfacesH/W interfaces vary in complexity

Plans and parts for home building are readily available


Interface Issues

• Many radios use RS-232 or TTL interfaces

• Some programs use RS-232 and/or Parallel ports

• Most newer computers don‘t have those interfaces You may need USB to RS-232 or TTL converter(s)

Optionally, you may find suitable multi-I/O cards

Check with other users to see what brands and types work

• Some programs or OS can’t handle real-time CW keying You may need specialized keying interfaces, like Win-Key

Check with other users to see what works

• Older Voice Keyers may use RS-232 or Parallel portsif you want to control them with the logging program

Some loggers, like N1MM, use the computer’s sound card

New computers and Operating Systems introduced complications


1K2N2222, 2N2219 . . .

1K2N2222, 2N2219 . . .

P/O LPT1

Typical Parallel Port Keying Interfaces

DVP and Band Data discrete outputs are also available on parallel ports.10K

PADDLE A 12

PADDLE B 13

PADDLE CENTER 14KEYER

PADDLE

GND 18

STROBE 1

KEY DRIVE 17

Low-levelpositivePTT to rig.Grounded onPTT keyed.

Low-levelpositive centerkeying to rig.Grounded onkey down.

GND 18

STROBE 1

PTT DRIVE 16

0.01uF

0.01uF


Opto-Isolated Interfaces

DVP and Band Data discrete outputs are also available on parallel ports.

GND 18

STROBE 1

PTT DRIVE 16 Low-levelpositivePTT to rig.Grounded onPTT keyed.

10KPADDLE A 12

PADDLE B 13

PADDLE CENTER 14KEYER

PADDLE

GND 18

STROBE 1

KEY DRIVE 17

P/O LPT1Low-levelpositive centerkeying to rig.Grounded onkey down.

1K

1K

Replacing transistors with Optos can improve RF immunity

4N25, 4N35, 4N37 …

4N25, 4N35, 4N37 …

0.01uF

0.01uF


Typical Serial Radio Interfaces

Many older Rigs, especiallyYaesus, need level translation

Most newer Rigs only need a simple cable

to PC to TransceiverRS-232 to TTLRS-232 to TTL

TTL to RS32TTL to RS32

+/- 12VRS-232

5v / 0v TTL

to PC to TransceiverRS-232+/- 12VRS-232

+/- 12VRS-232


MAX-232 IC 5V/RS-232 CAT Interface

For older Yaesu and other rigs with 5V TTL I/O


Discrete 5V/RS-232 CAT Interface

Transistors replace IC as TTL/RS-232 level-shifters


Some inexpensive foot switches

The one I use(cheap)

$ 8.70

$ 6.95

Best Buys, Baynesville (Balto) and other electronics stores also have inexpensive foot pedals meant for games or music.


Selected Contest Loggers

Appendix C


Popular Contest Logging Programs

Similar capabilities with varying implementations

All run under Windows OS• Need varying amounts of learning to fully utilize

CTWin (Free) – Grandaddy of them all• Windows character mode version of DOS program.

TR4W (Free)• Very flexible. Behavior taken from popular DOS program.

Writelog ($)• Popular Windows full-featured contest program.

Win-Test ($)• Many features and options. Easy transition for CT users.

N1MM (Free) • Most popular Win logger. Continuous open source development


Popular Contest Programs (con’d)

Contesting-specific with advanced features

• Band Maps with S&P “point & shoot”

• SO2R Support

• Spotting through a Telnet connection

• Radio, CW & voice keying, and rotator Interfaces

• Sound card support all with External DVP control most with varying degrees of Sound Card Voice some with sound card Receive recording

• Varying levels of RTTY and PSK31 support are provided Most generate and read digital modes using the sound card Some only log functions

Facilitate operating, logging, and exploiting opportunities


CTWin by K1EA

Uses Windows character mode. Minimal system required.

• Win version with same features as original premier CT logger Includes extensive set of utilities

• Contest support files actively maintained by AD1C & WA1Z No longer supported by K1EA User Group support

• Supports all major contests and a few others No new contests to be added. Limited user-defined contest capability

• RS-232 and LPT I/O USB with converter

• Controls some voice keyers*

• Free!

Win version of first serious contest logger, still in wide use

Not generally recommended for new starts

because new contests are not being added, but

• Good if you have old computer hardware

• Good to know as guest Op in existing station

*SM3WMV S/W Voice Keyer


TR4W by UA4WLI

• Small and fast 100% Windows API code Only 100,000 lines of code in 160KB of memory

• Win version with same features as successful TRlog by N6TR N6TR provided TRlog source code as basis Continuously adding more features

• S&P/Run Mode Adaptive

• Superior sound card voice support

• Over 140 supported contests

• RS-232, LPT, USB support USB I/O includes log backup

• Free!

New Win version of mature world-class adaptive contest logger


Writelog by Contesting Software, LLC

• Efficient code with minimal processing and memory requirements

• Requires only one window

• 110 supported contests

• Sound card voice

• RS-232, LPT I/O USB with converter

• $30 (updates same) Prev ver. available @ $18

Mature written-for-Windows high performance contest logger


Win-Test by F5MZN

• Efficient code with minimal processing and memory requirements

• Strong CT keystroke emulation

• Over 100 supported contests


• RS-232, Parallel, USB support

• ~$65 (50€)Proceeds support Radio Amateur Club de Kourou contest activities, including FY5KE (French Guiana).

Mature written-for-Windows high performance contest logger


N1MM by N1MM et. al. (N1MM, N2AMG, K3CT, N2IC, NA3M)

• Cooperative project with multiple participants/coders. Over 200,000 lines of code and growing Mainly Visual Basic & Access

• Runs on 1GHz PIII + 512K RAM

• Multiple Windows

• 110 supported contests Allows User-Defined contests


• RS-232, LPT I/O USB with converter

• Free

Newest and most popular Windows contest logger


• Single Window

• 41 supported contests 21 +20 State QPs


• RS-232, Parallel, USB support

• Limited Band Map and Spot Window – limited utility Prefix only, no indicators (dupe etc), no band or mode filtering . . .

• No Partial Call Check except in own log – No SCP, limited utility

• Can’t work Dupes – it’s important to work dupes

• No SO2R support

• Excellent personal customer service But updates may be slow

• $39 all programs or or $ 7* each contest separately

N3FJP by N3FJP [Info Only – Not Recommended]

Basic contest logger – Easy, but lacks important functionality

* network version $12

collected wisdom and lessons learned for the little pistol dan zeitlin, k2ywe (k3au) revised january...

Documents