rigctl doesn't work with USB-serial

9 posts / 0 new
Last post
DL4UNY
rigctl doesn't work with USB-serial

Hey guys,
I just tried to connect my rig with an USB-serial converter and got some weird problems:
rigctl -m 124 -r /dev/ttyUSB0 -t 4532 -s 4800 --set-conf=data_bits=8,stop_bits=2,serial_handshake=None,dtr_state=Unset,rts_state=Unset

works perfect, typed directly. But when I open cqrlog (this line is actually copied from cqrlog) I get this:

RigCtldPath:/usr/bin/rigctld
RigCtldArgs:-m 124 -r /dev/ttyUSB0 -t 4532 -s 4800 --set-conf=data_bits=8,stop_bits=2,serial_handshake=None,dtr_state=Unset,rts_state=Unset
RunRigCtld: FALSE
RigDevice: /dev/ttyUSB0
RigCtldPort:4532
RigCtldHost:localhost
RigPoll: 500
RigSendCWR: FALSE
RigId: 124

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

nothing changed! I can work perfect on the commandline, the transceiver takes my commands and I receive data, but it's not working when it's called from cqrlog. Do you have any idea what could be wrong here?

Everything works perfect (also via cqrlog) when it's connected to serial port...

Thanks in advance,
Andre - DL4UNY

ok2cqr
ok2cqr's picture
Re: rigctl doesn't work with USB-serial

Hello Andre,

I don't know why it shouldn't work with USB to serial interface. I can see something interesting in the cqrlog output:

RunRigCtld: FALSE

Please check if you have "Run rigctld after program starts" option cheched. Maybe that will be the problem.

73 Petr, OK2CQR

wblairm
rigctl doesn't work with USB-serial

I am having exactly the same problem since I upgraded from Ubuntu 10.04 to 12.04.

wblairm
rigctl doesn't work with USB-serial

***Please check if you have "Run rigctld after program starts" option cheched. Maybe that will be the problem

I have this checked and see the program running in the System Monitory.

n4af
Similar problem

12.04 w/ kernel 3.6rc6--- WORKS OK older linux (ubuntu based lxde variant) using CQRLOG 1.3. I do have another dual usb to serial cable to try, it is straight FTDI.

9.556571] USB Serial support registered for Moschip 7840/7820 USB Serial Driver
[ 9.557672] mos7840 1-5:1.0: Moschip 7840/7820 USB Serial Driver converter detected
[ 9.560306] usb 1-5: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB1
[ 9.560367] usb 1-5: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB2
9.556571] USB Serial support registered for Moschip 7840/7820 USB Serial Driver
[ 9.557672] mos7840 1-5:1.0: Moschip 7840/7820 USB Serial Driver converter detected
[ 9.560306] usb 1-5: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB1
[ 9.560367] usb 1-5: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB2
9.556571] USB Serial support registered for Moschip 7840/7820 USB Serial Driver
[ 9.557672] mos7840 1-5:1.0: Moschip 7840/7820 USB Serial Driver converter detected
[ 9.560306] usb 1-5: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB1
[ 9.560367] usb 1-5: Moschip 7840/7820 USB Serial Driver converter now attached to ttyUSB2 <<>>
Settings:
-----------------------------------------------------
RigCtldPath:/usr/bin/rigctld
RigCtldArgs:-m 229 -r /dev/ttyUSB2 -t 4534 --set-conf=dtr_state=ON,rts_state=ON
RunRigCtld: TRUE
RigDevice: /dev/ttyUSB2
RigCtldPort:4534
RigCtldHost:localhost
RigPoll: 500
RigSendCWR: FALSE
RigId: 229

Starting RigCtld ...
/usr/bin/rigctld -m 229 -r /dev/ttyUSB2 -t 4534 --set-conf=dtr_state=ON,rts_state=ON
rig_open: error = IO error
rigctld started!
Result0:N
Result1:Y
Result2:Y
Connected to localhost:4534
DBPing - select * from cqrlog001.db_version

DBPing - select * from cqrlog001.db_version

----

Here is what looks like good output for radio 1 on /dev/ttyUSB1
Settings:
-----------------------------------------------------
RigCtldPath:/usr/bin/rigctld
RigCtldArgs:-m 229 -r /dev/ttyUSB1 -t 4532 -s 4800
RunRigCtld: FALSE
RigDevice: /dev/ttyUSB1
RigCtldPort:4532
RigCtldHost:localhost
RigPoll: 500
RigSendCWR: FALSE
RigId: 229

rigctld started!
Result0:N
Result1:Y
Result2:Y
Connected to localhost:4532
CW init
SELECT * FROM profiles WHERE visible > 0 ORDER BY nr

SELECT * FROM profiles WHERE visible > 0 ORDER BY nr

2012-10-01 12:17:21

NEITHER RADIO WILL DISPLAY FREQ (both K3's at 4800 default)

Autostart rigctl--> no change

I do not know why the I/O error on rig 2 but both rigs show 0 for freq using 1.5.1 and both work on 1.3
I have reset rigs/USB to serial cable/CQRLOG with same result.

For some reason CQRLOG 1.3 d/n work w/ 12.04 (peppermint 3 O/S) kernel 3.6
Maybe this is know problem so I went to 1.5.1

I have another more generic question... I power down or multiboot into another linux flavor fairly often and my ports change. Anyway to hard assign my usb-serial ports so the assignments remain valid ?

Thanks, Howie N4AF

Howie N4AF

ok2cqr
ok2cqr's picture
Re: Similar problem

Hi Howie,

are you part of dialout group? Maybe that causes I/O error message when rigctld is trying to open the port.

Yes, there is a way how to have all USB converters always with the same files in /dev/. You must write your own udev rules for that. I had the same problem with WinKeyer and FT-817 interface. Maybe I could write small how to.

161 Petr

n4af
1.5.1 Rig Control

Hi Petr -

No, dialout has no members. Think I need to switch to FTDI dual usb to see what happens, but the moschip usb to serial seems ok on CQRLOG 1.3
Only confusion factor is my o/s is bleeding edge.
Maybe I need to upgrade my older system from 1.3 to 1.5.1 and see what happens..

I would like to thank you & Martin for HAMQTH lookup.
Works great in CQRlog and Logger32.

161, Howie

Howie N4AF

n4af
rigctld

Some kind of user error, I think all that was required was adding my user id to dialout and rebooting.

Anyway, all is now ok.

Tks, Howie N4AF

Howie N4AF

DL4UNY
Re: rigctl doesn't work with USB-serial

mmmmh, I'm member in dialout group and still have this problem. I'm running Debian with 2.6.32. I'm sure it's a kernel-issue since I have no problems with my another computer where I'm running Debian with 3.2.0.
@Petr - I checked this box and rigctld is running right after start. But unfortunately I don't get any precise error message, only 'False' :-)

Anyway, maybe it will get solved by itself after a kernel update.

73 de Andre, DL4UNY

DX-addicted
Contest-addicted
Long-term CQRLog-user
Proud cqrweblog-user: http://www.dl8bh.de/cqrweblog/
 
73 de DL4UNY - Andre http://www.dl4uny.de - contact@dl4uny.de