|
Note: DXKeeper/SpotCollector/DXView *will not* recognize
SV1GA/A as Mt. Athos. I recommend adding a user override
to DXView (Config -> Overrides) as soon as possible as
spots are already beginning to appear (17M CW).
73,
... Joe, W4TV
-------- Forwarded Message --------
Subject: [Ohio/Penn DX Bulletin] SV1GA/A -- Mount Athos
Date: Sat, 25 Jan 2025 20:05:40 +0000
From: Tedd Mirgliotta (KB8NW) via Ohio/Penn DX Bulletin <opdx+kb8nw_at_hotmail.com@...>
Reply-To: Tedd Mirgliotta (KB8NW) <kb8nw@...>
To: Ohio/Penn DX Bulletin <opdx@...>
SV1GA/A -- Mount Athos
From QRZ.com and other sources (edited by OPDX):
BREAKING NEWS FROM THE MT ATHOS PENINSULA
It was exactly fifty-years (50) ago in 1975, when SV1GA/A broke the
silence and Mt. Athos was on the air from the monastic community in
Greece.
While the dedicated religious community of some 2000 monks in twenty
monasteries, Month Athos is now in a glorious state with many new con-
structions and renovations underway.
To honor the 50th anniversary of the 1975 activation, the original
organizers:
Aris, SV1GA and Martti, OH2BH were invited to come back to Mt Athos
together with Adrian, KO8SCA, Gabi, YO8WW and Niko, OH2GEK.
The SV1GA/A team has arrived in Mt. Athos today and is busy setting up
their camp, up in the mountains. They should be on the air today but
it would take 2 or 3 days to be fully operational.
More information will follow.
July 1975 (exactly 50 years ago) SV1GA/A hit the airwaves from Mount Athos!
[cid:b59527f5-5b38-40b6-9ebc-877c51eae76e]
Tedd Mirgliotta, KB8NW - E-mail addresses:
<kb8nw@...><mailto:kb8nw@...> and<kb8nw@...><mailto:kb8nw@...>
Editor of the Ohio/Penn DX Bulletin (OPDX - DXer's Tool of Excellence)
President of the "Northern Ohio DX Association" (NODXA)
DX Advisor for the "Northern Ohio Amateur Radio Society
Past ARRL Assistant Director of the Great Lakes Division (1996-2022)
Sysop of the "Basic Amateur Radio Frequency BBS" (BARF80.ORG)
\--
You received this message as part of the **Ohio/Penn DX Bulletin** email group.
****
****(kb8nw@...)
|
I see him on FT8 and he is using SV1GA without the /A. ?I set up an override pointing both calls to Mt. Athos. I worked him and automatically uploaded to LOTW, eQSL, and Club Log. ?Club Log would not accept SV1GA as being from Mt. Athos and changed the QSO to Greece.
Does anyone know what callsign he will use when he uploads to LOTW??
toggle quoted message
Show quoted text
On Jan 25, 2025, at 14:40, Joe Subich, W4TV via groups.io <lists@...> wrote:
Note: ?DXKeeper/SpotCollector/DXView *will not* recognize
SV1GA/A as Mt. Athos. ?I recommend adding a user override
to DXView (Config -> Overrides) as soon as possible as
spots are already beginning to appear (17M CW).
73,
?... Joe, W4TV
-------- Forwarded Message --------
Subject: [Ohio/Penn DX Bulletin] SV1GA/A -- Mount Athos
Date: Sat, 25 Jan 2025 20:05:40 +0000
From: Tedd Mirgliotta (KB8NW) via Ohio/Penn DX Bulletin <opdx+kb8nw_at_hotmail.com@...>
Reply-To: Tedd Mirgliotta (KB8NW) <kb8nw@...>
To: Ohio/Penn DX Bulletin <opdx@...>
SV1GA/A -- Mount Athos
From QRZ.com and other sources (edited by OPDX):
BREAKING NEWS FROM THE MT ATHOS PENINSULA
It was exactly fifty-years (50) ago in 1975, when SV1GA/A broke the
silence and Mt. Athos was on the air from the monastic community in
Greece.
While the dedicated religious community of some 2000 monks in twenty
monasteries, Month Athos is now in a glorious state with many new con-
structions and renovations underway.
To honor the 50th anniversary of the 1975 activation, the original
organizers:
Aris, SV1GA and Martti, OH2BH were invited to come back to Mt Athos
together with Adrian, KO8SCA, Gabi, YO8WW and Niko, OH2GEK.
The SV1GA/A team has arrived in Mt. Athos today and is busy setting up
their camp, up in the mountains. They should be on the air today but
it would take 2 or 3 days to be fully operational.
More information will follow.
July 1975 (exactly 50 years ago) SV1GA/A hit the airwaves from Mount Athos!
[cid:b59527f5-5b38-40b6-9ebc-877c51eae76e]
Tedd Mirgliotta, KB8NW - E-mail addresses:
<kb8nw@...><mailto:kb8nw@...> and<kb8nw@...><mailto:kb8nw@...>
Editor of the Ohio/Penn DX Bulletin (OPDX - DXer's Tool of Excellence)
President of the "Northern Ohio DX Association" (NODXA)
DX Advisor for the "Northern Ohio Amateur Radio Society
Past ARRL Assistant Director of the Great Lakes Division (1996-2022)
Sysop of the "Basic Amateur Radio Frequency BBS" (BARF80.ORG)
\--
You received this message as part of the **Ohio/Penn DX Bulletin** email group.
****
****(kb8nw@...)
|
Later he started to use the SV1GA/A on 17 FT8 and worked him.
Red K0LUZ
On 1/26/2025 06:26 AM, TOM-KQ5S via
groups.io wrote:
I see him on FT8 and he is using SV1GA without the /A. ?I set up
an override pointing both calls to Mt. Athos. I worked him and
automatically uploaded to LOTW, eQSL, and Club Log. ?Club Log
would not accept SV1GA as being from Mt. Athos and changed the QSO
to Greece.
Does anyone know what callsign he will use when he uploads to
LOTW??
Tom-KQ5S
On Jan 25, 2025, at 14:40, Joe Subich, W4TV via
groups.io <lists@...> wrote:
Note: ?DXKeeper/SpotCollector/DXView *will not*
recognize
SV1GA/A as Mt. Athos. ?I recommend adding a user
override
to DXView (Config -> Overrides) as soon as possible
as
spots are already beginning to appear (17M CW).
73,
?... Joe, W4TV
-------- Forwarded Message --------
Subject: [Ohio/Penn DX Bulletin] SV1GA/A -- Mount Athos
Date: Sat, 25 Jan 2025 20:05:40 +0000
From: Tedd Mirgliotta (KB8NW) via Ohio/Penn DX Bulletin
<opdx+kb8nw_at_hotmail.com@...>
Reply-To: Tedd Mirgliotta (KB8NW)
<kb8nw@...>
To: Ohio/Penn DX Bulletin <opdx@...>
SV1GA/A -- Mount Athos
From QRZ.com and other sources (edited by OPDX):
BREAKING NEWS FROM THE MT ATHOS PENINSULA
It was exactly fifty-years (50) ago in 1975, when
SV1GA/A broke the
silence and Mt. Athos was on the air from the monastic
community in
Greece.
While the dedicated religious community of some 2000
monks in twenty
monasteries, Month Athos is now in a glorious state with
many new con-
structions and renovations underway.
To honor the 50th anniversary of the 1975 activation,
the original
organizers:
Aris, SV1GA and Martti, OH2BH were invited to come back
to Mt Athos
together with Adrian, KO8SCA, Gabi, YO8WW and Niko,
OH2GEK.
The SV1GA/A team has arrived in Mt. Athos today and is
busy setting up
their camp, up in the mountains. They should be on the
air today but
it would take 2 or 3 days to be fully operational.
More information will follow.
July 1975 (exactly 50 years ago) SV1GA/A hit the
airwaves from Mount Athos!
[]
Tedd Mirgliotta, KB8NW - E-mail addresses:
<kb8nw@...><mailto:kb8nw@...>
and <kb8nw@...><mailto:kb8nw@...>
Editor of the Ohio/Penn DX Bulletin (OPDX - DXer's Tool
of Excellence)
President of the "Northern Ohio DX Association" (NODXA)
DX Advisor for the "Northern Ohio Amateur Radio Society
Past ARRL Assistant Director of the Great Lakes Division
(1996-2022)
Sysop of the "Basic Amateur Radio Frequency BBS"
(BARF80.ORG)
\--
You received this message as part of the **Ohio/Penn DX
Bulletin** email group.
****
****( kb8nw@...)
--
Tom-KQ5S
|
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 (<https://wsjt.sourceforge.io/FT8_DXpedition_Mode.pdf>), this is normal for non-standard callsigns in Fox/Hound mode.
?
I entered SV1GA/A in the DX Call box in WSJT-X, made a contact, and logged the contact with SV1GA/A. Club Log accepted SV1GA/A as Mt. Athos when I uploaded the contact. I expect that they will probably be uploading as SV1GA/A.
?
73,
Rich VE3KI
?
?
On Sun, Jan 26, 2025 at 06:27 AM, TOM-KQ5S wrote:
I see him on FT8 and he is using SV1GA without the /A. ?I set up an override pointing both calls to Mt. Athos. I worked him and automatically uploaded to LOTW, eQSL, and Club Log. ?Club Log would not accept SV1GA as being from Mt. Athos and changed the QSO to Greece.
?
Does anyone know what callsign he will use when he uploads to LOTW??
?
Tom-KQ5S
On Jan 25, 2025, at 14:40, Joe Subich, W4TV via groups.io <lists@...> wrote:
Note: ?DXKeeper/SpotCollector/DXView *will not* recognize
SV1GA/A as Mt. Athos. ?I recommend adding a user override
to DXView (Config -> Overrides) as soon as possible as
spots are already beginning to appear (17M CW).
73,
?... Joe, W4TV
-------- Forwarded Message --------
Subject: [Ohio/Penn DX Bulletin] SV1GA/A -- Mount Athos
Date: Sat, 25 Jan 2025 20:05:40 +0000
From: Tedd Mirgliotta (KB8NW) via Ohio/Penn DX Bulletin <opdx+kb8nw_at_hotmail.com@...>
Reply-To: Tedd Mirgliotta (KB8NW) <kb8nw@...>
To: Ohio/Penn DX Bulletin <opdx@...>
SV1GA/A -- Mount Athos
From QRZ.com and other sources (edited by OPDX):
BREAKING NEWS FROM THE MT ATHOS PENINSULA
It was exactly fifty-years (50) ago in 1975, when SV1GA/A broke the
silence and Mt. Athos was on the air from the monastic community in
Greece.
While the dedicated religious community of some 2000 monks in twenty
monasteries, Month Athos is now in a glorious state with many new con-
structions and renovations underway.
To honor the 50th anniversary of the 1975 activation, the original
organizers:
Aris, SV1GA and Martti, OH2BH were invited to come back to Mt Athos
together with Adrian, KO8SCA, Gabi, YO8WW and Niko, OH2GEK.
The SV1GA/A team has arrived in Mt. Athos today and is busy setting up
their camp, up in the mountains. They should be on the air today but
it would take 2 or 3 days to be fully operational.
More information will follow.
July 1975 (exactly 50 years ago) SV1GA/A hit the airwaves from Mount Athos!
[cid:b59527f5-5b38-40b6-9ebc-877c51eae76e]
Tedd Mirgliotta, KB8NW - E-mail addresses:
<kb8nw@...><mailto:kb8nw@...> and<kb8nw@...><mailto:kb8nw@...>
Editor of the Ohio/Penn DX Bulletin (OPDX - DXer's Tool of Excellence)
President of the "Northern Ohio DX Association" (NODXA)
DX Advisor for the "Northern Ohio Amateur Radio Society
Past ARRL Assistant Director of the Great Lakes Division (1996-2022)
Sysop of the "Basic Amateur Radio Frequency BBS" (BARF80.ORG)
\--
You received this message as part of the **Ohio/Penn DX Bulletin** email group.
****
****(kb8nw@...)
--
Tom-KQ5S
|
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
toggle quoted message
Show quoted text
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.
|
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
|
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
|
My entry in DXKeeper automatically showed Mt Athos and uploaded to LoTW and Club Log as Mt Athos with no help from me. Jack AK7O (no slash A entered)
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
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
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
|
