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] 2 Next   Go Down
  Print  
Author Topic: call cq but no replies  (Read 714 times)
KD4VSI
Member

Posts: 19




Ignore
« on: August 02, 2007, 03:16:10 PM »

I've finally gotten brave enough to call cq using the code. I found a clear frequency at 7.053 and gave it a try.....for about 30 minutes. Then I checked to see if the antenna was actually connected instead of the dummy load. There seemed to be plenty of activity on the band just above and below me. although band conditions have been far from ideal, I have managed to make local contacts using ssb with 100 watts today. Is it just that nobody wants to waste time with someone who can only send about 10 words per minute?
Logged
VK3GDM
Member

Posts: 28




Ignore
« Reply #1 on: August 02, 2007, 04:14:35 PM »

I had a similar experience last night at about 1200z.  I decided to tinker around in the shack for a bit, with the radio tuned to a couple of CW stations in the background.

About an hour later I tried again on 40m and had three QSOs in succession.  This was followed by another two, for a total of 5 for the hour.

I think it’s just a timing thing. They have to be tunning past your frequency at the right time.

It pays to keep trying.

73
David Mayes
VK3GDM
Logged
KE3WD
Member

Posts: 5689




Ignore
« Reply #2 on: August 02, 2007, 04:17:26 PM »

Try again at another time.  

Try again at another freq.

Don't know, but if your sending sounds like it might be a hard read to the other folks, they may take a pass, answer there is to practice sending with good character weighting, timing, etc. and then try some more.  

Use a small tape recorder to record your sending, try sending some copy from a magazine article or newspaper, etc. using a code oscillator or the sidetone only of your rig if it allows that without sending and then come back tomorrow and see if you can copy your own code easily -- or not.  If not, this should isolate what you need to correct pretty quickly.  

If you send very nice code and characters, ignore that last paragraph and just chalk it up to not having anybody out there at the time who tried to answer you.  Maybe someone did try but you didn't hear them.  Make sure you listen without filters on when calling CQ, so that you can hear the widest area possible for a return call.  You can narrow it down and kick in the filters once you find that answer call.  


Don't give up, it will get better in all respects.



.
Logged
K7KBN
Member

Posts: 2802




Ignore
« Reply #3 on: August 02, 2007, 08:34:41 PM »

Instead of calling your own CQ, why not search around and answer one.  Takes a lot of the unknowns out of the equation.
Logged

73
Pat K7KBN
CWO4 USNR Ret.
KD4VSI
Member

Posts: 19




Ignore
« Reply #4 on: August 02, 2007, 08:59:24 PM »

 I tried to find someone calling cq who was sending at a speed I could copy, but couldn't find anyone. I guess its easy to get discouraged because I really want to make a contact. I'll try again in a few hours.
Logged
N8UZE
Member

Posts: 1524




Ignore
« Reply #5 on: August 03, 2007, 04:07:54 AM »

Look up the FISTS website and find their calling frequencies.  You will improve your odds of getting an answer.
Logged
N4KZ
Member

Posts: 598




Ignore
« Reply #6 on: August 03, 2007, 05:55:12 AM »

Don't let your disappointing first experience with CW sour you on the mode. Keep trying. Like so many other things in life, persistence is the key. (CW pun intended.)

73, N4KZ
Logged
VA7CPC
Member

Posts: 2386




Ignore
« Reply #7 on: August 03, 2007, 09:15:17 AM »

If you hear a CQ, but the sender is faster than you can copy, reply at _your speed_.  And add PSE QRS.

Usually, he'll slow down when he answers.  It's a matter of courtesy to newer (slower) operators.  As in driving, some people are more considerate than others.

     Charles
Logged
WB2WIK
Member

Posts: 20595




Ignore
« Reply #8 on: August 03, 2007, 09:57:26 AM »

What time of day?

Timing is everything.

7053 kHz is loaded with SSB DX activity at night (beginning around dusk, and then later all through the night) and isn't a good choice for a CW contact during those hours.  During daytime, though, it should be okay.

I don't answer anybody up as high as 7053 in the evening simply because I don't feel like QRMing the weaker DX SSB stations who are there.  (Of course, Americans cannot transmit SSB there; they are transmitting above 7125 -- but they are "listening" there, for DX who can transmit below 7100.)

You might try down a bit lower in the band if you're operating in the evening hours.

The other suggestion of simply answering other people is a good one, too.

WB2WIK/6
Logged
AK2B
Member

Posts: 94




Ignore
« Reply #9 on: August 03, 2007, 12:35:01 PM »

I would second the motion to join FISTS. You will find an entire orginization behind the efforts of beginners. They have a lot of members, all of which are willing to slow down to your pace. http://www.fists.org/

Tom ak2b
Logged
AE5I
Member

Posts: 124




Ignore
« Reply #10 on: August 03, 2007, 01:07:57 PM »

Hi Joel-

You've already gotten good advice.

The most important part is to stick with it!  After my first CW QSO, I couldn't have felt more incompetent...  ;-)  But, I kept at it and have worked CW for probably 99% of my QSOs since the early 90s.  It's definitely my favorite mode.

I want to echo a couple of points that have already been mentioned:

It is probably just a combination of propagation and timing that was working against you.  But, if you were indeed getting passed by intentionally, I would be it would be an issue of "spacing".  Unless I'm specifically looking for DX or some other particular type of QSO, about the only thing that makes me pass a CQer by is bad spacing.  If the bits all run together and the receiving op can't separate the characters easily, or if the words are run together so that it's one long string of characters, it's just too much work (and sometimes nearly impossible) to decipher what's being sent.

In my book, it's WAY better to have exaggerated spacing than to have too little.

Also, the difference in length of dits as compared to dahs needs to be either correct or even exaggerated.  If they both sound the same, once again, the code is not readable.

I'm not saying at all that this problem exists with your station, but it's definitely a reason that a CQ can go unanswered.

If you can easily monitor your transmissions on a computer, that's a good way to polish up your sending.  Basically, if a computer can copy you, then you're doing quite well. I just bought a little MFJ code reader to use for that exact purpose.  My favorite key is a bug and I'm looking for a good, convenient, objective way to evaluate and improve my sending.

Say, are you using an electronic keyer, bug, or straight key?  It's much easier to send perfect code with a keyer.  It's easiest to send absolutely unreadable code with a straight key.  I totally disagree with the concept of "you should start with a straight key before using anything else."  That's like telling a backhoe operator that he has to demonstrate proficiency with a shovel before he can learn to use a backhoe...  ;-) If you are using a keyer, about the only reason you might get passed by is if your word spacing is not sufficient.

Second point:  I would recommend looking a little lower in the band.  I'd say to scan 7.025 - 7.045 and 10.100 - 10.130 and 14.025 - 14.045 looking for CQers.  If you don't find anyone that sounds like a good one to call, I would try your CQ somewhere in the bottom half of those ranges.

Third point:  be sure to either (1) listen through a fairly wide filter or (2) tune around at least 1 kc above to 1 kc below your transmit frequency when you listen.  It's also a good idea to only CQ a couple or three times and then ID a couple of times each time before listening.  If a CQer just sends CQ umpteen dozen times before he IDs and listens, I'll get bored and move on.  Listening through a narrow filter is fine as long as you aggressively tune back and forth while listening for a reply.  In my neighborhood, the noise floor on 40 meters is too high to listen for weak signals through anything wider than a 250 cycle filter, so I just sweep back and forth while listening for a reply.

Don't worry about your speed!  EVERY one of us was at 10 wpm at one point and many many many courteous ops will slow right down and engage you in a QSO.  Believe me, on the air QSOs are the fastest way to get your speed up!  The most fun too....  Don't forget, this is AMATEUR radio!  You're not a ship's radio officer under pressure to get every character correct...  :-)  Have a good time and the speed and accuracy will come.

My operating schedule's a bit limited for the next few days due to other committments but after that I'd be delighted to make a schedule and be your first contact if you have not already had success.

DON'T GIVE UP!

73

Tom AE5I
Logged
AE5I
Member

Posts: 124




Ignore
« Reply #11 on: August 03, 2007, 10:45:15 PM »

The suggestion to join FISTS is also an excellent one!  I'd highly recommend it...

Tom
FISTS #2083
Logged
KD4VSI
Member

Posts: 19




Ignore
« Reply #12 on: August 04, 2007, 10:10:48 AM »

Thanks for all of the great advice. although I didn't have any more luck yesterday making a contact, I did manage to find a local ham who is willing to set up a schedule to practice cw. I met him by chance on one of the local 2 meter repeaters. As far as sending, I'm using a ten tec jupiter with its internal keyer and a bencher by-1 paddle. I have the character speed set to about 13wpm, but I exaggerate the spaces between characters and words quite a bit. I'd say it averages out to about 8-10 wpm. I'm willing to keep at it. The CW bug seems to have bitten hard. I'm going to investigate FISTS today as well. Thanks for the replies.
Logged
AE5I
Member

Posts: 124




Ignore
« Reply #13 on: August 04, 2007, 10:42:38 PM »

Well, running that gear and sending as you are, folks should not be passing you by because of your sending.  I bet it's just propagation and timing.....

Whatever you do, don't give up!

Take care...

Tom
Logged
KB9CRY
Member

Posts: 4283


WWW

Ignore
« Reply #14 on: August 06, 2007, 08:42:44 AM »

It could also be that your signal is too weak for the noisy summer conditions.


How much power are you driving from the amp and how high up is the yagi beam?

Logged
Pages: [1] 2 Next   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!