Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Using non NI usb raw device

9 views
Skip to first unread message

DrG

unread,
Nov 9, 2004, 5:20:32 AM11/9/04
to
I have a J&J engineering physiological monitoring system,model:
I-330C2 GP Plus.
I have problem to communicate with this device. The device is a USB
RAW device, the device came with its own software, but i'd like to
develope my system using labview. This device has its own unique
command set and I don't know this command set. How can I bypass this
problem to communicate with the device using labview? If you have some
examples i'll be glad to recieve them. If anyone had worked with that
type of devices before please send me a command set.
Thank you.

JoshuaP

unread,
Nov 9, 2004, 11:05:56 AM11/9/04
to
Reverse engineering a USB device that you did not build or design is
extremely difficult to impossible without having an in-depth
understanding on all of the commands that are required to configure
and setup the device correctly. Every USB RAW device is different and
there is no stand on how the commands are layed out in the USB
firmware. You could try using some tools like USB Monitor to see what
information is being transferred when you are using the driver, but it
is not going to be easy to recreate the driver using VISA or any other
API. This isn't serial or GPIB.

You would be better off just reusing their DLL in LabVIEW. You could
use the Call Library Function Node in LabVIEW to make calls to their
DLL. This way all you have to do is figure out what functions and
parameters are required when calling their DLL. The manufacturer
might even be able to tell you exactly what all of the functions and
parameters are if they support any kind of C API. You could even put
each function in its own sub-vi, so from a high level in LabVIEW you
would only be calling sub-VIs. This may sound difficult, but it would
be easier to reuse their DLL then trying to reverse engineer the
instrument. Working with USB is just as difficult as working with
PCI.

I hope this helps out.

-Josh

0 new messages