Why bother with the vm? Why not just natively run windows and save yourself a lot of time/effort?
Ah, i see. I thought he had just resorted to using windows in a vm on top of linux. If you are going to make it work in WINE, then yeah thats much better.
making progress, found a way to patch the FTDI interface here:
https://bugs.launchpad.net/ubuntu/+s...ux/+bug/460857 post #8
1) open a terminal window
2) install the latest kernel headers:
# sudo apt-get install kernel-headers-generic
3) download and uncompress the attached file ftdifix.tar.gz
4) change to the directory where you uncompressed the file, e.g.
# cd ftdifix
5) build the driver:
6) install the driver
# sudo make install
Until this is fixed, you may have to repeat these steps each time you install a new version of the kernel.
For me, the installation worked fine (the "sudo apt-get install kernal-headers-generic" was already up to date). ftdi_sio.ko seems to have been installed properly.
I believe the way to check data through my OBD2 cable should bebut nothing happens, so it leads me to believe that its still not being recognized?Code:
Another option is to use obdftdipty, which is in the obdgpslogger bundle. Put ftdi_sio in your modules blacklist, build and install obdftdipty [needs libftdi-dev].
when you run it, it tells you what pty it created. You could use that instead of /dev/ttyUSB0
Doesn't this mean its being detected?Code:
Bus 002 Device 003: ID 0403:cc4a Future Technology Devices International, Ltd product FTDI TACTRIX_OPENPORT_13U 0xcc4a OpenPort 1.3 Universal