Qlog and QRG control from the spots window

[dgleduc]

I am using QLog on Linux Mint qith Hamlib and Rigctl.
Changing the frequency from the Flex is ok on Qlog but when I click on a spot the frequency changes in Qlog but not on the Flex.
On the other hand QSSTV works ok, changing the band on QSSTV changes the band and frequency on the Flex.

The errors reported are:
No handler found on "power2mw"
No handler found on "short:l",KEYSPD
WRN Handler returned error error="strconv.ParseFloat: parsing "14080000,000000": invalid syntax" cmd=["short:F","14080000,000000"]
Looks like a command error.

Qlog 0.48.0
HamLib 4.7.0
nCAT-linux-amd64
nDAX-linu-amd64
Flex6400M

Any idea on how to correct this?

[foldynl]

And does QSSTV use Hamlib 4.7 ? Are you using QLog Flatpak or DEB package?

[dgleduc]

They both use the same Hamlib version. When I call a frequency change manually from rigctl it does work ok.

[foldynl]

I assume you are using flatpak. then try running qlog like this.

LC_NUMERIC=C flatpak run io.github.foldynl.QLog

It would also be useful to send a screenshot of the rig settings. There are several unusual things in your report that Qlog does not generate.

1. Qlog does not send a frequency. Hamlib does it.
2. Both apps, QLog and Hamlib, send the frequency value in Hz (without the decimal point).

[aa5sh]

I used a Flex 6400M for a while without issue - on my Mac. I'm curious how you have it setup so the screenshot would be helpful. I would use the 'Flex Slice A' rig with it directly talking the flex. I'd also love to see how you sending it successfully to RigCtl the format of the string your sending.

[dgleduc]

My stting, your code did work.

[foldynl]

Unfortunately, it seems that this is not a bug in QLog. The actual issue is that your locale is configured so that decimal numbers use a comma as the separator. QLog does not handle this, because the message sent to your nCAT is handled by Hamlib. QLog only requests Hamlib to set frequency; the message itself is formatted by Hamlib. It appears that Hamlib uses your locale settings.

However, nCAT written in Go is not locale-dependent, and based on the source code it likely does not handle this case. I do not know what led you to choose nCAT. At the moment, the only solution is to use the configuration I sent you.

[dgleduc]

I am new to Linux and use the settings I saw on different messages for the Flex6400M
Using a network address directly to the FLex does not seems to work this is why I am trying through nCat.
I would have prefered to talk directly to the Flex of course.
Using your code I get some errors (file attached)
Thank you for helping me so far.
F6DXE-connection-log.pdf

[aa5sh]

You should be able to talk directly to the flex with something like this:

You can use the same logic in other programs like WSJTX, as the Flex does allow multiple connections. No need for nCat or similar. Now this will not address any decimal separator issues if those exist.

[dgleduc]

Thank you, I am able to connect directly to the Flex.
I'll be doint test on the local setting option
Didier (Dick) F6DXE

[dgleduc]

Setup found, every thing is ok now. The commands from the spots are changing the Flex frequency an mode as expected.
I have been mislead by comments on using nCat and nDax to connect to the Flex.
Thank you for your help, much appreciated
Didier