LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why nothing is displayed in FFT graph?

WOW!
Much better now.
However, the data displayed in the charts seems to be...lot more dense than before. That is, now I seem to have much more points in the graphs than before. Probably because before I wasn't reading the files correctly.
PROBLEM: when I read the binary file some data is displayed in the graphs. If I read the same data again or new data, the old data is apparently not cleared - the new data is appended to the old data. This can be seen clearly in the graph for Fz; I'm not so sure about the other graphs where the data might just superimpose (this might be why it looked so dense to me? - I'm not sure here).
Could you suggest a solution for this problem?
I'm not sure if this is coming from the way the file is read or from some settings of the charts...A possible solution I see at this point would be to 'tell' the vi to clear the charts before new data is read but I'm not sure how to do this. Besides, would this really solve the problem or it would be just a 'work-around' the real problem...

Thank you for your help! I would have never imagined it would be so much trouble to correctly read a file for data analysis in LabVIEW... Thanks God for the 'Forum' and nice people like you.
0 Kudos
Message 11 of 16
(969 Views)
"Thanks God for the 'Forum' and nice people like you. "

Five star ratings are a good way to thank volunteers like Dennis.

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 12 of 16
(959 Views)
OK, thank you Ben.
0 Kudos
Message 13 of 16
(952 Views)
Anybody can answer my last question: How to avoid overwritting/appending to old graphs?
0 Kudos
Message 14 of 16
(944 Views)
Hello RPJ,

The Force F(z) graph is showing appended data because it using data from an uninitialized shift register.

An uninitialized shift register will retain its data from previous executions and in this case it results in appending data to the previous waveform. Initializing the shift register with an empty waveform (like the other shift registers) will prevent this behavior.

Regards,

Matt F
Message 15 of 16
(922 Views)
Thank you Matt.
I must have been really tired not to see that...
Everything's working fine now.

Regards,
Radu
0 Kudos
Message 16 of 16
(907 Views)