Bad USB driver or no interrupt channel?

[Akello]

Dennis,

I'm not aware of any way to save these files to text format. As I'm new to USB monitoring so I followed the directions on the USBPcap website (http://desowin.org/usbpcap/tour.html). The only way I've been able to find in a search still requires you to download new programs so you can view it as text in the cmd prompt and frankly, that sounds like it would make things harder. I don't want to burden you with this, sifting through a bunch of USB RAW data is bad enough. 

I'll just sift through the manual and wait for the .dll sourcecode. Thanks for the advice!

Yusif Nurizade

[Intaris]

Does your sniffer program output a device descriptor for the USB device you want to connect to?  This should tell you if you have an interrupt endpoint or not and (possible more importantly) tells you the number of said endpoint.  Default is 0x80, but mileage may vary.

I've been through the USB Spec a few times and have posted a couple of nuggets on the topic (Part 1, Part 2).  You seem to be reproducing the work I've done.

If you can post a screenshot of your sniffer instead of a text file then that would at least be somewhere to start.  And please no BMPs....

Shane.

[Akello]

Shane,

Thank you for weighing in. I'm not sure if what the sniffer provides is a descripter of the device. I've attached the screenshot you requested so maybe someone with a better handle on it than me can answer that question.The last 8 bits starting with the one highlighted seem to correspond to the actual USB data send to the device and include the 0x80 you mentioned so that might be a good sign. 

I've looked at your nuggets thread and found them very informative, I've referenced them in my initial post. Currently I'm stuck on the interruptusb.vi that you mention on the first page of Part 1; I am able to run it with another control device (an old Creative VF0400 webcam) but get an error with the tachometer.

The screenshot is attached as a JPEG. This is the capture of the device connected to the laptop running XP (working driver and software) where there software is not run. I can post other screenshots or other selections of this one upon request.

Thanks again for your help,
Yusif Nurizade

[Intaris]

If you could actually post a screen of the item one lower doen in your list (which is then the response from the USB device) then that should have the info.

Shane.

[Akello]

Intaris,

I'm VERY sorry for the late reply. I'm in the process of moving and it's consumed a lot of my time in the past couple of weeks.

Here is the screenshot of the entry you requested. Thank you again for your willingness to look at it.

Sorry again for the delay,
Yusif Nurizade

[Intaris]

OK, if you could expand the "Device Descriptor" entry in the lower of the two main windows we might actually get to see something useful....

[Akello]

My apologies, how's this one?

Also, I wanted to mention that I've been reading the USB manual and it occurs to me that I may not have been sending the whole command. There are multiple mentions in the text about how a command can be too big for the max character length. The solution is to send multiple packets of maximum length that terminate in a packet that isn't maxed out or a zero data packet. It's possible that the command I was sending was not the whole message and that is why I got the timeout error. I will look into this tomorrow, turning in now, but it still would not explain why the intterupt example didn't work.

Thanks again for the help,
Yusif Nurizade

[Intaris]

I need you to think with me here.  You didn't see that there was more to the text than you have sent me?  All the interesting bits are not visible in the picture you sent me.

[Akello]

Intaris,

I'm sorry for fumbling the attachments and thank you for your patience with me.

There is no more text in the collapsible Device Descriptor option that you asked for in an earlier post. I wasn't sure if you mean the next entry or other parts of that one so I included a snapshot of every expandible option for that entry and the one after it. I also didn't crop it so you could see where the scroll bar cuts off, hope this will be sufficient.

Thanks again,
Yusif Nurizade

[Akello]

Continued:

The forum only let me attach 3 JPEGS, here are the screen catures for the next entry.

Yusif Nurizade