Hi Taka,
I recommend you some systematic testing.
1. First, start just the instance which you use for your JT65B
transmissions. It should work without any problem.
2. Start your second instance (the other polarization level for JT65B).
See if it still works. (It should.)
3. Then start your other instances one after the other and check
whether it still works or not.
4. Once you have found out which instance breaks it, take a closer look
at its settings. First check whether you have really specified the "
--rig-name=InstanceNameXYZ" parameter correctly. If this is really
correct, check the other settings to see what is different from the
others.
I can confirm that it basically works if you control an audio port from
several instances. At least with my FT-991 it also works with WSJT-X and
JTDX next to each other (respectively with the 'improved' versions).
Or are you transmitting with both instances at the same time? I haven't
tried this yet, but I don't think it makes sense because the audio
signals are not time-synchronized.
Also consider whether you really need so many instances running at the
same time. As I wrote to you before, other OMs solve the problem with H
and V by simply having the QRGs of the two down converters slightly
different (e.g. 1 or 2 kHz apart) and then mixing the audio signals.
Then you can transmit and receive both polarization levels with one
WSJT-X instance. Because the more complex the setup, the more
error-prone it becomes.
73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de
Info: www.qrz.com/db/DG2YCB
Am 05.01.2024 um 13:44 schrieb JP3EXR via wsjt-devel:
Hi Uwe and the wsjt development team.
Thank you for supporting us with our JT65B problem.
I sent two emails about my situation.
Probably my settings is different from other stations.
I ask you the following question.
I have 6 icons and I have 6 folders under AppData Local of two JT65B
for H and V-pol, Q65A for H and V-pol and FT8 for H and V-pol of WSJT-X.
And I have 2 icons and I have 2 folders under AppData Local of two FT8
for H and V-pol of JTDX.
So I have their 8 folders under AppData Local, are those folders
causing trouble?
And I use the output all of the audio port are the same port as H and
V-pol for each WSJT and JTDX.
This is because I just use one side of TX which both IC-746pro.
Of course, I use it the same as WSJT-X and JTDX.
Is it okay to use the output audio port of the only one port to all of
the instances as share on one PC?
Taka, JP3EXR
*From:*Uwe, DG2YCB via wsjt-devel <wsjt-devel@lists.sourceforge.net>
*Sent:* Friday, January 5, 2024 7:44 PM
*To:* WSJT software development <wsjt-devel@lists.sourceforge.net>
*Cc:* Uwe, DG2YCB <dg2...@gmx.de>
*Subject:* Re: [wsjt-devel] I have in trouble JT65B of WSJT-X
Hi Taka, Larry, and all
I would really like to help you, but the error simply does not occur
on my PC. I have run numerous tests with two instances this morning.
Both with WSJT-X v2.6.1 and v2.7.0-rc3 and with wsjt-x_improved
v2.7.1-devel. I tested various settings (EME delay on/off, with FT-991
CAT control vs without (i.e. CAT = None), real transmission via
antenna vs virtual audio, and so on). Result: There was *not a single
case* where this error occurred. It always worked perfectly with
JT65B, and with the other modes. The decode button did not get stuck,
and I was also able to decode my own transmissions from the first
instance with the second one without any problems when using my
virtual audio cable. (Due to time constraints, I only tested the
latter for my 2.7.1-devel version).
Very important: The error that the second instance hangs after you
have transmitted with the first one (visible by the fact that the
Decode button remains cyan) always occurs if not both instances were
started with the " --rig-name=InstanceNameXYZ" parameter but only the
second one. In this case, the "zeroth" instance (that without the "
--rig-name..." parameter) shoots down all the others. So please make
sure once again that this is not the case. Perhaps caused by a
spelling mistake (" -rig-name..." instead of " --rig-name..." or
something like that).
73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de
Info: www.qrz.com/db/DG2YCB <http://www.qrz.com/db/DG2YCB>
Am 05.01.2024 um 04:19 schrieb Larry Davis via wsjt-devel:
i can run any of the other modes msk q65 but to try to run 2 jt65b
on the same computer one tx and one rxing the second one hang up
on decode you can run one all day long no problem i just stoped
running two version of jt65b
On Thursday, January 4, 2024 at 08:27:45 PM CST, Larry Davis via
wsjt-devel <wsjt-devel@lists.sourceforge.net>
<mailto:wsjt-devel@lists.sourceforge.net> wrote:
i don,t think it is a problem with the computer i ran into same
problem with 13900k 64 gb of ram with 2 wsjtx open on jt65b second
computer 14900k 64gb of ram same problem i just think it a bug
when you run 2 wsjtx the second one hang up on decodes
------------------------------------------------------------------------
*From:*JP3EXR via wsjt-devel <wsjt-devel@lists.sourceforge.net>
<mailto:wsjt-devel@lists.sourceforge.net>
*Sent:* Thursday, January 4, 2024 5:28 PM
*To:* 'Black Michael' <mdblac...@yahoo.com>
<mailto:mdblac...@yahoo.com>; wsjt-devel@lists.sourceforge.net
<wsjt-devel@lists.sourceforge.net>
<mailto:wsjt-devel@lists.sourceforge.net>
*Cc:* JP3EXR <exr0...@gmail.com> <mailto:exr0...@gmail.com>
*Subject:* Re: [wsjt-devel] I have in trouble JT65B of WSJT-X
Hi Mike W9MDB
Good morning from Japan.
Thank you for your cooperation.
Thank you for asked me about my current PC spec.
You are able to see the attached picture of my current PC
specification.
My current PC has 16GB memory and CPU has i7-4790K.
I used an older PC has 8GB memory and i5 CPU for WSJT-X.
I thought that my JT65B in problem was caused by the slow speed of
my old PC.
So I was thinking the same thing as Mike until November last year.
I thought I was able to solve my JT65B problem by replacing it
with the current faster PC.
Then I replaced my older PC to my current PC in November last year.
But unfortunately, my in problem with run two JT65B cannot be
resolved at this time.
I will test the advice you gave me yesterday on my WSJT PC today.
Then I will also email you of the test results.
Thank you
Taka, JP3EXR
-----Original Message-----
From: Black Michael <mdblac...@yahoo.com>
<mailto:mdblac...@yahoo.com>
Sent: Friday, January 5, 2024 2:40 AM
To: wsjt-devel@lists.sourceforge.net
Cc: JP3EXR <exr0...@gmail.com> <mailto:exr0...@gmail.com>
Subject: Re: [wsjt-devel] I have in trouble JT65B of WSJT-X
How much memory do you have in your computer?
Mike W9MDB
On Thursday, January 4, 2024 at 03:51:24 AM CST, JP3EXR via
wsjt-devel <wsjt-devel@lists.sourceforge.net>
<mailto:wsjt-devel@lists.sourceforge.net> wrote:
Hi wsjtx development team.
Thank you for helping me with my trouble.
Sorry I forgot to send you about my trouble situation.
Please check the two attached pictures.
I am sorry for the Japanese display on the two attached screens.
Both pictures run two JT65B of WSJT-X on my PC.
Then you know two JT65B were decoding every periods.
Please check the sample aa.
I turned on the Enable TX on the left side of two JT65B.
Then on the left side of two JT65B had TXing started at 0721.
The on the right side JT65B was decoding every periods even on the
left side of two JT65B had TXing started.
You can see the decoding time of the single pass decode on the
right side of JT65B.
The decoding process of JT65B on the right side became freezing
from 0721.
Please check the sample ca.
I turned on the Enable TX on the right side of two JT65B.
Then on the right side of two JT65B had TXing started.
Then The decoding process of JT65B on the left side is the same as
the sample a.
I am checking under what circumstances multiple JT65B are decoding
freeze.
I think two JT65B are decoding every periods if both JT65B does
not TX.
But JT65B of the TXing side does not decode in the TX period.
I think the decoding freeze of JT65B at the same periods of not TX
side of JT65B when TXing of JT65B finished of TXing period.
And the decoding freeze may occur immediately at the earliest, or
until about 10 TXing at the latest.
Please contact me if you need additional confirmation.
Best regard
Thank you
Taka, JP3EXR
_______________________________________________
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
