ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problemas con chart

hola, buen día¿ porque cuando le pongo un chart a mi señal tengo perdida de datos al almacenar información, pero si quito el chart los datos se almacenan correctamente.

0 Kudos
Message 1 of 7
(1,286 Views)

Hi Javo,

 


@Javo20200 wrote:

Hello, good day, because when I put a chart on my signal I have data loss when storing information, but if I remove the chart the data is stored correctly.


Simple solution: don't use a chart!

 

When you want more detailed/not the simplest suggestions: please attach your VI!

Downconvert (File->Save for previous) to an older LV version when you use one of the recent versions. I prefer LV2019.

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 7
(1,251 Views)

I attach the program

0 Kudos
Message 3 of 7
(1,217 Views)

Hi Javo,

 

could you please downconvert to LV2019 and attach again? (File->Save for previous)

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 7
(1,193 Views)

I'm not an expert, I'm a student, but I need to finish my project so I can get a degree, sorry for my English, I'm using a translator, I speak Spanish. I attach the 2019 version.

Download All
0 Kudos
Message 5 of 7
(1,187 Views)

I am designing a program for an EEG, 4 channels of 250 data per second each. I use the "mpusbapi" library from microchip. Without graphing I have no loss of data, if I put the chart my data presents losses, it is my only problem.

0 Kudos
Message 6 of 7
(1,180 Views)

Hi Javo,

 


@Javo20200 wrote:

Without graphing I have no loss of data, if I put the chart my data presents losses, it is my only problem.


So the chart update takes too much time and you need to reduce that impact…

 

General recommendations:

  • Replace all local variables by wires, especially all those "bandera" and "write handle" variables! There are race conditions hiding behind local variables…
  • Cleanup the code to make it more readable! Left-to-right wiring, subVIs instead of duplicated code, and so on!
  • Replace ExpressVIs by plain functions to reduce the impact of their (computational) overhead!
  • You already use a poducer-consumer scheme to separate DAQ from other task: use one more producer-consumer to also separate the data display from your analysis loop!
  • Don't update the chart too often (I don't see any loop iteration speed indication). Charts only needs to be updated <= 10 times per second…
  • You use a notifier to send data from TDMS loop to analysis loop: there is an EXPECTED loss of data! Why do you use a notifier?
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 7 of 7
(1,173 Views)