Help setting up radio interface for 706 MkIIG

57 posts / 0 new
Last post
dl1wil
Help setting up radio interface for 706 MkIIG rigctld

Readily the next days.

When it works on my tiny laptop then I'm pretty stretched to get it running in my new and biiig laptop. Lenovo with 3k monitor. Whitout scaling the display shows a realy small presentation.

I can ensure you that all your commands were taken by copy and paste including correcting m311 to m310.

Wil

oh1kh
Help setting up radio interface for 706 MkIIG rigctld

Hi!

OK. Yesterday evening I was replying with smart phone. You are right. Small displays are bad.
Now when I look your message again from 19" monitor I can see that you have done mistake.

At command prompt you have typed "rigctld" and after "Rig command:" the whole starting command with parameters. Wrong!
If you type just one word "rigctl" and press enter you will get dummy rig (same as -m 1) and it is at 145MHz as default.

Copy next line and paste it to your command console.It is one long line but this forum shows it with 2 or several lines depending of screen size. It will copy ok when you paint it from first "/" to last "t" and then select copy:

/usr/bin/rigctl -vvvvv -m 310 -r /dev/ttyUSB0 -s 19200 --set-conf=serial_handshake=None,dtr_state=Unset,rts_state=Unset

Here is example with my icom7300. Note that command line is otherwise same as you must have, but rig model number for me is 373, you must use 310.
You should get text like this:

[saku@hamtpad ~]$
[saku@hamtpad ~]$
[saku@hamtpad ~]$ whoami
saku
[saku@hamtpad ~]$ /usr/bin/rigctl -vvvvv -m 373 -r /dev/ttyUSB0 -s 19200 --set-conf=serial_handshake=None,dtr_state=Unset,rts_state=Unset
rigctl, Hamlib 3.3
Report bugs to

rig_init called
icom: _init called
rig_register called
rig_register: rig_register (355)
rig_register called
rig_register: rig_register (309)
rig_register called
rig_register: rig_register (310)
rig_register called
rig_register: rig_register (311)
rig_register called
rig_register: rig_register (313)
rig_register called
rig_register: rig_register (314)
rig_register called
rig_register: rig_register (315)
rig_register called
rig_register: rig_register (319)
rig_register called
rig_register: rig_register (320)
rig_register called
rig_register: rig_register (321)
rig_register called
rig_register: rig_register (322)
rig_register called
rig_register: rig_register (367)
rig_register called
rig_register: rig_register (323)
rig_register called
rig_register: rig_register (346)
rig_register called
rig_register: rig_register (324)
rig_register called
rig_register: rig_register (328)
rig_register called
rig_register: rig_register (330)
rig_register called
rig_register: rig_register (326)
rig_register called
rig_register: rig_register (327)
rig_register called
rig_register: rig_register (347)
rig_register called
rig_register: rig_register (357)
rig_register called
rig_register: rig_register (363)
rig_register called
rig_register: rig_register (329)
rig_register called
rig_register: rig_register (362)
rig_register called
rig_register: rig_register (345)
rig_register called
rig_register: rig_register (356)
rig_register called
rig_register: rig_register (375)
rig_register called
rig_register: rig_register (360)
rig_register called
rig_register: rig_register (370)
rig_register called
rig_register: rig_register (361)
rig_register called
rig_register: rig_register (373)
rig_register called
rig_register: rig_register (378)
rig_register called
rig_register: rig_register (331)
rig_register called
rig_register: rig_register (312)
rig_register called
rig_register: rig_register (316)
rig_register called
rig_register: rig_register (332)
rig_register called
rig_register: rig_register (334)
rig_register called
rig_register: rig_register (344)
rig_register called
rig_register: rig_register (368)
rig_register called
rig_register: rig_register (335)
rig_register called
rig_register: rig_register (369)
rig_register called
rig_register: rig_register (377)
rig_register called
rig_register: rig_register (336)
rig_register called
rig_register: rig_register (358)
rig_register called
rig_register: rig_register (337)
rig_register called
rig_register: rig_register (338)
rig_register called
rig_register: rig_register (339)
rig_register called
rig_register: rig_register (340)
rig_register called
rig_register: rig_register (341)
rig_register called
rig_register: rig_register (342)
rig_register called
rig_register: rig_register (343)
rig_register called
rig_register: rig_register (366)
rig_register called
rig_register: rig_register (303)
rig_register called
rig_register: rig_register (304)
rig_register called
rig_register: rig_register (306)
rig_register called
rig_register: rig_register (307)
rig_register called
rig_register: rig_register (302)
rig_register called
rig_register: rig_register (352)
rig_register called
rig_register: rig_register (353)
rig_register called
rig_register: rig_register (351)
rig_register called
rig_register: rig_register (364)
rig_register called
rig_register: rig_register (365)
rig_register called
rig_register: rig_register (354)
rig_register called
rig_register: rig_register (371)
rig_register called
rig_register: rig_register (372)
rig_register called
rig_register: rig_register (374)
rig_register called
rig_register: rig_register (376)
icom_init called
icom_init: civ_version=1
rig_token_lookup called
rig_confparam_lookup called
rig_set_conf called
rig_confparam_lookup called
rig_set_conf: serial_handshake='None'
rig_token_lookup called
rig_confparam_lookup called
rig_set_conf called
rig_confparam_lookup called
rig_set_conf: dtr_state='Unset'
rig_token_lookup called
rig_confparam_lookup called
rig_set_conf called
rig_confparam_lookup called
rig_set_conf: rts_state='Unset'
rig_open called
port_open called
serial_open called
serial_setup called
rig_get_vfo called
Opened rig model 373, 'IC-7300'
rig_strstatus called
Backend version: 0.8.3, Status: Stable

Rig command: f <------------------------Here you type "f" to get rig frequency------------
rig_get_freq called
icom_get_freq called
serial_flush called
write_block called
write_block(): TX 6 bytes
0000 fe fe 94 e0 03 fd ......
read_string called
read_string(): RX 6 characters
0000 fe fe 94 e0 03 fd ......
read_string called
read_string(): RX 11 characters
0000 fe fe e0 94 03 00 40 07 14 00 fd ......@....
from_bcd called
Frequency: 14074000

Rig command: q <------------------------Here you type "q" to stop program------------
rig_close called
port_close called
ser_close called
rig_cleanup called
icom_cleanup called
[saku@hamtpad ~]$

What ever you get to console copy and paste it all to your message so I can see what was the response text.

--
Saku
OH1KH

dl1wil
Help setting up radio interface for 706 MkIIG rigctl

Hi saku,

I take over every command line with copy and paste. I'm to lazy for typing all.

1) Your command "/usr/bin/rigctl…_state=Unset" is exatly taken over to cqrlog.

2) Today I become aware of a notice(?) of cqrlog by starting by terminal:

-----------------------
/usr/bin/rigctl -vvvvv -m 373 -r /dev/ttyUSB0 -s 19200 --set-conf=serial_handshake=None,dtr_state=Unset,rts_state=Unset
----------------------

and then rigctl"d" reports failed to started. Is it right the CI-V Adresse at 4EH? The qouters to explain why do I get on rictld...

To #1: It was necessary to me to turn into su mode. But when it worked.

O.k. now I do see the end comming of the problem.

73

oh1kh
Help setting up radio interface for 706 MkIIG rigctl

" To #1: It was necessary to me to turn into su mode. But when it worked."

Everything should work with your user account. NO su, NO sudo!

If you need su then you do not have rights to access serial device. You have to be member of user group that can read and write serial device.

[saku@hamtpad ~]$ groups
saku dialout lock
[saku@hamtpad ~]$ ls -l /dev/ttyUSB0
crw-rw----. 1 root dialout 188, 0 11. 4. 11:43 /dev/ttyUSB0
[saku@hamtpad ~]$

I think we are not having any progress with this subject and I have very hard to find a way how to solve this problem.

--
Saku
OH1KH

kd8cqc
CQRLOG will not display frequency for IC-706MKIIG

Not sure if this is the right place to post or if I should start a new thread. I started this thread almost two years ago and have started having trouble with the same rig. CQRLOG no longer displays the radio frequency. I have changed to Mint 19.1 and had been able to connect just fine, but maybe in the process of doing some update it seems to have broken. Just tonight I updated to CQRLOG ver. 2.4.0 hoping that it would help, but still no luck.
I have gone back through my original communications in this thread and have corrected a few problems. This is where I am at right now:

"cqrlog --debug=1" in terminal gives this response:

Cqrlog Ver:2.4.0 (001) Date:2019-10-27
**** DEBUG LEVEL 1 ****

OS:
Linux version 4.15.0-65-generic (buildd@lgw01-amd64-006) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019
SSL libraries:
libssl.so
libcrypto.so
Loaded 134350 LoTW users
Loaded 125829 eQSL users
Loaded 36919 SCP calls
*
User home directory: /home/peter/
Program home directory: /home/peter/.config/cqrlog/
Data directory: /home/peter/.config/cqrlog/database/
Memebers directory: /home/peter/.config/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/
*
56 us states loaded
Grid map created
/usr/bin/mysqld
MySQLProcess.Executable: /usr/sbin/mysqld Parameters: --defaults-file=/home/peter/.config/cqrlog/database/mysql.cnf
--datadir=/home/peter/.config/cqrlog/database/
--socket=/home/peter/.config/cqrlog/database/sock
--port=64000

Trying to connect to database
TMySQL57Connection : Server connect failed.
Trying:1
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

use cqrlog001

use cqrlog001

SELECT * FROM cqrlog_config

select * from db_version

[UpgradeMainDatabase] Old version: 16 cDB_MAIN_VER: 16
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 311 -r /dev/ttyUSB0 -t 4532 -s 19200
RunRigCtld: TRUE
RigDevice: /dev/ttyUSB0
RigCtldPort:4532
RigCtldHost:127.0.0.1
RigPoll: 100
RigSendCWR: FALSE
RigId: 311

Starting RigCtld ...
rigProcess.Executable: /usr/bin/rigctld Parameters: -m
311
-r
/dev/ttyUSB0
-t
4532
-s
19200

rigctld started!
Connected to 127.0.0.1:4532

Settings:
-----------------------------------------------------
RotCtldPath:/usr/bin/rotctld
RotCtldArgs:
RunRotCtld: FALSE
RotDevice:
RotCtldPort:4533
RotCtldHost:localhost
RotPoll: 500
RotId: 1

rotctld started!
Connected to localhost:4533
FreqmemSql:select id,freq,mode,bandwidth,info from freqmem order by id

FreqmemNR:0=0
FreqmemFirst:0 FreqmemLast:0
Sending: fmv

CW init
select * from view_cqrlog_main_by_qsodate LIMIT 500 OFFSET 0

LoadForm: frmMain
SELECT COUNT(*) FROM cqrlog_main

select count(*) from (select distinct adif from cqrlog_main where adif <> 0 and (adif not in (2,8,19,23,25,26,28,30,39,42,44,55,57,58,59,67,68,81,85,93,101,102,113,115,119,127,128,134,139,151,154,155,164,178,183,184,186,193,193,194,196,198,200,208,210,218,220,226,228,229,231,243,244,255,258,261,264,267,268,271,307,488,493))) 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 (dxcc_ref NOT LIKE '%*') AND (qsl_r = 'Q')) as foo

SELECT * FROM profiles WHERE visible > 0 ORDER BY nr

SELECT * FROM profiles WHERE nr = -1

SELECT * FROM profiles WHERE visible > 0 ORDER BY nr

SELECT * FROM profiles WHERE nr = -1

select * from view_cqrlog_main_by_qsodate where qsodate >= '2019-10-29' order by qsodate,time_on

LoadForm: frmNewQSO
Sending: fmv

Sending: fmv

Sending: fmv

(many times, then finally)
Msg from rig: RPRT -13

"ps ax | grep rigc" in terminal gives this response:

5074 ? Sl 0:00 /usr/bin/rigctld -m 311 -r /dev/ttyUSB0 -t 4532 -s 19200
5079 pts/0 S+ 0:00 grep --color=auto rigc

"telnet 127.0.0.1 4532" in terminal gives:

Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.

Then "f" gives:

RPRT -13

Then"q" gives:

Connection closed by foreign host.

So this appears to me that it is connecting to the radio but not getting the right response? I don't know where to go from here. You have always been great help, so I am sure we can work this out!
Thanks, Peter
KD8CQC

oh1kh
CQRLOG will not display frequency for IC-706MKIIG

Hi Peter !

From debug it looks like rigctld runs ok, but the rig is not at /dev/ttyUSB0 port.
Other possibility is that your CI-V interface is broken or has poor contact at back side of 706.
Or your rig side settings speed (19200) has changed, or CI-V address is not 706's default.

First check that USB0 is the rig port. Put powers on like just starting to use cqrlog and rig
At command console give:
ls -l /dev/ttyUSB*
See results. Then remove USB socket where CI-V converter is.
Give again
ls -l /dev/ttyUSB*
Compare results. Then put CI-V converter back to usb socket and once again give
ls -l /dev/ttyUSB*

Now you will be pretty sure what port your 706 uses. If it keeps staying in ttyUSB0 that is good.
If it has something else you have to change port at cqrlog.
If it seems that it was USB0 then it went to other port like USB1 it would be best to make "udev symlink" to keep it always in known port.
There are many goof instructions for that. Put words:
udev symlink usb serial
to Google search and see them.
I recommend to do symlink in any case, even if your rig stays at USB0. My rig appears always as /dev/icom7300

If it was not port name study cables and connectors of CI-V line.
If they look good you can check direction from rig to PC with terminal program like minicom or putty:
Stop cqrlog and be sure rigctld is not running by check with ps ax command.
Start minicom or putty to use 19200 baud speed and rig serial port (/dev/ttyUSB0 if it is that)
At rig setup check that TRN is ON (tranceive ON) (see the settings check at next chapter)
Now when you rotate VFO you should get some garbage to minicom (or putty) screen.
That proves something is coming from rig.

After that see your 706 manual how to enter setup mode and there look values of
CI-V address (see manual for default value. rigctld expects rig default but can accept any with external parameter)
Ci-V speed (must be auto or 19200 that is your setting at cqrlog side. I prefer 19200 instead of auto)
TRN oFF (tranceive must be OFF. rigctrld does not like tranceive ON it is meant to connect 2 icom rigs together via CI-V cable)

After these checks, what are the results?

--
Saku
OH1KH

Pages