Re: [wsjt-devel] FW: BUG in WSJT-X 2.3 and 2.4rc1 COM port

[Bill Somerville]

Hi Alex,




73
Bill
G4WJS.

On 15/02/2021 05:41, Alex Artieda, HB9DRI wrote:

try the attached file. It needs to go in the log files directory of each WSJT-X instance ("Settings->File->Open log directory").

Hello Mike

Sorry I didn’t answer to the list;



{

   "config": {

          "ptt_share": 1

   }

}

Then placethis file in C:\Users\[username]\AppData\Local\WSJT-X and in

Each of the 4 WSJT-X folders but doesn’t work,

Alex, HB9DRI

*From:* Black Michael via wsjt-devel <wsjt-devel@lists.sourceforge.net>
*Sent:* Monday, February 15, 2021 11:11 AM
*To:* wsjt-devel@lists.sourceforge.net
*Cc:* Black Michael <mdblac...@yahoo.com>
*Subject:* Re: [wsjt-devel] FW: BUG in WSJT-X 2.3 and 2.4rc1 COM port

The PTT port is no longer shareable by default.

Place this file in C:\Users\[username]\AppData\Local\WSJT-X

{

   "config": {

          "ptt_share": 1

   }

}

Mike W9MDB

I create a file named hamlib_settings.json and paste inside the code you send me: On Sunday, February 14, 2021, 07:43:47 PM CST, Alex Artieda, HB9DRI <hb9...@emeham.com <mailto:hb9...@emeham.com>> wrote:

73 de Alex, HB9DRI

Just to inform you, I found a bug regarding COM port for PTT, it appears in WSJT-X 2.3 and in 2.4 RC1, let me explain. I run 4 WSJT-X at the same time, I use Omnirig to control my IC9700 but PTT is manage via a COM port, this is a must for me to TX first a Sequencer via the COM port and later TX the radio, I cannot use CAT for PTT,  that guarantee me no RF spikes etc. 4 WSJT-X plus MAP65 plus WSJT10 are all configure to use COM3 for PTT, in this configuration I can TX with ANY of the 6 programs, more precise I can TX with the program were the decodes or best decode happens, unfortunate since WSJT-X 2.3 and 2.4RC1 I can TX ONLY with the FIRST program who opens the PTT COM port, the other ones don’t work and MAP65 give a opening COM port ERROR, the other WSJT-X simple don’t TX, would be great to fix this bug because when you run multiple WSJT-X is a must to work with all instance capable of TX, WSJT-X 2.2.2 works perfect. To confirm this bug I roll back to 2.2.2 and install 2.3 and later 2.4RC1, the bug appear in 2.3

hamlib_settings.json
Description: application/json

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