Radio is a TS 570D
Radio is setup for Baud 9600 1 stop bit. The default.
CAT control working OK on a PC running Logger32
To get CAT to work with a PC running Logger32 I need the following settings
8N1, 9600 baud
I also need CTS/RTS handshaking to be set on. Will not work without this set.
On Linux PC running Ubunu 22.04
Installed CQRLog 2.5.2
Initially all seemed fine but I cannot get CAT Control to work.
Hamlib version 4.3.1 is installed.
ls /dev/ttyUSB*
gives
/dev/ttyUSB0
Radio 1
Model 2004 Kenwood TS 570
Device /dev/ttyUSB0
Poll 1000 tried 500 as well
Port 4532
9600, Data Bits 8, Stop 1, Parity None.
As I need CTS/RTS on with a PC I set Handshake to Hardware but I have tried all premutations.
I have also tried flrig with more or less the same problems.
The interface cable is the same with Windows PC and Linux.
It uses the Silicon Labs CP210 chipset. I have heard that the FTDI is better?
So I need to get rigctl working before I go any further.
Running hamlib V4.3.1
On V4 of hamlib Rig numbers have changed.
HamLib rigctl -l
TS 570D = 2004
rigctl -m 2004 -s 9600 -r /dev/ttyUSB0 -vvvvv
Above returns a lot of information
If I am on VFOB then rig_set_vfo called vfo=VFOA sets it to A.
So I have some communication but.
Rig is on 7.176.58
rigctl f gives 145000000
rigctl F 7028000 does not change frequency.
Rig is on LSB
rigctl m returns FM
I need to get HamLib working before I can get CAT Control working with CQRLog.
Any advice would be much appreciated.
73
Dave
GM4NFI
HI Dave!
If rigctld gives 145MHz FM it looks like you are running "dummy" rig (#1) That defaults to 2mFM.
But what is the reason...?
If you have rig cable plugged and command terminal:
ls /dev/ttyUSB*
gives /dev/ttyUSB0
And when you unplug rig cable and repeat command and see the /dev/ttyUSB0 has disappeared we can be sure your cable is USB0
When cable connected give
ls -l /dev/ttyUSB*
You should see something similar as:
crw-rw---- 1 root dialout 188, 0 10. 7. 05:52 /dev/ttyUSB0
The owner of ttyUSB0 is "root" and the group is "dialout". Usually it is "dialout" but can be also something else.
Then give command:
groups
You should see your username first, then some others like:
saku dialout lock vboxusers wireshark
Now does that line contain same group name as ttyUSB0? (in my case there is "dialout" in both).
If not, you have to add your username to group that ttyUSB0 has after "root".
Using command (in my case it would be):
sudo usermod -a -G dialout saku
Check that it is ok retyping command:
groups
If your username has now proper group you can try again with Cqrlog (and also flrig).
Remember that you can not run Cqrlog (with /dev/ttyUSB0) and Flrig (with /dev/ttyUSB0) at same time.
Linux allows you to start both while Windoze says "port is already in use".
There are ways to run both at same time (without virtual serial ports program).
See: https://github.com/OH1KH/cqrlog/blob/loc_testing/compiled/setting_rigctl... for that case.
Please let me know if that helped you, or not.
--
Saku
OH1KH
If it helps at all, I had my old TS-570D running great with these settings:
Radio 1
Model 2004 Kenwood TS 570
Device /dev/ttyUSB0
Poll 1500 as well
Port 4532
57600, Data Bits 8, Stop 1, Parity default
Handshake: default, DTR: default, RTS: on
I have highlighted the differences. As you can see, I had my serial speed set higher (on the rig to match), and I found the settings in that last to be important.
Hope this helps!
73,
N1KX - Dave
HI Dave!
So your Linux username belongs "dialout" goup. OK?
Then you could first start Cqrlog with your parameters. When it is running open command terminal and give:
ps ax | grep rig
You should see something similar as:
[saku@hamtpad ~]$ ps ax | grep rig
5172 ? Sl 0:22 /usr/local/bin/rigctld -m 3073 -r /dev/icom7300 -t 4532 -s 19200
Of course with paramaters that your have entered in preferences/TRXcontrol.
Paint the part from starting from "/usr" to the end of line and copy to clipboard.
Stop Cqrlog.
Paste the copied string to command terminal and add "-vvvvv" to the end (without quotes).
When pressing enter you should see long dump text that should end to something like:
main: rigctld listening on port 4532
If you find "error(s)" from text they should tell you what went wrong.
Leave this console as is.
Open another command console and type:
telnet localhost 4532
You should see:
[saku@hamtpad ~]$ telnet localhost 4532
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Type:
f (enter)
You should see frequency from rig:
[saku@hamtpad ~]$ telnet localhost 4532
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
f
3580000
At the same time in the 1st command console you see what happens when you send letter "f" to rigctld.
There is lot of text, but should not conatin any "error(s)".
If they exist they should tell something.
Let me know, please.
--
Saku
OH1KH