Wine freezes when sending to com port, how to find out the reason?

Question

linux

Good day!
Wine 4.0-rc2, Ubuntu 18.04. I'm trying to make the service station stand work under Linux (everything is fine under Windows), I connect the device to the host, it is determined, in dmesg it shows that ftdi_sio is used and connected to ttyUSB0,
I made a simlinsk on ~/.wine/dosdevices/com3, I installed it for the program itself mfc42 via winetricks, the program started, sees the port, connects to the device, reads the version and other basic parameters from it.
There is an error in dmesg when connecting

ftdi_sio unable to read latency timer: -32
ftdi_sio unable to write latency timer: -32

The problem is this:
The fact is that roughly speaking different "tasks" from the program itself are sent to the stand, the size of these tasks can be either quite miserable (a couple of actions) or up to a couple of hundred.
So, if you send a small task, then it is loaded on the stand and everything works fine, but as soon as the size of the task exceeds some limit, then the sending does not reach the end (it always stops at the same place, if you send it and then same task)
There is nothing else in dmesg, Wine does not write about errors either.
When trying to setser /dev/ttyUSB0 low_latency again an error with unable to write latency timer: -32.
ftdi_sio defines the device as ft232bm, BUT the communication chip is VNC1L (the same from FTD, just two in one master and slave, as I understood from the docks, so it should be defined as ft232bm).
I think that something is either with the settings, or xs ... (there is nothing about the speed in the program settings, it apparently exposes something itself). Both the stand and the program are a black box.
Tell me where to dig?
PS I tried different versions of Wine, Ubuntu (I tried at least 11), changed computers, changed USB cables and went to another city to the same stand - everywhere the same behavior.
PPS I recompiled the ftdi_sio kernel module, took it directly from the repository - one damn thing, everything is the same.

Answer 1

The question is, does it work on windows? Because usb-> com controller can create problems. Examine your motherboard, sometimes com and lpt are soldered on it, but the connectors are only on the outer bracket and not behind.
Finger in the sky, but try in the connection settings of your application to reduce the connection speed and check that at least the standard one is used.

Standard baud rates include 110, 300, 600, 1200, 2400, 4800, 9600, 14400, 19200, 38400, 57600, 115200, 128000 and 256000 bits per second.

ftdi-usb-sio.sourceforge.net says that non-standard ones are supported, but work is not guaranteed, by the way, you can also enable debug there, trace what is being transmitted, and so on, suddenly what thoughts will appear.
ps just change the usb port, I have a mitx motherboard, one usb port of which is buggy with the mouse (and nothing else, it just jerks around in it), for example, the ports on the case may be less 'reliable' than on the motherboard, change the wire- extension between usb and controller, if any, etc.

Answer 2

wine is not and never will be a complete replacement for Windows. This is a set of crutches that work more or less well, but since Windows will never work. And even more so in relation to working with equipment.

Answer 3

I don't understand the topic, but I'll try to point you in the right direction.
First make sure the port references are configured correctly
https://wiki.winehq.org/Wine_User%27s_Guide#Serial...
https://forum.winehq.org/viewtopic.php?f=8&t=18385
Try to debug software in Wine
https://wiki.winehq.org/Wine_Developer%27s_Guide/D...
Make sure there is nothing like "not implemented" in the logs.
https://stackoverflow.com/questions/940374/how-can...
https://www.downtowndougbrown.com/2013/03/getting-... Would
you like to try running in ReactOS?!