Recent Posts

Pages: [1] 2 3 ... 10
1
USB / Re: input report too short
« Last post by Jan Axelson on April 24, 2017, 09:44:38 am »
In the routine ExchangeInputAndOutputReports, this line:

Array.Resize(outputReportBuffer, MyHid.Capabilities.OutputReportByteLength)

sets outputReportBuffer to match the output report length returned by the device during enumeration.

I would start by examining this value.
2
USB / Re: input report too short
« Last post by fotosettore on April 23, 2017, 08:30:47 pm »
hi jan

i solved enlarging the dimension of INPUT BUFFER (the answer of inverter) using the instruction                 

Capabilities.InputReportByteLength = 200

in Hid.vb file
now i can read all bytes of answer string !

now there is another problem  :( about data to send to inverter (OUTPUT BUFFER)
sending a command to inverter that is more than 9 bytes gives error
all commands that are shorter of 9 are ok and all works fine. Over gives error.
i tried to set
Capabilities.OutputReportByteLength = 15
in Hid.vb
and change
Dim outputReportBuffer() As Byte = Nothing
to
Dim outputReportBuffer(15) As Byte
but i did not solved : it does not work and gives error

please note that i'm using generic_hid_vb_50 and it seems does not permit to enlarge output buffer
please note that Usbhidio2 works fine without errors of in or out
 
so ... any idea ?


3
USB / Re: input report too short
« Last post by Jan Axelson on April 22, 2017, 09:07:49 pm »
From here:

http://janaxelson.com/hidpage.htm#MyExampleCode

Under the heading:

My example code

The C# code is here:

Visual C# (C Sharp)

generic_hid_cs_62

and the VB code is here:

Visual Basic .NET

generic_hid_vb_50
4
USB / Re: input report too short
« Last post by towlerg on April 22, 2017, 01:03:17 pm »
Sorry if I'm being dull but I can't find the utility, could you be more specific (like what heading is it under).
5
USB / Re: WinUSB Read Pipe
« Last post by Jan Axelson on April 20, 2017, 09:14:36 pm »
If enumeration succeeds, the device will appear in Device Manager.

The host can issue a reset whenever it wants. Typically, once enumeration is complete, the host would issue a reset only in an attempt to recover from repeated communication failures or other major bus problem.

To find out why you are getting a DEVICE_NOT_CONNECTED error, use whatever debugging tools you have to verify that the IN endpoint is always ready to either return NAK or send data on receiving an IN token packet.

_Immediately_ after sending data, the IN endpoint should be ready to return NAK or data in response to the next token packet.

If you can slow the transfers by adding delays between reads and the problem goes away, that will tell you it's a timing issue.
6
USB / Re: input report too short
« Last post by Jan Axelson on April 20, 2017, 12:57:01 pm »
That looks like my application. fotosettore is using VB so it's not the most recent version. The applications are here:

http://janaxelson.com/hidpage.htm#MyExampleCode
7
USB / Re: input report too short
« Last post by towlerg on April 20, 2017, 08:16:35 am »
Quote
If you are asking who wrote the Generic HID application at janaxelson.com, I did.

I'm curious about the program that was screen dumped in reply #2
8
USB / Re: WinUSB Read Pipe
« Last post by sudheerg_ on April 20, 2017, 07:24:06 am »
Some how we are able to find that there is a enumeration from Host to Target.

In what scenarios the Host can initiate USB Bus Reset to target.

I have verified WinUsb_GetPowerPolicy and for the parameter AUTO_SUSPEND it returns a value 0, means auto suspend is not enabled.

Any suggestions on how to debug this issue.
9
USB / Re: input report too short
« Last post by Jan Axelson on April 19, 2017, 11:02:08 am »
If you are asking who wrote the Generic HID application at janaxelson.com, I did.
10
USB / Re: input report too short
« Last post by towlerg on April 18, 2017, 04:38:15 pm »
Where does the Generic HID tester come from?
Pages: [1] 2 3 ... 10