Problems rigctld

9 posts / 0 new
Last post
dk5vq
Problems rigctld

Hi,

I don't know if it is a bug or a configuration Problem.
Since i updated to CQRLog 1.4.0 i have no CAT connection to my TS-870.
Never used rigctld before and i'm Linux Rookie. (Linux Mint 12, Kernel-Linux 3.0.0.12-generic, GNOME 3.2.1)
Starting CQRLog in Terminal, it shows as follows:

Settings:
-----------------------------------------------------
RigCtldPath:/usr/bin/rigctld
RigCtldArgs:-m %m -r %r -t %t -s
RunRigCtld: FALSE
RigDevice: /dev/ttyS0
RigCtldPort:4532
RigCtldHost:localhost
RigPoll: 500
RigSendCWR: FALSE
RigId: 210

rigctld started!
Result0:N
Result1:Y
Result2:Y
Connected to localhost:4532

Any ideas ?

vy 73 de Mario, DK5VQ

dk5vq
OK, i got it

after last "Google-session" i got the solution.

For those who have same problems, here's my commandline for TS-870:

-m 210 -r /dev/ttyS0 -s 9600 -t 4532 --set-conf=dtr_state=ON,rts_state=ON

ve7eme
TS-870

Not sure how to use this command line, from terminal I expect, are ther other entries prior to or post this entry?
Darrel VE7EME

Darrel VE7EME

ik3ocd
ik3ocd's picture
re Problems rigctld

Hello Darrel tries to edit the group file which is root / usr enter the line
tty:x:5:your username, save e restart system to me it worked.
hello soon and 73 de ik3ocd flavio

k8wdx
Is you usename part of the

Is you usename part of the dial out group?? try this in terminal:
gksudo gedit /etc/group

look for this:
dialout:x:20:"computer name"
Example my comuter name is k8wdx so mine would look like this:
dialout:x:20:k8wdx
then save, log out then back in, give it a try, see what happens.

Also if you are using Mint you will want to do this to get cluster and lookups working:
Terminal:

sudo touch /etc/resolv.conf
sudo gedit /etc/resolv.conf

you must create two lines:

nameserver 8.8.8.8
nameserver 8.8.4.4

save and restart

HTH Tom K8WDX

Tom K8WDX

ik3ocd
ik3ocd's picture
usr/group

root:x:0:
daemon:x:1:
bin:x:2:
sys:x:3:
adm:x:4:username
tty:x:5:username
disk:x:6:
lp:x:7:username
mail:x:8:
news:x:9:
uucp:x:10:
man:x:12:
proxy:x:13:
kmem:x:15:
dialout:x:20:username

-------------------------------------------------
after this change, the control rig should work...... ciao :-)

UA6CEY
Problems rigctld

Hello everybody!
Hello Petr!

Again and again rigctld problems!
CQRLog 1.5.1 + Hamlib (recent version) doesn't work with my Yaesu FT-897.
Fldigi and Flrig on the same n.book through the same /dev/ttyUSB0 works fine!

I can see rigctld messages in terminal window after CQRLog start.
I tried to vary all of rigctld paremeters - serial port ones, retry numbers, delaying between retries, etc. I tried to change rig's ID (similar FT857 & FT817). It doesn't work, but works with Fldigi $ Flrig.

Petr, please explain how to obtain more debugging info from CQRLog.

Sincerely,
UA6CEY Andrey

wblairm
Problems rigctld

I too am now having problems. Just upgraded to Precise and 1.5.1. Should there be any command line parameters? None show.
Thanks,
Blair

ve7eme
Getting there but still need something

Been trying off and on to for the last year to get radio control and various versions of CQRLOG to work together, my Rig is Kenwood TS-870s the hamlib identifier is -m 210. (2) suggestions back in this thread have allowed be to be able to establish communications from the terminal to the rig. First to add my username to the "dialout "group and the second a parameter string Supplied DK5VQwho has a TS-870s............as below a screen dump fro Terminal
 
darrel@solusos27a ~ $ rigctl -m 210 -r /dev/ttyUSB0 -s 9600 -t 4532 --set-conf=dtr_state=ON,rts_state=ONRig command: fFrequency: 14185000Rig command: mMode: USBPassband: 200Rig command: ...............................................
Both were correct responses for freq. and mode
I think the problem relates to Baudrate, I beleive that Hamlib -m 210 would set it at 57600, while it seems that it will only communicate (kenwood rig control) at -s 9600, nothing seems to work trx setting wise in CQRLOG? not sure where to find the conflict, or how to correct?
OS in use are SolusOS 1.3 based on Debian Whezzy and SolusOS 2a7
Any help would be appreciated
Darrel VE7EME
 

Darrel VE7EME