I picked up a RIgExpert to play with. I also have an IC-706MKIIG radio. I know the complete setup under Windows. I have not been able to get the system to work under OpenSuse 42.3.
The Audio Sound card shows up....
ls /dev/ttyUSB* shows nothing
ls /dev/ttyS* shows a list, not just active ports
Any ideas on what I need to get it working?
TNX Will WC2L
Hi !
I searched a bit about RigExpert, but I did not find schematic of it. Looks like it has microcontroller like Arduino, or similar, inside the box.
Then it might be that it appear also as /dev/ttyACM0 name.
The easiest way is to look from systemlogs with console.
In my fedora everything is logged to /var/log/messages , but this may be some other file in Suse.
in cosole [requires root] give:
sudo tail -f /var/log/messages
Then plug/unplug your RigExpert. You should see some lines and if it is detecetd by Suse there should be also text to see what the device name is.
--
Saku
OH1KH
A soon as you have cleared out what device your RigExpert really is I recommend to spend a little more time with this subject.
Specially if you have a computer that does not have stabile setup. I.E. several USB devices may be connected/disconnected in different orders.
You have to dig out devices idVendor, IdProduct and if you have devices with different serial numbers (not cheap Chinese adapters). With cheap adapters serials are always same and you have to use some other string as
product to separate 2 similar devices.
Setting up udev rule can make symlink always point to same name like /dev/rig what ever is the device connecting order or physical usb socket in use. Then you never have to worry what name your device can be found.
More about this from google with search words: udev symlink usb serial
Here is my symlink file making symlink /dev/ rig, cwkeyer, qps and A300 :
[saku@tpad ~]$ cat /etc/udev/rules.d/92-persistent-usb.rules
ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303", ATTRS{product}=="USB 2.0 To COM Device", SYMLINK+="rig"
ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A601VSBR", SYMLINK+="cwkeyer"
ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303", ATTRS{product}=="USB-Serial Controller D", SYMLINK+="gps"
ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="0da4", ATTRS{idProduct}=="0008", ATTRS{serial}=="CFB57B1C", SYMLINK+="A300"
--
Saku
OH1KH
Will,
try this script, it will show you what is on the ports.
#!/bin/bash
for sysdevpath in $(find /sys/bus/usb/devices/usb*/ -name dev); do
(
syspath="${sysdevpath%/dev}"
devname="$(udevadm info -q name -p $syspath)"
[[ "$devname" == "bus/"* ]] && continue
eval "$(udevadm info -q property --export -p $syspath)"
[[ -z "$ID_SERIAL" ]] && continue
echo "/dev/$devname - $ID_SERIAL"
)
done
I named it devcheck.sh. Don't forget to set up the attributes as executable.
Interesting.. Not much info here... I ran Martin's script and got the following:
/dev/input/event2 - Rextron_USB
/dev/input/event3 - Rextron_USB
/dev/input/mouse0 - Rextron_USB
/dev/snd/controlC1 - 046d_HD_Webcam_C525_68990980
/dev/input/event16 - 046d_HD_Webcam_C525_68990980
/dev/video0 - 046d_HD_Webcam_C525_68990980
/dev/input/event5 - Logitech_USB_Optical_Mouse
/dev/input/mouse1 - Logitech_USB_Optical_Mouse
/dev/snd/controlC0 - Burr-Brown_from_TI_USB_Audio_CODEC
/dev/input/event4 - Burr-Brown_from_TI_USB_Audio_CODEC
/dev/input/event2 - Rextron_USB
/dev/input/event3 - Rextron_USB
/dev/input/mouse0 - Rextron_USB
/dev/snd/controlC1 - 046d_HD_Webcam_C525_68990980
/dev/input/event16 - 046d_HD_Webcam_C525_68990980
/dev/video0 - 046d_HD_Webcam_C525_68990980
/dev/input/event5 - Logitech_USB_Optical_Mouse
/dev/input/mouse1 - Logitech_USB_Optical_Mouse
/dev/snd/controlC0 - Burr-Brown_from_TI_USB_Audio_CODEC
/dev/input/event4 - Burr-Brown_from_TI_USB_Audio_CODEC
The last two are the RigExpert device.
In Open Suse, it appears that Xorg.0.log is the log file to look at:
I removed and added the device:
[ 78889.179] (II) config/udev: removing device Burr-Brown from TI USB Audio CODEC
[ 78889.189] (II) UnloadModule: "libinput"
[ 78900.881] (II) config/udev: Adding input device Burr-Brown from TI USB Audio CODEC (/dev/input/event4)
[ 78900.881] (**) Burr-Brown from TI USB Audio CODEC : Applying InputClass "evdev keyboard catchall"
[ 78900.881] (**) Burr-Brown from TI USB Audio CODEC : Applying InputClass "system-keyboard"
[ 78900.881] (**) Burr-Brown from TI USB Audio CODEC : Applying InputClass "evdev keyboard catchall"
[ 78900.881] (**) Burr-Brown from TI USB Audio CODEC : Applying InputClass "libinput keyboard catchall"
[ 78900.882] (II) Using input driver 'libinput' for 'Burr-Brown from TI USB Audio CODEC '
[ 78900.882] (**) Burr-Brown from TI USB Audio CODEC : always reports core events
[ 78900.882] (**) Option "Device" "/dev/input/event4"
[ 78900.882] (**) Option "_source" "server/udev"
[ 78900.883] (II) input device 'Burr-Brown from TI USB Audio CODEC ', /dev/input/event4 is tagged by udev as: Keyboard
[ 78900.883] (II) input device 'Burr-Brown from TI USB Audio CODEC ', /dev/input/event4 is a keyboard
[ 78900.952] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.7/usb6/6-3/6-3.4/6-3.4:1.3/0003:08BB:2904.0010/input/input27/event4"
[ 78900.952] (II) XINPUT: Adding extended input device "Burr-Brown from TI USB Audio CODEC " (type: KEYBOARD, id 12)
[ 78900.952] (**) Option "xkb_layout" "us"
[ 78900.954] (II) input device 'Burr-Brown from TI USB Audio CODEC ', /dev/input/event4 is tagged by udev as: Keyboard
[ 78900.954] (II) input device 'Burr-Brown from TI USB Audio CODEC ', /dev/input/event4 is a keyboard
Will WC2L
Yep!
Seems to be yet another windoze related box.
I could not find proper schematic or block diagram for it, or even a mention of linux support. Windoze driver seems to create virtual serial ports for accessing CAT and keyer.
Where Ti-5 has clear block diagram, and based on that I think it works also in linux, this Ukraine made TI-8 seems to be W-only device.
--
Saku
OH1KH