communicate with laptop

Asked by Lester S

Hello, I'm trying to read information from my vehicle's DTC through a scan tool into my laptop. The ST is connected to my vehicle diagnostics port & a particular USB port on the laptop & I ran in terminal lsusb & then lsusb -v -d 0403:6001 to get info about device & "Couldn't open device, some info will be missing", don't know if that has anything to do with communication. When I connect everything up, laptop to device, device to DTC & open OBD program I get options. I need to know what to type in & which option to use.
Here is what's going on so far.

lessho@LatitudeD520:~$ lsusb
Bus 001 Device 002: ID 413c:a005 Dell Computer Corp. Internal 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

lessho@LatitudeD520:~$ lsusb -v -d 0403:6001

Bus 004 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Couldn't open device, some information will be missing
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor 0x0403 Future Technology Devices International, Ltd
  idProduct 0x6001 FT232 USB-Serial (UART) IC
  bcdDevice 6.00
  iManufacturer 1
  iProduct 2
  iSerial 3
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 90mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 2
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
lessho@LatitudeD520:~

How do I send you a picture of the program screens that asks for options so you can see for the end of my question?
Thanks

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Lester S
Solved:
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said :
#1

You might get more output with

sudo lsusb -v -d 0403:6001

You cannot directly upload pictures to Launchpad questions, you have to upload the picture to any picture hosting service (imageshack etc.) and then provide the link in your question document.

Revision history for this message
Lester S (lessho) said :
#2

That gave me all my info. The main problem is the auto doctor software is asking for device path & I typed /dev/ttyUSB0 & the connection failed, what do I type in?
Thanks

Revision history for this message
Lester S (lessho) said :
#3
Revision history for this message
Manfred Hampl (m-hampl) said :
#4

What is the output of
ls -l /dev/ttyU*

Maybe you have to create a udev rule to create such device.

Revision history for this message
Lester S (lessho) said :
#5

lessho@LatitudeD520:~$ sudo ls -l /dev/ttyU*
[sudo] password for lessho:
crw-rw---- 1 root dialout 188, 0 May 3 15:31 /dev/ttyUSB0

Revision history for this message
Lester S (lessho) said :
#6

Please guide me step by step to solve.
Thanks

Revision history for this message
Manfred Hampl (m-hampl) said :
#7

are you member of the 'dialout' group?

what is the output of

whoami
id
groups

Revision history for this message
Lester S (lessho) said :
#8

Not a member of the 'dialout' group. What is that?

lessho@LatitudeD520:~$ whoami
lessho
lessho@LatitudeD520:~$ id
uid=1000(lessho) gid=1000(lessho) groups=1000(lessho),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),108(lpadmin),124(sambashare)
lessho@LatitudeD520:~$ groups
lessho adm cdrom sudo dip plugdev lpadmin sambashare
lessho@LatitudeD520:~$

Revision history for this message
Lester S (lessho) said :
#9
Revision history for this message
Manfred Hampl (m-hampl) said :
#10

Maybe it is a access rights problem.
The protection settings as shown in the ls command show that the device can only be accessed by root and by members of the dialout group. So you should become member of that group.

Try the command

sudo addgroup lessho dialout

logoff and logon again, and then retry the program for accessing /dev/ttyUSB0

Revision history for this message
Lester S (lessho) said :
#11

I never found any info. about a dialout group. Success, connection to vehicle ECU is made!
Thank U, thank U, thank U!!!! You're Great!!!!

Revision history for this message
Lester S (lessho) said :
#12

Good to go.