开云体育

I am fascinated to find a thread in this FT-980 group to discuss CAT
connection to FT-980 using Hamlib library. I am now trying to do it
myself. However, when I try to use rigctl in the Hamlib library, it
times out. Since I could connect to and get information from my
FT-980S using a simple program that I wrote, I think hardware
connection is OK. My question is:

(1) Could any of you connect using rigctl to FT-980?

(2) If yes, what options did you use? I used:

rigctl -m 1031 -r /dev/tty.usbserial-10 -vvvvv

but it times out. I include the log below. What am I doing
wrong?

I am using Hamlib 4.5.2 installed via homebrew on M1 mac (Big Sur).
Any help/information is appreciated! Thank you in advance.

--
Kenichi Asai


$ rigctl -m 1031 -r /dev/tty.usbserial-10 -vvvvv
rigctl.c(445) Startup: rigctl -m 1031 -r /dev/tty.usbserial-10 -vvvvv
rigctl Hamlib 4.5.2 Fri Dec 23 23:04:12 2022 +0000 SHA=f12ac6
Report bugs to <hamlib-developer@...>

rig_check_rig_caps: p1=0x100f02d20, p2=0x100f092a0, rig_model=0x100f02d20, macro_name=0x100f092a0
yaesu: initrigs4_yaesu called
rig_init: rig_model=Yaesu FT-980
rig_init: backend for FT-980 does not contain hamlib_check_rig_caps
rig_init: rig has VFO_SUB
rig_init: rig has VFO_MAIN
rig_init: rig has VFO_MEM
ft980_init called
1:rig.c(812):rig_open entered
rig_settings_get_path: path=/Users/asai/.config/hamlib_settings
rig_settings_load_all: settings_file (/Users/asai/.config/hamlib_settings): No such file or directory
rig_open: cwd=/Users/asai
rig_open: /Users/asai/hamlib_settings does not exist
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/tty.usbserial-10
ser_set_rts: RTS=0
ser_set_dtr: DTR=0
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=4800,0x12c0
serial_setup: cfsetospeed=4800,0x12c0
serial_setup: data_bits=8
serial_setup: parity=0
serial_setup: Handshake=None
serial_setup: tcsetattr TCSANOW
read_string_generic called, rxmax=4095 direct=1, expected_len=1
ser_set_rts: RTS=0
2:rig.c(7417):async_data_handler_start entered
async_data_handler_start: async data support disabled since async_data_enabled=0
2:rig.c(7424):async_data_handler_start returning(0)
rig.c(254):add_opened_rig returning2(0)
rig_open: 0x13600ce1c rs->comm_state==1?=1
ft980_open called
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5024 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5034 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 0b .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5054 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5005 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5036 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 0b .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.4996 seconds after 0 chars, direct=1
rig.c(1275) trace
2:rig.c(2879):rig_get_vfo entered
rig_get_vfo: cache check age=1000000ms
rig_get_vfo: cache miss age=1000000ms
rig.c(2921) trace
ft980_get_vfo called
ft980_get_status_data called
rig_check_cache_timeout called
rig_check_cache_timeout: forced cache timeout
ft980_transaction called
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1, expected_len=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 01 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5003 seconds after 0 chars, direct=1
rig_get_vfo: returning -5(read_block_generic called, direct=1
read_block_generic(): Timed out 2.4996 seconds after 0 chars, direct=1
rig.c(1275) trace
2:rig.c(2879):rig_get_vfo entered
rig_get_vfo: cache check age=1000000ms
rig_get_vfo: cache miss age=1000000ms
rig.c(2921) trace
ft980_get_vfo called
ft980_get_status_data called
rig_check_cache_timeout called
rig_check_cache_timeout: forced cache timeout
ft980_transaction called
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1, expected_len=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 01 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5003 seconds after 0 chars, direct=1
Communication timed out
Communication timed out
)
2:rig_get_vfo: elapsed=2435ms
2:rig.c(2942):rig_get_vfo returning(-5) Communication timed out

rig_open: vfo_curr=currVFO, tx_vfo=TX
rig_open: default vfo = currVFO
rig_get_freq(1985) called vfo=VFOA
vfo_fixup:(from rig_get_freq:1991) vfo=VFOA, vfo_curr=currVFO, split=0
rig.c(1994) vfo=Main, curr_vfo=currVFO
rig_get_freq: cache miss age=1000000ms, cached_vfo=Main, asked_vfo=Main, use_cached_freq=0
rig_get_freq(2081): vfo_opt=0, model=1031
ft980_get_freq: called
ft980_get_freq: passed vfo = 0x4000000
ft980_get_status_data called
rig_check_cache_timeout called
rig_check_cache_timeout: forced cache timeout
ft980_transaction called
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1, expected_len=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 01 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.4996 seconds after 0 chars, direct=1
1:rig_get_freq: elapsed=2436ms
1:rig.c(1370):rig_open returning(0)
Opened rig model 1031, 'FT-980'
Backend version: 20200114.0, Status: Stable
rigctl_parse: called, interactive=1

Rig command: m
rigctl_parse: input_line: m
rigctl_parse: vfo_opt=0
1:rigctl_parse.c(2237):rigctl_get_mode entered
2:rig.c(2404):rig_get_mode entered
vfo_fixup:(from rig_get_mode:2427) vfo=currVFO, vfo_curr=currVFO, split=0
vfo_fixup: Leaving currVFO alone
rig_get_mode: currVFO cache check age=8325ms
rig_get_mode: cache miss age mode=8325ms, width=8325ms
rig.c(2475) trace
ft980_get_mode: called
ft980_get_mode: passed vfo = 0x20000000
ft980_get_status_data called
rig_check_cache_timeout called
rig_check_cache_timeout: forced cache timeout
ft980_transaction called
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1, expected_len=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 01 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5063 seconds after 0 chars, direct=1
rig_get_mode: retcode after get_mode=-5
3:cache.c(35):rig_set_cache_mode entered
3:cache.c(108):rig_set_cache_mode returning(0)
2:rig_get_mode: elapsed=2432ms
2:rig.c(2537):rig_get_mode returning(-5) Communication timed out

1:rigctl_parse.c(2243):rigctl_get_mode returning(-5) Communication timed out

get_mode: error = 0000 00 00 00 00 01 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5063 seconds after 0 chars, direct=1
rig_get_mode: retcode after get_mode=-5
rig_get_mode(2479): freqMainA=0, modeMainA=, widthMainA=0
rig_get_mode(2479): freqMainB=0, modeMainB=, widthMainB=0
3:cache.c(35):rig_set_cache_mode entered
rig_set_cache_mode(37): freqMainA=0, modeMainA=, widthMainA=0
rig_set_cache_mode(37): freqMainB=0, modeMainB=, widthMainB=0
rig_set_cache_mode(107): freqMainA=0, modeMainA=, widthMainA=0
rig_set_cache_mode(107): freqMainB=0, modeMainB=, widthMainB=0
3:cache.c(108):rig_set_cache_mode returning(0)
rig_get_mode(2534): freqMainA=0, modeMainA=, widthMainA=0
rig_get_mode(2534): freqMainB=0, modeMainB=, widthMainB=0
2:rig_get_mode: elapsed=2432ms
2:rig.c(2537):rig_get_mode returning(-5) Communication timed out

1:rigctl_parse.c(2243):rigctl_get_mode returning(-5) Communication timed out

Communication timed out

main: i/o error
1:rig.c(1392):rig_close entered
ft980_close called
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.4213 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5015 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5049 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.4994 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 0b .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.1516 seconds after 0 chars, direct=1
2:rig.c(7461):async_data_handler_stop entered
2:rig.c(7491):async_data_handler_stop returning(0)
ser_set_rts: RTS=0
ser_close: restoring options
rig_close(1528): 0x13600ce1c rs->comm_state==0?=0
1:rig.c(1530):rig_close returning(0)
main: rig_close retcode=0
1:rig.c(812):rig_open entered
rig_settings_get_path: path=/Users/asai/.config/hamlib_settings
rig_settings_load_all: settings_file (/Users/asai/.config/hamlib_settings): No such file or directory
rig_open: cwd=/Users/asai
rig_open: /Users/asai/hamlib_settings does not exist
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/tty.usbserial-10
ser_set_rts: RTS=0
ser_set_dtr: DTR=0
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=4800,0x12c0
serial_setup: cfsetospeed=4800,0x12c0
serial_setup: data_bits=8
serial_setup: parity=0
serial_setup: Handshake=None
serial_setup: tcsetattr TCSANOW
read_string_generic called, rxmax=4095 direct=1, expected_len=1
ser_set_rts: RTS=0
2:rig.c(7417):async_data_handler_start entered
async_data_handler_start: async data support disabled since async_data_enabled=0
2:rig.c(7424):async_data_handler_start returning(0)
rig.c(254):add_opened_rig returning2(0)
rig_open: 0x13600ce1c rs->comm_state==1?=1
ft980_open called
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5060 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.1723 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 0b .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.3258 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.2817 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5007 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 0b .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.3508 seconds after 0 chars, direct=1
rig.c(1275) trace
2:rig.c(2879):rig_get_vfo entered
rig_get_vfo: cache check age=48629ms
rig_get_vfo: cache miss age=48629ms
rig.c(2921) trace
ft980_get_vfo called
ft980_get_status_data called
rig_check_cache_timeout called
rig_check_cache_timeout: forced cache timeout
ft980_transaction called
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1, expected_len=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 01 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.4997 seconds after 0 chars, direct=1
rig_get_vfo: returning -5(read_block_generic called, direct=1
read_block_generic(): Timed out 2.3508 seconds after 0 chars, direct=1
rig.c(1275) trace
2:rig.c(2879):rig_get_vfo entered
rig_get_vfo: cache check age=48629ms
rig_get_vfo: cache miss age=48629ms
rig.c(2921) trace
ft980_get_vfo called
ft980_get_status_data called
rig_check_cache_timeout called
rig_check_cache_timeout: forced cache timeout
ft980_transaction called
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1, expected_len=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 01 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.4997 seconds after 0 chars, direct=1
Communication timed out
Communication timed out
)
2:rig_get_vfo: elapsed=2438ms
2:rig.c(2942):rig_get_vfo returning(-5) Communication timed out

rig_open: vfo_curr=currVFO, tx_vfo=TX
rig_open: default vfo = currVFO
rig_get_freq(1985) called vfo=VFOA
vfo_fixup:(from rig_get_freq:1991) vfo=VFOA, vfo_curr=currVFO, split=0
rig.c(1994) vfo=Main, curr_vfo=currVFO
rig_get_freq: cache miss age=48630ms, cached_vfo=Main, asked_vfo=Main, use_cached_freq=0
rig_get_freq(2081): vfo_opt=0, model=1031
ft980_get_freq: called
ft980_get_freq: passed vfo = 0x4000000
ft980_get_status_data called
rig_check_cache_timeout called
rig_check_cache_timeout: forced cache timeout
ft980_transaction called
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1, expected_len=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 01 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.3665 seconds after 0 chars, direct=1
1:rig_get_freq: elapsed=2431ms
1:rig.c(1370):rig_open returning(0)
main: rig_open retcode=0
rigctl_parse: called, interactive=1

Rig command: q
1:rig.c(1392):rig_close entered
ft980_close called
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5002 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.5040 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.4503 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00 .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.4999 seconds after 0 chars, direct=1
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 0b .....
read_block_generic called, direct=1
read_block_generic(): Timed out 2.4995 seconds after 0 chars, direct=1
2:rig.c(7461):async_data_handler_stop entered
2:rig.c(7491):async_data_handler_stop returning(0)
ser_set_rts: RTS=0
ser_close: restoring options
rig_close(1528): 0x13600ce1c rs->comm_state==0?=0
1:rig.c(1530):rig_close returning(0)
ft980_cleanup called

Hello?Kenichi,

I'm not an expert un CAT for FT-980, but in the past I tried using Omnirig and Omirig Client.
The details of CAT protocol are given in page 13 (page 15 of PDF) in service manual :
http://www.radiomanual.info/schemi/YAESU_HF/FT-980_serv.pdf

The physical link is in TTL (not in RS232), or without line transciver that invert the signal.
Normaly the FT-980 send a echo of the command in half duplex (see figure on bottom of page 13)
Using an oscilloscope you must see it? on Rx pin !

Based on your log, you send "Extrl crtl on/off" command :
write_block(): TX 5 bytes, method=1
0000 00 00 00 00 00

then the read command should recieved the same :
...and here nothing is recieved !
read_block_generic called, direct=1
read_block_generic(): Timed out 2.4995 seconds after 0 chars, direct=1
If the FT-980 recieve correctly this command the front panel is locked during CAT control !

Personnaly I gave up this transciver in CAT mode because all of digital controls are locked on front panel during CAT control !
It could be used in remote, but analog controls are not possible in CAT !?
And the response in CAT mode is really slow :? to get the frequency a STATUS CHECK is 148 bytes to read !!!

The FT-980 was one of the first in CAT mode, but the controller (CPU 8085) is really limited !
It is an 8-bit microprocessor designed by Intel in 1977 ! ! !

Regards,
JMat (Jean-Matthieu)
73 de F5RCT

Thanks JMat for various information! I made similar observation on
the log. After that, I looked into the source code of Hamlib library
and found that if I replace the line:



from:

result = port_select(p, fd + 1, &rfds, NULL, &efds, &tv, 1);

to:

result = port_select(p, fd + 1, &rfds, NULL, &efds, NULL, 1);

and recompile rigctl, I could successfully communicate with FT-980S
with "rigctl -m 1031 -r /dev/tty.usbserial-10"! Since the port_select
function eventually expands to select function, the change effectively
removes the timeout of select. However, even if I set the timeout
long enough by passing "-C timeout=10000" option to rigctl, the
original rigctl times out. I don't know why.

I am still interested in if anybody could talk to FT-980 from linux or
windows. It would then mean that the select function of mac does not
behave as we expect. Otherwise, I would consider asking a question to
the Hamlib mailing list.

Yes, locking during CAT control is annoying. The communication speed
would also be a problem. But FT-980S is my favorite rig I have been
using for 40 years, and I would like to explore its possibilities some
more.

--
Kenichi Asai

All,

I've been doing a bit of rig driver development for flrig over the last few months.

Absent from its list of supported radios is the FT-980. As soon as I finish the Optoelectronics scanner driver (Optocom, OS-535, etc.) I'll fix this omission. WSJT-X can use either hamlib or flrig as its radio-control front end, as can fldigi. Both support logging of one form or another.

73 - Fred, N8YX

Dear all,

I asked a question to the Hamlib mailing list and got the following
reply:



It turned out that if I pass "-C dtr_state=ON" option to rigctl, it
works fine without timeouts.

Thanks for the information on FT8 and logging programs. It is good to
know that I can use FT-980 for FT8. I am new to FT8, but would like
to try it in the near future. I am now finding how to do the audio
interface. I think I should connect AF OUT in the back panel of
FT-980 to the computer's Line In and PATCH IN to the Line Out. Am I
right?

--
Kenichi Asai

I played around with hamlib for a bit, submitted a change, even started work to improve the interface.

The biggest issue with the FT-980 I found is that most of the front panel interface locks out when you enter CAT, and CAT changes are temporary (ephemeral).?


--
-Mat Breton, N8TW

I'm going to write an FT-980 driver for flrig.

This will allow GUI control of tuning, IF? Shift and the other "locked out" functions. As Wald pointed out, for FT-8 (or any of the modes supported by wsjt-x, for that matter) the program automagically does most of what's needed. fldigi can use flrig as its tuning mechanism, and while not the same as spinning a VFO dial I've used this setup to tune my IC-751A/R-71A across the bands while operating digital modes. The '980 command set should add a little functionality over the Icoms of the same era.

Pie-in-the-sky would be concurrent dual radio support via flrig. Maybe hit a "sync" button and the transceiver follows a connected receiver, which could be used for tuning around the bands in search of interesting things. Or the transceiver always follows if a continual sync option is selected. I've a somewhat lengthy list of rig drivers to write for that application, and among them is one for the NRD-535D - which I'll probably use as a spotting RX for the FT-980.?

Stuff to ponder. It's all ones and zeros anyway.

73 - Fred, N8YX

Good news Fred - count me in to try the alpha version!

Peter G0LQU

Fred_N8YX wrote: