How do I fix a Call Library node with an unwired or bad terminal?

[mecheng86]

I am currently working on a program that's designed to both send and recieve analog data to/from a BNC 2090. Somewhere along the line, LabVIEW came across a problem in the Call Library Node in the Create AO Channel.vi. Because of this, most of the important subVI's don't work anymore. I've attached the file I'm working on. How would I go about fixing this unusual problem?

[Hooovahh · Accepted solution]

The only reason that VI is broken to me is because it is missing the matrixbreaker.vi.

I assume you some how edited your DAQmx VIs and broke one.  These VIs should be edited and are part of the DAQmx driver.  If you did so on accident perform a repair install of DAQmx.

[mecheng86]

My mistake. matrixbreaker.vi is a VI of my own design. I now have it attached below.

[JÞB]

---

@mecheng86 wrote:

I am currently working on a program that's designed to both send and recieve analog data to/from a BNC 2090. Somewhere along the line, LabVIEW came across a problem in the Call Library Node in the Create AO Channel.vi. Because of this, most of the important subVI's don't work anymore. I've attached the file I'm working on. How would I go about fixing this unusual problem?

---

Maybe Just maybe the problem is that dynamic data type cast

the DAQ assistant is set for continuous samples and "Use Waveform timing" is checked.  you have a scalar DBL wired to the assistant for data.  Just where do you think Samples per channel and dt are going to be coming from?  Kind of hard to get them from the Size(Y) and dt components of a scalar.

[mecheng86]

I hadn't considered that. Applying that adjustment to my program might help me fix a couple of other problems I've been having. However, the heart of the problem (for me, anyway) resides in the library its trying to call. The true problem affects more than just the DAQ assistant.

[dkfire]

If your problem is with the DAQmx vi's, then try to reinstall/repair your DAQmx installation.

I do not see any problem regarding CLFN for your vi's.

But I agree, try to stay away from the Dynamic Data wires.

[JÞB]

---

@mecheng86 wrote:

I hadn't considered that. Applying that adjustment to my program might help me fix a couple of other problems I've been having. However, the heart of the problem (for me, anyway) resides in the library its trying to call. The true problem affects more than just the DAQ assistant.

---

Would those be things you noticed and went digging deep into DAQmx functions to try to solve?  Breaking CLFNs you shouldn't have?  Make via.lib read only after you repair the driver.

[mecheng86]

Sounds about right. I'll make the appropriate adjustments when I reinstall the drivers. Thanks for all of your help.