Error -200089

[ehalpin13]

Hi everyone,

I keep getting error code -200089 and I can't find any proper description of what that error is. It seems to be coming from the create task vi and stops the code from taking any data. I've attached a snippet of the block diagram.

Any help at all would be appreciated!

[aptivo]

This means: Task name specified conflicts with an existing task name.

Simply rename the task. That should fix your issue.
All LabVIEW error codes can be found inside the folder: "C:\Program Files\National Instruments\Shared\Errors\English" 

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P8tFSAS&l

[crossrulz]

Help->Explain Error.  And you will see the error description be "Task name specified conflicts with an existing task name."  This tells me you are not properly clearing your task(s).  But to clear out you current situation, you just need to shutdown LabVIEW and start it back up.  But you need to make sure your task is cleared by your application when you are done with it.

[ehalpin13]

Thank you that removed that error! Now another error is present with this description

<nierror code="-50103">
The specified resource is reserved. The operation could not be completed as specified.

What does this mean?

[crossrulz]

---

@ehalpin13 wrote:

Thank you that removed that error! Now another error is present with this description

<nierror code="-50103">
The specified resource is reserved. The operation could not be completed as specified.

What does this mean?

---

It means there is another task that has your device's channel(s) reserved.  This is a mutex to keep multiple tasks from using the same resource.  Are you stopping and clearing out your tasks?

[ehalpin13]

I have attached my code below. These are the only tasks with these channels so I'm confused about how to fix this.

[aptivo]

In your event structure you have to make ensure that the terminals for the DAQmx wires are wired, otherwise your task won't be closed correctly.

(it will use the fefault value for the DAQmx task and not the value which has been previously created)

[GerdW]

Hi ehalpin,

never use "default if unwired" tunnels for references! NEVER!

Right now your DAQmx tasks (mostly) never get stopped/cleared…

Other problems:

• Buttons belong into their event cases.
• You should not use that DAQ loop inside the event case… (Read the full help for event structures!)
• You still don't use the Ramp function…
• …

[crossrulz · Accepted solution]

I would actually move the closing of the tasks into the Stop event case.  Then you really don't have to worry about the "Use Default If Unwired" setting on the Event Structure.  But you could help yourself a lot just cleaning by up your VI.

• Avoid wire bends
• Line up related VIs
• Use the Ramp Pattern VI to generate an array of points that you can then autoindex on