Try the latest hamlib and see if that fixes the problem.
New hamlib for Windows installation directions#1 Shut down WSJTX#2 Download
either the 32-bit or 64-bit DLL -- hopefully your browser doesn't block it but
may warn you multiple times.If you can do a "Save As" you can save it directly
in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is
there.http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dllhttp://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll#3
If you don't save directly you need to open a file browser and move the file
that way.If you're not familiar with that here's a video on the file
browser.https://www.youtube.com/watch?v=AyVqCJrs9dk
Mike W9MDB
On Friday, November 12, 2021, 10:42:54 AM CST, Sam W2JDB <w2...@aol.com>
wrote:
Hi,
I don't know if this is a Hamlib problem or a WSJT-X problem.
I run a TS590S (Windows 10) and as you are aware I wrote my own logging/rig
control software.
When testing version 2.5.2 I noticed extraneous beeps from the TS590S
whenWSJT-X switches from RX to TX.
Using my software, I was able to determine that WSJT-X is sending extraneous
Split commands ("FT1;" and "FT0") as it switches from RX to TX.
The settings in WSJT-X is set to use CAT for PTT and SPLIT=RIG.There should be
no reason to send these extraneous commands once WSJT-X starts and sets the
TS590S into SPLIT.
If this process is a regression in the new version, then please disregard
thefollowing paragraph
If the process was used so as to ascertain/set which VFO is used for RX and/and
TX, it would have been much more efficient to use the "FR"/"FT" commands in
conjunction with the "FA"/"FB" commands as it would be a lot less wear and tear
on the relay in the rig.
73, Sam W2JDB
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
