http://bugs.winehq.org/show_bug.cgi?id=29011
--- Comment #3 from John jstutch@googlemail.com 2011-11-13 05:30:55 CST --- I have attached +comm output, sorry about the huge file. This was the output of running the program, going to 'Options', selecting COM1, and clicking 'Test' to test the interface. (I have a symlink in .wine/dosdevices/com1 to /dev/ttyUSB0). A success message was displayed, following this, the interface was tested again, this time a failure message was displayed.
Once the port has been tested (or accessed by the program) once, the baud rate needs to be reset (e.g stty -F /dev/ttyUSB0 9600), before it can be tested (or used) correctly again. As I mentioned, I have got this to work completely by making the changes to serial.c detailed previously.
I don't think the giant warning is shown without +comm, but it is in the attached log.
The program can be downloaded at http://www.ross-tech.com/vcds-lite/download/index.html, some fairly detailed usage instructions are on that site too. It will, however require a USB-OBD2 interface. The one I have is a cheap KKL one from eBay. It is an FTDI FT2322 with a 12V line driver interface. As the KKL interface is a half-duplex bus, I think when testing the interface it puts some data onto the bus, and reads it back, checking for noise/latency/etc, so you may get the program to report a valid interface from a simple loopback interface. Certainly, using any valid linux tty, the program attempts to set the 10.4Kbps, and will report the port as OK (but interface not found), but only once before the baud is re-set manually.
It seems this behaviour has been noted before, at http://appdb.winehq.org/objectManager.php?sClass=version&iId=14255. Some seem to have managed with the launcher script given there, but I couldnt get it to work, even after fixing spelling mistakes, and it seems a bit of a hack anyway.
Thanks,
JStutch