K3 TRX control

14 posts / 0 new
Last post
gm4kgk
K3 TRX control

New to Linux and CQRLog but have successfully used my K3 with various bits of Windows software.
Preferences have been set up as per previous postings - /dev/ttyS0, 38400-8-N-2 etc and I belong to the dialout group, but the program refuses to talk to the rig.
In terminal mode $ rigctld -r /dev/ttyS0 -m 229 produces no response, but substituting rigctl for rigctld in the statement allows me to communicate with the K3. I get frequency and mode returned in response to 'f' and 'm'.
As I said this is all new to me. I wonder why rigctl produces results when rigctld doesn't. Any clues?
Norman - GM4KGK
 

ok2cqr
ok2cqr's picture
Re: K3 TRX control

Hi Norman,
 
do you have "run rigctld after program starts" option checked? It in Preferences -> TRX control.
 
73 Petr, OK2CQR
 

gm4kgk
Re: K3 TRX control

Hi Petr,
Thanks for reply. Yes, "run rigctld after program starts" is checked. I have read most of the postings on the forum regarding control of the K3 and tried various options that you and others have suggested in the past.
I am concerned that rigctld gets no response from the K3 in terminal mode. Rigctl (no "d") works fine in terminal mode.
The PC is dual boot and if I switch to Logger32 under Windows I can control the K3 perfectly using the same COM port and serial cable, so I am sure the problem lies with CQRLog or it's dependencies. I wish I was more experienced with the Linux platform.
BTW I am using CQRLog without control of the K3 and it is a very impressive piece of software, it has all the facilities I liked in Logger32 (and more) - I hope I don't have to revert to Windows :-)
Here are the settings in Preferences (TXR control)
Path = /usr/bin/rigctld
Radio = K3       Host = localhost
RIGID = 229,   Device = /dev/ttyS0,     Poll = 500,      Port = 4532
'Extra command line arguments' is blank, and 'Run rigctld' is checked
Serial = 38400-8-2-None
Handshake = None, and DTR/RTS are both Unset.
Hope that helps, 73
Norman - GM4KGK

ok2cqr
ok2cqr's picture
Re: K3 TRX control

Hi Norman,
 
rigctld won't work with commands from keyboard. Only rigctl works that way. Rigctld runs on background and I use TCP/IP to work with it.
Please try to set only serial speed and others parameters leave as default. It could help, sometimes rigctl doesn't accept all serial parameters.
 
73 Petr

gm4kgk
Re: K3 TRX control

Hi Petr,
I hope this is not going to take up too much of your precious time. Please excuse my ignorance but how do I set up or implement TCP/IP?
The baud rate is 38400 and I have set all other parameters to default. For info I can have a QSO with FLDigi running under Linux on /dev/ttyS0 with full Tx and Rx control. Frequency and mode are correct and can be changed from the GUI.
Very frustrating!!!
73 - Norman
 

ok2cqr
ok2cqr's picture
Re: K3 TRX control

Hi Norman,

 

please run cqrlog from console with --debug=1 parameter and paste here what it writes down. Thank you!

When rigctld is running, you can try it directly from console using this command:

echo "+\get_mode" | nc -w 1 localhost 4532

73 Petr

 
gm4kgk
Re: K3 TRX control

Hi Petr
I am very grateful to you for the time spent on my problem.
Here is the debug from CQRLog
--------------------------
norrie@norrie-desktop:~$ cqrlog --debug=1**** DEBUG LEVEL 1 ****Loading libssl: /usr/lib/i386-linux-gnu/libssl.soLoading libcrypto: /usr/lib/i386-linux-gnu/libcrypto.soLoading libmysqlclient: /usr/lib/i386-linux-gnu/libmysqlclient.so.18Loaded 68668 LoTW usersLoaded 78590 eQSL usersLoaded 45735 SCP calls*User home directory:    /home/norrie/Program home directory: /home/norrie/.config/cqrlog/Data directory:         /home/norrie/.config/cqrlog/database/Memebers directory:     /usr/share/cqrlog/members/ZIP code directory:     /usr/share/cqrlog/zipcodes/Binary dir:             /usr/bin/Share dir:              /usr/share/cqrlog/TConnection to MySQL:   5.5*140114 22:16:49 [Note] Plugin 'FEDERATED' is disabled.140114 22:16:49 InnoDB: The InnoDB memory heap is disabled140114 22:16:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins140114 22:16:49 InnoDB: Compressed tables use zlib 1.2.3.4140114 22:16:49 InnoDB: Initializing buffer pool, size = 128.0M140114 22:16:49 InnoDB: Completed initialization of buffer pool140114 22:16:49 InnoDB: highest supported file format is Barracuda.140114 22:16:49  InnoDB: Waiting for the background threads to start140114 22:16:50 InnoDB: 5.5.34 started; log sequence number 1589339140114 22:16:50 [Note] Server hostname (bind-address): '0.0.0.0'; port: 64000140114 22:16:50 [Note]   - '0.0.0.0' resolves to '0.0.0.0';140114 22:16:50 [Note] Server socket created on IP: '0.0.0.0'.140114 22:16:50 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them140114 22:16:50 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist140114 22:16:50 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure140114 22:16:50 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure140114 22:16:50 [Note] /usr/sbin/mysqld: ready for connections.Version: '5.5.34-0ubuntu0.12.04.1'  socket: '/home/norrie/.config/cqrlog/database/sock'  port: 64000  (Ubuntu)select * from tables where table_schema = 'cqrlog_common'SELECT log_nr,log_name FROM cqrlog_common.log_list order by log_nr
------------------------------------
Thanks again
73 Norman
 

gm4kgk
Re: K3 TRX control

Petr,
Here is some more output from the debug which follows from the earlier listing. I obtained this after I started the program and loaded a logbook.
Towards the end I closed the Log and Entry windows.
------------------------------------------------------------------
use cqrlog001use cqrlog001SELECT * FROM cqrlog_configselect * from db_versionselect * from cqrlog_common.db_versionOLD:3SELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIFSELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIFSettings:-----------------------------------------------------RigCtldPath:/usr/bin/rigctldRigCtldArgs:-m 229 -r /dev/ttyS0 -t 4532  -s 38400  --set-conf=parity=NoneRunRigCtld: TRUERigDevice:  /dev/ttyS0RigCtldPort:4532RigCtldHost:localhostRigPoll:    1500RigSendCWR: FALSERigId:      229Starting RigCtld .../usr/bin/rigctld -m 229 -r /dev/ttyS0 -t 4532  -s 38400  --set-conf=parity=NoneConfig parameter error: Feature not availablerigctld started!Connected to localhost:4532Settings:-----------------------------------------------------RotCtldPath:/usr/bin/rotctldRotCtldArgs:RunRotCtld: FALSERotDevice:  RotCtldPort:4533RotCtldHost:localhostRotPoll:    500RotId:      1rotctld started!Connected to localhost:4533CW initSELECT * FROM profiles WHERE visible > 0 ORDER BY nrSELECT * FROM profiles WHERE visible > 0 ORDER BY nrselect * from view_cqrlog_main_by_qsodate where qsodate >= '2014-01-09' order by qsodate,time_onLoadForm: frmNewQSOselect * from view_cqrlog_main_by_qsodate LIMIT 500 OFFSET 0LoadForm: frmMainColumn:QSODATE:TRUEColumn:TIME_ON:TRUEColumn:TIME_OFF:TRUEColumn:CALLSIGN:TRUEColumn:MODE:TRUEColumn:FREQ:TRUEColumn:RST_S:TRUEColumn:RST_R:TRUEColumn:NAME:TRUEColumn:QTH:TRUEColumn:QSL_S:FALSEColumn:QSL_R:TRUEColumn:QSL_VIA:FALSEColumn:LOC:FALSEColumn:MY_LOC:FALSEColumn:IOTA:FALSEColumn:AWARD:FALSEColumn:COUNTY:FALSEColumn:PWR:TRUEColumn:DXCC_REF:FALSEColumn:REMARKS:TRUEColumn:WAZ:FALSEColumn:ITU:FALSEColumn:STATE:FALSEColumn:LOTW_QSLSDATE:FALSEColumn:LOTW_QSLRDATE:FALSEColumn:LOTW_QSLS:FALSEColumn:LOTW_QSLR:FALSEColumn:CONT:FALSEColumn:QSLS_DATE:FALSEColumn:QSLR_DATE:FALSEColumn:EQSL_QSL_SENT:FALSEColumn:EQSL_QSLSDATE:FALSEColumn:EQSL_QSL_RCVD:FALSEColumn:EQSL_QSLRDATE:FALSEColumn:QSLR:FALSEColumn:COUNTRY:FALSESELECT COUNT(*) FROM cqrlog_mainselect count(*) from (select distinct adif from cqrlog_main where adif <> 0) as foo select count(*) from (select distinct dxcc_id.dxcc_ref from dxcc_id left join cqrlog_main on dxcc_id.adif = cqrlog_main.adif WHERE cqrlog_main.adif<>0 and ((qsl_r = 'Q') OR (lotw_qslr = 'L') OR (eqsl_qsl_rcvd='E'))) as fooSaveForm: frmMainClosing QSO list windowOnCloseQuery - NewQSOselect count(*) from cqrlog001.cqrlog_configSaving ini file to databaseselect count(*) from cqrlog001.cqrlog_configSaving ini file to databaseClosing DXCluster windowClosing TRXControl windowClosing GrayLine windowClosing dDXCCClosing dData/home/norrie/.config/cqrlog/database/norrie-desktop.pidCommand: kill 5727140114 22:49:38 [Note] /usr/sbin/mysqld: Normal shutdown140114 22:49:38  InnoDB: Starting shutdown...Closing ini file ...[TGtk2WidgetSet.Destroy] WARNING: There are 2 TimerInfo structures left, I'll free themAn unhandled exception occurred at $080717F5 :EAccessViolation :   $080717F5  $0818F425norrie@norrie-desktop:~$ 140114 22:49:39  InnoDB: Shutdown completed; log sequence number 1589339140114 22:49:39 [Note] /usr/sbin/mysqld: Shutdown completenorrie@norrie-desktop:~$
------------------------------
73 - Norman (GM4KGK)
 

ok2cqr
ok2cqr's picture
Re: K3 TRX control

Thank you for the output!
Here is the problem:
 
Starting RigCtld .../usr/bin/rigctld -m 229 -r /dev/ttyS0 -t 4532  -s 38400  --set-conf=parity=NoneConfig parameter error: Feature not available
 
It doesn't like the parity settings. Please set parity as default in Preferences -> TRX control.
 

gm4kgk
Re: K3 TRX control

Hi Petr
Hurrah!!! We are making great progress. After following your instructions I am able to control the K3 with CQRLog. I am very grateful for the time and effort you have put into solving this problem.
I notice that when I boot up the computer and first run CQRLog there is no communication if the K3 is  switched on after the program has loaded. This only happens after first boot of the computer, at other times I can start and close the program, switch the K3 on and off in any combination and everything is fine. Perhaps it has something to do with the first run of rigctld, but as you know I am no expert :-) It is a very minor thing and I am quite happy to live with it since I know that the K3 should be switched on first.
Once again, my sincere thanks for your help
73 - Norman (GM4KGK)
 

ok2cqr
ok2cqr's picture
Re: K3 TRX control

Hi Norman,
 
glad to read it works! There is no need to close program when you turn on K3 after program started. In New QSO window go to File -> Refresh TRX/ROT control. It could help.
 
73 Petr

gm4kgk
Re: K3 TRX control

Hi Petr,
Once again you have all the right answers :-)
The refresh works as you said and I am a happy CQRlog user.
73 de Norman (GM4KGK)

k8wdx
Norman, I have another tip

Norman, I have another tip for you since you are a new Linux user, BTW glad you got it working, when using Linux, always use the LTS version (Long Term Support), I dont know what version you are using now, but a new LTS version is coming this spring, most here will update to the new LTS version then wont update the OS again untill the new LTS version comes out, these LTS versions are supported for 5 years and come out every 3 years, just a tip form Tom, 73 de K8WDX

Tom K8WDX

IW2MXE
IW2MXE's picture
CQRlog work with K3

I use Linux Mint 17.1 and I confirm that my K3 work fine with this configuration in TRX menu:
Rig ID = 229
Device = /dev/ttyUSB0    (because I use a Serial RS232 to USB adapter Prolific)
Poll Rate = 500
Port Nr. 4532
Serial Port setted to = 38400/8/2 default   (Parity is default)
Handshake = none
DTR & RTS = unset
 
A very nice Log SW 
'73 de IW2MXE Diego

'73 de IW2MXE Diego (also AG6WJ)