LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VI crashes when trying to read multiple data types

Hello everyone,

 

Background:

I am developing a VI for a wind tunnel application in Labview 2017 student edition. I acquire data from about 8-9 pressure transducers that output current, a voltage signal, and 12 thermocouples. I am working with three cDAQ 9172 chassis. I need to see the readings real time and acquire as much data as I can, so I have continuous samples and the least acquisition rate I can do is 5kHz. I have a producer consumer architecture to handle this.

 

Problem:

The way I have it set up, the VI works when I try to read only two types of signals, current and temperature, or current and voltage. However, when I try to do the three types of signals simultaneously, the VI crashes in about a minute with the error 200279 "the application is not able to keep up with hardware acquisition."

 

What I have tried:

- DAQ assistant settings: I have tried multiple combinations of samples to read and acquisition rate, sometimes I have less, other times more samples to read than my acquisition rate value and none work. 

- Current and voltage in one chassis, thermocouples in another. Also, three different DAQ assistants. (I cannot put everything in one chassis because I'm limited in the number of slots).

 

What might be able to improve the VI and recommendations I've received:

- Use DAQmx VI's instead of DAQ assistant.

- Program a circular buffer.

 

Thoughts:

In my limited experience. I feel like the error that I'm getting of the hardware acquisition is not the issue because whenever I read only two types of signals it works just fine, even when I add more channels (acquire more information). And it is only when I read three that the VI crashes. I wonder if there's another way to configure or wire my VI for it to work. Do you think I should attempt the recommended modifications as well? Any input would be awesome. I've searched so many forums and haven't found anything pertinent. I attach my VI and snips from the block diagram.

0 Kudos
Message 1 of 3
(1,331 Views)

@vdel04 wrote:

I am working with three cDAQ 9172 chassis.


Why 3 chassis?  Move your modules into a single chassis and then you can just create 1 task.  This will eliminate a lot of overhead.

 

Next, stop using Express VIs,  You can get quite a bit of performance boosts by using the DAQmx API.  You can get even more performance boost by using the File IO functions instead of the Write Measurement File (stop constantly opening and closing the file).



There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 2 of 3
(1,327 Views)

Hello crossrulz,

 

Thank you for your response and feedback! I'll address your questions.

 

1. I am limited by the number of slots in the chassis. I have one full of thermocouples and heat strips, in another one I have pressure transducers and connections to valves, and pumps. I can fit the voltage card in the second and have tried it and get the same issue, so I tried doing three chassis to maybe isolate the different kind of signal but still did not solve the issue.

 

2. Thank you for the advice, I will make this change to the VI and improve performance. I appreciate it.

 

3. Could you elaborate on the "constantly opening and closing the Write to File" please? I have my Write to File VI wired to a button and I don't touch it during the whole run, so the file is updating and expanding itself along the test writing the data. It just, is this what you mean by saying that it constantly opens and closes?

 

I appreciate your comment

0 Kudos
Message 3 of 3
(1,293 Views)