eHam
eHam Forums => DXing => Topic started by: WB9LUR on March 28, 2023, 09:27:48 AM
-
Not the first time this has happened and probably won't be the last.
At 16:20 UTC 9G4X is transmitting on 24893 and listening over several kHz up....right where CY0S is transmitting on 24895. The 9G4X pileup completely crushes CY0S.
DQRM-maximus.
Randy / WB9LUR
-
You're probably right. And the LID fest automatically doubles.
-
Too many expeditions...
-
Why complain? I'm grateful that DXpeditions are back...the more the merrier.
Paul, W6IBU
-
No complaints, only an appeal for a modicum of coordination.
-
It seems the DX-pedition operators not only need to listen to their frequency before going qrv, but listen to where the pileup will be. Add to that, they may not hear the other operation or pileup.
Frank KG6N
-
If the Pilots are doing their job this should not be an issue.
Kind of Amazing that we have this problem today when the pilots can simply send a text via Sat Phone.
-
No complaints, only an appeal for a modicum of coordination.
CW8 will prevent all this:
https://ucictech.weebly.com
-
Contrary to popular belief, some coordination is possible and/or "situational awareness" kicked in.
CY0S is now in the clear on 3567. 9G4X moved up to 3570. 9X5RU is gone, hopefully to return, I still need them on 80m.
-
CW8 will prevent all this:
https://ucictech.weebly.com (https://ucictech.weebly.com)
Sounds like something that should be announced this coming Saturday (before noon if you're a purist for these things).
-
When that happens I just turn the big knob on the front of the radio or go find something else to do. Never a problem for me.
-
Imagine this... Four DXpeditions from four different countries from near the same area at the same time. And every DXer in the world needs all four for ATNOs. Does that sound like a recipe for disaster or what?
This happened in Oct 2010, with PJ2, PJ4, PJ5, and PJ7. The teams knew ahead of time this could turn out to be a major success that would make many DXers happy, but they realized this effort had the potential to be the biggest cluster **** in DX history. With careful planning, execution, and coordination between the teams, I don't recall a single incident of them stepping on each other. Kudos to the teams for a job well done.
As for DXpeditions listening where others are transmitting, this has probably been going on since operating split was invented. "Hey lid, he's working split," when the caller is actually trying to work another station. They usually seem to figure it out and correct the situation. As that famous shrimp boat captain Forrest Gump once said, "**** Happens" or "c'est la vie."
-
I've worked two DX-peditions at once on CW. I could hear them both come back to me simultaneously! I'm sure I have a log notation somewhere.
This is less of an issue on FT8, as everyone knows precisely who you are calling.
If your waterfall fills with calls for another operation you know that one of you ought to move.
-
Channelization would solve this problem.
-
Channelization would solve this problem.
One of the reasons 60 meters is not awarded by DXCC is because the allocation on 5 MHz is channelized. Wouldn't want that to happen to the other bands, or folks like these guys (https://60metersonline.com/was-dxcc-certificates.html) could take over the awards. Just fill out an application and send it along with the award fee to a guy who was on a site called the lid list and honored as lid of the month.