Anyone succesfully wrapped winusb.dll in Labview code?

[Daklu]

As the subject says, I'm looking to wrap winusb.dll funtionality in a LV class or library and wondering if anyone else has successfully done it already.  I found one old post where the author unsuccessfully attempted to use the shared library import wizard, but there wasn't any follow up. 

We currently wrap winusb calls in a private .Net assembly and call that assembly from our LV code.  Functionally this works fine, but since LV's dll calls store absolute paths to the dlls we end up with a lot of cross-linking when other devs open the project or we try to create reusable code modules that rely on the dll.  If we linked to winusb.dll directly I think we would avoid that problem.

TIA,

Dave

[Jusborne68]

Hi Daklu,

I'm in the process of implimenting the same functionality. How did this go? Did you take this on or take a different approach?

Thanks,

Billybones.

[Intaris]

If anyone gets a wrapper up and going, pleasse let me know.  I'd love to incorporate WInUSB into my USB class library.  I currently only have VISA and LibUSB and WinUSB (And OS-specific HID) is the next target but I'm weak at C.

Shane.

[rolfk]

WinUSB doesn't look that complicated to interface, but the question remains, do you want this to be 64 Bit compatible or possible to run pre 8.6. Both together are only possible with an extra external Library and lots of vodoo.

[Intaris]

Well for me personally, 64-bit and since my approach is LVOOP-based and uses functions only introduced post 2009, 8.6 compatibility is not required.

Do you have experience interfacint WInUSB directly from LV?

Shane.

[rolfk]

---

@Intaris wrote:

Do you have experience interfacint WInUSB directly from LV?

Shane.

---

Not so far with WinUSB but a lot of other C APIs. But I took a look at MSDN and it doesn't seem that complicated.

You are aware that WinUSB has limits in what is supported, such as no Isochronous transfer at all?

[Intaris]

I am aware, just as I am apparently aware (Unless someone can tellme otherwise) that the windiows VISA USB is built on WinUSB.....

Hence no isochronous support in VISA.....

Shane.

[Jusborne68]

Unfortunately, I'm stuck using 8.2.1 as the company that I'm contracting to is very tight on money and software updates are at the bottom of their priority list. What happened post 8.6 that made this task easier? If there was a compelling reason to upgrade I could probably talk them into it but I still may have to support 8.2.1 as well.

If I could get VISA to work I would be going that direction but I need to interrogate the port as fast as possible (every 1-2 mSec) and the VISA timeout for some reason has a minimum settable value of 50 mSec. I talked to NI about this and they don't know why this limit is there but ut is.

John.

[Daklu]

---

@Jusborne68 wrote:

Hi Daklu,

I'm in the process of implimenting the same functionality. How did this go? Did you take this on or take a different approach?

Thanks,

Billybones.

---

It never went anywhere.  It kept getting pushed back by other priorities and I've since forgotten about it.

[Jusborne68]

I know how that goes. Thanks for the response.