Each type of hardware (PCI/PCIe and cDAQ) has a limited number of concurrent hardware sessions available. This limits the number of concurrent tasks an application can call simultaneously.
DAQmx Clear Task.vi
DAQmx Control Task.vi
Don't abort the execution using the abort button if you are using a while loop to read or write and the Clear task is executed after the loop. Use the Stop Button attached to the conditional terminal of the Loop instead.Case 7: Attempting to use a task in NI-MAX while it is being used by a running LabVIEW program. If a LabVIEW program is currently running your DAQmx task to acquire data, then it will reserve the hardware resource corresponding to this task. This means that NI-MAX will be unable to concurrently access this hardware resource, or device.To prevent this conflict, you can either perform any NI-MAX actions before or after running your LabVIEW program, or while your program is stalling in a state before DAQmx Start Task has been called or after DAQmx Clear Task has been called. These functions reserve and release hardware resources, respectively.Case 8: Using the wrong source for a counter taskMake sure that the source you are selecting is supported for the task you are trying to run. (for example, wiring in an internal counter for a digital edge instead of the onboard clock).
Thank you for your feedback.
You changed your response to Not Helpful
You changed your response to Helpful
Collaborate with other users in our discussion forums
A valid service agreement may be required, and support options vary by country.