Hi:
Thanks in advance for your help. I am REALLY need some guidance.
I am tasked with bringing device control & data from our USB device into Labview. This is, um, *interesting* because I am basically clueless about Labview. I laid eyes on the v7.0 eval copy today for the first time. I have been studying the manuals, the website, and these forums to get familiar.
To start with, what I have today is a C++ API for controlling our device. Once configured, the C++ API object delivers continuous data asynchronously to the owner using Windows messages.
First, I gather that using the DLL external code method to get to my API functions will not work for the async data that I want to capture. Is this correct? Or is
there a way to catch windows messages or supply a callback to external code? Would a CIN be able to do this?
If the above is true: then I could wrap my API into a COM object and set up an event handler in Labview. [ The example code for this is very hard for me to follow. I'm "challenged" by the visual nature of Labview.. ] Also, I am concerned about the performance of that approach.
Also, using our API, it is possible to configure it to pump the continuous data out a windows "named pipe." However, I noticed another post out there lamenting the fact that there is no VI for windows named pipes. Is that correct?
Third: How does any of this relate to creating a device driver? I imagine that a driver could/would just bypass the API DLL and read/write straight into our windows USB device driver (although I haven't seen any examples of such).
Does anyone have any thoughts on these questions? What would you do?
Or
Does anyone see that I am missing something important
here?
Sorry for the mile-long post.
Thank you VERY much-
Suz.