Plug int he digirig, it’s discovered:
1431.841247] usb 3-2.2: new full-speed USB device number 8 using ehci-pci
[ 1431.960526] usb 3-2.2: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[ 1431.960533] usb 3-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1431.960536] usb 3-2.2: Product: CP2102N USB to UART Bridge Controller
[ 1431.960538] usb 3-2.2: Manufacturer: Silicon Labs
[ 1431.960540] usb 3-2.2: SerialNumber: 34ae09c19fcaeb11a5e18b561d69213e
[ 1431.960914] cp210x 3-2.2:1.0: cp210x converter detected
[ 1431.962794] usb 3-2.2: cp210x converter now attached to ttyUSB0
AS myself (non-root) the device always shows busy:
/usr/local/bin/rigctl -r /dev/ttyUSB0 -m 1035 -s 38400 -vvvvv
rigctl Hamlib 4.6~git May 11 04:27:40Z 2023 SHA=bdecc7 64-bit
Report bugs to hamlib-developer@lists.sourceforge.net
rig_check_rig_caps: p1=0x7efd0b15db00, p2=0x7efd0b164080, rig_model=0x7efd0b15db00, macro_name=0x7efd0b164080
yaesu: initrigs4_yaesu called
rig_init: rig_model=Yaesu FT-991 20230510.15
rig_init: rig has VFO_A
rig_init: rig has VFO_B
rig_init: rig has VFO_MEM
ft991_init called, version 20230510.15
1:newcat.c(466):newcat_init entered
1:newcat.c(507):newcat_init returning(0)
1:rig.c(830):rig_open entered
rig_settings_get_path: path=/home/rralphs/.config/hamlib_settings
rig_settings_load_all: settings_file (/home/rralphs/.config/hamlib_settings): No such file or directory
rig_open: cwd=/home/rralphs
rig_open: /home/rralphs/hamlib_settings does not exist
rig_open: async_data_enable=1, async_data_supported=0
serial_open: /dev/ttyUSB0
serial_open(230): open failed#1
serial_open(230): open failed#2
serial_open(230): open failed#3
serial_open(230): open failed#4
serial_open: Unable to open /dev/ttyUSB0 - Device or resource busy
port_open: serial_open(/dev/ttyUSB0) status=-6, err=Device or resource busy
rig_open: rs->comm_state==0?=0
1:rig.c(1036):rig_open returning(-6) IO error
Have done all the obvious stuff, I am in group dialout, removed brltty.
As root device will open but IO times out which I should have to run as root and my be related.
Seems to be a device driver issue?
Randy KB0NAV