From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
I don't know of any property that would indicate the state of a CWAI object. Perhaps you can trap the error that you get back from the board and do an ON ERROR RESUME NEXT to ignore the error. This would work if the second CWAI.Stop didn't lock up the DAQ board or something like that.
Another possibility is to attach a parasitic boolean variable to each instance of .Start and .Stop to keep track of the state of the CWAI. You could then check the value of this variable to see whether or not the CWAI is running. This assumes that there are no other hardware-related ways that start or stop the CWAI; these would render the boolean variable unreliable.