The following is for those that use the offset method of calling CQ in
FSK441 and ISCAT as well as those decoding them and preparing to reply to
the CQ. It would apply to any type of propagation.

This is something I learned a good while ago when K1JT added the nice
feature that allows us to double click on a decoded call to load it into
the To Radio box, look the call up, return the grid from CALL3.TXT file
(if there) and generate the messages to send. There is a section in the
Version 6 manual that covers how the program handles the information
obtained by double clicking on a call on page 11 and says:

"Double-clicking on a callsign in either one of the decoded text windows
will cause that callsign to be copied into the To radio box. The
corresponding grid locator will be looked up in the database and the
callsign inserted appropriately into the message boxes Tx1 and Tx2. If
the decoded text line includes “CQ” before the selected callsign,
message Tx1 will be selected for your next transmission. Otherwise, Tx2
will be selected. The status of TxFirst may be changed if the time-stamp
on the decoded message indicates this should be done and if
“Double-click on callsign sets TxFirst” has been checked on the Setup menu."

The important part for us that use and answer offset calling for CQ's is:
"If the decoded text line includes “CQ” before the selected callsign,
message Tx1 will be selected for your next transmission. Otherwise, Tx2
will be selected."

If you have anything between 'CQ' and your call, like 'U5' or 'D7' or
'253', the person receiving it and double-clicking on the call will have
the messages load and default to message 2 for sending, not message 1. I
had Bobby, N3LL send a U/D between 'CQ' and his call and later after his
call yesterday. It works as described. When his U/D was between CQ and
his call, message 2 was auto selected when his decoded call was
double-clicked. When the U/D was placed after his call and only 'CQ'
(and space) before his call, message 1 was selected.

Sounds easy enough. The catch is many of us that use the U/D have
traditionally placed the Up/Down part between the CQ and our call or
even run together with the CQ part such as 'CQU6'. If someone is not
careful, they will, by default, answer your CQ with message 2 instead of
message 1 when they double-click on your call to load up to call. I've
seen this happen a number of times over the years and just thought they
had goofed when in fact, I/we had contributed to or help create the
problem. I've heard other random operators say they have had several
answer a U/D CQ with message 2 and also blamed the answering operator
for not starting the qso with message 1 as they should. It happen to me
several times in the contest last weekend and I knew many of the
experienced operators generally knew better. I've also inadvertently
started answering with message 2 and catch it and change to 1. Seeing
this several times recently is what made me review the manuals again and
run the test with N3LL. Tip will modify the RH Manual and other
WSJTGroup pages as appropriate to reflect this as he has time.

So, the lesson is if you use U/D offset calling, be sure to place the
U/D part AFTER your call and not between 'CQ' and your call. All is well
if you follow that format. I would say the old dog learned a new trick,
but it is more like I finally remembered one I'd long since forgotten.
Pogo: "We have found the enemy and he are us." Thank you Bobby for the
nice test pings.

Bruce, N5SIX