From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW XY Graph slows down the application

Hi,

 

if the XY graph is filled with a lot of data a tab change slows down the application.
Enclosed the VI with three curves with 100k data points each.

 

Are there any UI elements other than the XY graph or options that prevent a redraw?

 

Any Ideas?

The amount of data to be displayed should not be reduced.

 

Thanks

B/R

Bastian

0 Kudos
Message 1 of 3
(722 Views)

Hi Stocki,

 


@Stocki wrote:

if the XY graph is filled with a lot of data a tab change slows down the application.

Any Ideas?


Use a different point style, like the small "+" or just a small ".". This already speeds up the graph a litte bit…

 


@Stocki wrote:

Enclosed the VI with three curves with 100k data points each.

 

The amount of data to be displayed should not be reduced.


It doesn't make a lot of sense to display 3×100k points in a graph of just ~700×250 pixel size.

I really recommend to reduce the size of your plots…

 


@Stocki wrote:

Are there any UI elements other than the XY graph or options that prevent a redraw?


When you place the graph on a tab container and switch between tabs then LabVIEW has to redraw the tab content when it becomes visible again…

Idea: don't place the graph in a tab container!

Best regards,
GerdW


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

+ Use singles in stead of doubles... Less data to copy, more speed.

 

+In stead of drawing the points, draw only the new points in the graph's embedded picture (Picture front, back or middle). This sounds like a lot of CPU power, but you can keep a 2D array in memory, and only add a point to it, then update the graph's picture. You do need to update all points when the scale (X or Y) changes. Or disable scaling (if possible). I've used this once for a project where the number of points where pretty much infinite.

0 Kudos
Message 3 of 3
(705 Views)