| Home |
| Search |
| Today's Posts |
|
|
|
#1
March 21st 05, 02:15 AM
|
|||
|
|||
something I don't understand
is how people can expect to work FT5XO on CW when they can't copy Morse.
Fired up on 40m this evening, but sat the paddle aside & gave up on working them (for now) when I found it simply totally impossible to figure out where the FT5 was listening. The offending calls below are NOT fake; while I don't guarantee I copied them all right, I'm pretty sure the operators appearing after "Pileup:" below really are lids. FT5XO: KC4AUF 5NN Pileup: W3QY W3QY KI0F KI0F FT5XO: K2CI 5NN Pileup: K2FU K2FU FT5XO: VE7XF 5NN Pileup: AA9PB AA9PB FT5XO: WX2K 5NN Pileup: K1UO K1UO FT5XO: K7 UP LID Pileup: VE3XB VE3XB FT5XO: N9IW 5NN Pileup: KV0Q KV0Q FT5XO: K8IW 5NN Pileup: K3PA K3PA FT5XO: UP LIDJAQ 5NN Pileup: KV0Q KV0Q FT5XO: K9NA 5NN Pileup: NS1L NS1L OK, at least in the second case, the guy who called had more than one letter in common with who FT5XO came back to..... There are plenty more guilty parties out there. It was difficult to collect the incriminating evidence, as before one "I don't recognize my own call!" lid could finish sending his call, another one would call over the top of him. Figuring out where the guy FT5XO actually came back to was is simply impossible in this mess. I DX for fun -- this kind of crap isn't. Dialed down to 1510 in the BCB & got my new one down there... Hint to DXers: IF YOU CAN'T COPY CODE, DON'T BOTHER TRYING TO WORK DX ON CW! That's what SSB and RTTY are for... -- Doug Smith W9WI Pleasant View (Nashville), TN EM66 http://www.w9wi.com (will try the FT5 later in the week, when hopefully I can be on past some of these lids' bedtimes...) |
|
#2
March 21st 05, 07:06 AM
|
|||
|
|||
|
As you know by the 2 nd or 3rd day from the end of the dxpedition they are
typically begging for q's on al lmodes..... I need them for #314 but I'm waiting for when it will be fun to work them and not a collage of dx cops, whistlers, carrier throwers, and frequency lords. As I get older busting pileups has revealed itself to me as the ego trip it has really been all along. I have a kw but I don't like the atmosphere till towards the end of the entire operation when I can work them in a relaxed environment and actually have a qso..gee what a novel idea!!! -- Charlie Ham Radio - AD5TH www.ad5th.com Live Blues Music www.492acousticblues.com "Doug Smith W9WI" wrote in message ... is how people can expect to work FT5XO on CW when they can't copy Morse. Fired up on 40m this evening, but sat the paddle aside & gave up on working them (for now) when I found it simply totally impossible to figure out where the FT5 was listening. The offending calls below are NOT fake; while I don't guarantee I copied them all right, I'm pretty sure the operators appearing after "Pileup:" below really are lids. FT5XO: KC4AUF 5NN Pileup: W3QY W3QY KI0F KI0F FT5XO: K2CI 5NN Pileup: K2FU K2FU FT5XO: VE7XF 5NN Pileup: AA9PB AA9PB FT5XO: WX2K 5NN Pileup: K1UO K1UO FT5XO: K7 UP LID Pileup: VE3XB VE3XB FT5XO: N9IW 5NN Pileup: KV0Q KV0Q FT5XO: K8IW 5NN Pileup: K3PA K3PA FT5XO: UP LIDJAQ 5NN Pileup: KV0Q KV0Q FT5XO: K9NA 5NN Pileup: NS1L NS1L OK, at least in the second case, the guy who called had more than one letter in common with who FT5XO came back to..... There are plenty more guilty parties out there. It was difficult to collect the incriminating evidence, as before one "I don't recognize my own call!" lid could finish sending his call, another one would call over the top of him. Figuring out where the guy FT5XO actually came back to was is simply impossible in this mess. I DX for fun -- this kind of crap isn't. Dialed down to 1510 in the BCB & got my new one down there... Hint to DXers: IF YOU CAN'T COPY CODE, DON'T BOTHER TRYING TO WORK DX ON CW! That's what SSB and RTTY are for... -- Doug Smith W9WI Pleasant View (Nashville), TN EM66 http://www.w9wi.com (will try the FT5 later in the week, when hopefully I can be on past some of these lids' bedtimes...) |
|
#3
March 21st 05, 07:29 AM
|
|||
|
|||
|
On Mon, 21 Mar 2005 02:15:52 GMT, Doug Smith W9WI
wrote: is how people can expect to work FT5XO on CW when they can't copy Morse. Fired up on 40m this evening, but sat the paddle aside & gave up on working them (for now) when I found it simply totally impossible to figure out where the FT5 was listening. The offending calls below are NOT fake; while I don't guarantee I copied them all right, I'm pretty sure the operators appearing after "Pileup:" below really are lids. FT5XO: KC4AUF 5NN Pileup: W3QY W3QY KI0F KI0F FT5XO: K2CI 5NN Pileup: K2FU K2FU FT5XO: VE7XF 5NN Pileup: AA9PB AA9PB FT5XO: WX2K 5NN Pileup: K1UO K1UO FT5XO: K7 UP LID Pileup: VE3XB VE3XB FT5XO: N9IW 5NN Pileup: KV0Q KV0Q FT5XO: K8IW 5NN Pileup: K3PA K3PA FT5XO: UP LIDJAQ 5NN Pileup: KV0Q KV0Q FT5XO: K9NA 5NN Pileup: NS1L NS1L OK, at least in the second case, the guy who called had more than one letter in common with who FT5XO came back to..... There are plenty more guilty parties out there. It was difficult to collect the incriminating evidence, as before one "I don't recognize my own call!" lid could finish sending his call, another one would call over the top of him. Figuring out where the guy FT5XO actually came back to was is simply impossible in this mess. I DX for fun -- this kind of crap isn't. Dialed down to 1510 in the BCB & got my new one down there... Hint to DXers: IF YOU CAN'T COPY CODE, DON'T BOTHER TRYING TO WORK DX ON CW! That's what SSB and RTTY are for... It's no better on SSB. For example the aforementioned FT5WJ this morning calls on 14.278 (I still don't understand this, Charlie's "help" notwithstanding) and says that he's listening 5 to 15 up. He's only about 44 here but I can understand this quite nicely. The exact same thing happens. He says, WX0XX and several hundred stations keep right on giving their calls, often while he's transmitting. If WX0XX actually makes a QSO everyone who heard him pile on his freq. In the meantime, FT5WJ, if anyone bothered to listen for a few minutes, is now listening on another frequency. A bit of listening instead of a lot of calling and this was easy to figure. I called once up 15 after he worked someone up 10 and he came right back with a 59. I remember an expedition from a few years ago (not the call just the event) where the op, transmitting on 14.195, said, "Listening 5 to 20 up....(mob starts calling)... and 14.190." Worked him on the first call on 14.190. |
|
#4
March 21st 05, 06:27 PM
|
|||
|
|||
|
Wes the real answer to your dx conundrum is that there are just so few ops
that even begin to approach 1/10th the competency level you have. Funny...I thought the true fruition of greatness in anything was a deeper true humility...you as the exception to that have proved the rule ..TY Wes... -- Charlie "Wes Stewart" wrote in message ... On Mon, 21 Mar 2005 02:15:52 GMT, Doug Smith W9WI wrote: is how people can expect to work FT5XO on CW when they can't copy Morse. Fired up on 40m this evening, but sat the paddle aside & gave up on working them (for now) when I found it simply totally impossible to figure out where the FT5 was listening. The offending calls below are NOT fake; while I don't guarantee I copied them all right, I'm pretty sure the operators appearing after "Pileup:" below really are lids. FT5XO: KC4AUF 5NN Pileup: W3QY W3QY KI0F KI0F FT5XO: K2CI 5NN Pileup: K2FU K2FU FT5XO: VE7XF 5NN Pileup: AA9PB AA9PB FT5XO: WX2K 5NN Pileup: K1UO K1UO FT5XO: K7 UP LID Pileup: VE3XB VE3XB FT5XO: N9IW 5NN Pileup: KV0Q KV0Q FT5XO: K8IW 5NN Pileup: K3PA K3PA FT5XO: UP LIDJAQ 5NN Pileup: KV0Q KV0Q FT5XO: K9NA 5NN Pileup: NS1L NS1L OK, at least in the second case, the guy who called had more than one letter in common with who FT5XO came back to..... There are plenty more guilty parties out there. It was difficult to collect the incriminating evidence, as before one "I don't recognize my own call!" lid could finish sending his call, another one would call over the top of him. Figuring out where the guy FT5XO actually came back to was is simply impossible in this mess. I DX for fun -- this kind of crap isn't. Dialed down to 1510 in the BCB & got my new one down there... Hint to DXers: IF YOU CAN'T COPY CODE, DON'T BOTHER TRYING TO WORK DX ON CW! That's what SSB and RTTY are for... It's no better on SSB. For example the aforementioned FT5WJ this morning calls on 14.278 (I still don't understand this, Charlie's "help" notwithstanding) and says that he's listening 5 to 15 up. He's only about 44 here but I can understand this quite nicely. The exact same thing happens. He says, WX0XX and several hundred stations keep right on giving their calls, often while he's transmitting. If WX0XX actually makes a QSO everyone who heard him pile on his freq. In the meantime, FT5WJ, if anyone bothered to listen for a few minutes, is now listening on another frequency. A bit of listening instead of a lot of calling and this was easy to figure. I called once up 15 after he worked someone up 10 and he came right back with a 59. I remember an expedition from a few years ago (not the call just the event) where the op, transmitting on 14.195, said, "Listening 5 to 20 up....(mob starts calling)... and 14.190." Worked him on the first call on 14.190. |
|
#5
March 22nd 05, 10:55 PM
|
|||
|
|||
|
"Doug Smith W9WI" wrote in message
... is how people can expect to work FT5XO on CW when they can't copy Morse. Fired up on 40m this evening, but sat the paddle aside & gave up on working them (for now) when I found it simply totally impossible to figure out where the FT5 was listening. The offending calls below are NOT fake; while I don't guarantee I copied them all right, I'm pretty sure the operators appearing after "Pileup:" below really are lids. FT5XO: KC4AUF 5NN Pileup: W3QY W3QY KI0F KI0F FT5XO: K2CI 5NN Pileup: K2FU K2FU FT5XO: VE7XF 5NN Pileup: AA9PB AA9PB FT5XO: WX2K 5NN Pileup: K1UO K1UO FT5XO: K7 UP LID Pileup: VE3XB VE3XB FT5XO: N9IW 5NN Pileup: KV0Q KV0Q FT5XO: K8IW 5NN Pileup: K3PA K3PA FT5XO: UP LIDJAQ 5NN Pileup: KV0Q KV0Q FT5XO: K9NA 5NN Pileup: NS1L NS1L OK, at least in the second case, the guy who called had more than one letter in common with who FT5XO came back to..... There are plenty more guilty parties out there. It was difficult to collect the incriminating evidence, as before one "I don't recognize my own call!" lid could finish sending his call, another one would call over the top of him. Figuring out where the guy FT5XO actually came back to was is simply impossible in this mess. I DX for fun -- this kind of crap isn't. Dialed down to 1510 in the BCB & got my new one down there... Hint to DXers: IF YOU CAN'T COPY CODE, DON'T BOTHER TRYING TO WORK DX ON CW! That's what SSB and RTTY are for... Doug, it sounded even worse from out here on the left coast. At least you don't hear ALL of the lids all at once due to skip zones. There was one W9 with a short call (from IL not TN (grin)) who called continuously about 1 KHz up for at least two hours. They never listened 1 up ... -- ... Hank http://home.earthlink.net/~horedson http://home.earthlink.net/~w0rli |
|
#6
March 22nd 05, 11:20 PM
|
|||
|
|||
|
There is this to understand
All of the below is old hat and has been going on for a long time -- 30 years that I know of. No worse now as compared to then. There are plenty of resources as how to work DX -- books and on the web. And from the looks of the "offenders" below (mostly extras) -- they know better or should. Maybe look em up and e-mail em. Snail mail anon if you wish. Will do little good to grouse here. -- I doubt, therefore I might be ! "Hank Oredson" wrote in message ink.net... "Doug Smith W9WI" wrote in message ... is how people can expect to work FT5XO on CW when they can't copy Morse. Fired up on 40m this evening, but sat the paddle aside & gave up on working them (for now) when I found it simply totally impossible to figure out where the FT5 was listening. The offending calls below are NOT fake; while I don't guarantee I copied them all right, I'm pretty sure the operators appearing after "Pileup:" below really are lids. FT5XO: KC4AUF 5NN Pileup: W3QY W3QY KI0F KI0F FT5XO: K2CI 5NN Pileup: K2FU K2FU FT5XO: VE7XF 5NN Pileup: AA9PB AA9PB FT5XO: WX2K 5NN Pileup: K1UO K1UO FT5XO: K7 UP LID Pileup: VE3XB VE3XB FT5XO: N9IW 5NN Pileup: KV0Q KV0Q FT5XO: K8IW 5NN Pileup: K3PA K3PA FT5XO: UP LIDJAQ 5NN Pileup: KV0Q KV0Q FT5XO: K9NA 5NN Pileup: NS1L NS1L OK, at least in the second case, the guy who called had more than one letter in common with who FT5XO came back to..... There are plenty more guilty parties out there. It was difficult to collect the incriminating evidence, as before one "I don't recognize my own call!" lid could finish sending his call, another one would call over the top of him. Figuring out where the guy FT5XO actually came back to was is simply impossible in this mess. I DX for fun -- this kind of crap isn't. Dialed down to 1510 in the BCB & got my new one down there... Hint to DXers: IF YOU CAN'T COPY CODE, DON'T BOTHER TRYING TO WORK DX ON CW! That's what SSB and RTTY are for... Doug, it sounded even worse from out here on the left coast. At least you don't hear ALL of the lids all at once due to skip zones. There was one W9 with a short call (from IL not TN (grin)) who called continuously about 1 KHz up for at least two hours. They never listened 1 up ... -- ... Hank http://home.earthlink.net/~horedson http://home.earthlink.net/~w0rli |
|
#7
March 23rd 05, 03:06 AM
|
|||
|
|||
|
"Caveat Lector" wrote in message
news:qL10e.60653$xt.54509@fed1read07... There is this to understand All of the below is old hat and has been going on for a long time -- 30 years that I know of. 50 years, but was not so bad 50 years ago. In fact was much better. It was better 30 years ago as well. No worse now as compared to then. Why shouldn't it get better? The equipment available to us is better. There are plenty of resources as how to work DX -- books and on the web. And from the looks of the "offenders" below (mostly extras) -- they know better or should. Yup. Maybe look em up and e-mail em. Snail mail anon if you wish. Will do little good to grouse here. Who's grousing? Didn't have any problem working them with 100W and inverted vee on 30M :-) But I did have to listen a bit until it was clear where they would listen next ... -- ... Hank http://home.earthlink.net/~horedson http://home.earthlink.net/~w0rli |
|
#8
March 23rd 05, 08:07 AM
|
|||
|
|||
|
Caveat Lector wrote:
There is this to understand All of the below is old hat and has been going on for a long time -- 30 years that I know of. No worse now as compared to then. I would disagree with that assessment. There are a lot of things in ham radio that aren't worse than they were 30 years ago. But this isn't one of them. I got my license in 1973 and I clearly remember a day when if you would listen, you could almost always find the guy the DX was working. Yeah, there were plenty of people who didn't know that - who would just pick a transmit frequency at random & just call there - but they didn't call continuously *every time* the DX stopped transmitting. Indeed, while I hate to join the "I hate packet" bandwagon there really does seem to be a correlation between continuous calling and the explosive growth of spotting nets. -- Doug Smith W9WI Pleasant View (Nashville), TN EM66 http://www.w9wi.com |
|
#9
March 23rd 05, 03:26 PM
|
|||
|
|||
|
"Doug Smith W9WI" wrote in message ... Caveat Lector wrote: There is this to understand All of the below is old hat and has been going on for a long time -- 30 years that I know of. No worse now as compared to then. I would disagree with that assessment. There are a lot of things in ham radio that aren't worse than they were 30 years ago. But this isn't one of them. I got my license in 1973 and I clearly remember a day when if you would listen, you could almost always find the guy the DX was working. I have no problem with finding the guy the DX is working. Nor do others here in our DX club. Yeah, there were plenty of people who didn't know that - who would just pick a transmit frequency at random & just call there - but they didn't call continuously *every time* the DX stopped transmitting. Yes they did now and they did then. Indeed, while I hate to join the "I hate packet" bandwagon there really does seem to be a correlation between continuous calling and the explosive growth of spotting nets. The spotting nets give a lot of info that was not available in the old days -- working country X only, working district X only, Up x to x freq, wrked em at XXX, QSX X , QSY to Band X, DX station is QRT, etc. So for the intelligent DXer this should bring more order out of chaos. But alas it seems to have helped very little -- so perhaps it is not the cluster hounds who are the problem as evidenced with the unbelievable "Who's the Dx" queries. Obviously these guys aren't looking at the cluster. Nor is the lid who is calling on the DX frequency -- one look at the packet cluster would reveal that --provided the lid knows what "he is working split" means. Alas chaps -- same o same o, I fear Caveat Lector -- Honor Roll, WAZ, etc. -- Doug Smith W9WI Pleasant View (Nashville), TN EM66 http://www.w9wi.com |
|
#10
March 23rd 05, 04:51 PM
|
|||
|
|||
|
On Wed, 23 Mar 2005 07:26:47 -0800, "Caveat Lector"
wrote: [snip] | Indeed, while I hate to join the "I hate packet" bandwagon there really | does seem to be a correlation between continuous calling and the explosive | growth of spotting nets. | |The spotting nets give a lot of info that was not available in the old |days -- working country X only, working district X only, Up x to x freq, |wrked em at XXX, QSX X , QSY to Band X, DX station is QRT, etc. | |So for the intelligent DXer this should bring more order out of chaos. But |alas it seems to have helped very little -- so perhaps it is not the |cluster hounds who are the problem as evidenced with the unbelievable "Who's |the Dx" queries. Obviously these guys aren't looking at the cluster. Nor is |the lid who is calling on the DX frequency -- one look at the packet cluster |would reveal that --provided the lid knows what "he is working split" means. I will admit to occasionally looking at worldwide Internet spots on the computer in a room away from the ham shack. I do this mainly to get a feel for what the propagation is around the globe. But I don't have a filtered packet cluster tuning my radio for me or have voice announcements calling me away from other things to work DX. I don't have a problem with those who want to operate this way, I just choose not to. That said, I do believe that clusters have caused a certain sloppiness to creep into current DX practice. For example, I have on occasion been the first to work some DX station and have had him ask me to spot him. I have to decline, since I wouldn't know how to do it if I wanted to. Why the guy can't just keep calling CQ until he makes his own pileup escapes me. But when he gets spotted and the pile is in place, he figures he doesn't have to identify anymore, so guys like me that tune across the pileup wonder who in the hell he is. I know better than to ask, but some don't, hence the "Who's the DX?" questions. The assumption that *everyone* is connected to a cluster is ridiculous. When did it become a requirement that to work DX you had to have a packet cluster connection? If on occasion, the DX would say, this is P5A, listening up 5 for W7s only, there would be a lot less chaos. |
| Reply |
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Forum | |||
| I don't understand | Shortwave | |||
| I don't understand 'split' | General | |||
| aerial coupling and nec2 - I do not understand my results | Antenna | |||
Hybrid Mode
