Setting up ASL3 with the radio interface to USBRadio and a AIOC device. I have edited the res_usbradio file with usb_devices = 1209:7388. This sets the devstr = 1-4:1.0 in the usbradio.conf. But when I try to use the Interface Tune CLI after selecting the device using (1), I get an error ‘the associated USB device string 1-4:1.0 was not found’ ? The command ‘asl-find-sound’ provides the result 1-4:1.0 → 1209:7388 AIOC which correct. The command lsusb provides the result Bus 001 Device 002: ID 1209:7388 Generic All-In-One-Cable. The question I have is the devstr = 1-4:1.0 command creating this string not found issue or is there another file I need to edit to get the AIOC to work correctly ? Thanks, James
1 Like
My system is a Dell WYSE 3040 running 64 bit Debian 12 (BookWorm) with ASL3. No longer allows PIP to be used so there is an issue here perhaps trying to run a python3 hid script ? So I found a solution to the 'USB device string not found' problem. Using a spare Pi 4 unit and installed 32 bit Debian 11 (Bullseye), then followed the instructions by G1LRO, Making an AllStarLink Node with the URC/AIOC – G1LRO HOMEPAGE, to change the identity of the AIOC to a CM108 Pid/Vid value. I could not get the python script to work with 64 bit BookWorm. PIP is allowed with Bullseye. The usbradio.conf could not work with the AIOC with the Dell amd64 Debian 12 OS, using the res_usbradio file mod. Hopefully later ASL3 running on amd64 can fix this AIOC 'USB device string was not found' issue. For now I will use the SimpleUSB fix from G1LRO to mod AIOC to a CM108. Thanks, James 73's
Have a look at https://allstarlink.github.io/adv-topics/usbinterfaces.
I had to make a separate SD card Bullseye installation for the sole purpose of running that script.
This link to G1LRO is not current and likely is wrong for ASL3. The maker of AIOC has notes on ASL3 here: GitHub - skuep/AIOC: Ham Radio All-in-one-Cable
Tried various ways to get the AIOC to link to the Res_USB, always in error with device not seen. Programming the AIOC with Bullseye to a CM108 PID/VID was the only one I found to work. ASL3 hopefully interfaces correctly with the CM108 device, but I now have issues trying to get the Parrot to work whilst setting up the node. Loads of pseudo errors appearing and the Tx not closing until I send a disconnect command. As I am not a linux programmer, I find it frustrating. The Dell WYSE are a good unit to host ASL3, and the cost is £15 per unit. Raspberry Pi 4 may be the default route to take if the errors become continuous to manage. James