++++++++++++++++++++++++++++++++++++++++++ Date: Sun, 18 Mar 2001 10:47:33 -0700 From: "Rod Cerkoney" Subject: [Elecraft] DXing tip Folks, I've heard this happen enough that I feel it's worth mentioning. When chasing DX don't tune up or call on the DX station's TX frequency. You may be interfering with others trying to hear there call. Listen for a while, a good DX op will announce where he is listening. For example last night 3G0Y was calling "3G0Y UP", tuning up the band 1kHz I heard the pack. I listened there for a while, selected a good TX frequency, and set up my rig for split operation. RX in VFO A, TX in VFO B. Then I started calling. I selected the TX frequency based on where I heard others being heard and a relative quite spot, usually on one edge or the other of the main pack. If I'm using a rig with out split, but WITH RIT or XIT, I do a similar thing, adjusting the rig to TX on one freq and listen on the DX freq. Now, sometimes the DX station is not working split, I STILL DON'T call on his frequency. First I zero beat my RX with his TX, then I use my XIT to call up 200-500Hz, starting 500 up and working down. Only on rare occasions, after many calls will I get within 100Hz of his TX Freq. This keeps me within his passband, without QRMing (hopefully) his transmissions. Hope this helps and GL DXing. 73, Rod N0RC Ft Collins CO +++++++++++++++++++++++++++++++++++++++++++ Date: Sun, 18 Mar 2001 13:27:04 -0600 From: Tom Hammond =?iso-8859-1?Q?N=D8SS?= Subject: [Elecraft] Ron's DXing tip Ron, et al: >I've heard this happen enough that I feel it's worth mentioning. When >chasing DX don't tune up or call on the DX station's TX frequency. You >may be interfering with others trying to hear there call. >................ > An EXCELLENT(!) recommendation, not calling ON the DX frequency, and even BETTER, that you LISTEN FIRST, to see if he's asking callers to listen "UP"... and MANY do nowadays. There are few things worse than QRMing a DX station by calling on his TX freq, when he's got a big pileup calling up 2 to 5kHz. The method I use is similar to Ron's, but will not work with the K1 because it has only one VFO. However the K2, and many other rigs as well, offer dual VFOs which lend themselves quite readily to working 'split'. As Ron does, I first tune on the DX station on VFO A. Then I listen to the DX station work several stations to determine whether he's working them 'on frequency' or 'split'. Obviously, if he's "working 'em" on-freq, I just in and call, trying to be the LAST station he hears when the rest of the pileup stops to take a breath (even on CW). But, if he's working 'em split, I then press the [LOCK] button (to lock in the DX TX freq into VFO B), I press [A = B] (to set VFO B to the DX TX freq), and then I hold [SPLIT] to select SPLIT FREQUENCY operation on the K2. Remember that the VFO [LOCK] is turned ON. Normally, this would prevent me from tuning at all, on EITHER VFO. HOWEVER... thanks to a suggestion made to Wayne early on in the K2 firmware development process, when you are in SPLIT VFO operation, with the VFO LOCK enabled, IF you press and hold the [REV] button, you are permitted to tune the alternate VFO (in this case, VFO B) as if it were not locked (to tune for the stations calling/working the DX). But as soon as the [REV] button is released, BOTH VFOs are again locked. So... as soon as the DX station calls a station and sends his report, I press [REV] and start tuning for the station who is WORKING the DX. Additionally, I'll listen to see if the DX station is working callers on the same frequency each time, or whether he's tuning up (or down) a bit when he picks out the next station. I also try to see if he's good enough an operator to be able to pick up 'tailenders', stations who dump in their call (only once) at the END of the report sent my the non-DX station. Once I determine where the non-DX station is, and how the DX is listening, I find the next guy he's working, and position my VFO B such that I should be the next in line. Releasing [REV] locks both VFOs so I can't accidently 'spin the dial' by an errant hand movement in the heat of battle. I have found that calling 'blind' (e.g. without having a pretty good idea of where the DX is actually listening and his operating habits) is much less productive for me. Although I must admit that it HAS worked on occasion... but I'm pretty sure it was blind luck on my part. 73, Tom Hammond N0SS +++++++++++++++++++++++++++++++++++++++++++++++