posting to list without html...
-------- Original Message --------
Subject: Re: USB question
Date: Sun, 21 Oct 2012 09:25:40 -0700
From: Charlie Sager <charsager@xxxxxxxxx>
To: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
CC:
ok, here is the output from lsusb -v
just the device in question.
================
Bus 002 Device 002: ID 1808:5555
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.01
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x1808
idProduct 0x5555
bcdDevice 0.01
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 37
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
On 10/20/2012 07:07 PM, Alan Stern wrote:
On Sat, 20 Oct 2012, Charlie Sager wrote:
Hi all,
I want to diagnose my "check engine" light in my car. I have a product
by a company called Autoenginuity. Scantool is their software that
comes with an OBD-II USB cable. The cable plugs into the car under the
dashboard. The other end of the cable is USB, and plugs into my laptop
PC. The Scantool software runs under Windows just fine. However, I want
to use my laptop which now has Ubuntu 12.04, with wine installed. I am
able to start the Scantool program under wine, but the software can't
communicate with any of comm ports, com1 through com10 (because I get a
message telling me this). Here is what I have so far:
Ubuntu 12.04
uname -r
3.2.0-26-generic
~$ lsusb before plugging in the device gives:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0402:9665 ALi Corp. Gateway Webcam
~$ lsusb after plugging in the device gives:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0402:9665 ALi Corp. Gateway Webcam
Bus 002 Device 006: ID 1808:5555
So, I'll assume vendorid=1808 productid=5555 is my device.
Please post the output from "lsusb -v" for this device.
If I type:
~$ dmesg -c
to clear the buffer, plug the device in, dmesg again and I get the
following:
[ 534.548115] usb 2-2: new low-speed USB device number 5 using uhci_hcd
[ 534.813724] generic-usb 0003:1808:5555.0004: hiddev0,hidraw0: USB HID
v1.00 Device [Multiplex Engineering USB to OBD-2] on
usb-0000:00:1d.0-2/input0
This sounds like this is my device - Multiplex Engineering USB to OBD-2
My question is, why don't I get a message like "now attached to ttyUSB0"
or similar?
The "lsusb -v" output will have your answer.
I don't know what device name to create a symbolic link to. Is "input0"
above = "ttyUSB0" or what device name?
You can't fix this problem by creating a symbolic link to anything.
I've tried creating a symbolic link in /dev by command:
ln -s /dev/usb/hiddev0 ~/.wine/dosdevices/com1
or
ln -s /dev/hidraw0 ~/.wine/dosdevices/com1
or
ln -s /dev/ttyS0 ~/.wine/dosdevices/com1
(I replaced 0 above with 1 thru 10, replaced com1 with com2 thru com10,
all these didn't work).
I tried the suggestions athttp://ubuntuforums.org/showthread.php?t=1339775
namely,
sudo modprobe usbserial vendor=0x1808 product=0x5555
Definitely the wrong approach.
But then after running dmesg again, I DID NOT see any messages with the
word "attached", such as
"usb 1-1: generic converter now attached to ttyUSB0" or similar. I only
saw the following:
[ 4253.524147] usb 2-2: new low-speed USB device number 2 using uhci_hcd
[ 4254.422816] generic-usb 0003:1808:5555.0001: hiddev0,hidraw0: USB HID
v1.00 Device [Multiplex Engineering USB to OBD-2] on
usb-0000:00:1d.0-2/input0
[ 4254.422893] usbcore: registered new interface driver usbhid
[ 4254.422901] usbhid: USB HID core driver
[ 4280.120573] usbcore: registered new interface driver usbserial
[ 4280.120642] USB Serial support registered for generic
[ 4280.120730] usbcore: registered new interface driver usbserial_generic
[ 4280.120739] usbserial: USB Serial Driver core
again the same output from:
diff before.txt after.txt
18a19
> hidraw0
175a177
> usb
And Scantool still does not communicate to any com ports.
Any thoughts on how to find out what named device in /dev is being assigned?
Nothing is being assigned. That's why symbolic links won't accomplish
anything -- there's nothing to link to.
How do I get it to "attach" to a name that I can create a symbolic link
to in ~/.wine/dosdevices/com1 ?
We can't answer that without seeing the "lsusb -v" output.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
