Has anybody gotten CQRlog to use CAT control with a Yaesu FTdx10? When I plug in the usb cable the only port that shows up is 'serial'. Can't get it to work. Any help would be greatly appreciated!
Dave ~ k8hw
Fri, 2023-09-22 17:52
#1
k8hw
Yaesu FTdx10
Hi!
Fdx10 is added to hamlib in 2020-12-28, so your Hamlib version should be later than that.
Most recommended to get the source from https://github.com/Hamlib and compile it. Be aware that new compile rolls over the package installed version, or remove it before compile (you need parameter to remove only it, not depended other packages ).
For usb port:
Open command terminal and type
sudo tail -f /var/log/messages
After that plug usb in and see what happens. Also what happens when you unplug usb.
That should tell you if linux notices the rig and what port is assigned.
If linux install is new check that there are no modem managers or others that think rig is modem and "steal" the connection, and that you username belongs to dialout group for access to usb port.
--
Saku
OH1KH
My system doesn't have the file /var/log/messages. I compared the contents of /dev before and after plugging in the usb connector. When the radio is connect two new ports 'ttyUSB0' and 'ttyUSB1' appear. When I point CQRlog to either port, nothing happens. I have another rig that works with CQRlog, but CQRlog is not seeing the FTdx10. The other rig uses /dev/TTYs1
No problem with my FTDX10....
How did you set it up?
Hi k8hw,
Nothing special, using Ubuntu (now on 23.04) and a recent version of Hamlib and a recent version of Cqrlog.
Just found the name of the USB port in /dev/serial/by-id. and used it in the rig setup menu i cqrlog. Must be 38400 baud and 2 stop bits...
Do you have the FTDX working with other programs?
73 de LB2EG Richard
Thanks for info Richard. This did not work with my radio. Here's the device I used:
/dev/serial/by-id/usb-RT_Systems_CT63_Radio_Cable_RT84H63I-if00-port0
And the rest of the settings in the picture.
File:
Well, wsjtx works fine. CAT in the green. BUT, with the same settings CQRLog not connecting to the radio. Not sure where to go next... i verfied all the data entry fields.
Blair
HI Blair!
You can not set same settings to Cqrlog if you use both programs at same time.
Please read this:
https://github.com/OH1KH/cqrlog/blob/loc_testing/compiled/setting_rigctl...
--
Saku
OH1KH
Try to start Cqrlog from command console typing:
cqrlog --debug=1
You should see lot of debug text. If it is hard to follow from console start with this line:
cqrlog --debug=1 > /tmp/debug.txt
And when Cqrlog has started, no rig connected, close it and after that study file /tmp/debug.txt with text editor.
You should see something *like* this at very beginning of debug text :
Settings:
-----------------------------------------------------
RigCtldPath:/usr/local/bin/rigctld
RigCtldArgs:-m 3073 -r /dev/rig -t 4532 -s 19200 --set-conf=serial_handshake=None,dtr_state=Unset,rts_state=Unset
RunRigCtld: TRUE
RigDevice: /dev/rig
RigCtldPort:4532
RigCtldHost:127.0.0.1
RigPoll: 1000
RigSendCWR: FALSE
RigChkVfo TRUE
RigId: 3073
Starting RigCtld ...
rigProcess.Executable: /usr/local/bin/rigctld
Parameters:
-m
3073
-r
/dev/rig
-t
4532
-s
19200
--set-conf=serial_handshake=None,dtr_state=Unset,rts_state=Unset
rigctld started!
Waiting for rigctld 1 @ 127.0.0.1:4532
Connected to rigctld
----------------------
Some keywords are " RunRigCtld: TRUE", "Starting RigCtld ...", "rigctld started!", "Connected to rigctld"
--
Saku
OH1KH
This is what I get on debug. BTW, I do start wsjtx from Cqrlog wih Ctrl-J. Works very well. But I get freq info from wsjtx because cqrlog shows frequency is zero. If I manually adjust it, it goes right back to zero.
Thanks Saku and the rest!
Blair
File:
Blair
HI Blair!
What I can see from your debug is that you are using rig model 1040 that is Yaesu.
Now if you have defined also wsjt-x/settngs/radio to use your Yaesu with same device settings /dev/ttyUSB0 it can not work properly.
In Windoze world it would say "serial port is in use". Linux does not do that. It allows user to access same serial device with several programs without complain, thinking that user does understand that using more than one program with same serial port will cause collisions.
Now if you can get readings to Cqrlog when it is running alone, no other program accessing your rig, set wsjtx/settings/radio to use rig model "Net Hamlib rigctld".
That way wsjtx will access your rig via Cqrlog opended rigctld and no collisions in serial line traffic does happen.
You can work with these settings if you just start Cqrlog *always* before wsjtx so that it finds the rigctld Cqrlog has started.
You can also start rigctld *before* any other program (at login) using a bash script. Then *ALL* your Ham programs should use rig model definition "Net Hamlib RIgctld".
That is the way I do it.
File:
--
Saku
OH1KH
Make sure you are a member of the group that owns /dev/ttyUSB0
or run
rigctl -m 1042 -r /dev/ttyUSB0 -vvv
and see what that says