I need help setting up CQRLOG to connect to my Icom 706 MKIIG. I am very new to Linux so be patient with me. It took me about a month and a half just to get the program installed and working. I installed it through Package Manager initially, but I had broken packages that defied being fixed because it was an older version, and the missing files seem to not be available anywhere. Any help I found on line to attempt to rectify that was either incomplete or wrong. No amount of updating helped. Eventually I deleted the old version and figured out how to install the latest stable version. I no longer have broken packages and the program seems to be working. So far so good.
However, I am having a terrible time attempting to get the software to communicate with my radio. I am running Linux Mint 17.3; CQRLOG ver. 2.0.4 (001).
In ‘Preferences’ setup on the TRX control tab I set up the following:
Path to rigctld binary: /usr/bin/rigctld (I think this was a default. I don’t recall setting it)
Host: localhost (also default)
RIG model: 311 Icom IC-706MkIIG
Device: (this is probably part of my problem. Have tried numerous things, but right now it is set to /dev/tty/USB2)
-When I run lsusb in terminal I get this response for this device:
Bus 006 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Poll rate: 500
Port number: 4532
Extra command line arguments: --civaddr=$58 (right or wrong I chose this based on some online help)
-the radio’s CI-V address is set to 58H
Run rigctld when program starts: box checked
Radio serial parameters:
(the following are set identical to my setup in Windows in N1MM logger, which took about 5 minutes to download, install and set up for radio interface! And it works! These settings also are the same as for Ham Radio Deluxe, which is what I have been using all along.)
Serial speed: 19200 (this is the setting in the radio)
Data bits: 8
Stop bits: 1
Parity: None
Handshake: None
DTR: OFF
RTS: OFF
I also tried setting all those parameters to ‘default’ based on online suggestion, but that didn’t work either.
I also have installed libhamlibs-utils, ver 1.2.15.3-1ubuntu4; Fldigi, ver 3.21.80-1 which I also cannot get to communicate with the radio.
I have also made sure I am a member of the appropriate dialout group, though I don’t remember how I did that now.
I have watched the videos and read the forums for this radio, all to no avail.
Any help with all of this would be greatly appreciated. The program looks good and I would love to get it working. But I am very frustrated with Linux right now and if I can’t get this program working with my radio I will have to revert to my Windows machine for logging, which I really don’t want to do!
Thanks again
Device: (this is probably part of my problem. Have tried numerous things, but right now it is set to /dev/tty/USB2)
If set this way, no worky. Should be /dev/ttyUSB2
<p>Jarmo</p>
I actually had it entered the way you have it. I miss-typed the entry in my post by adding an extra /. Please review everything I have described to see if there is anything else incorrect. And any other questions you can think of to ask me. It does not work.
Thanks, Peter
<p>Hi, I use linux mint 17.3 &18.1, the Extra Command line argument should be blank.Also speed 19200 correct,but data bits,stop bits,parity,handshake,DTR,and RTS all set to default.</p>
<p>When you download a file in mint,say cqrlog,go to your downloads folder and find cqrlog and right click.This brings up the debi installer and this will over-ride synaptic and instal the later version automatically.The repository is not as up to date as this web page.</p>
<p>73 john zl3aau</p>
<p> </p>
john-zl3aau
Thanks for your response. I had already tried all that, but just now did again. Still no connection to the radio.
Peter
HI Peter, Check your file /etc/group find dialout:x:20 and tty:x:5: and see if your user name has been added after these lines. If not you will need to add your user name. You will probably need to use root privileges to edit so be CAREFUL, the gksudo method does not seem to work with these later versions of mint. After editing shut down cqrlog and restart to apply the changes.
73 John
john-zl3aau
Hopefully making progress, but it still doesn't work.
From 'Menu' button went to 'Administration', 'Users and Groups', which brings up 'Users Settings' window. Clicked on 'Manage Groups' tab which brings up 'Groups settings' window. Scrolled down to 'dialout' properties, showed my user name as member and Group ID:20. Scrolled down to 'tty' properties, had to 'check' my user name as member, 'Group ID' was 5, and clicked 'OK'.
Rebooted computer and tried CQRLOG with no luck. Checked group properties again through same process and they showed new setting.
So, I was not a member of 'tty' but now am.
Are there any other groups I should be a member of? Checked properties for 'operator' and 'user' and I am not a member of those, should I be?
Any more ideas?
Peter, KD8CQC
Hi Peter, All should be working so maybe a hardware check is in order. In the 706 menu CI-V Baud should be set to 19200 not auto (You can reduce this if you wish). When using my 706 MKii on my laptop I have the following connections :- USB port to a USB/serial dongle.The Serial side of the dongle is plugged into a CI-V interface which has a 3.5 mm phone plug which is connected to the CI-V port on the rear of the 706. The port on the 706 is adjacent to a similar size port so check your user manual for the correct position. I am using a CI-V interface published in the ARRL Handbook many years ago.
73
john-zl3aau
It's definitely not the interface. I have a usb CI-V interface I recently bought off ebay. I have been using an old, slow Windows XP laptop with HRD for years, that I used with a serial port interface. I built this Linux machine mainly to transition to a better computer and away from Windows, so I basically built it to run CQRLOG. In the mean time I bought a refurbished Windows 7 laptop also. I have installed N1MM in it and also the last free version of HRD. The USB / CI-V interface works perfectly on that. Also installed DXKeeper on it, and although it works too, it is staggeringly complex and I don't have the tiniest interest in taking the time to attempt to use it. What a bloated program that tries to do way too much!!!
I indeed have the baud set to 19200. Not quite sure what to do now. My Linux machine is quickly looking like a big paper weight. I do appreciate your help. Let me know if you can think of anything else to look at.
Peter
First of all you should know what device becomes rig RS232.
Unplug rig's RS232 dongle.
Open a command line window.
type "ls /dev/tty*"(enter, and without quotes)
Then plug rig's RS232 dongle.
type again "ls /dev/tty*"(enter, and without quotes)
You should notice a new /dev/ttyUSBx device now. x may be any number.
When you know device type following (I have here ttyUSB1, use your own number)
Type:
ls -l /dev/ttyUSB1
Get something like:
crw-rw----. 1 root dialout 188, 1 19. 2. 20:33 /dev/ttyUSB1
In response see owner (root) and group (dialout) and before that is crw-rw----
First "rw-" means that owner can read and write to port.
Second means that group members can read and write.
Third "---" means that no one else can not do anything.
Okay. If your username is not at owner's place (should not be normally)
Then your username should belong the group named.
Type:
cat /etc/group (this may vary, in Fedora23 it is like this. Works without sudo, but if does not, put "sudo" as first word)
There are many lines and you should find the same group name from one line:
dialout:x:18:saku
Like this you should find your username from line that begins with same name as "ls -l /dev/ttyUSB1"
showed before.
If so, OK.
If not you should add your username to that group.
I assume that "sudo" works for you.
Type:
sudo usermod -a -G the_groupname your_username
Your password will be asked first, then command is done.
If that does not work you may have some graphical tool to modify users. Use that then.
When you find your username from "dialout"-line (may also be called "modem" group)
by typing again:
cat /etc/group
Then your'e done for that. You should now have access to /dev/ttyUSBx
++++++++++++++++++++++++++++++++
Cqrlog TRX Control
radio one:IC706 Host: 127.0.0.1
model ID: 309 Device: /dev/rig Poll rate: 1000 Port Number:4532
Extra command line arguments: -p /dev/rig -P RTS
Speed: 19200 Databits:default Stop bits: default Parity: Default
Handshake: None DTR: unset RTS: unset
Notes:
I have changed device name from udev so that what ever socket /dev/ttyUSBx rig's RS-232 dongle will become
it will always be linked also to /dev/rig (linking is done by the information of serial adapter).
---------------------------
Fedora23 it goes to file:
/etc/udev/rules.d/92-persistent-usb.rules
adding line: (you must use sudo, or be root to edit this file)
ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303", ATTRS{product}=="USB 2.0 To COM Device", SYMLINK+="rig"
Where IdVendor, idProduct and product can be taken from /var/log/messages
Type :
sudo tail -f /var/log/messages
and then plug your RS232 dongle. Press ctrl-C and the dig out ids from text.
Google how it goes with your distro if ithis does not fit to you.
--------------------------
I use CI-V and PTT with same RS-232/USB dongle. It works perfect, but needs "Extra command line arguments".
Do not use Host: localhost. Use 127.0.0.1 instead. Sometimes, if you have IP6 enabled using "localhost"
may cause problems. IP-Number is better.
+++++++++++++++++++++++++++++++
At IC706 side (I suppose it is the same with MKIIG) you should have:
CI-V TRN OFF
CI-V BAUD 19200
CI-V ADDRESS 48H
You get those by pressing "Lock" while powering on rig.
Change parameter with UP/DN buttons, parameter value with VFO knob
Power off rig after setting and power on without pressing "lock", as usual.
When these are ok, and still no rig control try:
When cqrlog is running open a command line window.
type "ps ax | grep rigc"(enter, and without quotes)
You should get something like:
11739 ? Sl 0:00 /usr/bin/rigctld -m 309 -r /dev/rig -t 4532 -p /dev/rig -P RTS -s 19200 --set-conf=serial_handshake=None,dtr_state=Unset,rts_state=Unset
With different process number (at beginning) and different parameters.
You should find only ONE of those lines. If there are several you have to kill them all and restart cqrlog
With command:
killall rigctld
So many times that it says "no precesses" (Cqrlog must be shut off before)
If that ONE line only is found try to type:
"telnet 127.0.0.1 4532"(enter, and without quotes)
if your distro has telnet installed you should get something like:
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
type:
"f" (enter, and without quotes)
You should get something like:
f
10138000
inidicating rigs current frequency in Hz
type "q" (enter, and without quotes)
q
Connection closed by foreign host.
That should prove that rigctl daemon is runing ok.
At that point it should work! If it all ready works with Windoze.
Most often reasons for defunct are:
- you do no know right /dev/ttyXXXyy port name
- you do not have read/write access to /dev/ttyUSBx port (you do not belong the group)
- you have wrong setting in cqrlog's preferences
--
Saku
OH1KH
--
Saku
OH1KH
Hi Peter, Check 1)the file system to see if rigctld is installed ie usr/bin/rigctld
2) Synaptic Amateur Radio (universe) to see if libhamlib-utils and libhamlib2 are installed. (I am using Cinnamon mint)
73
john-zl3aau
John
In Terminal, - sudo find / -name rigctld returns: /usr/bin/rigctld.
Software Manger shows following installed:
libhamlib-dev
libhamlib-utils
libhamlib2
Not sure how I installed rigctld, nor can I figure out how to do it if it isn't. Not listed in either Software Manager or Package Manager.
Peter
I might as well post one more time on this subject. I have no other choice than to give up on CQRLog and Linux. I really, really wanted to get this logging program working, as I wanted to get away from Windows and use Linux in my ham shack. This program looks really good, and I am sure that someone who knows Linux can get it working and find it useful. However, I am finding that Linux is ridiculously difficult to use, and setting up this software is almost impossible if you are not a Linux expert. I am grateful for the individuals who attempted to help me, however, for a beginner in Linux I could only get so far. Incomplete information is no help at all.
I need to be able to use a logging program on my computer and this still doesn't work. My old Windows XP laptop was just too slow and had a small hard drive and needed to be replaced. In 5 minutes I had the last free version of HRD downloaded, installed, and interfacing with my radio on a newer Windows 7 laptop. Three months of working on CQRLog didn't get it working!
I am not a Windows fan. My main computer is actually a Mac. But I have found that many in the Linux community must think that if someone owns a Linux computer, they must speak the language. This is not always the case.
I hope this can serve as a warning to someone contemplating this software. I am sure it is good, but save yourself some grief and frustration if you are not already a Linux expert.
73, KD8CQC
I'm sorry you can't get rig working.
In Preferences -> TRX control in serial port params set only serial speed, other settings leave as default. Close the program.
Now open a console and enter:
cqrlog --debug=1
Open CQRLOG and you sould see a lot of strange messages. Somewhere will be part related to rigctld. Could you copy it and paste here, please? I suppose there will be the reason why cqrlog doesn't work with your radio. Thank you!
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Thanks for responding. This is the output:
Trying to connect to database
170314 16:11:26 [Note] /usr/sbin/mysqld (mysqld 5.5.54-MariaDB-1ubuntu0.14.04.1) starting as process 3203 ...
TMySQL55Connection : Server connect failed.
Trying:1
Trying to connect to database
TMySQL55Connection : Server connect failed.
Trying:2
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
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/ttyUSB2 -t 4532 --civaddr=058 -s 19200
RunRigCtld: TRUE
RigDevice: /dev/ttyUSB2
RigCtldPort:4532
RigCtldHost:127.0.0.1
RigPoll: 1000
RigSendCWR: FALSE
RigId: 311
Starting RigCtld ...
/usr/bin/rigctld -m 311 -r /dev/ttyUSB2 -t 4532 --civaddr=058 -s 19200
rig_open: error = IO error
rigctld failed to start!
1
2
3
4
5
6
Settings:
-----------------------------------------------------
RotCtldPath:/usr/bin/rotctld
RotCtldArgs:
RunRotCtld: FALSE
RotDevice:
RotCtldPort:4533
RotCtldHost:localhost
RotPoll: 500
RotId: 1
rotctld started!
Connected to localhost:4533
select id,freq,mode,bandwidth from freqmem order by id
CW init
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 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 visible > 0 ORDER BY nr
Thanks, Peter, KD8CQC
Thank you for the debug output, Peter.
Problem is here:
Starting RigCtld ...
/usr/bin/rigctld -m 311 -r /dev/ttyUSB2 -t 4532 --civaddr=058 -s 19200
rig_open: error = IO error
rigctld failed to start!
rigctld could not open the port. Are you sure it's on /dev/ttyUSB2? According to your previous posts in the forum, it seems you are already member of dialout group. To be sure, please run from a console:
groups
You should get list of groups. Is there 'dialout'?
Please try to change /dev/ttyUSB2 to /dev/ttyUSB1 and run cqrlog with --debug=1 parameter again. As far as I know, the civaddr is not needed, hamlib uses good default values.
I'm sorry it's so complicated. These USB to Serial adapters may change the location after every computer reboot. It's not hard to set it to something like /dev/icomradio but it needs to do some "magic" in terminal. I'm going to describe it here on the website, soon.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
I ran the "groups" command and dialout is one of the groups. I ended up going back through previous posts and one of the suggestions in post #10 from oh1kh was to run command line "ls /dev/tty*" alternately unplugging and plugging in the USB adapter. Every time I plugged it back in and ran the command again, one of the devices that returned was /dev/ttyUSB0. No matter how many times I did it, the address didn't change. So I changed the USB address to 0 and clicked on Refresh TRX/ROT control, and now it works.
I know I had previously tried 0 as an address, but maybe there was something else wrong at the time. Seems a little slower than I expected to update the display changing frequencies and bands. Poll rate was 1000. I changed it to 500 then to 250, then to 100. That speeds it up. I noticed that the Frequency field in the logging window lags considerably behind the frequency display in the TRX control window.
I did also eliminate the 'extra command line arguments' --civaddr=058.
Ok, now I'm much happier, and now I can play with using it. How do I import my log book from HRD? What format should I use to export? ADIF, Cabrillo or Exel XML?
Thanks again for everyone's patience and help.
73, KD8CQC
Peter
Never mind. Figured out how to import ADIF file. Looks like I can be up and running.
Thanks again for the help!
73, KD8CQC
Hi Peter,
I have problem with the ICOM706(MK2) connection:
$ ls -l /dev/ttyUSB0crw-rw---- 1 root dialout 188, 0 Jun 30 20:22 /dev/ttyUSB0
I'm pretty shure that I'v got every step done right but the trx an the computer (Kubuntu 16.04) don't talk together. I'm added to the group "dialout", too. But nothing don't want work. I'v got set the initial settings of my Icom like in your description. Nope.
What informations do you need, too?
73 de Wil
System: Host: … Kernel: 4.8.0-58-generic x86_64 (64 bit) Desktop: KDE Plasma 5.8.7Distro: Ubuntu 16.04 xenial
Machine: Mobo: ASRock model: FM2A68M-HD+ Bios: American Megatrends v: P2.00 date: 01/12/2016
CPU: Dual core AMD A8-7600 Radeon R7 10 Compute Cores 4C+6G (-HT-MCP-) cache: 4096 KB
clock speeds: max: 3094 MHz 1: 3094 MHz 2: 3094 MHz 3: 3094 MHz 4: 3094 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics]
Display Server: X.Org 1.18.4 drivers: ati,radeon (unloaded: fbdev,vesa) Resolution: 1920x1080@59.93hz
GLX Renderer: Gallium 0.4 on AMD KAVERI (DRM 2.46.0 / 4.8.0-58-generic, LLVM 3.8.0)
GLX Version: 3.0 Mesa 12.0.6
Audio: Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller driver: snd_hda_intel
Card-2 Advanced Micro Devices [AMD/ATI] Kaveri HDMI/DP Audio Controller driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.8.0-58-generic
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
IF: enp1s0 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:2a:bc:19
Drives: HDD Total Size: 250.1GB (48.8% used) ID-1: /dev/sda model: Samsung_SSD_850 size: 250.1GB
Partition: ID-1: / size: 41G used: 7.6G (20%) fs: btrfs dev: /dev/sda2
ID-2: /home size: 191G used: 105G (55%) fs: xfs dev: /dev/sda3
ID-3: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/sda1
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 0.1C mobo: N/A gpu: 2.0
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 233 Uptime: 1:36 Memory: 1633.8/6929.4MB Client: Shell (bash) inxi: 2.2.35
Hi!
If you have done all tricks this message chain says and still no connect next question is:
Is your CI-V cable in shape? Do you know it for sure?
If you have, or can install, program minicom you could test a bit more.
Set minicom serial settings same as rig CI-V baud and 8bit, none, 1 stopbit.
Set rig's CI-V TRN temporary to ON.
Now, when rig is restarted and minicom is running you should see some garbage charcters
coming to screen every time you turn VFO knob.
If nothing happens check once more that rig's CI-V TRN os ON and CI-V baud is same that you put
to minicom's serial speed settings.
If they SURE are ok and nothing comes to screen when turining VFO knob you should check the CI-V cable
and that it SURE is the ttyUSBx device you think it is.
See this message chain how to check that ttyUSBx is the right one. If it is, measure your cable and if possible chec it with another program or visit another ham who has working icom CAT and test your cable there.
After fixed this problem remember to return CI-V TRN ot state OFF
--
Saku
OH1KH
--
Saku
OH1KH
Thx for your answer.
My CI-V cable is new and the led (one or two) flashes short when I turn on my PC. Therefor I'm shure it's o.k.
I've seted in my rig the "trn" on on and then I start minicom I get this message:
[code]
$ minicom
minicom: Fehler beim Öffnen der Datei »/dev/tty8«: Keine Berechtigung
[/code]
Translated: Error while opening file »/dev/tty8«
Huuh? I've got no idea why /dev/tty8 because "ls -l /dev/tty*" gives out "/dev/ttyUSB0" and I've got no more *USB ports.
73 de Wil
You have to start minicom with -s
minicom -s
Go serial settings (3rd from top)
set (A) serial device to /dev/ttyUSB0
set (E) baud to same as rig's CI-V baud is (A and B) and bits-party-stop to 8n1 (Q)
Exit serial settings (esc) and go "exit settings" (2nd from bottom)
Turn VFO and you should get garbage to window.
If not your CI-V cable is not ttyUSB0 as you think, or cable (or rig) is not working ok.
If garbage charcters came to window cable works at least from rig to pc. This just does not prove it works from PC to rig as you can not enter CI-V commands from keyboard.
Close terminal, set rig's CI-V TRN OFF and doublecheck cqrlog preferences/TRXcontrol.
See that "start rigctld at program start " is cheked and "Show TRx communication on terminal" is cheked. This one you can take of when all works.
open command window and start cqrlog by typing
cqrlog
at command prompt.
You should see TRX conversation after program start phase. What do you see?
--
Saku
--
Saku
OH1KH
minicom
I've done all as you've written. After leaving minicom, not closing, I get these garbage character as descripted. Is it important to save the new configuration? Every time when I wanna doing it do I get a error message (it's not possible).
When do I start cqrlog on terminal I do get these reply:
...
Msg from rig: RPRT -5
RPRT -11
Sending: fmv
Msg from rig: RPRT -5
DL1WIL_2017-07-04_19-56-02.adi
1
1a
2
3
4
5
6
Closing ini file ...
If I go back to minicom -s all new settings are reseted…
"Close terminal, set rig's CI-V TRN OFF and doublecheck cqrlog preferences/TRXcontrol.
See that "start rigctld at program start " is cheked and "Show TRx communication on terminal" is cheked"
All done
73 de Wil
OK.
After getting "garbage" you do not need minicom. You have proved that RIG can send something with the CI-V cable and that USB port is 0, as expected.
Msg from rig: RPRT -5
RPRT -11
Sending: fmv
Msg from rig: RPRT -5
This is the informative part. I assume this repeats all the time when cqrlog is running.
RPRT -5 tells that there is a timeout with rig. Here are the error code explanations. They go from 0 (ok) down -1, -2, ... etc
> public enum rig_errcode_e
> {
> RIG_OK = 0, // No error, operation completed sucessfully
> RIG_EINVAL, // invalid parameter
> RIG_ECONF, // invalid configuration (serial,..)
> RIG_ENOMEM, // memory shortage
> RIG_ENIMPL, // function not implemented, but will be
> RIG_ETIMEOUT, // communication timed out
> RIG_EIO, // IO error, including open failed
> RIG_EINTERNAL, // Internal Hamlib error, huh!
> RIG_EPROTO, // Protocol error
> RIG_ERJCTED, // Command rejected by the rig
> RIG_ETRUNC, // Command performed, but arg truncated
> RIG_ENAVAIL, // function not available
> RIG_ENTARGET, // VFO not targetable
> RIG_BUSERROR, // Error talking on the bus
> RIG_BUSBUSY, // Collision on the bus
> RIG_EARG, // NULL RIG handle or any invalid pointer
> parameter in get arg
> RIG_EVFO, // Invalid VFO
> RIG_EDOM // Argument out of domain of func
> }
So there is timeout problem (-5) and I assume that function that is not available (-11) is "Get vfo" as also my IC706 makes the same but that does not make harm. As long as frequency and mode comes ok.
"Sending: fmv" means that cqrlog sends: get_Frequency,get_Mode,get_Vfo =(fmv)
So the timeout is the problem. First try to set preferences/TRXcontrol/poll 2000 (2sek, or even more).
This might be that it does not help as there is timeout in traffic between rigctld and rig serial line.
And that is causing the reason for -5.
If dropping poll rate does not help next to try is the serial speed.
I use preferences/TRXcontrol/"radio one serial parameters" as:
19200 default default default
none unset unset
And it is working fine. If you have same, but not working you could change 19200 to 9600.
But remember to change CI-V BAUD at rig same as cqrlog has.
At same go check that CI-V ADDR is 48H and CI-V 731 is OFF
If that does not help what version of rigctld you are using? Is it very old?
open terminal and check:
saku@hamtpad ~]$ rigctld --version
rigctl, Hamlib 3.1
Copyright (C) 2000-2012 Stephane Fillod
Copyright (C) 2000-2003 Frank Singleton
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
That is what it should be. If older than 3.1 try to find update.
If it is 3.1 and does not work try to use some other 706 model. 309 or 310 if you now have 311 at preferences/TRXcontrol/RIG model. I assume that does not help as all 706 models use same source code, but it is not very hard to try anyway.
If you have installed WSJT-X digital mode program you should have 2 rigctld programs.
Then "normal" /usr/bin/rigctld and other one that comes with WSJT-X with latest bugfixes called /usr/bin/rigctld-wsjtx
If you have it try to put it to preferences/TRXcontrol/path to rigctld binary and then start all again and test if that works.
IF none of these do not help and you still get RPRT -5 you are in trouble as I can't give any more easy-to-try ideas.
If you can compile hamlib by your self you can download hamlib source and dig out src/icom/ic706.c file.
You will find from it lines:
.write_delay = 0,
.post_write_delay = 0,
.timeout = 1000,
.retry = 3,
Increasing all a bit and then recompile might help. Just get my old TS50s CAT working that way. (file src/kenwood/ts50s.c)
That is the last idea that I have.
But that is quite complicated and should not be needed as there are many ic706s that work with present values.
--
Saku
OH1KH
--
Saku
OH1KH
hamlib 3.1
Maybe now I know why it doesn't work. The command "rigctld --version" informs that "rigctl, Hamlib 1.2.15.3" is installed.
I'm on the way to find out the simplest way to install a newer version.
73 de Wil
Hi Wil,
Ensure also that you are member of the dialout group (I suppose you are).
To check, open a terminal (CTRL+ALT+t) and type 'groups' (without the quotes)
if dialout doesn't show up, type 'sudo useradd -G dialout yourname'
I compiled HAMLIB 3.1 from the sources:
https://sourceforge.net/projects/hamlib/files/hamlib/3.1%7Erc/hamlib-3.1...
I don't know if there is a repository where one can find packages
I solved the timeout problem by adding the following parameter to the call of rigctld:
--set-conf=timeout=10000.0
This sets the timeout to 10 seconds (10000.0 miliSeconds)
You can add it to your shell or in CQRLog under Preferences > TRX control > extra command line arguments.
In fact, my rig (TenTec Omni VII) seems not to be responding to rigctld while I'm operating the rig manually (pushing/turning knobs and also tuning) what leads to a timeout; my Elecraft K3 doen't produce this problem.
Also, passing the parameters of the connection to rigctld (even if they are the defaults) seems to be helpfull in some cases.
Example: rigctld -m 1611 -r /dev/ttyS0 -t 4532 --set-conf=timeout=10000.0 -s 57600 --set-conf=data_bits=8,stop_bits=1,serial_handshake=None
data_bits and stop_bits are defaults ...
Maybe playing around with handshake, DTR and RTS lead also to more stability. My Elecraft K3 needs DTR and RTS set to OFF.
I hope this helps
73 de Peter - ON4EZJ
Thanks Peter for all your effort.
I'm already in the group dialout but will check it in the next days again. I've got downloaded your compiled package. Maybe I make a upgrade to 17.04. In this version the actual version of hamlib present.
You read from me ;)
73 de Wil
Tnx, tnx, tnx.
Now it works. It' unbelievable for to see my little 706mk2 on my PC on Linux. I don't even need the time out option as extra argument, top. It is necessary to choose the simple 706 but when it works. Maybe there are little thinks to solve but I thing it will work out all right.
Tnh agn for your patience.
73 de Wil
Good evening Wil
I'm glad my explanations helped and hope that this thread can help other hams to make their rig work.
Hope we meet on air
73 de Peter ON4EZJ
Hi all, hi Peter,
here I'm again… and need ideas to get to run Cqrlog stable on my laptop (Dell e5430) to run.
But here my first summery:
you: crw-rw----. 1 root dialout 188, 1 19. 2. 20:33 /dev/ttyUSB1
me: crw-rw---- 1 root uucp 188, 0 11. Feb 18:57 /dev/ttyUSB0
you: dialout:x:18:saku
me: dialout:x:1001:me
you: 11739 ? Sl 0:00 /usr/bin/rigctld -m 309 -r /dev/rig -t 4532 -p /dev/rig -P RTS -s 19200 --set-conf=serial_handshake=None,dtr_state=Unset,rts_state=Unset
me: 2826 pts/2 S+ 0:00 grep --colour=auto rigc
"start rigctld at program start" and Show TRx communication on terminal" is cheked.
I've already installed minion 2.7.1. But I've got problems with telnet and already in a manjaro-forum asked for solution.
======================
After a little bit space:
$ cqrlog -debug
Cqrlog Ver:2.3.0 (001) Date:2018-06-17
**** DEBUG LEVEL 1 ****
SSL libraries:
/usr/lib64/libssl.so.1.0.0
/usr/lib64/libcrypto.so.1.0.0
Loading libmysqlclient: /usr/lib64/libmysqlclient.so
**************************
MySQL version: 10.
**************************
**********************************
MySQL version assigned: 5.6
**********************************
Loaded 125958 LoTW users
Loaded 120303 eQSL users
Loaded 37928 SCP calls
*
User home directory: /home/snoopy/
Program home directory: /home/snoopy/.config/cqrlog/
Data directory: /home/snoopy/.config/cqrlog/database/
Memebers directory: /home/snoopy/.config/cqrlog/members/
ZIP code directory: /usr/share/cqrlog/zipcodes/
Binary dir: /usr/bin/
Share dir: /usr/share/cqrlog/
TConnection to MySQL: 5.6
*
56 us states loaded
/usr/sbin/mysqld --defaults-file=/home/snoopy/.config/cqrlog/database/mysql.cnf --datadir=/home/snoopy/.config/cqrlog/database/ --socket=/home/snoopy/.config/cqrlog/database/sock --port=64000
Trying to connect to database
2019-02-11 20:02:47 0 [Note] /usr/sbin/mysqld (mysqld 10.3.12-MariaDB) starting as process 9715 ...
TMySQL56Connection : Server connect failed.
Trying:1
select * from tables where table_schema = 'cqrlog_common'
======================
Or without debug:
$ cqrlog
Cqrlog Ver:2.3.0 (001) Date:2018-06-17
**** DEBUG LEVEL 0 ****
**** CHANGE WITH --debug=1 PARAMETER ****
2019-02-11 20:04:29 0 [Note] /usr/sbin/mysqld (mysqld 10.3.12-MariaDB) starting as process 9763 ...
Settings:
-----------------------------------------------------
RigCtldPath:/usr/bin/rigctld
RigCtldArgs:
RunRigCtld: TRUE
RigDevice: /dev/ttyUSB0
RigCtldPort:4532
RigCtldHost:localhost
RigPoll: 1000
RigSendCWR: FALSE
RigId: 1
1
2
3
4
5
6
NOTE: Window with stalled focus found!, faking focus-out event
NOTE: Window with stalled focus found!, faking focus-out event
Closing ini file ...
Do I must drive crazy???
73 Petr
HI!
First of all this does not look good:
me: crw-rw---- 1 root uucp 188, 0 11. Feb 18:57 /dev/ttyUSB0
me: dialout:x:1001:me
Unless group uucp does have group dialout as member (that can't be)
Check what users uucp have. I made this check with my fedora and lubuntu. Fedora does not have uucp at all.
Fedora:
[saku@hamtpad ~]$ cat /etc/group | grep uucp
[saku@hamtpad ~]$ cat /etc/group | grep dialout
dialout:x:18:saku,test,test2,svxlink
Lubuntu:
saku@servo2:~$ cat /etc/group | grep uucp
uucp:x:10:
saku@servo2:~$ cat /etc/group | grep dialout
dialout:x:20:saku
If your username is not in uucp you must add it as the serial port is allowed only user root and group uucp.
At this point I have to ask do you run your system with username "root" ??
Or is your username actually "me" (nr 1001) as you have in your message. If so, make sure that "me" is member in uucp group.
Cqrlog will NOT run if user "root" is used. I must be ordinary user.
Your rigid reports:
RigId: 1
Rig nr1 is hamlib dummy rig. It is a virtual test rig inside the program.
You have to select the rig model that actually is connected to your serial port /dev/ttyUSB0
--------
Other thing that worries me is that your mysql reports to be mariadb 10, but your mysql version reports 5.6
I think mariadb 10.x should report mysql 5.7
Are you sure that you do not have mysql and mariadb both installed in your system?
Check these:
[saku@hamtpad ~]$ mysql --version
mysql Ver 15.1 Distrib 10.2.19-MariaDB, for Linux (x86_64) using readline 5.1
[saku@hamtpad ~]$ ls -l /usr/lib64/libmysqlclient.so
lrwxrwxrwx. 1 root root 15 10.12. 14:57 /usr/lib64/libmysqlclient.so -> libmariadb.so.3
Particularly that libmysqlclient.so points to libmariadb.so.X
--
Saku
OH1KH
Tnx for your fast answer.
So I try to answer your questions in right order.
$ cat /etc/group | grep uucp
uucp:x:987:
$ cat /etc/group | grep dialout
dialout:x:1001:me
I'm not loged in as root. I've got 2 passwords (1 for root).
Meanwhile I've tryed "$ sudo usermod -a -G uucp me". I will be asked for my login password. I get no response but after groups again I'm not in the group uucp.
$ mysql --version
mysql Ver 15.1 Distrib 10.3.12-MariaDB, for Linux (x86_64) using readline 5.1
and
$ ls -l /usr/lib64/libmysqlclient.so
lrwxrwxrwx 1 root root 15 25. Jan 15:21 /usr/lib64/libmysqlclient.so -> libmariadb.so.3
73
Hi!
Try "sudo su", if you get root prompt then try that usermod command without sudo.
[saku@hamtpad ~]$ sudo su
[sudo] salasana henkilölle saku:
[root@hamtpad saku]#
If you do not get root prompt your "me" is not in sudoers list. Then, as you know root password give: "su - root"
and after getting root prompt try that usermod command again without sudo.
[saku@hamtpad ~]$ su - root
Salasana:
[root@hamtpad ~]#
Mysql looks ok.
Let's try to get serial port working first.
--
Saku
OH1KH
Hi Saku,
fine, do we start with me as user...
$ sudo su
[sudo] Passwort für me:
[snoolux me]#
In the last line is no @.
I check it out better (for me) in my Manjaro forum
73
Hi Saku,
do I've got missed something?
73
Hi !
Sorry I have been busy with some developing issues.
So have you succeeded to add "me" to uucp group when trying to give command as root?
Here is a good wiki for groups:
https://wiki.archlinux.org/index.php/users_and_groups#System_groups
And when you have your user "me" in group uucp you can try dterm, minicom or picocom
that are mentioned in this wiki:
https://wiki.archlinux.org/index.php/working_with_the_serial_console
Starting one of those using serial port where your icom is connected should give some charcters to display when turning vfo knob.
This test requires that ic706 has parameter 23 CI-V TRN on. You can access this parameter by keeping "disp" button pressed while pressing PWR on. Move to 23 with memory "up" "dn" buttons. Set between on and off by turning vfo knob.
Once it is on and you see some char coming to screen when turning vfo go back to icom setting and put CI-V TRN off. It should be off in normal use.
Then it is time to try with cqrlog.
--
Saku
OH1KH
Hi Saku,
nice to read from you and to see you don't forgot me ;). I'm sorry to but I don't find my post with my annotation again that I haved turn(ed) to openSuse 15.0 Leap.
The good news here is, I get the garbage back again. The communication between minicom an trx is back again, yeah. My last problem is now to connect cqrlog with the Icom.
Maybe I'm here again:
Example: rigctld -m 1611 -r /dev/ttyS0 -t 4532 --set-conf=timeout=10000.0 -s 57600 --set-conf=data_bits=8,stop_bits=1,serial_handshake=None
data_bits and stop_bits are defaults ...
Installed is Hamlib 3.3. That should work. Because I do not understand anything here a little picture of the actual configuration of cqrlog.
Tnx for your patient
Wil
File:
Hi!
Ok.
In your picture:
RIG model: select 311 ic706mkIIG if you really have mkIIG (Others are 309 ic706, and 310 ic706MkII)
Device: /dev/ttyUSB0 if your rig interface is at ttyUSB0 port
Extra comand line: take all text away.
DTR: unset
RTS: unset
Others are ok.
Start your rig by keeping LOCK button pressed while pressing power. You get into settings mode.
use buttons UP and DN to get item "21 CI-V ADDRESS" it should display 48H.
press UP to get "22 CI-V BAUD" should display 19200
press UP to get "CI-V TRN" should display off
press UP to get "CI-V 731" should display off
if any of those displays show other values you can change them with VFO knob rotate.
Press power to shut down rig and start it again normally. Now it is ready.
--
Saku
OH1KH
Hi!
Ok.
In your picture:
RIG model: select 311 ic706mkIIG if you really have mkIIG (Others are 309 ic706, and 310 ic706MkII)
Device: /dev/ttyUSB0 if your rig interface is at ttyUSB0 port
Extra comand line: take all text away.
DTR: unset
RTS: unset
Others are ok.
Start your rig by keeping LOCK button pressed while pressing power. You get into settings mode.
use buttons UP and DN to get item "21 CI-V ADDRESS" it should display 48H.
press UP to get "22 CI-V BAUD" should display 19200
press UP to get "CI-V TRN" should display off
press UP to get "CI-V 731" should display off
if any of those displays show other values you can change them with VFO knob rotate.
Press power to shut down rig and start it again normally. Now it is ready.
--
Saku
OH1KH
Hi!
Ok.
In your picture:
RIG model: select 311 ic706mkIIG if you really have mkIIG (Others are 309 ic706, and 310 ic706MkII)
Device: /dev/ttyUSB0 if your rig interface is at ttyUSB0 port
Extra comand line: take all text away.
DTR: unset
RTS: unset
Others are ok.
Start your rig by keeping LOCK button pressed while pressing power. You get into settings mode.
use buttons UP and DN to get item "21 CI-V ADDRESS" it should display 48H.
press UP to get "22 CI-V BAUD" should display 19200
press UP to get "CI-V TRN" should display off
press UP to get "CI-V 731" should display off
if any of those displays show other values you can change them with VFO knob rotate.
Press power to shut down rig and start it again normally. Now it is ready.
--
Saku
OH1KH
Hi Saku,
it seems to that I've lost everything. Ok, "DTR: unset" and "RTS: unset" are unset.
If do I turn off "CI-V TRN" and "CI-V 731" then I don't get any garbage. Only when "CI-V TRN" is turned on, then the garbage flows. It's turned off again.
The last time where I do get it work was here:
https://www.cqrlog.com/comment/5500#comment-5500
That was at Linux Mint…
What do I overlook(?)?
Wil
Hi!
Do not worry about "the grabage". It is not needed for cqrlog. It just visualizes that your serial port receives data from your rig.
Actually "TRN" means functon where one Icom rig can drive other icom rig(s) connected to same CI-V wire. It is not needed here and rigctld does not like it at all.
So keep it "ON" only in test to see that rig connection works.
"731" will emulate old IC731 rig in CI-V commands. As rigctld knows ic706, MKII and MKIIG these should be used and 731 emulation switched of at rig side to get all CI-V properties in use.
"DTR: unset" and "RTS: unset" are unset if you need them for driving PTT relay. If your interface does not have that, but requires "real" handshake then you must set them on (by the interface manual instructions).
If your PTT relay uses those lines, from serial port in use, you have to set "extra command line arguments" to tell rigctld what is the serial device and the handshake line name where you have your PTT relay.
For example if you have PTT relay at same serial port as rig, using RTS line you need to have "DTR: unset" and "RTS: unset" and "extra command line arguments" will have line:
-p /dev/ttyUSB0 -P RTS
If the PTT is on different port than rig, lets say /dev/ttyUSB1, then you do not need to set "DTR: unset" and "RTS: unset". They can be "default".
But PTT is not first problem. Cqrlog works fine without it getting just frequency and used mode from your rig.
In earlier message --set-conf=timeout=10000.0 is recommended. How ever if your rig is IC706/MKII/MKIIG, as the subject of this message says, I think you do not need it.
If you want to try with it the right place for it is "extra command line arguments". Put just the text:
--set-conf=timeout=10000
to that place.
Settings in picture should work for you if your rig side settings are as I wrote on last message.
File:
--
Saku
OH1KH
Hi Saku,
at 1st it doesn't work but maybe the problem is at the version of my installed hamlib. Didn't you tolled me that v3 or better is needed? I've got v2.
Wil
Hi again,
I'v got checked out that the installed version of libhamlib is 3.3-lp150.14.1.
HI!
Settings in picture should work. If your rig settings (in rig) are:
"21 CI-V ADDRESS" 58H. Sorry, I checked this now from Icom and 48 is plain IC706. IC708MKIIG must have 58 here !!
MKII without G must have 4C here. So I was wrong with these numbers.
When you have preferences rig "311 Icom IC706MK2G" you must have 58H at rig's setup.
"22 CI-V BAUD" 19200
"CI-V TRN" off
"CI-V 731" off
If that fix did not help, then questions:
Are you sure that your rig CI-V interface is at /dev/ttyUSB0 ?
What kind of interface you have? Home made or some industrial brand?
After setting 58H to rig Try:
Set in preferences/TRXControl check "Show communication with TRX in console" then open command console and type there:
cqrlog
Copy messages you see to your text editor save and add that txt file to your next message. (or take a screen shot picture)
--
Saku
OH1KH
Hi Saku,
maybe the most important first:
Starting RigCtld ...
/usr/bin/rigctld -m 310 -r /dev/ttyUSB0 -t 4532 -s 19200 --set-conf=serial_handshake=None,dtr_state=Unset,rts_state=Unset
rig_open: error = IO error
rigctld failed to start!
My CI-V interface is industrial brand and connect to USB0. Mincon present garbage when the fitting option is enabled. Even when my 706MK2 is adjusted to CI-V 4C(H) there is no communication.
Wil
Hi!
When you open minicom and get garbage (when ci-v trn on at rig) what are minicom serial settings?
Does it have hardware handshake on then?
If so, put same values to cqrlog settings.
And what brand and model your interface is? I can google information for it.
If you change CI-V address to something else than default (see your manual) you must also change rigctld CI-V address with parameter -c
-c, --civaddr=ID set CI-V address, decimal (for Icom rigs only) NOTE!! it must be decimal! At rig side it is Hex.
Rigctld expects default address of ci-v by rig model given as parameter.
I have feeling this is just a small problem, but hard to find out via messages. I just need to be there...
--
Saku
OH1KH
Hi Saku,
via c&p I give you the infos:
A - Serieller Anschluss : /dev/ttyUSB0
…
| E - Bps/Par/Bits : 19200 8N1
| F - Hardware Flow Control : No
| G - Software Flow Control : No
CQRLOG via konsole:
Starting RigCtld ...
/usr/bin/rigctld -m 310 -r /dev/ttyUSB0 -t 4532 --civaddr=72 -s 19200 --set-conf=serial_handshake=None,dtr_state=Unset,rts_state=Unset
rig_open: error = IO error
rigctld failed to start!
1
2
3
4
5
6
Closing ini file ...
The start failing of rifctld is every time. The notice of "rig_open: error = IO error" occurse every time too.
I'vo no idea which model my interface is. I know that it worked with Mint… How do you can find out which brand it is?
Tnx
Wil
HI !
This is very weird. Open console. give:
whoami
What is the answer?
Then give :
minicom -s
Check that serial settings are as they should be (8N1 /dev/ttyUSB0). Then exit from settings and set rig side TRN ON. Turn vfo.
Check that you get garbage to minicom screen.
Then turn rig TRN OFF
Stop minicom.
then give:
usr/bin/rigctl -vvvvv -m 311 -r /dev/ttyUSB0 -s 19200 --set-conf=serial_handshake=None,dtr_state=Unset,rts_state=Unset
NOTE!! command is rigctl, no "d" at the end.
NOTE!! rig model is 311 as you say you have 706MKIIG. if your rig is MKII(no G) then use 310.
What text you get to console?
If last line you get is:
Rig command:
Give:
f (return)
You should get rig frequency
Give:
q (return)
rigctl closes.
--
Saku
OH1KH
Hi saku,
some times I believe Suse doesn't likes cqrlog:
------------------------------------------------
:~> rigctl
Rig command: usr/bin/rigctl -vvvvv -m 310- /dev/ttyUSB0 -s 19200 --set-conf=serial_handshake=None,dtr_state=Unset,rts_state=Unset
Precede multiple character command names with '\'
Rig command: f
Frequency: 145000000
Rig command: q
snoopy@linux-occb:~>
---------------------------------------------------
The story is that I didn't have been on 145 MHz but when I have turned the vfo it happend nothing. I've tested it on 160m. When I turn on TRN ON than I do get the garbage.
When I ask my PC whoami he says I'm snoopy.
What so I don't get right?
Tnx for all your affort
Hi!
Ok. I wanted to be sure that your console is not root console. Snoopy is ok answer.
/usr/bin/rigctl -vvvvv -m 310- /dev/ttyUSB0 -s 19200 --set-conf=serial_handshake=None,dtr_state=Unset,rts_state=Unset
Is that direct copy from terminal? Or just retype for you message?
Part
-m 310 -r /dev/ttyUSB0
Is the right typing format
Getting 145MHz from f looks like rigctl has selected dummy rig ( -m 1 )
Try again and be sure there are no typing errors.
There should be many lines of text before line "Rig command:" when one of parameters is "-vvvvv"
--
Saku
OH1KH
Pages