First post. I'm stumped.
I have a PC oscilloscope, a Link Instruments MSO-19, that I'm trying to get running under Wine. I installed it under a win64 prefix, and it appears to run just fine. However, it doesn't see the instrument itself. Linux sees it:
> lsusb
...
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 002 Device 006: ID 3195:f190 Link Instruments MSO-19
Bus 002 Device 010: ID 0451:f432 Texas Instruments, Inc. eZ430 Development Tool
Bus 002 Device 003: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub
It shows up in /dev
> ls -l /dev/ttyUSB0
crw-rw-rw- 1 root users 188, 0 Oct 21 22:26 /dev/ttyUSB0
You can see that I have the permissions wide open (I'm a member of 'users', but anyone should be able to access it with these permissions.)
This USB device really is the Link Instruments MSO-19:
> udevadm info /dev/ttyUSB0
P: /devices/pci0000:00/0000:00:09.0/0000:02:00.0/usb2/2-2/2-2.4/2-2.4:1.0/ttyUSB0/tty/ttyUSB0
N: ttyUSB0
S: MSO-19-0
S: serial/by-id/usb-Silicon_Labs_MSO-19_Link_Instruments_4313134950560000205-if00-port0
S: serial/by-path/pci-0000:02:00.0-usb-0:2.4:1.0-port0
E: DEVLINKS=/dev/serial/by-path/pci-0000:02:00.0-usb-0:2.4:1.0-port0 /dev/serial/by-id/usb-Silicon_Labs_MSO-19_Link_Instruments_4313134950560000205-if00-port0 /dev/MSO-19-0
E: DEVNAME=/dev/ttyUSB0
E: DEVPATH=/devices/pci0000:00/0000:00:09.0/0000:02:00.0/usb2/2-2/2-2.4/2-2.4:1.0/ttyUSB0/tty/ttyUSB0
E: ID_BUS=usb
E: ID_MM_CANDIDATE=1
E: ID_MODEL=MSO-19_Link_Instruments
I have a COM port mapped to the USB port:
> ls -l wine64/dosdevices/
total 0
lrwxrwxrwx 1 rod users 10 Oct 21 14:29 c: -> ../drive_c
lrwxrwxrwx 1 rod users 10 Oct 21 22:31 com1 -> /dev/ttyS0
lrwxrwxrwx 1 rod users 10 Oct 21 22:31 com2 -> /dev/ttyS1
lrwxrwxrwx 1 rod users 10 Oct 21 22:31 com3 -> /dev/ttyS2
lrwxrwxrwx 1 rod users 10 Oct 21 22:31 com4 -> /dev/ttyS3
lrwxrwxrwx 1 rod users 12 Oct 21 22:31 com5 -> /dev/ttyUSB0
lrwxrwxrwx 1 rod users 8 Oct 21 14:30 d:: -> /dev/sr0
lrwxrwxrwx 1 rod users 1 Oct 21 14:29 z: -> /
"wine64" is my WINEPREFIX.
The software itself gives me a "serial" error when I try to connect.
Any ideas? I don't know where to go from here.
Thanks,
-Rod
Arch Linux, wine version 2.19
Windows program can't see USB serial connection
Re: Windows program can't see USB serial connection
The Wine User's Guide mentions Linux users needing to add themselves to the sys or dialout groups to access serial ports. https://wiki.winehq.org/Wine_User%27s_G ... llel_Ports
You could also try remapping the device to a different com port following the instructions in the User's Guide.
You could also try remapping the device to a different com port following the instructions in the User's Guide.
Re: Windows program can't see USB serial connection
Thanks for the reply. Arch doesn't have a dialout group. They use uucp instead. I've tried adding myself to sys and uucp without success. Switching COM ports hasn't worked either.
I have been trying to use this program from a Windows 10 instance running inside virtualbox, also without success. I get the same behavior, so perhaps it isn't a wine configuration problem, but something in the way that linux is or isn't talking to some programs. Running native linux code doesn't have a problem with the USB devices.
I'll probably try the virtualbox groups to see if they can shed any light on the problem.
I have been trying to use this program from a Windows 10 instance running inside virtualbox, also without success. I get the same behavior, so perhaps it isn't a wine configuration problem, but something in the way that linux is or isn't talking to some programs. Running native linux code doesn't have a problem with the USB devices.
I'll probably try the virtualbox groups to see if they can shed any light on the problem.
Re: Windows program can't see USB serial connection
I know this thread is pretty old now, but I just stumbled on it. I'm also on Arch Linux.
The problem is likely COM5 isn't handled by the software. Frequently only COM1-4 are supported. If you rename com5 to com1 the software may begin working. I just had the same problem with some other software and a "mv com5 com1" was enough.
Note that I'm having trouble with wine auto-detecting COM ports every time I execute a program, and always assigning ttyUSB0 to COM5. Thus each execution I get to fix the symlinks in dosdevices. You may watch out for that same problem. I'm using Wine Staging 3.12.
The problem is likely COM5 isn't handled by the software. Frequently only COM1-4 are supported. If you rename com5 to com1 the software may begin working. I just had the same problem with some other software and a "mv com5 com1" was enough.
Note that I'm having trouble with wine auto-detecting COM ports every time I execute a program, and always assigning ttyUSB0 to COM5. Thus each execution I get to fix the symlinks in dosdevices. You may watch out for that same problem. I'm using Wine Staging 3.12.
Re: Windows program can't see USB serial connection
You need to change it in the registry. https://wiki.winehq.org/Wine_User%27s_G ... llel_Portsejona86 wrote:Note that I'm having trouble with wine auto-detecting COM ports every time I execute a program, and always assigning ttyUSB0 to COM5. Thus each execution I get to fix the symlinks in dosdevices.
