Re: [wsjt-devel] State names?

[Dave Slotter]

I recently learned of a cross-platform companion to WSJT-X called
GridTracker. It seems to offer some capabilities similar to JTAlertX. It
may be found at https://tagloomis.com/grid-tracker/

-Dave
 W3DJS

On Thu, May 30, 2019, 11:02 PM Jim Nuytens via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> As others have said, JT-Alert is built for this. If you use WSJT-X on
> Windows, you really need to be using JT-Alert as well.
>
> I won't use WSJT-X without JT-Alert.
>
>
> On 5/30/2019 12:00, Greg wrote:
>
> I'm working on multiband WAS and am nearing the end. (getting difficult)
> Is there anyway to see the state of those calling CQ??? A setting maybe
> that can be added?
>
>
>
>
> --
> [image: AVG logo] 
>
> This email has been checked for viruses by AVG antivirus software.
> www.avg.com 
>
> <#m_8857472639832916185_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] State names?

[Jim Nuytens via wsjt-devel]

As others have said, JT-Alert is built for this. If you use WSJT-X on 
Windows, you really need to be using JT-Alert as well.


I won't use WSJT-X without JT-Alert.


On 5/30/2019 12:00, Greg wrote:
I'm working on multiband WAS and am nearing the end. (getting 
difficult) Is there anyway to see the state of those calling CQ??? A 
setting maybe that can be added?




---
This email has been checked for viruses by AVG.
https://www.avg.com
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Proposed FT8 Frequencies for ARRL Field Day

[WB5JJJ]

As previously stated the unique format for exchanges of FD messages would
cause extreme frustration for those that don't know what's going on.  Thus
the migration to other frequencies is a very logical decision which should
be supported by both sides.  As Gary said, there is a large group that
could care less about FD ops.  Just listen to them on the voice segments.
At least in voice, you have the option to quickly give the proper response
and move on.  This is not so easy, on purpose, with FT8 and future FT4
ops.

I have created a CONFIGURATION that is for "other" uses such as DXPeditions
and rare DX.  I have all of those special frequencies in these
configurations.  With a couple of mouse clicks, I can get in or out of any
configuration and some even come up in F/H mode automatically.  When done,
the same procedure returns me to normal FT8.

WB5JJJ - George

On Thu, May 30, 2019 at 8:16 PM Gary  wrote:

> Let’s not, please.  Not everyone wants to participate in Field Day.  The
> suggested frequencies that Tim provided look good to me.
>
>
>
> 73 de Gary – W9BS
>
>
>
> *From:* Matthew Miller [mailto:mmill...@mail.umw.edu]
> *Sent:* Thursday, May 30, 2019 8:48 PM
> *To:* 'WSJT software development'
> *Subject:* Re: [wsjt-devel] Proposed FT8 Frequencies for ARRL Field Day
>
>
>
> Why not just use the normal expected FT8 frequencies for FT8?
>
>
>
> -Matt/KK4NDE
>
>
>
> *From:* Tim Goeppinger via wsjt-devel [mailto:
> wsjt-devel@lists.sourceforge.net]
> *Sent:* Thursday, May 30, 2019 2:17 PM
> *To:* wsjt-devel@lists.sourceforge.net
> *Cc:* Tim Goeppinger
> *Subject:* [wsjt-devel] Proposed FT8 Frequencies for ARRL Field Day
>
>
>
> I would like to finalize my list of Field Day frequencies, before I
> publish them in the "FT8 For Field Day"
>
> group on Facebook, and elsewhere.  7080 seemed good during our first
> practice.   These freqs were selected based on the fact that RTTY usage in
> FD is almost non-existent.  Any major problems with these?
>
>
>
> 1840
> 3580
> 7080
> 14080
> 21080
> 28080
> 50318
> 144174
>
>
>
> Tim N6GP
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Proposed FT8 Frequencies for ARRL Field Day

[Gary]

Let’s not, please.  Not everyone wants to participate in Field Day.  The 
suggested frequencies that Tim provided look good to me.

 

73 de Gary – W9BS

 

From: Matthew Miller [mailto:mmill...@mail.umw.edu] 
Sent: Thursday, May 30, 2019 8:48 PM
To: 'WSJT software development'
Subject: Re: [wsjt-devel] Proposed FT8 Frequencies for ARRL Field Day

 

Why not just use the normal expected FT8 frequencies for FT8?

 

-Matt/KK4NDE

 

From: Tim Goeppinger via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Thursday, May 30, 2019 2:17 PM
To: wsjt-devel@lists.sourceforge.net
Cc: Tim Goeppinger
Subject: [wsjt-devel] Proposed FT8 Frequencies for ARRL Field Day

 

I would like to finalize my list of Field Day frequencies, before I publish 
them in the "FT8 For Field Day"

group on Facebook, and elsewhere.  7080 seemed good during our first practice.  
 These freqs were selected based on the fact that RTTY usage in FD is almost 
non-existent.  Any major problems with these?

 

1840
3580
7080
14080
21080
28080
50318
144174

 

Tim N6GP

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Proposed FT8 Frequencies for ARRL Field Day

[John Kludt]

Tim,

I think these are good.  They will help separate the FD FT8 operations from
the casual FT8 operations.  Important as we all know  the exchanges are
different.  If everyone is one the same frequency (usual FT8 frequencies)
everyone gets frustrated.

John K4SQC
North Fulton Amateur Radio League
6m Band Captain

On Thu, May 30, 2019 at 2:22 PM Tim Goeppinger via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> I would like to finalize my list of Field Day frequencies, before I
> publish them in the "FT8 For Field Day"
> group on Facebook, and elsewhere.  7080 seemed good during our first
> practice.   These freqs were selected based on the fact that RTTY usage in
> FD is almost non-existent.  Any major problems with these?
>
> 1840
> 3580
> 7080
> 14080
> 21080
> 28080
> 50318
> 144174
>
> Tim N6GP
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Proposed FT8 Frequencies for ARRL Field Day

[Matthew Miller]

Why not just use the normal expected FT8 frequencies for FT8?

-Matt/KK4NDE

From: Tim Goeppinger via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Thursday, May 30, 2019 2:17 PM
To: wsjt-devel@lists.sourceforge.net
Cc: Tim Goeppinger
Subject: [wsjt-devel] Proposed FT8 Frequencies for ARRL Field Day

I would like to finalize my list of Field Day frequencies, before I publish 
them in the "FT8 For Field Day"
group on Facebook, and elsewhere.  7080 seemed good during our first practice.  
 These freqs were selected based on the fact that RTTY usage in FD is almost 
non-existent.  Any major problems with these?

1840
3580
7080
14080
21080
28080
50318
144174

Tim N6GP
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call sign error

[Joe Taylor]

Hi Rich,

On 5/30/2019 19:49, Rich Zwirko - K1HTV wrote:
   If stations with non-standard non-compound calls are presently 
allowed to skip the TX1 message and start with TX2, will a future 
release of WSJT-X inhibit users with such calls from doing the TX1 to 
TX2 skip?


Perhaps.  But think about it: most likely there are hundreds of ways in 
which someone can mis-configure or otherwise misuse WSJT-X in a way that 
makes standard QSOs difficult or impossible.


We can't prevent all of these possibilities, and we may show minimal 
enthusiasm for devoting time to "fix" or prevent difficulties that don't 
exist for users who watch what they're doing and consult the User Guide 
when in doubt.


-- 73, Joe, K1JT


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call sign error

[Bill Somerville]

On 31/05/2019 00:49, Rich Zwirko - K1HTV wrote:

Bill et al,
  If stations with non-standard non-compound calls are presently 
allowed to skip the TX1 message and start with TX2, will a future 
release of WSJT-X inhibit users with such calls from doing the TX1 to 
TX2 skip?


73,
Rich - K1HTV


Hi Rich,

I expect so. The fact that there is a minor defect doesn't obviate users 
with such calls from misconfiguration of WSJT-X. Anyone with a 
non-standard call should not be enabling that option if they want to 
have successful QSOs when replying to CQ callers.


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call sign error

[Rich Zwirko - K1HTV]

Bill et al,
  If stations with non-standard non-compound calls are presently allowed to
skip the TX1 message and start with TX2, will a future release of WSJT-X
inhibit users with such calls from doing the TX1 to TX2 skip?

73,
Rich - K1HTV

= = =

Hi Mike and Jari,

I will qualify that. For compound calls the above is true but for other
non-standard calls it is not. There is a defect that causes the option to
skip Tx1 to be allowed for non-standard non-compound calls, in that case a
double-click of a CQ decode will incorrectly send Tx2. Despite that users
with non-standard non-compound calls still need to understand the
implications and should not select the option to skip Tx1.

73
Bill
G4WJS.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Proposed FT8 Frequencies for ARRL Field Day

[Tim Goeppinger via wsjt-devel]

I would like to finalize my list of Field Day frequencies, before I publish 
them in the "FT8 For Field Day"group on Facebook, and elsewhere.  7080 seemed 
good during our first practice.   These freqs were selected based on the fact 
that RTTY usage in FD is almost non-existent.  Any major problems with these?
1840
3580
7080
14080
21080
28080
50318
144174
Tim N6GP
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] State names?

[Bill Somerville]

Mike,

your reply does not answer my question.

73
Bill
G4WJS.

On 30/05/2019 19:12, Mike Lewis wrote:


JTAlert is very much tuned to this purpose.  It uses callsign 
databases but has its own database that lets you filter what you are 
looking for,  states, counties, grids, countries, directional calls, ….


Mark off which state you need and it alerts via visible and/or audible 
means when the call decodes.  Excellent piece of work making award 
hunting very efficient.


Adding states to WSJTX would address part of the challenge, but you 
still have to sift though a lot.


*From:*Bill Somerville 
*Sent:* Thursday, May 30, 2019 09:23
*To:* wsjt-devel@lists.sourceforge.net
*Subject:* Re: [wsjt-devel] State names?

On 30/05/2019 17:00, Greg wrote:

I'm working on multiband WAS and am nearing the end. (getting
difficult) Is there anyway to see the state of those calling CQ? 
A setting maybe that can be added?

HI Greg,

is there a freely available computer readable database mapping US 
calls to states? We currently use the AD1C CTY.DAT database to map 
calls to Continents, DXCC Entities, WAE Entities, CQ Zones, and ITU Zones.


Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] State names?

[Mike Lewis]

JTAlert is very much tuned to this purpose.  It uses callsign databases but has 
its own database that lets you filter what you are looking for,  states, 
counties, grids, countries, directional calls, ….

Mark off which state you need and it alerts via visible and/or audible means 
when the call decodes.  Excellent piece of work making award hunting very 
efficient.

Adding states to WSJTX would address part of the challenge, but you still have 
to sift though a lot.

From: Bill Somerville 
Sent: Thursday, May 30, 2019 09:23
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] State names?

On 30/05/2019 17:00, Greg wrote:
I'm working on multiband WAS and am nearing the end. (getting difficult) Is 
there anyway to see the state of those calling CQ?  A setting maybe that can be 
added?

HI Greg,

is there a freely available computer readable database mapping US calls to 
states? We currently use the AD1C CTY.DAT database to map calls to Continents, 
DXCC Entities, WAE Entities, CQ Zones, and ITU Zones.

Bill
G4WJS.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] State names?

[David Beauchesne]

JTAlert will tell you in its “Decodes History Window”.

 

AK2L

 

 

From: Greg  
Sent: Thursday, May 30, 2019 09:01
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] State names?

 

I'm working on multiband WAS and am nearing the end. (getting difficult) Is 
there anyway to see the state of those calling CQ?  A setting maybe that can be 
added?

 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] State names?

[Earle]

Hi Greg,
There is a way using a helper program called Alert. It runs with WSJT as a 
complementary program. A version is available for Windows and Mac. 

Earle W1IPN

Sent from my iPhone

> On May 30, 2019, at 12:00 PM, Greg  wrote:
> 
> I'm working on multiband WAS and am nearing the end. (getting difficult) Is 
> there anyway to see the state of those calling CQ?  A setting maybe that can 
> be added?
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] State names?

[Black Michael via wsjt-devel]

If you're on Windows use JTAlert.
You may also want to check out LOTWQSL program on my QRZ page that will show 
you a map and/or grid of your states.
de Mike W9MDB

 

On Thursday, May 30, 2019, 11:22:27 AM CDT, Greg  wrote:  
 
 I'm working on multiband WAS and am nearing the end. (getting difficult) Is 
there anyway to see the state of those calling CQ?  A setting maybe that can be 
added?
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] State names?

[Bill Somerville]

On 30/05/2019 17:00, Greg wrote:
I'm working on multiband WAS and am nearing the end. (getting 
difficult) Is there anyway to see the state of those calling CQ?  A 
setting maybe that can be added?


HI Greg,

is there a freely available computer readable database mapping US calls 
to states? We currently use the AD1C CTY.DAT database to map calls to 
Continents, DXCC Entities, WAE Entities, CQ Zones, and ITU Zones.


Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] State names?

[Greg]

I'm working on multiband WAS and am nearing the end. (getting difficult) Is 
there anyway to see the state of those calling CQ?  A setting maybe that can be 
added?___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call sign error

[Bill Somerville]

On 30/05/2019 15:25, Bill Somerville wrote:

On 30/05/2019 15:15, Bill Somerville wrote:
double-clicking a CQ decode will do the right thing. The DX in this 
case must have taken deliberate action to send Tx2, that is their 
mistake, not our problem to fix.



Hi Mike and Jari,

I will qualify that. For compound calls the above is true but for 
other non-standard calls it is not. There is a defect that causes the 
option to skip Tx1 to be allowed for non-standard non-compound calls, 
in that case a double-click of a CQ decode will incorrectly send Tx2. 
Despite that users with non-standard non-compound calls still need to 
understand the implications and should not select the option to skip Tx1.


73
Bill
G4WJS.


Also as Reino, OH3MA, has just pointed out, the DX may have attempted to 
tail-end Jari's previous QSO by double-clicking a decode from him. That 
too would set up Tx2 as the Tx message when the option to skip Tx1 is 
enabled. It is the same problem, either way WSJT-X should not use Tx2 as 
the response to a double-clicked decode whether the option to skip Tx1 
is enabled or not.


73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call sign error

[Joe Taylor]

On 5/30/2019 10:24 AM, Black Michael via wsjt-devel wrote:
Is there any reason TX2 can't default to be " ME -01" instead of 
"THEM  -01" ?


YES.

You're assuming ME is a nonstandard call, which needs 58 bits to be sent 
in full.  In your example the hashed call  uses 12 bits.  That 
does not leave enough space for a numerical signal report.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call sign error

[Bill Somerville]

On 30/05/2019 15:24, Black Michael via wsjt-devel wrote:
Is there any reason TX2 can't default to be " ME -01" instead of 
"THEM  -01" ?

You may never see a CQ.


Mike,

you should either try such messages with the ft8code application or 
review the message packing code before making such suggestions. In 
short, it is not a valid standard message. Only RRR, RR73 or 73 are 
allowed as the third word in such messages.


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call sign error

[Bill Somerville]

On 30/05/2019 15:15, Bill Somerville wrote:
double-clicking a CQ decode will do the right thing. The DX in this 
case must have taken deliberate action to send Tx2, that is their 
mistake, not our problem to fix.



Hi Mike and Jari,

I will qualify that. For compound calls the above is true but for other 
non-standard calls it is not. There is a defect that causes the option 
to skip Tx1 to be allowed for non-standard non-compound calls, in that 
case a double-click of a CQ decode will incorrectly send Tx2. Despite 
that users with non-standard non-compound calls still need to understand 
the implications and should not select the option to skip Tx1.


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call sign error

[Black Michael via wsjt-devel]

Is there any reason TX2 can't default to be " ME -01" instead of "THEM 
 -01" ?You may never see a CQ.
Mike

 

On Thursday, May 30, 2019, 9:20:28 AM CDT, Bill Somerville 
 wrote:  
 
  Mike, 
  double-clicking a CQ decode will do the right thing. The DX in this case must 
have taken deliberate action to send Tx2, that is their mistake, not our 
problem to fix. 
  73 Bill G4WJS.
  
  

 copied another QSO involving the DX which is not a very good strategy as 
 they have no way of knowing if that is so.
 
 Stations with non-standard calls using F8, FT4, or MSK144 must 
 understand how hash codes work if they are going to be successful in 
 making QSOs.
 
 73
 Bill
 G4WJS.
 

 
 ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call sign error

[Black Michael via wsjt-devel]

How about for hashable calls we do a a last-time-TX1-transmitted.  And if TX2 
is started without ever transmitting TX1 then a warning dialog pops up to 
'splain things.
Mike
 

On Thursday, May 30, 2019, 8:23:21 AM CDT, Bill Somerville 
 wrote:  
 
 On 30/05/2019 14:13, Black Michael via wsjt-devel wrote:
> Maybe WSJT-X should ensure such users send CQ once in a while...that 
> would be non-intuitive.  A simple message in the decode window or such 
> that said "CQ needed, non std call" with a help file reference to 
> 'splain things.
>
Hi Mike and Jari,

there is no need to send CQ, the Tx1 message sent in reply to a CQ will 
also populate the hash table. It seems in this case that the DX has 
started with the TX2 message, that will only work if the CQ caller has 
copied another QSO involving the DX which is not a very good strategy as 
they have no way of knowing if that is so.

Stations with non-standard calls using F8, FT4, or MSK144 must 
understand how hash codes work if they are going to be successful in 
making QSOs.

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call sign error

[Bill Somerville]

On 30/05/2019 14:13, Black Michael via wsjt-devel wrote:
Maybe WSJT-X should ensure such users send CQ once in a while...that 
would be non-intuitive.  A simple message in the decode window or such 
that said "CQ needed, non std call" with a help file reference to 
'splain things.



Hi Mike and Jari,

there is no need to send CQ, the Tx1 message sent in reply to a CQ will 
also populate the hash table. It seems in this case that the DX has 
started with the TX2 message, that will only work if the CQ caller has 
copied another QSO involving the DX which is not a very good strategy as 
they have no way of knowing if that is so.


Stations with non-standard calls using F8, FT4, or MSK144 must 
understand how hash codes work if they are going to be successful in 
making QSOs.


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call sign error

[Black Michael via wsjt-devel]

Whoever is calling you is a non-standard callsign that you have not seen 
before.So the hash code that is being sent is not in your lookup table.If 
nobody ever sends their callsign without hashing it the only time you'll see it 
is when they call CQ...then it would be in your lookup table.
Maybe WSJT-X should ensure such users send CQ once in a while...that would be 
non-intuitive.  A simple message in the decode window or such that said "CQ 
needed, non std call" with a help file reference to 'splain things.
de Mike W9MDB
 

On Thursday, May 30, 2019, 8:08:11 AM CDT, Jari A  wrote: 
 
 
 Got this surprise. 

Station call me several times and all I got was:  <...> and report. Something 
wrong in the call sign. Very likely setting gone wrong, but does user see it 
incorrectly or does it come out bad?

Thought to post here, in case station recognices him/her self ( women dont do 
errors like this, or do they? )
Just to increase knowledge for users and fyi developers 

Greetings,
:Jari  / oh2fqv


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Call sign error

[Jari A]

Got this surprise.

Station call me several times and all I got was:  <...> and report.
Something wrong in the call sign. Very likely setting gone wrong, but does
user see it incorrectly or does it come out bad?

Thought to post here, in case station recognices him/her self ( women dont
do errors like this, or do they? )

Just to increase knowledge for users and fyi developers

Greetings,

:Jari  / oh2fqv

[image: image.png]
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel