LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

USB-HID Can't communicate

Solved!
Go to solution

Or maybe taking the definition of "Human Input Device" a little too literally and applying it to a microphone.....

 

Can't help thinking that HID (which only supports Control and Interrupt Endpoints) won't be terribly good for transmitting Audio.......

0 Kudos
Message 11 of 31
(1,593 Views)

@Intaris wrote:

Or maybe taking the definition of "Human Input Device" a little too literally and applying it to a microphone.....

 

Can't help thinking that HID (which only supports Control and Interrupt Endpoints) won't be terribly good for transmitting Audio.......


Well, unless you need high fidelity 512kS/s, 5+1 channel surround audio input, it's not that much of data for nowadays CPUs. 😀

 

An Intel Core 7 chip could get a 64kS/s data stream easily one by one through polling. 😀

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 12 of 31
(1,588 Views)

Sorry.   What I want to express is that what I want to communicate is an audio device, which integrates some USB HID commands, but Labview does not seem to have USB HID module.

0 Kudos
Message 13 of 31
(1,574 Views)

Sorry.  This audio device integrates USB HID commands, but Labview does not seem to have USB HID module.

0 Kudos
Message 14 of 31
(1,573 Views)

@hy12369 wrote:

Sorry.  This audio device integrates USB HID commands, but Labview does not seem to have USB HID module.


You got that totally right! But it can be done if you pull up your sleeves and get your hands dirty on your keyboard! 😀

 

And to the various comments: It is highly unusual to have an audio device connect to the computer through HID, since HID is anything but suited to do data streaming. So instead of repeating 4 times that it is an audio HID device it would be a lot more helpful to actually name the type and model and/or attach a manual to your post.

 

I can't help to agree with Intaris that there is a good chance that your claim of this being a USB HID device may be actually misinformed.

 

 

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 15 of 31
(1,567 Views)

@hy12369 wrote:

Sorry.   What I want to express is that what I want to communicate is an audio device, which integrates some USB HID commands, but Labview does not seem to have USB HID module.


Yes, it does. See this previous answer.

0 Kudos
Message 16 of 31
(1,560 Views)

wiebe@CARYA wrote:

@hy12369 wrote:

Sorry.   What I want to express is that what I want to communicate is an audio device, which integrates some USB HID commands, but Labview does not seem to have USB HID module.


Yes, it does. See this previous answer.


It's nitpicking but that API is technically not talking HID. Instead it accesses Windows Multimedia functions which present any type of joystick and similar game controller devices to the application in a somewhat generic manner. That almost all joysticks nowadays are in fact USB connected and therefore use HID communication is irrelevant for the LabVIEW VIs in question. It could be also a serial or parallel port connected joystick device as they were 25 years ago.

And this API won't expose special extensions such as in XBox and Playstation controllers present.

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 17 of 31
(1,557 Views)

 


@rolfk wrote:

wiebe@CARYA wrote:

@hy12369 wrote:

Sorry.   What I want to express is that what I want to communicate is an audio device, which integrates some USB HID commands, but Labview does not seem to have USB HID module.


Yes, it does. See this previous answer.


It's nitpicking but that API is technically not talking HID. Instead it accesses Windows Multimedia functions which present any type of joystick and similar game controller devices to the application in a somewhat generic manner. That almost all joysticks nowadays are in fact USB connected and therefore use HID communication is irrelevant for the LabVIEW VIs in question. It could be also a serial or parallel port connected joystick device as they were 25 years ago.

And this API won't expose special extensions such as in XBox and Playstation controllers present.


I've used XInputGetState to interface an PS2 controller, but it won't do PS3.

 

I did mention it will work for some HID devices, and it would be the first thing I try. If it works, you'd be done in 20 minutes, if not, look for something else...

 

EDIT: Some details about this Sound\HID device and it's commands would help... We're now creating our own undirected problems, not directed solutions.

0 Kudos
Message 18 of 31
(1,549 Views)

wiebe@CARYA wrote:

 

EDIT: Some details about this Sound\HID device and it's commands would help... We're now creating our own undirected problems, not directed solutions.


That's what much of our remarks to the OP actually were about. Sound together with HID sounds bogus. Not saying it can't exist, but it would be a poor choice by the device designer. And even if it is based on HID, the Input Device Control VIs won't really be helpful. They are not meant to work with Sound input devices but with Keyboards, Joysticks and similar devices.

 

If the device manufacturer has developed a Windows multimedia driver however, the Sound VIs would pick that device up automatically and the actual protocol would be totally irrelevant.

 

So yes what device is it? Where are the technical details about it? What software drivers if any does it come with?

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 19 of 31
(1,539 Views)

@rolfk wrote:

wiebe@CARYA wrote:

 

EDIT: Some details about this Sound\HID device and it's commands would help... We're now creating our own undirected problems, not directed solutions.


That's what much of our remarks to the OP actually were about. Sound together with HID sounds bogus. Not saying it can't exist, but it would be a poor choice by the device designer. And even if it is based on HID, the Input Device Control VIs won't really be helpful. They are not meant to work with Sound input devices but with Keyboards, Joysticks and similar devices.

 

If the device manufacturer has developed a Windows multimedia driver however, the Sound VIs would pick that device up automatically and the actual protocol would be totally irrelevant.

 

So yes what device is it? Where are the technical details about it? What software drivers if any does it come with?


It seems HID sound devices aren't that unusual:

 

 

https://en.wikipedia.org/wiki/Human_interface_device, Under HIDs for output:

 

 

Specifically for the USB_human_interface_device_class, under Other_devices:

automobile simulation controllers, exercise machines, telephony devices, thermometers, audio controls and medical instrumentation

 

So OP might actually be right... However, more info would help.

0 Kudos
Message 20 of 31
(1,527 Views)