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 <jstengrev...@comcast.net>
Reply-To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Date: Saturday, March 6, 2021 at 8:15 AM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
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 <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 <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 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 <g4...@classdesign.com> 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"<mcqui...@sfu.ca>  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

Reply via email to