Q-LOG for Linux and WF client

1

Howdy, im running remote (WF c <----> WF s )

I’m trying to configure QLog (logging program for Linux) on the client side. It has a way to pull Frequency and Band data from radio via the Hamlib library. For that I say to “Use Network” and “Use Port 4532” .

What should I do on the WF client to get it to work. Or does this need to happen at the WF Server

Note: there is a field for “Host” which for now I’m using 127.0.0.1 in hopes that the WF client can supply the data. Otherwise I can point this software to the host running the WF Server instead.

thanks!!!

Dan
W6DKW

2

Hi Dan,

Connect QLog to wfview on the client side. Make sure the hamlib port is the same on both sides. wfview defaults to 4533 and QLog defaults to 4532, so you will need to change one port to make them match. With wfview, after modifying the port, uncheck and re-check the rigctl checkbox just to make sure, and also press Save Settings.

If you are using wfview version 1.64 on the client side, there may be some rigctl commands lacking, but it should be enough for basic operation with QLog.

If you are running linux, you might want to consider using our build script with “creator-widgets” as the first argument. This will let you build and test version 2 (well, 1.91 actually), which has greatly enhanced code for handling rigctl connections.

–E
de W6EL

qlogconnect
qlogconnect1342×808 105 KB

3

Elliott
thanks for the info. much appreciated.

dan
W6DKW

4

Elliott

No joy. Does this require the HamLib installation? Or is WF client starting its own rigctld server?

For client im running 1.65

Dan

5

wfview has a compatible hamlib server inside it.

Make sure you have typed everything correctly. Save settings and restart wfview. Examine the log after wfview starts, then start QLog and see if you see it connect.

6

Elliott

I think it may be a QLOG problem. Because I can see in WF log that the rigctld service is started on port 4532.
image

I can verify a port is open with… netstat -a

And I can use netcat in a terminal and specify the port like so:
nc 127.0.0.1 4532

next, I can see in WF log that a connection is made.

And when I type “FREQ” into netcat, the WF log reports: "Unimplemented command 'FREQ' " (lol, I dont know the rigctl commands, I just wanted to be sure netcat and WF were actually communicating. And they are.)

so its gotta be an issue within QLOG.

This is the version. is it the same as yours? Mine is from a flatpack thru the “Software Center” in Ubuntu 22

image

7

If you think it is a QLog problem, send a bug report to the author on GitHub https://github.com/foldynl/QLog

73 de LB2EG Richard

8

Do you see any commands in the wfview log when QLog is (supposed to be) connecting? If not, then it is most likely a configuration issue with QLog.

wfview only implements a subset of the hamlib rigctld commands, so it is possible that QLog is using an unsupported command.

9

Hello
Qlog and Wfview(1.64) are working fine.
my steps.
Qlog radio settings

image
image737×605 25.6 KB

Connect to the radio.
image

DE JG3HLX syuu

1 Like
10

flatpak version of QLOG or did you build/install from github ?

11

Hello

Operational environment
OS Ubuntu Desktop 24.04 LTS
Build with wfview fullbuild-wfview.sh
Qlog DEB packages ppa:foldyna/qlog

If the wireless device connection fails, an error message will be displayed.
What is the content?

DE JG3HLX syuu

12

ok Finally got it working. I’m not sure what I was doing wrong but I got rid of the flatpak version and tried to match Nakao’s setup. I did the PPA install and the reconfigured the QLOG and it started working for me. So a VFO change on the rig is showing up in QLOG and a change in QLOG shows up in the VFO

Now I’m trying to setup QRZ lookups and also log service.