Locked Re: Trouble with Yaesu FT-747GX CAT #windows11 #Cat_RigControl #hamlib

Tordek <kedrot@...>

A bit of source digging later, I believe it's been caused by a change
between 2.3.1 and 2.4.0, where these lines were changed from:

#if defined (Q_OS_WIN)
std::locale::global (std::locale ("C"));
std::locale::global (std::locale ("en_US.UTF-8"));


// reset the C+ & C global locales to the classic C locale
std::locale::global (std::locale::classic ());

Versions up to 2.3.1 work correctly, and 2.4.0 exhibits the bug.
Unfortunately there isn't a 2.4.0-rc4-win64 available to try, which is
the latest tag before the change.

On Thu, 18 Aug 2022 at 09:27, Tordek <kedrot@...> wrote:

Since we both seem to be Spanish speakers, my brother offers a
thought... maybe there's a locale issue and it's parsing the wrong
decimal separator?

On Wed, 17 Aug 2022 at 16:00, Mauricio A. Taslik <mautas@...> wrote:

I confirm the error exactly as described. when it must read 7.000 MHz it
reads 7,000 MHz and that makes it impossible to use it. Keeps happening
since more than a year in all wsjtx versions until the last one I tried
some months ago, and it looks like it keeps happening. Quick "fix": use an
old versión from early 2019.

El mié, 17 ago 2022 a la(s) 13:45, Michael Black via groups.io (mdblack98=
yahoo.com@groups.io) escribió:

Please try this DLL....I just made a change that should help this....

And if it still is wrong (which it likely will be) please provide debug

New hamlib for installation directions

#1 Shut down WSJTX

Linux/Unix/Mac users need to compile the latest tar file from
Note: If compiling on Unix-like systems please uninstall any Hamlib
package you have before installing the new build

#2 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 -

Mike W9MDB

On Wednesday, August 17, 2022 at 12:47:55 AM CDT, kedrot@... <
kedrot@...> wrote:

I'm trying to setup CAT to control my rig; my settings are:

8 data bits
2 stop bits
no handshake
other pins on default

The Test CAT button works, it sets to green, and PTT also correctly starts

The issues:

When selecting a band from the dropdown, the rig is correctly set to the
appropriate frequency. A couple of seconds later, when the system polls the
current frequency, it's 100 times higher and it ends in 48. E.g.: 40m sets
to 7,074.000 Two seconds later, it becomes 707,400.048.

A few seconds later, I get a timeout error and the rig disconnects.

Any help is appreciated.

Join {main@WSJTX.groups.io to automatically receive all group messages.