KP5/NP3VI worked on 24.911 FT8

[Tom Weaver]

This is strange.  The call showed up on my FT8 screen as NP3VI.  I worked it and got a report from NP3VI.  When I logged it in N3FJP it showed up as W1AW/0

Any explanation?

[John Holstein, N8GB]

I don't know your setup or how you have your software running, but I do know that if I am running WSJT-X and I do not hit "OK" on the previous QSO to log it, it will save the previous QSO in the window and leave it there. If I don't notice this, I could hit "OK" and it will log the previous QSO and the current QSO doesn't come up in a window, whereby I have to enter in the new QSO manually.

/john

On Mon, Jan 12, 2026 at 3:58 PM Tom Weaver <tfwea...@gmail.com> wrote:

This is strange.  The call showed up on my FT8 screen as NP3VI.  I worked it and got a report from NP3VI.  When I logged it in N3FJP it showed up as W1AW/0

Any explanation?

--
You received this message because you are subscribed to the Google Groups "WVDXA DX Reflector" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wvdxa+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/wvdxa/SA1PR07MB9102DD0F675DF6FAECE38FCEA481A%40SA1PR07MB9102.namprd07.prod.outlook.com.

--

John Holstein, N8GB

www.n8gb.com

[Clark L. Stewart]

Tom,

I note that the DX'pedition sometimes signs NP3VI and sometimes as KP5/NP3VI.  I suspect if you double-clicked on one of the streams where he signed NP3VI, then that would have been the callsign you worked.



As you can see above, my WSJT-X identifies NP3VI as Puerto Rico and KP5/NP3VI as Desecheo Is.  Confusing, no?

Why it logged in N3FJP as W1AW/Ø is a mystery to me.  You might want to check your all.txt file to see if you accidentally called W1AW/Ø by mistake.

Did you click on the "Log QSO" button to log it?  If so, was your last QSO with W1AW/Ø?  Or, did the "Log QSO" window just pop up on its own after you made the QSO?

When he calls CQ, he just signs KP5/NP3VI:





73, Clark, W8TN

On 1/12/2026 3:58 PM, Tom Weaver wrote:

This is strange.  The call showed up on my FT8 screen as NP3VI.  I worked it and got a report from NP3VI.  When I logged it in N3FJP it showed up as W1AW/0

Any explanation?

--

[Franklin Powell]

Apparently, this is a known code issue with compound calls. Rapid uploading by the activator is a work-around.

73 

KA8SYV 

On Jan 12, 2026, at 5:15 PM, Clark L. Stewart <w8...@ntelos.net> wrote:

 Tom,

I note that the DX'pedition sometimes signs NP3VI and sometimes as KP5/NP3VI.  I suspect if you double-clicked on one of the streams where he signed NP3VI, then that would have been the callsign you worked.

<YxYfyH8jI9cgdhRu.png>

As you can see above, my WSJT-X identifies NP3VI as Puerto Rico and KP5/NP3VI as Desecheo Is.  Confusing, no?

Why it logged in N3FJP as W1AW/Ø is a mystery to me.  You might want to check your all.txt file to see if you accidentally called W1AW/Ø by mistake.

Did you click on the "Log QSO" button to log it?  If so, was your last QSO with W1AW/Ø?  Or, did the "Log QSO" window just pop up on its own after you made the QSO?

When he calls CQ, he just signs KP5/NP3VI:

<8e0Z6FW5S7XIO0jZ.png>

73, Clark, W8TN

On 1/12/2026 3:58 PM, Tom Weaver wrote:

This is strange.  The call showed up on my FT8 screen as NP3VI.  I worked it and got a report from NP3VI.  When I logged it in N3FJP it showed up as W1AW/0

Any explanation?

--

--
You received this message because you are subscribed to the Google Groups "WVDXA DX Reflector" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wvdxa+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/wvdxa/87b4464b-1cea-480c-a9c0-460107db844e%40ntelos.net.