Re: [wsjt-devel] Not sure if an issue

[David - K2DBK via wsjt-devel]

I've had this issue in the past (not currently happening) and switching
codecs has worked.

 

From: Alan McDonald via wsjt-devel  
Sent: Tuesday, February 13, 2024 1:05 PM
To: 'WSJT software development' 
Cc: Alan McDonald 
Subject: Re: [wsjt-devel] Not sure if an issue

 

Instead of re-starting the application, have you tried just going to the
Audio tab, then de-selecting and then re-selecting the USB CODECS?

Alan

 

From: Marty Wayne via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> > 
Sent: Wednesday, February 14, 2024 4:43 AM
To: WSJT software development mailto:wsjt-devel@lists.sourceforge.net> >
Cc: Marty Wayne mailto:mcway...@comcast.net> >
Subject: Re: [wsjt-devel] Not sure if an issue

 

I have had the same issue with FT-4/8.  I leave my WSJT running and freq
town to 40M over night.  At first use in the morning I need to restart WSJT
to be able to transmit.

 

MacBook Pro

Ventura 13.6.4

FT-1000MP

 

73,


Marty, W6NEV
_ . ... _ _   _ . . . .   _ .   .   . . . _
mcway...@comcast.net <mailto:mcway...@comcast.net> 
408-234-8023

 

 

On Feb 13, 2024, at 2:14 AM, David Hilton-Jones via wsjt-devel
mailto:wsjt-devel@lists.sourceforge.net>
> wrote:

 

Twice now I've had WSJT and QMAP (via SDRconsole) running for several hours
without doing anything, and then when I tried to click on station in Active
Stations window nothing happened. Relaunched all programmes and worked fine.

Seems it didn't like running in idle for a long time.


Just in case anybody else has seen this

David, G4YTL



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto: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] Not sure if an issue

[David Hilton-Jones via wsjt-devel]

Twice now I've had WSJT and QMAP (via SDRconsole) running for several hours
without doing anything, and then when I tried to click on station in Active
Stations window nothing happened. Relaunched all programmes and worked fine.

Seems it didn't like running in idle for a long time.


Just in case anybody else has seen this

David, G4YTL



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

Re: [wsjt-devel] Wsjt 2.7.0 rc3 apparent holes in transmission

[David Hilton-Jones via wsjt-devel]

I don’t think that it is always a USB problem.

 

I have been aware of very brief “holes” in the audio output for many 
years/versions. In fact, more often than not I see a brief dropout – shown by 
the RF output power dropping (with ALC glitch) and drop out of audio on monitor.

 

But my audio in/out is not via USB, but through the mic/phones connections on 
the computer.

 

I’ve always assumed that it’s due to a problem with audio “streaming” in the 
computer/soundcard – and ignored it!

David, G4YTL

 

From: Nic Sears via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: 30 January 2024 14:11
To: WSJT software development
Cc: Nic Sears
Subject: Re: [wsjt-devel] Wsjt 2.7.0 rc3 apparent holes in transmission

 

Thanks Neil, suspected that but audio stream on other output seemed ok. Cannot 
check usb stream, will try and find an update. Amazed an eme QSO works ok with 
holes!!

 

Nic

 

On 30 Jan 2024 13:03, Neil via wsjt-devel  
wrote:

Hi Nic, I had this problem with random gaps of about 2 seconds in transmission 
audio with an earlier release.  It was nothing to do with wsjt-x, the root 
problem was a buggy USB 3.0 driver for the internal card in the machine 
(i7/32GB/Win10).  I updated the driver and that fixed it.  It took a long time 
to diagnose!

-- 
Neil G4DBN
https://youtube.com/MachiningandMicrowaves

 

On 30/01/2024 12:20, Nic Sears via wsjt-devel wrote:

Hi there, Nic G3YEG here.
 
I have been using wsjt for quite a few years both ft8 (hf, vhf and uhf) and 
q65-60b on 432 eme and have never consciously notice the power output of any of 
my previous rigs varying during ft8 or q65 tx cycles.
 
Recently I Started using a new laptop with much higher spec than old machine  
and also changed over to rc3. I then noted that the alc on my ic9700 had 
started spiking on the tx cycle. 
 
This seems to be completely random and does not appear to effect the decoding 
of my signal at all, hf, vhf ,uhf ft8 and even with my very low power q65 eme 
set up having had 3 recent eme qso’s and seen the spikes occur on tx. It also 
occurs on the ts2000 i use for hf.
 
I have investigated and it seems that the transmission does have “holes” in it 
when you actually listen to it.
 
It is not consistent as sometimes the tx cycle is completely clean and 
sometimes has a number of holes.
 
I have reverted back to 2.6.1 and that also exhibits the same problem but it 
does seem to be to a lesser extent. However Not done that many tests on 2.6.1
 
I always run with nil or very low alc on both my rigs so the recent spiking has 
been quite obvious. The tx power output on both the rigs doesn’t seem to dip 
that but the 9700 current drain certainly drops on the rig metering.
 
The old machine was a Lenovo running Windows 10 with an amd a10 and 12gb memory 
driving the 9700 via a single usb interface. The new machine is an intel i7 
running Windows 11 with 32Gb memory again driving the 9700 via a single usb 
interface. The ts2000 is driven from the new machine via a usb to rs232 dongle 
for cat control and a usb to analogue dongle for the audio interface. The icom 
Ic-9700 usb driver was in use on both old and new machines.
 
I mentioned this observation to another local eme operator who has also noted 
these “holes” but also observed that it doesn’t seem to cause any remote 
station decoding problems.
 
Be grateful if you could consider my observation and advise if there is a real 
problem.
 
Thank you, Nic 
 

 

 

 

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

Re: [wsjt-devel] QMAP query

[David Hilton-Jones via wsjt-devel]

Many thanks Charlie

 

Done some further testing this morning and I think I have a partial 
explanation/solution.

 

Windows 10

 

WSJT-X rc2

QMAP

SDRC

RSPDx

 

No moon to play with at the moment, but just played with hitting “Tune” in 
WSJT-X.

 

If the auto-mute in DRC is off, then there is no problem. The QMAP thermometer 
reads ~48db.

 

If auto-mute is on, AND the Peak and Mean options are set to -20db or lower, 
then QMAP does not recover when going to receive. Thermometer is zero. Have to 
exit and reload QMAP then OK.

 

BUT, if Peak and Mean set to 0db, then after transmit QMAP returns to receive 
as normal.

 

Will be interesting to see if you can duplicate.

 

73


David

 

From: Charles Suckling via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: 19 December 2023 05:33
To: WSJT software development
Cc: Charles Suckling
Subject: Re: [wsjt-devel] QMAP query

 

Hi David

 

As far as I know, this hasn't been reported before.

 

I've been running SDRC to drive QMAP now for some time here, pretty much since 
SDRC build 3117 came out, and also haven't seen this behaviour.

 

The only problem I had, at first, was to have SDRC's demodulated audio 
outputting to the same audio 'port' as WSJT-X uses for transmitting, cured by 
muting SDRC.  It did not result in loss of signal to QMAP as you are seeing.

 

What level do you see on QMAP's thermometer normally?

 

What operating system are you running?

 

73

 

Charlie DL3WDG

 

On Tue, 19 Dec 2023 at 03:00, David Hilton-Jones via wsjt-devel 
 wrote:

I am using rc2, SDRconsole with RSPDx, and QMAP

 


Today, all was running fine. I clicked on a station in “Active stations”, and 
WSJT-x took me to transmit, and the QSO ran as normal.

 

However, after my first transmit period, on return to receive, QMAP was showing 
no input signal, whilst SDRconsole was displaying normally. WSJT-x was working 
normally. I closed QMAP, and re-opened it, then it was working again.

 

I obviously need to try again a few more times, but didn’t have time today.

 

Any thoughts?

 

David, G4YTL

Sent from the all-new AOL app for iOS 
<https://apps.apple.com/us/app/aol-news-email-weather-video/id646100661> 

___
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] QMAP query

[David Hilton-Jones via wsjt-devel]

I am using rc2, SDRconsole with RSPDx, and QMAP

Today, all was running fine. I clicked on a station in “Active stations”, and 
WSJT-x took me to transmit, and the QSO ran as normal.
However, after my first transmit period, on return to receive, QMAP was showing 
no input signal, whilst SDRconsole was displaying normally. WSJT-x was working 
normally. I closed QMAP, and re-opened it, then it was working again.
I obviously need to try again a few more times, but didn’t have time today.
Any thoughts?
David, G4YTL

Sent from the all-new AOL app for iOS
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] IC-705 little to no decodes

[David Garnier via wsjt-devel]

 Try running this simple web app from your browser, 
you will know right away whether your computers clock is synced to UTC.

https://time.is/

Dave - wb9own
 On Tuesday, December 5, 2023 at 08:17:28 AM CST, robert evans LAST_NAME 
via wsjt-devel  wrote:  
 
   All good suggestions. Thank You.       Last night..   Double checked 
everything on the old dell i3 win10   and it started decoding just fine.       
The thing is, that it is so slow, i loose track of what   i did and didn't do 
when i make changes.       And it takes forever to reboot.       I keep it 
around because it is about the bare   minimum system to support the usb drivers 
  now used by windows for modern radios.   ft-991, ft-dx10, ic-9700, ic-705, 
etc. etc. etc.       So, as a beta test of WSJT-X 2.7.0-rc2 on a   old dell i3 
win10 with the IC-705 it worked fine.           Back to the asus win11 i9 
laptop / IC-705 :   When WSJT-X 2.7.0-rc2 did decode the   dt was like 0.2 or 
less.   I'll revisit that soon.       Thanks Again.   N2LO~>              
  On 12/05/2023 3:52 AM EST Kari Sillanmäki via wsjt-devel 
 wrote:           OM,       Also make sure 
that you are not in "Hound" mode with the "Rx All Freqs" unchecked.       73's 
de Kari, oh2gqc       On 12/4/23 20:57, robert evans LAST_NAME via wsjt-devel 
wrote:  
   Using a IC-705 over the weekend and after 
installing the usb drivers in a asus win11 
i9 laptop i started WSJT-X 2.7.0-rc2.       The rig control worked fine and the 
signals 
where being displayed in the spect graph, 
but no decodes. Double checked the time set. 
Still no decodes.       Walked away for many minutes and there were 
decodes when i got back, but only a few.   Installed WSJT-X 2.6.1 and tried 
again.   Same behavior.       Every once in a awhile it would decode a 
frame and then none for long periods of 
time even though the spectrum graph showed 
signals on the waterfall continuously.       Switched to an old dell i3 win10 
laptop 
and saw the same behavior with wsjt-x.   Tried fldigi and it decoded Olivia and 
psk31 as well as cw no problem.       Tried JS8 as well - no problem.       
Back to WSJT-X and double checked the 
settings. Every once in a long while 
it might decode what looks like a frame.       N2LO~>           
 
 ___wsjt-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] Source code location for hashcodes.f90?

[David - K2DBK via wsjt-devel]

Thanks Reino, that was it.

 

I've uploaded my version to github: https://github.com/dkozinn/hashcodes

 

I am by no means a Python expert and there may be better ways to do this,
but the results from this appear to match the .f90 version output for any
callsigns that I put in. One small difference is that anything on the
command line is forced to uppercase automatically.

 

73,

David, K2DBK

 

From: Reino Talarmo via wsjt-devel  
Sent: Monday, December 4, 2023 6:35 AM
To: 'WSJT software development' 
Cc: Reino Talarmo 
Subject: Re: [wsjt-devel] Source code location for hashcodes.f90?

 

Hi David,

Was it at www.arrl.org/qexfiles year 2020
<http://www.arrl.org/qexfiles%20year%202020>  July/August, The FT4 and FT8
Communication Protocols

http://www.arrl.org/files/file/QEX%20Binaries/2020/ft4_ft8_protocols.tgz

 

73, Reino OH3mA

PS. I like to see that Python utility.

Reino

 

From: David - K2DBK via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]

Sent: Monday, December 4, 2023 12:03 AM
To: ws <mailto:wsjt-devel@lists.sourceforge.net>
jt-de...@lists.sourceforge.net
Cc: David - K2DBK mailto:k2dbk+w...@k2dbk.com> >
Subject: [wsjt-devel] Source code location for hashcodes.f90?

 

Primarily as an exercise for myself, I converted the hashcodes.f90 utility
to python. I'll (eventually) publish to github and I'd like to provide a
link to the original source, but I can no longer find where I downloaded it
from. Can someone please give me a link to that?

 

Thanks.

 

73,

 

David, K2DBK

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

[wsjt-devel] Source code location for hashcodes.f90?

[David - K2DBK via wsjt-devel]

Primarily as an exercise for myself, I converted the hashcodes.f90 utility
to python. I'll (eventually) publish to github and I'd like to provide a
link to the original source, but I can no longer find where I downloaded it
from. Can someone please give me a link to that?

 

Thanks.

 

73,

 

David, K2DBK

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

Re: [wsjt-devel] 3Y0J strange F/H operation

[David Kjellquist via wsjt-devel]

Unlike WSJT-X, JTDX software allows F on either odd or even

On 2/15/2023 10:44 AM, Ron WV4P via wsjt-devel wrote:
Lots of the people that got Clublog confirmations worked them in the 
Wrong time Slot. So the issue was real.


Ron, WV4P

On Wed, Feb 15, 2023 at 9:42 AM Palle Preben-Hansen, OZ1RH via 
wsjt-devel  wrote:


Fred, there were many 3Y0J pirates on, maybe you worked one of them?

73, Palle, OZ1RH.


Message: 1
Date: Wed, 15 Feb 2023 10:15:14 -0300
From: Fred Carvalho 
To: WSJT software development
, Joe
        Taylor 
Subject: [wsjt-devel] 3Y0J strange F/H operation
Message-ID:
       

Content-Type: text/plain; charset="utf-8"

GM to all

*This concerns F/H operation in 3Y0J*

During the DXpedition the team announced multiple times that
they were
using WSJT DXPedition Mode (F/H). However, FOX was  most of
the time in ODD
periods and accepted reports in any spot in the channel. QSY
below 1000Hz
was not necessary. My QSOs with them were always like that. It
took me some
time to understand how to work them, which I think was the
same to most of
the callers. BTW,  I have never seen FOX out of sync. The
worst that I can
remember was 0.4s.

Many thought ? myself included- that they were not using
WSJTx, but some
other multistream DXP mode application. However one of the
operators
confirmed to me that they have used WSJT software.

After the expedition they have stated that : ? *We had issues 
with the FT8
due to we did not have any device to sync against, and our
clock was 14
seconds off - which meant we at some time were TX odd, while
we thought it
was even.*?

Well a simple GPS device connected to one of their notebooks
would have
prevented the problem above.

So my questions to the developers are:

a)      Is it really possible that lack of sync would lead
them to TX in
ODD periods as FOX ?

b)      How come QSY below 1000 HZ was not necessary for the
Hound to
finalize the QSO with them?

This is very intriguing to many of us. Some clarification on
what happened
is very much appreciated

Thanks Fred PY2XB

-- 
Fred - PY2XB


___
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


--
Dave WB5NHL
8 band DXCC, 317 countries confirmed (Mixed , current)
Hamshack Hotline 
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Unable to find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds)

[David Schmocker via wsjt-devel]

Rex and everyone:
My apologies for the extra email bandwidth. 

I just (re-) joined the WSJT-X Development list today.

 

I’m aware (now) it’s previously reported and being handled.. Thank you everyone!

73,
Dave

 

From: Rex Moncur via wsjt-devel 
Reply-To: WSJT software development 
Date: Sunday, January 8, 2023 at 3:00 PM
To: 'WSJT software development' 
Cc: Rex Moncur 
Subject: Re: [wsjt-devel] Unable to find how to reset Q65A default Tx duration 
(defaults to 30 sec and my operating requires 60 seconds)

 

Hi Dave 

 

The answer to your first question is in a number of emails from Joe to the 
group and copied below:

 

73 Rex VK7MO

 

Hi Bill, Barry, and others,

 

On 1/7/2023 9:36 PM, Kurious George KB2SA via Moon-net wrote:

> I see folks reporting that 2.6.0 no longer supports Q65-30B?

 

Sorry about the missing T/R period control in WSJT-X 2.6.0.  This was 
completely unintentional.  The problem had been recognized and corrected, but 
the corrected code was inadvertently not moved into the master code branch.  A 
bug-fix release will be made very soon.

 

In the meantime, a simple workaround is to open the file WSJT-X.ini with a text 
editor (such as Notepad) search for any lines that contain "TRPeriod_Q65", and 
change the number to whatever you need.  For example, for one-minute T/R 
sequences you will want the line

 

   TRPeriod_Q65=60

 

You may find more than one instance of TRPeriod_Q65.  Change them all!

 

File WSJT-X.ini is in the Log directory, which can be accessed directly from 
the WSJT-X File menu.

 

  -- 73, Joe, K1JT

 

 

From: David Schmocker via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Monday, 9 January 2023 7:46 AM
To: WSJT software development
Cc: David Schmocker
Subject: Re: [wsjt-devel] Unable to find how to reset Q65A default Tx duration 
(defaults to 30 sec and my operating requires 60 seconds)

 

Everyone
My apologies for dual emails on this single problem.  But to clearly 
communicate the need, I am currently needing to know (essential requirement) 
how to change the Q65 primary/current operating duration (defaults 30 sec); how 
do I then change it to 60 sec so I can operate? 

 

Then part 2 (nice to have) is how does one change the default (where is the Mac 
equivalent of Windows WSJTX.ini file)?   Thank you 

 

Very 73,

Dave

 

From: David Schmocker via wsjt-devel 
Reply-To: WSJT software development 
Date: Sunday, January 8, 2023 at 2:33 PM
To: 
Cc: David Schmocker 
Subject: [wsjt-devel] Unable to find how to reset Q65A default Tx duration 
(defaults to 30 sec and my operating requires 60 seconds)

 

Hello,

Please advise where/how specifically do I change the Tx interval (duration) for 
Q65A. 

 

The default is currently 30 second period and my requirement needs 60 second 
default (Q65-60A for 6m EME) (in past versions this was settable from main 
screen and held there despite WSJT-X program restart). 

 

 

Operating platform:   Mac OS Mojave v10.14.6, Mac mini, 16GB 1600 MHz DDR3 RAM

 

Installed software version: WSJT-X v2.6.0 b7a9ef Improved  (Previously tried 
the regular version (not Improved), and the AL_Improved with all three of these 
versions testing the same in this regard (unable to move away from 30 second 
period for Q65).

 

 

Very grateful for all the team is doing and has done.  

 

Thank you, very 73, 

Dave KJ9I 

 

___ 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] Unable to find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds)

[David Schmocker via wsjt-devel]

Everyone
My apologies for dual emails on this single problem.  But to clearly 
communicate the need, I am currently needing to know (essential requirement) 
how to change the Q65 primary/current operating duration (defaults 30 sec); how 
do I then change it to 60 sec so I can operate? 

 

Then part 2 (nice to have) is how does one change the default (where is the Mac 
equivalent of Windows WSJTX.ini file)?   Thank you 

 

Very 73,

Dave

 

From: David Schmocker via wsjt-devel 
Reply-To: WSJT software development 
Date: Sunday, January 8, 2023 at 2:33 PM
To: 
Cc: David Schmocker 
Subject: [wsjt-devel] Unable to find how to reset Q65A default Tx duration 
(defaults to 30 sec and my operating requires 60 seconds)

 

Hello,

Please advise where/how specifically do I change the Tx interval (duration) for 
Q65A. 

 

The default is currently 30 second period and my requirement needs 60 second 
default (Q65-60A for 6m EME) (in past versions this was settable from main 
screen and held there despite WSJT-X program restart). 

 

 

Operating platform:   Mac OS Mojave v10.14.6, Mac mini, 16GB 1600 MHz DDR3 RAM

 

Installed software version: WSJT-X v2.6.0 b7a9ef Improved  (Previously tried 
the regular version (not Improved), and the AL_Improved with all three of these 
versions testing the same in this regard (unable to move away from 30 second 
period for Q65).

 

 

Very grateful for all the team is doing and has done.  

 

Thank you, very 73, 

Dave KJ9I 

 

___ 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] Unable to find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds)

[David Schmocker via wsjt-devel]

Hello,

Please advise where/how specifically do I change the Tx interval (duration) for 
Q65A. 

 

The default is currently 30 second period and my requirement needs 60 second 
default (Q65-60A for 6m EME) (in past versions this was settable from main 
screen and held there despite WSJT-X program restart). 

 

 

Operating platform:   Mac OS Mojave v10.14.6, Mac mini, 16GB 1600 MHz DDR3 RAM

 

Installed software version: WSJT-X v2.6.0 b7a9ef Improved  (Previously tried 
the regular version (not Improved), and the AL_Improved with all three of these 
versions testing the same in this regard (unable to move away from 30 second 
period for Q65).

 

 

Very grateful for all the team is doing and has done.  

 

Thank you, very 73, 

Dave KJ9I 

 

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

Re: [wsjt-devel] Blacklist feature

[David - K2DBK via wsjt-devel]

JTAlert (https://hamapps.com/) is an add-on for WSJT-X that does that. It's
also got a ton of other useful features.

 

73,

David, K2DBK

 

From: Bevan Daniel via wsjt-devel  
Sent: Saturday, January 7, 2023 6:38 AM
To: wsjt-devel@lists.sourceforge.net
Cc: Bevan Daniel 
Subject: [wsjt-devel] Blacklist feature

 

Hello Joe,

 

Would it be possible to implement a Blacklist feature, a list of call signs
you no longer want to respond to or be hijacked by?

 

73

Bevan

VK5BD

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

[wsjt-devel] WSJTX 2.6.0-rc6 Flex issue

[David Birnbaum via wsjt-devel]

I just tested rc6 on our remote Flex 6500 and things seemed ok. I was
focused on CAT control issues reported to this list. Found no problems here
(Win 11 up to date). Audio worked fine, some operator error in that mode
selection from menu doesn't change frequency list but using the button on
the UI does.

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

Re: [wsjt-devel] Bugreport FST4W spot upload to wsprnet

[David Owen via wsjt-devel]

Hi
At the moment I think that modes 2 and 15 are ambiguous in the WSPRNET database.
There does not seem to be an up-to date formal definition for uploads
(direct or bulk)
to the WSPRNET Database at present - at least none that I have found.
This is a bit annoying at times. This would be an oportunity for
someone who understands
the database to publish a short specification.
The interactive WSPRNET database works very well except for the "mode"
selection.

Regards

David Owen

GM1OXB

On Tue, Nov 22, 2022 at 6:26 PM Stefan HB9TMC via wsjt-devel
 wrote:
>
> Hi,
>
> When WSPR and FST4W spots are uploaded to wsprnet, there is an
> additional field to designate the mode.
>
>  From wsjtx/Network/wsprnet.ccp lines 274 to 288
> it was intended to use different mode IDs for WSPR and FST4W in order to
> distinguish between the two modes in the wsprnet database.
>
> WSPR-2: "2"
> WSPR-15: "15"
> FST4W-120: "3"
> FST4W-300: "5"
> FST4W-900: "16"
> FST4W-1800: "30"
>
> However, wsprnet does only accept the mode IDs 2, 5, 15 and 30. All
> other numbers are rewritten in their database to "2".
>
> FST4W-120 becomes "2" instead of "3"
> FST4W-900 becomes "2" instead of "16"
>
> So it still kind of works for all modes, except FST4W-900, which is
> stored as mode "2".
>
>
> There are two possible ways to fix this. Either wsprnet would accept the
> other mode IDs. Or it is fixed in WSJT-X.
>
> I tried to reach someone from wsrpnet, but without success.
> So, unless someone knows someone from wsrpnet who could fix it there, I
> would ask you to fix it in WSJT-X, by uploading FST4W-900 as mode "15".
>
>
> Thanks, 73
> Stefan
>
>
> ___
> 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] Fox Mode Button Behavior after software restart

[David Bean (KC2WUF) via wsjt-devel]

Yesterday I was working in the WAE RTTY contest when I saw a DXpedition F/H FT8 
operation. I stopped the RTTY contest, started WSJT-X v2.6.0-rc4 and hit the 
Hound button. I worked the DX station and shut down WSJT-X. 

Upon startup of WSJT-X today after the contest ended, The software was still in 
Hound mode (expected), but the Hound button wasn't highlighted (unexpected). 
Not a big deal, but thought I should mention it.
73 David KC2WUF
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib errors please for RC4 #hamlib

[David - K2DBK via wsjt-devel]

Using Icom 7600 and Windows 10:

 

[RIGCTRL][2022-09-14 16:16:36.723307][00:00:03.630366][error] 
rig_get_cache(298): unknown vfo=otherVFO

[RIGCTRL][2022-09-14 16:16:36.724306][00:00:03.630738][error] icom_set_vfo: 
unknown vfo 'currVFO'

[RIGCTRL][2022-09-14 16:16:36.724306][00:00:03.630753][error] icom_set_vfo: 
unsupported VFO otherVFO

[RIGCTRL][2022-09-14 16:16:36.802307][00:00:03.708487][error] icom_set_vfo: Rig 
does not have VFO A/B?

[RIGCTRL][2022-09-14 16:16:36.802307][00:00:03.708511][error] icom_set_vfo: 
Mapping VFOB=Sub

[RIGCTRL][2022-09-14 16:16:36.879308][00:00:03.786179][error] icom_set_vfo: Rig 
does not have VFO A/B?

[RIGCTRL][2022-09-14 16:16:36.879308][00:00:03.786203][error] icom_set_vfo: 
Mapping VFOA=Main

[RIGCTRL][2022-09-14 16:16:37.303309][00:00:04.210091][error] icom_set_vfo: Rig 
does not have VFO A/B?

[RIGCTRL][2022-09-14 16:16:37.303309][00:00:04.210114][error] icom_set_vfo: 
Mapping VFOA=Main

[RIGCTRL][2022-09-14 16:16:37.439312][00:00:04.345583][error] rig_get_vfo: no 
get_vfo

 

From: Black Michael via wsjt-devel  
Sent: Wednesday, September 14, 2022 6:05 PM
To: WSJT Software Development 
Cc: Black Michael 
Subject: [wsjt-devel] Hamlib errors please for RC4 #hamlib

 

If everyone running RC4 would please check their wsjtx_syslog.log file and see 
if there are any hamlib errors I would appreciate it.  If errors/warning are 
seen please send the log to me

 

Getting ready to release Hamlib 4.5 and would like to ensure all is working 
well.

 

For Windows

C:\Users\[username]\AppData\Local\WSJT-X\wsjtx_syslog.dat

For Linux

/home/[username]\.local\share\WSJT-X\wsjtx_syslog.dat

 

And RC4 version is not available for MacOS so no testing for Macs is needed.

 

Mike W9MDB

 

 

 

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

Re: [wsjt-devel] TX enabled after changing frequency with Hound set

[David - K2DBK via wsjt-devel]

This appears to have been fixed in rc4 (though I didn’t see it in the release 
notes). Can anyone else confirm?

 

From: Sam W2JDB via wsjt-devel  
Sent: Tuesday, August 30, 2022 10:50 AM
To: wsjt-devel@lists.sourceforge.net
Cc: Sam W2JDB 
Subject: Re: [wsjt-devel] TX enabled after changing frequency with Hound set

 

Duplicated here as well. Even tried to change the focus to another item and it 
still enabled TX when I press Enter. 

 

73,

Sam W2JDB

 

 

-Original Message-
From: Black Michael via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> >
To: David - K2DBK via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> >
Cc: Black Michael mailto:mdblac...@yahoo.com> >
Sent: Tue, Aug 30, 2022 9:59 am
Subject: Re: [wsjt-devel] TX enabled after changing frequency with Hound set

Duplicated this behavior -- doesn't matter if you enter a frequency or not.  
Just hitting enter on the box enables TX if there are messages in the generated 
messages.

 

If you just click somewhere else instead of hitting Enter it works OK.

 

And this only happens on Hound mode.

 

Mike W9MDB

 

 

 

On Tuesday, August 30, 2022 at 08:48:29 AM CDT, David - K2DBK via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net> > 
wrote: 

 

 

I’m running 2.6.0-rc3 under Windows 10 21H1 build 19043.1889 and have noticed 
the following behavior:

 

Start with Enable Tx turned off (grey, not red).

Click on the “H” button to enable Hound mode.

Click on the band dropdown, and manually enter a frequency (e.g., 14.088), hit 
enter

Enable Tx will turn red, and transmitting will begin at the proper point in the 
cycle.

 

Expected behavior is that Enable Tx will stay disabled.

 

73,

David, K2DBK

 

 

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

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto: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] TX enabled after changing frequency with Hound set

[David - K2DBK via wsjt-devel]

I'm running 2.6.0-rc3 under Windows 10 21H1 build 19043.1889 and have
noticed the following behavior:

 

Start with Enable Tx turned off (grey, not red).

Click on the "H" button to enable Hound mode.

Click on the band dropdown, and manually enter a frequency (e.g., 14.088),
hit enter

Enable Tx will turn red, and transmitting will begin at the proper point in
the cycle.

 

Expected behavior is that Enable Tx will stay disabled.

 

73,

David, K2DBK

 

 

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

Re: [wsjt-devel] Release Candidate WSJT-X 2.6.0-rc3

[David Garnier via wsjt-devel]

 Scroll down the page

Dave - wb9own


 On Monday, August 22, 2022, 11:28:31 AM CDT, Bobby Chandler via wsjt-devel 
 wrote:  
 
  
I don't find rc-3 on the page yet>
 
Bobby/N4AU
 
 On 8/22/2022 9:39 AM, Joe Taylor via wsjt-devel wrote:
  
Dear WSJT-X Users, 
 
 We are pleased to announce that Release Candidate WSJT-X 2.6.0-rc3 is ready 
for download by beta testers. A list of its essential changes from previous 
releases can be found in the Release Notes: 
 https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt 
 
 Links for downloading WSJT-X 2.6.0-rc3 can be found on the WSJT-X Home Page, 
https://physics.princeton.edu/pulsar/k1jt/wsjtx.html 
 Scroll down to find "Candidate release:  WSJT-X 2.6.0-rc3". 
 
 We hope you will enjoy using this beta release of WSJT-X 2.6.0.  As a beta 
tester you should report on your experiences with its new features, successful 
and otherwise, on one of the relevant WSJT forums.  Bugs should be reported by 
following instructions found here in the User Guide: 
 
https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.6.0-rc3.html#_bug_reports
 
 
 WSJT-X and MAP65 are licensed under the terms of Version 3 of the GNU General 
Public License (GPLv3).  Development of this software is a cooperative project 
to which many amateur radio operators have contributed.  If you use our code, 
please have the courtesy to let us know about it.  If you find bugs or make 
improvements to the code, please report them to us in a timely fashion.  
Additional licensing details can be found here: 
 https://physics.princeton.edu//pulsar/k1jt/devel.html 
 
  73 from the WSJT Core Development Team 
  Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Chet, KG4IYS; Uwe, DG2YCB; 
  Brian, N9ADG; and John, G4KLA 
 
 
 ___ 
 wsjt-devel mailing list 
 wsjt-devel@lists.sourceforge.net 
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
 
 -- n...@outlook.com  n...@arrl.net 
___
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] Dropdown issue when switching configs

[David - K2DBK via wsjt-devel]

Hi Mike,

 

Resetting the frequencies in the Hound configuration seems to have done the 
trick. I’ll go back and update them to the actual frequencies used for F/H.

 

Has any thought been given to allowing a set of Hound frequencies to exist 
similar to how there are separate flags for FT8, FT4, etc? With the new Hound 
button the only reason I now need that separate configuration is for the 
frequencies; if they could “co-exist” with the regular FT-8 frequencies I 
wouldn’t need that.

 

In any case, thanks for the help.

 

David, K2DBK

 

From: Black Michael via wsjt-devel  
Sent: Friday, August 5, 2022 5:22 PM
To: David - K2DBK via wsjt-devel 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Dropdown issue when switching configs

 

I can't duplicate that problem here -- presumably your Hound frequencies were 
done in a earlier version?

Have you tried resetting the frequencies?

 

 

File/Settings -- Frequencies tab -- right-click in list and select "Reset".

Probably in the Hound config.

 

Mike W9MDB

 

 

 

On Friday, August 5, 2022 at 02:35:40 PM CDT, David - K2DBK via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net> > 
wrote: 

 

 

Anyone?

 

From: David - K2DBK via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> > 
Sent: Wednesday, July 27, 2022 7:59 PM
To: wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 
Subject: [wsjt-devel] Dropdown issue when switching configs

 

I’m running 2.6.0-rc2 under Windows 10 21H1 Build 19043.1826.  I’m having an 
issue where if I switch to a configuration that has Hound mode enabled (via the 
new buttons), I can’t select anything from the band mode dropdown until I 
select another mode (from the new buttons), at which point it works normally. 
Even if I enter a frequency manually into the band dropdown, I still can’t 
actually get the frequencies to populate and drop down.

 

Here’s a link to a video I took demonstrating this: 
https://www.youtube.com/watch?v=_AlZwbpyq8w

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto: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] Dropdown issue when switching configs

[David - K2DBK via wsjt-devel]

Anyone?

 

From: David - K2DBK via wsjt-devel  
Sent: Wednesday, July 27, 2022 7:59 PM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] Dropdown issue when switching configs

 

I'm running 2.6.0-rc2 under Windows 10 21H1 Build 19043.1826.  I'm having an
issue where if I switch to a configuration that has Hound mode enabled (via
the new buttons), I can't select anything from the band mode dropdown until
I select another mode (from the new buttons), at which point it works
normally. Even if I enter a frequency manually into the band dropdown, I
still can't actually get the frequencies to populate and drop down.

 

Here's a link to a video I took demonstrating this:
https://www.youtube.com/watch?v=_AlZwbpyq8w

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

[wsjt-devel] Dropdown issue when switching configs

[David - K2DBK via wsjt-devel]

I'm running 2.6.0-rc2 under Windows 10 21H1 Build 19043.1826.  I'm having an
issue where if I switch to a configuration that has Hound mode enabled (via
the new buttons), I can't select anything from the band mode dropdown until
I select another mode (from the new buttons), at which point it works
normally. Even if I enter a frequency manually into the band dropdown, I
still can't actually get the frequencies to populate and drop down.

 

Here's a link to a video I took demonstrating this:
https://www.youtube.com/watch?v=_AlZwbpyq8w

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

Re: [wsjt-devel] Bug Report

[David Tiller via wsjt-devel]

Jason,

This sounds like a textbook example of RFI getting into your computer or USB 
cable. I had a similar issue on 80m and found that a few well-placed ferrites 
on my USB cable fixed the issue.

Search for "FT8 RFI" for other folks advice.

To verify, try transmitting into a dummy load or at _very_ low power. If it 
doesn't happen, you've proven it's due to RFI.


> On May 9, 2022, at 10:25 AM, W2JDM via wsjt-devel 
>  wrote:
> 
>  
> WSJTX Version: 2.5.4
> OS – Mac Monterey 12.3.1
> Radio – Yaesu 991A
> SiliconLabs Driver – 6.0.2 for Mac
>  
> When tuned to 40m (and only 40m), using FT8, the software loses CAT control 
> shortly after transmitting.  The symptoms are that it will hold the transmit 
> too long and eventually show ORANGE status in WSJTX.  It will reset and 
> reconnect, but not after losing the QSO due to timing issues.  This occurs 
> each and every time I transmit on 40m, including when using TUNE.  I want to 
> emphasize that it seems to ONLY occur on 40m and not any other band.  I use 
> other software that also has CAT control over the 991A and it works as 
> designed.
>  
> I have also changed the mode to FT4 and 40m behaves normally.  It seems 
> isolated to only when using FT8 and 40m.
>  
> Please let me know if you need any additional details.
>  
> 73
> Jason – W2JDM
>  
> ___
> 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] want to avoid duplicate/redundant effort: any work done towards integrating HackRF into WSJT-X?

[David Tiller via wsjt-devel]

If your use case is compatible with soapysdr, I’d suggest adding support for 
that; it supports a lot of SDRs. 

Are you also going to try to implement sdr audio? That’s a different kettle of 
fish. 

> On Feb 13, 2022, at 18:00, William Smith via wsjt-devel 
>  wrote:
> 
> Looks like it’s _not_ in Hamlib, which is probably where you want to add it, 
> so wsjt and others will pick it up.
> 
> https://hamlib.github.io
> 
> 73, Willie N1JBJ
> 
> 
>> On Feb 13, 2022, at 5:35 PM, Lillian Kish via wsjt-devel 
>>  wrote:
>> 
>> I want to add direct rig control for the HackRF SDR into WSJT.
>> 
>> Before I go and reinvent the wheel, i want to ask if any work has been done 
>> on this before? 
>> 
>> Thanks!
>> 
>> 
>> ___
>> 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] Additional info on WSJT-X arrow size discrepancy

[David Tiller via wsjt-devel]

Very interesting. I have these font-y lines in my .ini file. I take it the 
first is for astronomical data, the second for the RX lists, and the last for 
the rest of the UI. 

Now that I know where I can manually revert things, I'll try a few fonts.

Thanks!

[Astro]
font="Courier,18,-1,5,50,0,0,0,0,0"

[Configuration]
DecodedTextFont="Courier,10,-1,5,50,0,0,0,0,0"
Font=".Lucida Grande UI,13,-1,5,50,0,0,0,0,0"


> On Jan 15, 2022, at 3:30 PM, Alex Lelievre via wsjt-devel 
>  wrote:
> 
> Hi David,
> 
> I think that the font panel doesn’t show the font when .AppleSystemUIFont is 
> the selected font.  You can look inside the WSJT-X.ini file to see what font 
> you have selected.  Offhand, I have it set to 12 point.   The ini file is in 
> ~/Library/Preferences/WSJT-X.ini.
> 
> alex K6LOT
> 
> 
>> On Jan 15, 2022, at 5:08 AM, David Tiller via wsjt-devel 
>>  wrote:
>> 
>> Alex,
>> 
>> Thanks again for the reply - I must be an idiot; I searched for a font 
>> chooser in WSJT-X before I went on the OS font wild goose chase. I didn't 
>> even see that!
>> 
>> Interestingly, when I click on 'Font', it shows the following - note that no 
>> Family is selected (I scrolled all the way down - nada)!!! Do you know what 
>> it's supposed to be, or at least what you have selected for a font?
>> 
>> 73, K4DET
>> 
>> 
>> 
>>> On Jan 14, 2022, at 9:53 PM, Alex Lelievre via wsjt-devel 
>>>  wrote:
>>> 
>>> Hi David,
>>> 
>>> You want to take a look at the font for WSJT-X, I was thinking perhaps you 
>>> changed it in order to reproduce this bug.
>>> 
>>> Here’s where to look (in the Preferences for WSJT-X):
>>> 
>>> 
>>> 
>>> alex K6LOT
>>> 
>>>> On Jan 14, 2022, at 6:13 PM, David Tiller via wsjt-devel 
>>>>  wrote:
>>>> 
>>>> Alex,
>>>> 
>>>> Thanks for the reply. 
>>>> 
>>>> I'm not sure where in OSX 10.13.6 to look, but according to this page ( 
>>>> https://apple.stackexchange.com/questions/12661/whats-the-font-in-mac-os-xs-gui
>>>>  ) the default font is San Francisco. I don't think I've changed it.
>>>> 
>>>> I cannot find SanFrancisco listed anywhere in the choices available to 
>>>> TextEdit, but I do see a lot of files named SF*.otf in 
>>>> /System/Library/Fonts which I assume are San Francisco OpenType font 
>>>> files. I also see SF OpenType fonts listed in SystemInformation/Fonts with 
>>>> many in the family "System Font" - all mention SanFrancisco in the 
>>>> Copyright.
>>>> 
>>>> Lucida Grande displays the two arrows with different sizes.
>>>> 
>>>> If you'd like to take this offline from the group, email me at mycall @ 
>>>> arrl . net.
>>>> 
>>>> Thanks!
>>>> 
>>>> 
>>>> 
>>>>> On Jan 14, 2022, at 2:58 PM, Alex Lelievre via wsjt-devel 
>>>>>  wrote:
>>>>> 
>>>>> Hi David,
>>>>> 
>>>>> What font do you have your UI set to?  That could have some effect.
>>>>> 
>>>>> alex K6LOT
>>>>> 
>>>>>> On Jan 14, 2022, at 11:00 AM, David Tiller via wsjt-devel 
>>>>>>  wrote:
>>>>>> 
>>>>>> Dear devs,
>>>>>> 
>>>>>> I know this is a very minor issue, but I'd like to pass on some 
>>>>>> additional info I've found.
>>>>>> 
>>>>>> The issue is this: Using WSJT-X 2.5.4 under OSX 10.13.6, the arrows on 
>>>>>> the 'Set TX freq to RX freq' and 'Set RX freq to TX freq' buttons are 
>>>>>> not the same size.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> As you can see, the up-arrow button is much larger than the down-arrow, 
>>>>>> even though the arrow glyph itself seems smaller.
>>>>>> 
>>>>>> I found the definitions of the buttons 'pbT2R' and 'pbR2T' in 
>>>>>> https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/widgets/mainwindow.ui
>>>>>>  - the definitions are identical except that on my Mac, the UTF-8 
>>>>>> characters used to represent the arrows are not rendering to the same 
>>>>>> size. The misrendering shows on the page at SF in chrome and Safari as 
>>>>>> well as if

Re: [wsjt-devel] Additional info on WSJT-X arrow size discrepancy

[David Tiller via wsjt-devel]

Alex,

Thanks for the reply. 

I'm not sure where in OSX 10.13.6 to look, but according to this page ( 
https://apple.stackexchange.com/questions/12661/whats-the-font-in-mac-os-xs-gui 
<https://apple.stackexchange.com/questions/12661/whats-the-font-in-mac-os-xs-gui>
 ) the default font is San Francisco. I don't think I've changed it.

I cannot find SanFrancisco listed anywhere in the choices available to 
TextEdit, but I do see a lot of files named SF*.otf in /System/Library/Fonts 
which I assume are San Francisco OpenType font files. I also see SF OpenType 
fonts listed in SystemInformation/Fonts with many in the family "System Font" - 
all mention SanFrancisco in the Copyright.

Lucida Grande displays the two arrows with different sizes.

If you'd like to take this offline from the group, email me at mycall @ arrl . 
net.

Thanks!



> On Jan 14, 2022, at 2:58 PM, Alex Lelievre via wsjt-devel 
>  wrote:
> 
> Hi David,
> 
> What font do you have your UI set to?  That could have some effect.
> 
> alex K6LOT
> 
>> On Jan 14, 2022, at 11:00 AM, David Tiller via wsjt-devel 
>> mailto:wsjt-devel@lists.sourceforge.net>> 
>> wrote:
>> 
>> Dear devs,
>> 
>> I know this is a very minor issue, but I'd like to pass on some additional 
>> info I've found.
>> 
>> The issue is this: Using WSJT-X 2.5.4 under OSX 10.13.6, the arrows on the 
>> 'Set TX freq to RX freq' and 'Set RX freq to TX freq' buttons are not the 
>> same size.
>> 
>> 
>> 
>> As you can see, the up-arrow button is much larger than the down-arrow, even 
>> though the arrow glyph itself seems smaller.
>> 
>> I found the definitions of the buttons 'pbT2R' and 'pbR2T' in 
>> https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/widgets/mainwindow.ui 
>> <https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/widgets/mainwindow.ui> 
>> - the definitions are identical except that on my Mac, the UTF-8 characters 
>> used to represent the arrows are not rendering to the same size. The 
>> misrendering shows on the page at SF in chrome and Safari as well as if you 
>> cut-and-paste into a unicode-aware editor (TextEdit, Pages, etc).
>> 
>> I also noted that when the text from the above page (rendered in chrome) is 
>> pasted into TextEdit, the font used for the majority of the text is 
>> Courier/Regular/14. The font for the up-arrow character switches to Courier 
>> New/Regular/14. The down-arrow, however, does NOT seem to trigger a switch 
>> to Courier New/Regular 14, rather it shows as 'Fixed/14' with no typeface 
>> chosen. If I force the down-arrow font to Courier New/Regular/14, the glyph 
>> changes to the same size as the up arrow. I cannot force the down-arrow font 
>> to Courier/Regular/14 - it will not accept that, as if the glyph is not in 
>> that font.
>> 
>> Something is afoot with font handling on OSX. I tried a few other fonts in 
>> TextEdit:
>> 
>> Fonts that render the arrows with different sizes: American Typewriter, 
>> Avenir, Courier, Bank Gothic, Baskerville, Bodoni, Cochin, Copperplate, etc
>> 
>> Fonts that render the arrows with the same size: Andale Mono, Arial, 
>> Chalkboard, Comic Sans, Courier New, Times New Roman, etc
>> 
>> Unfortunately the other up- and down-arrows in the unicode space (23F6, 
>> 23F7, 2BC5, 2BC6) are in miscellaneous pages that are seemingly not present 
>> in many fonts. 
>> 
>> Image clip of definition of the SMALL UP ARROW:
>> 
>> 
>> 
>> Image clip of definition of the LARGE DOWN ARROW:
>> 
>> 
>> 
>> Thanks for reading this far!
>> 
>> 73, K4DET
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net <mailto: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 v2.5.4 (configurations)

[david--- via wsjt-devel]

Thank you Peter!

I did not know that.

  

David, AK2L

  

  

From: Peter Sumner via wsjt-devel  
Sent: Monday, January 10, 2022 17:22
To: WSJT software development 
Cc: Peter Sumner 
Subject: Re: [wsjt-devel] wsjt-x v2.5.4 (configurations)

  

Hi David (AK2L),

  this does not have to be the case, if you tick enable the setting "Monitor 
returns to last used frequency" in each of your configs on the main settings 
page, you may get a   pleasant surprise. :-)

  

regards,

Peter, vk5pj

  

On Tue, Jan 11, 2022 at 10:21 AM david--- via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net> > 
wrote:

Roger,

When you switch modes as you described, WSJT-X will read the radio's current 
frequency, but will not automatically switch it for you.   I see this all the 
time when I switch between FT4 and FT8.

It is normal behavior and you will have to select the frequency you want from 
the combo box.

David, AK2L


-Original Message-
From: Martin Davies G0HDB via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> > 
Sent: Monday, January 10, 2022 15:54
To: WSJT software development mailto:wsjt-devel@lists.sourceforge.net> >
Cc: Martin Davies G0HDB mailto:marting0...@gmail.com> >
Subject: Re: [wsjt-devel] wsjt-x v2.5.4 (configurations)

On 10 Jan 2022 at 22:26, roger stafford via wsjt-devel wrote:

> Hi
> I use both ft8 and 165 on six meters a lot and of late have to swap between 
> the to modes often while trying to work dx.
> So I set up 2 configurations which works well apart from the freq (ft8 313 
> and qt65 275 which I have to change each time the rest of the settings are 
> saved every time.
> Is this a fault my end ? or could it be changed to save the freq in the 
> config.
> 
> Many thanks stay SAFE
> 
> De roger vk3fz

Hi Roger, for each configuration you can edit the frequency list so that it 
includes only the frequencies appropriate for that configuration's mode, ie. 
when you're in the FT8 configuration you could edit the frequency list so that 
it contains only the 313 (and I'd suggest the 323) frequencies, and similarly 
for the Q65 config.

When you edit the frequency list you can 'tag' each frequency with the mode to 
which it's appropriate, rather than having 'All' selected for the mode.

HTH,
--
Martin G0HDB

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



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



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto: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 v2.5.4 (configurations)

[david--- via wsjt-devel]

Roger,

When you switch modes as you described, WSJT-X will read the radio's current 
frequency, but will not automatically switch it for you.  I see this all the 
time when I switch between FT4 and FT8.

It is normal behavior and you will have to select the frequency you want from 
the combo box.

David, AK2L


-Original Message-
From: Martin Davies G0HDB via wsjt-devel  
Sent: Monday, January 10, 2022 15:54
To: WSJT software development 
Cc: Martin Davies G0HDB 
Subject: Re: [wsjt-devel] wsjt-x v2.5.4 (configurations)

On 10 Jan 2022 at 22:26, roger stafford via wsjt-devel wrote:

> Hi
> I use both ft8 and 165 on six meters a lot and of late have to swap between 
> the to modes often while trying to work dx.
> So I set up 2 configurations which works well apart from the freq (ft8 313 
> and qt65 275 which I have to change each time the rest of the settings are 
> saved every time.
> Is this a fault my end ? or could it be changed to save the freq in the 
> config.
> 
> Many thanks stay SAFE
> 
> De roger vk3fz

Hi Roger, for each configuration you can edit the frequency list so that it 
includes only the frequencies appropriate for that configuration's mode, ie. 
when you're in the FT8 configuration you could edit the frequency list so that 
it contains only the 313 (and I'd suggest the 323) frequencies, and similarly 
for the Q65 config.

When you edit the frequency list you can 'tag' each frequency with the mode to 
which it's appropriate, rather than having 'All' selected for the mode.

HTH,
--
Martin G0HDB

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



___
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] Cleaner Updates/Installs

[david--- via wsjt-devel]

Dave,

Michael is correct -- this issue should be fixed.

But, I have an easier way for you to deal with this in the future...

I am not interested in installing multiple versions on my computer.  (I know 
Michael has to because he has to test Hamlib.)

On my computer, I install WSJT-X in this folder regardless of version:

 C:\Program Files\WSJT-X

To do that, you must override the default path offered by the program.  This 
will leave you with one version.  Also, I do not allow the program to add a new 
shortcut every time an update is installed.  Instead, I have one shortcut on my 
desktop to the above path.

Unfortunately, this will still leave you with multiple versions listed in the 
Add/Remove Apps control panel.  To clean that up:
[1] change the above path temporarily to something else such as:
 C:\Program Files\WSJT-Xxxx
[2] go to the Add/Remove Apps control panel.
[3] uninstall each of the older versions of WSJT-X listed there.
 Each time you ask Windows to uninstall, it will say something like
 "I can't find that.  Would you it removed from the list of programs."
 You say yes.
[4] When you are done with step 3, leaving only the most recent version of 
WSJT-X showing, undo the name change you made in step 1.

Yes, it's a pain in the neck.  But it is a lot faster than what you were doing.

David, AK2L







-Original Message-
From: Black Michael via wsjt-devel  
Sent: Monday, January 10, 2022 06:26
To: wsjt-devel 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Cleaner Updates/Installs

This is a long-standing problem that needs to be fixed.

WSJT-X should use a default path that includes the version#.  

That will provide two things

#1 Very easy for user to start whichever version they want
#2 Avoid duplicate program entries

This patch makes the default install directory match the WSJT-X version.

diff --git a/CMakeCPackOptions.cmake.in b/CMakeCPackOptions.cmake.in index 
eceae4edf..ae1c70900 100644
--- a/CMakeCPackOptions.cmake.in
+++ b/CMakeCPackOptions.cmake.in
@@ -5,7 +5,8 @@
 set (CPACK_PACKAGE_VENDOR "@PROJECT_VENDOR@")
 set (CPACK_PACKAGE_CONTACT "@PROJECT_CONTACT@")
 set (CPACK_RESOURCE_FILE_LICENSE "@PROJECT_SOURCE_DIR@/COPYING") -set 
(CPACK_PACKAGE_INSTALL_DIRECTORY ${CPACK_PACKAGE_NAME})
+#set (CPACK_PACKAGE_INSTALL_DIRECTORY 
+${CPACK_PACKAGE_NAME}$NAME{CPACK_PACKAGE_VERSION_PATCH})
+set (CPACK_PACKAGE_INSTALL_DIRECTORY 
+"@CPACK_PACKAGE_NAME@-PACK_PACKAGE_VERSION_MAJOR@.@CPACK_PACKAGE_VERSIO
+N_MINOR@.@CPACK_PACKAGE_VERSION_PATCH@")
 set (CPACK_PACKAGE_EXECUTABLES wsjtx "@PROJECT_NAME@")
 set (CPACK_CREATE_DESKTOP_LINKS wsjtx)
 set (CPACK_STRIP_FILES TRUE)


Mike W9MDB






On Monday, January 10, 2022, 12:57:41 AM CST, Dave Fitches via wsjt-devel 
 wrote: 









Hi folks, 

Firstly - awesome work with the program to everyone involved (past and 
present!) 

Just one nit-picky thing... 
When we have a new version come out, and I install it, it creates a brand new 
Start Menu folder for the new version. 

So I now have in my Start Menu: 
wsjtx 2.40
wsjtx 2.50
wsjtx 2.52
wsjtx 2.54 

Likewise in my installed programs listing in "Add/Remove Programs" I have all 4 
versions of the software listed. And given the program installs to the same 
location every time it installs, if I remove the old versions of the software, 
it causes no end of problems. 

To remove the old versions I have to remove the oldest. Then because all the 
files are gone, to remove the next oldest I have to re-install the new version. 
THEN remove the next oldest. ...rinse and repeat. 

To my mind - it should be working thus: 

* If you're installing over an existing version in the SAME INSTALL DIRECTORY 
(Default behaviour), then it should update the existing package and update the 
version number in the Installed Programs list to prevent duplicate listings of 
the same install location, and either use a Common Name for the Start Menu 
folder, or remove the OLD Start Menu folder for the previous version number and 
add the NEW version into Start Menu. 

* If you're installing to a brand new directory and there's an existing copy 
installed elsewhere, leave the existing stuff alone because some people might 
want to run an old version and a new version, so list them seperately. 

I admit - I have ZERO programming chops to do any of these things myself, but I 
can make constructive suggestions for future releases!  

Again - I wish to say I am in awe of the software as it stands! These points 
above are piddling things, especially when compared to the joy this program 
brings to a new Ham Operator working off a compromised antenna using QRP, and 
is still able to make DX contacts despite that! If there was a "Donate here to 
support this software" link - I'd be doing it! 

Thanks and 73 

de VK3DVF 


-- 


  = Dave 'Rusti' Fitches = 

_

[wsjt-devel] WSJT-X 2.5.2 cosmetic issue

[David Tiller via wsjt-devel]

All,

I've been running WSJT-X 2.5.2 under OSX 10.13.6 and have noticed that the 
up-pointing arrow for setting the TX freq is abnormally large.

It doesn't seem related to the size of the main window or whether or not it (or 
the down arrow) has been clicked.

Thanks and 73 - K4DET

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

Re: [wsjt-devel] Yaesu rig split problems

[david--- via wsjt-devel]

I have a FTDX-5000 with WSJT-X 2.5.1 and use split with no difficulty.  (And 
have had no difficulty running split all the way back to the first version of 
WSJT-X that supported FT8.)

I do not use DATA modes – just plain USB filtering.

 

David, AK2L

 

 

From: Black Michael via wsjt-devel  
Sent: Thursday, November 4, 2021 05:36
To: WSJTX Group ; WSJT Software Development 

Cc: Black Michael 
Subject: [wsjt-devel] Yaesu rig split problems

 

I'm trying to solve rig split operation problems with Yaesu rigs and need some 
Yaesu operator help...

 

I need any Yaesu owners to state their rig model and whether or not "Rig split" 
works in WSJT-X or if you see flashing on the rig when Rig split is turned on.

 

So 3 questions

#1 Can you make QSOs?

#2 Does rig operation look smooth?  Should be a little activity as freq & mode 
get set on both VFOs but it I'd like to know if the display goes a little nuts 
when it's happening with Rx/Tx flickering or such.

 

Mike W9MDB

 

 

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

[wsjt-devel] Feature request

[David Wells via wsjt-devel]

WSJT-X is a GREAT program and I tremendously enjoy it!  However, one small 
change in FT-4 and FT-8 (and potentially other modes) would make it easier to 
pick out desired callsigns.
In the display of FT-4 and FT-8 signals, the callsign of the intended station 
is shown first, as it should be, followed by the callsign of the sending 
station when receiving.  There is a space between the callsigns.  If this space 
could instead be a tab, all of the sending callsigns could be shown in the same 
straight column.  It would make it much easier for every user to quickly scan 
down the list and single out a station for a desired contact.  As it is now, 
more time is necessary to scan for callsigns since our eyes have to constantly 
dart left and right to find the callsign in each line.
This should be an easy fix and would greatly enhance quickly scanning the list.
Thank you for the program and your time, have a great day!
Dave Wells, KD5E
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows installers alerting for malware on VirusTotal

[David - K2DBK via wsjt-devel]

I don’t know how much this helps, but one thing I’ve done is to sign up a 
(free) Virus Total account. It allows you to weigh in on the community score.

 

From: Black Michael via wsjt-devel  
Sent: Tuesday, October 26, 2021 11:43 PM
To: Joseph Botto via wsjt-devel 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Windows installers alerting for malware on VirusTotal

 

I just submitted wsjtx-2.5.1-win64.exe to virus total and got 1 hit on a 
generic (it shows 2 but lists 1).

https://www.virustotal.com/gui/file/b2007bf26ede3e8f68866d817971645c3c6fb88c9a952ba7bc3982993ce453c8

None of the listed items that are inserted are on my system so it's definitely 
a false positive.

 

Anti-virus vendors are false alarming on all sorts of things nowadays.  All you 
have to do is submit it and they whitelist it pretty quickly.

 

Not seen 1 piece of ham software yet that had a virus in it.  JTAlert gets 
alerted on every release and gets whitelisted every release too.

 

Mike W9MDB

 

 

 

 

On Tuesday, October 26, 2021, 05:46:53 PM CDT, Joseph Botto via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net> > 
wrote: 

 

 

Hello all, 

Over the last few releases of WSJT-X, the Windows installers available for 
download from the main WSJT-X site 
(https://physics.princeton.edu/pulsar/k1jt/wsjtx.html) have been alerting on 
VirusTotal for malware. This has been exhibited going back to at-least the 
2.3.x branch. The VirusTotal scan results can be viewed directly by uploading 
one of the installers to VirusTotal, and either seeing the archived results, or 
re-running the scans. 

 

While the installers are only alerting for 3/64 scanner products (which 
indicates that they are likely false positives), I personally won't install 
anything downloaded from the internet that has even one alert. 

Would the WSJT-X developers be able to contact those alerting scanners to see 
why the installers are being flagged as containing malware?


 

 

73,

 

-Joe Botto

KM4SQS

http://km4sqs.blogspot.com/

https://github.com/km4sqs

 

 

___
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] Message Bit to Request Other Station to QSY to your Frequency

[David Tiller]

> On Jul 8, 2021, at 1:21 PM, Gary McDuffie  wrote:
> 
> I find a few of them won’t bother to respond until I’m within a few hundred 
> hertz of them.

You hit the nail on the head with this comment. I think there are still 
operators that insist on using narrow filters and are therefore deaf to callers 
outside their tiny passband. It's annoying to have to jump into the inevitable 
pileup on/near their TX frequency only to be swamped by KW-class stations. 

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

Re: [wsjt-devel] 2021 Field Day Logging Issues

[david]

Add my vote for this:

1) In the contest log set the record entry field for the newest/latest entry to 
be that entry’s actual count since the first log, vs 1. Having the latest log 
at the top of the window is good, but having it numbered one not so much - 
especially if you are trying to keep track of your total log count as I was.

David, AK2L




-Original Message-
From: Al Pawlowski  
Sent: Monday, June 28, 2021 08:00
To: WSJT software development 
Subject: Re: [wsjt-devel] 2021 Field Day Logging Issues

WSJT-x worked well for me this FD. However, I would suggest a couple of 
changes/improvements be considered.

1) In the contest log set the record entry field for the newest/latest entry to 
be that entry’s actual count since the first log, vs 1. Having the latest log 
at the top of the window is good, but having it numbered one not so much - 
especially if you are trying to keep track of your total log count as I was.

2) Add some type of real obvious duplicate log entry indicator to the contest 
log so that such log entries can be found easily and corrected, perhaps even in 
for real time. Took me some time last night to find a few dupe’s I had.

3) At least for FD configurations, add a highlight color for Dupe and/or 
New/Unworked call on band or mode. JTalert “B4” helped on this, but was far 
from perfect.


Al Pawlowski, K6AVP
Los Osos, CA USA





___
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 Development and AVX

[David Spoelstra]

Another Linux way is to use the "lscpu" command.

An easy way to see the flags would be "lscpu | grep -i avx".

-David, N9KT



On Wed, Jun 9, 2021 at 2:53 PM Michael Pittaro  wrote:

> Intel provides tools to do the feature identification for you.  See:
>
> https://www.intel.com/content/www/us/en/support/articles/05607/boards-and-kits/desktop-boards.html
>
> The Intel processor identification utility provides the information
> directly.  (I believe this is windows only, but didn't dig for Linux
> versions.)
>
> The Intel® Processor Diagnostic Tool also provides that information, plus
> diagnostic tests.It used to be available for Linux, but a quick check
> shows it's currently windows only.
>
> Us Linux hacks can 'cat /proc/cpuinfo' to get this information, but it
> requires some interpretation of the flags field :-)
>
> 73's
> mike, kj6vcp
>
> ___
> 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] Q65 and split mode - did I miss something?

[David Tiller]

Dear WSJTX authors,

I just tried Q65 with 2.4.0 final (OSX 10.13.6), and so far, so good. I tried 
using split mode with my IC 756PRO and didn't get the same results as I get on 
the other modes; i.e. for TX frequencies below 1500 Hz the TX VFO does NOT 
'drop down' in frequency to ensure the audio going into the radio is >= 1500 
Hz. 

Example that works as expected with FT8:

Split set to 'rig', RX VFO 50.313. When I choose TX freq 500, the TX VFO 
immediately switches to 50.312. 

Example that doesn't work as expected with Q65:

Split set to 'rig', RX VFO 50.275. When I choose any TX frequency, the TX VFO 
_stays_ on 50.275.

If I missed something in the user's guide or quick start guide, please feel 
free to chastise me.

Thanks in advance, K4DET

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

Re: [wsjt-devel] FT4 logging prompt

[David Gillooly]

Some hams on there end will not log a QSO unless they receive the
confirmation 73 after their RRR/RR73.

I am not saying its wrong or right just that it's the practice of some hams

Dave, AA6RE

On Thu, May 6, 2021 at 1:34 PM Martin Davies G0HDB 
wrote:

> The FT4 mode was introduced in WSJT-X version 2.1.0 in 2019; the release
> notes and announcements state that the mode is intended for use in HF
> digital contesting where 'quick-fire' exchanges such as those achieved
> using RTTY are desired.  I'd like to suggest a change that would help
> achieve this aim a bit better; the following applies to v2.1.0 and all
> subsequent versions up to and including v2.3.1 (I haven't yet tried any of
> the RC versions of v2.4.0).
>
> An FT4 (and an FT8!) QSO generally looks something like the following:
>
> CQ K1JT FN20
>   K1JT G0HDB IO82
> G0HDB K1JT -10
>   K1JT G0HDB R-08
> G0HDB K1JT RR73
>   K1JT G0HDB 73
>
> Currently, the logging window only pops open on my screen to prompt me to
> log the QSO when the final (Tx5) '73' message is being sent - this is to
> all extents and purposes superfluous because the QSO has been successfully
> completed when K1JT has sent his RR73 (and I've received it).  My sending
> the superfluous '73' message extends the overall duration of the QSO by
> adding a further Tx period at my end of the sequence so I can't move on to
> trying to start the next QSO.
>
> I'd like to suggest that the logging window is opened when I've *received*
> the other station's RR73 message and that sending the final Tx5 '73'
> message is either removed from the sequence altogether or is made
> optional.  This would help to improve the overall throughput of FT4 QSOs.
>
> The code to open the logging window on receipt of an incoming 'RR73'
> message and to desist from sending the Tx5 '73' message must already exist
> within the app because that's what already happens when I operate as a
> Hound in FT8 Fox & Hounds mode - when I receive the Fox's 'RR73' the
> logging window pops open and my system doesn't send the unnecessary Tx5
> '73' .
>
> I'd actually like to see the logging window open in any mode when I either
> send *or receive* an RRR or RR73 message - in my opinion that would align
> the prompting to log the QSO much more closely with the completion of the
> exchange of the essential information for the QSO and would leave the
> sending of a final '73' as an optional nicety.
>
> --
> 73, Martin G0HDB
>
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_3674534888006593587_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

[wsjt-devel] WSJT-X v2.3.1 Crash

[david]

This message appeared this morning:

Running: C:\Program Files\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e "C:\Program 
Files\wsjtx\bin" -a C:\Users\david\AppData\Local\WSJT-X -t 
C:\Users\david\AppData\Local\Temp\WSJT-X
At line 614 of file C:\Users\bill\src\k1jt\wsjtx\lib\decoder.f90 (unit = 13) 
Fortran runtime error: Cannot open file 'fort.13': Permission denied Error 
termination. Backtrace:
Could not print backtrace: libbacktrace could not find executable to open
#0  0x
#1  0x
#2  0x
#3  0x
#4  0x
#5  0x
#6  0x
#7  0x
#8  0x
#9  0x
#10  0x
#11  0x
#12  0x
#13  0x
#14  0x
#15  0x





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

[wsjt-devel] Q65_Sync only goes to 1kHz on Mac OS 10.14.6

[David Schmocker]

GE Gents:
WSJT-X v2.4.0 rc4, Mac OS 10.14.6.   Q65_Sync still only displays orange 
‘grass’  from 0 Hz up to 1000Hz (not full 3500Hz bandwidth of radio and 
display). 

Thank you for all you’re doing.  Very 73,

Dave KJ9I

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

Re: [wsjt-devel] Elecraft K3

[David Schmocker]

GM Mike:
I can test K3S if helpful.   Please provide the specific use-case/instructions 
for Mac OS 10.14.6 

If it’s any mode other than Q65 or JT-65, I’ll need the settings used also Very 
73

Dave KJ9I

 

Just a question:  Why select “Fake-It” with K3S?  I was advised to use “Rig” 
and it works well.  

 

From: Black Michael via wsjt-devel 
Reply-To: Black Michael , WSJT software development 

Date: Monday, March 22, 2021 at 2:25 PM
To: WSJT Software Development 
Cc: Black Michael 
Subject: [wsjt-devel] Elecraft K3

 

Anybody out there with an Elecraft K3 or K3S willing do some testing for hamlib?

 

I have a report that Fake It does not work correctly on the K3/K3S so would 
like to see some debug from other users to determine if this is a rig problem 
or an Elecraft problem.

 

The behavior in Fake It is that the VFO will start walking up or down if the 
transmit offset frequency is different.

Rig Split seems to work OK.

 

Mike W9MDB

 

 

___ 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] Q65_Sync truncates at 1,000Hz

[David Schmocker]

Joe:
OK thank you so much; I appreciate that. Very 73,
Dave

On 3/20/21, 1:45 PM, "Joe Taylor"  wrote:

Hi Dave,

On 3/20/2021 2:01 PM, David Schmocker KJ9I wrote:

> This seems maybe a bug?On my WSJT-X, the Q65_Sync only gets up to 
> 1,000 Hz.  Unable to attach screenshot (even compressed) due to 
> email reflector attachment size limits; could email to anyone directly 
> off-list..
> 
> Changing Bins/Pixel does not fix this (it stays capped at 1,000Hz).
> 
> This is on Mac OS 10.14.6 Mojave.  WSJT-X v2.4.0rc3  computer is Intel 
> 3GHz Intel Core i7,  16GB of 1600 MHz DDR3 RAM.  Graphics Intel Iris 
> 1536 MB  (Mac Mini).
> 
> I am running this from a mode-specific WSJT-X Config named Q65 EME K3S
> 
> Thank you for any help/ideas on how to resolve this.

We believe this problem has already been fixed in WSJT-X 2.4.0-rc4, 
which will be released soon.  Please upgrade to RC4 when it's made 
available, and report back if you still have a problem.

-- 73, Joe, K1JT


___
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] Q65_Sync truncates at 1,000Hz

[David Schmocker]

Hello, 

This seems maybe a bug?On my WSJT-X, the Q65_Sync only gets up to 1,000 Hz. 
 Unable to attach screenshot (even compressed) due to email reflector 
attachment size limits; could email to anyone directly off-list..   

Changing Bins/Pixel does not fix this (it stays capped at 1,000Hz). 

 

This is on Mac OS 10.14.6 Mojave.  WSJT-X v2.4.0rc3  computer is Intel 3GHz 
Intel Core i7,  16GB of 1600 MHz DDR3 RAM.  Graphics Intel Iris 1536 MB  (Mac 
Mini). 

I am running this from a mode-specific WSJT-X Config named Q65 EME K3S  

 

Thank you for any help/ideas on how to resolve this. 

 

Very 73,


Dave KJ9I

 

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

Re: [wsjt-devel] WSJT-X 2.4.0-rc3 Audio Issue

[David Birnbaum]

>
> I've been having the same issue - no transmit audio although TUNE does
> work.  Same setup except I'm connected to the IC7300 directly via USB.
>

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

Re: [wsjt-devel] Feature request: Rx level input slider

[David Schmocker]

Mike:
Thank you for settings cross-check (current settings):  Others have proposed 
reducing RF level (need to adjust AF level to preserve EME system noise figure)

 

K3S entryValuecomments
AF GAINLOreduces output level by about 10dB vs. HI setting
AF LIMNOR 030don’t want AGC limiting levels for optimal EME decoding
LIN OUT=PHONESNOR 000 gives 0dB while NOR 001 saturates WSJT-X at +78dB

 

With LIN OUT set to =PHONES, I can use the radio K3S AF control to somewhat 
control the audio out level via the USB port, but it’s super sensitive.  A 
10-Turn trimmer AF control would be required to set it properly. 

The audio output abruptly jumps from zero to too hot when using the radio’s AF 
(volume) control. 
Also I’ve checked the computer MIDI settings (already at minimum). 

 

I have searched for WSJT-X audio settings and K3S on internet 
(N5XLHamRadio.blogspot.com has one good post but it must have referenced an 
older WSJT-X version that had Rx input slider).   

 

I’ll keep researching settings and welcome an email off-list from anyone who 
finds alternate solution on this to kj9idave (at) charter ( d ot)  net    

 

Absent an Rx input level slider-control, I believe I just need to live 
with/accept the the 57dB level currently showing (no signals) on WSJT-X with 
Ref Spectrum measured viewing Cold Sky North.   

thank you 

 

Very 73, 
Dave KJ9I

 

From: Black Michael via wsjt-devel 
Reply-To: Black Michael , WSJT software development 

Date: Monday, March 15, 2021 at 12:01 AM
To: WSJT software development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Feature request: Rx level input slider

 

Have you tried this setting?  Seesms reducing this should work.

 

LIN OUT NOR 010 

Sets the LINE OUT level. LINE OUT connections go to PC soundcard inputs.

Settings above 10 may result in overdrive of the soundcard or saturation of the

KIO3’s isolation transformers; monitor signals using the PC to avoid this.

Note: Normally, LIN OUT sets a fixed-level receive-only output for main/sub

(L/R), compatible with digitalmodes. Tapping 1 switches LINOUT to

=PHONES, where the line outputs match headphone audio, audio level is

controlled by AF/SUB gain controls, and both RX andTX audio are available.

 

Mike W9MDB

 

 

 

On Sunday, March 14, 2021, 11:31:56 AM CDT, David Schmocker 
 wrote: 

 

 

Dear WSJT-X development team:
Feature request:

Could we eliminate the Tx Power slider (lower right of main screen) and replace 
it with an Rx input level slider (far lower left of screen immediately adjacent 
to the Rx dB level) to allow attenuation of input Rx signal please?

 

More detail/context:

Elecraft K3S radio with WSJT-X users who use the USB-to-K3S radio interface can 
only reduce the input volume so far (typically maintains 60dB WSJT-X level on 
the Rx dB level indicator).   Further reducing the audio output of the K3S 
drops the Signal to the point we see ‘jail bars’ (internal noise). 

To enable setting K3S output to WSJT-X recommended 30dB, the above Rx level 
slider would help.

Tx slider seems unnecessary because every radio (correct me if wrong) allows a 
Tx or drive level reduction on the radio itself). 

 

Very 73, 

Dave KJ9I

 

___
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 feature request: JT-65A (1270Hz) and Q65 (1500Hz) defaults

[David Schmocker]

Bill:
OK.. will do this (I already have a unique config for some modes).

Thank you!

73,

Dave

 

From: Bill Somerville 
Reply-To: WSJT software development 
Date: Sunday, March 14, 2021 at 11:37 AM
To: 
Subject: Re: [wsjt-devel] WSJT-X feature request: JT-65A (1270Hz) and Q65 
(1500Hz) defaults

 

On 14/03/2021 16:30, David Schmocker wrote:

Dear WSJT development team:
Would it be possible (easy) to establish default Tx and Rx frequencies per 
mode: 

 

JT-65A (Tx 1270 Hz and Rx 1270Hz) any time JT-65 mode is selected and 

 

Q65 (Tx 1,500 Hz and Rx 1500 Hz)?  

 

I realize these can be manually changed (what I do currently), but when I am 
coaching a new user in another country who has limited time also, having the 
mode-specific frequency defaults would be one less problem to overcome across 
language barriers and time constraints. 

 

Just a friendly suggestion.. thank you..

 

Very 73,


Dave KJ9I

Hi Dave,

both of those modes have multi-signal decoders in WSJT-X and are likely to be 
used when more than one signal is in the rig's passband. Given that default 
audio offsets do not have much meaning. I would recommend setting up separate 
configurations for each mode used, that will recall the last used Tx and Rx 
offsets when switching to each configuration.

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] Feature request: Rx level input slider

[David Tiller]

You wrote:

“Tx slider seems unnecessary because every radio (correct me if wrong) allows a 
Tx or drive level reduction on the radio itself).”

That is very much not the case. Many rigs require a different drive level per 
band, something that WSJTX handles perfectly.


> On Mar 14, 2021, at 12:25, David Schmocker  wrote:
> 
> Tx slider seems unnecessary because every radio (correct me if wrong) allows 
> a Tx or drive level reduction on the radio itself).



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

[wsjt-devel] WSJT-X feature request: JT-65A (1270Hz) and Q65 (1500Hz) defaults

[David Schmocker]

Dear WSJT development team:
Would it be possible (easy) to establish default Tx and Rx frequencies per 
mode: 

 

JT-65A (Tx 1270 Hz and Rx 1270Hz) any time JT-65 mode is selected and 

 

Q65 (Tx 1,500 Hz and Rx 1500 Hz)?  

 

I realize these can be manually changed (what I do currently), but when I am 
coaching a new user in another country who has limited time also, having the 
mode-specific frequency defaults would be one less problem to overcome across 
language barriers and time constraints. 

 

Just a friendly suggestion.. thank you..

 

Very 73,


Dave KJ9I

 

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

[wsjt-devel] Feature request: Rx level input slider

[David Schmocker]

Dear WSJT-X development team:
Feature request:

Could we eliminate the Tx Power slider (lower right of main screen) and replace 
it with an Rx input level slider (far lower left of screen immediately adjacent 
to the Rx dB level) to allow attenuation of input Rx signal please?

 

More detail/context:

Elecraft K3S radio with WSJT-X users who use the USB-to-K3S radio interface can 
only reduce the input volume so far (typically maintains 60dB WSJT-X level on 
the Rx dB level indicator).   Further reducing the audio output of the K3S 
drops the Signal to the point we see ‘jail bars’ (internal noise). 

To enable setting K3S output to WSJT-X recommended 30dB, the above Rx level 
slider would help.

Tx slider seems unnecessary because every radio (correct me if wrong) allows a 
Tx or drive level reduction on the radio itself). 

 

Very 73, 

Dave KJ9I

 

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

Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync

[David Kaplan via wsjt-devel]

The ~ is actually a shortcut for /Macintosh HD/Users/Username were Username is 
the name of your home folder.

You can try /Macintosh HD/Users/Username/Library/Preferences directly.

Does that help?

David, WA1OUI


On Mar 6, 2021, at 11:21 AM, John Stengrevics  wrote:

Hi Dave,

I followed your instructions, but ~/Library/Preferences/ is not there.  Neither 
is there a folder for WSJT.  And if I search “Library” for 
~/Library/Preferences/, nothing comes up.

John
WA1EAZ



> On Mar 6, 2021, at 11:10 AM, David Schmocker  <mailto:kj9id...@charter.net>> wrote:
> 
> Hi John:
> In order to show that folder,  
>  
> Open Mac finder
> Hold down the “Alt (Option)” key (lower left of keyboard).
> Navigate with mouse to the Go pull-down menu
> Select (left-click) library from that list.. 
> Think now you can see those previously hidden files.   ?  
>  
> 73
> Dave KJ9I
>  
> From: John Stengrevics  <mailto:jstengrev...@comcast.net>>
> Reply-To: WSJT software development  <mailto:wsjt-devel@lists.sourceforge.net>>
> Date: Saturday, March 6, 2021 at 10:05 AM
> To: Steven Franke mailto:s.j.fra...@icloud.com>>
> Cc: WSJT software development  <mailto:wsjt-devel@lists.sourceforge.net>>
> Subject: Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync
>  
> Steve,
>  
> I understand, but I can’t find the ~/Library/Preferences/ folder.  If I 
> search my Mac for it, nothing comes up but “WSJT User Guide.”  I don’t see it 
> anywhere.
>  
> Sorry to be so clueless here.
>  
> John
> WA1EAZ
> 
> 
>> On Mar 6, 2021, at 10:54 AM, Steven Franke > <mailto:s.j.fra...@icloud.com>> wrote:
>>  
>> John, 
>>  
>> The file that Bill sent to you should be placed in the ~/Library/Preferences 
>> folder. This is the folder that your existing WSJT-X.ini file is located in. 
>> You should be able to open the ~/Library/Preferences folder and simply grab 
>> the attachment that Bill sent and drag it into that folder. When you are 
>> done you should see both WSJT-X.ini and wsjtx_log_config.ini next to (or 
>> near) each other in the list of files in that folder.
>>  
>> ut User Guide.73 Steve k9an
>> 
>> 
>>> On Mar 6, 2021, at 9:43 AM, John Stengrevics >> <mailto:jstengrev...@comcast.net>> wrote:
>>>  
>>> Hi Steve,
>>>  
>>> Thanks for that.  
>>>  
>>> I have followed your suggestions.  However, I don’t see 
>>> ~/Library/Preferences/ under WSJT.  (Bill had asked me to move a file that 
>>> he sent (wsjt_log_config.ini) there for debugging purposes.)  Maybe move it 
>>> to WSJT INI?
>>>  
>>> 73,
>>>  
>>> John
>>> WA1EAZ
>>> 
>>> 
>>>> On Mar 6, 2021, at 10:27 AM, Steven Franke via wsjt-devel 
>>>> >>> <mailto:wsjt-devel@lists.sourceforge.net>> wrote:
>>>>  
>>>> John, 
>>>> You can make the ~/Library folder visible in Finder with the following 
>>>> steps:
>>>>  
>>>> 1. Open a Finder window.
>>>> 2. Select your home directory in the left panel of the Finder window.
>>>> 3. Select Show View Options under the “View” menu.
>>>> 4. Check the “Show Library Folder” box.
>>>>  
>>>> Thereafter, your Library folder will always be visible.
>>>>  
>>>> 73 Steve k9an
>>>> 
>>>> 
>>>>> On Mar 6, 2021, at 8:36 AM, John Stengrevics >>>> <mailto:jstengrev...@comcast.net>> wrote:
>>>>>  
>>>>> Hi Bill,
>>>>>  
>>>>> I can’t find the ~/Library/Preferences/ directory in which to put the 
>>>>> file.  Can you provide a bit more detail on how I can locate it?  Sorry.
>>>>>  
>>>>> John
>>>>> WA1EAZ
>>>>> 
>>>>> 
>>>>>> On Mar 6, 2021, at 9:20 AM, Bill Somerville >>>>> <mailto:g4...@classdesign.com>> wrote:
>>>>>>  
>>>>>> Hi John,
>>>>>>  
>>>>>> so I can see what is happening put the attached file into the WSJT-X 
>>>>>> configuration files directory (~/Library/Preferences/ on macOS), restart 
>>>>>> WSJT-X, run a minimal test to demonstrate the issue, then quit WSJT-X 
>>>>>> (do not turn off the rig until WSJT-X has exited). There will be a new 
>>>>>> file on your Desktop called WSJT-X_RigControl.log, send me that file for 
>>>>>> analy

Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync

[David Schmocker]

John:
Please send your telephone number to me at kj9idave. (at).  Charter. [dot]. 
Net.  . Let’s try a phone call. 

Very 73,
Dave

 

From: John Stengrevics 
Reply-To: WSJT software development 
Date: Saturday, March 6, 2021 at 10:24 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync

 

Hi Dave,

 

I followed your instructions, but ~/Library/Preferences/ is not there.  Neither 
is there a folder for WSJT.  And if I search “Library” for 
~/Library/Preferences/, nothing comes up.

 

John

WA1EAZ

 

 



On Mar 6, 2021, at 11:10 AM, David Schmocker  wrote:

 

Hi John:
In order to show that folder,  

 

Open Mac finder

Hold down the “Alt (Option)” key (lower left of keyboard).

Navigate with mouse to the Go pull-down menu

Select (left-click) library from that list.. 

Think now you can see those previously hidden files.   ?  

 

73
Dave KJ9I

 

From: John Stengrevics 
Reply-To: WSJT software development 
Date: Saturday, March 6, 2021 at 10:05 AM
To: Steven Franke 
Cc: WSJT software development 
Subject: Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync

 

Steve,

 

I understand, but I can’t find the ~/Library/Preferences/ folder.  If I search 
my Mac for it, nothing comes up but “WSJT User Guide.”  I don’t see it anywhere.

 

Sorry to be so clueless here.

 

John

WA1EAZ




On Mar 6, 2021, at 10:54 AM, Steven Franke  wrote:

 

John, 

 

The file that Bill sent to you should be placed in the ~/Library/Preferences 
folder. This is the folder that your existing WSJT-X.ini file is located in. 
You should be able to open the ~/Library/Preferences folder and simply grab the 
attachment that Bill sent and drag it into that folder. When you are done you 
should see both WSJT-X.ini and wsjtx_log_config.ini next to (or near) each 
other in the list of files in that folder.

 

ut User Guide.73 Steve k9an




On Mar 6, 2021, at 9:43 AM, John Stengrevics  wrote:

 

Hi Steve,

 

Thanks for that.  

 

I have followed your suggestions.  However, I don’t see ~/Library/Preferences/ 
under WSJT.  (Bill had asked me to move a file that he sent 
(wsjt_log_config.ini) there for debugging purposes.)  Maybe move it to WSJT INI?

 

73,

 

John

WA1EAZ




On Mar 6, 2021, at 10:27 AM, Steven Franke via wsjt-devel 
 wrote:

 

John, 

You can make the ~/Library folder visible in Finder with the following steps:

 

1. Open a Finder window.

2. Select your home directory in the left panel of the Finder window.

3. Select Show View Options under the “View” menu.

4. Check the “Show Library Folder” box.

 

Thereafter, your Library folder will always be visible.

 

73 Steve k9an




On Mar 6, 2021, at 8:36 AM, John Stengrevics  wrote:

 

Hi Bill,

 

I can’t find the ~/Library/Preferences/ directory in which to put the file.  
Can you provide a bit more detail on how I can locate it?  Sorry.

 

John

WA1EAZ




On Mar 6, 2021, at 9:20 AM, Bill Somerville  wrote:

 

Hi John,

 

so I can see what is happening put the attached file into the WSJT-X 
configuration files directory (~/Library/Preferences/ on macOS), restart 
WSJT-X, run a minimal test to demonstrate the issue, then quit WSJT-X (do not 
turn off the rig until WSJT-X has exited). There will be a new file on your 
Desktop called WSJT-X_RigControl.log, send me that file for analysis please 
(g4wjs  classdesign  com)?

 

Once you have sent me the log file delete the wsjtx_log_config.ini and 
WSJT-X_RigControl.log files to resume normal operation.

 

73
Bill
G4WJS.

 

On 06/03/2021 14:13, John Stengrevics wrote:

Bill, 

 

I have CAT selected and it does connect when I click on Test.

 

John (G4KLA) had asked what driver I was using.  I replied that the driver had 
not changed.  It has always been  /dev/cu.usbserial-A503XYAO.

 

John

WA1EAZ




On Mar 6, 2021, at 9:07 AM, Bill Somerville  wrote:

 

Hi John,

 

which option do you have checked for "Preferences->Radio->PTT Method"?

 

73
Bill
G4WJS.

 

On 06/03/2021 14:03, John Stengrevics wrote:

Hi Bill, 

 

I just tried to use Q65 with “Cumulative" selected as you suggested.  However, 
the problem is still there as described below.  I have to shut down my 
transceiver (Elecraft K3S) to get it to stop transmitting.

 

Thanks,

 

John

WA1EAZ




On Mar 6, 2021, at 8:44 AM, Bill Somerville  wrote:

 

Hi John,

 

I am not sure as I have not investigated this issue yet. It is easy enough to 
check, select "Cumulative" for the 2D spectrum display, restart WSJT-X, and see 
if the iusse goes away.

 

73
Bill
G4WJS.

 

On 06/03/2021 13:25, John Stengrevics wrote:

Hi Bill, 

 

Will this fix solve the problem I reported yesterday with OS Big Sur?  I’ll 
repost below in case you didn’t see it.

 

Thanks,

 

John

WA1EAZ

 

Repost - some additions in red:  

 

John & Joe,

I had been using the previous version successfully on a MacBook Pro (Intel not 
M1) OS Big Sur 11.2.2.

Today, I downlo

[wsjt-devel] "PTT hangs" on Mac OS 10.14.6

[David Schmocker]

Everyone
I just tested mode JT65 and the “PTT hang” issue (new to 2.4.0rc2) affects JT65 
also.  


My test data shows this issue is not Q65-specific. 

 

Very 73, if there’s testing helpful to isolate root cause, I volunteer. 

 

Dave KJ9I

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

Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync

[David Schmocker]

On Mar 6, 2021, at 5:55 AM, Bill Somerville  wrote:

 

Hi Dave and Kevin,

we have finally tracked down the cause of this crash, thanks for your patience 
it was not so easy to track down. It is repaired for the next release, for now 
if you do not use of the Q65_Sync Wide Graph synchronization plot the crash 
will be avoided. Note this is not a Mac specific issue although it does seem to 
have the most severe effects on that platform.

73
Bill
G4WJS.

On 06/03/2021 03:59, David Schmocker wrote:


Hello all,

A second report that mirrors this one:WSJT-X 2.4.0rc2

OS 10.14.6,  Mac Mini

Mode Q65,Waterfall Q65_ Sync selected and slow to let go of PTT line to K3S 
radio (even after Tx period).   (when I go into Radio Panel, the Test PTT Red 
bar stays on, won't easily release).

Then when a decode should take place, I get a crash exactly as Kevin reported 
with the same exact message as reported below.

Thank you,   73,

Dave KJ9I



On 3/5/21, 8:47 PM, "Kevin McQuiggin"  wrote:

Hi All:
I tried submitting this earlier today, but it didn’t seem to make to the 
list.  Hence, a re-submission:

Just trying out RC2 on an iMac, MacOS version 10.14.6 Mojave.

Selection of “Q65_Sync” from dropdown box on the wide graph causes a crash 
as soon as the application starts to TX.  Selection of “Cumulative” (the 
default) and TX/RX are normal.

Specific exception was "EXC_BAD_ACCESS (SIGSEGV)”.

I have saved the crash dump and can provide as necessary.

73,

Kevin VE7ZD

 

___
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 

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

Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync

[David Tiller]

John,

~/Library is usually a hidden directory in the finder. I made a symlink to it 
called 'libr' that I use to get to it via the finder. You can see the Library 
directory in terminal, so if you want to cp the file from a terminal session, 
you can.

To create a symbolic link, in terminal type:

ln -s Library libr

Once created, you can see libr in finder and click into it.

73 de K4DET

> On Mar 6, 2021, at 9:36 AM, John Stengrevics  wrote:
> 
> Hi Bill,
> 
> I can’t find the ~/Library/Preferences/ directory in which to put the file.  
> Can you provide a bit more detail on how I can locate it?  Sorry.
> 
> John
> WA1EAZ
> 
>> On Mar 6, 2021, at 9:20 AM, Bill Somerville > <mailto:g4...@classdesign.com>> wrote:
>> 
>> Hi John,
>> 
>> so I can see what is happening put the attached file into the WSJT-X 
>> configuration files directory (~/Library/Preferences/ on macOS), restart 
>> WSJT-X, run a minimal test to demonstrate the issue, then quit WSJT-X (do 
>> not turn off the rig until WSJT-X has exited). There will be a new file on 
>> your Desktop called WSJT-X_RigControl.log, send me that file for analysis 
>> please (g4wjs  classdesign  com)?
>> 
>> Once you have sent me the log file delete the wsjtx_log_config.ini and 
>> WSJT-X_RigControl.log files to resume normal operation.
>> 
>> 73
>> Bill
>> G4WJS.
>> 
>> On 06/03/2021 14:13, John Stengrevics wrote:
>>> Bill,
>>> 
>>> I have CAT selected and it does connect when I click on Test.
>>> 
>>> John (G4KLA) had asked what driver I was using.  I replied that the driver 
>>> had not changed.  It has always been  /dev/cu.usbserial-A503XYAO.
>>> 
>>> John
>>> WA1EAZ
>>> 
>>>> On Mar 6, 2021, at 9:07 AM, Bill Somerville >>> <mailto:g4...@classdesign.com>> wrote:
>>>> 
>>>> Hi John,
>>>> 
>>>> which option do you have checked for "Preferences->Radio->PTT Method"?
>>>> 
>>>> 73
>>>> Bill
>>>> G4WJS.
>>>> 
>>>> On 06/03/2021 14:03, John Stengrevics wrote:
>>>>> Hi Bill,
>>>>> 
>>>>> I just tried to use Q65 with “Cumulative" selected as you suggested.  
>>>>> However, the problem is still there as described below.  I have to shut 
>>>>> down my transceiver (Elecraft K3S) to get it to stop transmitting.
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> John
>>>>> WA1EAZ
>>>>> 
>>>>>> On Mar 6, 2021, at 8:44 AM, Bill Somerville >>>>> <mailto:g4...@classdesign.com>> wrote:
>>>>>> 
>>>>>> Hi John,
>>>>>> 
>>>>>> I am not sure as I have not investigated this issue yet. It is easy 
>>>>>> enough to check, select "Cumulative" for the 2D spectrum display, 
>>>>>> restart WSJT-X, and see if the iusse goes away.
>>>>>> 
>>>>>> 73
>>>>>> Bill
>>>>>> G4WJS.
>>>>>> 
>>>>>> On 06/03/2021 13:25, John Stengrevics wrote:
>>>>>>> Hi Bill,
>>>>>>> 
>>>>>>> Will this fix solve the problem I reported yesterday with OS Big Sur?  
>>>>>>> I’ll repost below in case you didn’t see it.
>>>>>>> 
>>>>>>> Thanks,
>>>>>>> 
>>>>>>> John
>>>>>>> WA1EAZ
>>>>>>> 
>>>>>>> Repost - some additions in red:  
>>>>>>> 
>>>>>>> John & Joe,
>>>>>>> 
>>>>>>> I had been using the previous version successfully on a MacBook Pro 
>>>>>>> (Intel not M1) OS Big Sur 11.2.2.
>>>>>>> 
>>>>>>> Today, I downloaded Mac version 2.4.0-rc2.  
>>>>>>> 
>>>>>>> When running Q65, T/R = 30 seconds, Submode A, the program continues to 
>>>>>>> transmit after the 30 second period is complete for 60 seconds total.  
>>>>>>> However, it does not seem to drive my amplifier after 30 seconds. [PTT 
>>>>>>> is activated for the second 30 seconds, but no audio to drive the amp.] 
>>>>>>>  I have since tried FT8 on WSJT-X and can confirm that it works as 
>>>>>>> usual.  Thus, the p

Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync

[David Schmocker]

Good morning everyone 

OS 10.14.6 here (Intel )..  I saw in 2.4.0rc2 installation instructions we must 
uninstall then reinstall the drivers to the radio.
For my application, this is the USB-CODEC inside the K3S radio.. I am currently 
trying to figure out how to uninstall then reinstall this driver Hoping it 
fixes the (hang-on PTT) issue I also have

 

73,
Dave

 

From: John Stengrevics 
Reply-To: WSJT software development 
Date: Saturday, March 6, 2021 at 8:15 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync

 

Bill,

 

I have CAT selected and it does connect when I click on Test.

 

John (G4KLA) had asked what driver I was using.  I replied that the driver had 
not changed.  It has always been  /dev/cu.usbserial-A503XYAO.

 

John

WA1EAZ



On Mar 6, 2021, at 9:07 AM, Bill Somerville  wrote:

 

Hi John,

 

which option do you have checked for "Preferences->Radio->PTT Method"?

 

73
Bill
G4WJS.

 

On 06/03/2021 14:03, John Stengrevics wrote:

Hi Bill, 

 

I just tried to use Q65 with “Cumulative" selected as you suggested.  However, 
the problem is still there as described below.  I have to shut down my 
transceiver (Elecraft K3S) to get it to stop transmitting.

 

Thanks,

 

John

WA1EAZ



On Mar 6, 2021, at 8:44 AM, Bill Somerville  wrote:

 

Hi John,

 

I am not sure as I have not investigated this issue yet. It is easy enough to 
check, select "Cumulative" for the 2D spectrum display, restart WSJT-X, and see 
if the iusse goes away.

 

73
Bill
G4WJS.

 

On 06/03/2021 13:25, John Stengrevics wrote:

Hi Bill, 

 

Will this fix solve the problem I reported yesterday with OS Big Sur?  I’ll 
repost below in case you didn’t see it.

 

Thanks,

 

John

WA1EAZ

 

Repost - some additions in red:  

 

John & Joe,

I had been using the previous version successfully on a MacBook Pro (Intel not 
M1) OS Big Sur 11.2.2.

Today, I downloaded Mac version 2.4.0-rc2.  

When running Q65, T/R = 30 seconds, Submode A, the program continues to 
transmit after the 30 second period is complete for 60 seconds total.  However, 
it does not seem to drive my amplifier after 30 seconds. [PTT is activated for 
the second 30 seconds, but no audio to drive the amp.]  I have since tried FT8 
on WSJT-X and can confirm that it works as usual.  Thus, the problem seems to 
be isolated to Q65.

I did follow the instructions in the Readme file.  

If there is a file I can send you, please let me know.

I would appreciate any suggestions you can provide.

Best 73,

John
WA1EAZ



On Mar 6, 2021, at 5:55 AM, Bill Somerville  wrote:

 

Hi Dave and Kevin,

we have finally tracked down the cause of this crash, thanks for your patience 
it was not so easy to track down. It is repaired for the next release, for now 
if you do not use of the Q65_Sync Wide Graph synchronization plot the crash 
will be avoided. Note this is not a Mac specific issue although it does seem to 
have the most severe effects on that platform.

73
Bill
G4WJS.

On 06/03/2021 03:59, David Schmocker wrote:


Hello all,

A second report that mirrors this one:WSJT-X 2.4.0rc2

OS 10.14.6,  Mac Mini

Mode Q65,Waterfall Q65_ Sync selected and slow to let go of PTT line to K3S 
radio (even after Tx period).   (when I go into Radio Panel, the Test PTT Red 
bar stays on, won't easily release).

Then when a decode should take place, I get a crash exactly as Kevin reported 
with the same exact message as reported below.

Thank you,   73,

Dave KJ9I



On 3/5/21, 8:47 PM, "Kevin McQuiggin"  wrote:

Hi All:
I tried submitting this earlier today, but it didn’t seem to make to the 
list.  Hence, a re-submission:

Just trying out RC2 on an iMac, MacOS version 10.14.6 Mojave.

Selection of “Q65_Sync” from dropdown box on the wide graph causes a crash 
as soon as the application starts to TX.  Selection of “Cumulative” (the 
default) and TX/RX are normal.

Specific exception was "EXC_BAD_ACCESS (SIGSEGV)”.

I have saved the crash dump and can provide as necessary.

73,

Kevin VE7ZD

 

___
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] RC2 Report on MacOS 10.14.6 Mojave - Q65_Sync

[David Schmocker]

Hello all, 

A second report that mirrors this one:WSJT-X 2.4.0rc2

OS 10.14.6,  Mac Mini

Mode Q65,Waterfall Q65_ Sync selected and slow to let go of PTT line to K3S 
radio (even after Tx period).   (when I go into Radio Panel, the Test PTT Red 
bar stays on, won't easily release). 

Then when a decode should take place, I get a crash exactly as Kevin reported 
with the same exact message as reported below. 

Thank you,   73, 

Dave KJ9I



On 3/5/21, 8:47 PM, "Kevin McQuiggin"  wrote:

Hi All:
I tried submitting this earlier today, but it didn’t seem to make to the 
list.  Hence, a re-submission:

Just trying out RC2 on an iMac, MacOS version 10.14.6 Mojave.

Selection of “Q65_Sync” from dropdown box on the wide graph causes a crash 
as soon as the application starts to TX.  Selection of “Cumulative” (the 
default) and TX/RX are normal.

Specific exception was "EXC_BAD_ACCESS (SIGSEGV)”.

I have saved the crash dump and can provide as necessary.

73,

Kevin VE7ZD



___
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] Icom 7300 Split weirdness with 2.3.0 Oc42df

[David Garnier]

 Hello,

I solved my problem, by going into the Split Operation box and uncheck Rig to 
None.

Test setup as follows: WSJTX configured for operation with 7300,
no other crap software in between, nothing. The barest of configuration.

Note. I swear the prior release didn't have this problem but I can't test 
that theory because that s/w release has been deactivated. Drat.

Don't get me wrong guys I'm still a happy customer and I appreciate all
the software work that has gone into WSJTx.

73's - Dave - wb9own


 On Thursday, February 18, 2021, 11:43:24 PM CST, David Garnier 
 wrote:  
 
 Hello,

To operate 630m on IC-7300 I use an 80m-630m transmit converter,
this has worked flawlessly until recently.

I'm not sure how to describe this but Ham Lib appears to be recalling
from memory a "past split frequency setting" of the radio and now I 
can't clear it.  How do I clear this "memory setting?"

If I push the split button on 7300 the green indicates "S" so that piece
is still functional.

Thanks,

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

Re: [wsjt-devel] clock offset / fudge adjustment, automatic/manual

[David Smith]

"The only way around that..." --> I'd disagree.
"If you are that far off .." --> It's software. When there's will, there's
a way.
"internt time" --> Problem statement/use case is portable use without
internet access.

On Thu, Mar 4, 2021 at 8:17 AM Sam W2JDB via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> David,
>
> If you are that far off the internet time, how would the instance of
> WSJT-X running
> on your PC be able to even decode the incoming messages and letting you
> know
> how far of you are.
>
> The whole point of syncing to internet time (FT8, FT4) is that it needs
> the timing
> to decode said messages.
>
> The only way around that is to include a sync signals within the message
> itself which
> change the contents of the message itself.
>
> 73,
>
> Sam W2JDB
>
>
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] clock offset / fudge adjustment, automatic/manual

[David Smith]

again, clarifying the use case: Portable use, no internet.

On Thu, Mar 4, 2021 at 8:56 AM Derek Turner via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> I find this interesting because a while ago I suggested something similar
> where the system clock could be adjusted in order to synchronise with and
> work rare DX stations whose clocks were significantly erroneous. I started
> experimenting but lost interest when the particular problem I was having
> with an African station just went away.
>
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] clock offset / fudge adjustment, automatic/manual

[David Smith]

To clarify my use case and some reasoning:

1) Since WSJT is highly dependent on clock accuracy, there should be a way
to either manually or automatically sync the clock to received stations.
2) I'm not suggesting at all that WSJT modify the system clock. In fact, my
suggestion is that WSJT leave the system clock alone, and that we add a
feature that allows offset to the system clock.
3) Using other devices or software to do this for you adds complexity that
isn't necessary; ntpd, chrony, GPS, all of these add new dependencies and
fiddles/adjustments that make using WSJT more complicated to use.
4) Really the main problem to solve here is portable operation.  Adding
more software, or more hardware, to solve this problem uses more power and
reduces battery life.
5) potentially, allowing an automatic offset adjustment within the software
itself to average the clocks of received stations has the potential to
completely eliminate the need for "accurate clocks" across the board. Of
course, this is assuming everyone using FT8 (as an example) was using WSJT
or software capable of this automatic adjustment.  If I'm not mistaken
(which is entirely possible) clocks could be off by minutes, hours, days,
etc, as long as the second hand lines up with received stations.

On Thu, Mar 4, 2021 at 4:02 AM 
wrote:

>
> Date: Thu, 04 Mar 2021 10:43:36 +
> From: Alan 
> To: WSJT software development 
> Subject: Re: [wsjt-devel] clock offset / fudge adjustment,
> automatic/manual
> Message-ID:
> <
> 177fcd5f3c0.27f6.308160ffa91046202f89ff6226309...@alangroups.plus.com>
>
> Content-Type: text/plain; charset="us-ascii"; Format="flowed"
>
> In my experience portable operation does indeed have a problem with
> drifting clocks due to temperature variations, and particularly wind.
>
> Internet connectivity may well be unavailable, so I've bought a cheap GPS
> dongle that does the job just fine.
>
>
> I'm not sure a fixed clock adjustment will deal with it though, because
> I've found the drift on my laptop to be rather dynamic and it could soon
> get out of step.  I agree changing the system clock would be unwise.
>
>
> Averaging received time differentials to provide a correction is an
> interesting thought though, but in my view providing that was done only
> inside WSJT-X and only for the current session - no changes to the system
> clock itself, or permanent config changes.
>
>
> Alan G0TLK
> On 4 March 2021 07:31:47 Claude Frantz 
> wrote:
>
> > On 3/4/21 1:53 AM, David Smith wrote:
> >
> >> Proposal:
> >> Add an adjustment that allows you to manually adjust an offset to the
> >> system clock.  Being able to simply enter +/- seconds at the 100ths of a
> >> second would be helpful, ie: "-2.3s" or "+0.9s"
> >
> > Hi David and all,
> >
> > If you use ntpd or chrony, you have the ability to insert this data in
> > the appropriate config of these pieces of software.
> >
> > This has no place in the software using the time services.
> >
> > Best wishes,
> > Claude (DJ0OT)
> >
>
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] clock offset / fudge adjustment, automatic/manual

[David Smith]

Hi,

Two tiered request, I think the first should be relatively easy:

Use case:
For portable stations it would be really great to not have to sync your
clock super accurately. I know there's already tolerance in WSJT, but it
couldn't hurt to be able to more closely control this within the software
itself.

Proposal:
Add an adjustment that allows you to manually adjust an offset to the
system clock.  Being able to simply enter +/- seconds at the 100ths of a
second would be helpful, ie: "-2.3s" or "+0.9s"

This would allow most users to sync to the received stations and not have
to deal with an external clock sync source.  One can argue you can do this
with the system clock, however in my case I have Windows 10 running WSJT in
a VM on a MAC (for reasons, I know, dont say just use the software on the
mac itself) but it will constantly overwrite the VM clock.


Second proposal:
Based on received signals, have a checkbox in addition to the above
control, to automatically adjust the software clock offset to the system
clock.  I'm going to oversimplify the implementation, but again, based on
the average received stations clock offset from your system clock,
automatically adjust the offset to match the received stations.


Thanks!
David
AF6HO
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Possibly another clue (terminal window text leading up to Segmentation fault: 11)

[David Schmocker]

George:
Thank you; Sometimes (after only step 1) it runs fine for a while.   But I have 
let it in “monitor” mode and it sometimes keeps running. 

However to use the program requires changing settings (the Decode pull-down 
menu defaults arrive unoptimized) and so it’s not as simple as start it and let 
it run. 

Also in order to get maximum sensitivity (I am an EME user), this requires 
adding the callsign of Target station into “To Radio” field.  Sometimes these 
above routine operational actions result in crash. 

 

Dave

 

From: George J Molnar 
Reply-To: WSJT software development 
Date: Sunday, February 28, 2021 at 10:35 AM
To: WSJT software development 
Cc: John Nelson 
Subject: Re: [wsjt-devel] Possibly another clue (terminal window text leading 
up to Segmentation fault: 11)

 

What happens when you take step #1 only, then press enter? That should launch 
the app just fine. 

 

I built an Automator action to do just that, and haven’t had a single issue.

 

 

George J Molnar, KF2T
College Park, Maryland, USA






On Feb 28, 2021, at 9:38 AM, David Schmocker  wrote:

 

Everyone:
Thank you so much for the help here. 

 

Here’s (1st time) some text leading up to the fatal “Segmentation fault: 11” in 
terminal window.  

 

This Segmentation fault: 11   displays in terminal window every time WSJT-X 
crashes. 

 

Last login: Sun Feb 28 06:41:47 on ttys000

Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx

objc[935]: Class FIFinderSyncExtensionHost is implemented in both 
/System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit 
(0x7fffac6a13f0) and 
/System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride
 (0x12e7d7f50). One of the two will be used. Which one is undefined.

Segmentation fault: 11

Davids-Mac-mini:~ davidschmocker$ 

 

 

Sequence of events leading up to this:
Launched WSJT-X using terminal window: 
/Applications/wsjtx.app/Contents/MacOS/wsjtx
navigating to pull-down menu: File-Open which delivered dialog box #1:
2a) 

2b) I pressed “OK” and then got dialog box #2

3a) 

3b) I pressed “OK” and then I was routed to the directory path containing log 
files, etc.

 

 
Finally, in the terminal window I noticed this text (same as above)
 

Last login: Sun Feb 28 06:41:47 on ttys000

Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx

objc[935]: Class FIFinderSyncExtensionHost is implemented in both 
/System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit 
(0x7fffac6a13f0) and 
/System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride
 (0x12e7d7f50). One of the two will be used. Which one is undefined.

Segmentation fault: 11

Davids-Mac-mini:~ davidschmocker$ 

 

___
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] Possibly another clue (terminal window text leading up to Segmentation fault: 11)

[David Schmocker]

Everyone:
Thank you so much for the help here. 

 

Here’s (1st time) some text leading up to the fatal “Segmentation fault: 11” in 
terminal window.  

 

This Segmentation fault: 11   displays in terminal window every time WSJT-X 
crashes. 

 

Last login: Sun Feb 28 06:41:47 on ttys000

Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx

objc[935]: Class FIFinderSyncExtensionHost is implemented in both 
/System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit 
(0x7fffac6a13f0) and 
/System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride
 (0x12e7d7f50). One of the two will be used. Which one is undefined.

Segmentation fault: 11

Davids-Mac-mini:~ davidschmocker$ 

 

 

Sequence of events leading up to this:
Launched WSJT-X using terminal window: 
/Applications/wsjtx.app/Contents/MacOS/wsjtx
navigating to pull-down menu: File-Open which delivered dialog box #1:
2a) 

2b) I pressed “OK” and then got dialog box #2

3a) 

3b) I pressed “OK” and then I was routed to the directory path containing log 
files, etc.

 

 
Finally, in the terminal window I noticed this text (same as above)
 

Last login: Sun Feb 28 06:41:47 on ttys000

Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx

objc[935]: Class FIFinderSyncExtensionHost is implemented in both 
/System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit 
(0x7fffac6a13f0) and 
/System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride
 (0x12e7d7f50). One of the two will be used. Which one is undefined.

Segmentation fault: 11

Davids-Mac-mini:~ davidschmocker$ 

 

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

[wsjt-devel] Possible clues to OS 10.14.6. crash?

[David Schmocker]

When trying to retrieve Log File,  I first opened WSJT-X using Terminal window. 
 /Applications/wsjtx.app/Contents/MacOS/wsjtx

 

Next I did File-Open from pulldown menu.. this succeeds but yields some 
interesting interim messages (maybe clues to why I am crashing often)? 

 

 

Then this in the terminal window which was used to launch WSJT-X. 

 

Last login: Sun Feb 28 06:41:47 on ttys000

Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx

objc[935]: Class FIFinderSyncExtensionHost is implemented in both 
/System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit 
(0x7fffac6a13f0) and 
/System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride
 (0x12e7d7f50). One of the two will be used. Which one is undefined.

 

 

Hoping maybe somewhere in here is something useful? 

 

Very 73, thank you for all of your work and help.

 

Dave KJ9I

 

 

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

Re: [wsjt-devel] Crash during QSO

[David Schmocker]

Hi Neil 
Sure.. 

What do you prefer Word.doc or .txt file or ?? 

 

From: Neil Zampella 
Reply-To: WSJT software development 
Date: Sunday, February 28, 2021 at 7:41 AM
To: 
Subject: Re: [wsjt-devel] Crash during QSO

 

David,

is it possible to send this as an attachment, rather than a 'cut and paste' 
into an email?

Thanks,

Neil, KN3ILZ

On 2/28/2021 7:23 AM, David Schmocker wrote:

Sending JA7QVI KJ9I R-24. 

 

Awaiting RRRSH message (crash at start of Tx minute).. 

___ 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] What is path of Refspec.dat on Mac OS 10.14.6 please?

[David Schmocker]

Everyone:
Where is the Refspec.dat stored on Mac OS Mojave please ? 

Please advise:  thank you !

Very 73,

Dave KJ9I






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

Re: [wsjt-devel] WSJT-X v2.4.0rc1 crashes on OS 10.14.6

[David Schmocker]

John:
Great; thank you: 
Today the action that caused crash was (in Q65-60A mode),  EME Configuration,   
 changed radio freq. from 50.188 to 50.190 with radio connected to computer 
(WSJT-X Unexpected close details attached).  Please advise if other detail is 
helpful. 

Process:   wsjtx [2348]
Path:  /Applications/wsjtx.app/Contents/MacOS/wsjtx
Identifier:org.k1jt.wsjtx
Version:   v2.4.0 (2.4.0)
Code Type: X86-64 (Native)
Parent Process:bash [610]
Responsible:   wsjtx [2348]
User ID:   501

Date/Time: 2021-02-28 05:39:31.910 -0600
OS Version:Mac OS X 10.14.6 (18G8022)
Report Version:12
Anonymous UUID:1E2D07E1-9532-235B-3F34-D0F5B383F64D


Time Awake Since Boot: 41000 seconds

System Integrity Protection: enabled

Crashed Thread:0  Dispatch queue: com.apple.main-thread

Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x00720232
Exception Note:EXC_CORPSE_NOTIFY

Termination Signal:Segmentation fault: 11
Termination Reason:Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [2348]

VM Regions Near 0x720232:
MALLOC_LARGE   00014860c000-00014868c000 [  512K] rw-/rwx 
SM=PRV  
--> 
STACK GUARD76aea000-76aeb000 [4K] ---/rwx 
SM=NUL  stack guard for thread 8

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.qt-project.QtCore   0x00012bb8b3ee QMutex::lock() + 14
1   org.qt-project.QtCore   0x00012bc452fe 
QRegularExpressionPrivate::compilePattern() + 30
2   org.qt-project.QtCore   0x00012bc46a49 
QRegularExpression::match(QString const&, int, QRegularExpression::MatchType, 
QFlags) const + 41
3   org.k1jt.wsjtx  0x00010f1c0536 
MainWindow::stdCall(QString const&) + 54
4   org.k1jt.wsjtx  0x00010f20964b 
MainWindow::genCQMsg() + 619
5   org.k1jt.wsjtx  0x00010f1b81bd 
MainWindow::handle_transceiver_update(Transceiver::TransceiverState const&) + 
445
6   org.qt-project.QtCore   0x00012bd93f95 void 
doActivate(QObject*, int, void**) + 1157
7   org.k1jt.wsjtx  0x00010f228df5 
Configuration::impl::handle_transceiver_update(Transceiver::TransceiverState 
const&, unsigned int) + 1157
8   org.qt-project.QtCore   0x00012bd8bb9f 
QObject::event(QEvent*) + 943
9   org.qt-project.QtWidgets0x00012ac25e9a 
QWidget::event(QEvent*) + 4698
10  org.qt-project.QtWidgets0x00012abea9ea 
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 266
11  org.qt-project.QtWidgets0x00012abebe11 
QApplication::notify(QObject*, QEvent*) + 497
12  org.k1jt.wsjtx  0x00010f268226 
ExceptionCatchingApplication::notify(QObject*, QEvent*) + 22
13  org.qt-project.QtCore   0x00012bd60a34 
QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
14  org.qt-project.QtCore   0x00012bd61d79 
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 809
15  libqcocoa.dylib 0x00012e820259 
QCocoaEventDispatcherPrivate::processPostedEvents() + 313
16  libqcocoa.dylib 0x00012e8209c8 
QCocoaEventDispatcherPrivate::postedEventsSourceCallback(void*) + 40
17  com.apple.CoreFoundation0x7fff484ccd13 
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
18  com.apple.CoreFoundation0x7fff484cccb9 __CFRunLoopDoSource0 
+ 108
19  com.apple.CoreFoundation0x7fff484b05af 
__CFRunLoopDoSources0 + 195
20  com.apple.CoreFoundation0x7fff484afb79 __CFRunLoopRun + 1189
21  com.apple.CoreFoundation0x7fff484af482 CFRunLoopRunSpecific 
+ 455
22  com.apple.HIToolbox 0x7fff4770e1ab 
RunCurrentEventLoopInMode + 292
23  com.apple.HIToolbox 0x7fff4770dee5 
ReceiveNextEventCommon + 603
24  com.apple.HIToolbox 0x7fff4770dc76 
_BlockUntilNextEventMatchingListInModeWithFilter + 64
25  com.apple.AppKit0x7fff45aa577d _DPSNextEvent + 1135
26  com.apple.AppKit0x7fff45aa446b 
-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] 
+ 1361
27  com.apple.AppKit0x7fff45a9e588 -[NSApplication run] 
+ 699
28  libqcocoa.dylib 0x00012e81f62f 
QCocoaEventDispatcher::processEvents(QFlags) + 
2495
29  org.qt-project.QtCore   0x00012bd5cacf 
QEventLoop::exec(QFlags) + 431
30  org.qt-project.QtCore   0x00012bd61042 
QCoreApplication::exec() + 130
31  org.k1jt.wsjtx  0x00010f264ec7 main + 10551
32  libdyld.dylib   0x7fff744943d5 

[wsjt-devel] WSJT-X v2.4.0rc1 crashes on OS 10.14.6

[David Schmocker]

Hi Bill:
Have you been able to find root cause of the crashes of WSJT-X in rc1 please?

 

Just about any operation I do, crashes about 50% of the time  with same result:

 

Last login: Sat Feb 27 13:22:02 on ttys000

Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx

Segmentation fault: 11

Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx

Segmentation fault: 11

Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx

Segmentation fault: 11

Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx

Segmentation fault: 11

Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx

Segmentation fault: 11

Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx

Segmentation fault: 11

Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx

Segmentation fault: 11

Davids-Mac-mini:~ davidschmocker$ /Applications/wsjtx.app/Contents/MacOS/wsjtx

 

 

Operations that cause WSJT-X to crash:
 Turn the VFO knob on my connected Elecraft K3S,  or
Go into Preferences, Audio tab, change one setting.. the moment I hit “OK”. 
(crash). 
 

If you need more data, I can supply it.   Please advise (maybe this issue has 
already been fixed for rc2 ?   

 

I saw someone else report they had crashes of their WSJT-X in Windows.. don’t 
know if cause is the same?? 

 

Thank you.  73,   please let me know if more data would help!

 

Dave KJ9I 

 

 

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

[wsjt-devel] Waterfall WSJT v10 vs. WSJT-X

[David Schmocker]

Everyone
Waterfall bake-off: WSJT v10 vs. WSJT-X :
WSJT v10. Nice waterfall with great detail. Six months ago, I would have 
joined the suggestion to “keep the old WSJT v10 waterfall”

 

Why I currently favor WSJT-X waterfall:

The precise frequency (DF) of target weak EME signal is usually not known until 
1st visible waterfall trace appears. 

WSJT-X sometimes (with aggressive settings) decodes JT-65A and/or Q65-60A 
signals that are barely or invisible on the waterfall.    (WSJT v10 would only 
decode when I could detect some faint paint-splashes on the waterfall). I 
realize the Waterfall gain, sensitivity, zero, etc.  settings have everything 
to do with when signal is visible vs. when it decodes.  

WSJT-X has the new Q65_Sync (fish-finder) (bottom of waterfall) that helps 
locate signals barely visible to the eye.  This is incredibly valuable because 
oft-times when running a sked with a new DX station,  his DF (radio frequency) 
remains unknown relative to mine (Doppler shift and all else factored in).

 

Scratching, scraping, digging for every 0.1dB more to bring that SNR to 
something usable is primary goal on 6m EME. 

 

I still use my old legacy JT-65A receive computers (one on Windows XP, another 
on Fedora core 30, and a third on Debian 10) but soon (with Q65), the XP PC 
will become officially obsolete (the hardware is insufficient to support 
current software) and the others will be changed from WSJT v11 to WSJT-X 
v2.4.0. 

 

Also, WSJT-X decodes multiple signals within the passband so WSJT-X replaces 
both WSJT v10 and MAP65 in a single software package. 

 

73,

Dave KJ9I

 

 

 

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

[wsjt-devel] Split weirdness with 2.3.0 Oc42df

[David Garnier]

Hello,

To operate 630m on IC-7300 I use an 80m-630m transmit converter,
this has worked flawlessly until recently.

I'm not sure how to describe this but Ham Lib appears to be recalling
from memory a "past split frequency setting" of the radio and now I 
can't clear it.  How do I clear this "memory setting?"

If I push the split button on 7300 the green indicates "S" so that piece
is still functional.

Thanks,

Dave - wb9own


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

Re: [wsjt-devel] WSJT-X crashes Mac OS 10.14.6 run via terminal window

[David J Schmocker]

Bill. Thank you. I was selecting a preset freq 

Sent from my iPhone using 100% recycled electrons


> On Feb 18, 2021, at 8:06 AM, Bill Somerville  wrote:
> 
> 
> On 18/02/2021 13:19, David Schmocker wrote:
>> Good morning everyone:
>> 
>> Symptom: WSJTX v2.4.0rc1 crashes (self-closes all windows) with MALLOC error:
>> 
>>  
>> 
>> Steps to duplicate behavior:
>> 
>> Launch WSJT-X using terminal window:  
>> /Applications/wsjtx.app/Contents/MacOS/wsjtx.  This returns (in terminal 
>> window):  Segmentation Fault 11
>>   Frequency select in to 6m  50.210 MHz (this causes WSJT-X immediately to 
>> Monitor ON (even with Monitor Off on Startup in Preferences).
>> Mode set to Q65-60A, SH messages checked
>> Position mouse into “TO RADIO” field  and click to put mouse there.. program 
>> closes. 
>>  
>> 
>> WSJTX Unexpected close window contents attached.
>> 
>>  
>> 
>> Process:   wsjtx [452]
>> 
>> Path:  /Applications/wsjtx.app/Contents/MacOS/wsjtx
>> 
>> Identifier:org.k1jt.wsjtx
>> 
>> Version:   v2.4.0 (2.4.0)
>> 
>> Code Type: X86-64 (Native)
>> 
>> Parent Process:bash [436]
>> 
>> Responsible:   wsjtx [452]
>> 
>> User ID:   501
>> 
>>  
>> 
>> Date/Time: 2021-02-18 07:10:29.605 -0600
>> 
>> OS Version:Mac OS X 10.14.6 (18G8022)
>> 
>> Report Version:12
>> 
>> Anonymous UUID:1E2D07E1-9532-235B-3F34-D0F5B383F64D
>> 
>>  
>> 
>>  
>> 
>> Time Awake Since Boot: 330 seconds
>> 
>>  
>> 
>> System Integrity Protection: enabled
>> 
>>  
>> 
>> Crashed Thread:0  Dispatch queue: com.apple.main-thread
>> 
>>  
>> 
>> Exception Type:EXC_BAD_ACCESS (SIGSEGV)
>> 
>> Exception Codes:   KERN_INVALID_ADDRESS at 0x00300232
>> 
>> Exception Note:EXC_CORPSE_NOTIFY
>> 
>>  
>> 
>> Termination Signal:Segmentation fault: 11
>> 
>> Termination Reason:Namespace SIGNAL, Code 0xb
>> 
>> Terminating Process:   exc handler [452]
>> 
> Hi Dave,
> 
> I have not yet been able to reproduce this issue. It is somehow related to 
> the text entered in the WSJT-X main window frequency/band selection entry. 
> Above you say "Frequency select in to 6m  50.210 MHz", what exactly did that 
> entail. For example were you selecting a preset working frequency, or were 
> you directly entering a new frequency?
> 
> 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] WSJT-X self-closing on OS 10.14.6 (v2.4.0 RC1)

[David Schmocker]

Bill,

Thank you so much.  You guys are great.. and WE REALLY appreciate all the hard 
work going on by you and all of the development team!

Very 73,

Dave KJ9I 

 

From: Bill Somerville 
Reply-To: WSJT software development 
Date: Thursday, February 18, 2021 at 7:35 AM
To: 
Subject: Re: [wsjt-devel] WSJT-X self-closing on OS 10.14.6 (v2.4.0 RC1)

 

On 17/02/2021 20:12, David Schmocker wrote:

Everyone:
Running WSJT-X from the terminal window, it runs fine in Q65 mode, however I 
set mode to Q65-60A, and then I clear TO RADIO field (by putting mouse in this 
field then hitting delete to erase JA station in there from before”.  Next I 
type in ‘N0TB’ (who was calling CQ but not decoding at the time).  As soon as I 
type N0TB into TO RADIO then tab out of the field, the program closes. 

Here are details:

Hi Dave,

thanks for the issue report, I am investigating.

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] Running WSJT-X v2.4.0rc1 from terminal window on OS 10.14.6 Mojave Mac mini

[David Schmocker]

Hi Bill:
It seems you are always working (never sleeping)!  Thank you for your help. 

 

Here’s permissions view you requested: 

 

 

 

From: Bill Somerville 
Reply-To: WSJT software development 
Date: Wednesday, February 17, 2021 at 4:17 AM
To: 
Subject: Re: [wsjt-devel] Running WSJT-X v2.4.0rc1 from terminal window on OS 
10.14.6 Mojave Mac mini

 

On 17/02/2021 01:57, David Schmocker wrote:
Hi Bill,
1) uninstalled all WSJT-X prior instances (v2.2.2, v2.3.0, and v2.4.0rc1) by 
dragging icon from Applications folder into trash can
2) re-down loaded WSJT-X .dmg file
3) launched .dmg installer
4) carefully followed the G4KLA Readme.txt instructions for my Intel processor 
(installation succeeded)
5) re-tried to run WSJT-X (from shortcut).  Realizing in the past it 
auto-closed itself, I only kept it open for 15 seconds then closed it with 
pull-down menu: File-Quit (WSJTX).
6) opened terminal window and tried again to run WSJT-X  (no success) 
Screenshots attached.    Thank you 
73,
Dave
Hi Dave,

did you follow the graphical instructions in the installer to drag and drop the 
WSJT-X application bundle into the /Applications folder?

Assuming you did, what does the following command print when run from a 
terminal:
ls -lR /Applications/wsjtx*
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] Is there any forecast for WSJT-X v2.4.0rc2 please

[David Schmocker]

Bill, 
Thank you so much for your patience.
Here's bottom section of my finder in which I have left just single instance of 
WSJTX v2.4.0rc1 (named wsjtx).  

And what I get when I try to run it in terminal window with or without 
"Untitled" up front.I appreciate any inputs/suggestions.  Thank you   very 
73,
Dave


On 2/16/21, 5:05 PM, "Bill Somerville"  wrote:

Hi David,

to uninstall an application bundle like WSJT-X simply drag and drop it 
into the trash can.

73
Bill
G4WJS.

On 16/02/2021 22:39, David Schmocker wrote:
> Gents
> Thank you; I believe I foolishly (and contrary to User-Guide instruction) 
 installed WSJTX v2.4.0rc1 and v2.3.0 over the top of  formerly working v2.2.2 
because I don't understand how you create a separate install folder in OS.
> After doing the terminal window set-up commands for Mac, I dragged all 
(2.3.0 and 2.4.0rc1) installer shortcuts into the same Mac Applications folder).
>
> Next thinking I could somehow get the computer to separate these three 
WSJT shortcuts all same name in Applications folder (viewed in Finder), I went 
into finder and renamed two of the three instances with the version number.
>
> Now I think I need to learn how to uninstall all of the parts in OS 
10.14.6, I think I need to start over with a clean install of just 2.4.0rc1.
>
> I would highly prefer to read or go off-line with this; your developer 
time is way too valuable!
>
> Very 73,
> Dave KJ9I
>
>
> On 2/16/21, 4:28 PM, "Joe Taylor"  wrote:
>
>  Dave --
>
>  There is no problem using WSJT-X v2.4.0-rc1 under macOS.  Many are 
doing
>  so; all needed instructions have been posted on this reflector.  If 
you
>  need help, just ask.
>
>  Release candidates are published and updated when they are ready.  At
>  this stage of development we can't predict exactly when that will be.
>
>   -- Joe, K1JT
>
>  On 2/16/2021 5:03 PM, David Schmocker wrote:
>  > Good afternoon/good evening gents:
>  > Is there any estimate when WSJT-X v2.4.0rc2 might be on the WSJT-X 
home
>  > page please?
>  >
>  > More detail:
>  >
>  > Joe K1JT mentioned it would help if I could provide 6m EME .wav 
files.
>  > I am currently unable to run WSJT-X v2.4.0rc1 because my OS 
10.14.6
>  > Mojave shuts down WSJTX with a Memory Allocation MALLOC error.
>  >
>  > Bill kindly provided the terminal-window work-around which doesn’t 
work
>  > (blocked due to permissions) so I am unable to do much yet.I 
tried
>  > sudo su (then my password) and then the path to launch WSJTX but it
>  > fails out every time.
>  >
>  > I don’t wish to consume precious developers’ time on tech support 
here.
>  > Just wondering when we may expect to see 2.4.0rc2.
>  >
>  > We REALLY appreciate all you’re doing!   Thank you so much,  very 
73,
>  >
>  >
>  > Dave KJ9I




___
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] Is there any forecast for WSJT-X v2.4.0rc2 please

[David Schmocker]

Gents
Thank you; I believe I foolishly (and contrary to User-Guide instruction)  
installed WSJTX v2.4.0rc1 and v2.3.0 over the top of  formerly working v2.2.2 
because I don't understand how you create a separate install folder in OS.
After doing the terminal window set-up commands for Mac, I dragged all (2.3.0 
and 2.4.0rc1) installer shortcuts into the same Mac Applications folder). 

Next thinking I could somehow get the computer to separate these three WSJT 
shortcuts all same name in Applications folder (viewed in Finder), I went into 
finder and renamed two of the three instances with the version number.   

Now I think I need to learn how to uninstall all of the parts in OS 10.14.6, I 
think I need to start over with a clean install of just 2.4.0rc1.

I would highly prefer to read or go off-line with this; your developer time is 
way too valuable! 

Very 73,
Dave KJ9I 


On 2/16/21, 4:28 PM, "Joe Taylor"  wrote:

Dave --

There is no problem using WSJT-X v2.4.0-rc1 under macOS.  Many are doing 
so; all needed instructions have been posted on this reflector.  If you 
need help, just ask.

Release candidates are published and updated when they are ready.  At 
this stage of development we can't predict exactly when that will be.

-- Joe, K1JT

On 2/16/2021 5:03 PM, David Schmocker wrote:
> Good afternoon/good evening gents:
> Is there any estimate when WSJT-X v2.4.0rc2 might be on the WSJT-X home 
> page please?
> 
> More detail:
> 
> Joe K1JT mentioned it would help if I could provide 6m EME .wav files. 
> I am currently unable to run WSJT-X v2.4.0rc1 because my OS 10.14.6 
> Mojave shuts down WSJTX with a Memory Allocation MALLOC error.
> 
> Bill kindly provided the terminal-window work-around which doesn’t work 
> (blocked due to permissions) so I am unable to do much yet.I tried 
> sudo su (then my password) and then the path to launch WSJTX but it 
> fails out every time.
> 
> I don’t wish to consume precious developers’ time on tech support here.  
> Just wondering when we may expect to see 2.4.0rc2.
> 
> We REALLY appreciate all you’re doing!   Thank you so much,  very 73,
> 
> 
> Dave KJ9I
> 
> 
> 
> ___
> 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] Is there any forecast for WSJT-X v2.4.0rc2 please

[David Schmocker]

Hi Bill:
Screenshot attached:   (note my application is named ‘WSJTX_2.4.0rc1’).    

Thank you 

 

 

From: Bill Somerville 
Reply-To: WSJT software development 
Date: Tuesday, February 16, 2021 at 4:08 PM
To: 
Subject: Re: [wsjt-devel] Is there any forecast for WSJT-X v2.4.0rc2 please

 

On 16/02/2021 22:03, David Schmocker wrote:

Good afternoon/good evening gents:
Is there any estimate when WSJT-X v2.4.0rc2 might be on the WSJT-X home page 
please?

 

More detail:

Joe K1JT mentioned it would help if I could provide 6m EME .wav files.I am 
currently unable to run WSJT-X v2.4.0rc1 because my OS 10.14.6 Mojave shuts 
down WSJTX with a Memory Allocation MALLOC error.

 

Bill kindly provided the terminal-window work-around which doesn’t work 
(blocked due to permissions) so I am unable to do much yet.I tried sudo su 
(then my password) and then the path to launch WSJTX but it fails out every 
time.

I don’t wish to consume precious developers’ time on tech support here.  Just 
wondering when we may expect to see 2.4.0rc2. 

 

We REALLY appreciate all you’re doing!   Thank you so much,  very 73,


Dave KJ9I

Hi Dave,

please explain what "blocked due to permissions" consists of? You don't need to 
use root privileges to run WSJT-X, in fact it strongly recommended not to.

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

[wsjt-devel] Is there any forecast for WSJT-X v2.4.0rc2 please

[David Schmocker]

Good afternoon/good evening gents:
Is there any estimate when WSJT-X v2.4.0rc2 might be on the WSJT-X home page 
please?

 

More detail:

Joe K1JT mentioned it would help if I could provide 6m EME .wav files.    I am 
currently unable to run WSJT-X v2.4.0rc1 because my OS 10.14.6 Mojave shuts 
down WSJTX with a Memory Allocation MALLOC error.

 

Bill kindly provided the terminal-window work-around which doesn’t work 
(blocked due to permissions) so I am unable to do much yet.    I tried sudo su 
(then my password) and then the path to launch WSJTX but it fails out every 
time.

I don’t wish to consume precious developers’ time on tech support here.  Just 
wondering when we may expect to see 2.4.0rc2. 

 

We REALLY appreciate all you’re doing!   Thank you so much,  very 73,


Dave KJ9I

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

Re: [wsjt-devel] WSJT-x2.3.0 Anwser problem

[david]

Adrian,

 

Regarding your “need to rework the station”, all the data you need to log the 
QSO is in WSJT-X’s ALL.TXT file.  I occasionally have to use that to record a 
QSO.

 

David, AK2L

 

 

From: Adrian  
Sent: Tuesday, February 16, 2021 12:01
To: WSJT software development 
Subject: Re: [wsjt-devel] WSJT-x2.3.0 Anwser problem

 

The problem I am having with v2.3.0 is the auto log popup sometimes not working 
on the RR73 or 73, and a need to rework the station to get the logging popup. 
The effect is random and not often.

The Call 1st feature you describe always works here on v2.3.0, but I also have 
the checkbox in settings to force 1st call on CQ

On 17/2/21 2:53 am, on4...@telenet.be <mailto:on4...@telenet.be>  wrote:

Hi Joe and colleagues,
 
I have identified a problem here with a colleague PA3GZD. It works with WSJT-X 
version 2.3.0 in Windows 7. Everything has always worked fine, until now. He's 
going to call CQ. On his right screen he sees a station coming back to him, but 
he keeps calling CQ. WSJT-X does not answer the answering station. If PA3GZD 
then clicks on that station on the right screen, the QSO will continue and 
reports will be exchanged. What can go wrong here. Like info. Thanks in 
advance. See alo attachment.
 
Kind regards
ON4CKT Rudy
https://www.qsl.net/on4ckt






___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto: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] Rc4 Tx levels will cause future QRM problems

[David Tiller]

No wheel, only Mac touchpad (wheel emulation w/ 2 finger slide stinks).  No 
easy page up/down either. 

> On Feb 15, 2021, at 11:24, Larry B. via wsjt-devel 
>  wrote:
> 
> Or the wheel on your mouse.
> 
> 73 -- Larry -- W1DYJ
> 
>  
> From: Bill Somerville
> Sent: Monday, February 15, 2021 10:01
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] Rc4 Tx levels will cause future QRM problems
>  
> Hi David,
>  
> you can already do that by selecting the slider and using the up and down 
> arrow keys. Page up and down for 1 dB increments.
>  
> 73
> Bill
> G4WJS.
>  
>> On 15/02/2021 14:58, David Tiller wrote:
>> You wrote: "How about adding a small "dB' box right under the "Pwr" label"
>> 
>> If you add that (and I hope you do), please make it a spinner box so we can 
>> adjust it with up/down arrows by preferably 0.1 dB increments. 
>> 
>>> On Feb 15, 2021, at 9:35 AM, Rich - K1HTV mailto:k1...@comcast.net wrote:
>>> 
>>> I noticed that while running WSJT-X v2.4.0-rc1, the original WSJT-X "Pwr" 
>>> control setting produced excessive AGC levels on my K3 transceiver. TX 
>>> levels are over 5 dB higher with WSJT-X Version 2.4.0-rc1 than with 
>>> previous versions.
>>> 
>>> Unless a software change is made so TX audio levels match those of previous 
>>> versions of WSJT-X, I'm afraid that we all will be hearing more kazoo 
>>> sounds on the FT8 & FT4 frequencies and will be seeing more and more 
>>> spurious signals on our Wide Graph screens.
>>> 
>>> "Pwr" slider idea:
>>> Would it be possible to change the way to read the "Pwr" slider setting dB 
>>> level?  Presently, users must move the slider setting in order to check the 
>>> dB level,We should be able to read the setting without having to change it.
>>> 
>>> How about adding a small "dB' box right under the "Pwr" label  I think that 
>>> would make more sense than the way it is now. Can this change be 
>>> implemented?
>>> 
>>> 73,
>>> Rich - K1HTV
>  
> 
> ___
> 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] Rc4 Tx levels will cause future QRM problems

[David Tiller]

Bill,

Selecting the slider often changes it, at least on a Mac, so you have no idea 
what the original setting was. Having a way to adjust it without having to be a 
touchpad ninja would help.


> On Feb 15, 2021, at 10:01 AM, Bill Somerville  wrote:
> 
> Hi David,
> 
> you can already do that by selecting the slider and using the up and down 
> arrow keys. Page up and down for 1 dB increments.
> 
> 73
> Bill
> G4WJS.
> 
> On 15/02/2021 14:58, David Tiller wrote:
>> You wrote: "How about adding a small "dB' box right under the "Pwr" label"
>> 
>> If you add that (and I hope you do), please make it a spinner box so we can 
>> adjust it with up/down arrows by preferably 0.1 dB increments. 
>> 
>>> On Feb 15, 2021, at 9:35 AM, Rich - K1HTV  
>>> <mailto:k1...@comcast.net> wrote:
>>> 
>>> I noticed that while running WSJT-X v2.4.0-rc1, the original WSJT-X "Pwr" 
>>> control setting produced excessive AGC levels on my K3 transceiver. TX 
>>> levels are over 5 dB higher with WSJT-X Version 2.4.0-rc1 than with 
>>> previous versions.
>>> 
>>> Unless a software change is made so TX audio levels match those of previous 
>>> versions of WSJT-X, I'm afraid that we all will be hearing more kazoo 
>>> sounds on the FT8 & FT4 frequencies and will be seeing more and more 
>>> spurious signals on our Wide Graph screens.
>>> 
>>> "Pwr" slider idea:
>>> Would it be possible to change the way to read the "Pwr" slider setting dB 
>>> level?  Presently, users must move the slider setting in order to check the 
>>> dB level,We should be able to read the setting without having to change it.
>>> 
>>> How about adding a small "dB' box right under the "Pwr" label  I think that 
>>> would make more sense than the way it is now. Can this change be 
>>> implemented?
>>> 
>>> 73,
>>> Rich - K1HTV
> 
> ___
> 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] Rc4 Tx levels will cause future QRM problems

[David Tiller]

Bill,

I don't know about anyone else's setup, but my max power, no ALC power slider 
values are radically different per band. There is no one analog drive level 
adjustment on my interface (RigExpert Standard) that'll give reasonable power 
levels on all bands. My rig is a 756PRO, BTW.

> On Feb 15, 2021, at 10:05 AM, Bill Somerville  wrote:
> 
> On 15/02/2021 14:35, Rich - K1HTV wrote:
>> I noticed that while running WSJT-X v2.4.0-rc1, the original WSJT-X "Pwr" 
>> control setting produced excessive AGC levels on my K3 transceiver. TX 
>> levels are over 5 dB higher with WSJT-X Version 2.4.0-rc1 than with previous 
>> versions.
>> 
>> Unless a software change is made so TX audio levels match those of previous 
>> versions of WSJT-X, I'm afraid that we all will be hearing more kazoo sounds 
>> on the FT8 & FT4 frequencies and will be seeing more and more spurious 
>> signals on our Wide Graph screens.
>> 
>> "Pwr" slider idea:
>> Would it be possible to change the way to read the "Pwr" slider setting dB 
>> level?  Presently, users must move the slider setting in order to check the 
>> dB level,We should be able to read the setting without having to change it.
>> 
>> How about adding a small "dB' box right under the "Pwr" label  I think that 
>> would make more sense than the way it is now. Can this change be implemented?
>> 
>> 73,
>> Rich - K1HTV
> 
> Rich,
> 
> everyone should be setting their equipment used with WSJT-X to give maximum 
> clean output when the Pwr slider is at the top (0dB attenuation).
> 
> The output levels have not changed, have you checked your setup, particularly 
> the master sound card output level and the per application mixer level fro 
> WSJT-X?
> 
> See https://wsjtx.groups.io/g/main/message/13890 for a recipe for setting Tx 
> audio levels correctly.
> 
> 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] Rc4 Tx levels will cause future QRM problems

[David Tiller]

You wrote: "How about adding a small "dB' box right under the "Pwr" label"

If you add that (and I hope you do), please make it a spinner box so we can 
adjust it with up/down arrows by preferably 0.1 dB increments. 

> On Feb 15, 2021, at 9:35 AM, Rich - K1HTV  wrote:
> 
> I noticed that while running WSJT-X v2.4.0-rc1, the original WSJT-X "Pwr" 
> control setting produced excessive AGC levels on my K3 transceiver. TX levels 
> are over 5 dB higher with WSJT-X Version 2.4.0-rc1 than with previous 
> versions.
> 
> Unless a software change is made so TX audio levels match those of previous 
> versions of WSJT-X, I'm afraid that we all will be hearing more kazoo sounds 
> on the FT8 & FT4 frequencies and will be seeing more and more spurious 
> signals on our Wide Graph screens.
> 
> "Pwr" slider idea:
> Would it be possible to change the way to read the "Pwr" slider setting dB 
> level?  Presently, users must move the slider setting in order to check the 
> dB level,We should be able to read the setting without having to change it.
> 
> How about adding a small "dB' box right under the "Pwr" label  I think that 
> would make more sense than the way it is now. Can this change be implemented?
> 
> 73,
> Rich - K1HTV
> ___
> 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] #Feature request. 2.4.0

[David Schmocker]

GA/GM Bill and all of the developers, 

Thank you so much for all the team is doing.   

 

Can Short-Hand messages be added for Q65A (used at 6m)  also please?   

 

It’s helpful to have those single-tone messages  Q65A at 6m EME because I have 
had at least one 6m EME JT65A weak signal QSO where the decoder didn’t decode 
the SH message, yet I was able to visibly see a ‘paint splash’ (partial trace) 
at the right frequencies knowing that SH message that was being sent so I could 
visually decode this.   Also, if I go on a DXpedition (which I plan to), [my 
apologies in advance this is going to open a hornet’s nest], I am interested in 
working more stations, not spending time distinguishing between level-based 
reports.  Perhaps my HF background where contesters give “599” no matter 
what colors this request.   With EME,  SH messages help.  Having the choice of 
SH or not gives the level-sensitive or SH option. 

 

I appreciate your consideration. Thank you!   Very 73,

 

Dave KJ9I

 

(flames if any to be sent to me directly not to the list please)

 

From: Bill Somerville 
Reply-To: WSJT software development 
Date: Tuesday, February 9, 2021 at 5:00 AM
To: 
Subject: Re: [wsjt-devel] #Feature request. 2.4.0

 

On 09/02/2021 03:54, Hattori, Yoshihisa wrote:

Hi all.

I am testing Q65 and realized that we are missing Short hand indicator on 
waterfall display, which is provided for JT65. (three yellow lines suggesting 
the RO/RRR/73 tones.) While less Q65/QRA64 users are using shorthand, it is 
good to have those since Sh will not be decoded and users need to visually 
identify the signal. Can you please implement it?

 

De JO1LVZ/Hatt

Hi Hatt-san,

the single tone short code markers are shown for sub-modes C or wider.

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] TS-450S

[David Tiller]

Also, the CP2012 is not 5v tolerant. 
https://www.sparkfun.com/datasheets/IC/cp2102.pdf

> On Feb 8, 2021, at 3:33 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> Hmmm..that's 4-wire...so ground, tx, rx, and 5V and wouldn't work with 
> hardware flow control.
> 
> Mike W9MDB
> 
> 
> 
> 
> On Monday, February 8, 2021, 01:33:11 PM CST, August Treubig 
>  wrote:
> 
> 
> A din 6 pin and this will work fine.
> 
> https://www.adafruit.com/product/954 
> 
> No magic.  Just a bit of soldering.
> Aug
> AG5AT 
> 
> Sent from my iPad
> 
>> On Feb 8, 2021, at 1:02 PM, Bill Somerville  wrote:
>> 
> 
>> 
> 
> Hi Mike,
> 
> there are several third-party replacements for the now unavailable IF-232C 
> module that is needed on this and other early Kenwood rigs. Most faithfully 
> replicate the original IF-232C, some may not. The manual is almost certainly 
> correct, the reporter, if he is correct, almost certainly has a non-standard 
> IF-232C replacement.
> 
> 73
> Bill
> G4WJS.
> 
> On 08/02/2021 18:17, Black Michael via wsjt-devel wrote:
>> The dude said "manual is wrong".
>> 
>> Trying to get more information on serial cable to see if that's the cause.
>> 
>> Old thread noticed a difference between cable types on a 450.  Might have to 
>> do with RTS/CTS wiring differences and whether the cable supports hardware 
>> flow control.
>> 
>> https://wsprnet.org/drupal/node/1307 
>> 
>> Mike W9MDB
>> 
>> 
>> On Monday, February 8, 2021, 12:06:48 PM CST, Bill Somerville 
>>   wrote:
>> 
>> 
>> On 08/02/2021 17:45, Black Michael via wsjt-devel wrote:
>> 
>> > Anybody with a TS-450S out there that is available for some testing?
>> >
>> > I've got somebody claiming it needs 1 stop bit and XONXOFF handshake 
>> > which I've never heard before and 2 stop bits and HARDWARE handshake 
>> > is the default setup and has been for years.
>> >
>> > Mike W9MDB
>> 
>> Mike,
>> 
>> 
>> according to the TS-450S/TS-690S CAT programming manual it is full 
>> duplex 4800 baud 8N2 with RTS/CTS flow control using TTL signal levels. 
>> I would be very surprised if that information was incorrect!
>> 
>> 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 
> 
> ___
> 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] wsjtx v2.3-rc4 TX6 oddity

[David Tiller]

I have seen the same behavior and haven't been able to nail down what triggers 
it either.

> On Jan 30, 2021, at 8:08 AM, Alan Groups  wrote:
> 
> I changed the text message in Tx6 by adding a call prefix  so it became "CQ 
> JA..."
> 
> Worked OK until I tried to change it back to just "CQ" - then the change 
> wouldn't stick.  It kept reverting to "CQ JA" several times, but eventually 
> it did hold.
> 
> Not sure what happened, but I may have been a bit quick and initially changed 
> it at the tail end of a TX slot.  Haven't been able to replicate it in 
> subsequent testing but just mentioning it as something clearly got tangled up.
> 
> In trying to replicate that I also managed to transmit "CQ J..." when the 
> code obviously read the message while I was in the middle of typing JA!
> 
> Incidentally while I was being received in JA no QSO resulted from the above 
> messing about - band opening closed!
> 
> Hope that helps.
> 
> Alan G0TLK
> 
> 
> 
> ___
> 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] WSPR Band Hopping

[David Birnbaum]

Glad to report that the crashes with 2.2.2 when band hopping in WSPR seems
to be fixed in 2.3.0-rc2

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

Re: [wsjt-devel] Logged wrong report

[David - K2DBK]

Any thoughts here?

 

From: K2DBK-WSJT  
Sent: Sunday, November 29, 2020 10:54 AM
To: 'WSJT software development' 
Subject: [wsjt-devel] Logged wrong report

 

I'm not sure if this is a regression from a previous version, but running
v2.3.0-rc2 I had the following sequence:

 



 

You can see that I was sent -16 3 times, then C31VM sent +06 to another
station, and finally came back with RRR to me. However, the pre-filled
values in the logging dialog make it appear that he sent +06 to me, as
evidenced by the line from the log:

 

2020-11-28,23:28:45,2020-11-28,23:31:15,C31VM,JN02,7.075287,FT8,-13,+06

 

I have the .wav files for this sequence if that would be helpful.

 

-- 

73,

David, K2DBK

 <http://k2dbk.com> http://k2dbk.com

twitter: @k2dbk

 

 

 

As an operator I know it's my responsibility to log the correct information,
but I'm guessing this isn't intended behavior.

 

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

Re: [wsjt-devel] WSJTX-2.3.0-rc2 compile error

[David Spoelstra]

You need the boost libraries:
sudo apt install libboost-dev


On Sun, Nov 15, 2020 at 12:09 PM Stefan Wernli  wrote:

> Hi,
>
> I get an error when compiling the new rc2 on debian testing. 2.3.0-rc1
> compiles successfully on the same system.
>
>
> -- Building wsjtx v2.3.0.0-rc2
> -- Performing Test HAVE_MATH
> -- Performing Test HAVE_MATH - Failed
> -- Performing Test HAVE_LIBM_MATH
> -- Performing Test HAVE_LIBM_MATH - Success
> CMake Error at
> /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:165
> (message):
>   Could NOT find Boost (missing: Boost_INCLUDE_DIR log_setup log)
> (Required is at least version "1.63")
> Call Stack (most recent call first):
>   /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:458
> (_FPHSA_FAILURE_MESSAGE)
>   /usr/share/cmake-3.18/Modules/FindBoost.cmake:2177
> (find_package_handle_standard_args)
>   CMakeLists.txt:841 (find_package)
>
> -- Configuring incomplete, errors occurred!
>
>
> 
> CMakeError.log:
>
> 
> Performing C SOURCE FILE Test HAVE_MATH failed with the following output:
> Change Dir:
>
> /home/user/bin/wsjtx-2.3.0-rc2/build/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp
>
> Run Build Command(s):/usr/bin/gmake cmTC_93eb3/fast && gmake[3]:
> Entering directory
>
> '/home/user/bin/wsjtx-2.3.0-rc2/build/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp'
> /usr/bin/gmake  -f CMakeFiles/cmTC_93eb3.dir/build.make
> CMakeFiles/cmTC_93eb3.dir/build
> gmake[4]: Entering directory
>
> '/home/user/bin/wsjtx-2.3.0-rc2/build/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp'
> Building C object CMakeFiles/cmTC_93eb3.dir/src.c.o
> /usr/bin/cc   -DHAVE_MATH -o CMakeFiles/cmTC_93eb3.dir/src.c.o -c
>
> /home/user/bin/wsjtx-2.3.0-rc2/build/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp/src.c
> Linking C executable cmTC_93eb3
> /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_93eb3.dir/link.txt
> --verbose=1
> /usr/bin/cc  -DHAVE_MATH CMakeFiles/cmTC_93eb3.dir/src.c.o -o cmTC_93eb3
> /usr/bin/ld: CMakeFiles/cmTC_93eb3.dir/src.c.o: in function `main':
> src.c:(.text+0x1f): undefined reference to `sqrt'
> collect2: error: ld returned 1 exit status
> gmake[4]: *** [CMakeFiles/cmTC_93eb3.dir/build.make:106: cmTC_93eb3] Error
> 1
> gmake[4]: Leaving directory
>
> '/home/user/bin/wsjtx-2.3.0-rc2/build/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp'
> gmake[3]: *** [Makefile:140: cmTC_93eb3/fast] Error 2
> gmake[3]: Leaving directory
>
> '/home/user/bin/wsjtx-2.3.0-rc2/build/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeTmp'
>
>
> Source file was:
> #include
> float f; int main(){sqrt(f);return 0;}
>
> 
>
> 73
> Stefan
>
>
>
> ___
> 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] TUNE and TX levels different, why?

[david]

TUNE could be the power setting recommended for your antenna tuner to do its
job.
And the TX level is for sending messages.
My antenna tuner requires at least 25 watts to work properly, but I may only
operate with 10 watts.

David, AK2L


-Original Message-
From: Barry Jackson  
Sent: Saturday, November 14, 2020 09:43
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] TUNE and TX levels different, why?

Why do TUNE and TX have separate level settings?

I want to use TUNE to adjust the power level for the next transmit cycles,
isn't that what everyone wants?

If there is some obscure use case for separate levels, then may I suggest a
means of making this optional, and the default being that there is only one
setting used for both TUNE and TX?
Maybe a 'Link' check box.

Thanks,
Barry
G4MKT


___
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] macOS Transmit Audio Problem

[David Kaplan via wsjt-devel]

I posted this on the main WSJT group with no response.

I'm running macOS Catalina 10.15.7, and recently intentionally erased my iMac 
and added all the programs back manually (rather than a restore) to delete 6 
years of crud (a technical term). Now I have WSJT-X 2.3.0 rc1 installed and am 
having an audio problem. The audio pref panels shows USB Audio Codec for 
transmit and receive, and receive populates the waterfall and decodes many 
stations.

My problem is that my IC-756Pro III keys, but does not transmit any audio. I 
checked and the power slider on the right side of WSJT-X is at its highest (for 
testing). I'm using a Timewave Navigator and checked that the controls haven't 
changed since I successfully transmitted before these changes, and I'm not 
hearing any audio from the Navigator.  I tried testing on WSJT-X 2.2.2 but had 
the same problem.

Any thoughts on where to investigate next?

Thanks & 73,

David, WA1OUI 

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

Re: [wsjt-devel] Shared memory error

[David Kaplan via wsjt-devel]

Quite a difference, thanks.

I had hoped that the distro at the WSJT-X site had been updated, but I guess 
not.

73,

David, WA1OUI

On Oct 27, 2020, at 4:31 PM, Black Michael via wsjt-devel 
 wrote:

https://wsjtx.groups.io/g/main/message/16844 
<https://wsjtx.groups.io/g/main/message/16844>

Mike W9MDB




On Tuesday, October 27, 2020, 03:27:05 PM CDT, David Kaplan via wsjt-devel 
 wrote:


I’m running Catalina 10.15.7 and a few weeks ago saw a notice that for the new 
beta the shmmax had to be increased. I carefully flagged and saved that email. 
Now that I am ready to install the beta, the email is nowhere to be found.

I had completely erased and re-installed everything on my iMac to clean off 6 
years of crud buildup.

I downloaded a fresh copy, have increased my shmmax to the14680064 listed in 
the readme and sample sysctl.conf. This is confirmed with the sysctl command. 
However I still get an error “Shared Memory Error, Unable to create shared 
segment”… and this is after reboot.

Thanks & 73,

David, WA1OUI

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
<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] Shared memory error

[David Kaplan via wsjt-devel]

I’m running Catalina 10.15.7 and a few weeks ago saw a notice that for the new 
beta the shmmax had to be increased. I carefully flagged and saved that email. 
Now that I am ready to install the beta, the email is nowhere to be found.

I had completely erased and re-installed everything on my iMac to clean off 6 
years of crud buildup.

I downloaded a fresh copy, have increased my shmmax to the14680064 listed in 
the readme and sample sysctl.conf. This is confirmed with the sysctl command. 
However I still get an error “Shared Memory Error, Unable to create shared 
segment”… and this is after reboot.

Thanks & 73,

David, WA1OUI

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

[wsjt-devel] WSTT-X 2.3.0 rc1, UDP Messages, FST4W T/R Period

[David Owen]

Hi
I am trying to find the FST4W T/R period (i.e. 120,300,900,...) in UDP
messages sent by WSJT-X 2.3.0 rc1. The "T/R Period" in the "Status"
messages always indicates "-1".
Am I looking in the wrong place?
Regards

David Owen
GM1OXB


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

Re: [wsjt-devel] Release Candidate: WSJT-X 2.3.0-rc1

[David Tiller]

Bill,

Thanks for the thoughtful and informative reply.

In the US, the regs https://www.law.cornell.edu/cfr/text/47/97.119 
<https://www.law.cornell.edu/cfr/text/47/97.119> state (** emphasis added **):

§ 97.119 Station identification.
(a) Each amateur station, except a space station or telecommand station, must 
transmit its assigned call sign on its transmitting channel at the end of each 
communication, ** and at least every 10 minutes during a communication**, for 
the purpose of clearly making the source of the transmissions from the station 
known to those receiving the transmissions. No station may transmit 
unidentified communications or signals, or transmit as the station call sign, 
any call sign not authorized to the station.

(b) The call sign must be transmitted with an emission authorized for the 
transmitting channel in one of the following ways:

(1) By a CW emission. When keyed by an automatic device used only for 
identification, the speed must not exceed 20 words per minute;

(2) By a phone emission in the English language. Use of a phonetic alphabet as 
an aid for correct station identification is encouraged;

(3) By a RTTY emission using a specified digital code when all or part of the 
communications are transmitted by a RTTY or data emission;

(4) By an image emission conforming to the applicable transmission standards, 
either color or monochrome, of § 73.682(a) of the FCC Rules when all or part of 
the communications are transmitted in the same image emission

b(1) is what I suggested. 

b(3) is applicable, but naturally you'd have to use some 'specified digital 
code' in addition to the signal you're trying to ID. RTTY would be way too wide 
- maybe a faster narrowband mode? It would be funny to ID a slow FST4 
transmission with a simultaneous fast FST4 transmission down-band. 

b(2) and b(4) are not applicable unless you want an unholy mess.

> On Sep 28, 2020, at 10:24 AM, Bill Somerville  wrote:
> 
> Hi David,
> 
> I am not sure of the exact FCC regulations. Here I believe sending a callsign 
> at the start and end of a QSO may be sufficient.
> 
> The callsign is effectively spread throughout the message, the nature of the 
> FEC parity bits is that each contributes to a set of received bits that *may* 
> be used to extract the message, those received bits may or may not include 
> the originally source encoded callsign. It is incorrect to state that the 
> parity bits are a repetition of any part of the original message, at least 
> not as any form of direct copy. this is the nature of parity bits when there 
> are more than one of them. As single parity bit can only be used to detect 
> certain types of errors like single bit errors, with more than one parity bit 
> greater than single bit errors can be detected, and missing (erased) bits can 
> be reconstructed.
> 
> All the standard messages contain the transmitting station callsign or a hash 
> code of it that can be mapped back to the callsign if it has been recently 
> received in full. Think of that like me identifying as WJS for brevity in an 
> ongoing QSO, a not uncommon practice which may or may not be construed as 
> proper identification.
> 
> For reference the relevant condition of the UK licence is this:
> 13 Identification
> 13(1) The Licensee, or, if this Licence is a Full Licence, then any other 
> authorised person
> who uses the Radio Equipment, shall ensure that:
> (a) the station is clearly identifiable at all times;
> (b) the Callsign is transmitted as frequently as is practicable during 
> transmissions, unless
> the specific requirements of Note (g) to the Notes to Schedule 1 of this 
> Licence apply;
> and
> (c) the Callsign is given in voice or other appropriate format consistent 
> with the mode of
> operation.
> The reference to Note (g) refers to this text which only applies when using 
> the 5MHz band:
> (vii) Where the Licensee intends to operate within a “net” (a network), the
> Licensee shall observe the following requirements in relation to the
> transmission of his or her Callsign:
> (a) The Licensee shall transmit the station Callsign when he
> first joins the net and on leaving it;
> (b) subject to sub-clause (c) below, whilst participating in the
> net, the Licensee shall not be required to transmit the
> station Callsign when making contact with other
> participants;
> (c) where the Licensee’s transmissions have been other than
> in speech mode for at least fifteen minutes, the Licensee
> shall transmit his call sign when next he transmits speech.
> 
> 73
> Bill
> G4WJS.
> 
> On 28/09/2020 14:41, David Tiller wrote:
>> Thanks, Joe, K1JT, Steve, K9AN, and Bill, G4WJS for all your hard work and 
>> these new modes.
>> 
>> I don't want to be a stick in the mud and I am not trying t

Re: [wsjt-devel] Release Candidate: WSJT-X 2.3.0-rc1

[David Tiller]

Thanks, Joe, K1JT, Steve, K9AN, and Bill, G4WJS for all your hard work and 
these new modes.

I don't want to be a stick in the mud and I am not trying to stir the pot, but 
is there any issue with modes that transmit for >= 10 minutes and the US 
requirement to ID at least every 10 minutes?  

I don't think part 97.119 addresses IDs that take longer than 10 minutes. 

I admit I don't fully understand all of the details of the transmitted data in 
FT4/FST4, so if I'm off-base, please forgive me (and kindly correct me!). If 
the FEC employed spreads the callsign bits out over the message, then my 
analysis is incorrect from the git-go.

For FST4, if the message bits are symbol-encoded and transmitted in the order 
as shown in the QEX Article on FT4 [See QEX 2020 Jul/Aug, page 7] and assuming 
the sender's callsign is sent as the second c28 call, it looks like in most 
cases the sending callsign is within the first 57 bits of the 77 bit raw 
message.  That means that 57/77 = 74% of the raw message has to be transmitted 
before the sender's callsign is transmitted. That means the longest 
transmission that gets the sender's call in at/under 10 minutes is about 13.5 
minutes or 810 seconds.

If I have the callsigns backwards, then the sender's call is sent first in most 
cases. That makes the longest transmission more like 27.5 minutes, but then the 
last 17.5 minutes of the transmission are unidentified (barring FEC repetition 
of the callsign bits). That means the longest tx in this case would be 20 
minutes - The first 10 are identified in the message and the last 10 would be 
identified by an explicit ID by the operator.

I know this won't be a popular idea, but adding a low power CW ident at a 
standard (low, perhaps sub 100 Hz) frequency in addition to the transmitted 
signal every 10 minutes would unquestionably address this. Remember that the 
requirement is for each station to ID, not to ensure that the ID doesn't clash 
with other ID transmissions. If every FST4 signal over 10 minutes id'ed via CW 
on VFO + 50 Hz, say, that would be sufficient to satisfy 97.119.

Ideas/comments?

Again, I'm just asking the question, please don't shoot the messenger.

> 

> On Sep 27, 2020, at 4:23 PM, Joe Taylor  wrote:
> 
> The first public candidate release of WSJT-X 2.3.0 is now available for 
> download and use by beta testers.  This release is your first chance to
> try two new modes designed especially for use on the LF and MF bands, and to 
> provide feedback to the WSJT Development Team.  The new modes are:
> 
> - FST4, for 2-way QSOs.  Options for sequence lengths from 15 seconds
>   to 30 minutes, with threshold sensitivities from -20.7 to -43.2 dB in
>   a 2500 Hz reference bandwidth.
> 
> - FST4W, for WSPR-like transmissions.  Sequence lengths from 2 minutes
>   to 30 minutes, threshold sensitivities from -32.8 to -44.8 dB.
> 
> FST4-60 is about 1.7 dB more sensitive than JT9, largely because it uses 
> multi-symbol block detection where appropriate. With AP decoding in FST4 the 
> advantage can be as much as 4.7 dB. Additional sensitivity details with 
> respect to path Doppler spread are illustrated in the following graph 
> comparing JT9 and FST4-60:
> https://physics.princeton.edu/pulsar/k1jt/jt9_vs_fst4.pdf
> 
> FST4W-120 is about 1.4 dB more sensitive than WSPR, and FST4W submodes with 
> longer transmissions have proportionally better sensitivity. Decoding 
> probabilities are plotted as a function of SNR on the additive white Gaussian 
> noise (AWGN) channel for WSPR and all FST4W submodes here: 
> https://physics.princeton.edu/pulsar/k1jt/wspr_vs_fst4w.pdf
> 
> Tests over the past several months have shown FST4 and FST4W frequently 
> spanning intercontinental distances on the 2200 m and 630 m bands. Further 
> details and operating hints can be found in the "Quick-Start Guide to FST4 
> and FST4W":
> 
> https://physics.princeton.edu/pulsar/k1jt/FST4_Quick_Start.pdf
> 
> We strongly recommend that users of JT9 and WSPR on the LF and MF bands 
> should migrate to the more sensitive modes FST4 and FST4W.
> 
> 
> Links to installation packages for Windows, Linux, and Macintosh are 
> available here:
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
> Scroll down to find "Candidate release:  WSJT-X 2.3.0-rc1".
> 
> You can also download the packages from our SourceForge site:
> https://sourceforge.net/projects/wsjt/files/
> It may take a short time for the SourceForge site to be updated.
> 
> WSJT-X is licensed under the terms of Version 3 of the GNU General Public 
> License (GPL).  Development of this software is a cooperative project to 
> which many amateur radio operators have contributed.  If you use our code, 
> please have the courtesy to let us know about it.  If you find bugs or make 
> improvements to the code, please report them to us in a timely fashion.
> 
> We hope you will enjoy using this beta release of WSJT-X 2.3.0.  Please 
> report bugs by following instructions found here 

Re: [wsjt-devel] FST4/W

[David Tiller]

FA said: "But IIRC the OP asked for a description of the protocols, i.e. a 
design document ..."

On the WSJT-X homepage, https://physics.princeton.edu/pulsar/K1JT 
 under references, there are various 
links to to just that sort of thing:

Protocol design docs for:

FT4/FT8: https://physics.princeton.edu/pulsar/K1JT/FT4_FT8_QEX.pdf 


MSK144: https://physics.princeton.edu/pulsar/K1JT/MSK144_Protocol_QEX.pdf 


JT65: http://physics.princeton.edu/pulsar/K1JT/JT65.pdf 


JT65's Reed Solomon decoder: 
https://physics.princeton.edu/pulsar/K1JT/FrankeTaylor_QEX_2016.pdf 


The original WSJT: 
http://physics.princeton.edu/pulsar/K1JT/WSJT_QST_Dec2001.pdf 
 (almost 20 
years ago!)

I'm not sure it could've been any easier to find. 


> On Aug 27, 2020, at 12:44 PM, James Shaver  wrote:
> 
> “Code-parrots” is totally being added to my lexicon going forward lol 
> 
> 
> 73,
> N2ADV
> 
>> On Aug 27, 2020, at 11:36 AM, Fons Adriaensen  wrote:
>> 
>> On Thu, Aug 27, 2020 at 12:01:53PM +0100, Bill Somerville wrote:
>> 
>>> you are ignoring those that would take the unfinished work in progress,
>>> despite protocols not being finalized, and copy the code parrot fashion into
>>> their so-called derivative products, which they then release as "complete"
>>> before the original authors have even made a public release. All this
>>> despite being politely asked not to do just that until the protocols are
>>> fixed.
>> 
>> That is indeed a problem with most open source software, it has hit me
>> as well as developer of audio-related applications.
>> 
>> But IIRC the OP asked for a description of the protocols, i.e. a design
>> document, not for ready-to-use code. Surely such documentation does exist,
>> and I doubt very much it would help the code-parrots who probably don't
>> even understand the basics.
>> 
>> Ciao,
>> 
>> -- 
>> FA
>> 
>> 
>> 
>> ___
>> 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] Changes to the INSTALL file in the 2.2.2 tarball

[David Spoelstra]

Bill is correct. The tarball on this page is complete and easy to build:
https://physics.princeton.edu/pulsar/K1JT/wsjtx.html

I was just giving him some minor corrections to the INSTALL file in the
tarball. Otherwise it was a snap to build on Ubuntu 20.04.

-David, N9KT


On Tue, Aug 11, 2020 at 8:31 PM Bill Somerville 
wrote:

> Steve,
>
> your reply below makes no sense!
>
> I will repeat, the combined sources tarball we release includes
> instructions to build on Linux, they are complete. Yes there are some typos
> and it needs updating for the version numbers mentioned, that is fixed for
> the next release, did you even read this email thread before suggesting
> that some other instructions should be followed?
>
> What are you suggesting needs to be "forced" to run?
>
> By far the simplest instructions to follow are the ones provided in the
> single INSTALL file at the root of the sources tarball. Note the singular
> INSTALL file.
>
> Like many Open Source projects there are different build instructions for
> developers wishing to contribute to the project, there's nothing unusual
> about that, but those instructions are not needed for users who simply want
> to build the application to run. We provide a build script, and
> instructions to run it, just for that sort of user.
>
> 73
> Bill
> G4WJS.
>
> On 12/08/2020 01:21, Stephen VK3SIR wrote:
>
> Bill,
>
>
>
> KISS Principle in my answer to Rob’s post …. Yes the “dropped tarball” it
> can be forced to run … but its BY FAR simpler and easier to follow the
> instructions in the INSTALL files :-D
>
>
>
> I have had lots and lots and lots of background inquiry on Ubuntu 20.04 …
> following the steps in the install file and compiling from source is BY FAR
> the easiest way to make WSJTX work – and properly (considering there have
> also been a lot of changes to Hamlib).
>
>
>
> By the way, has the INSTALL files been updated for the next release as
> they were a little dated and some instructions out of sync?
>
>
>
> 73
>
>
>
> Steve I
>
> VK3VM / VK3SIR
>
>
>
> *From:* Bill Somerville  
> *Sent:* Wednesday, 12 August 2020 10:10 AM
> *To:* wsjt-devel@lists.sourceforge.net
> *Subject:* Re: [wsjt-devel] Changes to the INSTALL file in the 2.2.2
> tarball
>
>
>
> Steve,
>
>
>
> there is no need to follow the build instructions in the project git repo
> if you are building to run. Maybe if you are building to contribute
> patches. The INSTALL file in the sources tarball we provide contains
> complete instructions for building a working WSJT-X for Linux. Please don't
> over-complicate a relatively simple recipe for building.
>
>
>
> 73
> Bill
> G4WJS.
>
>
>
> On 12/08/2020 01:01, Stephen VK3SIR wrote:
>
> Rob,
>
>
>
> There is no repo that you can just “drop and run” for WSJTX 2.2.2 – You
> really need to compile your own 
>
>
>
> Go to the JTSDK @ GROUPS.IO site. I have a post there for dependencies
> etc. needed to build your own WSJTX on Ubuntu 20.04.
>
>
>
> i.e.
> https://groups.io/g/JTSDK/topic/some_dependencies_requisites/75311015?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,75311015
>
>
>
> Then follow the steps inside the INSTALL files (the top level one in the
> repo and then the main set of steps inside WSJTX.TGZ)
>
>
>
> 73
>
>
>
> Steve I
>
> VK3VM / VK3SIR
>
>
>
> *From:* Rob Robinett  
> *Sent:* Wednesday, 12 August 2020 8:44 AM
> *To:* WSJT software development 
> 
> *Subject:* Re: [wsjt-devel] Changes to the INSTALL file in the 2.2.2
> tarball
>
>
>
> Hi Bill and David,
>
>
>
> Could I find a source tarball which builds on Ubuntu 20.04?  I have
> several wsprdaemon sites which want to move to 20.02.
>
>
>
> My attempt to follow David's instructions have failed and I have so much
> other SW to work on that I don't want to reinvent the wheel.
>
>
>
> Thanks,
>
>
>
> Rob
>
>
>
> On Mon, Aug 3, 2020 at 4:55 AM Bill Somerville 
> wrote:
>
> Hi David,
>
>
>
> I am not ruling out portable packaging, I just don't think it should be
> the prime focus of a small and busy development team. If someone makes a
> portable package, commit to keep it up to date, and it gets some traction
> amongst Linux users of WSJT-X; then that's fine.
>
>
>
> I assume you realize that the WSJT-X CMake build script already knows how
> to make a basic Debian or RPM package, the package target does that if run
> on a suitable machine. You would be better to use a git checkout rather
> than the combined WSJT-X sources tarball with bundled Hamlib. Tha