The CWAO.start is a Traditional NI-DAQ (Legacy) function. I suggest upgrading to the NI-DAQmx driver. With NI-DAQmx, you can use the DAQmxWaitUntilTaskDone function. More information about this can be found in the NI-DAQmx C Reference Help.
Please take a look at the Config_DAQ_Event_Message function. More information can be found in the Traditional NI-DAQ Function Reference Help. This function Notifies Traditional NI-DAQ applications when the status of an asynchronous DAQ operation (initiated by a call to DAQ_Start, DIG_Block_Out, WFM_Group_Control, and so on) meets certain criteria you specify. I think this is what you are looking for.
the Config_DAQ_Event_Message does indeed seem to have what I'm looking for. However I have two more question:
1) Will it works with CWAO.Start initiated output?
2) I am not sure how to use it in VB -- the examples in the manual are
in C, and I do not know how to read windo messages and/or pass a
reference to a callback function in VB (is that at all possible?)
Please
take a look at the Config_DAQ_Event_Message function. More
information can be found in the Traditional NI-DAQ Function Reference
Help. This function Notifies Traditional NI-DAQ applications when
the status of an asynchronous DAQ operation (initiated by a call to DAQ_Start, DIG_Block_Out, WFM_Group_Control, and so on) meets certain criteria you specify. I think this is what you are looking for.
The Config_DAQ_Event_Message function should be exactly what you are looking for. There is another function that you should take a look at as well: the progress event function. More information on this function is located in CWDAQ.chm the help file. As for your second question: there is another discussion forum that has some more information about using callback functions in VB.
