From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »
VISA USB-RAW on cRIO-9030
metux
Member
07-19-2018 10:22 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Why don't you just use the standard HID stack (as the device seems to be speak the standard USB HID protocol) ?
Linux Embedded / Kernel Hacker / BSP / Driver development / Systems engineering
Jolt
Member
07-20-2018 07:29 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi Metrux,
Can you explain your suggestion further? While I have my device and application working as described in this thread I'm always happy to gain more understanding or find a better way.
metux
Member
07-20-2018 01:22 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
@Jolt wrote:
Hi Metrux,
Can you explain your suggestion further? While I have my device and application working as described in this thread I'm always happy to gain more understanding or find a better way.
If the device is really an USB HID device (as it seems - dont have one here to confirm that), it should be automatically detected by the linux input subsystem and appear under /dev/input/ (assuming they didn't forget to compile in the generic usb hid driver).
Linux Embedded / Kernel Hacker / BSP / Driver development / Systems engineering
Jolt
Member
07-22-2018 10:38 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Maybe, and this is admittedly a bit out of my depth, but the only way I could get the device to be available through my LV code was as described above. The OS does recognize it natively as an HID device but without an address in MAX/LV I couldn't figure out how to target it with the USB Raw functions in LV.
metux
Member
07-23-2018 04:56 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Maybe, and this is admittedly a bit out of my depth, but the only way I could get the device to be available through my LV code was as described above.
I guess, LV doesn't have an binding for the standard input/event device API, you could just write one.
IIRC you can call C code from a VI, correct ? Well, then just call libevdev:
https://www.freedesktop.org/wiki/Software/libevdev/
(this library supports Linux as well as BSD).
The OS does recognize it natively as an HID device but without an address in MAX/LV I couldn't figure out how to target it with the USB Raw functions in LV.
If the driver is already bound to the device, you won't get direct access via USB subsystem.
You'd have to unbind the driver (or reconfigure udev to completely ignore that device).
OTOH, reimplementing the whole HID stack in userland isn't an entirely trivial job. I don't see much value in going through all of that, doing an completely own implementation, just for one project.
Instead I'd advice just to use the standard API.
Linux Embedded / Kernel Hacker / BSP / Driver development / Systems engineering
metux
Member
07-23-2018 05:36 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I just posted a new proposal @ idea exchange:
Linux Embedded / Kernel Hacker / BSP / Driver development / Systems engineering
- « Previous
-
- 1
- 2
- Next »
