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: 

Sound & Vibration, Order Analysis: parameters and strange results

Hi,

 

I'm using the Sound and Vibration toolkit to do order analysis. My VI takes temporal data as input (analyzed channels + tachometer) and generates a graph of amplitude vs tachometer frequency.

 

I basically use the two express vi depicted hereunder:

 

Order tracking.png

 

 

 

My problem is that there are very few informations about the effect of the parameters of the method and their relationship.

 

For instance:

- what is exactly the "bandwidth [order]" parameter? It seems to determine the number of revolution taken into account for the analysis. Am I correct?

 

-  does the size of the block of data that is inputed to the VI have an influence on the results? If yes what is the influence?

 

- It seems that the time the order analysis VI takes is longer for each new iteration. Isn't there some kind of memory leak somewhere or   memory not correclty prealocated?

 

- Does the frequency at which the tachometer is computed have an influence on the resulting order tracking graph?

 

- I get very "edgy" results like if the computation was made in steps (see picture). How is it possible?Is there a way to correct that effect?

 

Edgy sweep.png

 

 

 

Thanks in advance

 

peper

0 Kudos
Message 1 of 2
(2,411 Views)

Hi Peper,

 

Bandwidth [order]—Specifies an order span centered at the order that you specify in Orders to track. Specify a Bandwidth [order] value between 0.01 and 1. If Bandwidth [order] is less than 0.01, the Bandwidth [order] sets to 0.01. If Bandwidth [order] is greater than 1, the Bandwidth [order] sets to 1. The default is 1. It can be realted to revolution, time or speed(rpm), and it is set when you configure the order tracking VI.
 
The size of the block data could delay the results, bringing also memory leakages, but I cannot say that for sure without seeing your code.
 
0 Kudos
Message 2 of 2
(2,374 Views)