LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Saving current graph data

Solved!
Go to solution

I couldn't find a panel update property node. But it sounds like that would work. Here is my vi.

0 Kudos
Message 11 of 41
(3,189 Views)

Do you want a freeze button in there to do the freezing, or you just want it to freeze for a split second when you hit Acquire?

 

The terminal "Waveform Graph" is what is updating the graph. If you move that terminal to somewhere that isn't receiving data, then the graph won't change.

Cheers


--------,       Unofficial Forum Rules and Guidelines                                           ,--------

          '---   >The shortest distance between two nodes is a straight wire>   ---'


0 Kudos
Message 12 of 41
(3,179 Views)

I actually would love to stop the data from going to the graph so I can actually see what I'm about to aquire...For instance: I turn off my signal source...damping occurs. I stop the graph. I aquire what's on the graph. I know I can do this with the export function but I wanted to programatically do this somehow. I need to be able to look at my "frozen data" before I decide to aquire it.

0 Kudos
Message 13 of 41
(3,173 Views)

There must be a way to save the data left on the graph in an excel file, without having to open excel?

0 Kudos
Message 14 of 41
(3,170 Views)

Is the rest of the data still acquiring, or you just want to halt altogether?

Cheers


--------,       Unofficial Forum Rules and Guidelines                                           ,--------

          '---   >The shortest distance between two nodes is a straight wire>   ---'


0 Kudos
Message 15 of 41
(3,164 Views)

As the others have said, you should make your program in a way that allows you to stop updating the graph without completely exiting your VI. For the record, here is a way to freeze the panel using defer front panel updates.

 

Freeze Updates.png

0 Kudos
Message 16 of 41
(3,160 Views)

@Gregory wrote:

I have found that the data you export from a graph is not necessarily the raw data that you send to the graph. 


The main problem is that the formatting of the data is limited to the formatting of the axis markers. For example if you markers are "%.1f" for a pleasing look, the data will only be saved with a precision of 1 decimal digits causing serious quantiziation. (See also this old comment!)

 

(Here's a picture, sorry for the typos ;))

 

 

I typically set the formatting to a fancy format and hide the axis, but that's not always a solution. I think the current save behavior is not useful.

 

Personally, I would bypass this mechanism and instead just branch the wire going to the graph and do the saving in a custom subVI. No extra indicators needed.

 

 

Message 17 of 41
(3,148 Views)

I think freezing the graph is the least of my worries now...considering I need to actually view the frozen data before I send it to file. And I could hault aquisition...as long as the data points are still on the graph and are obtainable.

0 Kudos
Message 18 of 41
(3,138 Views)

Greg, I'm not sure I understand your snippet regarding deferring panel updates.

0 Kudos
Message 19 of 41
(3,134 Views)

You correctly called it a snippet, so I assume you've dragged it to your block diagram to view the code?

 

Was there a specific question about it?

0 Kudos
Message 20 of 41
(3,123 Views)