The world's best linux logging program!

You are here

Rigcontrol not working

Rig is an FT1000-MP and using a USB to Serial therefore the device is /dev/ttyUSB0. The serial parameters are correct. The port default is 4532. The program is not communicating with the radio. What am I missing here? No idea how to check the Ubuntu 16.04 port the radio is actually connected to in Settings.

CQRLOG was downloaded from Petr's PPA.

New to Linux how do I check the port and if the drivers are working for the usb/serial?
73
john

We need to test that rigctld is there and is able to run.
In terminal, write /usr/bin/rigctld
rigctld is a daemon (a process running in the background) and shows no terminal output if is run in so simple way.

To verify that rigctld can be run you need another terminal instance (ie. you will have TWO terminals running simultaneously). Open the terminal again and run ps aux. rigctld must be there as the attached image shows.

This will verify if your rigctld is functional.

In the next step we will investigate why rigctld does not start up if you start CQRlog and the appropriate option in Preferences is checked.

When you get prompt "Rig command:" (if you get it. Otherwise you get reason why it does not start)
Then give letter f and enter.
You should get current rig frquency.
giving q enter stops the rigctl and you get command prompt back.

Rig command: q
rig_close called
port_close called
ser_close called
rig_cleanup called
icom_cleanup called
[saku@hamtpad ~]$

When rigctl does what you want you may try rigctld with same parameters (from console adding just one parameter more: -t 4352)
If it starts ok you can try cqrlog with same settings (without extra parameter -vvvvv)

your setup seems promising. The main problem is to find the right radio type and the port. From previous dumps it seems to be USB0 but with the proper radio type can't help (never had any Yaesu). Try radio type 103, 104, 124 or 125. Set the poll rate to 500, this is an very acceptable value. The port comm parameters are usually:

Thank you Martin and Saku. This has been and will continue to be a great learning experience for me. At times it was frustrating but thanks to the both of you much knowledge has been gained not only about this fine program but Linux in general.

As I turn the vfo dial cqrlog's qso frequency window now tracks but have an issue clicking on a spot in the dx cluster window. The call is entered but the mode and frequency takes anywhere from 2-5 minutes for the to change and many times an inaccurate call and frequency results. Polling is set to 500.

From preferences/TRXControl
- drop the pollrate. 500ms might be to fast if your rig uses 4800baud as Martin suspected. Try with 1000 or 1500 (1-1,5sec) it is still fast enough.

If that does not help you have to dig out why rig does not move. Long time, as you said 2-5min (!!!), looks like communication error between rig and rigctld that would explain wrong frequency (but not wrong callsign).

To find the reason drop the poll rate (just for testing period) to 5000. Then uncheck "Run rigctld at program start" .
Open console and give command:

Now rigctld should run in your console window. Start cqrlog now. As you unchecked "run rigctld at program start" cqrlog will not start another rigctld, but uses this one running in you console.

When cqrlog is up you will see from console what happens when it polls rig on every 5000 (5sec). At that point double click DXcluster line to make your TX move to DX's frequency.
Look what happens at console window. Any errors seen then???

You can scroll console lines, and also kill rigctld with Ctrl+C to stop polling fill up then console window.
If you kill rigctld like that you can restart it using "arrow up" key that brings you the last typed command and pressing enter after that.
How ever cqrlog does not work after that until you use NewQSO/File/Refresh TRX/ROT control.

When you have finished with testing remember to return poll rate and "Run rigctld at program start" from Preferences/TRXcontrol.

Saku
I dropped the poll rate to 1500 and that corrected the issue. All is working well now.
Next week I am going to read and reread back over this entire series of replies and redo the commands to learn from this. This is great insight into the inner workings of Linux and cqrlog.

Now I have a similar problem to John. I had everything working with a fresh install on Linux Mint 18.3. I had the radio and PC talking and I could read the radio frequency in CQRLog. Then I tried installing fldigi using Package Manager. I was able to install the program but could not get it to talk to the radio, no matter what I tried.

Radio Yaseu FT-1000D (rig 103)

I quit out of fldigi and decided to run CQRLog and get on the air to make a few contacts. To my sadness, now CQRLog won't read the radio frequency anymore. I use a generic serial/parallel port card plugged into a pci slot on the motherboard. From there, that serial cable plugs into my Yaseu (MFJ) radio interface. It has worked perfectly for years. No issues running it under Windows-7 with N1MM Logger either. Running ps aux - it looks like proper operation of ttyS4.

When you are sure no other program is running using serial port in question you should get cqrlog working with exisiting settings that did work before.

Then you could check Hamlib version. If you have installed wsjt-x you actually have 2 versions.
[saku@tpad ~]$ rigctl --version
rigctl, Hamlib 3.3

Copyright (C) 2000-2012 Stephane Fillod
Copyright (C) 2000-2003 Frank Singleton
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[saku@tpad ~]$ rigctl-wsjtx --version
rigctl(d), Hamlib 3.3~git

Copyright (C) 2000-2012 Stephane Fillod
Copyright (C) 2000-2003 Frank Singleton
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

If there is difference in version use higest. Should be over 3. In case of using rigctl-wsjtx/rigctld-wsjtx you have to change the filename of "path to rigctld" in cqrlog preferences.

It is bit hard to pinpoint your problem "as remote". But if n1mm logger works with windows side using same hardware we can assume that there is no problem at hardware side.
Try these first and tell what you did find out.

I tried your suggestions above and still have the same issue. Here are a few extra details.

I tried to download, compile and install WSJT-X 2.0 from K1JT's web page. Since I use Linux Mint and there is no install package available yet for version 2.0 (AMD64), this is my only option. I got most of the way compiling and installing while adding any missing library and developer files along the way, until I got one that Synaptic Package Manager could not find or install. At that point, I just quit my attempt to install WSJT-X 2.0.

I know they will work on my machine (both CQRLog 2.3.0(001) and WSJT-X 2.0), because I had them running under Mint 19.1 - but I also had issues with Evolution email not running correctly on Mint version 19.1 (could not receive any messages, but could send without any problem at all), that I downgraded my OS and did a fresh, new install of Mint version 18.3. The other programs seem to behave correctly now running Mint 18.3, but CQRLog can't communicate with the radio, but did work just fine with Mint 19.1.

Copyright (C) 2000-2012 Stephane Fillod
Copyright (C) 2000-2003 Frank Singleton
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Typing in the following: rigctl-wsjtx --version
Returns the following: rigctl-wsjtx: command not found

Typing in the following: grig -m 103 -r /dev/ttyS4 -s 4800 -d 3
Returns the following: Lots of messages and a graphical window pops up showing a generic radio interface with the window title heading:
GRIG: Yaesu FT-1000D
The ONLY thing that appears to work is the S-Meter. Is changes appropriately as I tune in loud or quiet stations on the actual radio. No frequency display and no other function appear to work. Then I quit GRIG.

Is there something wrong with my path to rigctrld?

I did notice one new thing I didn't see previously- not related to GRIG testing.
While in CQRLog, if I go to the File menu and hit the option:
Refresh TRX/ROT Control
The CAT light blinks three times on the radio, but still won't read the radio frequency. I can repeat this over and over with the same results.

I'm getting VERY frustrated. I have blown a TON of time playing around to get it working. Any more ideas?

No matter what I tried, I just could not make this work properly. I finally wiped out my Linux Mint 18.3 partition and swap space, reformatted the partition and reinstalled Mint 19.1 - After a few minutes of setup and configuration with CQRLog, I had everything working once again.

The reason I went back to Mint 18.3 was because I just could not get Evolution or Thunderbird to receive ANY email - but I could always send no problem. That turned out to be a NSS Network Security file that needed to be installed on Mint 19.1 - because my local internet provider, COMCAST had a compatibility issue with something in LM 19.1 and when Mint 19.1 was released, this updated file was not originally included. It took quite a bit of searching to figure this one out.

Now that I'm back on Mint 19.1 - I've got CQRLog and WSJT-X working properly. They are talking to each other and the radio as well. Evolution works now and even my old HP laser printer got the latest driver installed and I can print also - I'm happy.

Now I've got to figure out how to get fldigi up and running AND talking to the radio.
Thanks again for all your help and assistance - I appreciate it very much.