Page 7 of 8 FirstFirst 12345678 LastLast
Results 61 to 70 of 75

Thread: Trying to get USB OBD2 interface to work...

  1. #61
    Low Bitrate
    Join Date
    Jan 2009
    Posts
    67
    Quote Originally Posted by redleader36 View Post
    evoscan version 2.5 does have settings for choosing a com port! if anyone needs a copy, let me know.
    Have you had any luck getting evoscan to interface w/ the cable? I went down the same road you are going, and hoping that 2.5 would allow you to select a com port. notice it wont let you change between com 1, 2, 3, or 4.

    That being said, I *think* the problem really lies with the Ubuntu 9.10 ftdi drivers. Since Ubuntu wont properly detect the cable, Evoscan and Wine have no chance. This is based on all the previous work i did with Gary (last couple pages).

    To test this theory, one could downgrade to ubuntu 9.04, install wine and ubuntu and see if there is any luck. I have seen numerous posts of "similar" Windows Based OBD2/CAN logging tools that do work in Wine, but the tutorials were written using older versions of ubuntu.

    Just to clarify from your previous comments: Playonlinux is based on Wine. The trouble hasn't been getting the application to run, but has always been interfacing it with the cable. I have posted how to setup symbolic links, but if Ubuntu wont recognize the cable we are at a dead end for now.

    Please report back w/ your findings. As another enthusiast stated: "Windows doesn't deserve a partition on my hard drive"

  2. #62
    North of the land of Hey Huns
    Auto Apps:loading...

    Join Date
    Jun 2004
    Location
    Westminster, MD
    Posts
    2,127
    Supposedly the FTDI issue introduced in 9.10 is fixed in the kernel in karmic-proposed... at least in theory. If it is not recognising the USB cable at all as it seems is the case with you (There's no /dev/ttyUSB* I assume) perhaps try upgrading?
    "stop with the REINSTALLS, what do you think we got some lame-o installer!!!" - mitchjs
    RevFE
    My Shop

  3. #63
    Low Bitrate
    Join Date
    Jan 2009
    Posts
    67
    interesting... I am fully upgraded on 9.10. Evoscan installed and pointing to Com1. When I put in my cable it is recognized as ttyUSB1 (ttyUSB0 is my 3g chip).

    created a symbolic link:
    sudo -s
    ln -s /dev/ttyUSB1 ~/.wine/dosdevices/com1
    No worky still

    ...
    On a side note: Evoscan relies on the tactrix drivers that are packaged in ECUflash. I think these drivers continuously fail when trying to install them. Perhaps I have been barking up the wrong tree... maybe this isn't a linux issue instead a Windows driver install issue...

  4. #64
    North of the land of Hey Huns
    Auto Apps:loading...

    Join Date
    Jun 2004
    Location
    Westminster, MD
    Posts
    2,127
    Can you open /dev/ttyUSB1 in screen or some other serial client and see if you can talk to the device manually?
    "stop with the REINSTALLS, what do you think we got some lame-o installer!!!" - mitchjs
    RevFE
    My Shop

  5. #65
    Low Bitrate
    Join Date
    Jan 2009
    Posts
    67
    screen /dev/ttyUSB1
    get a blank screen, now what?

  6. #66
    Newbie redleader36's Avatar
    Join Date
    Dec 2007
    Posts
    16
    Quote Originally Posted by unsungboxer View Post
    Have you had any luck getting evoscan to interface w/ the cable?
    I have not gotten evoscan to recognize my cable in linux yet. I should mention i am using a vag-com cable instead of a tactrix, but I have confirmed this cable to work while booting the pc into windows.

    Quote Originally Posted by unsungboxer View Post
    I went down the same road you are going, and hoping that 2.5 would allow you to select a com port. notice it wont let you change between com 1, 2, 3, or 4.
    Here is a screenshot of my version of evoscan 2.5 and it does allow you to select com1-4.


    Quote Originally Posted by unsungboxer View Post
    That being said, I *think* the problem really lies with the Ubuntu 9.10 ftdi drivers. . . To test this theory, one could downgrade to ubuntu 9.04, install wine and ubuntu and see if there is any luck. I have seen numerous posts of "similar" Windows Based OBD2/CAN logging tools that do work in Wine, but the tutorials were written using older versions of ubuntu.
    I am already running Kubuntu 9.04. I can't upgrade any farther because my ati card is now considered legacy and I am stuck with 8.10 graphic drivers on a 9.04 system.

    Quote Originally Posted by unsungboxer View Post
    Just to clarify from your previous comments: Playonlinux is based on Wine. The trouble hasn't been getting the application to run, but has always been interfacing it with the cable. I have posted how to setup symbolic links, but if Ubuntu wont recognize the cable we are at a dead end for now.

    Please report back w/ your findings. As another enthusiast stated: "Windows doesn't deserve a partition on my hard drive"
    I understand Playonlinux is just a python front end for organizing multiple versions of wine and different prefixes for each program. I only tried it because winetricks would not work for me and it already had an install option for dotnet 2.0.

    I have tried linking my appropriate ttyUSB0 device to com1 in my playonlinux prefix's dosdevices directory, to no avail.

    i noticed evoscan2.5 comes up with error for "Error: Unable to load DLL 'FTD2XX.dll': Exception from HRESULT: 0x8007007E" when trying to connect. Could this be a roadblock?

    sorry if thats alot of concerns in one post. I would love to figure this out. I also hate dual booting!

  7. #67
    Low Bitrate
    Join Date
    Jan 2009
    Posts
    67
    Quote Originally Posted by redleader36 View Post
    I have not gotten evoscan to recognize my cable in linux yet. I should mention i am using a vag-com cable instead of a tactrix, but I have confirmed this cable to work while booting the pc into windows.

    Here is a screenshot of my version of evoscan 2.5 and it does allow you to select com1-4.



    i noticed evoscan2.5 comes up with error for "Error: Unable to load DLL 'FTD2XX.dll': Exception from HRESULT: 0x8007007E" when trying to connect. Could this be a roadblock?
    I think you and I have come to the same conclusion, which is good someone else is working this with me.

    Couple things:

    1. Since you are using 9.04, this is ruling out my theory that this is a 9.10 driver issue. Malcom's post a minute ago brought me to the same conclusion.

    2. Vag Com is the program that I have seen documentation of working with Wine/Ubuntu using a symbolic link. So this is proof of concept that it *should* work.

    3. Your screenshot is what I am seeing in my install too. Notice that it won't actually allow you to select a different port. it gives you the option, but the check mark wont move. This makes me think that evoscan isn't really seeing the ports (or the symbolic ones). I have tried making symbolic links using "com4", no luck.

    *** I am now starting to think this comes down to figuring out how to install the cable drivers in wine. I have a feeling our cables are essentially the same. the search continues...

    btw, AIM: unsungboxer if you wanna chat bout it

  8. #68
    Low Bitrate
    Join Date
    Jan 2009
    Posts
    67
    Few more thoughts...

    1. Try downloading and installing ECUflash (which contains tactrix and FTDI drivers) .. notice it fails when it gets to the tactrix CDM drivers...
    http://www.openecu.org/index.php?title=EcuFlash

    2. Since the drivers can't be installed via the install shield, maybe we should try manually downloading the FTDI drivers from this site, then extract them and put them in the rigth directories? (I am really just making this up as I go)
    http://www.ftdichip.com/Drivers/D2XX.htm

  9. #69
    Newbie redleader36's Avatar
    Join Date
    Dec 2007
    Posts
    16
    do we actually need the windows drivers, or do we just need evoscan to think the tactrix drivers are installed? i don't think wine actually supports windows drivers, just the application layer.

  10. #70
    Low Bitrate
    Join Date
    Jan 2009
    Posts
    67
    Quote Originally Posted by redleader36 View Post
    do we actually need the windows drivers, or do we just need evoscan to think the tactrix drivers are installed? i don't think wine actually supports windows drivers, just the application layer.
    I am really not sure actually? Are you using a serial cable or usb?

Page 7 of 8 FirstFirst 12345678 LastLast

Similar Threads

  1. Replies: 0
    Last Post: 12-01-2008, 05:48 PM
  2. QUESTION about M2-160WATT AND X-TREME CARPC
    By kostas_lion in forum Power Supplies
    Replies: 3
    Last Post: 05-15-2008, 10:50 AM
  3. Modular Shutdown Controller with USB Interface
    By evandude in forum Power Supplies
    Replies: 11
    Last Post: 02-19-2007, 12:57 PM
  4. Problem with ITPS / hibernation and External USB HD
    By veetid in forum Power Supplies
    Replies: 5
    Last Post: 01-02-2006, 09:35 PM
  5. are usb 2.0 devices able to work with usb 1.1 hubs?
    By chris in nh in forum General Hardware Discussion
    Replies: 9
    Last Post: 06-28-2004, 08:27 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •