I use
http://www.eterlogic.com/Products.VSPE.html
No need to register, and supports 4 CAT connections to the VCP using
splitter to real comport.
I use it with wsjtx, Commander , N1MM and MMTTY. for the last years with
no issue.
On 17/2/21 9:07 pm, Alex Artieda, HB9DRI wrote:
Hello Bill
I can omit to work with Omnirig BUT the IC-9700 config embedded in
WSJT-X have the same behavior that the PTT, only the 1^st WSJT-X
instance can manage, the only way to have SHARE CAT com port was using
Omnirig.
Regards
Alex, HB9DRI
*From:* Bill Somerville <g4...@classdesign.com>
*Sent:* Wednesday, February 17, 2021 5:20 PM
*To:* wsjt-devel@lists.sourceforge.net
*Subject:* Re: [wsjt-devel] FW: BUG in WSJT-X 2.3 and 2.4rc1 COM port
Hi Alex,
thanks for that.
OK, I now understand what is happening. The Hamlib configuration
overrides do not currently apply when using any form of CAT control
other than Hamlib, including via Omni-Rig. I will change that for the
next release.
Another option is not to use Omni-Rig, which may be dependent on other
applications you use. The Hamlib rigctld (which we ship a version of
with WSJT-X called rigctld-wsjtx) also supports the PTT sharing
configuration option.
73
Bill
G4WJS.
On 17/02/2021 08:07, Alex Artieda, HB9DRI wrote:
Hello Bill
Sorry but the file you send me is exact to the code propose by
Mike, the code is the same and I copied in ALL WSJT-X instances I
have and I cannot share the PTT port.
My config in Radio tab in ALL WSJT-X instances:
For RIG: I use Omni Rig 2 where CAT is configure over a separate
port, this works ok ( I never succeed to use the IC-9700 option in
WSJT-X)
For PTT: I use com port 2 RTS, that works good v2.2.2 or in 2.3
and 2.4rc1 if only one instance open the port
Mode: None
Split Operation: RIG
I don’t use CAT for PTT because I need to PTT first my sequencer,
then the sequencer PTT the radio as last event.
Alex, HB9DRI
*From:* Bill Somerville <g4...@classdesign.com>
<mailto:g4...@classdesign.com>
*Sent:* Tuesday, February 16, 2021 7:50 PM
*To:* wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>
*Subject:* Re: [wsjt-devel] FW: BUG in WSJT-X 2.3 and 2.4rc1 COM port
Hi Alex,
the file I sent was different from the text Mike suggested.
What settings are you using on the "Settings->Radio" tab of your
WSJT-X instances?
73
Bill
G4WJS.
On 16/02/2021 12:45, Alex Artieda, HB9DRI wrote:
Hello Bill
The file you send me has the same code send to me from the
beginning, I delete the file I create and I confirm your file
was installed into the log directory in each WSJT-X instance I
had, doesn’t work.
To confirm the problem I install in another computer two
WSJT-X and use your file and doesn’t work.
As you mention in one of your last emails you will back in the
next release to sharing the PTT port, something make totally
sense if you consider it was working ok in version 2.2.2.
Regards
Alex, HB9DRI
*From:* Bill Somerville <g4...@classdesign.com>
<mailto:g4...@classdesign.com>
*Sent:* Tuesday, February 16, 2021 5:31 PM
*To:* wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>
*Subject:* Re: [wsjt-devel] FW: BUG in WSJT-X 2.3 and 2.4rc1
COM port
Hi Alex,
the file I attached was the correct one. Others have used it
without issues. Please double check the file is correctly
named and has not been mangled by Windows in some way. Note
the file name must be hamlib_settings.json
73
Bill
G4WJS.
On 16/02/2021 04:29, Alex Artieda, HB9DRI wrote:
Hello Bill
Following your instructions I use your file (looks the
same as I use before) and I place in the properly log
directory for each of the WSJT-X (totally 4) and doesn’t
work, the PTT is not share.
I wonder why if in WSJT-X 2.2.2 the PTT com port was share
by default now is not?
Regards
Alex, HB9DRI
*From:* Bill Somerville <g4...@classdesign.com>
<mailto:g4...@classdesign.com>
*Sent:* Monday, February 15, 2021 6:29 PM
*To:* wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>
*Subject:* Re: [wsjt-devel] FW: BUG in WSJT-X 2.3 and
2.4rc1 COM port
Hi Alex,
try the attached file. It needs to go in the log files
directory of each WSJT-X instance ("Settings->File->Open
log directory").
73
Bill
G4WJS.
On 15/02/2021 05:41, Alex Artieda, HB9DRI wrote:
Hello Mike
Sorry I didn’t answer to the list;
I create a file named hamlib_settings.json and paste
inside the code you send me:
{
"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>
<mailto:wsjt-devel@lists.sourceforge.net>
*Sent:* Monday, February 15, 2021 11:11 AM
*To:* wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>
*Cc:* Black Michael <mdblac...@yahoo.com>
<mailto: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
On Sunday, February 14, 2021, 07:43:47 PM CST, Alex
Artieda, HB9DRI <hb9...@emeham.com
<mailto:hb9...@emeham.com>> wrote:
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
73 de Alex, HB9DRI
_______________________________________________
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
