LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Improve system response speed

Good afternoon,

I am currently developing an implementation in LabVIEW using the following hardware:

* cDAQ-9174

* NI-9208 (analog inputs)

* NI-9211 (thermocouples)

I have created a DAQ Assistant for the analog and temperature signals, and another DAQ Assistant for the digital signals. However, I am having problems with slowness in the system: reading data and updating the graph is taking too long.

I would be grateful if you could give me some guidance on how to optimize the speed of data acquisition and display. What recommendations are there to improve performance in this type of configuration?

Thank you very much for your help.

 

0 Kudos
Message 1 of 8
(286 Views)

Buenas tardes,

Actualmente me encuentro desarrollando una implementación en LabVIEW utilizando el siguiente hardware:

  • cDAQ-9174

  • NI-9208 (entradas analógicas)

  • NI-9211 (termopares)

He creado un DAQ Assistant para las señales analógicas y de temperatura, y otro DAQ Assistant para las señales digitales. Sin embargo, estoy teniendo problemas de lentitud en el sistema: la lectura de datos y la actualización del gráfico están tardando demasiado.

Agradezco si me pueden orientar sobre cómo optimizar la velocidad de adquisición y visualización de los datos. ¿Qué recomendaciones existen para mejorar el rendimiento en este tipo de configuración?

Muchas gracias por su ayuda.

0 Kudos
Message 2 of 8
(216 Views)

@cristianCR77 wrote:

Good afternoon,

I am currently developing an implementation in LabVIEW using the following hardware:

* cDAQ-9174

* NI-9208 (analog inputs)

* NI-9211 (thermocouples)

I have created a DAQ Assistant for the analog and temperature signals, and another DAQ Assistant for the digital signals. However, I am having problems with slowness in the system: reading data and updating the graph is taking too long.

I would be grateful if you could give me some guidance on how to optimize the speed of data acquisition and display. What recommendations are there to improve performance in this type of configuration?

Thank you very much for your help.


Without seeing your VI, some general advice

  1. Don't use DAQ assistant, use native DAQmx functions. Look in the example finder for ideas.
  2. Use separate loops for DAQ acquisition, processing, and display.
  3. If you are displaying a lot of points, decimate your data before display using a Min/Max decimation.
  4. If you attach a VI, save it to a previous version like 2020.
0 Kudos
Message 3 of 8
(269 Views)

It would be helpful if you could share your code.

What happens if you take the 9211 out of the picture?  That device can only sample at a max rate of 14 S/s.  If you are recording data on 4 channels, that's about 300ms.  If you have this DAQ assistant in the same loop as your analog inputs, everything will slow down to this rate. 

aputman
0 Kudos
Message 4 of 8
(260 Views)

Hello, thank you very much for your reply.

I share below the code I currently have developed, as well as the channels I have configured at the moment. I really appreciate your suggestions or observations to optimize the response speed of the system and improve the overall performance of the application.

cristianCR77_0-1747171410083.png

cristianCR77_1-1747171448757.png

 

 

0 Kudos
Message 5 of 8
(251 Views)

@cristianCR77 wrote:

cristianCR77_0-1747171410083.png


Where's the rest of the program?

There is no top-level loop (are you using "continuous run" mode???)

We see a local variable but the terminal is nowhere to be seen.

All rows have the same size, no need to measure that over and over inside a tight loop.

We have no idea what's happening inside the blue SubVI.

How do you define and measure "response speed"?

0 Kudos
Message 6 of 8
(231 Views)

Duplicated with Improve system response speed

-------------------------------------------------------
Applications Engineer | TME Systems
https://tmesystems.net/
0 Kudos
Message 7 of 8
(198 Views)

Hi cristian,

 


@cristianCR77 wrote:

I share below the code I currently have developed,…

I really appreciate your suggestions or observations…


There's a difference between "code" and "image of parts of code" - we cannot edit/debug/run images with LabVIEW.

 

When you need help then YOU need to provide (real) code and explain the whole picture!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 8 of 8
(166 Views)