Quote:
Originally Posted by Invictus3593
WE just want Labview to read/initialize it as a joystick like the other USB stick we use, but this one just has maybe a couple toggle switches, a few buttons and status LED's for certain conditions.
If the uno is incapable of being a Human Interface Device, then can labview at least read the value of the pins to do the same thing?
We didn't get a Cypress board with our kit this year, we're veteran. Would the Cyress be easier to use with Labview if we bought that instead?
Thank you guys for all the quick responses!!
|
I'm not familiar with how a HID would be implemented, but I've never seen it done before, as there are simpler alternatives - namely the Cypress and the CCI.
If you really
need both I and O, then the Cypress would indeed be easier to use as a framework is already in place to implement it. If you only need I, however, then the CCI may be a simpler option. It's a product offered by eStop Robotics that emulates a USB Joystick and allows you to feed sensor input to the robot through the Driver Station.
If you've never done this before, I would suggest going with the CCI as it is a much simpler and robust product to work with. Think about how critical being able to send outputs to your operator interface is - how often is your operator going to look down at his control panel while he's behind that glass? Is he going to be able to interpret that data and actually use it in a match?
Alternatively, as previously mentioned, you can use the Teensy (4334 has a whitepaper here on CD about their implementation of it as a), which can emulate a USB Joystick. Alternatively, it can be implemented as a HID or serial device. Keep in mind that when a device is implemented as a Joystick, it is only capable of feeding input to your system - it cannot receive output.