Windows hEvent in LabVIEW 5.1.1

[mpeltzer]

I am developing LabVIEW applications that utilize in-house hardware on various Windows environments. Part of the driver API for these devices make use of Windows hEvents for interrupt handling.

So far I have been unsucessful in using the 'Call Library Function' vi to create and communicate with an hEvent.

I have also not found any information about this in the LabVIEW documentation, Google Groups, this forum, or the internet at large.

Any information (like, if this is even possible) is greatly apperciated.

[Jeremy Braden]

I took a crack a finding an answer and came up empty. Can you use activeX events instead? You might consider writing a C dll that can process the hEvents and output the semiprocessed data into LabVIEW. It would work like an intermediary dll to interface LabVIEW with the hEvent dll.

[wiebe@CARYA]

Hi,

I've created a set of vi's that wait for serial port events.

The vi waits until anything is send to the port. Unfortunately, this also
means that the vi cannot be stopped normally (you'll get the "resetting vi"
dialog).

Is this what you mean?

Regards,

Wiebe.


"mpeltzer" wrote in message
news:506500000008000000427C0000-1042324653000@exchange.ni.com...
> I am developing LabVIEW applications that utilize in-house hardware on
> various Windows environments. Part of the driver API for these
> devices make use of Windows hEvents for interrupt handling.
>
> So far I have been unsucessful in using the 'Call Library Function' vi
> to create and communicate with an hEvent.
>
> I have also not found any information about this in the LabVIEW
> docum
entation, Google Groups, this forum, or the internet at large.
>
> Any information (like, if this is even possible) is greatly
> apperciated.

[mpeltzer]

No, this is not what I mean at all.

But the good news is that I was able to use the WIN32 API as I thought I might. I simply used 'Call Library Funciton' nodes to call out to 'CreateEvent', 'WaitForSingleObject', and 'CloseHandle'. My problems were actually not with the LabVIEW to WIN32 bridge, but in how I was using my internal API.

[wiebe@CARYA]

Hi,

That is the same set of MS Api's that I used...

To be precice, I used CreateFile, SetCommMask, WaitCommEvent and ReadFile.
These are all in the same list, but a bit more specific for the serial
port...

Regards,

Wiebe.


"mpeltzer" wrote in message
news:5065000000050000000DDF0000-1042324653000@exchange.ni.com...
> No, this is not what I mean at all.
>
> But the good news is that I was able to use the WIN32 API as I thought
> I might. I simply used 'Call Library Funciton' nodes to call out to
> 'CreateEvent', 'WaitForSingleObject', and 'CloseHandle'. My problems
> were actually not with the LabVIEW to WIN32 bridge, but in how I was
> using my internal API.