Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
USB descriptors are supported only up to 8.1 according to your link. And libwdi/zadig is useful links for me, thank you very much! I'll be used ones in my other projects. But I don't need to new USB driver in Windows due to I'll get much more problems with put all together in LabView. I want to use standard WIndows USB-Serial that always present and directly supported via VISA. The NI-VISA isn't using specific protocols for USB. The VISA is just an intermediate level for most of the serial protocols in the NI ecosystem. I'm operating low-level USB packets, commands, responses in the same manner as in C for example but from LabView. But I have to generate the specific INF file which needs for recognition of VISA for each one of the specific instances with a unique USB PID/UID. The problem is mandatory signing such INF files in Windows10 and I'm looking for any way to avoid this.
Well you could try performing some man in the middle but apart from that I think your best choice is to use some sort of pre built USB stack or maybe an FTDI with custom hardware.
Related posts
- I need help with my saber files uploading to my saber
- Bluetooth Passthrough: Easier libusbK driver swapping with a config file and batch script.
- SDR Software for Windows Surface RT for ARM 32 bit
- Can’t get avrdude to work
- Warn if (Windows ISO) media will no longer be bootable after Q1 2024 (Rufus)