Hi,
I'm using Kenwood TS-850S connected to my computer via a USB port. TRX control doesn't worked with CQRLOG 1.4.1 and Xubuntu 12.04. Here is the information displayed in Terminal when I click on "Refresh TRX Control" in CQRLOG:
RigCtldPath:/usr/bin/rigctld
RigCtldArgs:-m %m -r %r -t %t -s 4800
RunRigCtld: TRUE
RigDevice: /dev/ttyUSB0
RigCtldPort:4532
RigCtldHost:localhost
RigPoll: 500
RigSendCWR: FALSE
RigId: 209
Starting RigCtld ...
/usr/bin/rigctld -m 209 -r /dev/ttyUSB0 -t 4532 -s 4800
rigctld started!
Result0:N
Result1:Y
Result2:Y
Connected to localhost:4532
I have no idea what could be wrong. Any help would be much appreciated.
Marcin SQ2OSE
Welcome back,
Everything works fine on the RigId 216 :)
Regards
Marcin SQ2OSE
try this:
rigctld --model=209 --rig-file=/dev/ttyUSB0 --serial-speed=4800 --set-conf=dtr_state=OFF, rts_state=OFF
the port defaults to 4532
I am having a problem getting rigctid to work with an Icom 756PROIII. I am using a USB to Serial adapter /dev/ttyUSB0. I receive a config parameter error,
I am not sure what is the error:
"Config parameter error: Invalid parameter"
These are the results from Terminal when refreshing TRX Control:
Settings:
-----------------------------------------------------
RigCtldPath:/usr/bin/rigctld
RigCtldArgs:-m 357 -r /dev/ttyUSB0 -t 4532 -s 19200 --set-conf=data_bits=8,stop_bits=1,parity=None,dtr_state=OFF,rts_state=OFF
RunRigCtld: TRUE
RigDevice: /dev/ttyUSB0
RigCtldPort:4532
RigCtldHost:localhost
RigPoll: 100
RigSendCWR: TRUE
RigId: 357
Starting RigCtld ...
/usr/bin/rigctld -m 357 -r /dev/ttyUSB0 -t 4532 -s 19200 --set-conf=data_bits=8,stop_bits=1,parity=None,dtr_state=OFF,rts_state=OFF
Config parameter error: Invalid parameter
rigctld started!
Result0:N
Result1:Y
Result2:Y
Connected to localhost:4532
select count(*) from cqrlog002.cqrlog_config
Saving ini file to database
-------------------------------------------------------------------
Thanks for all help.
Lee,
K5LY
New Hope, TX
CW Forever
I have a Pro3 so lets see if I might be able to help...
First thing you should probably do is take CQRlog out of the loop and make sure that rigctld works properly on your system.. If you are running linux and you don't already have it installed download grig, its part of hamlib and it's a good way of testing rigctrl
Once you have that installed open a terminal and type..
grig -r /dev/ttyUSB0 -m357 -s 19200
Of course you need to make sure that your Pro3 cat data speed is set to 19200 if not adjust either the radio or the -s parameter to match what your rig is currently set for..
Don't worry about any other settings. If you haven’t altered anything in the radio setup it should connect using rigctld defaults..
If that works and you can connect to your rig with grig then you need to check and make sure you can connect grig to rigctld so exit grig and in the terminal type
rigctld -r /dev/ttyUSB0 -m357 -s 19200
open another terminal and type
grig -r localhost -m2
Now play around with grig to see if its communicating with the pro-3 and look for errors in the output of both terminals.. If this works that means that rigctrld is working properly and the problem is in your CQRlog setup..
What you can do is start rigctrld manually and then select 2 as the rig id in cqrlog then refresh cqrlog's trx control and it should connect with the rigctld instance you started manually..