Measurement Computing ADAC-LVi - Manual (Page 121)

Chapter 2 Buffer Config Library
ADAC LabVIEW VI 115
ADAC Get Buffer Done Handler
This VI gets the buffer done message handler method. The internal ADAC-LVi buffers
can be accessed in LabVIEW by either polling the buffer status information for a
completed buffer (CHECK_BUFFER) or asynchronously by using a LabVIEW
occurrence to receive buffer done messages (POST_MESSAGE_PARAMS). If
POST_MESSAGE_PARAMS is selected an additional call to ADAC Occurrence
Config.vi must be made to configure the occurrence.
The occurrence can then be set to "wait on occurrence", this effectively puts your VI to
sleep saving precious processor time until a buffer done message is sent or the wait on
occurrence times out.
The ADAC Occurrence Config.VI automatically sets the Done Handler to
POST_MESSAGE_PARAMS and calls AL_SetBufferDoneHandlerMsg to configure the
occurrence done buffer messages to LabVIEW.
Device Handle (0) Device Handle is a numeric value that is used to identify the device
subsystem. The default Device Handle is 0.
error in (no error) Error in describes error conditions occurring before this VI executes.
This cluster defaults to no error.
Device Handle out Device Handle out contains the value of Device Handle in.
Done Handler Done Handler is a numeric value of the current hardware buffer done
handler method set in the ADAC-LVi driver. The available options are:
0:CHECK_BUFFER Buffers are polled for completion.
1:POST_MESSAGE_PARAMS A windows message is posted to a LabVIEW
occurrence. The information to configure the occurrence must be processed by a call to
ADAC Occurrence Config.vi.
See the ADAC Occurrence Config.VI.