TRX Control with Icom 7200

13 posts / 0 new
Last post
N7DXT
TRX Control with Icom 7200

I just started with CQRLOG and Linux, so I am really a newbie.  
Is there more information on the CI-V setting on the Icom 7200?  This is posted in the online help page
 
Extra command line arguments usefull when you have to specify more parameters to rigctld. E.g. CIV address.
 
Thanks very much 
N7DXT
 

ok2cqr
ok2cqr's picture
Re: TRX Control with Icom 7200

Into Extra command line arguments you can put parameter which will be added to commandline for rigctld. The right format is
 
--civaddr=id
 
where id is the CIV address.
 
As far as I know, there is no need to specify this parameter if you let the default value. Please run CQRLOG from console like this:
 
cqrlog --debug=1
 
and you'll see what rigctld returned and what is wrong.
 
73 Petr, OK2CQR

N7DXT
Thank you Petr

Cheers

N7DXT
TRX Control Debug log; Failure to connect to radio

 
**** DEBUG LEVEL 1 ****
 
Loading libssl: /usr/lib/x86_64-linux-gnu/libssl.so
Loading libcrypto: /usr/lib/x86_64-linux-gnu/libcrypto.so
Loading libmysqlclient: /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18
Loaded 63175 LoTW users
Loaded 71853 eQSL users
Loaded 43156 SCP calls
*
User home directory:    /home/n7dxt/
Program home directory: /home/n7dxt/.config/cqrlog/
Data directory:         /home/n7dxt/.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
*
select * from tables where table_schema = 'cqrlog_common'
 
SELECT log_nr,log_name FROM cqrlog_common.log_list order by log_nr
 
use cqrlog001
 
use cqrlog001
 
use cqrlog001
 
SELECT * FROM cqrlog_config
 
select * from db_version
 
select * from cqrlog_common.db_version
 
SELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIF
 
SELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIF
 
 
Settings:
-----------------------------------------------------
RigCtldPath:/usr/bin/rigctld
RigCtldArgs:-m 361 -r /dev/ttyusb009 -t 4532  -s 9600 
RunRigCtld: TRUE
RigDevice:  /dev/ttyusb009
RigCtldPort:4532
RigCtldHost:localhost
RigPoll:    500
RigSendCWR: FALSE
RigId:      361
 
Starting RigCtld ...
/usr/bin/rigctld -m 361 -r /dev/ttyusb009 -t 4532  -s 9600 
rigctld started!
Connected to localhost:4532
 
Settings:
-----------------------------------------------------
RotCtldPath:/usr/bin/rotctld
RotCtldArgs:
RunRotCtl

ok2cqr
ok2cqr's picture
Re: TRX Control Debug log; Failure to connect to radio

Thank you for the debug output but the insteresting part starts a few lines after last line from debug log you've pasted here :). Could you add also the rest of debug output, please? Thank you!

N7DXT
I may have posted teh new log

I may have posted teh new log in another post, sorry for the confusion.  Also, I do not understand how to determine the usb port I am using.  When I run lsusb, the port numbers seem to change when I restart the computer.
n7dxt@n7dxt-Studio-1440:~$ cqrlog --debug=1
 
**** DEBUG LEVEL 1 ****
 
Loading libssl: /usr/lib/x86_64-linux-gnu/libssl.so
Loading libcrypto: /usr/lib/x86_64-linux-gnu/libcrypto.so
Loading libmysqlclient: /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18
Loaded 63175 LoTW users
Loaded 71853 eQSL users
Loaded 43156 SCP calls
*
User home directory:    /home/n7dxt/
Program home directory: /home/n7dxt/.config/cqrlog/
Data directory:         /home/n7dxt/.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
*
140126 17:36:28 [Note] Plugin 'FEDERATED' is disabled.
140126 17:36:28 InnoDB: The InnoDB memory heap is disabled
140126 17:36:28 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140126 17:36:28 InnoDB: Compressed tables use zlib 1.2.3.4
140126 17:36:28 InnoDB: Initializing buffer pool, size = 128.0M
140126 17:36:28 InnoDB: Completed initialization of buffer pool
140126 17:36:28 InnoDB: highest supported file format is Barracuda.
140126 17:36:29  InnoDB: Waiting for the background threads to start
140126 17:36:30 InnoDB: 5.5.35 started; log sequence number 1595675
140126 17:36:30 [Note] Server hostname (bind-address): '0.0.0.0'; port: 64000
140126 17:36:30 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
140126 17:36:30 [Note] Server socket created on IP: '0.0.0.0'.
140126 17:36:30 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
140126 17:36:30 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
140126 17:36:30 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
140126 17:36:30 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
140126 17:36:30 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.35-0ubuntu0.12.04.1'  socket: '/home/n7dxt/.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
 
use cqrlog001
 
use cqrlog001
 
use cqrlog001
 
SELECT * FROM cqrlog_config
 
select * from db_version
 
select * from cqrlog_common.db_version
 
SELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIF
 
SELECT * FROM cqrlog_common.dxcc_ref ORDER BY ADIF
 
 
Settings:
-----------------------------------------------------
RigCtldPath:/usr/bin/rigctld
RigCtldArgs:-m 361 -r /dev/ttyusb009 -t 4532  -s 9600 
RunRigCtld: TRUE
RigDevice:  /dev/ttyusb009
RigCtldPort:4532
RigCtldHost:localhost
RigPoll:    500
RigSendCWR: FALSE
RigId:      361
 
Starting RigCtld ...
/usr/bin/rigctld -m 361 -r /dev/ttyusb009 -t 4532  -s 9600 
rig_open: error = IO error 
rigctld started!
Connected to localhost:4532
 
Settings:
-----------------------------------------------------
RotCtldPath:/usr/bin/rotctld
RotCtldArgs:
RunRotCtld: FALSE
RotDevice:  
RotCtldPort:4533
RotCtldHost:localhost
RotPoll:    500
RotId:      1
 
rotctld started!
Connected to localhost:4533
CW init
SELECT * FROM profiles WHERE visible > 0 ORDER BY nr
 
SELECT * FROM profiles WHERE visible > 0 ORDER BY nr
 

ok2cqr
ok2cqr's picture
Re: I may have posted teh new log

Here is the problem:
Starting RigCtld .../usr/bin/rigctld -m 361 -r /dev/ttyusb009 -t 4532  -s 9600 rig_open: error = IO error rigctld started!Connected to localhost:4532
 
Are you sure that your USB to serial interface is connected to /dev/ttyusb009? The device name is case sensitive, I suppose it should be something like /dev/ttyUSB009 or /dev/ttyUSB9. If you don't know what devide name it has, unplug the converter, plug it again and dmesg command. You should see the device assigned to /dev/ file.

k8wdx
k8wdx's picture
I have found it is easier to

I have found it is easier to get Fldigi going with rig control first, has drop downs for ports, easier to find the right port... Tom de K8WDX

Tom K8WDX

N7DXT
So I have to make another

So I have to make another program work to get this thing to work??

N7DXT
I took your advice, and got

I took your advice, and got it working.  The radio must be connected to the computer and on before I open CQRLOG.  If I open the log and then turn on the radio, rigcontrol never sees the radio.  
At least I can proceed with up the learning curve.  
Thank you for the advice

N7DXT
Okay so what is the best way

Okay so what is the best way to identifiy the usb port I am conneted to?  I have a radio with a built in sound card, so I just plug the radio into a usb port,  On wiindows program DX Labs, it identifies the Com Port 3.  When I run "lsusb" command in the terminal, I see two possible locations, 005 and 006 now, so I was trying that.  If I change ports, I see a differnet number.  
I can't belive it is this hard to make your program work.  I have searched your forum and none are using an IC-7200 radio it apprears.  I can find no help with this?  
Why cant the program discover the correct port?  
 
 
 

PA1SBM
PA1SBM's picture
as i posted in another thread

as i posted in another thread you put your problem in , i think this could help.....
-------------------------------------------------------------------------------------------------------------------
Hi Gary, 
 
What distribution are you running ??
Looking at your config in the log file , i see something weird...
/dev/ttyusb009
is all in lowercase...
I am pretty sure that the USB parts needs to be in upper case.
To be sure type in a terminal screen: ls /dev/tty*
This should give you all tty devices including the usb one....
Also the 009 seems to be an odd number... my usb>rs232 converter gets /dev/ttyUSB0 or /dev/ttyUSB1
Anyway, the ls command should give you back what port the converter has...
 
good luck!
 
Alex
PA1SBM

N7DXT
Thanks, that was the problem,

Thanks, that was the problem, I needed upper case for USB.  I loaded FLDIGI and could see the correct port.  Thank you for the help.