wsjt-devel — WSJT software development

Re: [wsjt-devel] Linux Mint

[Christoph B. <my...@de...>]

Re: Doug Breault, Sr.
> Thanks. If I wait until the improved version is available, will I then not
> have to delete anything from my 2.7.0 wsjt-x? I'd like to keep 2.7.0
> working and untouched if possible. I need daily FT8 sustenance to stay
> alive.

The "wsjtx" and "wsjtx-improved" packages conflict with each other
because they install things into the same place. You can reinstall
either after uninstalling the other, though. Your config/logs/other
data in your home directory will stay untouched.

73,
Christoph DF7CB

[wsjt-devel] Linux windows resizing not available

[Marco C. <PY...@ou...>]

 Hello,

Noticed this on my Linux Opensuse Tumbleweed and would like to report that when starting WSJTX 3.0 as always I did so far with older versions, by adding "--style Fusion" as QT style definition of the window style, the submenu windows of settings are not resizeable, they stay always at their full size, difficulting to click on the buttons at the right bottom end, which are hidden by the desktop task bar.

TNX, PY1ZRJ, Marco

Inviato da Outlook per Android<https://aka.ms/AAb9ysg>

Re: [wsjt-devel] Linux Mint

[Doug B. Sr. <dou...@gm...>]

Thanks. If I wait until the improved version is available, will I then not
have to delete anything from my 2.7.0 wsjt-x? I'd like to keep 2.7.0
working and untouched if possible. I need daily FT8 sustenance to stay
alive.

On Wed, Sep 24, 2025 at 7:12 AM Christoph Berg via wsjt-devel <
wsj...@li...> wrote:

> > > Preparing to unpack .../wsjtx_3.0.0_improved_PLUS_250924_amd64.deb ...
> > > Unpacking wsjtx (3.0.0) ...
> > > dpkg: error processing archive
> > > /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb
> > > (--install):
> > >  trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is also
> > > in package wsjtx-data 2.7.0~rc3+repack-1build2
>
> You are mixing packages from different sources (upstream packaging for
> improved, Debian/Ubuntu packaging for 2.7.0). These have not been
> designed to work together, so you will have to remove the other one
> before installation.
>
> I haven't yet had the time to upload the new improved version to
> Debian, will do that soonish.
>
> Christoph
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] Linux Mint

[Christoph B. <my...@de...>]

> > Preparing to unpack .../wsjtx_3.0.0_improved_PLUS_250924_amd64.deb ...
> > Unpacking wsjtx (3.0.0) ...
> > dpkg: error processing archive
> > /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb
> > (--install):
> >  trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is also
> > in package wsjtx-data 2.7.0~rc3+repack-1build2

You are mixing packages from different sources (upstream packaging for
improved, Debian/Ubuntu packaging for 2.7.0). These have not been
designed to work together, so you will have to remove the other one
before installation.

I haven't yet had the time to upload the new improved version to
Debian, will do that soonish.

Christoph

Re: [wsjt-devel] Linux Mint

[Adrian <vk...@gm...>]

Copy > backup your logs to a another folder, then run ;

sudo apt purge wsjtx

try install again and restore logs.


73


vk4tux

On 24/9/25 19:45, Doug Breault, Sr. via wsjt-devel wrote:
> Hi All,
>
> Getting an error trying to install 3.0 on Mint
>
> (Reading database ...
> (Reading database ... 5%%
> (Reading database ... 10%%
> (Reading database ... 15%%
> (Reading database ... 20%%
> (Reading database ... 25%%
> (Reading database ... 30%%
> (Reading database ... 35%%
> (Reading database ... 40%%
> (Reading database ... 45%%
> (Reading database ... 50%%
> (Reading database ... 55%%
> (Reading database ... 60%%
> (Reading database ... 65%%
> (Reading database ... 70%%
> (Reading database ... 75%%
> (Reading database ... 80%%
> (Reading database ... 85%%
> (Reading database ... 90%%
> (Reading database ... 95%%
> (Reading database ... 100%%
> (Reading database ... 662932 files and directories currently installed.)
> Preparing to unpack .../wsjtx_3.0.0_improved_PLUS_250924_amd64.deb ...
> Unpacking wsjtx (3.0.0) ...
> dpkg: error processing archive 
> /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb 
> (--install):
>  trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is 
> also in package wsjtx-data 2.7.0~rc3+repack-1build2
> dpkg-deb (subprocess): decompressing archive 
> '/home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb' 
> (size=27241192) member 'data.tar': internal gzip write error: Broken pipe
> dpkg-deb: error: <decompress> subprocess returned error exit status 2
> dpkg-deb (subprocess): cannot copy archive member from 
> '/home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb' to 
> decompressor pipe: failed to write (Broken pipe)
> Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
> Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ...
> Processing triggers for mate-menus (1.26.1+mint1) ...
> Processing triggers for desktop-file-utils (0.27-2build1) ...
> Processing triggers for man-db (2.12.0-4build2) ...
> Errors were encountered while processing:
>  /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb
>
> uname -a
> Linux Squatch 6.8.0-79-generic #79-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 
> 12 14:42:46 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
>
> lsb_release -a
> No LSB modules are available.
> Distributor ID: Linuxmint
> Description: Linux Mint 22
> Release: 22
> Codename: wilma
>
> TNX
> KC1UUH Doug
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Linux Mint

[Doug B. <kv...@gm...>]

I have the same error on Linux Mint 22.2 codename Zara

Dougl KV4ZY

On Wed, Sep 24, 2025, 5:51 AM Doug Breault, Sr. via wsjt-devel <
wsj...@li...> wrote:

> Hi All,
>
> Getting an error trying to install 3.0 on Mint
>
> (Reading database ...
> (Reading database ... 5%%
> (Reading database ... 10%%
> (Reading database ... 15%%
> (Reading database ... 20%%
> (Reading database ... 25%%
> (Reading database ... 30%%
> (Reading database ... 35%%
> (Reading database ... 40%%
> (Reading database ... 45%%
> (Reading database ... 50%%
> (Reading database ... 55%%
> (Reading database ... 60%%
> (Reading database ... 65%%
> (Reading database ... 70%%
> (Reading database ... 75%%
> (Reading database ... 80%%
> (Reading database ... 85%%
> (Reading database ... 90%%
> (Reading database ... 95%%
> (Reading database ... 100%%
> (Reading database ... 662932 files and directories currently installed.)
> Preparing to unpack .../wsjtx_3.0.0_improved_PLUS_250924_amd64.deb ...
> Unpacking wsjtx (3.0.0) ...
> dpkg: error processing archive
> /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb (--install):
>  trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is also in
> package wsjtx-data 2.7.0~rc3+repack-1build2
> dpkg-deb (subprocess): decompressing archive
> '/home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb'
> (size=27241192) member 'data.tar': internal gzip write error: Broken pipe
> dpkg-deb: error: <decompress> subprocess returned error exit status 2
> dpkg-deb (subprocess): cannot copy archive member from
> '/home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb' to
> decompressor pipe: failed to write (Broken pipe)
> Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
> Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ...
> Processing triggers for mate-menus (1.26.1+mint1) ...
> Processing triggers for desktop-file-utils (0.27-2build1) ...
> Processing triggers for man-db (2.12.0-4build2) ...
> Errors were encountered while processing:
>  /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb
>
> uname -a
> Linux Squatch 6.8.0-79-generic #79-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 12
> 14:42:46 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
>
> lsb_release -a
> No LSB modules are available.
> Distributor ID: Linuxmint
> Description: Linux Mint 22
> Release: 22
> Codename: wilma
>
> TNX
> KC1UUH Doug
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

[wsjt-devel] Linux Mint

[Doug B. Sr. <dou...@gm...>]

Hi All,

Getting an error trying to install 3.0 on Mint

(Reading database ...
(Reading database ... 5%%
(Reading database ... 10%%
(Reading database ... 15%%
(Reading database ... 20%%
(Reading database ... 25%%
(Reading database ... 30%%
(Reading database ... 35%%
(Reading database ... 40%%
(Reading database ... 45%%
(Reading database ... 50%%
(Reading database ... 55%%
(Reading database ... 60%%
(Reading database ... 65%%
(Reading database ... 70%%
(Reading database ... 75%%
(Reading database ... 80%%
(Reading database ... 85%%
(Reading database ... 90%%
(Reading database ... 95%%
(Reading database ... 100%%
(Reading database ... 662932 files and directories currently installed.)
Preparing to unpack .../wsjtx_3.0.0_improved_PLUS_250924_amd64.deb ...
Unpacking wsjtx (3.0.0) ...
dpkg: error processing archive
/home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb (--install):
 trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is also in
package wsjtx-data 2.7.0~rc3+repack-1build2
dpkg-deb (subprocess): decompressing archive
'/home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb'
(size=27241192) member 'data.tar': internal gzip write error: Broken pipe
dpkg-deb: error: <decompress> subprocess returned error exit status 2
dpkg-deb (subprocess): cannot copy archive member from
'/home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb' to
decompressor pipe: failed to write (Broken pipe)
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ...
Processing triggers for mate-menus (1.26.1+mint1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for man-db (2.12.0-4build2) ...
Errors were encountered while processing:
 /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb

uname -a
Linux Squatch 6.8.0-79-generic #79-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 12
14:42:46 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a
No LSB modules are available.
Distributor ID: Linuxmint
Description: Linux Mint 22
Release: 22
Codename: wilma

TNX
KC1UUH Doug

[wsjt-devel] Request for WSJT-X.ini Refresh

[<n3...@ea...>]

Hello all, 

 

I'm new to this group list so I apologize if my following request is
misplaced or not proper.  I use my own logging software (Win-EQF) and it
interfaces nicely with WSJT-X in realtime, so my request is related to that
end.

 

It would be helpful if the WSJT-X.ini could be updated when BAND or MODE is
changed.  The existing [COMMON] parameters, DialFreq and Mode, if refreshed
when the program changes band or mode, would be useful.

 

Thank you in advance for any consideration.

 

73,

Tom N3EQF

 

Re: [wsjt-devel] WXSJT-X v 3.0.0-rc1 Watchdog tests

[Glenn W. <af...@al...>]

Further testing indicated that operation of 3.0.0-rc1 started with a 30 
second timeout (Settings->General->Behavior) used in months-old prior 
operation of 2.7.0-ga. The 6 second value for SuperHound is apparently a 
SH default that overrides the display only when the time has decremented 
to 2 minutes or below. A video is available.
--Glenn, AF8C


-- 
This email has been checked for viruses by Avast antivirus software.
www.avast.com

Re: [wsjt-devel] QMAP screen scaling in 3.0.0-rc

[DG2YCB <DG...@gm...>]

Hi Erik,

So far, HighDPI scaling has only been implemented in the wsjtx main 
program, not yet in QMAP.

73 de DG2YCB,
Uwe
_________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: DG...@gm...
Info: www.qrz.com/db/DG2YCB

Am 22. September 2025 17:27:00 schrieb Erik Icket via wsjt-devel 
<wsj...@li...>:

> Dear developers,
>
> In QMAP version "v0.5 250915 improved PLUS" the scaling of the frequency,
> date & time and Astro data fields is not done correctly when System ->
> Display -> Scale is set to 150%.
> Setting the scaling to 100% and all fields and widgets are correctly
> displayed.
>
> Also the version should probably read ... 250925
>
> This is a MINOR problem and happens on W11.
>
> Regards,
> Erik
> ON4PB
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] QMAP screen scaling in 3.0.0-rc

[Erik I. <run...@gm...>]

Dear developers,

In QMAP version "v0.5 250915 improved PLUS" the scaling of the frequency,
date & time and Astro data fields is not done correctly when System ->
Display -> Scale is set to 150%.
Setting the scaling to 100% and all fields and widgets are correctly
displayed.

Also the version should probably read ... 250925

This is a MINOR problem and happens on W11.

Regards,
Erik
ON4PB

Re: [wsjt-devel] WXSJT-X v 3.0.0-rc1 Watchdog tests

[Glenn W. <af...@al...>]

My ONLY message that I was sending was "E44OM AF8C EN81" with 
unsuccessful contacts using 3.0.0. I had a successful contact with E44OM 
on 10m with 2.7.0. So I was NOT criticizing SuperHound as defective, 
only the timer display in the right-hand corner.

My point was that the watchdog timer readout should not start at 30 
minutes, then in the middle suddenly decrement to 2 minutes, and have 
glitches (29,26) and so forth. The numbers should decrement smoothly 
from 5 or whatever is first, end up at 0 like it does, and without 
converting from "WD" to "HWD" (which I interpret to mean "Hound Watch 
Dog").  This leads me to worry about things like buffer sizes being 
wrong or pointer problems in the code. Code design should never have 
issues like that.

Also, other than all that readout glitching, the actual watchdog timing 
out and stopping transmissions worked fine.  Also I did not test with 
plain Hound or non-Hound operation. Maybe I should do that! I will let 
you know.

--Glenn, AF8C

On 9/22/2025 1:37 AM, Reino Talarmo via wsjt-devel wrote:
> Hi Glenn,
> 
> This is just educated guesswork about how the SuperHound
> may work.
> First, I assume that the same principle is applied to
> the SuperFox as in F/H protocol:
> 'Fox will respond to such "R+rpt" messages by sending
> "RR73" up to three times.'
> Secord, that should mean the Hound at maximum sends the
> "R+rpt" only three times and automatically stop after
> that. The change in the WD: may indicate an
> implementation of that feature. I have no idea which
> messages you were sending in your test as it may affect
> to the behavior.
> 
> 73, Reino OH3mA
> 
> 
> 
> 
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


-- 
This email has been checked for viruses by Avast antivirus software.
www.avast.com

[wsjt-devel] Fox/Hound behavior in 3.0.0-rc1

[Erik I. <run...@gm...>]

Dear developers,

I observed this odd F/H behavior this morning when working FP5KE :

1. When activating Hound, the "DX Call" turns yellow and "Enable TX" turns
yellow at the end of the watchdog timer, although 'Enable Wait features' are
disabled.
2. The hound calls the fox for a much longer period as before. In earlier
releases, the hound was calling 2-3 mins. In rel 3.0.0-rc1, the hound calls
as longs as the watchdog timer is not expired.

Note this is regular F/H and not Superfox mode, and "Enable Wait features"
are disabled.
Is this the correct behavior ?

Kind regards,
Erik
ON4PB

Re: [wsjt-devel] WXSJT-X v 3.0.0-rc1 Watchdog tests

[Kari S. <kai...@gm...>]

Hi Glenn,

This is by design.

"//To keep calling Fox, Hound must reactivate Enable Tx at least once 
every 2 minutes"

The "HWD" indicates that your timer is about to pop soon.

73's de Kari, oh2gqc


On 9/22/25 01:26, Glenn Williams via wsjt-devel wrote:
> Tests run after NIL results for QSO E44OM on 18095 this afternoon,
> ONLY while in SuperHound mode. I have run this multiple (10?) times
> into dummy load after the DX QRT'd.
>
> As opposed to the description in
> https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-3.0.0-rc1.html
> where the lower right corner display imaged as "WD:6m"
> I followed the watchdog timeout sequence during SuperHound as:
>
> Starting transmit:
> Text    WD background Color  "Enable TX" background Color
> WD:30m       White             Red
>
> After clicking "Enable TX" (each minute two Tx transmissions)
> Text    WD: background Color  "Enable TX" Color  Transition to next # on
> WD:30m       White             Red               End of 2nd Tx
> WD:29m       White             Red               End of 2nd Tx
> WD:28m       White             Red               End of 2nd Tx
> WD:27m       White             Red               Mid of Rx after 2 Tx
> HWD:2m       White             Red               Mid of Rx after 2 Tx
>                                    (sometimes flickers to WD:26)
> HWD:1m       Yellow            Red               Mid of Rx after 2 Tx
>                                    (sometimes flickers to WD:29)
> HWD:0m         Red               Yellow            halt
>
> --Glenn, AF8C
>
>
>

Re: [wsjt-devel] DXCC Filter

[Manuel O. <ct...@ho...>]

Dear Jim,

thank you.
Best 73

Manuel
CT1BZG
________________________________
De: Jim Brown via wsjt-devel <wsj...@li...>
Enviado: 22 de setembro de 2025 06:46
Para: wsj...@li... <wsj...@li...>
Cc: Jim Brown <k9...@au...>
Assunto: Re: [wsjt-devel] DXCC Filter

Hi Manuel,

There is an excellent free third-party software called JTAlert that
provides all sorts of alerts, by band. It's written by a ham in VK.
Google will find it.

73, Jim K9YC

On 9/21/2025 10:09 AM, Manuel Oliveira via wsjt-devel wrote:
> Dear coleagues,
>
> on this new version 3.0.0  how it is possible to show ONLY new DXCC on
> band messages on the Band Activity window? I know we can filter by the
> colours but still receive the other messages, would like to see ONLY the
> new DXCC on band.


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

Re: [wsjt-devel] DXCC Filter

[Jim B. <k9...@au...>]

Hi Manuel,

There is an excellent free third-party software called JTAlert that 
provides all sorts of alerts, by band. It's written by a ham in VK. 
Google will find it.

73, Jim K9YC

On 9/21/2025 10:09 AM, Manuel Oliveira via wsjt-devel wrote:
> Dear coleagues,
> 
> on this new version 3.0.0  how it is possible to show ONLY new DXCC on 
> band messages on the Band Activity window? I know we can filter by the 
> colours but still receive the other messages, would like to see ONLY the 
> new DXCC on band.

Re: [wsjt-devel] WXSJT-X v 3.0.0-rc1 Watchdog tests

[Reino T. <rei...@ko...>]

Hi Glenn,

This is just educated guesswork about how the SuperHound
may work. 
First, I assume that the same principle is applied to
the SuperFox as in F/H protocol: 
'Fox will respond to such "R+rpt" messages by sending
"RR73" up to three times.'
Secord, that should mean the Hound at maximum sends the
"R+rpt" only three times and automatically stop after
that. The change in the WD: may indicate an
implementation of that feature. I have no idea which
messages you were sending in your test as it may affect
to the behavior.

73, Reino OH3mA

[wsjt-devel] WXSJT-X v 3.0.0-rc1 Watchdog tests

[Glenn W. <af...@al...>]

Tests run after NIL results for QSO E44OM on 18095 this afternoon,
ONLY while in SuperHound mode. I have run this multiple (10?) times
into dummy load after the DX QRT'd.

As opposed to the description in
https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-3.0.0-rc1.html
where the lower right corner display imaged as "WD:6m"
I followed the watchdog timeout sequence during SuperHound as:

Starting transmit:
Text    WD background Color  "Enable TX" background Color
WD:30m       White             Red

After clicking "Enable TX" (each minute two Tx transmissions)
Text    WD: background Color  "Enable TX" Color  Transition to next # on
WD:30m       White             Red               End of 2nd Tx
WD:29m       White             Red               End of 2nd Tx
WD:28m       White             Red               End of 2nd Tx
WD:27m       White             Red               Mid of Rx after 2 Tx
HWD:2m       White             Red               Mid of Rx after 2 Tx
                                    (sometimes flickers to WD:26)
HWD:1m       Yellow            Red               Mid of Rx after 2 Tx
                                    (sometimes flickers to WD:29)
HWD:0m	     Red               Yellow            halt

--Glenn, AF8C



-- 
This email has been checked for viruses by Avast antivirus software.
www.avast.com

Re: [wsjt-devel] DXCC Filter

[Uwe, D. <dg...@gm...>]

Hi Manuel,

There is no such feature in v3.0.0, as our basic concept is primarily to 
highlight stations rather than hide them. However, if it's only a few 
DXCCs you are interested in, the following trick would work:

1. Hide stations from all continent:


2. Add the prefixes (or parts of it) you like to see to the Always Pass 
list, and activate "Apply filters only to the callsigns of the calling 
station":


For the example shown, the result looks like this:

73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg...@gm...
Info: www.qrz.com/db/DG2YCB


Am 21.09.2025 um 19:09 schrieb Manuel Oliveira via wsjt-devel:
> Dear coleagues,
>
> on this new version 3.0.0  how it is possible to show ONLY new DXCC on 
> band messages on the Band Activity window? I know we can filter by the 
> colours but still receive the other messages, would like to see ONLY 
> the new DXCC on band.
>
> Best 73,
> Manuel
> CT1BZG
>
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] DXCC Filter

[Manuel O. <ct...@ho...>]

Dear coleagues,

on this new version 3.0.0  how it is possible to show ONLY new DXCC on band messages on the Band Activity window? I know we can filter by the colours but still receive the other messages, would like to see ONLY the new DXCC on band.

Best 73,
Manuel
CT1BZG

Re: [wsjt-devel] when starting WSJT-X rig defaults to "ADAT www.adat.ch" and not the wanted rig

[Peter S. <vk...@gm...>]

Hello Arkadiusz,
 thanks for expanding on my original question, yes indeed the more I look
into HAMLIB the murkier it gets for us FLRIg users. If indeed WSJT-X was to
store the rig ID's instead of the display name it would be a great step
forward as I now count the entry for FLRig has changed over three times as
different HAMLIB developers submit changes, it started out as "FLRig flrig"
then the next one seems to be "FLRig " note the space at the end and then
"W1HKJ FLRig" then just in the last few weeks we are back to "FLRig flrig"

All of these hamlib variations stil pass through extra information (rig
type connected in FLRig) that WSJT-X appears to harvest and store, which
leads to uncertainty if WSJT-X will work at next startup or give me the oh
so common (for me anyway) rig control error and a need to reselect the rig
all over again.

If the HAMLIB ID was stored instead of the display name coming from HAMLIB
life would be a lot simpler in the long run as the code for HAMLIB seems to
be quite fluid and what was a good suggestion one week gets undone the
next, leaving us with "pot luck" if you update HAMLIB at any point.

I understand a rewrite of the way this is handled would not be a trivial
job but once done it would not need to be touched again.

Regards,
Peter, vk5pj

On Sun, Sep 21, 2025 at 6:40 AM Arkadiusz Miśkiewicz via wsjt-devel <
wsj...@li...> wrote:

> On 27/07/2025 03:18, Peter Sumner via wsjt-devel wrote:
> > Hi,
> >   for some time now (all of the 2.7 variants and now 2.8) when I open
> > WJST-X or swap between configurations, I end up with a rig control error
> > and the current rig is shown to be "ADAT www.adat.ch <http://
> > www.adat.ch>" and not the previously selected FLRIG setting.
>
> Old thread but...
>
> That's because wsjt-x remembers rig by name in config. Rig names come
> from hamlib library. Hamlib has stable rig IDs (number) but not names
> (string). Names can change.
>
> wsjt-x has few flaws regarding handling of its config file:
>
> - if wsjtx finds unknown rig in its config it won't tell anything to the
> user and it will instead use ADAT silently as ADAT is just first on the
> list (been there, was debugging why the hell my config stopped working
> and that issue wasn't obvious because I wasn't expecting silent changes)
>
> - it remembers rigs in config by name (which are not stable) instead of
> using IDs (which are stable in hamlib)
>
>
> and FLrig name has changed in hamlib recently. Twice. First from "FLRig"
> to "W1HKJ FLRig" and later to "FLRig FLRig".
>
>
> ps. wsjt-x should have search bar in rig config - it's a pain to find
> the right option there for fist time
>
> --
> Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] when starting WSJT-X rig defaults to "ADAT www.adat.ch" and not the wanted rig

[Arkadiusz M. <ar...@ma...>]

On 27/07/2025 03:18, Peter Sumner via wsjt-devel wrote:
> Hi,
>   for some time now (all of the 2.7 variants and now 2.8) when I open 
> WJST-X or swap between configurations, I end up with a rig control error 
> and the current rig is shown to be "ADAT www.adat.ch <http:// 
> www.adat.ch>" and not the previously selected FLRIG setting.

Old thread but...

That's because wsjt-x remembers rig by name in config. Rig names come 
from hamlib library. Hamlib has stable rig IDs (number) but not names 
(string). Names can change.

wsjt-x has few flaws regarding handling of its config file:

- if wsjtx finds unknown rig in its config it won't tell anything to the 
user and it will instead use ADAT silently as ADAT is just first on the 
list (been there, was debugging why the hell my config stopped working 
and that issue wasn't obvious because I wasn't expecting silent changes)

- it remembers rigs in config by name (which are not stable) instead of 
using IDs (which are stable in hamlib)


and FLrig name has changed in hamlib recently. Twice. First from "FLRig" 
to "W1HKJ FLRig" and later to "FLRig FLRig".


ps. wsjt-x should have search bar in rig config - it's a pain to find 
the right option there for fist time

-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

Re: [wsjt-devel] v3.0.0.0 rc 1 report

[Andy D. <a.d...@ms...>]

"It would be interesting to see whether the Diagnostic mode provides any meaningful difference between those two versions of wsjt-x in your system. 73, Reino OH3mA"

Reino,

Thanks for your interest.  Before we go any further I would like you to know that some time ago (April 2025) I reported a different compatibility problem with Win 8.1 and an "Improved" version of WSJ-X.  Members of that team spent several days with me trying to understand what was happening and never found a solution despite providing some custom diagnostic builds.

If I remember correctly the diagnostic logs for those test showed that WSJT-X thought it was commanding the required rig state but my rig did not change to the commanded state.  At that time, just like this time, there were no other Win 8.1 testers.

I had abandoned trying to use any "Improved" version later than 2.7.1 rc8 which runs fine at my station.  However, WSJT-X 3.0.0 rc1 is an "official" version not an "improved" version so I decided to try it.  Since I had tried it I was obligated to submit a test report.

I did attempt to capture diagnostic mode files for this specific 3.0.0 rc1 problem which is related only to rig keying.   Nothing jumps out at me.  Please send me a private email if you would like to look at them.  If any others are interested I will share via DropBox.

73,
Andy, k3wyc

Re: [wsjt-devel] v3.0.0.0 rc 1 report

[Reino T. <rei...@ko...>]

It would be interesting to see whether the Diagnostic
mode provides any meaningful difference between those
two versions of wsjt-x in your system. 

 

73, Reino OH3mA

 

From: Andy Durbin via wsjt-devel
<wsj...@li...> 
Sent: Saturday, September 20, 2025 2:00 PM
To: WSJT software development
<wsj...@li...>
Cc: Andy Durbin <a.d...@ms...>
Subject: Re: [wsjt-devel] v3.0.0.0 rc 1 report

 

"If looks like a Hamlib problem with your rig. I am
ruling out RFI. Do you know which versions of the Hamlib
you are using with wsjt-x versions."

 

I am not using Hamlib.  My TS-590S control is by
Omni-Rig 1.20.

 

You are correct that this is not an RFI issue.  The RF
environment does nor change when swapping between
different version of WSJT-X.  In any event there is no
RF if the rig is not keyed.

 

This is a compatibility issue with Win 8.1.

 

73,

Andy, k3wyc

 

  _____  

From: Andy Durbin <a.d...@ms...
<mailto:a.d...@ms...> >
Sent: Friday, September 19, 2025 4:38 PM
To: WSJT software development
<wsj...@li...
<mailto:wsj...@li...> >
Subject: Re: v3.0.0.0 rc 1 report 

 

"Sorry to hear that you had trouble using WSJT-X
3.0.0-rc1. You appear to be an outlier: well over 2500
people are using 3.0.0-rc1 with good results."

 

Joe,

 

I have no doubt this reported keying issue will only be
seen when using my exact test configuration.  That
requires Win 8.1. 

 

The last time I reported an issue with an "improved"
derivative of WSJX-X no other Win 8.1 user reported that
they had attempted to reproduce my result.   No one else
ran my test as specified so no one saw the reported test
failure.

 

I can completely understand if the team decides not to
support Win 8.1 but, unless someone else runs 3.0.0 rc1
with Win 8.1, I shall assume my test result is valid.
It is 100% repeatable as documented later in this email.

 

If someone reports the test works with Win 8.1 then
there would be the opportunity to look for any station
configuration differences and to attempt to isolate the
anomaly.   I have no idea why there are WSJT-X failure
modes with Win 8.1 that are not seen with other versions
of Windows.

 

I have no doubt that I could install 3.0.0 rc1 on one of
my Windows 11 computers and it would work properly but
my station computer runs Win 8.1.

 

So, what say all those 2,500 plus users of 3.0.0 rc1?
Anyone have a Win 8.1 computer and willing to run tests?


 

The reported issue is very easy to reproduce at my
station.  I installed 3.0.0 rc1 in a separate directory
from v2.7.1 rc8 devel.  I close 2.7.1 rc8 and open 3.0.0
rc1.  It starts normally.

 

I press main window Tune - Tune button goes red and
counter starts counting down.  My TS-590S is not keyed.

 

 I click Tune again before the counter expires,  The
button is no longer red.  I click it again with the same
result.

 

File /Settings / Radio - Test CAT gives green. Test PTT
keys my TS-590S. Clicking Test PTT again clears Test PTT
and the TS-590S in un-keyed.

 

Exit settings with Cancel.

 

Click Main window Tune.  Rig is keyed and modulated.

 

Click Tune again. Modulation stops but TS-590S remains
keyed

 

Click Tune again - rig remains keyed and becomes
modulated

 

Click Tune again  = modulation stops and rig remains
keyed. (Stopped keying with TS-590S front panel SEND to
force RX).

 

Exit 3.0.0 rc1 and run 2.7.1 rc8

 

Click Tune multiple times - Keying and modulation turn
on and off as expected.  

 

Nothing different in the test configurations excepts the
WJT-X version.

 

73,

Andy, k3wyc

 

 

Re: [wsjt-devel] Vertical colored lines in the Wide-Graph (v3.0.0-rc1)

[Ton P. <pa...@mu...>]

Hello Joe, Hisami,

Thank you so much for your help. I should have noticed that control but I
didn't.
Problem solved.

73
Ton PA0TBR

On Fri, 19 Sept 2025 at 23:27, Joseph Taylor <jo...@pr...> wrote:

> Hi Ton,
>
> ###
> How can I turn off the vertical (green & red) colored lines in the
> Wide-Graph?
>
> When trying to find a weak EME station in the waterfall these lines are
> very annoying.
> ###
>
> Uncheck the box labeled *Bars* at bottom left of the Wide Graph.
>
>  -- 73, Joe, K1JT
>