Re: [wsjt-devel] Windows 11 - All good?

[Black Michael via wsjt-devel]

What do you hate about the task bar?

 

On Monday, October 4, 2021, 04:27:59 PM CDT, Randall Hansen via wsjt-devel 
 wrote:  
 
 I installed Win 11 with no problems except some adjusting of Codec levels.  PS 
I hate what they did to the taskbar
On Mon, Oct 4, 2021 at 3:54 PM August Treubig via wsjt-devel 
 wrote:

So you have a brand new PC or Laptop that is Windows 11 certified?   If you 
don’t know the answer, then you machine most likely will not run Windows 11.  
Micro$oft is playing games to make money.  

Aug AG5AT 

Sent from my iPad

> On Oct 4, 2021, at 2:52 PM, halsteaw--- via wsjt-devel 
>  wrote:
> 
> Windows 11 starts its rollout tomorrow, and I was wondering if anyone
> was in the Windows Dev/Beta channel, and had tested WSJT-X on it?
> 
> ~Warren
> KN6HXP
> 
> 
> ___
> 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 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] Windows 11 - All good?

[Randall Hansen via wsjt-devel]

I installed Win 11 with no problems except some adjusting of Codec levels.
PS I hate what they did to the taskbar

On Mon, Oct 4, 2021 at 3:54 PM August Treubig via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> So you have a brand new PC or Laptop that is Windows 11 certified?   If
> you don’t know the answer, then you machine most likely will not run
> Windows 11.  Micro$oft is playing games to make money.
>
> Aug AG5AT
>
> Sent from my iPad
>
> > On Oct 4, 2021, at 2:52 PM, halsteaw--- via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
> >
> > Windows 11 starts its rollout tomorrow, and I was wondering if anyone
> > was in the Windows Dev/Beta channel, and had tested WSJT-X on it?
> >
> > ~Warren
> > KN6HXP
> >
> >
> > ___
> > 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X and Ham Radio Deluxe

[Harry E. Hoffman via wsjt-devel]

David,

The about screen says I do have HRD 6.7.0.391 and like I said at first 
it looked like that issue was gone, but 30 minutes later it was back. 
Now the 9700 is still fine and does not show the issue. I did a bit more 
testing with the 7300 and found that if WSJT-X "split mode" is set to 
either Rig or Fake It the issue is present but if set to NONE there is 
no twitch or mode changing, but this is only on the 7300 the 9700 does 
not have this issue it is just fine in Fake It. I use HRD to pass on the 
rig control so I don't have to bother with com port spliters and both 
HRD and WSJT-X can talk to the radios. When I am running N1MM using 
their EW1 and EW2 configurations for WSJT-X, I am using DX Lab Suite 
Commander as the rig control and there are no issues, it is only when 
using HRD. I have separate configurations for each radio in WSJT-X and 
put the HRD focus on the needed radio to pass along rig control. Logging 
is working just fine. So for now WSJT-X mode control is set to NONE and 
I select DATA mode using either HRD or the radio's controls.


I thought that the issue had been solved but it wasn't. No problem the 
work around works just fine. Thanks for all the input.


73 KA2ENE, Harry

--

On 10/4/2021 4:07 PM, david--- via wsjt-devel wrote:

Harry,

You might want to try again in a day or two.

This morning I tried to download HRD 391 and found that the link was still
pointing to 357.
Apparently someone forgot to point the link to the update.

David, AK2L


-Original Message-
From: Harry E. Hoffman via wsjt-devel 
Sent: Monday, October 4, 2021 12:39
To: Harry E. Hoffman via wsjt-devel 
Cc: Harry E. Hoffman 
Subject: Re: [wsjt-devel] WSJT-X and Ham Radio Deluxe

Sorry, looks like I spoke too soon, when I tried it again a while later the
same old behavior returned to the 7300. The mode indicator "twitches" and
the USB-D drops out. Back to WSJT-X mode setting of NONE.
Funny though the 9700 appears to still be good. Must be issues in HRD.

73 KA2ENE

-

On 10/4/2021 3:01 PM, Harry E. Hoffman via wsjt-devel wrote:

Operating System is Windows 10 (20H2)

Some good news for those that had the problem of your IC-7300 dropping
out of DATA mode when using HRD as the Rig Control for WSJT-X. Not
sure if the fix is in HRD or WSJT-X as both have new versions. If you
remember with previous versions if you had WSJT-X set to use the MODE
setting of Data/Pkt, then when you switched between TX and RX the Mode
indicator on the 7300's display would "twitch" every time and
sometimes it would drop out of USB-D and go to just plain USB. The
temporary fix was to set WSJT-X mode control to NONE and set the radio
to USB-D manually. I am now running version 6.7.0.391 of HRD and
version 2.5.0 of WSJT-X and with WSJT-X set to Data/Pkt there is no
more "twitching" of the mode indicator on the 7300 and the mode
appears to stay put and not drop out of USB-D. Now that the IC-9700
Rig Control has added the missing DATA mode to the software the
IC-9700 also appears to behave well using WSJT-X under HRD Rig
Control. Check it out to see if it is working for you as well.

73 KA2ENE


___
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 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] wsjt-devel Digest, Vol 92, Issue 13

[Al Pawlowski via wsjt-devel]

If you mouse over the Tx message # boxes (in 2.5 anyway), an info message will 
appear. For Tx4, it tells you how to set the Tx4 message to either RR73 or RRR. 
If you set it for RRR, the auto-sequence will move to Tx5 which has a default 
of 73. If you set it for RR73, it will skip Tx5 and go to Tx6, the CQ message. 
So, you can use what you want.

I usually use 73 and move my cursor back to Tx4 and click Tx enable when my 73 
is sent. if the other op sends another 73, WSJTx sends another 73 from me. If 
the other op goes quiet or calls someone else, I click Tx disable. In pre 2.5 
versions, the auto-sequencer would even do 3 Tx5 73’s for me (don't have to 
enable each time) if no message was decoded from the other op. I assume it will 
do the same in 2.5, but I have not had a need to try yet.



> On Oct 4, 2021, at 12:44, wsjt-devel-requ...@lists.sourceforge.net wrote:
> 
> Date: Mon, 4 Oct 2021 19:09:02 + (UTC)
> From: Andrew Neumeier mailto:ka2...@yahoo.com>>
> To: WSJT Software Development  >
> Subject: [wsjt-devel] Question FT8

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

Re: [wsjt-devel] Question FT8

[Bruce Bohannon via wsjt-devel]

Gary, you very correct. I'm with you on that. Slow down. Enjoy the 
program for what it is.


Bruce WA1YZN

On 10/4/2021 16:50, Gary McDuffie via wsjt-devel wrote:



On Oct 4, 2021, at 13:09, Andrew Neumeier via wsjt-devel 
 wrote:

This is a different situation than working strong signals on HF, where I rarely 
operate FT8, so my experience is different.  So, when another station sends 73, 
and my station does not automatically respond, I'll just have to do that 
manually.

And this is the problem, Andy…. All of these modes were started on VHF.  After 
FT8 had been on the air a short time, some people decided to try it out on HF.  
By the way, there wasn’t a bunch of whining about too many sequences on HF wen 
it started.  People were happy to run it as it was, and it worked quite well.  
The more people got into it, the more there started to be this strange desire 
to make things go faster.  Contests, etc., just made it worse.  I would guess 
that the majority of the people on these modes now don’t know a thing about 
using them on six or two meters.  All you hear now is faster, faster, FASTER!  
Good grief!  As I posted months ago, why not just get the phone out and see how 
fast you can call your ham buddies and log contacts.  What’s happened to ham 
radio?  What is the hurry?

I know - unpopular opinion right now, but I know I’m not the only one.

Gary - AG0N

___
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] Question FT8

[Gary McDuffie via wsjt-devel]

> On Oct 4, 2021, at 13:09, Andrew Neumeier via wsjt-devel 
>  wrote:
> 
> This is a different situation than working strong signals on HF, where I 
> rarely operate FT8, so my experience is different.  So, when another station 
> sends 73, and my station does not automatically respond, I'll just have to do 
> that manually.  

And this is the problem, Andy…. All of these modes were started on VHF.  After 
FT8 had been on the air a short time, some people decided to try it out on HF.  
By the way, there wasn’t a bunch of whining about too many sequences on HF wen 
it started.  People were happy to run it as it was, and it worked quite well.  
The more people got into it, the more there started to be this strange desire 
to make things go faster.  Contests, etc., just made it worse.  I would guess 
that the majority of the people on these modes now don’t know a thing about 
using them on six or two meters.  All you hear now is faster, faster, FASTER!  
Good grief!  As I posted months ago, why not just get the phone out and see how 
fast you can call your ham buddies and log contacts.  What’s happened to ham 
radio?  What is the hurry?

I know - unpopular opinion right now, but I know I’m not the only one.

Gary - AG0N

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

Re: [wsjt-devel] Windows 11 - All good?

[August Treubig via wsjt-devel]

So you have a brand new PC or Laptop that is Windows 11 certified?   If you 
don’t know the answer, then you machine most likely will not run Windows 11.  
Micro$oft is playing games to make money.  

Aug AG5AT 

Sent from my iPad

> On Oct 4, 2021, at 2:52 PM, halsteaw--- via wsjt-devel 
>  wrote:
> 
> Windows 11 starts its rollout tomorrow, and I was wondering if anyone
> was in the Windows Dev/Beta channel, and had tested WSJT-X on it?
> 
> ~Warren
> KN6HXP
> 
> 
> ___
> 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] WSJT-X and Ham Radio Deluxe

[david--- via wsjt-devel]

Their download link is fixed.  Just downloaded 391 and I see some of the new 
features.
AK2L


-Original Message-
From: August Treubig via wsjt-devel  
Sent: Monday, October 4, 2021 13:14
To: WSJT software development 
Cc: August Treubig 
Subject: Re: [wsjt-devel] WSJT-X and Ham Radio Deluxe

HRD has an issue that the version being downloaded is 357, not 391.   They say 
that it is fixed, but will take a while to propagate.  So you need to make sure 
you get 391.   

Aug
AG5AT 

Sent from my iPad

> On Oct 4, 2021, at 2:40 PM, Harry E. Hoffman via wsjt-devel 
>  wrote:
> 
> Sorry, looks like I spoke too soon, when I tried it again a while later the 
> same old behavior returned to the 7300. The mode indicator "twitches" and the 
> USB-D drops out. Back to WSJT-X mode setting of NONE. Funny though the 9700 
> appears to still be good. Must be issues in HRD.
> 
> 73 KA2ENE
> 
> -
> 
>> On 10/4/2021 3:01 PM, Harry E. Hoffman via wsjt-devel wrote:
>> Operating System is Windows 10 (20H2) Some good news for those that 
>> had the problem of your IC-7300 dropping out of DATA mode when using HRD as 
>> the Rig Control for WSJT-X. Not sure if the fix is in HRD or WSJT-X as both 
>> have new versions. If you remember with previous versions if you had WSJT-X 
>> set to use the MODE setting of Data/Pkt, then when you switched between TX 
>> and RX the Mode indicator on the 7300's display would "twitch" every time 
>> and sometimes it would drop out of USB-D and go to just plain USB. The 
>> temporary fix was to set WSJT-X mode control to NONE and set the radio to 
>> USB-D manually. I am now running version 6.7.0.391 of HRD and version 2.5.0 
>> of WSJT-X and with WSJT-X set to Data/Pkt there is no more "twitching" of 
>> the mode indicator on the 7300 and the mode appears to stay put and not drop 
>> out of USB-D. Now that the IC-9700 Rig Control has added the missing DATA 
>> mode to the software the IC-9700 also appears to behave well using WSJT-X 
>> under HRD Rig Control. Check it out to see if it is working for you as well.
>> 73 KA2ENE
>> ___
>> 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 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] WSJT-X and Ham Radio Deluxe

[david--- via wsjt-devel]

Harry,

You might want to try again in a day or two.

This morning I tried to download HRD 391 and found that the link was still
pointing to 357.
Apparently someone forgot to point the link to the update.

David, AK2L


-Original Message-
From: Harry E. Hoffman via wsjt-devel  
Sent: Monday, October 4, 2021 12:39
To: Harry E. Hoffman via wsjt-devel 
Cc: Harry E. Hoffman 
Subject: Re: [wsjt-devel] WSJT-X and Ham Radio Deluxe

Sorry, looks like I spoke too soon, when I tried it again a while later the
same old behavior returned to the 7300. The mode indicator "twitches" and
the USB-D drops out. Back to WSJT-X mode setting of NONE. 
Funny though the 9700 appears to still be good. Must be issues in HRD.

73 KA2ENE

-

On 10/4/2021 3:01 PM, Harry E. Hoffman via wsjt-devel wrote:
> Operating System is Windows 10 (20H2)
> 
> Some good news for those that had the problem of your IC-7300 dropping 
> out of DATA mode when using HRD as the Rig Control for WSJT-X. Not 
> sure if the fix is in HRD or WSJT-X as both have new versions. If you 
> remember with previous versions if you had WSJT-X set to use the MODE 
> setting of Data/Pkt, then when you switched between TX and RX the Mode 
> indicator on the 7300's display would "twitch" every time and 
> sometimes it would drop out of USB-D and go to just plain USB. The 
> temporary fix was to set WSJT-X mode control to NONE and set the radio 
> to USB-D manually. I am now running version 6.7.0.391 of HRD and 
> version 2.5.0 of WSJT-X and with WSJT-X set to Data/Pkt there is no 
> more "twitching" of the mode indicator on the 7300 and the mode 
> appears to stay put and not drop out of USB-D. Now that the IC-9700 
> Rig Control has added the missing DATA mode to the software the 
> IC-9700 also appears to behave well using WSJT-X under HRD Rig 
> Control. Check it out to see if it is working for you as well.
> 
> 73 KA2ENE
> 
> 
> ___
> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X and Ham Radio Deluxe (Some Good News)

[Neil Zampella via wsjt-devel]

If you're using the Secondary UDP Server in WSJT-X to do the logging to
HRD, then be aware, that is 'deprecated', that is no longer being
supported.   Its been that way for a while and still available, but it
may disappear in a newer version.

Neil, KN3ILZ


On 10/4/2021 3:17 PM, Bruce Bohannon wrote:

Harry, why are you using HRD for your rig control? It all can be done
with the 7300. Use WSJT-X to direct the logging to  hrd for your
logging. I have not had any hick-ups doing it this way. Also is true
for the 7610 as well. I can also use JT-Alert and I tell it not to log
to hrd so I do not get a double logging of the contact.as well.

Maybe I'm missing something in the conversation.

Bruce WA1YZN

On 10/4/2021 15:01, Harry E. Hoffman via wsjt-devel wrote:

Operating System is Windows 10 (20H2)

Some good news for those that had the problem of your IC-7300
dropping out of DATA mode when using HRD as the Rig Control for
WSJT-X. Not sure if the fix is in HRD or WSJT-X as both have new
versions. If you remember with previous versions if you had WSJT-X
set to use the MODE setting of Data/Pkt, then when you switched
between TX and RX the Mode indicator on the 7300's display would
"twitch" every time and sometimes it would drop out of USB-D and go
to just plain USB. The temporary fix was to set WSJT-X mode control
to NONE and set the radio to USB-D manually. I am now running version
6.7.0.391 of HRD and version 2.5.0 of WSJT-X and with WSJT-X set to
Data/Pkt there is no more "twitching" of the mode indicator on the
7300 and the mode appears to stay put and not drop out of USB-D. Now
that the IC-9700 Rig Control has added the missing DATA mode to the
software the IC-9700 also appears to behave well using WSJT-X under
HRD Rig Control. Check it out to see if it is working for you as well.

73 KA2ENE


___
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] WSJT-X and Ham Radio Deluxe (Some Good News)

[Bruce Bohannon via wsjt-devel]

Harry, why are you using HRD for your rig control? It all can be done 
with the 7300. Use WSJT-X to direct the logging to  hrd for your 
logging. I have not had any hick-ups doing it this way. Also is true for 
the 7610 as well. I can also use JT-Alert and I tell it not to log to 
hrd so I do not get a double logging of the contact.as well.


Maybe I'm missing something in the conversation.

Bruce WA1YZN

On 10/4/2021 15:01, Harry E. Hoffman via wsjt-devel wrote:

Operating System is Windows 10 (20H2)

Some good news for those that had the problem of your IC-7300 dropping 
out of DATA mode when using HRD as the Rig Control for WSJT-X. Not 
sure if the fix is in HRD or WSJT-X as both have new versions. If you 
remember with previous versions if you had WSJT-X set to use the MODE 
setting of Data/Pkt, then when you switched between TX and RX the Mode 
indicator on the 7300's display would "twitch" every time and 
sometimes it would drop out of USB-D and go to just plain USB. The 
temporary fix was to set WSJT-X mode control to NONE and set the radio 
to USB-D manually. I am now running version 6.7.0.391 of HRD and 
version 2.5.0 of WSJT-X and with WSJT-X set to Data/Pkt there is no 
more "twitching" of the mode indicator on the 7300 and the mode 
appears to stay put and not drop out of USB-D. Now that the IC-9700 
Rig Control has added the missing DATA mode to the software the 
IC-9700 also appears to behave well using WSJT-X under HRD Rig 
Control. Check it out to see if it is working for you as well.


73 KA2ENE


___
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] Question, FT8

[Gary McDuffie via wsjt-devel]

> On Oct 4, 2021, at 07:18, Neil Zampella via wsjt-devel 
>  wrote:
> 
> When you send RR73, when the Tx Enable turns off, the operator has the OPTION 
> to click it back on, select the Tx5 message, and have it go out.
> 
> See ... already implemented.  Just takes TWO clicks.

Yep, takes probably a half a sequence to figure out those steps and get it 
done.  By then, it won’t decode and you have to wait until the next cycle.  
Ridiculous waste of time.  Just default it to send.  It takes ONE click to kill 
it if it isn’t needed!

Gary - AG0N

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

Re: [wsjt-devel] WSJT-X and Ham Radio Deluxe

[August Treubig via wsjt-devel]

HRD has an issue that the version being downloaded is 357, not 391.   They say 
that it is fixed, but will take a while to propagate.  So you need to make sure 
you get 391.   

Aug
AG5AT 

Sent from my iPad

> On Oct 4, 2021, at 2:40 PM, Harry E. Hoffman via wsjt-devel 
>  wrote:
> 
> Sorry, looks like I spoke too soon, when I tried it again a while later the 
> same old behavior returned to the 7300. The mode indicator "twitches" and the 
> USB-D drops out. Back to WSJT-X mode setting of NONE. Funny though the 9700 
> appears to still be good. Must be issues in HRD.
> 
> 73 KA2ENE
> 
> -
> 
>> On 10/4/2021 3:01 PM, Harry E. Hoffman via wsjt-devel wrote:
>> Operating System is Windows 10 (20H2)
>> Some good news for those that had the problem of your IC-7300 dropping out 
>> of DATA mode when using HRD as the Rig Control for WSJT-X. Not sure if the 
>> fix is in HRD or WSJT-X as both have new versions. If you remember with 
>> previous versions if you had WSJT-X set to use the MODE setting of Data/Pkt, 
>> then when you switched between TX and RX the Mode indicator on the 7300's 
>> display would "twitch" every time and sometimes it would drop out of USB-D 
>> and go to just plain USB. The temporary fix was to set WSJT-X mode control 
>> to NONE and set the radio to USB-D manually. I am now running version 
>> 6.7.0.391 of HRD and version 2.5.0 of WSJT-X and with WSJT-X set to Data/Pkt 
>> there is no more "twitching" of the mode indicator on the 7300 and the mode 
>> appears to stay put and not drop out of USB-D. Now that the IC-9700 Rig 
>> Control has added the missing DATA mode to the software the IC-9700 also 
>> appears to behave well using WSJT-X under HRD Rig Control. Check it out to 
>> see if it is working for you as well.
>> 73 KA2ENE
>> ___
>> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Windows 11 - All good?

[halsteaw--- via wsjt-devel]

Windows 11 starts its rollout tomorrow, and I was wondering if anyone
was in the Windows Dev/Beta channel, and had tested WSJT-X on it?

~Warren
KN6HXP


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

Re: [wsjt-devel] Question, FT8

[Bill Frantz via wsjt-devel]

On 10/3/21 at 10:50 PM, wsjt-devel@lists.sourceforge.net (Alex 
via wsjt-devel) wrote:


Even though I had let go of this rule, I think I will reinstate 
it again. No 73, no QSO. I really don't care if that means my 
log will be a few Q's short. The world is already rude enough 
as it is. We can take a few moments to be courteous.


You must realize that no number of messages can ensure that both 
ends are ready to log the QSO. It is an example of the Two 
Generals' Problem*. For DXing, if you received the necessary 
exchange data (usually a call sign and a signal report), then 
log the QSO and LotW work it out. For contesting where, if one 
side logs the QSO and the other does not, the side making the 
log entry loses points agreement is more important. Examination 
of logs by contest organizers shows many more cases where points 
are lost due to mismatching log entries in FTx contests than in 
CW, voice, or RTTY contests. So, in contests log the entry when 
the contest rules say you should.


73 Bill AE6JV

* The Two Generals' Problem (from 
)

In computing, the Two Generals' Problem is a thought experiment 
meant to illustrate the pitfalls and design challenges of 
attempting to coordinate an action by communicating over an 
unreliable link. In the experiment, two generals are only able 
to communicate with one another by sending a messenger through 
enemy territory. The experiment asks how they might reach an 
agreement on the time to launch an attack, while knowing that 
any messenger they send could be captured.


t is related to the more general Byzantine Generals Problem and 
appears often in introductory classes about computer networking 
(particularly with regard to the Transmission Control Protocol, 
where it shows that TCP can't guarantee state consistency 
between endpoints and why this is the case), though it applies 
to any type of two-party communication where failures of 
communication are possible. A key concept in epistemic logic, 
this problem highlights the importance of common knowledge. Some 
authors also refer to this as the Two Generals' Paradox, the Two 
Armies Problem, or the Coordinated Attack Problem.[1][2] The Two 
Generals' Problem was the first computer communication problem 
to be proved to be unsolvable. An important consequence of this 
proof is that generalizations like the Byzantine Generals 
problem are also unsolvable in the face of arbitrary 
communication failures, thus providing a base of realistic 
expectations for any distributed consistency protocols.


--
Bill Frantz| There are now so many exceptions to the
408-348-7900   | Fourth Amendment that it operates only by
www.pwpconsult.com | accident.  -  William Hugh Murray



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

Re: [wsjt-devel] WSJT-X and Ham Radio Deluxe

[Harry E. Hoffman via wsjt-devel]

Sorry, looks like I spoke too soon, when I tried it again a while later 
the same old behavior returned to the 7300. The mode indicator 
"twitches" and the USB-D drops out. Back to WSJT-X mode setting of NONE. 
Funny though the 9700 appears to still be good. Must be issues in HRD.


73 KA2ENE

-

On 10/4/2021 3:01 PM, Harry E. Hoffman via wsjt-devel wrote:

Operating System is Windows 10 (20H2)

Some good news for those that had the problem of your IC-7300 dropping 
out of DATA mode when using HRD as the Rig Control for WSJT-X. Not sure 
if the fix is in HRD or WSJT-X as both have new versions. If you 
remember with previous versions if you had WSJT-X set to use the MODE 
setting of Data/Pkt, then when you switched between TX and RX the Mode 
indicator on the 7300's display would "twitch" every time and sometimes 
it would drop out of USB-D and go to just plain USB. The temporary fix 
was to set WSJT-X mode control to NONE and set the radio to USB-D 
manually. I am now running version 6.7.0.391 of HRD and version 2.5.0 of 
WSJT-X and with WSJT-X set to Data/Pkt there is no more "twitching" of 
the mode indicator on the 7300 and the mode appears to stay put and not 
drop out of USB-D. Now that the IC-9700 Rig Control has added the 
missing DATA mode to the software the IC-9700 also appears to behave 
well using WSJT-X under HRD Rig Control. Check it out to see if it is 
working for you as well.


73 KA2ENE


___
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] WSJT-X and Ham Radio Deluxe (Some Good News)

[Harry E. Hoffman via wsjt-devel]

Operating System is Windows 10 (20H2)

Some good news for those that had the problem of your IC-7300 dropping 
out of DATA mode when using HRD as the Rig Control for WSJT-X. Not sure 
if the fix is in HRD or WSJT-X as both have new versions. If you 
remember with previous versions if you had WSJT-X set to use the MODE 
setting of Data/Pkt, then when you switched between TX and RX the Mode 
indicator on the 7300's display would "twitch" every time and sometimes 
it would drop out of USB-D and go to just plain USB. The temporary fix 
was to set WSJT-X mode control to NONE and set the radio to USB-D 
manually. I am now running version 6.7.0.391 of HRD and version 2.5.0 of 
WSJT-X and with WSJT-X set to Data/Pkt there is no more "twitching" of 
the mode indicator on the 7300 and the mode appears to stay put and not 
drop out of USB-D. Now that the IC-9700 Rig Control has added the 
missing DATA mode to the software the IC-9700 also appears to behave 
well using WSJT-X under HRD Rig Control. Check it out to see if it is 
working for you as well.


73 KA2ENE


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

[wsjt-devel] Question FT8

[Andrew Neumeier via wsjt-devel]

Since I started this discussion, and have now read all the comments, some 
clarification is probably in order.  

Most of my operating is on vhf, and the majority of that on 2M.  So, I am often 
dealing with very weak signals, many can't be heard, many of those at the edge 
of the capability of FT8 to decode.  So, I see RR73 rarely used.  So, when a 
station I am in contact with sends 73, I know he has received my RRR, and by 
sending 73 I have in turn acknowledged his receipt of that message.  Often, if 
I don't send 73, the other station will send 73 again, looking for my response. 
 So in a qso like this, stations are rarely making contacts in rapid 
succession.  It's the kind of environment where I may see a disturbance on the 
waterfall and start turning my beam to investigate and try to peak the signal.  
Often I'm dealing with qsb peaks until the signal is strong enough to decode.  
A qso like this can take some time and I've seen them last for 5 minutes, maybe 
more.  This is a different situation than working strong signals on HF, where I 
rarely operate FT8, so my experience is different.  So, when another station 
sends 73, and my station does not automatically respond, I'll just have to do 
that manually.  

So, I was just asking about this, about the cutoff of my transmit after I 
received a 73.  I wanted only to be sure the software was behaving correctly, 
I'm not asking for a new feature to accommodate me or seeking a discussion 
about operating etiquette. 

Thanks to all who responded to my question.  


73,Andy, ka2uqw
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question, FT8

[Sam W2JDB via wsjt-devel]

Actually, if you are the originator of the RR73 message, the only messages that 
you should be expecting is either a 73 confirming your RR73 (part of auto seq) 
completing the QSO, or a retransmission of the SNR message (also part of auto 
seq), in which case you should retransmit the RR73 message by re-enabling TX 
with TX4 containing the said RR73. If you receive neither, while you may still 
log the QSO, you really don't know if the other party logged the QSO on their 
end. 
73,
Sam W2JDB


-Original Message-
From: Alex via wsjt-devel 
To: WSJT software development 
Cc: Alex 
Sent: Mon, Oct 4, 2021 12:39 pm
Subject: Re: [wsjt-devel] Question, FT8

Yes, that was exactly my point. Thanks for setting me straight. How could I 
have been so stupid to miss that.

73,
--Alex KR1STOn Oct 4, 2021, at 9:33 AM, Neil Zampella via wsjt-devel 
 wrote:
 It's currently optional ...  
 
 When you send RR73, when the Tx Enable turns off, the operator has the OPTION 
to click it back on, select the Tx5 message, and have it go out.
 
 See ... already implemented.  Just takes TWO clicks.
 
 Neil, KN3ILZ
  On 10/4/2021 7:21 AM, Alex wrote:
  
 Hi Jim,
 
  Hence the suggestion to make it optional. 
 
  Perhaps there should be a penalty for not being courteous on the bands. I can 
live with that.
 
  I always had to laugh when I read the discussions on the RTTY lists after a 
contest. It's full of complaints about operators sending a character too many 
here and there. 
 
  We're in a bad place if sending a 73, which is done in almost every other 
mode (including RTTY contests back when I participated), is too much to ask for.
 
  One can hardly argue that fully automatic operations (including logging) is a 
bad thing if sending a 73 is too much to ask for.
 
  73,
  --Alex KR1ST On Oct 4, 2021, at 2:43 AM, Jim Brown via wsjt-devel 
 wrote: 
 On 10/3/2021 7:50 PM, Alex via wsjt-devel wrote:

 No 73, no QSO. I really don't care if that means my log will be a few Q's 
short. The world is already rude enough as it is. We can take a few moments to 
be courteous.
Not when there's short band opening for DX, and not in a contest. :)When the 
other station sends RRR or RR73 and I immediately call CQ, heshould know that I 
copied it. If I didn't, I'd send R-10 again. And ifyou re-send R-10, I know you 
didn't get my RRR or RR73, so I re-send it.This stuff is LOOONG established 
practice on the HF bands, especiallyfor contesting and DX pileups. Indeed, the 
most discourteous thing wecan do with working a contest (or in a DX opening) is 
to make thecontact take longer to complete -- it slows the other station 
down!Contest rules penalize you if a QSO in your log is not in the 
otherstation's log, and it's often the loss of ANOTHER QSO. Failing 
tounderstand these issues has driven RTTY contesters crazy when FT8 andFT4 were 
added to RTTY Roundup, and when those same RTTY contestersworked to set up a 
pure digital contest.73, Jim K9YCwsjt-devel mailing 
listwsjt-devel@lists.sourceforge.nethttps://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 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] Question, FT8

[Alex via wsjt-devel]

Yes, that was exactly my point. Thanks for setting me straight. How could I 
have been so stupid to miss that.

73,
--Alex KR1ST

On Oct 4, 2021, 9:33 AM, at 9:33 AM, Neil Zampella via wsjt-devel 
 wrote:
>It's currently optional ...
>
>When you send RR73, when the Tx Enable turns off, the operator has the
>OPTION to click it back on, select the Tx5 message, and have it go out.
>
>See ... already implemented.  Just takes TWO clicks.
>
>Neil, KN3ILZ
>
>On 10/4/2021 7:21 AM, Alex wrote:
>> Hi Jim,
>>
>> Hence the suggestion to make it optional.
>>
>> Perhaps there should be a penalty for not being courteous on the
>> bands. I can live with that.
>>
>> I always had to laugh when I read the discussions on the RTTY lists
>> after a contest. It's full of complaints about operators sending a
>> character too many here and there.
>>
>> We're in a bad place if sending a 73, which is done in almost every
>> other mode (including RTTY contests back when I participated), is too
>> much to ask for.
>>
>> One can hardly argue that fully automatic operations (including
>> logging) is a bad thing if sending a 73 is too much to ask for.
>>
>> 73,
>> --Alex KR1ST
>> On Oct 4, 2021, at 2:43 AM, Jim Brown via wsjt-devel
>> > > wrote:
>>
>> On 10/3/2021 7:50 PM, Alex via wsjt-devel wrote:
>>
>> No 73, no QSO. I really don't care if that means my log will
>> be a few Q's short. The world is already rude enough as it
>is.
>> We can take a few moments to be courteous.
>>
>>
>> Not when there's short band opening for DX, and not in a contest.
>:)
>> When the other station sends RRR or RR73 and I immediately call
>CQ, he
>> should know that I copied it. If I didn't, I'd send R-10 again.
>And if
>> you re-send R-10, I know you didn't get my RRR or RR73, so I
>re-send it.
>> This stuff is LOOONG established practice on the HF bands,
>especially
>> for contesting and DX pileups. Indeed, the most discourteous
>thing we
>> can do with working a contest (or in a DX opening) is to make the
>> contact take longer to complete -- it slows the other station
>down!
>>
>> Contest rules penalize you if a QSO in your log is not in the
>other
>> station's log, and it's often the loss of ANOTHER QSO. Failing to
>> understand these issues has driven RTTY contesters crazy when FT8
>and
>> FT4 were added to RTTY Roundup, and when those same RTTY
>contesters
>> worked to set up a pure digital contest.
>>
>> 73, Jim K9YC
>>
>>
>>
>>
>>
>
>>
>> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Question, FT8

[Neil Zampella via wsjt-devel]

It's currently optional ...

When you send RR73, when the Tx Enable turns off, the operator has the
OPTION to click it back on, select the Tx5 message, and have it go out.

See ... already implemented.  Just takes TWO clicks.

Neil, KN3ILZ

On 10/4/2021 7:21 AM, Alex wrote:

Hi Jim,

Hence the suggestion to make it optional.

Perhaps there should be a penalty for not being courteous on the
bands. I can live with that.

I always had to laugh when I read the discussions on the RTTY lists
after a contest. It's full of complaints about operators sending a
character too many here and there.

We're in a bad place if sending a 73, which is done in almost every
other mode (including RTTY contests back when I participated), is too
much to ask for.

One can hardly argue that fully automatic operations (including
logging) is a bad thing if sending a 73 is too much to ask for.

73,
--Alex KR1ST
On Oct 4, 2021, at 2:43 AM, Jim Brown via wsjt-devel
mailto:wsjt-devel@lists.sourceforge.net>> wrote:

On 10/3/2021 7:50 PM, Alex via wsjt-devel wrote:

No 73, no QSO. I really don't care if that means my log will
be a few Q's short. The world is already rude enough as it is.
We can take a few moments to be courteous.


Not when there's short band opening for DX, and not in a contest. :)
When the other station sends RRR or RR73 and I immediately call CQ, he
should know that I copied it. If I didn't, I'd send R-10 again. And if
you re-send R-10, I know you didn't get my RRR or RR73, so I re-send it.
This stuff is LOOONG established practice on the HF bands, especially
for contesting and DX pileups. Indeed, the most discourteous thing we
can do with working a contest (or in a DX opening) is to make the
contact take longer to complete -- it slows the other station down!

Contest rules penalize you if a QSO in your log is not in the other
station's log, and it's often the loss of ANOTHER QSO. Failing to
understand these issues has driven RTTY contesters crazy when FT8 and
FT4 were added to RTTY Roundup, and when those same RTTY contesters
worked to set up a pure digital contest.

73, Jim K9YC






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] Question, FT8

[Alex via wsjt-devel]

Hi Jim,

Hence the suggestion to make it optional.

Perhaps there should be a penalty for not being courteous on the bands. I can 
live with that.

I always had to laugh when I read the discussions on the RTTY lists after a 
contest. It's full of complaints about operators sending a character too many 
here and there.

We're in a bad place if sending a 73, which is done in almost every other mode 
(including RTTY contests back when I participated), is too much to ask for.

One can hardly argue that fully automatic operations (including logging) is a 
bad thing if sending a 73 is too much to ask for.

73,
--Alex KR1ST

On Oct 4, 2021, 2:43 AM, at 2:43 AM, Jim Brown via wsjt-devel 
 wrote:
>On 10/3/2021 7:50 PM, Alex via wsjt-devel wrote:
>> No 73, no QSO. I really don't care if that means my log will be a few
>
>> Q's short. The world is already rude enough as it is. We can take a
>few
>> moments to be courteous.
>
>Not when there's short band opening for DX, and not in a contest. :)
>When the other station sends RRR or RR73 and I immediately call CQ, he
>should know that I copied it. If I didn't, I'd send R-10 again. And if
>you re-send R-10, I know you didn't get my RRR or RR73, so I re-send
>it.
>This stuff is LOOONG established practice on the HF bands, especially
>for contesting and DX pileups. Indeed, the most discourteous thing we
>can do with working a contest (or in a DX opening) is to make the 
>contact take longer to complete -- it slows the other station down!
>
>Contest rules penalize you if a QSO in your log is not in the other
>station's log, and it's often the loss of ANOTHER QSO. Failing to
>understand these issues has driven RTTY contesters crazy when FT8 and
>FT4 were added to RTTY Roundup, and when those same RTTY contesters
>worked to set up a pure digital contest.
>
>73, Jim K9YC
>
>
>
>
>___
>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] Question, FT8

[Claude Frantz via wsjt-devel]

On 10/4/21 1:17 AM, Allan Downie via wsjt-devel wrote:

Hi Allen, Bill & all,

Technically the return 73 is not 
required for a valid QSO, however it is the polite thing to do. At the 
very least if confirms to your operating partner that all was received. 
I would like to at least see it as an operator option.


I support this request.

Best wishes,
Claude


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

Re: [wsjt-devel] Question, FT8

[Jim Brown via wsjt-devel]

On 10/3/2021 7:50 PM, Alex via wsjt-devel wrote:
No 73, no QSO. I really don't care if that means my log will be a few 
Q's short. The world is already rude enough as it is. We can take a few 
moments to be courteous.


Not when there's short band opening for DX, and not in a contest. :) 
When the other station sends RRR or RR73 and I immediately call CQ, he 
should know that I copied it. If I didn't, I'd send R-10 again. And if 
you re-send R-10, I know you didn't get my RRR or RR73, so I re-send it. 
This stuff is LOOONG established practice on the HF bands, especially 
for contesting and DX pileups. Indeed, the most discourteous thing we 
can do with working a contest (or in a DX opening) is to make the 
contact take longer to complete -- it slows the other station down!


Contest rules penalize you if a QSO in your log is not in the other 
station's log, and it's often the loss of ANOTHER QSO. Failing to 
understand these issues has driven RTTY contesters crazy when FT8 and 
FT4 were added to RTTY Roundup, and when those same RTTY contesters 
worked to set up a pure digital contest.


73, Jim K9YC




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