Re : Task name specified conflicts with an existing task name.

[bmann2000]

I'm using DAQmx in a large application, much of the code I inherited.  DAQmxCreate Task is at the start of the call chain, this VI creates a Task Name defined by a hardwired String.  During debug, sometimes I stop the application before DAQmx Clear Task has executed.

The next time I try to run, I receive the error "Task name specified conflicts with an existing task name".

LabVIEW help is clear in explaining that you must execute DAQmx Clear Task within the same loop to avoid the error.  But how do I recover for the ungraceful stop that can happen during debug?  Can I programmatically clear all tasks as part of an initialization routine?

[M.athieu.]

During your debug is there an error entering your DAQMX VIs ? If yes it can prevent a proper closure / clear. 

[bmann2000]

The problem is that Clear is not executed, the application has stopped.  I then want to recover the situation without closing LabVIEW.  I know how to prevent it, but it can happen during debug when my code fails to complete a sequence.

[M.athieu.]

Sorry haven't read well 🙂 

You have to close / clear the task before running it again if you don't close LabVIEW. Maybe take a standalone VI which open / clear / close the task (using clear errors) freeing you from the problem. Then you should be able to restart normally.

[stevem181]

Try placing a Clear Task before the Create Task like this:

steve

[bmann2000]

many thanks, I did look through the available VIs, it never occurred to me that I could connect a String to the Task input.

[AshwinMiriyala]

Hello, I'm having the same issue using the nidaqmx python api.  I forgot to close the task before exiting the python interface, and now I don't know how to get back to that task to close it. Could you tell me the script to close the task now so I can re-use the task name?

What I should have done before exiting the python terminal is:

tsk=nidaqmx.task.Task('task')

tsk.close()