Call Search
     

New to Ham Radio?
My Profile

Community
Articles
Forums
News
Reviews
Friends Remembered
Strays
Survey Question

Operating
Contesting
DX Cluster Spots
Propagation

Resources
Calendar
Classifieds
Ham Exams
Ham Links
List Archives
News Articles
Product Reviews
QSL Managers

Site Info
eHam Help (FAQ)
Support the site
The eHam Team
Advertising Info
Vision Statement
About eHam.net

   Home   Help Search  
Pages: [1]   Go Down
  Print  
Author Topic: Tips for Working a Special Event (1x1) Station?  (Read 300 times)
N2LJD
Member

Posts: 7


WWW

Ignore
« on: December 08, 2004, 10:03:39 AM »

Greetings.

Next year I'm going to be operating as W2N (3/5-3/7/05) & W2A (10/02/05).  Having never been the control operator for a 1x1, wondering if anyone has any tips for successful operation?

73

Joe
Logged
AC5E
Member

Posts: 3585




Ignore
« Reply #1 on: December 08, 2004, 12:15:56 PM »

Pretty much the same as any other contest or special event operation. Since you have a little time I would suggest you work a few contests, such as the 10 Meter contest this weekend.

Generally speaking, try to get plenty of rest before the event, get well hydrated, keep plenty of water available, avoid coffee or other diuretics, and do have a regular operator rotation so you don't sit there with your legs clamped for several hours. Special events should be fun, not make you a candidate for a kidney transplant.

Operating - often slower is faster. Getting it right the first time, correcting errors now, and making sure the other station knows he's in the log are speed makers. Trying to make too many log entries in too little time is a run killer.

So give your call phonetically on every over, give the call you copied back to the calling station along with the report {AD5HG you are 59 with N2A}, and if you wind up with a pileup call for the partials you copied (The 9 call with E, please), other stations with some distinctive characteristic such as "the mobile, the YL," or whatever, will all help sort things out without burning time.

If you can log two to three stations a minute and keep it up you are on a world class pace. Twenty seconds is a long time, but a log entry every fifteen seconds often leads to busted calls, and other time consuming problems.

Hope that helps

73  Pete Allen  AC5E
Logged
WB2WIK
Member

Posts: 20666




Ignore
« Reply #2 on: December 08, 2004, 04:00:30 PM »

Relax and enjoy it!

If you're a good operator, you'll handle it fine.  If not, this is the opportunity to learn to become a better one.

WB2WIK/6
Logged
N6AJR
Member

Posts: 9927




Ignore
« Reply #3 on: December 08, 2004, 04:14:39 PM »

advertise your special function for the call in advance and post some where like on your qrz. call the qsl info, and leave a note here in NEWS and also on qrz in News.. like "joe Smhoe annual qrp amplifier contest" will be using call w3w and qsl through a1bcd or such..
Logged
K0NR
Member

Posts: 9


WWW

Ignore
« Reply #4 on: December 08, 2004, 08:04:51 PM »

How fast you want to go is somewhat personal preference, but always determined by your operating skill. Don't attempt to go so fast that you are missing calls, making lots of errors, etc.

It helps alot if the special event operator is very consistent on how the contact is made. Most operators on the other end will note how you are operating and fall into line. For example, on the first transmission you might give the other station's call, signal report, your name and <over>. On the next and last transmission, thank them for the contact and give the QSL info. This should cue the other guy that the contact is over. Whatever you decide to do, being consistent will really help with the flow.

Bob K0NR
Logged
2E0ESW
Member

Posts: 27




Ignore
« Reply #5 on: August 23, 2005, 12:47:56 PM »

Nice to see you back Pete, I particularly missed your late absence.

Welcome back!!!!!

73
Etienne Swanepoel 2E0ESW
Bude
Cornwall
UK
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!