FT-990

9 posts / 0 new
Last post
w8sfc
FT-990

Does anyonehave an idea as to which rig hamlib id would be used with my FT-990 (Rom v1.3)? 73
Sid Grant W8SFC

ok1rr
ok1rr's picture
FT-990

Try 116.

You might try also

rigctl -l

which displays all supported radios.

w8sfc
FT-990

Yep, the FT-990 is 116, but not sure what the correct poll rate. The default is 500, but I think it should be 2 seconds. Any idea what the correct entry is for 2 seconds?
I appreciate all the assistance.

73
SFC Sid Grant USA (Ret.)

PA3GOS
That would be 2000. The time

That would be 2000. The time entry is in milliseconds. I have my Kenwood TS8-850 set for two seconds as well.

73, Tjalling PA3GOS

w8sfc
FT-990

I set the settings at 4800 baud, 8 data, 2 stop, no parity, DTR on. The serial to rig cable is from xggcomms. the rig communicates with the PC but won't release back to receive. any suggestions? The poll rate is 2000 as suggested. Frequency and mode readout is correct but just won't switch back to receive.

73
SFC Sid Grant USA (Ret.)

PA3GOS
Re:FT-990

First thing I'd suggest in your case is to toggle the DTR. Normally the "Default" settings will do best but one might have to play around a bit to get the proper result.

73, Tjalling PA3GOS

w8sfc
Ft-990

It seems that even toggling the DTR doesn't fix the strange behavior. The TRX windows displays the correct mode/ freq. etc., but even when you exit CQRLOG the rig stays in transmit. Not real sure that the interface cable is compatabile with Linux at this point. 73

73
SFC Sid Grant USA (Ret.)

F6GOX
FT-990 transmit ON

Hello Sid,

I have the same "transmit ON blocked " behavior with my FT-990 + microham USBII + CQRLOG.

Have you find any solution from your side ?

73 Laurent F6GOX

oh1kh
FT-990 transmit ON

HI Laurent!

This is a bit old thread, 7 years!

First of all check that you have latest Hamlib. FT990 model number there is 1016. It is a good indicator as older Hamlibs have only 3-number models.
As cqrlog does not drive microhamII ptt , that is linked to RTS line, Transmit staying on must happen when cqrlog closes and closes rigctld too.
Then RTS state turns to wrong state or is left floating that causes PTT to activate.
That is my quess.

I suggest following test:
Cqrlog/prefences/TRXcontrol change rig model to 2 (Net hamlib rigctrld). Uncheck "Run rigctld at program start" checkbox. Close cqrlog.
Open command console start rigctld manually using right parameters and rig model. Leave command console open and rigctld there running.
Open cqrlog. Check that you can see right frequency there. Close cqrlog.
Did TX leave transmit ON when cqrlog closed?

If this works, and specially if you are using other programs that need rig control like wsjt-x, jtdx, fldigi, qsstv, etc you should read this document:
https://github.com/OH1KH/cqrlog/blob/loc_testing/compiled/setting_rigctl...
and make your configurations following those instructions.

--
Saku
OH1KH