Date   

locked Re: Added complexity when transmitting while multiple WSJT-X instances are running on a station with a shared TX resource with 2.3.0-rc2

Bill Somerville
 

On 16/11/2020 05:18, Clint Turner wrote:
It would appear that a change between version <=2.3.0-rc1 and 2.3.0-rc2 has added a complexity to those who operate with multiple WSJT-X instances.

For example:

For years I have been operating on both the 2200 and 630 meter bands using both WSPR and JT-9 (now FST4) with multiple windows open, allowing simultaneous reception on these modes and bands, using the same computer - taking advantage of what was apparently a quirk.  I happen to use separate receivers and one common transmitter with transverter - as is commonly done on these and some other bands.  Because of the multiplicity of available modes offered by WSJT-X - particularly for these LF/MF bands, one almost has to have multiple instances running at the same time to capture what is going on.

Here's the rub:

Until 2.3.0-rc2, as long as you didn't try to transmit on more than one instance at once - or as long as you didn't try top bring up another instance while another was transmitting - they could all share the same COM port for PTT

As of 2.3.0-rc2, it seems as though that something is tying things up, signalling that the COM port is busy, even if nothing is being actively controlled:  Unlike previous versions, Even if none of the other instances are transmitting, one cannot transmit at all if any of the instances are configured with the same COM port.  What this now means is that one must conveniently go to Files->Settings->Radios->PTT Method->Port every $#!+ time I wish to switch transmit from one instance to another.

Prior to 2.3.0-rc2, there was no conflict as long as these two things were true:

  • One didn't attempt to transmit with two instances sharing the same COM port PTT method configuration at the same time.
  • One didn't start another instance using the same COM port PTT method configuration while another was transmitting.
Was this change intentional, or is it an artifact of a problem that might have needed to have been addressed?  Is there some other way in which one can share local radio resources with jumping through a whole bunch more hoops than before?

Whatever the cause, this change does add another layer of complexity when trying to use WSJT-X using shared radio resources.

73,
Clint, KA7OEI

P.S.  No, I'm not using CAT control.

Hi Clint,

this was a unilateral change by the Hamlib team, I did request that it not be made, or the new behaviour be optional, but was told nobody uses this feature :(

You can return to the previous behaviour by creating a file called hamlib_settings.json in the WSJT-X log files directory containing the following text:

{
    "config": {
    "ptt_share": "1"
    }
}

73
Bill
G4WJS.


locked Re: Unable to disable tx-1 and transmit tx 2 first in 2.3.0 rc2 #IssueReport

Bill Somerville
 

On 15/11/2020 21:10, AB8WD-Willie via groups.io wrote:
I used to be able to double click on tx 1 under now and bypass it rc-2 unable to do so.
Hi OM,

thanks for reporting this issue. I can confirm it is a regression, calls starting with two alphabetic characters are erroneously being categorized as non-standard when checking if eliding Tx1 messages is allowed. This defect is repaired for the next release.

73
Bill
G4WJS.


locked WSJT-x v 2.2.2 hamlib error

Jan Kappert
 

Since I had an olderversion installed, I upgraded with the version 2.2.2
After launching the program, I get a hamlib error referring to a problem with the rig.
I do not use a rig; only tx/rx switching.
When I look into the settings, I see I can select: Cat or USB.
In earlier versions I had to select a com port.
I use a labtop.
With WSJT-10 all works fine.

Whatever I do on the settings, I keep popping up the hamlib error.
How can I get rid of it?

Thanks in advance,

Jan, PAoPLY


locked Re: Unable to disable tx-1 and transmit tx 2 first in 2.3.0 rc2 #IssueReport

Dwight Bosselman <NS9I@...>
 

Same here.

73 Dwight NS9I

On 11/15/2020 3:10 PM, AB8WD-Willie via groups.io wrote:
I used to be able to double click on tx 1 under now and bypass it rc-2 unable to do so.



locked Re: Dependency Issues - Ubuntu Mate 20.04

Rick Chapman
 

Hi Bill

Yes, there was a missing dependency in the rc1 install which I didn't pick up, sorry about that.  I must have had that dependency installed already.  But you solved it anyway.  I've made a note of it.

I see your rc2 query has a response already, I haven't tried it yet but will this morning (on a proper clean install!).

73s

Rick(GM4JIB)

On 16/11/2020 02:09, Bill Carpenter wrote:
Hi Rick,

Thanks again for the help.  I uninstalled 2.3.0rc1 and installed 2.1.2 which works fine.  Used that for a couple of days until 2.3.0rc2 showed up today.  That installation failed so I decided to try installing 2.2.2 per your instructions.  That also failed until I uninstalled 2.1.2 via synaptic.  After that 2.2.2 installed fine and is working fine. I suspect there is a conflicting package or two and that may also be why the 2.3.0rc2 failed.  In the meantime I'll stay with 2.2.2 for now.

Thought you might want to know in case you run across anyone else with the same problem I had.

73, Bill NZ0T



locked Re: WSJT-X 2.3.0-rc2

Philip
 

Read the docs all working fine here.
Philip G7JUR


locked Good news rc2, FST4 welcome / Correction/ RE: [WSJTX] WSJT-X 2.3.0 rc1 Triple decode and crash.

Amos Sobel 4X4MF
 

Good news

 

On Oct 3,2020 I did give up rc1 because it had to many problems as listed below.

Yesterday I did bring up 2.3.0 rc2 and all the problems are gone. Good work Joe, Bill  and folks.

 

Now let’s come back to FTS4 on 160m. I am listening on 160m when it is active on my side, that is 03:00-05:00 UTC  and 19:00-22:00 UTC. From time to time I will switch to FST4 1839.000  Khz  and call CQ. You are all welcome to report and QSO.

 

Amos 4X4MF

=============================================================

 

 

Bill

 

This one:

 

 

How can I tell  you which  one when you do not give each panel a name or a number? Please do!

 

Amos 4X4MF

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: Saturday, October 3, 2020 2:48 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] WSJT-X 2.3.0 rc1 Triple decode and crash.

 

Amos,

 

you mention "Rig Control Error" twice below, neither time did you include the details of the error message. There many tens of different rig control errors, unless you tell me which one we cannot proceed.

 

73
Bil
G4WJS.

 

On 03/10/2020 07:59, Amos Sobel 4X4MF wrote:

Bill

 

I will try to elaborate the case for our common purpose:

1. I am using Flex 6600 and 4 instances of WSJT-X and JTAlert. Win10 2004 and I7 computer.

2.4O7CC did not come again yesterday  so I was not able to dig into that case.

3. During my calling to 4O7CC I did loose TX few times. I had to start “Enable Tx” again and again.

4. I did also lose Radio connection, that is, panel “Rig control Error” did appear and I had to renew the connection.

5. Yesterday I did notice that when I switch frequencies by way of changing SmartSDR profiles, rc1 does show “Rig control Error” most of the times for 1-3 instances.

6. Re-installing WSJT-X 2.2.2 does eliminate the problem.

7. Installing rc1 does bring the problem again.

 

I hope this does help. Do not hesitated to contact me again.

 

Amos 4X4MF

 

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: Friday, October 2, 2020 2:40 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] WSJT-X 2.3.0 rc1 Triple decode and crash.

 

Amos,

 

we release WSJT-X release candidates (RC) in advance of a full general availability (GA) release so we can all benefit from some extra testing by those who choose to help. That early access and help comes with an obligation to report issues with enough information to allow the development team to fix any defects. With that in mind please answer the following questions:

  • What rig are you using?
  • How is it connected to your PC for audio and rig control of PTT and frequency.
  • Please be more specific about "crash", did the application simply disappear from your screen without warning? Was there any error message, if so what did it say, including details?
  • Please be more specific about "repeatedly disconnect from the radio", how was that behaviour indicated? Was there any error message, if so what did it say, including details? Did the "disconnection" occur at a particular action by you or the program while progressing through a QSO?

Any other information that might help to reproduce this issue would be welcome too.

 

73
Bill
G4WJS.

 

On 02/10/2020 07:13, Amos Sobel 4X4MF wrote:

Reino my friend

 

  1. Thank you for the explanation.
  2. Calling 4O7CC made my rc1 crash. First it did stop calling and later it did repeatedly  disconnect from the radio. Reinstalling rc1 did repair the situation.
  3. 4O7CC did not answer my calls yesterday. I did call other 160 FT8 stations today. If 4O7CC come back today, I will call it and see if it makes rc1 crash again.

 

Amos  4X4MF

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Reino Talarmo
Sent: Friday, October 2, 2020 8:01 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] WSJT-X 2.3.0 rc1 Triple

 

Hi Amos,

4O7CC used a multifrequency derivate of wsjt-x program. The TX frequency separation is 60 Hz. It is not same as a Fox station and can be worked using normal FT8. They are using at least one special looking message, which contains TU to one station and a report to another station. As far as I have understood they are not expecting  a 73 from you at all.

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Amos Sobel 4X4MF
Sent: 1. lokakuuta 2020 23:18
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] WSJT-X 2.3.0 rc1 Triple

 

Bill

 

My rc1 WSJT-X does show triple decode of the same station on 160mFT8  as in the attached snip.

How come?

 

Amos 4X4MF

 


locked Good news rc2, FST4 welcome, RE: [WSJTX] WSJT-X 2.3.0 rc1 Triple decode and crash.

Amos Sobel 4X4MF
 

Good news

 

On Oct 3,2020 I did give up rc1 because it had to many problems as listed below.

Yesterday I did bring up 2.3.0 rc2 and all the problems are gone. Good work Joe, Bill  and folks.

 

Now let’s come back to FTS4 on 160m. I am listening on 160m when it is active on my side, that is 03:00-05:00 UTC  and 19:00-23:00 UTC. From time to time I will switch to FST4 1839.000  Khz  and call CQ. You are all welcome to report and QSO.

 

Amos 4X4MF

=============================================================

 

 

Bill

 

This one:

 

 

How can I tell  you which  one when you do not give each panel a name or a number? Please do!

 

Amos 4X4MF

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: Saturday, October 3, 2020 2:48 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] WSJT-X 2.3.0 rc1 Triple decode and crash.

 

Amos,

 

you mention "Rig Control Error" twice below, neither time did you include the details of the error message. There many tens of different rig control errors, unless you tell me which one we cannot proceed.

 

73
Bil
G4WJS.

 

On 03/10/2020 07:59, Amos Sobel 4X4MF wrote:

Bill

 

I will try to elaborate the case for our common purpose:

1. I am using Flex 6600 and 4 instances of WSJT-X and JTAlert. Win10 2004 and I7 computer.

2.4O7CC did not come again yesterday  so I was not able to dig into that case.

3. During my calling to 4O7CC I did loose TX few times. I had to start “Enable Tx” again and again.

4. I did also lose Radio connection, that is, panel “Rig control Error” did appear and I had to renew the connection.

5. Yesterday I did notice that when I switch frequencies by way of changing SmartSDR profiles, rc1 does show “Rig control Error” most of the times for 1-3 instances.

6. Re-installing WSJT-X 2.2.2 does eliminate the problem.

7. Installing rc1 does bring the problem again.

 

I hope this does help. Do not hesitated to contact me again.

 

Amos 4X4MF

 

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Bill Somerville
Sent: Friday, October 2, 2020 2:40 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] WSJT-X 2.3.0 rc1 Triple decode and crash.

 

Amos,

 

we release WSJT-X release candidates (RC) in advance of a full general availability (GA) release so we can all benefit from some extra testing by those who choose to help. That early access and help comes with an obligation to report issues with enough information to allow the development team to fix any defects. With that in mind please answer the following questions:

  • What rig are you using?
  • How is it connected to your PC for audio and rig control of PTT and frequency.
  • Please be more specific about "crash", did the application simply disappear from your screen without warning? Was there any error message, if so what did it say, including details?
  • Please be more specific about "repeatedly disconnect from the radio", how was that behaviour indicated? Was there any error message, if so what did it say, including details? Did the "disconnection" occur at a particular action by you or the program while progressing through a QSO?

Any other information that might help to reproduce this issue would be welcome too.

 

73
Bill
G4WJS.

 

On 02/10/2020 07:13, Amos Sobel 4X4MF wrote:

Reino my friend

 

  1. Thank you for the explanation.
  2. Calling 4O7CC made my rc1 crash. First it did stop calling and later it did repeatedly  disconnect from the radio. Reinstalling rc1 did repair the situation.
  3. 4O7CC did not answer my calls yesterday. I did call other 160 FT8 stations today. If 4O7CC come back today, I will call it and see if it makes rc1 crash again.

 

Amos  4X4MF

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Reino Talarmo
Sent: Friday, October 2, 2020 8:01 AM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] WSJT-X 2.3.0 rc1 Triple

 

Hi Amos,

4O7CC used a multifrequency derivate of wsjt-x program. The TX frequency separation is 60 Hz. It is not same as a Fox station and can be worked using normal FT8. They are using at least one special looking message, which contains TU to one station and a report to another station. As far as I have understood they are not expecting  a 73 from you at all.

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Amos Sobel 4X4MF
Sent: 1. lokakuuta 2020 23:18
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] WSJT-X 2.3.0 rc1 Triple

 

Bill

 

My rc1 WSJT-X does show triple decode of the same station on 160mFT8  as in the attached snip.

How come?

 

Amos 4X4MF

 


locked Added complexity when transmitting while multiple WSJT-X instances are running on a station with a shared TX resource with 2.3.0-rc2

Clint Turner
 

It would appear that a change between version <=2.3.0-rc1 and 2.3.0-rc2 has added a complexity to those who operate with multiple WSJT-X instances.

For example:

For years I have been operating on both the 2200 and 630 meter bands using both WSPR and JT-9 (now FST4) with multiple windows open, allowing simultaneous reception on these modes and bands, using the same computer - taking advantage of what was apparently a quirk.  I happen to use separate receivers and one common transmitter with transverter - as is commonly done on these and some other bands.  Because of the multiplicity of available modes offered by WSJT-X - particularly for these LF/MF bands, one almost has to have multiple instances running at the same time to capture what is going on.

Here's the rub:

Until 2.3.0-rc2, as long as you didn't try to transmit on more than one instance at once - or as long as you didn't try top bring up another instance while another was transmitting - they could all share the same COM port for PTT

As of 2.3.0-rc2, it seems as though that something is tying things up, signalling that the COM port is busy, even if nothing is being actively controlled:  Unlike previous versions, Even if none of the other instances are transmitting, one cannot transmit at all if any of the instances are configured with the same COM port.  What this now means is that one must conveniently go to Files->Settings->Radios->PTT Method->Port every $#!+ time I wish to switch transmit from one instance to another.

Prior to 2.3.0-rc2, there was no conflict as long as these two things were true:

  • One didn't attempt to transmit with two instances sharing the same COM port PTT method configuration at the same time.
  • One didn't start another instance using the same COM port PTT method configuration while another was transmitting.
Was this change intentional, or is it an artifact of a problem that might have needed to have been addressed?  Is there some other way in which one can share local radio resources with jumping through a whole bunch more hoops than before?

Whatever the cause, this change does add another layer of complexity when trying to use WSJT-X using shared radio resources.

73,
Clint, KA7OEI

P.S.  No, I'm not using CAT control.


locked Re: Dependency Issues - Ubuntu Mate 20.04

Bill Carpenter
 

Hi Rick,

Thanks again for the help.  I uninstalled 2.3.0rc1 and installed 2.1.2 which works fine.  Used that for a couple of days until 2.3.0rc2 showed up today.  That installation failed so I decided to try installing 2.2.2 per your instructions.  That also failed until I uninstalled 2.1.2 via synaptic.  After that 2.2.2 installed fine and is working fine. I suspect there is a conflicting package or two and that may also be why the 2.3.0rc2 failed.  In the meantime I'll stay with 2.2.2 for now.

Thought you might want to know in case you run across anyone else with the same problem I had.

73, Bill NZ0T


locked Re: v2.3 rc2 will not install

Bill Somerville
 

On 16/11/2020 01:28, Bill Carpenter wrote:
Just tried to install v2.3 rc2 Linux 64 bit for 20.04 (Mint 20) and installation failed saying a package would not install though I don't know which one.  I installed the rc1 and ran it for a couple of weeks with no trouble.  Uninstalled it and ran v 2.1.2 (no package for 20.04 2.2.2) the last couple of days which is working fine.  So not sure why rc2 won't install.

73, Bill NZ0T

Hi Bill,

there is a new prerequisite you must install:

sudo apt-get install libboost-all-dev

I would not normally recommend installing a development package when you only need the run-time libraries, but in this case the library packages are rather awkwardly named.

73
Bill
G4WJS.


locked v2.3 rc2 will not install

Bill Carpenter
 

Just tried to install v2.3 rc2 Linux 64 bit for 20.04 (Mint 20) and installation failed saying a package would not install though I don't know which one.  I installed the rc1 and ran it for a couple of weeks with no trouble.  Uninstalled it and ran v 2.1.2 (no package for 20.04 2.2.2) the last couple of days which is working fine.  So not sure why rc2 won't install.

73, Bill NZ0T


locked Re: Unable to disable tx-1 and transmit tx 2 first in 2.3.0 rc2 #IssueReport

Jim Shorney
 

I can confirm that it does the same here, with standard call signs. TX4 double-click action works as expected.

73

-Jim
NU0C


On Sun, 15 Nov 2020 21:14:58 +0000
"Bill Somerville" <g4wjs@...> wrote:

On 15/11/2020 21:10, AB8WD-Willie via groups.io wrote:
I used to be able to double click on tx 1 under now and bypass it rc-2
unable to do so.
Hi OM,

what callsign are you using?

73
Bill
G4WJS.


locked Congratulations and maybe one build defect

The Hempsteads
 

Hi everyone,
   I'm new here, and just built wsjtx and jtsdk from scratch on windows.

FIrst of all, congratulations and thanks to the entire team.  While it did take me some time to find the correct instruction page (I started with JTSDK, and should have started with JTSDK-64) which caused some frustration, once I was on the right instructions page, nearly everything went smoothly.  Being a software developer by profession, I understand the magnitude of this task.   Well done!

I may have found one defect.  When I went to build wsjtx, it could not find cmake.  I found in the jtsdk64.cmd file it put the path to cmake as "..../Bin"  with a capital B on bin.   once I change that to a lower case B it worked fine.

I did then go back and do a git clone of version 2.2.2, as I'm not ready to play with release candidates.

Again,  Thank you, and excellent work.

Dave Hempstead
WA1RCT


locked Re: WSJT-X 2.3.0-rc2

Jeff Stillinger
 

FYI - No action required at this time...

[kb6ibb@KB6IBB-15 wsjtx-build]$ ./wsjtx --style="fusion"
[2020-11-15 11:09:18.529975] [0x00007f4feed9bc80] [info] Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.

(wsjtx:29925): Gtk-WARNING **: 11:09:18.590: Theme parsing error: gtk-contained.css:4703:12: not a number

(wsjtx:29925): Gtk-WARNING **: 11:09:18.591: Theme parsing error: gtk-contained.css:4703:12: Expected a string.

=========================

NAME="Oracle Linux Server"
VERSION="8.3"
ID="ol"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="8.3"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Oracle Linux Server 8.3"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:oracle:linux:8:3:server"
HOME_URL="https://linux.oracle.com/"
BUG_REPORT_URL="https://bugzilla.oracle.com/"

ORACLE_BUGZILLA_PRODUCT="Oracle Linux 8"
ORACLE_BUGZILLA_PRODUCT_VERSION=8.3
ORACLE_SUPPORT_PRODUCT="Oracle Linux"
ORACLE_SUPPORT_PRODUCT_VERSION=8.3


locked VU Meter pops up on xmit.

Doug Bates - WB4JPG
 

Hello All,

I'm running Window's 10 Pro and been using WSIT-X for several years.  Recently when I transmit (FT8) a VU meter pops up on the Desk Top.  That's not a big deal, but besides being annoying it changes the level of my speakers if I'm listening to something.

I've searched a bit online, but have not discovered anything so I'm reaching out to the group.

How do I remove the VU meter and how to keep WSIT-X from changing my speaker volume?

Doug
WB4JPG   


locked Re: FT-847 to amplifier cable or connector

Neil Foster
 

  John,
I have a 5 pin Mini DIN and will be glad to send you the connector for the cost of shipping only. I can also make a cable for you as a gift. I am guessing that the amp uses an RCA connector on the amp end?
73 and stay well
Neil  N4FN
Marietta GA


locked Re: Unable to disable tx-1 and transmit tx 2 first in 2.3.0 rc2 #IssueReport

AB8WD-Willie
 

AB8WD
7Q7RU  AB8WD EN72  EXAMPLE


locked Re: FT-847 to amplifier cable or connector

Paul Selwood G3YDY
 

When I had an FT847 I purchased Mini Din Connectors and made up leads as appropiate. 
Much cheaper than buying the dedicated lead.
Good Luck
73
Paul
G3YDY 


locked Re: Unable to disable tx-1 and transmit tx 2 first in 2.3.0 rc2 #IssueReport

Bill Somerville
 

On 15/11/2020 21:10, AB8WD-Willie via groups.io wrote:
I used to be able to double click on tx 1 under now and bypass it rc-2 unable to do so.
Hi OM,

what callsign are you using?

73
Bill
G4WJS.

17241 - 17260 of 35492