I have added myself to the dialout group but when I try to connect to radio I get:
blair@blair-XPS-8930:~$ rigctld -m 214 -r /dev/ttyS4
rig_open: error = IO error
I attached a screen capture of the CAT setting in the ExpertSDR software.
Sat, 2020-04-25 23:31
#1
Trouble connection to SDR radio from Expert
I could not get the above command to work from command line.
Back to Win10 :(
Too many nuances.
Hi!
Are you sure that your rig is at port /dev/ttyS4 ?
That sounds like true RS232 device, not USB port as today almost all ports are.
I got that same error when my rig plug is disconnected (USB to serial converter with IC706).
rigctl -vvvvv -m 3009 -r /dev/rig -t 14532 -p /dev/rig -P RTS -s 19200 --set-conf=serial_handshake=None,dtr_state=Unse
rigctl, Hamlib 4.0~git Apr 4 2020 16:34:29
Report bugs to
rig_init called
initrigs4_icom: _init called
rig_register called
rig_register: rig_register (3055)
rig_register called
...
...
...
rig_open called
port_open called
serial_open called
serial_open: OPEN before
serial_open: OPEN after
serial_open: Unable to open /dev/rig - No such file or directory
main: error opening rig, try#5
rig_open: error = IO error
Opened rig model 3009, 'IC-706'
Backend version: 20200316.0, Status: Untested
Rig command:
So it feels like you are not accessing right port.
Add -vvvvv to your command to see rigctld debug messages. Perhaps it will tell more about IO error.
You can also use terminal mode instead of daemon with command rigctl (leave the "d" away)
rigctl -m 214 -r /dev/ttyS4 -vvvvv
Then you can test rig (once you have the IO error away)
"f"(enter) gives frequency
"F 14000000" (enter) sets frequency
"Q" ends rigctl
--
Saku
OH1KH
Saku,
Thank you for taking the time to respond.
I haven't given up completely....
If I do not have the radio attached to the tryS0, I get this:
blair@blair-XPS-8930:/bin$ ./rigctl -m 214 -r /dev/ttyS0
rig_open: error = Communication timed out
blair@blair-XPS-8930:/bin$
So it seems to be working but radio is not attached. If I attach radio to the same port it get this:
lair@blair-XPS-8930:/bin$ ./rigctl -m 214 -r /dev/ttyS0
rig_open: error = IO error
blair@blair-XPS-8930:/bin$
am i missing something here? does Linux not share the port? here's the permissions:
blair@blair-XPS-8930:/dev$ ls -al ttyS0*
crw-rw-rw- 1 root dialout 4, 64 Apr 29 16:38 ttyS0
blair@blair-XPS-8930:/dev$
Still baffled. it was so easy with a rig with a USB to Serial adapter. With Dos we pair serial ports with a virtual serial port software.
Thanks,
Blair
It looks to me that the root of the problem is that you cannot share tty ports in linux. I look into ways of splitting a port and but was not to get it to work. There is no virtual port mapping as there is in Win10.
Hi!
Only one program can communicate with serial port. (with rig). That has to be rigctld.
See this:
https://github.com/OH1KH/cqrlog/blob/loc_testing/compiled/setting_rigctl...
--
Saku
OH1KH
Hello Blair,
I try to explain whats going on:
- rigctld is using the serial port exclusively - there is no other way (same in windows!)!
- rigctld opens a virtual port in the network (look for hamlib, port 4532) , where you can connect many programs! (same like windows!).
So you have to understand how things work :-) It is well documented.
73 de Martin, DL1MTG
--
73 de Martin, DL1MTG
See this post:
https://www.cqrlog.com/node/2469