Hi Rich,
Thanks for the detailed explanation. ?I logged from JTAlert which showed the call without the /A and logged it in DXKeeper without the /A. ?I need to update the contact in DXKeeper to reflect the /A and upload again. ?Since you can¡¯t update an existing QSO on LOTW this will create a new QSO. ?I can delete the QSO from eQSL and Clublog and will not have a duplicate.
Thanks again for the help.
Tom - KQ5S
toggle quoted message
Show quoted text
On Jan 26, 2025, at 09:45, ve3ki via groups.io <ve3iay@...> wrote:
I wasn't using Hound mode either. You do not need to use Hound mode to make contacts with a Fox. They were clearly in Fox (or multi-stream) mode; they were sending as many as 5 parallel streams when I worked them. Nevertheless, I wasn't using Hound mode. I chose to stay on my own Tx frequency and did not QSY to their frequency as Hound mode would have done. Perhaps Hound mode would have made the contact more quickly, or perhaps not; that varies.
?
The <> displayed in the message you received indicates that that message contained a hash code instead of a full callsign. This is because there are not enough bits in a message to send full callsigns in compound Tx4/Tx2 messages. The ... between the angle brackets indicates that your instance of WSJT-X was not yet able to determine the full callsign from that hash code. Presumably you had entered SV1GA into the DX Call box, but the <...> is a clue that that was not their full callsign, because SV1GA corresponds to a different hash code from their full callsign. If you had entered SV1GA/A into the DX Call box instead of just SV1GA, the full callsign corresponding to that hash code would have been recognized and the <...> would have been replaced by <SV1GA/A> in the display of the message you received.
?
From my ALL.TXT file I can see that people were making contacts with them both as SV1GA/A and as SV1GA, but their own CQ and Tx4/Tx2 compound messages were always from SV1GA/A.
?
73,
Rich VE3KI
?
?
On Sun, Jan 26, 2025 at 10:10 AM, TOM-KQ5S wrote:
I was not using fox/hound mode. ?When I worked them this is what I received.
?
250126_021100 ? ? 7.056 Rx FT8 ? ?-14 ?1.6 ?510 KQ5S RR73; AB1J <...> -02
?
Tom-KQ5S
On Jan 26, 2025, at 09:01, ve3ki via groups.io <ve3iay@...> wrote:
When I worked them, their Tx6 (CQ) message was CQ SV1GA/A, and their compound Tx4/Tx2 message contained a hash for SV1GA/A, as in VE3KI RR73; K9RE <SV1GA/A> -02. Their separate Tx2 and Tx4 messages just contained SV1GA without the /A. According to the user guide for Fox/Hound mode (<>), this is normal for non-standard callsigns in Fox/Hound mode.
--
Tom-KQ5S
